I remember that I had similar issues with my old Galaxy S5 and the issue persists with my current Google Pixel 3a XL.
I don't want to use "Google Location Accuracy". I'm totally OK with just using GPS. So I went to the location settings and switched "Google Location Accuracy" to "off".
BUT: I have to redo this regularly. The usual hint is that Pokemon Go gets unexpectedly fast GPS fix. In this case I revisit the settings just to find out that Google decided to reenable "Google Location Accuracy" against my will.
I still don't know what the pattern behind this is. To be honest I'm a bit pissed that Google gives a **** about my preferences and toggles them back on every now and then.
Is this a common issue? I searched a bit and could not find anything interesting about automatic reenabling of "Google Location Accuracy". Is there some other setting I have to change to permanently opt out of "Google Location Accuracy"? Is this done by an app that can be uninstalled/disabled? Is it at least possible to install some APK which monitors the setting and warns if Google, again, reenabled it against my will?
Thanks in advance.
I run Samsung's. I keep location disabled 99% of the time. Firewall block that game or ditch it.
Enough of these data mining whores...
MicroG?
Related
I picked up a Charge last Friday and rooted it the next day. However, both before and after the root (to gummycharged) the network location functionality was broken. Maps would only give me a location if GPS was enabled; trying to get one with GPS off gives a "Please enable a My Location source in system settings" popup even though "VZW Location services" is checked. And nevermind the legal message that comes up every time GPS is enabled...
So the question is, did I break something? I've searched for stuff all day, and though there was some stuff about things being broken with that function on other devices around the end of last year, I haven't seen anything since. I'm wondering if I should just wait for a gingerbread ROM to come along and install that to see if that fixes things...
Update: I have tried copying in a networklocation.apk file from another ROM into my system/app folder, but still no luck. I don't understand why it won't even try to use the network location. I even found the NetWork Location app, which seems to be working just fine and giving me lat/long. It just doesn't work for maps.
VZW Location Services isn't a source that google maps (or pretty much any other program on your phone) can access. That service is only for Verizon Navigator (which is $10/mo and doesn't provide much that Google Maps gives you for free).
So, you have to enable one of the other location services, either the GPS or the google location services.
Google wrote the message that "Please enable a My Location source in system settings" but Verizon added the menu entry for their location services after that. That's why it sounds like checking the Verizon box should make maps work, but it doesn't.
Ah, that makes some sense now. *smacks forehead*
So, I've checked the Google box, and now I don't get the message any more, but it still won't give me a location even after rebooting.
Should I go back and install the regular gummycharged mod? I think my screwing around with networklocation.apk may have actually broken it...
EDIT: IT WORKS!!! Went back, reinstalled gummycharged, and it f'ing works!
You, sir, are The Man. Or The Woman, as the case may be.
Hey everyone, my play services updated last night to 6.5.87. I keep my location on "device only" to tame the wakelocks and since the update my GPS icon turns on every time I unlock my screen. When I go to location it says that play services was using "high battery" location. This is really annoying as "device only" location was awesome for me. It would get rid of the npl location wakelocks and GPS worked great when I needed it without having to switch to "high accuracy". I'm running stock 5.0, unrooted. Has anyone encountered the same issue? Or can anyone that's running the same play services check if it occurs to you too? Thanks.
Are you using smart lock with location setup? If so that's why. Did the exact same thing to me when testing it. Even worse it never worked when in doors because the GPS couldn't ever see me.
frigidazzi said:
Are you using smart lock with location setup? If so that's why. Did the exact same thing to me when testing it. Even worse it never worked when in doors because the GPS couldn't ever see me.
Click to expand...
Click to collapse
Nope. I only have my moto 360 setup as a trusted device/smart lock. Trusted places is set as "none" That's why I'm so confused why it started happening.
I am getting this too. Haven't narrowed it down yet. Might be one of my greenified apps.
Jnewell05 said:
I am getting this too. Haven't narrowed it down yet. Might be one of my greenified apps.
Click to expand...
Click to collapse
The thing is, if you look at location services, it tells you that google play services is the one that's requesting the GPS location.
Since a while I'm having big problems with SmartLock Trusted Places. When I'm @ home and having the home address from Google Maps enabled, it almost never works.
If I manually add my neighbors addresses as well it works for the moment but that result does not last.
If I go into the settings and add something it updates my location to the very address that is added automatically by enabling Home from Google Maps.
Location and location history is enabled on the device.
High accuracy, battery saving & device only all get the same result, it does not work.
Running 5.1 with Google Play services 7.0.97 (-438).
Does it work for you?
I actually just logged on to ask the same thing. It's been this way ever since 7.x dropped. It's so frustrating all the issues this new play services has caused.
Hi all.
Out of the blue I got this error message every minute.
I use Unofficial Beanstalk ROM 5.0.2.
Stock kernel.
I cleared cache, and Dalvik. I also cleared cache of Google Play Services and Google Services Framework.
But this error keeps coming back.
I haven't changed anything in the phone nor have I messed with any system settings.
I can't find any decent solution to the problem.
The apk shows version 7.5.71 (1955121-438)
Appreciate your help.
gil80 said:
Hi all.
Out of the blue I got this error message every minute.
I use Unofficial Beanstalk ROM 5.0.2.
Stock kernel.
I cleared cache, and Dalvik. I also cleared cache of Google Play Services and Google Services Framework.
But this error keeps coming back.
I haven't changed anything in the phone nor have I messed with any system settings.
I can't find any decent solution to the problem.
The apk shows version 7.5.71 (1955121-438)
Appreciate your help.
Click to expand...
Click to collapse
AFAIK, there is no "decent" solution at this time.
Please change your Location setting to Device Only. It will stop the FCs for the time being.
knedge said:
AFAIK, there is no "decent" solution at this time.
Please change your Location setting to Device Only. It will stop the FCs for the time being.
Click to expand...
Click to collapse
No one knows why it happens or how to solve this? wierd.
How is this related to device location settings?
Out of nowhere I get "Google Play Services" has stopped working messages like every 20sek. Working with the phone is impossible and my Moto 360 doesn't work anymore either Using Stockrom CM12S with franco kernel, any ideas or solution?
Same problem here. This is so annoying!
Will try "device only" now. AFAIK this uses only GPS to get your current location - so this should dramaticly increase battery drain, right?
This trick didn't help
Same case. I am also getting these errors. there are solutions people have posted to disable GPS. But the phone is useless when it is without GPS.
Waiting for a fix ASAP.
For me it actually did! In another thread another solution came up: try enabling "keep awake", "wake up" and "autostart" in Privacy Guard for the Google Play Services. This also worked for me (although my Privacy Guard was not enabled for the Google Play Services the settings still did matter! So make sure to really enable them in the submenu!).
The random crashing seems to occur when:
location "high accuracy" PLUS Google Play Services are limited in Privacy Guard (keep awake, wake up, autostart)
Disabling one of the two should fix the problem.
BTW disabling GPS didn't solve the problem for me. "device only" means you only use GPS and not network location. The network location thing is what causes the crashing in combination with the Privacy Guard. So (at least for me) no need to disable GPS.
Looks good. Let me see if there is any issues now. I remember we all changed the "keep awake", "wake up" and "autostart" in Privacy Guard for the Google Play Services in an older version of Google Play Services.
Hope this is all fixed now and should not drain the battery (as it did in previous version).
How I solved the Play Services stopped FCs
Hardly this last version of Google Play Services will work properly, either clearing the data, blocking services on Privacy Guard, etc. Tested many things and the problem comes from the last update of Play Services, which includes in its changelog suspiciously some "Location Api improvements".
In my experience these last days the problem it seems to come when the services requests for location. If you use Apps asking frequently for locations you'll have the error very often, making usefulness your phone, as least mine. Using 3 Apps needing GPS location at same time is frustrating..
How I solved for now:
Go to Play Store, find Google Play Services in your Apps
Click on Uninstall (only will uninstall the last update of Google Play Services).
From that moment, some advice about certain Google Apps (Hangouts, Google Maps, etc.) may appear if you have these Apps installed. Ignore them, otherwise you'll need to update again if you want to use them, but...
But I can't find google play services in play store.
GPS vs Networ in Location fixed
gil80 said:
Hi all.
.
Out of the blue I got this error message every minute.
I use Unofficial Beanstalk ROM 5.0.2.
Stock kernel.
I cleared cache, and Dalvik. I also cleared cache of Google Play Services and Google Services Framework.
But this error keeps coming back.
I haven't changed anything in the phone nor have I messed with any system settings.
I can't find any decent solution to the problem.
The apk shows version 7.5.71 (1955121-438)
Appreciate your help.
Click to expand...
Click to collapse
Same as TerrorApple. Disable Location services, but as this is needed often enable Location services only with GPS. This worked for my device
I have installed a fake GPS application (Lockito) and set it up as Mock Location App. It doesn't actually matter which one I use, it's always the same behaviour.
I start a route, but it's jumping to my real location every 4 to 5 seconds, stays there for a similar amount of time and jumps back to my faked location.
My understanding is that this mock locations dev option would overrule ANY location update from somewhere else, but seems it isn't.
What I tried:
- Device administrator: turn off any administrator
- Location set to "GPS only".
- turn off wifi scanning
- smalli patch activated in magisk (with mock location checked)
- fused location on (or off) -- no change in behaviour
- Using the "experimental mode" of Fake GPS routes: no change in behaviour
- Google Play Services 21.2.12-16 (I tried uninstalling the current version, but this leaves my fake gps app not working)
- Installing the app as a system app (restart afterwards): no change compared with the normal
- Google Maps 10.47.1 (reverted this back to 9.26.1)
So, what I'm wondering is: what process is injecting my real location?
And should that even happen when using the mock locations? As far as I know if I would be using mock locations it should just use this info as my gps information... And not use any other data?
Does anyone have any hints on what I can still try?
coder.toolbox said:
I have installed a fake GPS application (Lockito) and set it up as Mock Location App. It doesn't actually matter which one I use, it's always the same behaviour.
I start a route, but it's jumping to my real location every 4 to 5 seconds, stays there for a similar amount of time and jumps back to my faked location.
My understanding is that this mock locations dev option would overrule ANY location update from somewhere else, but seems it isn't.
What I tried:
- Device administrator: turn off any administrator
- Location set to "GPS only".
- turn off wifi scanning
- smalli patch activated in magisk (with mock location checked)
- fused location on (or off) -- no change in behaviour
- Using the "experimental mode" of Fake GPS routes: no change in behaviour
- Google Play Services 21.2.12-16 (I tried uninstalling the current version, but this leaves my fake gps app not working)
- Installing the app as a system app (restart afterwards): no change compared with the normal
- Google Maps 10.47.1 (reverted this back to 9.26.1)
So, what I'm wondering is: what process is injecting my real location?
And should that even happen when using the mock locations? As far as I know if I would be using mock locations it should just use this info as my gps information... And not use any other data?
Does anyone have any hints on what I can still try?
Click to expand...
Click to collapse
Find your location settings on system settings, select your Google account then turn off location accuracy, you want the location setting on, but you don't want the improved accuracy.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Find your location settings on system settings, select your Google account then turn off location accuracy, you want the location setting on, but you don't want the improved accuracy.
Click to expand...
Click to collapse
Thanks. This I knew already. Yesterday night I finally figured it out what was going on & posted it here: forum.xda-developers.com/showpost.php?p=83200513&postcount=6163.