Anand's Google Nexus One Review
by Anand Lal Shimpi on April 3, 2010 3:40 AM EST- Posted in
- Smartphones
- Mobile
Performance: Faster but Choppier
Much like the display, the Nexus’ performance can be frustrating at times. First, the bad. Switching between pages on the home screen and scrolling through applications is downright choppy. The scrolling process isn’t slow, but the animation isn’t smooth - which makes the phone feel slower than it is. It’s a framerate issue that’s been present on every Android device I’ve used (for the life of me I can’t remember whether or not it was present on the Motorola Droid). It varies depending on the app as well. Scrolling through contacts is perfectly smooth, scrolling through Facebook isn’t. I doubt it’s a hardware issue but rather a software optimization/driver problem. Why it hasn’t been fixed by now is anyone’s guess.
Another inexplicably slow part of the Android experience involves getting the virtual keyboard to appear. The keyboard appears whenever you tap in a text input box. Doing so upon first entering an application (e.g. the SMS app) usually takes several taps before it’ll actually respond. It’s frustrating beyond belief and inexcusable given the horsepower of the Snapdragon SoC in the Nexus One. Again, this just seems to be a software optimization issue rather than an inherent platform limitation.
Now the good news. When launching and interacting with an app the Nexus One feels lightning quick, going back to the iPhone 3GS afterwards feels much slower. Applications respond with a sense of urgency that no other smartphone I’ve used can offer. This is a pure clockspeed thing thanks to the 1GHz Snapdragon from Qualcomm.
| Applications Processor Performance | |||||
|
Apple iPhone 3GS (ARM Cortex A8)
|
Google Nexus One (Qualcomm Snapdragon QSD8250)
|
Advantage Nexus One | |||
| Load www.anandtech.com | 6.9 seconds | 6.7 seconds | 3.0% | ||
| Load www.digg.com | 12.5 seconds | 9.0 seconds | 38.9% | ||
| Load www.arstechnica.com | 12.1 seconds | 10.8 seconds | 12.0% | ||
| Load www.engadget.com | 17.7 seconds | 13.3 seconds | 33.1% | ||
| Load www.gizmodo.com | 20.8 seconds | 13.7 seconds | 51.8% | ||
| Load www.techreport.com | 6.2 seconds | 5.0 seconds | 24.0% | ||
| Launch Web Browser | 0.7 seconds | 0.7 seconds | 0.0% | ||
| Launch Email App | 0.7 seconds | 0.7 seconds | 0.0% | ||
| Launch Maps App | 5.0 seconds | 2.0 seconds | 150% | ||
| Launch Camera App | 2.8 seconds | 2.0 seconds | 40.0% | ||
Loading web pages proved to be anywhere from 3 to over 50% faster than the iPhone 3GS. Launching simple apps didn't move any quicker on the Nexus One, but firing up the Maps and Camera apps (and waiting for them to be usable) was much faster on the Nexus One. The more processor intensive the task, the more the Nexus One can flex its muscle.
Those applications that spawn other apps (e.g. clicking on a Google Maps link in the browser and having it spawn the Maps app) also do so very quickly. If it weren’t for frame rate issues, the Nexus One would be perfect from a performance standpoint.
It’s weird, the flexibility that Android offers is very PC like. And by that, I mean that the platform really does feel like a condensed version of Windows or Linux running in a smartphone. Unfortunately, the weird quirks also seem to come with the package. In fact, I’d say Android really does feel like a more modern version of what Windows Mobile used to be rather than an iPhone, webOS or Windows Phone 7 competitor.
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