Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have installed Google Latitude and am wondering how much quicker my battery will run flat? I know the way Apple implemented its "mutitasking" framework minimises the impact?

share|improve this question
up vote 7 down vote accepted

Specifically, the Latitude app (and other background location-updating apps) register themselves for location updates "on significant location change".

How the phone knows the location has changed significantly is when the phone does a cell tower handoff. It's moved enough that it's out of range of the tower it was talking to and its service is handed to the next tower. At that time, if any apps are registered for location updates, the phone fires up its GPS, gets its coordinates, and feeds them to those apps. Those apps then get to do a LITTLE work with what they were told.

When iOS 4 came out, I wrote a little app to play with this API. Basically it just sat in the background and recorded lat/lng for every update it got. Between my office and my house (like 10 miles) it got eight or nine sets of coordinates.

That means eight or nine times (call it once a mile or so) that the phone has to fire up the GPS chip, listen for signals from outer space, and do something with them. That obviously takes up more electricity than if it didn't have to do that.

Is it MUCH more? You know what? Not really. I charge my phone when it needs it (rather than, say, nightly), and I didn't notice it needing it more than usual when my little app was running. So my guess is that Latitude won't be a major battery suck. But it'll definitely suck some.

share|improve this answer
+1 for testing and reporting. – msanford Dec 14 '10 at 15:21
Are you sure it actually uses the GPS? I'm pretty sure it uses Cell Tower triangulation only. The changes between updates shift significant both in the foreground and the background, and is too unreliable to actually be GPS. – Jason Salaz Dec 14 '10 at 20:07
@VxJasonxV I got some hits in my test app that were within 10 meters. I believe that kind of resolution is only available via GPS. I wouldn't be surprised if it didn't work to hard to get a GPS lock--you might be inside and out of the running for a good GPS fix. – Dan Ray Dec 15 '10 at 17:00
Ok, your app uses GPS, part of CoreLocation. But... does Google's? – Jason Salaz Dec 15 '10 at 21:02
Oh. Well, I don't know. You can specify the desired horizontal accuracy, so I guess if you asked to be within a kilometer, it might quit before even getting into actual GPS business... – Dan Ray Dec 15 '10 at 21:40

Yes, any app that runs in the background needs some attention from the CPU, and this costs battery power. Further, if the app needs GPS and/or 3G service or other battery-intensive services, then of course the battery will deplete even faster.

But depending on your situation and circumstances, this can be a trade-off that's worth it, especially if you only need to do this for shorter periods of time.

share|improve this answer

Due to the way multitasking is done in iOS 4, Apple tried to implement it in a way to reduce this as much as possible. For example, with the latitude app, it can only poll and post location information at certain intervals.

So, yes, any background app actually working (like GPS or Upload type apps) will use a little more resources than a phone not running them.

But, if one were to run this type of app fully in the background (for example, how some jailbroken apps do), it would be using a significant amount more of power.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.