Hi all,
I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.
Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M
The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.
I have logcat in *:V and nothing is ejected that looks suspect, it just ends.
I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.
My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
Wipster said:
Hi all,
I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.
Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M
The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.
I have logcat in *:V and nothing is ejected that looks suspect, it just ends.
I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.
My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
Click to expand...
Click to collapse
There are people who report crashes when phone connects to GSM instead of WCDMA, you can lock your phone to WCDMA Only on the testing menu (dial *#*#4636#*#* and go to "Phone information").
Also, changing ROM might help. there is officialy built CM10, and CM10.1 is quite stable (I'm using it myself as a daily driver for a month now). Also there are many Sense ROMs which are very stable.
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
Wipster said:
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
Click to expand...
Click to collapse
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
astar26 said:
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
Click to expand...
Click to collapse
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.
I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.
Thanks
Wipster said:
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.
I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.
Thanks
Click to expand...
Click to collapse
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
astar26 said:
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
Click to expand...
Click to collapse
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.
Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.
Edit: Attached is the kmsg for CM10 at a crash.
Wipster said:
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.
Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.
Edit: Attached is the kmsg for CM10 at a crash.
Click to expand...
Click to collapse
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.
You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
astar26 said:
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.
You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
Click to expand...
Click to collapse
It was stock CM9 and CM10 I have tried, no other kernels.
With the CM10 image, can I just install a kernel from another ROM and it 'work' or do I need to change roms over to test?
I upgraded the radio (11.76A.3504.00U_11.24A.3504.31_M) using the latest RUU and then plopped my CM10 backup back on and so far so good, signal seems better however I'm sure that's placebo, will keep you posted.
Edit: OK so upgrading the radio did nothing whatsoever. Still crashing.
Attached is a nice crash, stops at msm_pm_power_collapse something to do with shutting down CPU, maybe for clock change, I have changed the minimum clock freq to 384Mhz just in case mine is a device which cant do 192mhz.
Just tried Albinomans ROM and its still crashing.
Attached is the kmsg and the logcat in verbose mode.
Related
I'm using CM7 Eaglesblood 2.8 with the T15 Trinity kernel.
My problem is that my GPS won't turn on after my phone has been on for a while. I'm not 100% sure after what exactly the GPS stops working, but so far every day I try to use it after my phone has been on for a day, this error occurs.
It works once I reboot, but I don't want to have to reboot my phone every time I wish to use my GPS.
Some details:
-the GPS is enabled, but the icon in the notification bar doesn't turn on when I am atttempting to use GPS
-I've attempted using a series of apps that use GPS and this behavior is consistent throughout all of them
-I've experienced the same issue on the newest CM7 Hellfire ROM with the faux SV and OC/UV 048 kernels which makes me think this is an issue with CM7 or the G2X
-I've used GPS status and it produced no results
-I've searched this error through both your forum search and Google. Google produced some results, but none of them helped
So my question, or rather request, is to know whether or not I'm the only one having this problem. I use my GPS a lot, so this is very annoying. Also if someone was having this problem, I'd like to know how they fixed it (and also if they didn't)
GPS is properly fixed in 21y firmware the stock 2.3.4 release, but that means no custom roms.
Sent from my LG-P999 using XDA
Hmm okay, thanks. Well in any case, I have a custom ROM which I rather use than the stock. Is there a solution available for CM7 users?
Possibly unrelated, but yesterday my GPS started becoming inaccurate as well as malfunctional. I haven't changed anything, so I'm thinking it's similar to when data is slow some days. If that's the case, it'll fix itself over time.
The original problem still remains, however. Right now I'm under the impression that this is a problem that doesn't have a solution.
I had nothing but trouble with GPS on my G2X. I even exchanged the phone twice in an attempt to get one with a decent GPS. All the symptoms you describe would occur on my phone. Sometimes I'd have to do multiple reboots to get it working again. Since I updated the baseband last week it's been working much, much better.
I miss running CM, and I hope that devs will find a way to make custom ROMs work with the new baseband, but I'd rather have a working phone than a custom ROM. In addition to the GPS issue, my random lock-ups haven't appeared yet either. Granted I haven't had this update on my phone a full week yet, so I can't be certain that it's fixed all the problems yet.
Hi,
I rooted my phone a couple of days back & upgraded to ICS using Hellfire v1.8 rom.
Since I was getting lags, I also got the flak0's lag fix.
I have started facing an issue the phone would freeze post a long call on the phone screen, I can't even get it to reboot by pressing 'lock+vol up' button. The only way is to remove the battery & put it back.
I saw a similar issue seen in this thread from partzman2:
http://forum.xda-developers.com/showthread.php?p=28342782#post28342782
But unfortunately, I am unable to comment on the thread as I don't have enough posts in my name. I searched the forums for this issue, but couldn't find a solution.
Any help is appreciated.
My sincere thanks to dev folks
Just wanted to take a moment to thank the dev folks who put in a lot of work in creating these roms/mods - experience is so much better, I can't even begin to explain.
I have had g2x for more than 14 months now & I had been running stock froyo 1st & then GB (2.3.3) - the experience was so bad, that I used it only for making phone calls or occasional emails, as i couldn't even browse or do anything w/o hitting some problem or the other. Even phone calls used to crash at times.
After updating to ICS, I haven't stopped using the phone be it browsing, watching you tube videos, trying new apps, emails etc, with occasional phone calls .
Again, thanks a lot for so much hard work, its really appreciated.
gg84 said:
Just wanted to take a moment to thank the dev folks who put in a lot of work in creating these roms/mods - experience is so much better, I can't even begin to explain.
I have had g2x for more than 14 months now & I had been running stock froyo 1st & then GB (2.3.3) - the experience was so bad, that I used it only for making phone calls or occasional emails, as i couldn't even browse or do anything w/o hitting some problem or the other. Even phone calls used to crash at times.
After updating to ICS, I haven't stopped using the phone be it browsing, watching you tube videos, trying new apps, emails etc, with occasional phone calls .
Again, thanks a lot for so much hard work, its really appreciated.
Click to expand...
Click to collapse
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here: http://download.cyanogenmod.com/?type=nightly&device=tenderloin
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Blazing angel said:
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here:
[//gg84 - I had to snip out the link as I am not even allowed to post a link which actually someone else had put & I am just quoting //]
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Click to expand...
Click to collapse
Thanks for the info. Actually, I went through quite a bit of dev threads before deciding to go with ICS - I was quite curios about its features & was ready to take the risk.
Only thing is that owain's recent 79 build seemed to have quite a bit of issues from the posts, & hellfire seemed a bit old/stable, so went with that. I didn't consider using old owain's builds (which might be an overlook from my part).
Is there a way I can find what I might lose (& possibly gain), if I switch to owain's 77 build?
I am using Jul15, 2011 baseband & kernel is 2.6.32.59-CM9-faux123-050.
Is there a better baseband/kernel that I should try?
I switched the kernel to harsh kernel & I feel that the speed has improved, but "freezing on a call randomly" issue still exists. Also, it crashes & reboots once in a while but I still feel that its worth all the pain as now I am actually able to make use of the phone.
Blazing Angel, did you find the latest baseband which I can try using?
Another bug I found is that I cannot really configure the lock screen buttons/shortcuts - as in adding a an app to be able to accessed from the lock screen like we do for camera. I see the option of changing this in setting but it doesn't persist when I try to change it.
Anyone seeing this?
gg84 said:
I switched the kernel to harsh kernel & I feel that the speed has improved, but "freezing on a call randomly" issue still exists. Also, it crashes & reboots once in a while but I still feel that its worth all the pain as now I am actually able to make use of the phone.
Blazing Angel, did you find the latest baseband which I can try using?
Another bug I found is that I cannot really configure the lock screen buttons/shortcuts - as in adding a an app to be able to accessed from the lock screen like we do for camera. I see the option of changing this in setting but it doesn't persist when I try to change it.
Anyone seeing this?
Click to expand...
Click to collapse
The latest baseband is march 2012. To update, you need to install Tmobile's V21Y update.
Follow this guide
http://forum.xda-developers.com/showthread.php?t=1674901
Note: If you install this, and try to use a rom other than CM7 7.2.0, you need to flash owains New_baseband fix after flashing a rom from here
http://owain.hopto.org/T-Mobile LG...w_baseband.zip
Hi just want to add info with new baseband the bluetooth doesn't work.
Blazing angel said:
Hi, welcome to XDA :fingers-crossed:
I have some sort of sad news for you. In general-- ICS on the G2X isn't really stable right now. A lot of rom's have problems with lag after a few weeks, graphical errors, rebooting, and phone calles (as you mentioned). I'm not sure exactly how to fix your problem, but I had it too. I couldn't find a suitable fix, so i went back to Cyangogenmod 7 (gingerbread)
The latest nightly (newest build uploaded on their server) is available here: http://download.cyanogenmod.com/?type=nightly&device=tenderloin
If you are NOT using the march 2012 baseband, flash "old_baseband.zip". I am looking for the file (not sure what thread it is in).
What baseband are you one?
Also, If you must try ics, i suggest Owain's build 77. It's one of the most stable I've found so far.
I'll update post soon.
Click to expand...
Click to collapse
some of that i experienced my self , most of the times the camera and hdmi port is sacrificed in the g2x
Thanks for the info guys. Say my gps works/locks already (takes a bit of time though) with the hellfire ICS, is there anything I get by flashing this new baseband?
Does it or would it fix the random freezing on calls by any chance?
Basically, I read the instructions & it seems that I'd have to go back to stock, unroot & then re-root + reflash + restore my apps etc - seems like too much if I am not getting something out of it.
If it doesn't add much value, then I will consider doing it once another stable version of hellfire or owain's rom is released..
BTW, did anyone experience the lock screen config issue I posted in my earlier post - basically I can't add custom short cuts to the lock screen, there is an option to do this in the settings but they dont stick (I am on hellfire v1.8 right now)
I wanted to thank the developers of MR3 in this thread. Liquid, Jester, etc.
I'm a long time lurker of this forum since I got my Thunderbolt. I'm VERY VERY appreciative of the developers for creating a very functional ICS rom for the Thunderbolt. Shame on HTC and Verizon for sandbagging so long with what should be a very simple upgrade for them. I was running Thundershed for awhile but grew tired of the Gingerbread look and feel of Android. My friends all mostly have newer phones with ICS, and I couldn't believe that it was supposed to be out in August and it's now mid-October and it's still not out.
To my surprise, I log on to here and see that an ICS ROM had been released.
My only issues with this ROM are random restarts and the white screen error in Facebook/Gmail/etc. I don't really use the video camera much in general; could you use an aftermarket app, or is it broken period?
Otherwise, I absolutely LOVE this and will never go back to Verizon's bloated software. Even when an OTA is released with ICS I won't go back. My phone is running much faster and much better than with Sense and Gingerbread. With data off I had a 10% decrease in battery in 7 hours; with data on and normal use I'll get maybe 5 hours out of a charge on this ROM. About normal for this phone and it's absolutely terrible battery life with the stock battery.
I have it overclocked to 1.5ghz running interactiveX as my governor. It runs beautifully, other than those two minor issues I pointed out above. I haven't experienced any data drops or anything out of the sort like that.
vashts80 said:
I wanted to thank the developers of MR3 in this thread. Liquid, Jester, etc.
I'm a long time lurker of this forum since I got my Thunderbolt. I'm VERY VERY appreciative of the developers for creating a very functional ICS rom for the Thunderbolt. Shame on HTC and Verizon for sandbagging so long with what should be a very simple upgrade for them. I was running Thundershed for awhile but grew tired of the Gingerbread look and feel of Android. My friends all mostly have newer phones with ICS, and I couldn't believe that it was supposed to be out in August and it's now mid-October and it's still not out.
To my surprise, I log on to here and see that an ICS ROM had been released.
My only issues with this ROM are random restarts and the white screen error in Facebook/Gmail/etc. I don't really use the video camera much in general; could you use an aftermarket app, or is it broken period?
Otherwise, I absolutely LOVE this and will never go back to Verizon's bloated software. Even when an OTA is released with ICS I won't go back. My phone is running much faster and much better than with Sense and Gingerbread. With data off I had a 10% decrease in battery in 7 hours; with data on and normal use I'll get maybe 5 hours out of a charge on this ROM. About normal for this phone and it's absolutely terrible battery life with the stock battery.
I have it overclocked to 1.5ghz running interactiveX as my governor. It runs beautifully, other than those two minor issues I pointed out above. I haven't experienced any data drops or anything out of the sort like that.
Click to expand...
Click to collapse
I second this thread.
A major thanks goes out to all of you who develop, in any way, for the Thunderbolt community. This even includes testers.
To answer your questions...
The video and front camera are broken even with an aftermarket app and will remain broken, most likely, until Verizon releases the OTA. From the OTA, our awesome developers will then be able to fix camera issues and many other issues that will make their ROM's 100% stable.
Also, if you get random reboots, you may want to flash to a different radio.
If you are currently running the OTA radios from the 2.11.605.19 software and still get these reboots, try flashing the combo radio and hopefully the reboots will vanish or, at least, happen less often.
If you go to your settings, about phone, software information, more, and look at the baseband version...
If the numbers you see are:
1.49.00.0406w_1, 0.01.79.0331w_1
Then you are on the OTA 2.11.605.19 radios, which is my recommendation for the radios to use with this ROM. If these are the radio numbers you see, try the combo radio. If the numbers you see under your phones baseband version is not:
1.49.00.0406w_1, 0.01.79.0331w_1
Then it may be:
1.48.00.0930w_3, 0.01.78.0916w_3
If it is:
1.48.00.0930w_3, 0.01.78.0916w_3
Try flashing the 2.11.605.19 OTA radios found here:
http://forum.xda-developers.com/showthread.php?t=1605557
If you have the 2.11.605.19 radios, though, try flashing the combo radio found here:
http://forum.xda-developers.com/showthread.php?t=1864157
If you aren't sure how to flash a radio, here's a video tutorial for you to follow:
http://www.youtube.com/watch?v=eu-KLjHGGhc&sns=em
Sent from my ADR6400L using xda premium
Definitely want to ditto this thread. Thanks for continuing to support the Thunderbolt. I was on the verge of retiring the Thunderbolt. ICS has brought new the Tbolt new life though!
thanks for the links. I'm going to try upgrading tonight and see if that helps. I notice you flash the radio in hboot. If I do a nandroid backup, does it also backup the radio (so I can restore it)? Or if I **** up, will it be permanently bricked?
Ditto to all that has been said. Thank You to all who made this happen, including HTC and Verizon. Their inaction drove me to decide to root and find alternatives. I've been incredibly pleased with MR3.
Thanks all!
Sent from the Great Beyond using XDA App
vashts80 said:
thanks for the links. I'm going to try upgrading tonight and see if that helps. I notice you flash the radio in hboot. If I do a nandroid backup, does it also backup the radio (so I can restore it)? Or if I **** up, will it be permanently bricked?
Click to expand...
Click to collapse
If you backup that ROM after flashing the radio, it will back up the ROM. Hboot is a whole different thing than the recovery. That radio is downloaded to the phone and will automatically run on any ROM after its downloaded, even if you start from scratch. But flashing any of those two radios will not brick you on any ROM. Worst case being you won't have signal or data until you flash different radios again.
Say if you upgraded to the newer radios, and then you flash a ROM based on an older software version, you won't brick. In fact, you may not ever experience any issues. Maybe just signal changes or random signal drops.
But no, it won't brick you. It's almost impossible to brick a Thunderbolt.
I recommend after flashing the new radios, immediately go and either change the name from PG05IMG to something custom, move into a different folder that's off of the root of the SD card, or just delete it once flashed.
This is for in a such case where you need to get back into recovery from hboot, it won't prompt you to install the radio again. Because if you had to get into recovery from hboot, it wouldn't allow you to since it runs a check for the PG05IMG files first... and with that being said... I was always told to never flash the same radio twice without changing to a new one first.
Sent from my ADR6400L using xda premium
i dont' see why these ROMs get so much acclaim... when i tried LiquidSmooth it wouldn't stay connected to the Internet. tried to toggle wifi and 3G/4G. nothing works and i have to reboot the phone every time i want to use the Internet.
Liquid MR3: the setup crashed and now the ROM won't even come all the way up...
unless my phone's broken or something (going to Verizon tomorrow to reflash and check it), i say they're both absolute garbage. i've had much better luck with ROMs on other phones.
moonlightcheese said:
i dont' see why these ROMs get so much acclaim... when i tried LiquidSmooth it wouldn't stay connected to the Internet. tried to toggle wifi and 3G/4G. nothing works and i have to reboot the phone every time i want to use the Internet.
Liquid MR3: the setup crashed and now the ROM won't even come all the way up...
unless my phone's broken or something (going to Verizon tomorrow to reflash and check it), i say they're both absolute garbage. i've had much better luck with ROMs on other phones.
Click to expand...
Click to collapse
Did you try a different radio and redownload? The first shot isnt always the right one....
trter10 said:
Did you try a different radio and redownload? The first shot isnt always the right one....
Click to expand...
Click to collapse
whelp... as you can see from my post number, i'm not exactly the most well-versed member around. idk what that means. any reading you can point me to or explanation?
moonlightcheese said:
whelp... as you can see from my post number, i'm not exactly the most well-versed member around. idk what that means. any reading you can point me to or explanation?
Click to expand...
Click to collapse
Back up 9 posts and you'll see a link to a video tutorial on how to flash a different radio. You'll even see 2 links to 2 different radios to flash and try.
Sent from my ADR6400L using xda premium
RBarnett09 said:
Back up 9 posts and you'll see a link to a video tutorial on how to flash a different radio. You'll even see 2 links to 2 different radios to flash and try.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
well i reflashed Liquid this morning and it didn't crash this time, connected fine via wifi and setup completed properly.
all of my radio issues were on the old version (not sure if there's a difference in radios or whatnot), but if it acts up again i will try your recommendations. thanks a lot.
---------- Post added at 11:08 AM ---------- Previous post was at 10:52 AM ----------
moonlightcheese said:
well i reflashed Liquid this morning and it didn't crash this time, connected fine via wifi and setup completed properly.
all of my radio issues were on the old version (not sure if there's a difference in radios or whatnot), but if it acts up again i will try your recommendations. thanks a lot.
Click to expand...
Click to collapse
ah i see what happened now.
the first time i flashed it, i cleared /data after the flash before i brought the OS up, but you've included the launcher as a user app and not a system app. was this intentional? a user could easily screw up by uninstalling the launcher and have no way to interact with the OS. shouldn't there be a default launcher embedded in the system programs?
i'm an Android dev, but my understanding of system development is limited, but if i'm not mistaken, any Android ROM should come with a default launcher that is not uninstallable and has no icon as a backup launcher just in case.
He did install it that way so if the user wants to install their own launcher and remove the default. Its simple to make the new one a system app. All that has to be done is move the apk to /system and it is uninstallable.
Sent from my Thunderbolt using Tapatalk 2
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
rpod83 said:
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
Click to expand...
Click to collapse
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
MagicalHobo said:
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
Click to expand...
Click to collapse
Thanks, MagicalHobo. Did you ever try a different ROM with success?
rpod83 said:
Thanks, MagicalHobo. Did you ever try a different ROM with success?
Click to expand...
Click to collapse
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
biglittlegato said:
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Click to expand...
Click to collapse
From my experience, GPS works perfectly on aospx.
I saw a new "nightly" has been pushed out for the Relay. Based on the changelog (fixing integer overflows and underflows), this looks like a fix for Stagefright.
I've updated from within the 20150607 nightly, and so far, everything looks good. My GPS and camera still work fine, and I didn't bother toggling any settings before updating.
At least I have ONE phone with a Stagefright fix. It's kind of ironic that it's the oldest of my Androids.
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
So I guess it's time to bite the bullet and do the double-twist-and-backflip GPS fix. Let me go over this for a moment, to get it straight.
I need a new CWM recovery, latest'n'greatest.
I need and old 10.1 or maybe 10.2 ROM image.
I need the old baseband firmware to go with the old ROM image.
Is this the full list?
There have been numerous links to all three of these, but I tried last week, and at least some of them have gone stale. Does anyone have a current and working set of links for them?
My wife's Relay is still at CM11M8, and really it's about time I got her properly flashed forward, especially now with Stagefright and Freak both fixed. We've locked out on Stagefright so far because we have voice-only through PureTalkUSA, only do data on wifi, and therefore don't do MMS.
GPS fix:
You need a CM10.1 build (Only ones ever produced were 'experimental'), the ICS stock baseband (modem) and the JB stock baseband. Recovery doesn't particularly matter, so long as you can flash images, but I still recommend the CWM that has been around for a while (I've tested it, it works fine even with upcoming Images)
Procedure:
Boot into recovery, run a full backup on your device.
flash ICS baseband
Flash CM10.1 Image
Factory Reset
Boot into system (Not sure if this is needed, but I always do.)
Once system boots up, shut system down.
Open phone, pull battery.
Wait ~30 seconds, replace battery.
Boot phone.
Once system boots up, (If you have a way to test it, GPS should work now). Reboot into recovery.
Flash JB baseband.
Restore your system backup.
Reboot into system. Your GPS should now work with your current system.
I posted a reply into a thread, there was an up to date link with just the modem... I can confirm that running on CM nightly (june something) I have no issues with GPS, wifi 2.4ghz band doesnt work with bluetooth enabled though
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
phred14 said:
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
Click to expand...
Click to collapse
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
dzl said:
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
Click to expand...
Click to collapse
I got my Relay about a year and a half ago for Christmas, mostly as a learning vehicle, but also for the convenience. The plan from the get-go was to put Cyanogenmod on it. For a while it was wifi-only, then a few months later my wife decided she wanted one, and I found the Family Flex Plan at PureTalkUSA that let us have two phones for the the cost of a Virgin Mobile and TracFone. (What we had before) It's also one of the few ways to get voice-only, and use wifi for data.
The Relay is getting a bit long in the tooth, and perhaps most discouraging "aging" side of it is the ramp-down here. However anything I get will be CM-ready from the get-go.
Flashed the latest CM11 nightly today. No major bugs so far with moderate use throughout the day. So much faster than my Xperia with the stock firmware, actually enjoying Android again.
Sent from my SGH-T699 using XDA Free mobile app
20150823
I had been running M8 since it came out until last weekend. Decided to do a complete wipe and try for the newest nightly to fix the Stagefright bug. Things went real smooth. GPS is working faster than ever.
Everything runs like a dream... except the adaptive light sensor. Adaptive brightness is not working at all. I've check the sensors and the Lux sensor is working fine. If I turn on adaptive brightness, and then adjust, the settings crash. Anyone else experiencing anything like this?
Yeah that is one thing that I have noticed as well, the auto brightness doesn't work. Can't say I've attempted to diagnose it at all though.
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
TPMJB said:
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
Click to expand...
Click to collapse
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
phred14 said:
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
Click to expand...
Click to collapse
I would like for updates to CM12, but we only have unofficial versions of CM12. I am a noob at compiling and I hear it is an arduous task to get it working.
Magamo said:
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
Click to expand...
Click to collapse
Some time between then and now (some time in September, I believe) the stagefright fixes were backported to the omni-4.4 branch. I have a build from this running on my relay right now and Zimperium gives it a clean bill of health.
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
kodimagnyl said:
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
Click to expand...
Click to collapse
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
i have a rooted stock rom, can i move to the latest cm11 nightly build?
phred14 said:
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
Click to expand...
Click to collapse
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
kodimagnyl said:
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
Click to expand...
Click to collapse
Can't reach the second link, but I've already got a copy of the current modem, the old one is what I've been missing. Things are starting to get busy, so I don't know how soon I'll be able to try it.
BTW, I've been told to do a "nandroid backup", then wipe and load the back-level stuff, do the GPS fix, then a "nandroid restore". I'm going to presume that the backup / restore doesn't handle the modem, and on my way back from back-level, I'll first have to use heimdall to reload the current modem?
Thanks