You know, it’s starting to look like Apple may have been on to something with the whole prohibiting third party apps from running in the background thing. While the iPhone isn’t exactly known for its stellar battery life, Apple could at least be certain that apps weren’t drawing more power than they needed by constantly running in the background. And while iPhone OS 4.0 will support allowing some apps to run while you’re doing other things with your phone, there will be a limited set of APIs for multitasking, which should help keep energy consumption down.

Google Android, on the other hand, lets developers run pretty much willy nilly. The up side is that users can quickly switch between any running application. The down side, apparently, is that there are no real limitations keeping apps from constantly running in the background, using your phone’s radio and other hardware, and running down your battery.

Speaking at an event this week, Google co-founder Larry Page basically said that Android phone should be able to get at least all-day battery life. And if that’s not happening, Page blames third party apps that are running constantly in the background.

The answer is basically to develop apps that do a better job of managing how they use the radio transmitter and receiver. But it doesn’t sound like Google is planning to make anyone do that anytime soon.

via Android Community

Brad Linder

Brad Linder is editor of Liliputing and Mobiputing.He's been tinkering with mobile tech for decades and writing about it since...

4 replies on “Google: Third party apps responsible for crappy Android battery life”

  1. Google has given conferences on maximizing battery life for Android. Whether or not developers follow their guidelines is another case. However, like any “computer” device users need to be aware of the apps they use and how they affect the system as a whole and act accordingly.

    Personally I always prefer choice over no-choice.

  2. If Google would release a profiling app like powertop, except integrated in to the system so that it would warn you if a program's resource consumption goes above certain thresholds, then the users can fix their own problem by using another program. Ideally this will get reflected in market ratings (“great app but kills my batt. uninst”)

Comments are closed.