Hi,
every time I use GPS Navigation, it crashes my phone. It does not do this during navigation, but afterwards, about 2-10 minutes after terminating the GPS application and the GPS sensor.
Usually the phone is quite warm then. I cannot shut down the phone with power + sound up. I can only pull the battery.
This happened on stock 10B, 10C and numerous CM nightlies.
It happened with Google Maps Navigation and Navigon.
Anyone else having the same issues? Would you think it could be the April Baseband or rather the hardware itself. I tend to say it should not be the ROM.
Thanks for any help!
Solution
Just in case anyone has the same issues: updating to the May Baseband solved my issues.
I'm using CM7 on my Nexus One. The issue happened twice; right now the GPS is working fine but I'd like to find what can be done to diagnose this, or if there's anyone out there who already knows a fix...
Here's what it looks like:
I turn on the GPS, open GNavigation (or Waze, or Maps). GPS gets a fix but when I start driving, it doesn't update my location. After a while, it loses the fix, the reacquires it, still doesn't update it, loses fix again, and this keeps happening as 5-minute long loops.
Here's how it looks like in the GPS Status app:
It's as if GPS gets a fix, then hangs (my coordinate are not updated in GPS Status app) without giving any errors, then turns itself off and on, gets a fix again, rinse and repeat.
What I tried:
Reset and download A-GPS state. Reset dalvik cache using recovery. Reset A-GPS state, turn off GPS, turn off phone, turn on phone (and variations of this). Didn't work...
What worked:
Finally I got sick of it and took out my real GPS device. I didn't turn off nexus' navigation (wanted to torture it a bit out of spite and frustration).
After driving for 40 minutes (and nexus finding, losing, finding ... GPS fixes as I was driving), suddenly it got a fix, and it just started working again without problems.
Anyone know what's happening here and how to fix it? Thanks so much in advance
You are not alone
Rebooting almost always fixes it for me. Unfortunately it takes several minutes.
Airplane mode also instantly fixes it, but then you lose A-GPS and all communications.
Radio updating may fix the problem.
Try flashing a latest radio image.
Latest radio
Thanks. I guess a new, functioning radio would indeed solve the problem.
However, I already have the latest radio flashed: 32.50.0032U_5.12.00.08 for the Nexus One. Earlier radios have other heavy shortcomings, so they are not a good option.
i wold know if it was good be4
cuz it was worked fine but now ive same problem
i thought this problem form rom
but now i dont know the reson
sorry 4 broken eng
thx
I am waiting for ICS and hope that will fix it.
I'm having a couple of wonky issues that recently presented themselves.
First, the compass is acting up. It always points in the wrong direction in Maps. It is usually about 45 degrees off, but lately it seems to only want to point south. It also points in the wrong direction when using GPS Essentials, but I haven't tried anything else.
Second, and the more frustrating issue: Maps is not working. First issue with maps: When I search for a destination and look at the route (before I start the route guidance), if the screen shuts off the phone will not wake up. I will have to reboot the phone. Second issue with maps: Route guidance crashes the phone. Specifically, when the voice talks, maps will freeze, causing me to have to reboot the phone. The really strange part is if I turn the volume all the way down, I can navigate just fine. It is only when the voice talks that it crashes. However, as you can guess, a voiceless guidance isn't all that helpful.
Things that I have done in the past that may or may not have any affects on my current issue: I have used faux's kernel, but went back to the stock kernel. I also use Viper's audio fix.
Does anyone have any suggestions for me to try to fix this??
*sigh*
The only time things work correctly is if you ask for help, right? I don't know if I have a permanent fix, but the compass and maps issues have subsided.
Here's what I did: I tried to use GPS Essentials multiple times to calibrate the compass with no success. I then tried GPS Status and Toolbox and that seemed to properly calibrate the compass, so that issue may be resolved.
Concerning the maps crashing: I tried disabling Viper audio for the phone speaker (I hadn't had this issue when the voice guidance was through the bluetooth), and it seemed to act normally. Since I only used Viper for the phone speaker I decided to totally uninstall the driver and app.
I don't know if this is a perma fix, but I'll try it out for a while and see what happens.
I don't know what might have happened, but this morning, I tried to connect my Phone to WiFi, and for some reason, it wouldn't. The WiFi toggle button that you see when you pull down the Notification Bar, now that WiFi button keeps turning on and off constantly. The time it takes between each toggle (on to off or off to on) is just about 0.5 - 1 sec. This is crazy. I can't connect to my WiFi.
I googled for solutions, no luck. I hard reset my Phone, no luck still. I wiped Partition Cache too. I entered into the Safe Mode, the same behavior happened. It's weird. It's like my Phone is possessed or something. A virus maybe?
Any input would be much appreciated. My phone is running the latest Firmware from T-mobile. And I got the update maybe 1-2 weeks ago and it had been working fine until this morning the issue started.
My phone just started doing this as well. Wifi keeps turning off and on. If I want to keep it off I have to restart my phone. If I want to use the wifi I have to manually toggle it from the wifi settings. Just weird it started doing this just recently. Maybe an app we both have installed?
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
febzz88 said:
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
Click to expand...
Click to collapse
Haha I was about to post this solution as well! Turning off the wifi in location accuracy fixed it. You're right about probably some Google app is causing this as this hadn't happened before yesterday. Sorry you had to format your phone to find this out...hopefully google or samsung can fix this from their end.
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
I just uninstalled wear and same issue persist. Last app from Google that I did an update on was Google home...formally known as chromecast.
---------- Post added at 10:30 AM ---------- Previous post was at 10:04 AM ----------
I just uninstalled Google home and the issue went away.
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
febzz88 said:
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
Click to expand...
Click to collapse
Yup that was me leaving a comment haha
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
androidschmandroid said:
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
Click to expand...
Click to collapse
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
alanmv567 said:
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
Click to expand...
Click to collapse
no, i do not.
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Go to location>improve location>unchecked wifi scanning. It just worked for me
Uninstalling android wear seems to have worked for me.
febzz88 said:
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Click to expand...
Click to collapse
Definitely not the compass, been through the calibration process. Attempted many fixes including special GPS settings and utilities. At times the phone can sit there with screen on for over 10 minutes without acquiring a single satellite. I'm thinking hardware issue, possibly contacts for the antenna. In any case, not relevant to this thread...
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
DirtySant0 said:
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
Click to expand...
Click to collapse
I had tried this prior to reformatting my phone and it didn't help. I then wiped the cache again and reformatted the phone; in fact I reformatted and cleared cache 3x because the issue kept coming back after I reinstalled apps again. This is weird, the situation and resolution vary a lot from one user to another. Then I simply turned off WiFi Scanning under Improve Accuracy in Location, and the issue went away.
WHEW! Uninstalling Wear and Home did it for me. For now, anyway. I "fixed" it this morning by toggling Ultra Power Saver on and off, and it worked all day until I came home from work. Then nothing helped until I found this thread. Changing GPS settings didn't do it for me, but I'm still on Lollipop so my location settings are a little different.
Thank you, Febzz and Alan!
Google home was the issue!!
Sent from my SM-N910T using Tapatalk
Changes in router's Wireless Security had caused it in my case
This is old thread but still I am posting this solution as it could be useful tip for someone in future.
I had this issue and was causing me real headache. I initially thought it was hardware failure of my phone but later I found reason is something else.
For some reason I had changed Wireless Security of my WiFi router from WPA2 Personal to something else (I guess WEP).
That was causing my phone (intex cloud 4g) often to turn on and off WiFi on its own. I changed the Wireless Security back to WPA2 Personal and phone is now back to normal (not turning WiFi on and off on its own)
I have a problem with GPS. Rarely finds satellites and loses them. I noticed the problem after the installation of the update from 1 January.
Has anyone noticed similar problems on their device?
This is really annoying. Especially when it comes to navigation.
I'll add that I've already removed the case and it didn't help anything.
Greets.
I second this. I have the same issue w/ my GPS.
The problem has solved itself. I don't know how, but everything has returned to normal.
I have the same problem after Oreo update. Then a new update came and the problem stoped for a while, but now it's back!
Does anyone have a solution or workaround?
Same here...