Anand's Google Nexus One Review
by Anand Lal Shimpi on April 3, 2010 3:40 AM EST- Posted in
- Smartphones
- Mobile
Battery Life: Unimpressive
The iPhone doesn't have a very long lasting battery. Before my iPhone I was a Blackberry user; my battery lasted for days. With the iPhone, especially while I'm traveling, I have to keep charging it throughout the day or risk a completely dead phone by 6PM. The Nexus One is worse.
To test battery life I ran the same suite of battery life tests I have been using in our smartphone reviews for the past couple of years:
The wireless web browsing test uses the 3G or WiFi connection to browse a series of 20 web pages varying in size, spending 20 seconds on each page (I timed how long it takes me to read a page on Digg and came up with 36 seconds; I standardized on 20 seconds for the test to make things a little more stressful). The test continues to loop until the phone dies. This test is designed to simulate a relatively heavy, but realistic data load on the phone. We're stressing the modem/WiFi radio, SoC, memory and display subsystems here. This should also be the sort of battery life you get when you are using any apps that use data (but not 3D acceleration). The display brightness was set to roughly 30% on the Nexus One and 50% on the iPhone.
The H.264 movie playback test loops a 480 x 208 632Kbps re-encode of Slumdog Millionaire until the phone dies. The majority of the device is idle during this test stressing the memory subsystem, video decoder, audio decoder and display more than anything else. The display brightness was set to roughly 30% on the Nexus One and 50% on the iPhone.
The talk time test measures battery life over the course of a conversation between the phone being tested and another phone. The conversation is actually an MP3 playlist on repeat played into the microphone of the phone being tested. The display was disabled.
| Battery Life | |||||
Apple iPhone 3G |
Apple iPhone 3GS |
Google Nexus One | |||
| Wireless Web Browsing (3G) | 4.50 hours | 4.82 hours | 3.77 hours | ||
| Wireless Web Browsing (WiFi) | 6.67 hours | 8.83 hours | 5.62 hours | ||
| H.264 Movie Playback | 4.70 hours | 9.65 hours | 6.67 hours | ||
| 3G Talk Time | 4.82 hours | 4.82 hours | 4.67 hours | ||
Despite having a larger 1400 mAh battery, the Nexus one proved to have worse battery life across the board than the iPhone 3GS both in my tests and in my day to day usage. The only redeeming quality here is that you can easily swap out spare batteries, while the iPhone requires a 3rd party external battery if you need more juice on the go.
Talk time is lower than on the iPhone 3GS. Using the 3G data or WiFi connections both result in the phone dying faster than the 3GS. Even H.264 video playback discharges the Nexus One's battery faster.
I'm not sure if it's the AMOLED display, the Snapdragon SoC or just inefficiencies in Android but the battery life story isn't a good one.
Android does have a power consumption page that shows what percentage of battery drain can be attributed to various components in the phone (e.g. display, OS, specific apps, idle time). It’s not granular enough for my needs but it’s a great way of showing users, at a high level, what’s killing the battery.
Facebook
Twitter
RSS
95 Comments
View All Comments
coolVariable - Saturday, April 10, 2010 - link
Oh, STFU you fanboy.1. No calendar sync. Buggy Contact sync (e.g. contact pics, birthdays, ...). Buggy e-mail sync (just stops randomly). STFU since you have no clue what you are talking about.
3. A phone that can't even make calls. GREAT!!!! I don't fvcking care what the reason for the problem is. A $600 phone should be able to make a fvcking phone call!!!!!!
4. Love your little walled garden? Why don't you get an Apple phone if you are soooooo in love with a company locking down the functionality of your phone???????? Anand bad-mouthes Apple for its walled garden and ignores this "walled garden"???
5. Walled garden! Walled garden! Walled garden! Walled garden!
All of the above are pretty big problems with android per se and the Nexus One specifically!
It's pathetic that they weren't even mentioned during this review.
Not to mention the myriad of other (often cosmetic) problems and bugs with android (e.g. contact sort, etc).
And a tech-savy reviewer would have also mentioned the hypocrisy that you need to "jailbreak" android to do a lot of things. While that is fine, it pretty hypocritical that you can't "un-jailbreak" the Nexus One for a warranty exchange (something that is pretty easy to do with the iphone).
ruzveh - Sunday, April 11, 2010 - link
Anand nice article and m also looking fwd to buy one phone in near future from GoogleFrom my point of view is that 1GHz processor with 65nm is draining the battery life. Imagine if u insert 1GHz processor with 32nm (todays std) or even less will boost ur battery life almost double. I dont understand so called this chip company why not jumping onto 32nm bandwagon or to somewhat 25nm or even less?
i just feel these cos r wasting so called resources and time for money / profits. Dont they knw resources r limited and so purchasing power.
Thats secondary thing. Ohh what? r u thing i forgot to mention primary issue? lolz
Well its obvious.. Innovation in Battery power. What i hate in mobiles are speed and battery life for which i m ending up using my cell ph for only calls & ofcourse sms since past 8yrs 6630 and not willing to change untill they come up with good phones..
coming back to battery life i really dont understand why these cos r not doing something in batter life when there is lot of room for improvement in it like todays model feature only 1500mah battery power wheres a small pencil cell can go all the upto 3000mah or even more. We definitely want to see double the capacity then what they r featuring today.. Anand can u clear me on this prospect?
I am v much sure if v give proper attention in this area we can do wonders. Comon someone has to do something sooner or the later...
7.saturnine - Wednesday, April 14, 2010 - link
I don't understand the trend of putting as few physical buttons on a device as possible. How do you skip or pause music when the device is in your pocket? Pull it out, unlock the screen, find the music app & press the button? That is ridiculous.On my HTC Touch (WinMo6) it has hardly any buttons either, but at least one programmable physical button (that I have programmed to open the camera from any app I am in) & a directional pad/enter button. Sometimes I just like using the directional pad to go through menus & select something rather than moving my thumb all the way up the screen. Yes that sounds incredibly lazy, but aren't these devices all about ease of use, simplicity & speed? Programmable hardware buttons do just that. They are focusing too much on the aspect of a touch screen.
Affectionate-Bed-980 - Thursday, April 15, 2010 - link
This seems to be a forgotten thing. I spent 2 hrs playing around writing probably pages worth of notes just to test it out on Android.You say the iPhone lackED it? I have an iPod Touch 1G and I guess I'm used to multitouch by now, but how long did it take for Apple to add it? I notice how ridiculously fast I can type on it and not skip words/keys. On Android, it's a totally different thing.
A few tips from me as I've investigated this for a long time and I've made cries out on Android forums with very little sympathy:
1) HTC's IME keyboard that is modded on XDA is a LOT better. The developer tried to implement a little pseudo multitouch so it is more used to you pressing the next key before releasing the previous. This is a HUGE issue with the space bar and if you use the stock android keyboard, you're going to be skipping words like mad if you type too fast.
2) Smart Keyboard Pro has multitouch. It also features a debug mode that you can look at your touch points. It definitely picks up multitouch flawlessly. Is it as good as the iPhone keyboard? Somehow I was still typing faster on my iPod than on my Android phone with Smart Keyboard Pro.
However, with the mods the modders have made on the HTC IME Keyboard, I've decided to stick with it. It's getting better and it's handling multitouch somewhat even though it's not a true multitouch implementation.
But you're right. It's night and day without multitouch. For people who haven't used the iPhone enough, they fail to appreciate the keyboard. Most people just go "Oh I type fine on my Nexus One. I type pretty fast." Obviously you can't type THAT fast if it lacks multitouch. Maybe they should look at what "fast" means on the iPhone :D
rossmandor - Monday, August 30, 2021 - link
nice one