Database Develop

NetworkLocationLocator battery drain

hi everyone, recently i discovered huge battery drain on my note. when i fully charge it the battery drops from 100 to 80 percent in about 9 hours of standby. in order to find the culprit i installed better battery stats and let it run over night. i found out that something called networklocationlocator keeps my device from going into deep sleep (see attached screenshot).
does anyone know which app is behind this service? i think that its google now but i am not quite sure and dont want to uninstall it since its a really good app.
thanks in advance
Sent from my Note

probably when you go to settings and then location services, switch all off, switch back on only when you need it.
It would be interesting what is triggering your phone to seek location, could be a buggy app running silently updating every so often. I think the logs could tell you that. But not sure. I set location of in many apps in app settings cause I feel they dont need it.
I know that switching apps is buggy, It could be google maps running silently in background. Got to settings, apps running and stop those. Might need to stop as well in cached running.
I guess with root, and something like pdroid or lbe you can block apps requesting location services, also an option
Sent with a grin (^.^)

baz77 said:
probably when you go to settings and then location services, switch all off, switch back on only when you need it.
It would be interesting what is triggering your phone to seek location, could be a buggy app running silently updating every so often. I think the logs could tell you that. But not sure. I set location of in many apps in app settings cause I feel they dont need it.
I know that switching apps is buggy, It could be google maps running silently in background. Got to settings, apps running and stop those. Might need to stop as well in cached running.
I guess with root, and something like pdroid or lbe you can block apps requesting location services, also an option
Sent with a grin (^.^)
Click to expand...
Click to collapse
This is a 'bug' with google maps that has persisted for at least over a year now and it affects a lot of devices. Users have been complaining for the longest time and it seems like it's falling on deaf ears at google. It's a shame! There is NO acceptable 'fix' - turning off google locations services will get rid of this problem but again, as i said, that's not acceptable!

jknolls said:
This is a 'bug' with google maps that has persisted for at least over a year now and it affects a lot of devices. Users have been complaining for the longest time and it seems like it's falling on deaf ears at google. It's a shame! There is NO acceptable 'fix' - turning off google locations services will get rid of this problem but again, as i said, that's not acceptable!
Click to expand...
Click to collapse
I dont think its a bug affecting all roms. Nor that it has been there for over a year.

SystemUpdateService always on

Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?

keeekeeess said:
Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?
Click to expand...
Click to collapse
I installed (cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip) on my device
and i am not found this problem?

try wakelock detector to see what's keeping it awake http://forum.xda-developers.com/showthread.php?t=2179651

Starting today, I got this issue as well on a Nexus 4 device running the M7 snapshot with hellscore kernel. The first 2 steps you took didn't work for me too. Didn't know about #3 this far.
keeekeeess said:
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Click to expand...
Click to collapse
Doesn't sound pretty, but how did you do this? Still better than running out of battery halfway through the day, I'd guess.
pryerlee: WLD says exactly that - Google Play Services -> SystemUpdateService, for me currently 4h23m, being 100% of the time - plus it says "x2" (what's that precisely?)

not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962

it is not work this servicein with lock screen!!
(i speek arabic good but english not good)
Sent from my GT-I9000 using XDA Free mobile app

pryerlee: Couldn't make anything out of those.
Just linking the other way round as well, maybe it'll help - the issue popped up on CM forums too: http ://forum.cyanogenmod. com/topic/96459-systemupdateservice-wakelock-on-cm11-m7-massive-battery-drain/
(sry for destroying the link, I'm blocked from posting it.)

pryerlee said:
not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962
Click to expand...
Click to collapse
I did all of the options, the service is closed yet it was still running.
I compromised and installed Paranoid Android 4.4.2 and the problem is no more.

So just trying stuff without any deeper thoughts, I just did two things, locked the phone afterwards and now the wakelock seems to be gone:
1. I enabled SystemUpdateService using Disable Service App, which had already been disabled when we first looked.
2. I looked into the CM update function, where - having selected all stable releases - nothing was showing and refreshing didn't work. Got the idea to look into Disable Service App again, and found that UpdateCheckService of CyanogenMod-Updater was disabled. Enabled it, refreshed CM updater, got a list of stable releases.
My beginner's guess would be #1 did it - but why was #2 even an issue in the first place?

Running CM 11 M7 Snapshot 6/9/14 msm8960 on Motorola Atrix HD MB886. Have seen something similar.
Details:
- Have not seen this issue for weeks of running this ROM until now.
- This seems to have started a few (2?) days ago after an update. Google Play Music, Maps, Search, Drive, Sheets, and Docs all received updates in the past week.
- Typically, based on the configuration and usage of my phone, when the screen on is off the phone is in Deep Sleep (percentage in high 90s).
- At some point after some app or service is run, the phone stops going into deep sleep.
- Better Battery Stats shows SystemUpdateService as having partial wakelock for about the same percentage of time that the phone should be in deep sleep (high 90s).
- SystemUpdateServices does not seem to be hogging battery even considering that it might be folded into another category, but the wakelock causes the phone to use battery more than twice as fast as in deep sleep.
- A restart clears it up until the SystemUpdateService is invoked again by... whatever... seems to be something I do manually - still chasing it.

IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.

Silkeyway said:
IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.
Click to expand...
Click to collapse
I've been able to consistently replicate the problem 100% by running the Google Play app when the phone has a data connection.
If I run the Google Play app when the phone has no data connection the problem does not occur until the next time the phone has a data connection, whether or not Google Play is running.
I do have all auto-updating disabled in google and elsewhere which makes this easier to chase.
See if it happens when your phone has no data connection, with apps and google things set not to autoupdate.
As for the temporary fix: Like you said: Disable Service app, System Apps list, Google Play Services, SystemUpdateService enable/disable.

I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?

I also had the wakelock on my P990.
systemupdateservice was disabled in gooogle service framework, but it was still active as receiver and actice receiver in google play services - disabling it there solved the wakelock for me.

Silkeyway said:
I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?
Click to expand...
Click to collapse
Now that I've tested during a work day I'm seeing the problem occur more pervasively as some of you are
- It starts any time I go on line.
- Reboot sometimes but not always fixes
- Toggling using Disable Service app no longer works reliably
- Must stop Google Services Framework to fix issue until next time I go on line
= Royal PITA!
As for your question; It is not uncommon in the world of computers (and phones) to have to toggle a setting on/off or off/on to get the setting to stick, especially when something deeper in the system is turning it on and off without a flag letting the user know.

Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).

Silkeyway said:
... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Indeed hoping the same, and it looks like M8 and the nightly to which you refer will not yet be using the KK bootloader (great for my old Moto AtrixHD MB886 w/JB bootloader). Found that same XDA post referring to Autorun Manager which looks like a good temporary fix - working good so far. Does not hold setting through restart but still more effective than others..

I've the same issue here since 2/3 days on my 9001 running CyanogenMod 11.0 by ADC-Team - Release 8, maybe it was some app update occurred recently... I didn't have any issue with the same rom before.
---------- Post added at 10:29 AM ---------- Previous post was at 10:00 AM ----------
I can confirm that downgrading Google Play Services to version 4.3.25 is a working workaround.
http://forum.xda-developers.com/showpost.php?p=53851739&postcount=3026

Silkeyway said:
Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Hey everyone,
i can confirm the issue for CM11 M7 and it all started with the recent update to Google Play Services 5 v84.
The workaround mentioned before works very well until a reboot ... lets hope the best for CM11 M8!

Best workaround I've found:
"Finally I was able to block the SystemUpdateService wakelock, using this app:
https://play.google.com/store/apps/d...com.rs.autorun
go to settings, enable the option to show system entries
find google play services and disable:
SystemUpdateService$Receiver
SystemUpdateService$ActiveReceiver
SystemUpdateService$SecretCodeReceiver
done... no more wakelock and it didn't break anything, syncs all work ok
I know this app doesn't look the best, but I tried others like "Android Tuner Free", "Disable Services", "Gemini App Manager", etc, but they allowed me to only disable the main service and didn't show the other receivers that had to be disabled."
As the other user said, this is all caused by the Google Play Services update that has being rolling out this last week. The solution above is reboot proof (At least for me). Thanks to the user who posted it.

Did anyone notice constant "Searching using GPS" notification after Lollipop update

Did anyone notice constant "Searching using GPS" notification after Lollipop update
Hi guys,
I have Note 4 Exynos version N910C and I have just received OTA Lollipop update for my region. After update everything was ok until the day before yesterday when I needed to change the sim, so it was the first restart after the update. After restart I noticed that there is constant "searching using GPS" notification when I am in the building and seems to went out when I am outside, which means there is some app is constantly searching for GPS and it also seem to drain my battery. So I was inspecting in the settings under Location saw that Yahoo weather which I use as lock screen has reported high battery usage. So tried to clear the app data and voila....the notification went of and everything seem to be at normal. Then I tried to restart the phone and the notification displays again and remain again constant. So now after each restart I have to clear data from Yahoo weather to turn off the "searching using GPS" notification and for my phone not drain the battery. I think it might be some flaw in Yahoo weather after Lollipop update. I did not do factory reset after OTA update so the problem might be because of that.
Just wanted to share for someone who might face the same issue.

I had it on the 910F. Turned off that option for that app. User daemon? I think it was called. Check GPS log. They say by clearing it's cache it'll fix it. But I disabled it as I don't use the widget.

I think that's the Unified daemon which provides data to samsung apps like location for weather.

Yes. That's the one. I have it disabled and it worked wonders. GPS works perfectly, except for that widget.

gps
zkyevolved said:
Yes. That's the one. I have it disabled and it worked wonders. GPS works perfectly, except for that widget.
Click to expand...
Click to collapse
Out of interest how do i turn this off do i need to be rooted?
Many thanks
chris

dambuster617 said:
Out of interest how do i turn this off do i need to be rooted?
Many thanks
chris
Click to expand...
Click to collapse
No need to be rooted. Find it in options. Location. And there it will be with high under its usage. Everything else should be low....

Well that sucks for us that use the widget...

just remember that when you disabled it, you wont get the latest or regular weather update in your note 4.

I've noticed that since the lollipop update I lose the last known position on the GPS. This is used to get a fast fix. So after a reboot I need to go outside to get a GPS fix. Over I've got the first fix the subsequent fixes are sick, even indoors. It's like the GPS is not using a-GPS or Wi-Fi location based services to get an approximate fix to speed up the first fix.
Sent from my SM-N910F

Massive Google Services Drain

Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?

MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.

simms22 said:
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.
Click to expand...
Click to collapse
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.

MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.

StykerB said:
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.
Click to expand...
Click to collapse
Thanks for the tip. No Gasbuddy installed. A few weeks back I had FiveStars installed (a purchasing points app) and it caused a huge Bluetooth wakelock. But that was removed a while ago and didn't affect Google Play Services.

MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.

simms22 said:
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.
Click to expand...
Click to collapse
Yeah, I think you're right.
Sent from my Nexus 6 using XDA Labs

MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
There is an app in the playstore called 'Disable services.
You can disable the services you don't use/need.

In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs

MrBrady said:
In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!

kornball said:
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!
Click to expand...
Click to collapse
Just Google Play Services. I didn't think of looking in GS Framework.
Sent from my Nexus 6 using XDA Labs

WiFi keeps turning on and off on its own

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)