I don’t leave home enough times for Google Maps to rank third on my battery usage list.
That’s what made it so strange when I went through my power settings recently. Maps was near the top, ahead of Gmail and a few other apps I use every day.
I couldn’t figure out why it was taking up that much power when I hadn’t touched it in four days.
The timing was bad too, because I was still struggling with battery life despite the improvements that each Google Pixel upgrade keeps promising.
Then I worked out what was happening, and it was something I’d been ignoring for a very long time.
Google Maps had been working in the background since day one
Even during those weeks when I barely left the house
A few minutes of investigation revealed the obvious cause: Maps running constantly in the background.
I’ve used Google Maps features for decades, but it’s never been an app I spend much time on. I set it up once and open it when I need it.
I knew it did some work in the background, though I never understood how much of the battery that was costing me.
At some point, I had set the app’s location permissions to Allow all the time, as one typically does with a “trusted” Google application, without really thinking about what it meant.
With that permission, Maps doesn’t wait for you to open it before checking where you are.
It pings your location on its own schedule throughout the day, so features like traffic alerts and location history stay up to date, whether you need them at that moment or not.
Each of those checks relies on GPS, Wi-Fi, and mobile network signals to fix your position, and the precise mode I had enabled uses all three for accuracy.
Those radios are power-hungry components in a mobile device, and waking them on a loop drains the battery quietly. You won’t notice it happening, but it’s a significant amount by the end of the day.
To see the damage, open your phone settings, navigate to Apps, and pick Google Maps. Then, tap App battery usage to see how much it has consumed and how much of that came from background activity.
How I fixed it with basically zero effort
Just a few taps, really
The fix lives in the same area. Head to Settings > Apps > Google Maps > Permissions > Location, and switch the setting from Allow all the time to Allow only while using the app.
You can reach the full list of offenders from the other direction. Go to Settings > Location > App location permission, which sorts every app by how much access it has.
Anything under Allowed all the time that you don’t actively use is a candidate for the same change.
I left the Use precise location toggle on. Switching to approximate location would save a little more power, since it skips GPS and uses network signals alone, but I’d rather have the accuracy for the times I open Maps to find somewhere.
I also turned off background data for the app, which stops it from silently downloading map times and updates when I’m not looking at the screen.
That was a second, smaller battery drain that the location change wouldn’t catch on its own.
Why the default tends to be background access
A tradeoff that makes sense for some people
It’s easy for me to complain about changing settings to save battery power, but the access exists for a reason that’s fair enough.
Plenty of Maps features rely on continuous location to work properly, and some people use them every day.
Commute suggestions, proactive traffic alerts, and location history depend on the app knowing where you are without being opened first.
Google now keeps your Maps Timeline off by default and stored on your device, so this isn’t a case of the system quietly switching everything on for you.
The all the time access is usually granted at some point by you, though you probably forgot about tapping the prompt.
Some users depend on these features running day to day, but I’m not one of them. The battery cost doesn’t earn its place for me, since I don’t really need Maps to make my morning commute easier.
I freed up 2GB of RAM by changing one Android setting, and my Pixel’s been flying ever since
The performance boost was worth every trade-off
My battery issues are mostly behind me
The change worked well enough that I started limiting background usage on more apps to squeeze out a bit more life and performance.
When I need Maps, it behaves exactly as it always did, with location kicking in and navigation running fine after I open it.
The only thing I gave up was the background work, which I never benefited from.
So that’s one app off my list, and the battery lasts noticeably longer for it.
What really stuck with me is how long I went without checking, assuming the battery was the problem when it was a setting I’d tapped through years ago.
If your usage stats show an app you barely touch near the top, it’s worth a look before you start blaming the hardware.
