Related
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.
The GPS takes 5 minutes to lock, and it does it at 1600 meters (un)accuracy.
It behaves like this no matter what rom i try (Sky, Slim, CM9/10, Embryo etc), except for stock Rogers ICS.
The agps patch and other gps patches on XDA didn't do anything.
When i first bought it, it had stock Rogers ICS and GPS worked perfectly, never mind the fact that i live in EU.
Then i tried custom roms and it started to funk around and has been doing as long as i run a custom rom.
Today i installed Rogers ICS as a last resort and suddenly the GPS locks in seconds and with great accuracy too (9 meters).
And so the question, what the hell is causing this?
OR
How do i make the GPS work with the custom roms?
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
rpr69 said:
I have been running custom ROM's since a day after I got my Skyrocket, and the AGPS patch has never failed to work for me. I have been running CM10 for pretty much the last 4+ months, and GPS always works. Not sure what your issue might be.
Click to expand...
Click to collapse
I'm not sure either.. The phone is canadian with a Rogers brand on battery cover. When i install a stock AT&T rom the GPS more or less dies.
Any other rom and the GPS dies. Stock Rogers ICS rom and voila works like a clockwork.
And it doesn't react at all to any GPS patch, and i've tried like 10 different ones. aGPS is not new to me, i've successfully used it on other phones. But for some reason it doesn't do anything for my Skyrocket.
Mike on XDA said:
You can flash agps patch from Boombah's aroma installer. Always works for me
------------------------------------------------------------------------
Sent from my Skyrocket i727 w/ Blinky'sRevenge
-----------------Nexus 7 running AOKP M1-----------------
Click to expand...
Click to collapse
Thanks i'll try that, just don't see how Aroma is going to help if it's the same patch i've tried earlier.
On the other hand, with ghouly issues like this who knows what might help and what won't ?
Worst case scenario is that i'll be stuck with Rogers FW if i want working GPS, which is acceptable with some tweaks especially the Droid Razr M launcher
The thread is here: http://forum.xda-developers.com/showthread.php?t=1732304
--------------------------------------------------------------------
Sent from my Skyrocket i727 running Team Dirt
--------------Nexus 7 running AOKP PUB--------------
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
icenight89 said:
Did u by any chance leave location access for Google apps disabled? If u did on AOSP ROMs GPS will never lock
Click to expand...
Click to collapse
Nope, it's always turned on.
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Jack_R1 said:
If SW doesn't solve/change anything - where might the problem be? Yes, that's right, it's probably in HW!
Check your GPS antenna contacts (antenna is inside the inner plastic, the one you see when you open back cover and remove the battery). Bend them a bit and clean their contact points to make sure they contact well.
If your phone is still within warranty or the above doesn't help - replace it.
Click to expand...
Click to collapse
Hi Jack_R1
Software does indeed solve everything. In short: stock rogers ics rom = perfect gps, custom rom/stock at&t rom= no gps.
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Jack_R1 said:
Oops. Guess I skipped some lines reading the OP - returned and found your line talking about it. Sorry about that.
Did you try reinstalling custom ROMs after you got quick lock on stock ROM, to test that the issue remains?
I'd suggest a couple of things:
1. Try installing AT&T ICS ROM for testing. If it also gives you a good lock - you'll have better reference point.
2. Look at the APN you use in Rogers' ROM and in other ROMs. If you're using automatic ones - they might be different and include GPS-related stuff (type "supl").
3. Copy stock gps.conf from Rojers and try using it on custom ROMs.
4. Download FasterFix and try choosing different NTP pools.
5. Download GPS Status & Toolbox, see what exactly happens when you run it, describe here. What satellites are you seeing (numbers), how much time after running it, in which condition, etc.
Click to expand...
Click to collapse
1 The AT&T roms didn't give me an adequate lock, until the JB updates were leaked & released.
2 I'm always using automatic APN's but they don't have any GPS info.
Haven't tried #3..
4 FasterFix didn't help.
5 GPS Status shows 4-7 satellites and only 2-3 locks with horrible accuracy. The thing is now i get perfect locks with any ROMs.. I could've disallowed Google Services to use GPS as I might've confused it with Google Search & Ads wanting my location..
Thanks for your help :good:
Is there a stable ICS out for T959v? Stable as in GPS and wifi calling for t mobile is functional.
knicks791 said:
Is there a stable ICS out for T959v? Stable as in GPS and wifi calling for t mobile is functional.
Click to expand...
Click to collapse
lol no.
I wouldn't consider WiFi calling a factor in a roms "stableness". Its more of a feature. Cm9 is stable and GPS does work
Yeah forget about wifi calling. I think cna 2.0 is great. Cm9 release 8 and well for as early as it was released beam is fairly stable.
Sent from my SGH-T959V using Tapatalk 2
ICS AOKP is stable.....
Stable as in normal human definition, yes. Stable as in Wifi calling, no.
Wifi hotspot?
Theraze said:
Stable as in normal human definition, yes. Stable as in Wifi calling, no.
Click to expand...
Click to collapse
How about stable as in wifi hotspot? I don't use it often, but when I do I need it to work well (business). Works fine on my Vibrant, but I also have SGS4G that I'd like to see if I can get better signals on cell (especially), gps and wifi. I had been sticking with GB ROMs since they seemed the best for GPS/wifi, but would like to move to ICS if possible.
The ICS hotspot has worked basically always worked fine unless you screw with services. My wife used AOKP when we were out of town a few weeks ago. I used Barnacle and Wifi tethering for root users while on JB.
Both ICS and JB worked fine for tethering.
Theraze said:
The ICS hotspot has worked basically always worked fine unless you screw with services. My wife used AOKP when we were out of town a few weeks ago. I used Barnacle and Wifi tethering for root users while on JB.
Both ICS and JB worked fine for tethering.
Click to expand...
Click to collapse
Good. Is there a "best" for GPS? Seems most JB have issues and several ICS as well from what I've read so far.
JB doesn't have GPS yet. That's its issue, but airfluip1 thinks he might have some ideas on how to fix it. Hopefully he'll get it working, or Erik will, or someone else maybe. But for now, skip JB if you need GPS.
ICS has 3 different options for GPS, and it's not always apparent which is better.
1) Assisted GPS. This requires having a build.prop file that tells your phone how to use GPS for this. Most of our ROMs want to do this, but end up in number 3 instead. There are directions on how to fix this if you aren't using Ultragen, or just use Ultragen which comes with this properly configured from the start. First connection to GPS may take 15-30 minutes, but it should be much faster after that.
2) Non-assisted GPS. This comes from flashing YAGF. It disables the assisted GPS and just uses the satellites fresh every time. This CAN be much faster, but won't work well in clouded/wooded/indoor areas.
3) Bad GPS. This is when 1 or 2 fail, generally number 1. The phone is told to use AGPS but it's disabled in the build.prop, or any of a wide variety of other issues. GPS will work... sometimes... but it's highly irregular.
Best option? Start with Ultragen (remember... 1.0.1, not 1.0, which had several major issues) and see if the AGPS is good for you. If you don't like it, flash YAGF and go to unassisted. Decide it's worse and hate it? Wipe the ROM (to get out the modified system files) and reflash Ultragen.
Or start modifying your own files, but be careful that your phone boots up. Don't use Microsoft Word or Notepad or Wordpad or any of those tools. Use a proper hex or *nix editor.
Theraze said:
JB doesn't have GPS yet. That's its issue, but airfluip1 thinks he might have some ideas on how to fix it. Hopefully he'll get it working, or Erik will, or someone else maybe. But for now, skip JB if you need GPS.
ICS has 3 different options for GPS, and it's not always apparent which is better.
1) Assisted GPS. This requires having a build.prop file that tells your phone how to use GPS for this. Most of our ROMs want to do this, but end up in number 3 instead. There are directions on how to fix this if you aren't using Ultragen, or just use Ultragen which comes with this properly configured from the start. First connection to GPS may take 15-30 minutes, but it should be much faster after that.
2) Non-assisted GPS. This comes from flashing YAGF. It disables the assisted GPS and just uses the satellites fresh every time. This CAN be much faster, but won't work well in clouded/wooded/indoor areas.
3) Bad GPS. This is when 1 or 2 fail, generally number 1. The phone is told to use AGPS but it's disabled in the build.prop, or any of a wide variety of other issues. GPS will work... sometimes... but it's highly irregular.
Best option? Start with Ultragen (remember... 1.0.1, not 1.0, which had several major issues) and see if the AGPS is good for you. If you don't like it, flash YAGF and go to unassisted. Decide it's worse and hate it? Wipe the ROM (to get out the modified system files) and reflash Ultragen.
Or start modifying your own files, but be careful that your phone boots up. Don't use Microsoft Word or Notepad or Wordpad or any of those tools. Use a proper hex or *nix editor.
Click to expand...
Click to collapse
Just a suggestion, but the Pimp My Rom application https://play.google.com/store/apps/...sMSwxLDYsImNvbS5hbmRyb2d1aWRlLnBpbXBteXJvbSJd under GPS Tweaks will download the proper GPS files for location, or alternatively, you can install the GPS Status and Toolbox App https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5lY2xpcHNpbS5ncHNzdGF0dXMyIl0 which you can set to download the newest AGPS File when you open it.
I am using AOKP ICS and have no issue with GPS. Was getting like 120 sec TTL for like 12 Satellites according to GPS Tools, which is not terribly life affecting for me.
Which... is irrelevant if your build.prop doesn't use those files. As I said. You can tell GPS Status to update every hour, but if the phone isn't set to use them, they're helping you as much as throwing the phone up 20 feet into the air (without twisting it). Slightly less, since they're using up storage and not getting your phone closer to the satellites.
That being said, the TopNTP app did have GPS modifications as one of its options. Not sure if it does the build.prop flag we need, but...
Wow, it seems the SGS4G may actually be worse than the Vibrant for GPS.
LoL
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
Theraze said:
Which... is irrelevant if your build.prop doesn't use those files. As I said. You can tell GPS Status to update every hour, but if the phone isn't set to use them, they're helping you as much as throwing the phone up 20 feet into the air (without twisting it). Slightly less, since they're using up storage and not getting your phone closer to the satellites.
That being said, the TopNTP app did have GPS modifications as one of its options. Not sure if it does the build.prop flag we need, but...
Click to expand...
Click to collapse
There is gps. It just no worky right! It will take a lil more then downloading a * "NIX" EDITOR and edit build.prop
Sent from my SGH-T959V using Tapatalk 2
hechoen said:
We'll call this one hidden in plain site.
I've been testing a new kernel for Beastmode lately and was trying to get GPS to work. I flashed 3.1 google specific build and still no lockie. So I did what cryptic mentions in the OP and READ the notes. Well that note that I quoted up above is the thing that needs to be done for this phone to make GPS work. After I added that line to the build.prop and rebooted I got a lock in about 10 seconds indoors to an accuracy of 6 meters. Not bad for this phone at all.
Most of are ICS ROMs use CM as a base. So after going through and looking at most of their props NONE of them have that line. I don't know how it's escaped notice as long as it has. I've only tested it on CM9 8-29 build with Beastmodes yet to be released kernel. I doubt that it matters though. Flash the zip, add that line, reboot and you should be good to go.
So thanks to cryptic for this fix and one of the most detailed OP's I've ever had the pleasure of reading. And too erikmm(aka Beastmode) for the incentive to actually look into this.
Click to expand...
Click to collapse
As I said...
Theraze said:
Best option? Start with Ultragen (remember... 1.0.1, not 1.0, which had several major issues) and see if the AGPS is good for you. If you don't like it, flash YAGF and go to unassisted. Decide it's worse and hate it? Wipe the ROM (to get out the modified system files) and reflash Ultragen.
Click to expand...
Click to collapse
Thanks ! Where can I download YAGF for a T959v ? Is Ultragen v1.8 also good or only 1.0.1 ?
Remember that you have to flash something that actually works on our phone, unless you're making your own franken-build.
Ultragen 1.01 is available in post 4 of the Ultragen thread. There is no Ultragen 1.8... at least, not here on XDA for our phone.
Regarding the GPS, it's the same YAGF2 from the Vibrant forums... it's just a generic-ish fix that may or may not placebo you.
Unfortunately, I don't understand the technical jargon regarding all the GPS options...maybe I'm better off not knowing.
However, I'm running CM9 with Proton kernel & LB6 modem and everything works (except, of course, for wi-fi calling).
No problems whatsoever with GPS. Battery drains a little fast but I have a zillion chargers laying around the house,
office, & car...no big deal.
I've been fighting with the cm11 d2lte builds since I updated to a nightly in the beginning of September; since then (I believe the 9/7 nightly was the last one that worked), I've had trouble with GPS losing locks, or getting locks at all. I tried several nightly updates in hopes this was a known and fixed problem, as I've seen many complaints about GPS in cm11, but none of the nightly or snapshot updates helped, and some made things worse.
I have tried everything I could find, including toggling between Maps and other map/GPS related apps, full ROM wipes and fresh installs, wipes to flash stock firmware and then come back to cm11 after getting a GPS lock in stock, 3rd party apps like GPS Status to update/wipe aGPS (assisted) data, etc. The state my phone is in now is:
- Did a full wipe of data and cache partitions
- Installed stock backup, got a GPS lock, and rebooted
- Wiped again and installed the most current cm11 snapshot for d2lte (11-20141008-SNAPSHOT-M11-d2lte)
- Using GPS Status and toggling between Maps and Waze to try and get GPS locks
I'm able to get a lock sometimes, but not often enough and not when I need one most: Maps recently turned a 1.5 hour trip into a 3.5 hour nightmare with a really bad route and no ability to reroute.
As an afterthought, I realized that when I'm in my car, I'm usually using the phone for 2 things:
- GPS/maps
- audio output from headphone jack to car aux input
While playing with GPS on the way home today, I unplugged my audio cable from the headphone jack ... and I suddenly got a GPS lock. Plugged the audio cable back in, and lost the lock. Pulled it again, and got a lock. WTF? I've been fighting with this for a month, and don't think I've seen a single mention of audio affecting GPS.
Can anyone else possibly verify this? And any suggestions on a fix?
Thanks!
I've read before that tightening the screws inside the back of the battery sometimes solves this issue
From my Wicked S3 on SOKP
Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.
ShapesBlue said:
I've read before that tightening the screws inside the back of the battery sometimes solves this issue
Click to expand...
Click to collapse
Not sure what you mean, but if you mean the 10 screws surrounding
the frame, I've tried tightening them. I don't know of any screws on or beneath the battery.
MrBrady said:
Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.
Click to expand...
Click to collapse
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?
deesto-xda said:
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?
Click to expand...
Click to collapse
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.
MrBrady said:
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.
Click to expand...
Click to collapse
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.
deesto-xda said:
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.
Click to expand...
Click to collapse
Most custom roms are based off other roms, aicp is one of the many. I switched directly to CM11 today because I was on another version of a cm based rom and the reboots were too much for me.
From my CM11 S3
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