Related
I have a problem with a long time to get fix on the GPS
Ever since the 2.3.3 i'm using custom roms and kernel, with 2.3.2 i only used stock as custom roms were randomly resetting and were draining the battery faster than stock.
I found that with stock 2.3.3 GRI40 the GPS fix work fine.
When i changed the kernel (one with voodoo sound and color) every time the fix takes about 3-5 minutes even when I just loose the signal in a tunnel.
Then came Modaco r13 built on GRI54 which is the best (feeling) rom for me its fast and battery time is great no random resets but the GPS fix again takes long.
What I did this time was not to move to stock kernel but move to back to the original 2.3.2/1 radio (used radio XXJK8 from GRH78).
This also fixed this problem!!
too bad as the new radio has better wifi reception in my opinion...
Anyone else also experience this?
I think maybe on the new radio they changed the access to the GPS in some way (driver?) that the custom kernels are not taking advantage of.... every fix with custom kernel is like the first fix instead of remembering all the sats
Ever since the 2.3.3 OTA update, my GPS takes forever to get a fix. It takes at least 5 minutes, and that's really frustating. My phone is not rooted and running the stock Android 2.3.3 OS.
I wonder if others are having a similar GPS issues like me.
Help me out here.
Thanks
@mastiff78 : I have a similar issue since 2.3.3. Sometimes the gps fix takes forever. If I reboot the phone, the next fix is instant.
Strange and frustrating
Add me to the list of people suffering from long GPS lock times since updating to 2.3.3.
I've got this problem too. I don't use it that often but after waiting for like 2 minutes, my friend pulls out her nexus one and gets gps lock in like 30 seconds.
I am using a voodoo kernel with 2.3.3 and get a gps fix with the GPS Status app in about 10 seconds. Google Earth is quick to get a fix as well, and that was after testing indoors beside a window. Are you updating the A-GPS info regularly?
I have noticed in the last few days, since moving to the voodoo kernel, that the compass is pretty much useless. To be honest, I cant say if it was the 2.3.3 update or the voodoo kernel which is the apparent cause. It worked perfectly before so its unlikely to be a hardware issue.
Hi all,
I do have the same problem with my nexus s (2.3.3 stock kernel):
- fix after cold start takes ages
- I frequently lose gps fix due to a "weak signal"
I have compared my old htc tattoo with the nexus s (using gps test):
- the old one sees the same satellites with almost identical signal to noise ratios as the nexus s but the nexus s simply uses less satelites for the fix! When the nexus s suddenly loses the fix, the tattoo does not although it sees the same satellites and has the same SNR values.
To me, this seems to be a software issue!
Any ideas on how to fix this?
Good to know that I'm not the only one with that problem... Did anyone report this issue to Google?
Well, I thought it would be helpful to report this issue in the "Google Mobile Forum":
-----------------------
As I am not allowed to post links, please go to the google support forum:
Help forum > Google Mobile > Android Devices > Other Google Products > Nexus S frequently loses gps fix
------------------------
Maybe you should describe and report your problem there as well...I really hope that we can draw a little more attention to this issue.
Thank you in advance!
tuck2 said:
Hi all,
I do have the same problem with my nexus s (2.3.3 stock kernel):
- fix after cold start takes ages
- I frequently lose gps fix due to a "weak signal"
I have compared my old htc tattoo with the nexus s (using gps test):
- the old one sees the same satellites with almost identical signal to noise ratios as the nexus s but the nexus s simply uses less satelites for the fix! When the nexus s suddenly loses the fix, the tattoo does not although it sees the same satellites and has the same SNR values.
To me, this seems to be a software issue!
Any ideas on how to fix this?
Click to expand...
Click to collapse
Try a different radio, XXJK8 or XXKB3. I’m using XXKB3 at the moment; I’ve been able to see up to 12 satellites and sometimes 11/11 connection. Fix time is faster (60 – 100 seg average) than XXKB1, but it’s still slower than it was before 2.3.3 which was about 30 sec
I am running CM7 with SuperAOSP kernel and I have no problem at all with the GPS. It gets the fix in less than a minute without any data connection (so, without A-GPS) and when I drive with copilot the accuracy is consistently less than 5m. With netarchy's kernel GPS worked nicely as well. I've never tried it with 2.3.3 stock or other radios...
Anyone noticing random crashes with the g2 cm7? Atleast once a week when I take it out of my pocket it doesn't power on and requires a battery pull to turn it on. (No lights, nothing)
Battery voltage issue?
Different people have been having different issues. What nightly/RC are you on? did you do a full data/cache/dalvik wipe before flashing the ROM? did you try fixing permissions?
Yup, I know there are some issues but it seems strange that the whole phone goes into a stale state which requires a battery pull. I believe its happened once or twice with cm6 as well.
I have done all the wipes and fixes etc. I am right now on nightly #15, I previously was on nightly #7 for a long time so maybe it was just that release. Thanks for your reply.
Haven't had one random reboot. Still using nightly 6. My mytouch4g has not had this problem either.
From my permarooted 1209mhz G2 with CM7 nightly 6
Are you overclocked?
Sent from my %s running Cyanogenmod.
Only to 1Ghz.
Today it died while charging, dead and needed a battery pull. Any ideas?
You're not the only one with this issue (myself included), and the cause is not yet known. And it seems there may be a couple different variations of this issue with the same symptom (of the phone powering off while asleep and needing a battery pull to power back on). May be related to overclock, GPS, screen-off profiles, full moon, or who knows what. See this thread for some various thoughts on the problem.
http://forum.xda-developers.com/showthread.php?t=908095
I personally think its a kernel issue, or that the kernel is at least one of the factors. I flashed pershoot's kernel and the problem seems to be solved, so far (keeping my fingers crossed). Having the GPS on while you turn of the screen also seems to be a common trigger for many who experience this problem.
Hi there,
Thank you so much for your reply! I couldn't seem to find any information on the forum.
I just wrote a post because I had the same thing happen to me. Phone just went dead for ni reason and I had to pull out the battery. But my phone isn't rooted. So it might not be because of CM7.
Tried to call Bell, but the wait time was too long. So will try to call them when I get home.
Sent from my HTC Vision using XDA Premium App
There are at least two other threads about this on XDA and quite a few others on the net.
Google HTC phone freeze random crash reboot battery pull or some combo.
No solutions and it happens on stock phones as well as rooted.
Did you search?
Having the same problem recently on my unlocked Desire Z from Bell, using on the Rogers network. It started yesterday and all of a sudden it turns off, and the only way to turn it on is removing the battery and putting it back in. This never was an issue for months. The only thing I updated from that affects the hardware is the new Google Maps, so I think GPS may be the case. But I really need GPS on my phone...
Yesterday I did an experiment with GPS. For me GPS is the case that makes my phone to freeze. With new Google maps it freezes even faster, more often.
Sent from my HTC Vision using XDA App
I've been using HyperDroid rom for a long time and been having issues with my navigation software for a while and I'm not sure what the exact problem is.
I'm using iGO My Way and sometimes the GPS will work fine for a while and then a lot of times it loses signal after about 4 minutes and won't lock back on until I reboot the phone and restart the program.
Then at other times the phone gets hot and will just freeze.
I also noticed after these things happen it won't help turning the GPS on/off, it will keep draining the battery even if I turn it off. I always have to reboot to get everything back to normal.
So I don't know if the GPS module is bad, or if it's not a good idea to use iGO.
I haven't tried using other navigation software since I need an offline one with maps of Israel. I don't have a data plan.
I did use SportyPal many times in the past for cycling with GPS and it never froze.
Try to use Sygic for a week...with this one I doesn't had any of your issues since android was given to our leo!
Hey thanks! I gave Sygic a try and the GPS actually connects much faster and so far I didn't lose signal in the middle. Also the phone doesn't get as hot as with iGO. It only froze once, but I'll keep testing it. It's much smoother and faster than iGO though.
Well, sadly, I lose signal with Sygic also...
I don't know what the problem is :/
Sygic
i have been using Sygic from quite a while now. It does not works well with few of the ROMS.
Currently i am using American Android 2.3.7 and it works like a charm for me with it.
Which ROM are you using ?
HyperDroid 5.8.0 but seems like no one else is complaining about GPS issues.
Could be the radio version (2.15.50.14) or maybe the GPS module on my phone is defected...
chance your rom
You can change your rom bro.I think you have to
Because radio is not problem 2.15....... is very good.I am using same radio,but different rom.I havent problem with igo or sygic
Yeah but I like HyperDroid. It's fast and stable!
I'm waiting for the ICS roms to get better... then I'll probably switch.
Hello
Sorry for bumping this but I have exactly the same problem. This has nothing to do with Sygic. The problem can arise with any application that uses the GPS and fails to shut it off properly (at least that's what I understand). From the moment that this happens, the GPS doesn't work anymore, heats up the phone and drains the battery fast. The only way to get it back working is to reboot the phone. Turning the GPS off and on, doesn't change anything.
I had this problem since 2.3.7. I had found a kernel update that had fixed the problem in that version (dorimanx's kernel but I can't remember the version) but since I upgraded to ICS and now JB the problem came back. With JB it works much better but it is there. With ICS it was a nightmare. I have tried many (over 10) different ROMs and each and every one of them had the problem. This is something that has been around for ages and nobody seems to have found the real cause or a remedy. I'd love to cure it since I love my HD2 and it's the only thing that is marring its performance. Have you had any success with it?
Regards
George
i to have had this problem and i find it to be a rom problem will work ok for a hour or two then have to reboot the phone the only rom i seem to get it to work ok are the old gb light roms its about 120 deoxd
Had the same problems with most of the sensation or other sense Roms. The problem is solved since i use 4.x.x Roms as dataonsd installations. Now googlemaps works like a charm. Love the traffic info
Sent from my NexusHD2 using xda app-developers app
I'm experiencing issues when I use the navigation. After a while the message "gps signal lost" comes up and my phone is not able to get a singnal again. Until, yes until I switch GPS off and back on. The fix comes within seconds and I can use the navigation for another...5 to 10min until I need to switch if off and on again...
Does anyone have the same issue and/or a fix for that?
Are you on Stock or Custom ROM?
Stock Rom, stock kernel. I only rooted it
Sent from my Nexus 4 using Tapatalk 2
Not too sure. I had an issue on CM10.1 with GPS.
Have you tried GPS Status and Toolbox from the market, you can reset your GPS.
Also Faster Fix, also from the market allows you to specify your region.
Let me know if any of this has helped.
Sent from my Nexus 4 using Tapatalk 2
The problem is not the fix. It just comes up with GPS signal lost. As soon as I just switch gps off and back on, the fix comes almost immediately and I can use it for another 5 or 10min. I'm not sure if this might be a temperature issue. I mean the phone feels warm but not hot.
Sent from my Nexus 4 using Tapatalk 2
I have the same exact problem on mine! I'm stock everything, not even rooted. Both times I've used my gps to get anywhere this happened. The first time I was dropping someone off at the airport and was driving for about 3 hours total and the second time was yesterday when I had a 4.5 hour drive.
The first time I thought maybe it was cloudy or there was some kind of interference, although when I would exit navigation and go back in it was fine for another 10 minutes. After yesterday, I'm beginning to think it is completely unreliable. I won't be able to use it to drive anywhere because it is so dangerous to have to fiddle around with your phone every ten minutes to get the navigation to work again.
I am glad I found this in a search so I know there is at least one other person out there with the same problem. Do you think we just got bad phones and need to get them replaced?
I think I've solved the problem for my phone at least (or it's just a coincidence). Today before I drove home 4.5 hours, I installed cm10.1 on my phone and the whole time I was driving it only lost signal once. Although when it lost signal I gave it 30 minutes to find itself and it was following me but couldn't lock on and was only accurate to like 50 meters or something. As soon as I reset the navigation though it was pin point accurate for the rest of the trip.
I installed cm10.1 after reading in another thread about someone whose nexus 4 took an outrageous amount of time to acquire a gps lock. He said it was fixed by wiping his data.
So of you're still having trouble with your phone you could try backing up your apps and doing a factory reset or flashing cm10.1.
I haven't installed CM10.1 yet but thanks for the suggestion.
I installed francos kernel r15 and had on single signal lost yesterday.
I think it's heat related. I repositioned the phone after the first time it lost it and it was fine for the rest of the journey (45min)
I think the OS disables the GPS when it gets too hot. But instead of switching it off, it just doesn't work until you reset it. Werid.
I'm gonna try CM soon to see if it makes a difference to me too.
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
I haven't installed CM10.1 yet but thanks for the suggestion.
I installed francos kernel r15 and had on single signal lost yesterday.
I think it's heat related. I repositioned the phone after the first time it lost it and it was fine for the rest of the journey (45min)
I think the OS disables the GPS when it gets too hot. But instead of switching it off, it just doesn't work until you reset it. Werid.
I'm gonna try CM soon to see if it makes a difference to me too.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I have the exact same problem with my Nexus 4. Galaxy Nexus worked with no problem. Nexus 4, gps lock is achieved very quickly but then lost after 10 to 15 minutes of driving. After trying factory reset and manually reinsitalling the OS, I called Nexus support and exchanged phones. I never thought it was a hardware problem, but thats the only thing Nexus support could do for me. With the new phone, I reproduced the problem with both OS versions 4.2 and 4.2.1.
Now, the exciting stuff. For a little while I decided to revert back to my Galaxy Nexus (by taking my SIM out of the Nexus 4 and putting into the Galaxy Nexus). After doing so, I also did a manual reinstall of 4.2.1 (this was all before getting my replacement phone). To test the Nexus 4 with the reinstall, I used my Galaxy Nexus's wifi hotspot and connected my Nexus 4 to it and used the Nexus 4's navigation WITHOUT ANY PROBLEM! As soon as I put the sim back into it, the problem started up again.
My hunch is that Google location services (that use cell towers to triangulate) are somehow interfering with location services in general in software, and by putting the sim card back into the phone, I enabled Google location services to interfere with the GPS software.
No resolution to the problem, but just some interesting correlations!
I am having the same issue. Nexus 4 acquires GPS signal immediately. Using GPS Status app I clocked it at under 4 seconds. However, within 3-10 minutes of navigating, GPS loses signal and NEVER re-acquires it. I tried this with Google Maps, Mapquest and Copilot Live. Restarting the navigation application re-locks the GPS almost instantly.
Ultimately, the navigation function is not usable if you have to fiddle with the phone every couple minutes while driving. Google support was of no help. I returned the phone, but now regretting it, since it was perfect in almost every other way.
There are reports floating around that 4.2.2 software fixes the GPS issue. Can anybody confirm this?
P.S.
I am on T-mobile in Washington, DC area.
Re: [a APP] LMT Launcher v1.91 for GNex/Nexus4/Nexus7/GSIII/HD2 and more... (ROOT)
Custom ROM and kernel fixed it for me
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
Custom ROM and kernel fixed it for me
Click to expand...
Click to collapse
Can you elaborate as to which custom ROM and which kernel? Thanks.
max_gorkiy said:
Can you elaborate as to which custom ROM and which kernel? Thanks.
Click to expand...
Click to collapse
For me it is xylon room with Franco kernel
Sent from my Nexus 4 using Tapatalk 2
max_gorkiy said:
I am having the same issue. Nexus 4 acquires GPS signal immediately. Using GPS Status app I clocked it at under 4 seconds. However, within 3-10 minutes of navigating, GPS loses signal and NEVER re-acquires it. I tried this with Google Maps, Mapquest and Copilot Live. Restarting the navigation application re-locks the GPS almost instantly.
Ultimately, the navigation function is not usable if you have to fiddle with the phone every couple minutes while driving. Google support was of no help. I returned the phone, but now regretting it, since it was perfect in almost every other way.
There are reports floating around that 4.2.2 software fixes the GPS issue. Can anybody confirm this?
P.S.
I am on T-mobile in Washington, DC area.
Click to expand...
Click to collapse
I'm having trouble with it too, 4.2.2. definitely does not fix the GPS issue that I have too!
Did you ever got a solution for this?
I think it was a heat issue.
A custom kernel worked for me
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
I think it was a heat issue.
A custom kernel worked for me
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hey edgeball,
I was wondering if using the franco kernel is still working for you, and if you have tried upgrading to 4.3.
I just bought a nexus 4 and i am very disappointed to have these problems with the gps as i use the gps all the time.
I have the same problem where the gps signal is lost but the other problem that i am having (after a few minutes of navigating is the signal becomes weak I get this halo around the arrowhead that indicates my location. This halo i believe is showing uncertainty of location, meaning I could be anywhere inside the circle. Then the circle gets bigger, like 50 feet diameter. Then my location starts jumping around. I will be on one side of the intersection, then the other, then back again. And every time this happens the route is recalculated.
Then ultimately I loose the gps signal and it keeps searching until i either reboot of turn the gps off and then on.
This morning I installed franco kernel and I didn't loose the gps signal during my 45 minute commute but I did have this second problem I described there the location becomes inaccurate I my arrowhead starts jumping around the intersection.
I was just wondering if you have experienced the same problem.
thanks.
oh btw I am trying the franco kernel on slimbean 7 (4.2.2)
whobalagosh said:
I have the exact same problem with my Nexus 4. Galaxy Nexus worked with no problem. Nexus 4, gps lock is achieved very quickly but then lost after 10 to 15 minutes of driving. After trying factory reset and manually reinsitalling the OS, I called Nexus support and exchanged phones. I never thought it was a hardware problem, but thats the only thing Nexus support could do for me. With the new phone, I reproduced the problem with both OS versions 4.2 and 4.2.1.
Now, the exciting stuff. For a little while I decided to revert back to my Galaxy Nexus (by taking my SIM out of the Nexus 4 and putting into the Galaxy Nexus). After doing so, I also did a manual reinstall of 4.2.1 (this was all before getting my replacement phone). To test the Nexus 4 with the reinstall, I used my Galaxy Nexus's wifi hotspot and connected my Nexus 4 to it and used the Nexus 4's navigation WITHOUT ANY PROBLEM! As soon as I put the sim back into it, the problem started up again.
My hunch is that Google location services (that use cell towers to triangulate) are somehow interfering with location services in general in software, and by putting the sim card back into the phone, I enabled Google location services to interfere with the GPS software.
No resolution to the problem, but just some interesting correlations!
Click to expand...
Click to collapse
Given this, would it be possible to fix this issue by only turning on "GPS satellites" and not "Wi-Fi & mobile network location"? By doing so, the phone isn't looking for cell towers and WiFi. I have no idea on this topic but if a SIM card isn't inserted into the phone, would that not mean that the phone is not using cell towers for location?
Hi,
I have two Nexus 8gb, one rooted (mine) and the other one unrooted (my wife's), both run stock JB 4.2.1. The thing is that BT sometimes works fine and suddenly it doesn't work anymore till I reboot the device... it happens in both device, so rooting is not the trouble. I have restored the rooted one with factory settings and the same... BT works fine but some day it crashes, after rebooting it works again.
Some of you have the same problem? Any solution?
Thanks in advance.
makilol said:
Hi,
I have two Nexus 8gb, one rooted (mine) and the other one unrooted (my wife's), both run stock JB 4.2.1. The thing is that BT sometimes works fine and suddenly it doesn't work anymore till I reboot the device... it happens in both device, so rooting is not the trouble. I have restored the rooted one with factory settings and the same... BT works fine but some day it crashes, after rebooting it works again.
Some of you have the same problem? Any solution?
Thanks in advance.
Click to expand...
Click to collapse
What you're describing is an issue I've had with Android over multiple phones and multiple versions of Android. I don't have a solution for you but I will tell you that I'm pretty sure there will be some work done to the BT stack in the next release of Android as there are multiple problems with the new Broadcom stack they are using in v4.21. New sound quality issues and connection issues primarily. So hang tight.
makilol said:
Hi,
I have two Nexus 8gb, one rooted (mine) and the other one unrooted (my wife's), both run stock JB 4.2.1. The thing is that BT sometimes works fine and suddenly it doesn't work anymore till I reboot the device... it happens in both device, so rooting is not the trouble. I have restored the rooted one with factory settings and the same... BT works fine but some day it crashes, after rebooting it works again.
Some of you have the same problem? Any solution?
Thanks in advance.
Click to expand...
Click to collapse
I use Bluetooth all day. I turned it on this morning at 08:00 AM. It has been on almost 5 hours. The phone is streaming Sirius XM satalite the entire time. No issue. Same thing every day. I have had 0 problems since I bought the phone.
I think your BT device is the problem.
I don't think so, because the BT device is off when I turned on the BT in the Nexus 4... I have tried several ways, 1st turn on the BT device, other times the Nexus 1st... but there isn't a clear patter, it doesn't work randomly. The BT in the phone doesn't activate, it blocked, only a reboot makes it works... extrange.