Database Users

So... about this GPS problem...

I have been diligently searching for a thread to pop up along the lines of "GPS FIX" But I can't find any. I just wanna know if there is a definitive fix in the nightlies or not?

Not really. Some people are replacing their gps framework with one from an early nightly with generally working GPS. Other than that it seems different radios etc. Are having varying results.
Sent from my HTC Vision using XDA App

convolution said:
I have been diligently searching for a thread to pop up along the lines of "GPS FIX" But I can't find any. I just wanna know if there is a definitive fix in the nightlies or not?
Click to expand...
Click to collapse
Bad news here, I am on cm7 nightly 17, still without GPS( It worked only once).
The once worked method, which is replacing gps.vision.so from nightly #4 no longer works.

churchmice said:
Bad news here, I am on cm7 nightly 17, still without GPS( It worked only once).
The once worked method, which is replacing gps.vision.so from nightly #4 no longer works.
Click to expand...
Click to collapse
Yea this is how its been for several nightlies. GPS works on first reboot, but it doesn't work if you turn it off then back on again. I'm on #17 too.

churchmice said:
Bad news here, I am on cm7 nightly 17, still without GPS( It worked only once).
The once worked method, which is replacing gps.vision.so from nightly #4 no longer works.
Click to expand...
Click to collapse
This is the issue I had. I didnt mind replacing the gps.vision.so from Nightly #4 into the new Nightly's but now thats not even working on Nightly #17. It seems the GPS issue is getting progressively worse.

I'm on RC2 and was able to get my GPS working by flashing the latest AUS radio image (12.28h.60.140f_26.06.02.27). Before flashing it I was still on the old version from tmobile (12.21.60.09b_26.02.01.15). After flashing the AUS radio image my GPS started working but I was having problems with the reliability and speed of my data connection, even standing less than 800' from a T-mobile tower I was getting 1.5Mb/s download at best and it would only come in bursts. At that point I flashed the T-mobile image (12.28b.60.140e_26.03.02.26) from the OTA update and my data problems were fixed, started getting a steady connection and 4Mb/s+ download standing in the exact same spot, AND my GPS was still working. I've rebooted my phone several times since then I used the GPS for about 2 hours strait yesterday so it seems to be persistent and stable.

I have found that if I leave my GPS ON before I flash a new nightly or ROM, that it works fine. I have only ran into the GPS issue a few times but that was because I had it off before I flashed a new build. Never messed switching RADIOs or anything.
Here is what I have done to fix issues:
-If I flashed a new CM7 Gingerbread ROM without GPS ON prior to the flash, I usually go back to CM6 and turn GPS ON and then reflash the CM7 ROM and it works.
-Yesterday had a strange issue though, I went to Flash a new CM7 nightly and sure enough I forgot to leave GPS ON. So I went back to CM6 and tried to turn GPS on and it didn't work. So I then Flashed one of the MIUI ROMs and that still didn't work. So then I tried Flashing the newest Nightly from CM again and it worked very wierd.
That has been my experience with this GPS issue. Some how I have managed to fix it myself without too much trouble. Hopefully this helps people with these issues.

hogg2500 said:
I have found that if I leave my GPS ON before I flash a new nightly or ROM, that it works fine. I have only ran into the GPS issue a few times but that was because I had it off before I flashed a new build. Never messed switching RADIOs or anything.
Here is what I have done to fix issues:
-If I flashed a new CM7 Gingerbread ROM without GPS ON prior to the flash, I usually go back to CM6 and turn GPS ON and then reflash the CM7 ROM and it works.
-Yesterday had a strange issue though, I went to Flash a new CM7 nightly and sure enough I forgot to leave GPS ON. So I went back to CM6 and tried to turn GPS on and it didn't work. So I then Flashed one of the MIUI ROMs and that still didn't work. So then I tried Flashing the newest Nightly from CM again and it worked very wierd.
That has been my experience with this GPS issue. Some how I have managed to fix it myself without too much trouble. Hopefully this helps people with these issues.
Click to expand...
Click to collapse
This worked for me also. I backed up RC2 with gps on, flashed MIUI, and then restored and blam it worked! thanks, I needed this so badly.

I had this problem for a while as well. Flashing CM7 #3 did the trick for me. I downloaded a copy of xboarder56's stock GB test ROM today and I have to say it works flawlessly! Smooth and fast and with working GPS.
Sent from my HTC Vision using XDA App

So from the input I gather that nightlies have not yet fixed the problem. Since I don't need the GPS until the summer I guess I can wait a month or two before searching again...

Gps works fine for me.
Sent from my G2 running Cyanogenmod 7.

Fixed the GPS issue on CM7 by upgrading the radio:
Vision_RADIO_12.28e.60.140f_26.04.02.17. It works just fine in the US.
http://www.megaupload.com/?d=OKYRIPQW
To flash radio you must have radio s-off using gfree.
http://forum.xda-developers.com/showthread.php?t=855764
You need to downgrade to the stock kernel or CM 6.1.0 for gfree to work.

I'm not sure what the problem is either, but I decided to leave the GPS/Navigation running over one night. When I woke up, the GPS fixed itself. I haven't had a problem since then.

use these basic steps to try and fix the gps:
http://forum.xda-developers.com/showthread.php?t=983742&highlight=gps+fix

funkeee said:
Fixed the GPS issue on CM7 by upgrading the radio:
Vision_RADIO_12.28e.60.140f_26.04.02.17. It works just fine in the US.
http://www.megaupload.com/?d=OKYRIPQW
To flash radio you must have radio s-off using gfree.
http://forum.xda-developers.com/showthread.php?t=855764
You need to downgrade to the stock kernel or CM 6.1.0 for gfree to work.
Click to expand...
Click to collapse
But does it work when you turn GPS on/off/on after rebooting? My GPS works fine after flashing a new radio till I turn it off and back on again.

mesome383 said:
I'm on RC2 and was able to get my GPS working by flashing the latest AUS radio image (12.28h.60.140f_26.06.02.27). Before flashing it I was still on the old version from tmobile (12.21.60.09b_26.02.01.15). After flashing the AUS radio image my GPS started working but I was having problems with the reliability and speed of my data connection, even standing less than 800' from a T-mobile tower I was getting 1.5Mb/s download at best and it would only come in bursts. At that point I flashed the T-mobile image (12.28b.60.140e_26.03.02.26) from the OTA update and my data problems were fixed, started getting a steady connection and 4Mb/s+ download standing in the exact same spot, AND my GPS was still working. I've rebooted my phone several times since then I used the GPS for about 2 hours strait yesterday so it seems to be persistent and stable.
Click to expand...
Click to collapse
Can you please provide a link to download these two images?

martonikaj said:
But does it work when you turn GPS on/off/on after rebooting? My GPS works fine after flashing a new radio till I turn it off and back on again.
Click to expand...
Click to collapse
Locks on within 5 seconds after reboot and turning gps on and off.
Edit: I got it to fail after flipping it on and off a bunch of times. Sigh.
Sent from my HTC Vision using XDA App

USB not working???

I was wondering if anyone else was haivng an issue with USB. I can connect and charge my nook fine, but when I connect it to PC, it doesn't recognize, and when it does, it only shows up for a split second and vanaishes. Anyone else have similar issues?

I have the same issue. CM7 n64, dalingrin4/11 kernel. Won't connect via USB or show the USB Debugging dialog when I plug it in. Wondering if it's an issue w/the nightlies. Had any luck?

Yep I just found this on N63 and N64. I flashed back to stable 702. I tried both Kernels also so it is a ROM problem.

wpbear said:
Yep I just found this on N63 and N64. I flashed back to stable 702. I tried both Kernels also so it is a ROM problem.
Click to expand...
Click to collapse
Flashing back to 7.0.2 worked for me too.

Works great on 7.0.3 stable.

wpbear said:
Yep I just found this on N63 and N64. I flashed back to stable 702. I tried both Kernels also so it is a ROM problem.
Click to expand...
Click to collapse
It is in fact a rom issue. The latest nightlies are version 2.3.4 and progress is being made on the sleep issue, however at the moment the USB connectivity is down. If you flash back to a stable, you're going back to 2.3.3 and regain use of the usb connect. Just be carefull flashing back to the stables from the nightlies, because people have been getting a lot of FC with apps.

hockeyfamily737 said:
It is in fact a rom issue. The latest nightlies are version 2.3.4 and progress is being made on the sleep issue, however at the moment the USB connectivity is down. If you flash back to a stable, you're going back to 2.3.3 and regain use of the usb connect. Just be carefull flashing back to the stables from the nightlies, because people have been getting a lot of FC with apps.
Click to expand...
Click to collapse
Yup people should really read before posting this crap.. READ BEFORE YOU FLASH

No sound on calls

A friend of mine has a brand new nexus4 but when phone calls are made there is no sound. It has 4.2.2 with .48 radio and new bootloader. I tried a couple things: rooted it and flashed the bootloader and radio again with stock rom. Then install cm 10.1 with the new and old radios with the same results.
Any suggestions?

farrock02 said:
A friend of mine has a brand new nexus4 but when phone calls are made there is no sound. It has 4.2.2 with .48 radio and new bootloader. I tried a couple things: rooted it and flashed the bootloader and radio again with stock rom. Then install cm 10.1 with the new and old radios with the same results.
Any suggestions?
Click to expand...
Click to collapse
Is their no sound at all or is the volume just really low, almost to the point where you cant hear anything? If so, I had this same problem and all i did was restart my phone and it seemed to fix itself.

Android802 said:
Is their no sound at all or is the volume just really low, almost to the point where you cant hear anything? If so, I had this same problem and all i did was restart my phone and it seemed to fix itself.
Click to expand...
Click to collapse
Nah man. Its no sound at all either way. I can't hear him and he can't hear me.
Sent from my Nexus 4 using xda app-developers app

farrock02 said:
A friend of mine has a brand new nexus4 but when phone calls are made there is no sound. It has 4.2.2 with .48 radio and new bootloader. I tried a couple things: rooted it and flashed the bootloader and radio again with stock rom. Then install cm 10.1 with the new and old radios with the same results.
Any suggestions?
Click to expand...
Click to collapse
I had the same issue after the latest PIE rom update. Flashing the radio solved my problem, try this radio: http://forum.xda-developers.com/showthread.php?t=2087227

Real quick: did your friend test the phone for sound at the store before paying for it? Or did the no-sound issue kick in only after a little tinkering?

When waking up device, gets black screen, hangs for few secs, then reboots

When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?

its because of the kernal, mine does this aswell..

kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!

I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.

beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.

verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.

I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying

There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading

beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!

Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.

It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.

Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.

grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.

i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..

[Q] Problems with WIFI & BT when using custom ROMs

Hi guys.
I bought my Nexus 4 (after selling me old Galaxy S2) a few hours ago and I'm running into some issues.
Whenever I'm on a ROM that isn't Stock, my wifi or wifi + BT aren't working. The WiFi status is always 'Turning on wifi...' and never changes, and occasionally its the same for Bluetooth.
I've tried installing CM11, Carbon and AOKP, changing kernels, even flashing the stock radio to see if anything changes, but it all stays the same.
Another thing I've noticed (I don't know if it has anything to do with the WiFi, but it could be) is that on AOKP and on the Carbon, I can't click the top right button in the notification bar (the one that shows you all the toggles).
The thing is that whenever I flash back to Stock 4.4, everything is ok, and both the WiFi and BT are working as planned.
I'm actually clueless after trying anything I could think of. Does any of you have any idea what's going on?
Thanks in advance.

Ardethian said:
Hi guys.
I bought my Nexus 4 (after selling me old Galaxy S2) a few hours ago and I'm running into some issues.
Whenever I'm on a ROM that isn't Stock, my wifi or wifi + BT aren't working. The WiFi status is always 'Turning on wifi...' and never changes, and occasionally its the same for Bluetooth.
I've tried installing CM11, Carbon and AOKP, changing kernels, even flashing the stock radio to see if anything changes, but it all stays the same.
Another thing I've noticed (I don't know if it has anything to do with the WiFi, but it could be) is that on AOKP and on the Carbon, I can't click the top right button in the notification bar (the one that shows you all the toggles).
The thing is that whenever I flash back to Stock 4.4, everything is ok, and both the WiFi and BT are working as planned.
I'm actually clueless after trying anything I could think of. Does any of you have any idea what's going on?
Thanks in advance.
Click to expand...
Click to collapse
Hello, you have to flash older radio to enable wifi. Try version 84. Just flash the zip from CWM.
http://forum.xda-developers.com/showthread.php?t=2087227

toycz said:
Hello, you have to flash older radio to enable wifi. Try version 84. Just flash the zip from CWM.
http://forum.xda-developers.com/showthread.php?t=2087227
Click to expand...
Click to collapse
Hi, thanks for the reply.
I noticed that a lot of my sensors are dead as well when not using a stock rom.
I've had nothing but Android devices for the past 4 years, but in this case, I don't know whether the radio solution can solve the problem, since it looks more like a Kernel issue, or am I wrong?
Isn't the radio supposed to affect only wifi and BT? What about the other sensors?
Will try that soon though, phone has 2% battery.

Ardethian said:
Hi, thanks for the reply.
I noticed that a lot of my sensors are dead as well when not using a stock rom.
I've had nothing but Android devices for the past 4 years, but in this case, I don't know whether the radio solution can solve the problem, since it looks more like a Kernel issue, or am I wrong?
Isn't the radio supposed to affect only wifi and BT? What about the other sensors?
Will try that soon though, phone has 2% battery.
Click to expand...
Click to collapse
I'm having a similar issue. On nexus 4 phone with current stock ROM running 4.4.2, I tried Cyanogenmod 10.1.3 but wifi was always in trying to connect mode, never managed to turn it on/off. The same behavior is on miui ROM but on stock everything works fine!

tushargok said:
I'm having a similar issue. On nexus 4 phone with current stock ROM running 4.4.2, I tried Cyanogenmod 10.1.3 but wifi was always in trying to connect mode, never managed to turn it on/off. The same behavior is on miui ROM but on stock everything works fine!
Click to expand...
Click to collapse
Are you running the .98 radio with 4.4.2?

4.4.2 WIFI and Bluetooth connection issues
Ardethian said:
Hi guys.
I bought my Nexus 4 (after selling me old Galaxy S2) a few hours ago and I'm running into some issues.
Whenever I'm on a ROM that isn't Stock, my wifi or wifi + BT aren't working. The WiFi status is always 'Turning on wifi...' and never changes, and occasionally its the same for Bluetooth.
I've tried installing CM11, Carbon and AOKP, changing kernels, even flashing the stock radio to see if anything changes, but it all stays the same.
Another thing I've noticed (I don't know if it has anything to do with the WiFi, but it could be) is that on AOKP and on the Carbon, I can't click the top right button in the notification bar (the one that shows you all the toggles).
The thing is that whenever I flash back to Stock 4.4, everything is ok, and both the WiFi and BT are working as planned.
I'm actually clueless after trying anything I could think of. Does any of you have any idea what's going on?
Thanks in advance.
Click to expand...
Click to collapse
If the custom roms you are using are based on 4.4.2 it may be a problem with the newer kernel. This article recommends flashing the 4.4 kernel as a possible fix.
http://www.androidpolice.com/2013/1...-still-suffer-from-assorted-bluetooth-issues/