Battery Drain *after* using location

Italianblend

macrumors 68000
Original poster
Mar 21, 2011
1,781
231
Fatima
Hi,

(Yes, I know, location services drain your battery more, but this happens after I'm done using location).

I have been using the mapmyride app to keep track of my running and biking. The app uses location services.

I have found that after a workout, even after I have ended the workout on the app, I will get a fast battery drain throughout the day. It's as if the location services are still working, even though the app doesn't need them.

I usually reboot the phone and the drain goes away.

This is unfortunate; I don't mind using location services when I'm doing a workout, but why does the phone continue to use location after I'm done with it? Is this a common issue? (4S)
 

nparmelee

macrumors 6502
Jan 23, 2008
296
0
We've seen this with Map My Ride as well and now make sure to completely close it from the recent apps as well. Even though you aren't in an active ride, it still is tracking your location.
 

iceterminal

macrumors 68000
May 25, 2008
1,868
27
Dallas Tx.
It sounds as if the app is still running in the background and using up the juice even though its not active.
Next time after you're finished with your ride, make sure you go into "multitasking" and close it completely. Then see if your battery responds differently.
 

zazazew

macrumors newbie
Jun 23, 2015
1
0
Here's a handy tip. Under settings in the App you can log off. It's kind of hidden in the app for some unknown reason. It will stop battery drain. It's a pain having to login before each work out but a dead battery is more of a pain.
 

C DM

macrumors Sandy Bridge
Oct 17, 2011
47,537
16,037
Here's a handy tip. Under settings in the App you can log off. It's kind of hidden in the app for some unknown reason. It will stop battery drain. It's a pain having to login before each work out but a dead battery is more of a pain.
Seems like just closing the app would be simpler. But then again, a lot of this was probably changed over the past 3 years (since the thread was created and updated last), so none of this might really be an issue anymore.