Hi everybody,
Just noticed I'm having some issues with sensors being used 100% of the time by navigation apps, eating up my battery like crazy.
First I've noticed Sygic 11.2.6 showing as the second battery consumer (about 25% of the total battery usage at any given time) with orientation sensor used 100% of the time even though no process related to Sygic was running.
Restarting would fix the problem, only for it to reappear as soon as I started Sygic again.
After I've uninstalled Sygic I noticed Google Maps 6.6.0 having about the same behavior, using the accelerometer 100% of the time even after force closing the app. Again, restarting the phone would fix the issue but running Maps once would make it appear again.
I tried uninstalling the updates, reverting to version 5.8.0 and no more accelerometer issues. Updated to 6.6.0 and started having the same issues again. Uninstalling the updates once more and again no sensor issue.
One interesting thing is that if I restart the phone and then disable auto-rotation, once I run Sygic or Google Maps 6.6.0 the apps start using the orientation/accelerometer sensor 100% of the time just like they use to (even though it's disabled!!!!...?!?!).
To me this would seem like a software issue. Anybody else experiencing something similar?!
Thank you in advance for your opinions!
Inginerul said:
Hi everybody,
Just noticed I'm having some issues with sensors being used 100% of the time by navigation apps, eating up my battery like crazy.
First I've noticed Sygic 11.2.6 showing as the second battery consumer (about 25% of the total battery usage at any given time) with orientation sensor used 100% of the time even though no process related to Sygic was running.
Restarting would fix the problem, only for it to reappear as soon as I started Sygic again.
After I've uninstalled Sygic I noticed Google Maps 6.6.0 having about the same behavior, using the accelerometer 100% of the time even after force closing the app. Again, restarting the phone would fix the issue but running Maps once would make it appear again.
I tried uninstalling the updates, reverting to version 5.8.0 and no more accelerometer issues. Updated to 6.6.0 and started having the same issues again. Uninstalling the updates once more and again no sensor issue.
One interesting thing is that if I restart the phone and then disable auto-rotation, once I run Sygic or Google Maps 6.6.0 the apps start using the orientation/accelerometer sensor 100% of the time just like they use to (even though it's disabled!!!!...?!?!).
To me this would seem like a software issue. Anybody else experiencing something similar?!
Thank you in advance for your opinions!
Click to expand...
Click to collapse
Yes... noticed this with Sygic. It's a known app bug, and they still haven't fixed it yet. Haven't had this issue with Google maps though. Be warned however that any navigation app will chew up your battery very fast... Can't help it since it's accessing the Net, Compass, Accelerometer and GPS antenna - all at the same time at a high refresh rate...
Thank you fir your reply!
I know navigation is supposed to use a lot of battery but doing it even with processes closed?
It's good to know you confirm the Sygic bug. Honestly I've googled for 2 days and wasn't able to find any useful info about such a bug with Sygic. And for me, since Google Maps 6.6.0 acts the same way, it makes me think it's also a bug. For now I'm sticking to Maps 5.8.0 and I've reported the issue over to Google.
Thank you again!
Related
Hello,
I have a Nexes S since about a month, and in this period, I noticed that Google Maps have a strange behavior: whenever I run a task manager, I find Google Maps process active and if I kill it, after a few minutes it became newly active.
Also in battery consumption screen of Nexus S menu, I can read tath Google Maps is always around 20% of total battery consumption.
Is this behavior normal?
Is there a manner to limit Google Maps Activity?
Thanks.
Mephysto
Which version of gb are you using? On 2.3.2 there were issues with latitude, if you were signed in then it would drain battery life but the 2.3.3 update supposedly fixed this issue.
Also, if you after using location based stuff I'm pretty sure it uses maps to determine where you are. Therefore fc won't work as it will just open again.
Sent from my Nexus S using XDA App
I'm sorry,
I have gb 2.3.3. I'll try to logoff from latitude.
For what it's worth, my battery dropped from about 35% to 10% overnight last night, and I'm not sure why. I did notice that Google Maps was listed as taking up 23% of my battery. I'm on 2.3.3 also.
Uninstall the updates and install again.
Sent from my Nexus S using XDA App
mephysto666 said:
Hello,
I have a Nexes S since about a month, and in this period, I noticed that Google Maps have a strange behavior: whenever I run a task manager, I find Google Maps process active and if I kill it, after a few minutes it became newly active.
Also in battery consumption screen of Nexus S menu, I can read tath Google Maps is always around 20% of total battery consumption.
Is this behavior normal?
Is there a manner to limit Google Maps Activity?
Thanks.
Mephysto
Click to expand...
Click to collapse
Ever since the 5.1 update to Google Maps there's a permanent service which will run (and restart if you attempt to kill it). However, if you are not signed into Latitude it should use little to no battery. It doesn't even appear on my Battery Use list if I haven't used Maps.
I recommend never staying signed into Latitude. It will destroy your battery due to the constant GPS and data updates.
After the latest 4.4.4 OTA update, im getting battery drained from Google Maps and Waze after opening them. Force closed them but the GPS is still going on. Location has been turned off. It only goes off after rebooting. Any solutions for this?
jkfoong said:
After the latest 4.4.4 OTA update, im getting battery drained from Google Maps and Waze after opening them. Force closed them but the GPS is still going on. Location has been turned off. It only goes off after rebooting. Any solutions for this?
Click to expand...
Click to collapse
The same thing is happening to me. Also on 33R. Did you (or anyone) find a solution for this? (apart from rebooting)
Cheers,
No, this is not about the Play Services wakelock, this is about Google Search
Here's a link to the album where I show the wakelock: https://imgur.com/a/J133S
I asked on Reddit as well, but got no answers, so I thought I'd try here.
Symptoms:
Google App is awake all the time
Wakelock being held is the AudioIn wakelock
Relatively high battery drain considering airplane mode is being used (Google App probably uses periodic pinging of GPS)
A pro of this is that "OK Google" seems to work all the time even with the screen off and phone unplugged.
About my phone:
For the record I'm on an April build of CM11 (someone on XDA built this over a month ago to include the SystemUpdateService) wakelock.
The screenshots are on Google Search 4.5.13.19
I tried updating to Search 4.6.10.19, but saw the same wake issue.
I tried flashing the latest Gapps which includes Search 4.6.10.19 and Play Services 7.5.66. Still no good. After I unplugged my phone for work today I noted that OK Google worked in the car without plugging the phone in and confirmed phone was awake the whole time.
Using Amplify for nlpcollectorwakelock and nlpwakelock
Using Greenify but not greenifying Search or Play Services
Not using Privacy guard to do any funky stuff like disabling keep awake either.
Misc.
Looks like someone else experienced this too except he's on CM12.1?
bump
No one has this issue? I thought it was CM11 only so I wiped my phone completely, installed CM12.1 and flashed TK Gapps 0530 full and I got the wakelock the same day....
I've got this. Oneplus one, cm12.1.
Find a couple of posts about it but no solution
Hi there,
i'm currently on the newest cm13 nightly and if i'm updating my system my compass is always completly wrong. After different solution for the compass calibration it will work till the next update again. Is there a way that the compass has not to be calibrated on every update? it's really annoying because sometimes the calibration works instantly and then sometimes it takes more than 10 minutes.
Especially if i want to use gps and have not calibrated after update, it can be that i need much time for calibration to get gps work..
Thanks
When I us the Google Fit app to track my hike, it stops tracking and GPS immediately after screen goes off. As soon as the screen is on again, GPS and fit app works again.
I have the apps allowed to run in the background and turned off the battery optimization for these apps and the Goggle play service.
I haven't found a protected list or something similar in Emui 8.
Locus (an other tracker) works well.
Any ideas how to solve this?
I found the solution : I closed (click on it) the lock in the recent apps history. Now Google fit works
Unfortunately, this solution isn't stable. Sometimes it works sometimes not.