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
Related
I just went from RC3 to 7.0 hoping that this would clear up my GPS issue, but its still not working. I'm not getting any satellites in the gps status app. Everything worked okay with the stock ROM and I think it was working on RC1, but for all the other release candidates after that I haven't been able to get a gps lock.
The first time I flashed 7.0 I didn't wipe data/cache, but after the GPS still didn't work I tried wiping and installing 7.0 and the gps still is not working.
I've tried everything I've been able to find in other threads, but so far nothing I've tried has worked. Can anyone think of anything that I can try? Thanks.
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.
I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?
Elbob10s said:
I'd like to give the most recent nightly a try. I made a backup of my ROM via ROM Manager. I have Titanium Backup do I want to backup all user apps, all system data, or both?
What is the process now to properly upgrade from 7.0.3 to Nightly 100? Do I need to wipe data?
Click to expand...
Click to collapse
Going from 7.0.3 to the new nightlies is a big jump. They've changed from Gingerbread 2.3.3 to 2.3.4 as well as several kernel changes, and tons of other stuff. In this case it's probably best to do a full wipe before installing the nightly. Then restore your user apps in Titanium, however DON'T restore system data, as this will cause big problems. Any ROM settings that you customized in 7.0.3 (in Settings or CyanogenMod settings) you'll have to manually set again.
edit: One thing to note, if you're a heavy corporate Exchange email user, you'll want to hold off on the nightlies for now. There is an email issue that seems to be occurring on the Inspire only, that causes all email apps to crash when viewing messages on an Exchange server. The problem's been around since nightly 88 and hasn't been fixed yet. However, if this is no big deal to you, then the nightlies have otherwise been working well.
I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now
Elbob10s said:
I only use the Gmail app so that won't be an issue for me. I'm using the LorDmod 5.5 kernel I'll probably have to flash that again.
Thanks! I believe I know what I have to do now
Click to expand...
Click to collapse
If you flash a new nightly you'll definitely want to upgrade to the newer LorDModUE kernel as well. It is specifically designed for the newer nightlies.
edit: He's got a new smartass2 cpu governor in v4.0 so be sure to check it out.
+1 for LorDMod UE kernel on CM7 nightlies! Kicks butt!
@Elbob10s,
One more thing I forgot to mention. Once you've installed the new nightly, then it's usually OK to flash subsequent nightlies directly on top of the previous one without wiping. When you do this, you'll need to reinstall LorDMod again, since the kernel will get overwritten back to default.
I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.
Elbob10s said:
I'm on nightly 101 now, I tried 100 before it. I'm having a couple of minor issues with ADW Launcher and how it's showing the dock background now.
My personal contact icon is showing the grey box now only. On 7.0.3 I was experiencing a bug where the box would take over if I lost phone signal for any time until I rebooted, I was hoping that would have been fixed in then nightly lol.
But my biggest issue was after flashing LorDMod 5.6 last night the Home, Menu, Back, and Search buttons would no longer respond. I ended up doing another wipe and reflashing nightly 100. Is that the incorrect version for the nightlies?
I'm now on 101 in hopes of the contact icon working but no dice. Haven't tried to flash the kernel yet.
Click to expand...
Click to collapse
Yes that was a known issue on LM 5.x kernel on the newer nightlies. You want to move up to LM UE kernel, the link is in my sig. It was designed for the newer nightlies.
The UE with smartass2 is working great. I fixed the contact icon issue by adding my phone number in the phone settings.
Everything seems to be working great now.
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.
I have recently installed AOKP build 40, but the problem is I often receive no signal until rebooting into recovery and wiping the cache. This works but it is very frustrating to have to do this frequently. Does anyone know of a permanent fix to this problem?
I was having a similar problem. You can turn on airplane mode, leave it for about thirty seconds, and turn it off. It works better than nothing.
Now can you answer me a question as you do seem to still be running AOKP. Do you have trouble downloading stuff from the Google Playstore? It keeps timing out on me. Won't let me down anything until I force stop, disable, and re enable. The bigger issue is that it followed me back to a sense rom and I'm still having trouble downloading.
Sounds like the RIL startup bug which was fixed a week or so ago by intervigil in CM9 alpha 12. I think the fix is in the kernel and that it'll work on AOKP as well. Try to fastboot flash boot a recent CM9 boot.img, from alpha 12 or newer. Download from ville.giev.de or cm9 thread in development