Data pooped out on me on the cm9 build. Tried dirty flashing over it but to no avail. I'll probably flash aokp in the morning to see if it holds out longer.
Upvote
0
Data pooped out on me on the cm9 build. Tried dirty flashing over it but to no avail. I'll probably flash aokp in the morning to see if it holds out longer.
Get a logcat of the radio and post it on pastebin. You should have wifi off just to make sure it tries to connect. Start the log at boot and let it go for at least 5 min.
adb logcat -b radio > radio.log
Can someone running the CM9 build from TDM run GPS test and use the compass feature. I need to know if anyone else is getting reversed readings from north and south (I have 3 real compasses that all say it's backwards).
how did you fix the bluetooth? was it in the kernel? or in the rom itself? cause if its in the rom then i might be able to fix it in mine
I'm running the CM9 beta 1 and its working right for me. What compass app are you using?
Can someone running the CM9 build from TDM run GPS test and use the compass feature.
GPS Test has a virtual compass in it that works off the phones magnetic sensors. I played around with it a bit and changed it from true north to magnetic north and it finally starting working correctly.hes not using a compass app, he's using real compasses.
TDM:
digging thru more logs and came upon this.
[ 01-08 00:10:06.434 468:0x1e8 W/WiredAccessoryObserver ]
This kernel does not have wired headset support
Know anything about why that would be or if it's an easily fixable option?
Don't know.. never seen that before. But we should find out what it means. Thanks!
Are you set to CDMA only in the network type menu? If it was LTE/CDMA i would expect to see some GSM commands being sent.tdm, here's the link to the radio log. Sorry I didn't get it sooner. My wife was dragging me all over today and I haven't had time until now. I didn't get it right from bootup but I did start it soon thereafter. From what I can see, it's some kind of error from lteOnCdmaProductType. Of course, I don't really know much about this yet so I'm most likely wrong.
[ 12-15 22:53:19.090 438:0x388 E/LocSvc_eng ]
I/===> int loc_eng_set_position_mode(loc_eng_data_s_type&, LocPosMode&) line 583
[ 12-15 22:53:19.090 438:0x389 D/LocSvc_adapter ]
loc_eng_set_position mode, client = -1234, interval = 1000, mode = 1
[ 12-15 22:53:19.090 438:0x389 E/LocSvc_api_rpc_glue ]
slot not available ioctl_type = RPC_LOC_IOCTL_SET_FIX_CRITERIA
[ 12-15 22:53:19.090 438:0x388 E/LocSvc_eng ]
I/===> int loc_eng_start(loc_eng_data_s_type&) line 444
[ 12-15 22:53:19.090 438:0x389 E/LocSvc_api_rpc_glue ]
I/---> loc_start_fix line 422 -1234
Has anyone else noticed that when you close the notification drawer in an app that the screen flickers? I'm getting this in both CM9 and AOKP. sometimes when this happens the app closes. Not a force close ( or at least I don't get the pop up ) but just closes.
As far as I can tell, both have data that can be finicky any time you reboot into recovery. I always keep data through regular reboots on both CM9 and AOKP and when I use recovery, cycling the radio on/off a few times always brings it back for me.So if I understand the posts correctly, AOKP is working great with data, but CM9 has some glitches?
I only as because I need my phone to be 100% for work. I can handle some glitches, but I have to have data to get email 24/7.
So if I understand the posts correctly, AOKP is working great with data, but CM9 has some glitches?
I only as because I need my phone to be 100% for work. I can handle some glitches, but I have to have data to get email 24/7.
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.