Linked by Kroc Camen on Thu 30th Sep 2010 12:12 UTC
Permalink for comment 443308
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-06-29
True, but the operating system can go very far in determining battery life. My Android phone, the Motorola Cliq, has a friggin' huge battery but barely makes it through a day of light browsing once or twice an hour, and a couple of phone calls and texts. Why? It has a low power, efficient processor, and an energy efficient screen so those aren't the culprits. The cell and WiFi radios are no different than any other Motorola smartphone when it comes to power draw, so it's not them either.
No, I'll tell you why: Because it's running the older, less efficient version 1.5 of the OS, and the MotoBlur UI that runs on top of the OS is constantly polling data, even when you set the phone in "Battery Saver" mode. This device is a clear case of the software, not the hardware, running the battery down. I'm looking forward to the 2.1 update mostly for the gain in battery life.