Smartphone (and tablet) battery scorekeeping

After reviewing dozens of smartphones and a few not-so-smart ones, I’ve settled on a couple of standard battery tests. To see how long the device will hang on in a best-case scenario, I’ll set it to check a couple of e-mail accounts, Facebook and Twitter (with WiFi and Bluetooth on but not connected), then let it sit on a desk and see what percent of its battery is left after 24 hours. To subject it to a far-less-forgiving trial, I will then play streaming audio through the Pandora app (with the same wireless settings and background apps active) and force the screen set to stay illuminated full-time.

I’ll note these figures in individual reviews, but as they pile up it gets harder to check back to see how a phone compares to its cohorts. That’s where this post comes in: It lists battery-life results from prior reviews and some post-publication tests, and I’ll update it each time I review a new phone. The same goes for tablet battery data, which you can see after the jump.

Keep in mind a few caveats: In some cases, especially with the oldest reviews, I may have departed slightly from the testing routines described above. Some of these figures are also approximations, on account of my not having kept whatever notes had exact times. And you could be looking at the occasional fluke result here.

Apple iPhone 4, AT&T: 95%, 6:21

Apple iPhone 4, Verizon: 93%, 6:20

Apple iPhone 5, Verizon (LTE): 85%, 7:44

Google Nexus S, T-Mobile: 47%, 7:22

HTC 8XT, Sprint (LTE): 33%, 4:34. ( also tests talk time; this one ran 10:32.)

HTC Evo 4G LTE, Sprint (3G only): 85%, 8:26

HTC Evo Shift, Sprint (WiMax): 66%, 77% with WiMax off

HTC First, AT&T (LTE): 65%, 7:07

HTC Inspire, AT&T: 88%

HTC ThunderBolt, Verizon (LTE): 57%, 4:20

Kyocera Hydro Edge, Boost: 70%, 4:52. 9:14 talk time.

LG Nexus 4, T-Mobile: 54%, 5:03

LG Nitro HD, AT&T (LTE): 64%, 4:31

LG Optimus F3, T-Mobile (LTE): 91%, but service on loaner model’s SIM was shut off before I could finish a Web-radio test. 14:30 talk time.

LG Optimus F6, T-Mobile (LTE): 91%, 10:38, 15:03 talk time.

Motorola Droid 2, Verizon: 80%, “six and a half hours”

Motorola Droid Bionic, Verizon (LTE): 70%, 4:45

Motorola Moto X, Republic Wireless (Sprint LTE): 60% (78% on WiFi), 10:53

Motorola Nexus 6, T-Mobile (LTE): 79%, 7:48

NEC Terrain, AT&T (LTE): 68%, 5:34. 9:49 talk time.

Nokia Lumia 520, AT&T: 89%, 7:16, 11:00 talk time

Nokia Lumia 900, AT&T (LTE): 71%, 4:45 (this Web-radio test was done with the Slacker Radio app, since there was no Pandora app for Windows Phone 7; in a second try, it only lasted 4:05)

Nokia Lumia 1020, AT&T (LTE): 88%, 6:29

Samsung Ativ S Neo, Sprint (LTE): 92%, 8:58. 12:52 talk time.

Samsung Epic 4G, Sprint (WiMax): 74%; with WiMax off, 73%, “slightly less than five hours”

Samsung Galaxy Nexus, Verizon (LTE): With WiFi on, ran out in just under 11 hours, allowed 3:56 of Pandora playback; with WiFi off, 59%, 4:04

Samsung Galaxy Note, AT&T (LTE): 37%, 6:14 (I don’t know how that would be possible on a screen with a 5.3-in. screen, but there you have it)

Samsung Galaxy Note II, AT&T (LTE): 82%, 10:19

Samsung Galaxy S, T-Mobile: 88%

Samsung Galaxy S II, AT&T: 73%, 7:05

Samsung Galaxy S III, T-Mobile: 83%, 6:37

Samsung Galaxy S 4, Sprint: 78%, 7:24

Samsung Galaxy S7, Verizon: 70%, 11:25

Continue reading

How I test smartphone battery life

Back when most people used mobile phones to talk–because any sort of sustained online use would be too painful–it was obvious how you should test their battery life: You’d want to know how long you could carry on a conversation.

So as a reviewer, I would have to stage a talk-time test, preferably without actually speaking for four or five hours at a stretch. For a while, I would call my desk phone at the Post with a review phone, then place the phone on hold and wait for its battery to run down. (I had to take the bus home from work a few times to avoid having the call drop on my way into the nearest Metro station.) Then I switched to a slightly more elaborate setup at home: As you can see in the photo at right, I’d tune a radio to WAMU, call my home line and place the phone in front of the radio’s speaker, where it would have uninterrupted hours of human speech to listen to and relay to the home line.

But once mobile Web browsing became something you might enjoy doing, I had to incorporate that into my evaluation. As I recall, my tests on the first iPhone included setting its browser to either the scoreboard page at Major League Baseball’s site or the Post’s home page, both of which refreshed automatically every minute or so.

Once I realized the appeal of on-the-go Web-radio listening and recognized how it required more data transfer by a smartphone, I decided I needed to test that as well. So I now start up the Pandora app–which has the advantages of being available for most major mobile platforms and of offering an “Auto-Lock” option to keep the screen illuminated for a worst-case test–and see how long it takes for a phone to run down.

Another realization came after I’d spent enough time with smartphones with a habit of fetching data in the background (such as my own Android model): Not all phones have the same standby time. For example, I discovered that while an iPhone 4 would have more than 90 percent of a charge remaining after 24 hours sitting on a desk, one Android model had less than half left.

When deadlines permit, I now conduct a standby test too, as you can see in today’s writeup of AT&T’s version of the Samsung Galaxy S II and Verizon’s Motorola Droid Bionic. (Both showed about 70 percent left on their battery gauges.) Between that and the Web-radio test, I think I have a good handle on a phone’s best- and worst-case performance in most contexts.

But not all. Using GPS for turn-by-turn navigation always runs it down quickly–if your car doesn’t have a USB port in the dash to charge the phone, buy a cheap, generic USB adapter and stash it in the glove box with a spare USB cable–and so does sharing its Internet connection over WiFi tethering. Taking a phone to a bandwidth-starved environment like CES, where it’s constantly hunting for a signal, kills its battery too.

What sort of battery-life tests have you found most useful? Which ones should I incorporate into my own research?