You could say that the Galaxy Nexus is the most anticipated Android device of 2011. It’s what Android enthusiasts were hoping the Nexus S to be when dual core technology started cropping up in mid-2010. The Galaxy Nexus was already out towards the end of 2011 in the West, but here in Asia, we are only getting a glimpse of this device now.
As an Android Enthusiast, I have high expectations of the Galaxy Nexus. After all, it is a Pure Google device that’s considered by many to run bleeding edge Android OS. It is Android at its best. However, after spending 5 days with the Galaxy Nexus, it seems to me that either Android hasn’t exactly arrived, or I’ve had too high an expectation on the Nexus. The Galaxy Nexus experience left me wanting and at times – frustrated.
If you’ve haven’t read my previous article on hardware acceleration, you wouldn’t have a clue where I’m coming from, but if you have, then I’m sure you’ll agree with some of the points I’ve mentioned below. Perhaps I have been sold the idea that Ice Cream Sandwich has taken the Android OS to match the UI smoothness of iOS. Frankly, it hasn’t, but it’s close. Very close.
“Don’t get me wrong.”
I love ICS, and I definitely love Android, but there are some parts of ICS which I felt that Google could have done better. Even stranger, was my experience using Touchwiz 3.0 and HTC Sense 3.0 made the experience of the Android 4.0 Pure Google interface disappointing in certain areas. I definitely loved the look of ICS, but not the way certain things worked. If only I could have Touchwiz/HTC Sense functions with an ICS look.
There are tonnes of Galaxy Nexus reviews online, and you certainly do not need me to regurgitate what they have said. So, I’m just gonna cut all the sugar coated words and put the Galaxy Nexus under the knife. This is one review without bias.
Unlike the International version of the Galaxy S2, the Galaxy Nexus feels sturdier in the hands. It looked like the marriage between HTC’s aluminium unibody and Samsung’s plastic surgery. The thought of your phone breaking when it hits the floor dissipates from the mind and I am sure this is one phone that can handle a drop test without breaking. It fits in the pocket nicely and there are no concerns about inferior built quality. This does not feel ‘cheap’, unlike previous Samsung Phones – which is a good thing.
The power button and volume rocker feels too soft. It lacks a ‘clicky’ feel which makes me wonder if they could have made it harder like the power button on an iPhone. There are several incidences where I’ve taken the Nexus out of my pocket to realise that the screen was already turned on. Harder buttons would have prevented this.
The curved display is wonderful. When placed faced down, the screen never touches the table, and this prevents scratches on your display. The 3.5mm jack is located on the bottom of the phone and this is slightly awkward for me.
The position of the camera right in the middle of the phone’s back will mean more unnecessary scratches on the camera lens. A simple phone case should solve this though. The battery cover is similar to that on the Galaxy S2. I thought it would have been a nice touch if this was Kevlar coated instead as it didn’t provided enough grip as I thought it would. Still any sensible person will likely get a case to solve this.
The position of the speaker is horrible and contributes to the soft ringtone volume of the phone (especially when the phone is placed with the speakers facing down on a table). I’ve tested this against other Android devices and the ringtone volume is perhaps about 50% the volume of other devices. This makes missed calls and missed messages a norm with this phone.
I love the Android 4.0 purplish Tron-like look. It’s futuristic, and modern, but not without some areas of disappointment. Android 4.0 boasts hardware acceleration – which means the on screen components are generated by the GPU and is unlike previous Android versions which draws the components from the Processor. This ultimately means less processor hogging – and ultimately smoother graphics and superior battery life.
The transition between homescreens is without a doubt, the smoothest I’ve seen on an Android device. However, I did notice minute lags when opening the app drawer and while scrolling through the widget drawer. To the untrained eye, this may not be problem, but this frankly means that hardware acceleration did not resolve all the laggy problems Android faced. Ultimately, this may mean that Android lovers will have to live with such ‘minute’ lags for as long as Android exists.
Android 4.0 is Google’s attempt at simplicity. However, I felt that Google made a design flaw with the OS. They should have kept the Menu button, instead of the back button. Currently, the back button minimises the current app to the background. I honestly preferred this to be a menu button instead. The home button should have done what the back button is currently doing.
Application sharing is one of the strong points of Android. With a normal Android phone, pressing the menu button (while you’re in a browser or photo gallery) launches the sharing functions and this lets you share your content on Facebook or Twitter. With Android 4.0, sharing gets a little bit tricky. For example, in the Browser, the sharing function is located in the settings – which unfortunately, is located on the top right of the screen. So much for one handed web browsing…
Also, this ‘settings’ button (the one that looks like 3 little bullets lined up like a colon) isn’t executed right. Occasionally, this button is on the top, and at other times, it appears on the bottom. The lack of consistency where this button is placed makes it hard to navigate – especially when the menu button has been given the boot. I find this frustrating whenever I attempted to access the settings and sharing functions.
The multitasking button is a big welcome in an app saturated world. However, at times I wished it to be as simple as TouchWiz or HTC Sense where I could just kill all the apps running in the background with one simple touch. The fact that the back button pushes apps to the background seems to make it necessary for a ‘one touch, kill all apps’ feature within the multitasking page, instead of killing apps one by one, which proves to be a pain, when you have 10-15 apps running at the same time. Although Android 4.0 proves to be running competently with that many apps in the background, it would be nice to have something that tidies up the system quickly.
The Auto Focus function on the Galaxy Nexus is acceptable. I find the ability to go really closed-up on macro shots to be an even greater deal. On a usual Android phone, macro shots usually allows you to be around 15-20cm away from the photo subject, but the Galaxy Nexus allows you to come up to around 7-9cm away from the photo subject; allowing really nice and tight close-ups unavailable on other devices.
Photography on the Galaxy Nexus turns out to be more ‘mellow’ – with less contrast between darker and brighter areas. Shots from the Nexus are comparable with other Android devices, though the macro capabilities really make the Nexus camera shine.
The Super Amoled screen on the Galaxy Nexus works well with the revamped ICS look. Battery life is great on the Galaxy Nexus as well, not to mention proper data management tracking capabilities built straight in the OS.
Calls are on par with other Android phone, although I find that the speaker/speakerphone to be a bit lower in volume. I guess the position of the speaker grill might be a problem. The browser is smooth and the auto sync with your Chrome browser makes saving bookmarks a lovable experience. Although the browser is smooth, it’s very mechanical. When scrolling, it does scroll smooth, but it comes to a screeching halt – unlike the browser on the SGS2 which flows smoothly until it slows and comes to a stop.
The Galaxy Nexus comes with a PowerVR SGX 540 graphics processor – which performs very well on the homescreens even in the presence of a live wallpaper. The minute lag in the app drawer and widget drawer is there, but is invisible to the untrained eye.
When subjected to intensive 3D graphics and gaming, the PowerVR SGX 540 didn’t really perform as expected. I personally use Wind-Up Knight as my own benchmark for intensive 3D gaming, and on the higher levels of the game, the Nexus wasn’t smooth. I am not sure if the team at Robot Invader incorporated the right drivers, (it could be a texture problem) but the GPU could not keep up with the game. It made me wonder if this could be another area where GPU fragmentation could happen.
Third party applications are also not as smooth as I hoped them to be. Facebook for Android was one of the apps that had minute lags that disrupted the smooth ICS experience. It’s not a big deal, but it’s a pebble in the shoe that has to be dealt with.
There are many things I love about the Galaxy Nexus and Android 4.0. The new user interface is a joy to behold, apart from several quirks here and there. It’s polished, and is what Android is meant to be – fast, smooth and friendly. However, I can’t help but feel that unlike WebOS and iOS, Android 4.0 is still going through growing pains. It’s certainly one of the best devices out there, although I felt that it’s still living under the enormous shadow of the SGS2. Pure Google has been an eye opener, and strangely, it renewed my love for TouchWiz and HTC Sense. Although gimmicky, manufacturer UI does not seem to be a bad thing right now, provided it increases the functionality of Android, instead of hogging ram resources.
The Galaxy Nexus is brilliant for any newcomers to Android, but as a person who has handled close to 10 Android devices – it left me wanting. If you can live without TouchWiz and Sense, and some of the quirks I’ve highlighted in this article, this device is for you.
For me, I felt that the Galaxy Nexus (surprisingly) wasn’t my cup of tea. As I thought more about what kind of Android 4.0 device would appeal to me better, I felt it was something akin to ICS look and feel + TouchWiz functionality. Now, if only Samsung can keep me on the bleeding Android edge, on non-Nexus devices, I will be a happy man. Based on the recent UI look and feel guide released by Google, this might be possible soon.
HSPA+ 21Mbps/HSUPA 5.76Mbps 850/900/1700/1900/2100
1.2 GHz Dual Core Processor
4.65” 1280X720 HD Super AMOLED
5 MP AF with LED Flash
Recording 1080p Full HD Video@30fps
3.5mm Ear Jack
Android Market™, Gmail™, Google Earth™, YouTube™, Movie Studio
Google Maps™ 5.0 with 3D maps and turn-by-turn navigation
Syncing with Google Calendar™, Google+ app
Bluetooth® technology v 3.0
Wi-Fi 802.11 a/b/g/n
Accelerometer, Compass, Gyro, Light, Proximity, Barometer
1GB(RAM) + 16GB Internal memory
135.5 x 67.94 x 8.94mm, 135g
Standard battery, Li-on 1,750 mAh
Like this post? Share it!
Two things have made the Galaxy Nexus better for me.
First, the official 2000 mAh battery all the way from Korea, which gives it a great weighty hand feel while at the same time raising it up off of the speaker and camera lens.
And second, for the low volume of the speaker I installed Volume+ to raise the volume a few dB’s and it makes a world of difference.
Thanks for posting the app link.
Not sure why you’re saying “Currently, the back button minimises the current app to the background” it’s only true if there’s nowhere left in the app to go back to. The home button minimizes apps regardless of where you are or what menu your in. The back button takes you back one screen/menu up to and including exiting the app.
I will agree with you on the speaker location though, not ideal but not a huge issue either.
yes, the back button does take you one step back in the app. However, when going back to the previous app, it minimises the app, instead of the usual exiting on other devices. This proves to be an annoyance when you’ve gathered up to 20 apps running in the background, and the multitasking button will have you sliding to close apps one by one.
It’s a small issue, but it’s annoying without a one touch, close all apps feature.
The back button is developer implemented – so most games will exit, while many apps will, some won’t. But my previous point about task killers remains. Don’t use them, unless you’re pre-Froyo.
Why do you care about what’s in the recent-apps list so much, Randy?
This is a very biased and uninformed article. He complains about UI lag that’s imperceptible. If the author would do any research he would discovery that Android always had a form of hardware acceleration on the UI instead of claiming that ICS is the first version to have it.
The author had lost all credibility IMO when he complained that there wasn’t a kill all apps task manager. It amazes me that people still insist on task managers for Android.
Also, the entire section the author went on about the back button and the menu button clearly demonstrated that he has little or no experience with Android at alland should not be writing for an Android blog.
“so much for one handed browsing”. Seriously? If this author doesn’t know about “Quick Controls” in the browser in ICS then how much of a real authority is he on Android?
I could keep ripping this article apart but frankly I don’t have all night, cause I could keep going on and on with this guy’s nonsense.
Yep – ICS introduced a few more elements that can be hardware accelerated, but it’s always been there. There’s been huge discussions on this subject since November – author appears unaware of them.
And task killers? Since Froyo, no-one has needed them. They /decrease/ system performance. The only reason you want to kill a task is if it’s hung and that’s happened about twice to me in over two years of Android.
Although I happen to agree about the back button. It’s had its day. It’s a confusing concept because it’s so inconsistently implemented. Not Android’s fault, but still.
If you want to complain about ICS, complain that it /still/ doesn’t have a solution for restoring app data. It’s 2012 and if you lose/break your phone, your replacement device will have lost all game saves. Where’s the incentive to 3-star an Angry Birds level if you know you’ll lose your progress when you buy/get a new phone??
dear scaine, this is a review unit, and i am not able to root it nor, do advanced stuff on it. Hence, the argument on app data restoration, would definitely not be in the article.
I’m not advocating task killers. Unlike most users, i like keeping my ram free (it’s just me). It’s just nice that there is a built in app killer (like the one on Sense and Touchwiz) which clears all the apps in one shot. With the Nexus, you will have to manually swipe to kill all of the apps.
It’s just annoying – also because the way the back button minimises apps and not exits them.
Seems you missed both my points, Randy :
1. You don’t need a task killer. By complaining about the lack of one, you most certainly ARE advocating their use. After Froyo, task killers were proven to decrease performance. Keep your RAM free? You mess up Android’s in built cache by doing so, causing more stutter and performance issues. (oh, and swiping the ICS task list, doesn’t necessarily kill the app, in some cases, it just removes it from view)
2. My whole point on backups is that you shouldn’t HAVE to root a phone to get a back up of it. So, if you want to complain about something, complain that ICS doesn’t have a back up solution. At all. None. You must either root your phone, or lose your app data. Yes, Google will back up your apps – but so what? You’ve lost your progress/settings/personalisations.
The article needs research. Your answers to these comments don’t inspire much confidence that will happen in future.
Scaine, Yes i agree with your assessment that froyo has made task killers irrelevant, but i must say, that there are exceptions to the case.
I have seen Optimus 2x (2 buddies of mine own them) and one is running GB and the other Froyo, and both are forced to use task killers. They are ordinary users, and not Android enthusiasts like you and I. Without task killers, a simple 10 second sms takes them about 2 minutes to complete, especially when app switching. So despite task killers being ‘unnecessary’ it’s not always the case. Life is intolerable without task killers – in their case.
I also own a HTC Sensation XE. And I love my dungeon defenders game. And for your information – i can’t have a decent game on it because the device comes with 768 mb ram and it keeps hanging up after the 3rd wave or so. There are no fixed for this yet, as this is a ram problem. It just crashes as it pleases.
The only device that has passed with flying colours is the SGS2 – only because it comes with 1GB of ram – which makes it more than enough to multitask (in my case).
The thing is this – not everyone uses their devices the way that you do. Mainstream users will max their phones with apps – ram guzzlers like go locker, go launcher, widgets and weather widgets, etc. Not all devices can tolerate such punishment.
The Nexus has always been a ‘developer device’. This may be true when the nexus one was out, but it can’t be said of the industry now. Although the Galaxy Nexus comes with 1GB of ram, the performance is good – and i must say a task killer is unnecessary for it. But being a person who comes from a background of having task killers, I might be killing apps out of habit.
The problem is that, previous devices that i have used including the Legend, the Captivate, O2X, Galaxy Tab, all needed a form of task killing while running froyo.
So yes, in theory, i agree that task killers are unnecessary, but it also depends on the hardware specs and user behaviour. In my opinion, task killers were part and parcel of android until only quite recently (about a year back). It was only when the SGS2 with 1gb came out and performance was very impressive that task killers start to fade in existence.
In terms of backup, i believe mybackup pro does the job? no?
Interesting, but I had a shed of apps on my now-aging Nexus-One and didn’t need a task killer. I guess you’ve been a bit unlucky there (or your friends/colleagues have).
Regarding MyBackup Pro, it’s not going to back up any settings, only the application entry itself. Sure, it will do photos and music (and the app entries, as I say), but if you spend 50 hours 3-starring every Angry Birds level, you can kiss it goodbye when you get a new phone – you’ll be back at the start. I feel that this is an unacceptable oversight from Google.
Yes, the UI is smoother, despite Android having a history of lag.
The thing is, they got the homescreen right. It’s close to perfect in terms of smoothness, but this doesn’t translate well into the app drawer and widget drawer.
Question is – why?
I am convinced that Google could rectify this, but they haven’t.
And I’m not the only one who noticed this.
I handed the review unit to everyone who wants to see it, and EVERYONE noticed the app drawer lag. And you could see smiles turn to frowns because of that.
It may be a negligible issue to pick on, but it is a concern that despite being stressed again and again, still present despite hardware acceleration.
Oh guys…. you really should have another go at writing this article. Just for this review alone I should be removing you from my feeds!
I’ve been thinking about removing them for a while now. Android Authority is absolutely not that, an authority on Android. So many of their articles are so misinforming, inaccurate and frankly pro-apple sounding that it amazes me. After this article though, I’m taking them off my RSS news feed.
From your feedback, i can assume you guys enjoy the nexus very much.
I can’t say the same on my end. I sincerely tried to like it, but it didn’t impress me as much as i wanted it to.
Randy, I am looking to purchase a new mobile. I’m new to Android. Should I go now for the Nexus or wait until WHEN ? for the S3.? Paul (China)
Recommend you to wait paul.. S3 and HTC One X looks good.
Always test before buying though.
Thank you Randy … I will wait until the end of April to see if there is any firm news on the S3 …