I've been running the stock rooted ROM for some time with no issues.
Today, I decided to try the latest LeeDroid kernel. So, I restored a recent LeeDroid ROM and flashed the latest LeeDroid kernel. After that, no GPS--none whatsoever. No GPS icon on the top of the screen. No GPS readings from GPS Test and GPS Status apps.
I flashed a few different ROMs, same thing. No GPS.
After doing some research, I flashed the stock radio (with RIL) and bam, GPS is back.
I went through the LeeDroid process again, and I can confirm flashing the latest Kernel kills GPS somehow.
No big deal, since it's back, just and FYI.
Related
I'm wanting to know if flashing a new rom can automatically change my RIL's? I know radio does not change unless I purposely flash a new radio, but without using ROM names I'll try to describe my issue and the reason behind my question.
I was using a Sense 3.5 rom for a week with everything working just great. I decided to try a different kernel with that rom and after flashing the new kernel my gps stopped working. OK, reflash the original rom and things are back to working well.
THEN...I decide I want to try CM7 so I flash a CM rom and try it out for a couple days, decide that it's really not going to work for me and go back to original rom with original kernel.
NOW...gps is taking forever to lock, and google nav doesn't lock at all unless I open up a gps app like gps status or chartcross gps test. I flashed cryps AGPS patch for tmous users and it still has this same issue.
Any ideas, opinions, or other solutions are greatly appreciated. I use my navigation a lot and it's a key requirement for my phone so quick gps lock is extremely important for me.
kingston73 said:
I'm wanting to know if flashing a new rom can automatically change my RIL's? I know radio does not change unless I purposely flash a new radio, but without using ROM names I'll try to describe my issue and the reason behind my question.
I was using a Sense 3.5 rom for a week with everything working just great. I decided to try a different kernel with that rom and after flashing the new kernel my gps stopped working. OK, reflash the original rom and things are back to working well.
THEN...I decide I want to try CM7 so I flash a CM rom and try it out for a couple days, decide that it's really not going to work for me and go back to original rom with original kernel.
NOW...gps is taking forever to lock, and google nav doesn't lock at all unless I open up a gps app like gps status or chartcross gps test. I flashed cryps AGPS patch for tmous users and it still has this same issue.
Any ideas, opinions, or other solutions are greatly appreciated. I use my navigation a lot and it's a key requirement for my phone so quick gps lock is extremely important for me.
Click to expand...
Click to collapse
Mostly the rils are replaced by the rom IF the chef puts it in. But more inclined all do.
And yes the ril and radio is essential to have gps working quickly. So you can just match the radio to the ril.
If that doesn't work, compare the rils on an old nandroid and the new rom. I'm going to say that the rils will be different.
And also in my experience, flashing different kernels also affects the gps locks as well. For me bricked and faux kernels always borked my gps. So now I only go with the bundled kernel, because most times, the dev tested out the gps with the kernel before releasing it.
You can always flash the matching radio to the RIL you now have, that should sort you out
http://forum.xda-developers.com/showthread.php?t=1200403
Thanks for the answers and suggestions so far. So this is what I've done so far:
- reflashed first rom after doing a factory reset/wipe in ext4 recovery. It used to work well with my signal and my gps using the latest 10.56 TmoUS radio. After trying to get lock for 15 minutes I gave up
- read the RIL thread and flashed the recommended .169 ril for the 10.56 radio and still bad gps, no lock. What's weird is in both the above cases Ucenter gps app finds satellites but google nav and endomondo do not lock, ever. So I know my gps hardware is working but it's just not communicating with any apps.
- I'm going to now try using Superwipe and reinstalling the rom 1 more time, not sure if that will do anything at all but I'm out of ideas. Otherwise I may have to give up on this particular rom even though it used to work well.
And no, the rom does not recommend any particular radio.
Remember to try the rom (with matching ril) without flashing a kernel first.
Although I saved my problem already, I thought I'd post it anyway, in case somebody has the same troubles. There are many GPS-related threads, but they're more or less all about long fix-times.
When this happened I was running the ported stock-4.0.4 with matr1x-kernel & clockworkmod.
I'll describe how I fixed it (=long way) and a possible faster way.
Today I noticed my GPS wasn't working anymore, despite being on in settings. According to every app it was there and turned on, but they all couldn't find a single satelite. (Maps, Z-Device, GPS Test,...) Also the GPS-Icon in statusbar never showed up. After doing a full wipe and reflash of my rom twice, I was certain it's a HW-failure.
So the plan was: back to GB 2.3.6-stock, lock bootloader and send it in for service.
After flashing stockrom, I decided to give it another try first - it was working again, including the icon.
Flashed back to ICS and no problems ever since.
My theory:
At some point the GPS-chip got stuck between off and on, yet reporting to be fully functional to Android (and thus all Apps). Flashing a rom containing radio reset it and fixed this.
Long way:
(all stock-roms contain stock-recovery, so if you let it start booting, clockworkmod will be overwritten and you have to flash it again via fastboot!)
- flash stock GB (includes older radio and bootloader)
- flash stock 4.0.3 (to get latest version of radio and bootloader)
- flash your favourite custom-rom (they all come without radio and bootloader)
Fast way: (theoretical)
- reflash any radio suitable for your phone-model
Update:
I now know what triggered the bug, running a version of matr1x-kernel with cm9-swapfile on a non-cm9-rom. Or it's a general bug in the cm9-versions of matr1x v18.0 & 18.5.
But it should be noted that once the bug occurred, changing kernel was the first thing I tried. neither flashing an older matr1x-version without the swap nor another kernel (glados) helped. Only after I flashed a stockrom GPS came back to live.
I have been pondering this thought(s) for a couple days now and I need some input and/or answers haha.
If you flash new radio (1.08ts), 2.35 base rom, and the 2.35 wifi patch. Can you return back to a aosp rom and still have wifi working? I am just not for sure if that patch is permanent and if it breaks wifi on aosp and now your stuck on Sense.
Last thought. Say you go back to aosp rom, since after installing new radio and patch from previous 2.35 base testing you still experience data drops on aosp when screen is off; can you go back to an older radio that doesn't have data drops when screen turns off and having that 2.35 patch not interfere with the older radio?
I just like having my options open and don't want to screw everything up because I wanted to test out new base haha.
Thanks in advanced to whom that has positive input.
meXdroidMod Paralyzed Blue V 1.2
Just flashed the 11/04 CM10 and the 11/4 kernel last week. And the new 10/11 GAPPs. Love it. Battery life much better. Several issues resolved. Even the GPS lock on maps is much faster. However, when I try to use the navigation, it locks up and I no longer get the navigation icon in the task bar. It just says waiting for location. It does show the GPS navigation lock though. I did the 11/18 kernel update but no luck. I have reinstalled the rom and the kernel again. Also uninstalled and reinstalled maps with the navigation but still nothing. Anyone else having this problem? I've looked through the posts and not found anyone else with similiar post after this flash. If no suggestions, where is the link for the old kernels and GAPPs?
Currently version 4.1.2
Kernel version 2.6.35.7-I997UCLB3-CL977492-g9951ac1 (Also tried flashing back to g5674fa6 from 10/28 without success).
CyanogenMod Version 10-20121104
Thanks
So over the past few weeks I've been extremely flash happy. I've practically flashed every ROM in the dev section besides the JB roms that have broken radios. The latest ROM I flashed to was MIUI V4, it was super SUPER laggy and sluggish so I decided to go back to my all time favorite ROM of eaglesblood 4.0.4 AOSP. I flashed the rom, my favorite kernel (trinity g2x ics OC), new baseband fix and ICS Gapps package. Everything went fine at first boot except for the fact that I had no battery meter. It was gone. When I went into settings > battery it said my battery percentage was 999%. I figured it must have been something I did to the ROM zip as I modded battery icons in eaglesblood a few weeks prior may have had a corrupt file or something. So did a fresh download of the ROM. Flashed everything again, in the exact order and had the same problem. From there, I went back to my trusty nandroid backup of vanilla CM7 and my battery meter is working just fine. I cannot find a solution on the internet to what would make my battery icon, stats and overall detection completely disappear. Any ideas?