Database Users

why google maps use so much battery

View attachment 1600400
As attach,google maps use too much battery-----I had not use maps ..

Go into Google maps settings into location and uncheck all options in there and ensure that it isn't reporting your location.
Sent from my Nexus 4 using xda premium

much thanks，I'll try this
Sent from my Nexus 4 using Tapatalk 2

tsongwh said:
much thanks，I'll try this
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
press the thanks button instead report back with findings

If you don't use maps at all, freeze with TB

calanizzle said:
If you don't use maps at all, freeze with TB
Click to expand...
Click to collapse
And when you do use maps.... it's a hassle. If you have maps set up properly, it shouldn't even be using any battery life at all unless you turn the app on and actually start using it.
With your theory, you should freeze all apps you don't use? Doesn't make any logical sense.

I've got a similar issue with my battery usage. Comparing the maps usages on my N4 to my Photon, and on my N4, the usage is 10%, keep awake is 40m and the gps is 6m, and CPU is 8m.
For my Photon, the usage is 2%, the keep awake is 2h and the cpu total is 2m.
I do have CM10 on my Photon and still stock on my N4, but the behavior does seem odd. The N4 has much more usage

for me, unchecking location reporting did not fully do the trick. what you need to do is make sure maps does not autostart and cause wakelocks which decrease your battery life substantially. to do this, download an app called "autostarts" from the play store and disable all maps autostarts by sorting the autostart processes by app. this will not allow maps to autostart and use increased battery, but you will still be able to open maps normally and use it to its full extent

Hi
zephiK said:
And when you do use maps.... it's a hassle. If you have maps set up properly, it shouldn't even be using any battery life at all unless you turn the app on and actually start using it.
With your theory, you should freeze all apps you don't use? Doesn't make any logical sense.
Click to expand...
Click to collapse
Exactly it doesn't make much sense.
The usual issue is Google will periodically use Maps to get a GPS fix and Wi-Fi list to update it's own Wi-Fi to Location database. Saves them driving around with cars all the time and getting complaints about privacy I suppose :cyclops: Often it is this background updating of Google Wi-Fi locations that continually pop Google Maps into the battery list even if we never use it between charges.
There is now an easy to use global setting to quickly disable Google Maps from doing this, this is under Settings - Accounts - Google - Location, flick the switch here to off, now Google applications can not poll for locations or do background updates, however other applications can still use GPS and request a location.
Regards
Phil

sorry for bumping this but quite recently my maps app has been consuming battery more than my wifi, it's comparable with OP's photo. Now here is the thing, I already had this problem before and I solved it by disabling location reporting and stuff, but a few days ago it suddenly began to consume battery as if i had reenabled the location reporting stuff. I have used a app called wakeup detector to try and find whats wrong and this is what I'm getting. I hope someone can help.

Download "Greenify" if you're rooted.
Sent from my Nexus 4 using Tapatalk 2

Anyone here using greenify?

And if so: is it working for you? And what apps are greenified on your nexus?
Sent from my Nexus 4 using xda app-developers app

Yes.
Yes.
Maps is a big one. It likes to run in the background and eat up battery.

im using, its working, and most my apps are greenified, besides a few root apps. i dont use notifications for any app besides gtalk and gmail, so i greenify all that i can. i also use an app called autostarts, which works well in conjunction with greenify

ya
I still don't know it's purpose.
Yolo
I can't get facebook message notifications even though I ungreenified them

I used to use it. Among the apps I Greenified were:
1. Facebook
2. Maps
3. ESPN Scorecenter
Although I found that WhatsApp and Viber woke my device quite often, I use them all the time so it didn't make sense to include them in the list.
In terms of effect, it did reduce battery consumption some. But then I figured I'd just be a responsible user and sparingly install apps and turn off notifications altogether if I didn't really need them (or use bookmarks to mobile web versions instead). If you really need all your apps, then Greenify is a safe choice.

mlag said:
I used to use it. Among the apps I Greenified were:
1. Facebook
2. Maps
3. ESPN Scorecenter
Although I found that WhatsApp and Viber woke my device quite often, I use them all the time so it didn't make sense to include them in the list.
In terms of effect, it did reduce battery consumption some. But then I figured I'd just be a responsible user and sparingly install apps and turn off notifications altogether if I didn't really need them (or use bookmarks to mobile web versions instead). If you really need all your apps, then Greenify is a safe choice.
Click to expand...
Click to collapse
The concept of turning off notifications altogether is good only of the app is properly written for it. For example Facebook.... Even if you turn off all notifications whatsoever it still creates wakeups.
Sent from my Nexus 4 using Tapatalk 4 Beta

deeren said:
The concept of turning off notifications altogether is good only of the app is properly written for it. For example Facebook.... Even if you turn off all notifications whatsoever it still creates wakeups.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Correct. Which is why I now use m.facebook.com instead. The Facebook app is a really terrible battery drainer.

I see maps waking up the phone quite often. But will Google now still work if you greenify maps?
Sent from my Nexus 4 using xda app-developers app

Excessive drain with Google Maps....

Anyone know how to get rid of the excessive battery drain from Google Maps? Currently running Slim Beta 4 and KT's Kernal. Are there settings I can change or is the only option involve freezing it which is NOT a valid option. Thanks.
Sent from my SGH-I337 using Tapatalk 4

chipstien said:
Anyone know how to get rid of the excessive battery drain from Google Maps? Currently running Slim Beta 4 and KT's Kernal. Are there settings I can change or is the only option involve freezing it which is NOT a valid option. Thanks.
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Yea, it happens. There are several threads about it already. You might want to try clearing your Maps cache, turning off locator services (might derp other functions), or uninstalling and then re-installing maps.
Personally, I find that the "drain" is usually temporary and happens often around the same time anything "Google" is updated. You can try manually stopping the app in settings and then reboot the phone. Most times, the "drain will subside during the next charge cycle. If you need further information, try searching for the many threads that already exist about this. There is some good info in them. Good luck.

You can also use Greenify to "sleep" your Maps or any other app.
It should not be necessary though. A proper Maps install won't drain the battery at all.

Root, Facebook, and battery life

After rooting my H810, I was unable to Greenify Facebook, as it was recognized as a system app (preinstalled bloat), and seemed to be a major battery hog. I was also limited on how I could limit its permissions.
I used Titanium Backup to delete that FB app, then reinstalled it from the market. That version was able to be Greenified, and there is more control over permissions. Since then, I have seen a considerable improvement in battery life. I've been unplugged since 6:20 this morning and I'm still at 76% right now at 2:26! I don't know if there was something rogue going on with the FB app behind the scenes, but I see a huge improvement. Far too significant to be a placebo.

What permissions did you limit?
Sent from my LG-H811 using Tapatalk

Supersanborn said:
What permissions did you limit?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Every single one except location. I usually have that turned off on my phone anyway.

Eric618 said:
Every single one except location. I usually have that turned off on my phone anyway.
Click to expand...
Click to collapse
How do you update permissions?

Eric618 said:
After rooting my H810, I was unable to Greenify Facebook, as it was recognized as a system app (preinstalled bloat), and seemed to be a major battery hog. I was also limited on how I could limit its permissions.
I used Titanium Backup to delete that FB app, then reinstalled it from the market. That version was able to be Greenified, and there is more control over permissions. Since then, I have seen a considerable improvement in battery life. I've been unplugged since 6:20 this morning and I'm still at 76% right now at 2:26! I don't know if there was something rogue going on with the FB app behind the scenes, but I see a huge improvement. Far too significant to be a placebo.
Click to expand...
Click to collapse
Then if so get the premium version of greenify which lets you hibernate system apps

Apps like facebook and clean master eats up the major system resources and put a heavy load on the ram and processor..this is a proven thing..and not a personal opinion..
Sent from my Micromax A110 using XDA Free mobile app

There's Debloater, so you don't even need root to get rid of the bloat. I also noticed a huge improvement in battery life and responsiveness after clearing out a ton of crap!

I haven't tested this. But I thought I saw someone mention that even if you Debloat an included bloatware app, you can't simply install a replacement (updated version). The phone considers it already installed.
My apologies if a have this wrong. But it sounded like root would be required to replace apps that cannot normally be uninstalled, as was described above.

Did you freeze the Facebook system app or completely uninstall it?
I'm afraid of getting security errors on boot if a system app is missing

RedOCtobyr said:
I haven't tested this. But I thought I saw someone mention that even if you Debloat an included bloatware app, you can't simply install a replacement (updated version). The phone considers it already installed.
My apologies if a have this wrong. But it sounded like root would be required to replace apps that cannot normally be uninstalled, as was described above.
Click to expand...
Click to collapse
That may be true. I think Debloater does the same as going to the app in the Apps menu and disabling it. I disabled Facebook that way, and it showed up as blocked in Debloater before I'd ever actually blocked anything. (But Debloater lets you disable apps that the menu doesn't.) I don't use Facebook so I haven't tried to install another version.

I completely uninstalled it with TI, rebooted, then installed it fresh from the market. Then I locked down permissions and Greenified.

Eric618 said:
I completely uninstalled it with TI, rebooted, then installed it fresh from the market. Then I locked down permissions and Greenified.
Click to expand...
Click to collapse
How do you change the permissions?

elsamuraiguapo said:
How do you change the permissions?
Click to expand...
Click to collapse
I use App Ops by Nowsky. It's available in the Play Store.

Marshmallow 6.0.1 App permission (waking up device)

Hi all,
I have a question regarding the new app permission management in Marshmallow 6.0.1. In Lollipop (5.1.1) we used to have the option to prevent an app from waking up the device or keeping it awake. I used to uncheck that box for Google Play services as this was constantly running and eating up my battery. When I go through the new extended Marshmallow app management, I get several options that i can allow or deny (body sensors, calendars, camera, contacts, location, etc. see attached screenshot). But nowhere can I find the option to prevent the app/service from waking up or keeping the device awake.
Anyone know where I can find this or how to do this in Marshmallow?

OneTruth said:
Hi all,
I have a question regarding the new app permission management in Marshmallow 6.0.1. In Lollipop (5.1.1) we used to have the option to prevent an app from waking up the device or keeping it awake. I used to uncheck that box for Google Play services as this was constantly running and eating up my battery. When I go through the new extended Marshmallow app management, I get several options that i can allow or deny (body sensors, calendars, camera, contacts, location, etc. see attached screenshot). But nowhere can I find the option to prevent the app/service from waking up or keeping the device awake.
Anyone know where I can find this or how to do this in Marshmallow?
Click to expand...
Click to collapse
Use latest package disabler for preventing apps to awake the phone or updated through Google play
Sent from my SM-G928F using Tapatalk

zizon65 said:
Use latest package disabler for preventing apps to awake the phone or updated through Google play
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
Is that the only way for now?

That's the appropriate way I know
Sent from my SM-G928F using Tapatalk

zizon65 said:
That's the appropriate way I know
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
What I can find in the Play Store is Package Disabler Pro (Samsung). From the description and the screenshots I see you can enable/disable apps/services. I can do that already with Titanium Backup. But I can't disable the Google Play services, I just want to keep them from waking up the device, or keeping it awake while screen is off.

OneTruth said:
What I can find in the Play Store is Package Disabler Pro (Samsung). From the description and the screenshots I see you can enable/disable apps/services. I can do that already with Titanium Backup. But I can't disable the Google Play services, I just want to keep them from waking up the device, or keeping it awake while screen is off.
Click to expand...
Click to collapse
Yes but with Package Disabler Pro for Samsung you can do things, that you can't with TTB, in one word it's more powerful
Sent from my SM-G928F using Tapatalk

zizon65 said:
Yes but with Package Disabler Pro for Samsung you can do things, that you can't with TTB, in one word it's more powerful
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
TB does what it needs to do for me, as I'm not looking for anything beyond what it can do. Just freeze apps/services I don't use and every once in a while a backup. I just need something good that can prevent an app from waking up device, just like the basic functionality we had in Lollipop in the app management section.

zizon65 said:
Yes but with Package Disabler Pro for Samsung you can do things, that you can't with TTB, in one word it's more powerful
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
You're completely missing his point. He doesn't want to disable google play services, he wants to prevent it from waking up the phone.
Package Disabler Pro is more powerful than TB? I hope you're trolling.
OneTruth said:
TB does what it needs to do for me, as I'm not looking for anything beyond what it can do. Just freeze apps/services I don't use and every once in a while a backup. I just need something good that can prevent an app from waking up device, just like the basic functionality we had in Lollipop in the app management section.
Click to expand...
Click to collapse
As far as I can tell, the doze feature is supposed to be in charge of preventing wakelocks and keep your phone from staying awake. So Google probably thought that denying the stay awake permission isn't needed anymore. Tbh, it denying 'stay awake' in app permissions in previous builds on android didn't do much for battery life, at least for me. Some things you could try is cleaning google play services data, and deleting google now if you dont use it.

Bhavpreet said:
You're completely missing his point. He doesn't want to disable google play services, he wants to prevent it from waking up the phone.
Package Disabler Pro is more powerful than TB? I hope you're trolling.
As far as I can tell, the doze feature is supposed to be in charge of preventing wakelocks and keep your phone from staying awake. So Google probably thought that denying the stay awake permission isn't needed anymore. Tbh, it denying 'stay awake' in app permissions in previous builds on android didn't do much for battery life, at least for me. Some things you could try is cleaning google play services data, and deleting google now if you dont use it.
Click to expand...
Click to collapse
You did not understand me either! What I've said is that Package Disabler Pro not only can prevent app from waking up the phone, but can prevent such app from updated by Google play service.
I also maintain that Package Disabler Pro is more powerful than TTB in terms of preventing an app from doing anything even operating in the background.
Sent from my SM-G928F using Tapatalk

@Bhavpreet I think for me it did quite the thing. Before I disabled apps/services I didn't need I saw Google Play Services popping up in the battery stats a lot. Once I hit the switch and didn't allow the service to wake up the phone or keep it awake, it disappeared from the battery stats.
Currently, from what I can see in the battery stats, the play service is running 4 things:
- Google Service Framework
- Google Play Services
- Google Backup Transport
- Google Account Manager
I have the backup to cloud enabled for contacts/notes/etc. Which one of the above is safe to freeze without interfering in that process?
@zizon65 Are you talking about freezing/disabling an app? Or only stopping it from waking up the device, but leaving the service/app intact for when you manually open it?

@OneTruth it could be achieved by using xposed for the module appopsxposed though I only tested it under cm13 on another phone

zizon65 said:
You did not understand me either! What I've said is that Package Disabler Pro not only can prevent app from waking up the phone, but can prevent such app from updated by Google play service.
I also maintain that Package Disabler Pro is more powerful than TTB in terms of preventing an app from doing anything even operating in the background.
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
He does not want to disable it, he just wants to stop it from waking the device. Disabling google play services effectively transforms your device into a dumb phone, whats the point?
OneTruth said:
@Bhavpreet I think for me it did quite the thing. Before I disabled apps/services I didn't need I saw Google Play Services popping up in the battery stats a lot. Once I hit the switch and didn't allow the service to wake up the phone or keep it awake, it disappeared from the battery stats.
Currently, from what I can see in the battery stats, the play service is running 4 things:
- Google Service Framework
- Google Play Services
- Google Backup Transport
- Google Account Manager
I have the backup to cloud enabled for contacts/notes/etc. Which one of the above is safe to freeze without interfering in that process?
@zizon65 Are you talking about freezing/disabling an app? Or only stopping it from waking up the device, but leaving the service/app intact for when you manually open it?
Click to expand...
Click to collapse
You wont be able to remove any of those 4 services without breaking google play services as a whole afaik. I don't even use google for my backup account, but i still have backup transport eating at my battery. Google Services, on average, uses 1-4% of my battery, usually on the lower end. Like I said, clear its data and cache, give it a restart, and see if that helps. I also recommend turning off auto update in the playstore, and deleting google now data and app and reinstalling it.
Last option, and this will definitely work considering you upgraded, factory reset the device.
Also, PDP disables apps, meaning it completely gets rid of them from your device until theyre enabled again, which is not a solution to your problem.

@Bhavpreet How com this was possible in Lollipop without breaking anything? Everything was running perfectly for me, without Google Play Services ever showing up in the battery stats. So I won't be factory resetting. Clearing cache already did that, no result. Will try out @Zenroid solution.

I think this is doing the trick. Will post back with results after the next full charge.
Zenroid said:
@OneTruth it could be achieved by using xposed for the module appopsxposed though I only tested it under cm13 on another phone
Click to expand...
Click to collapse