ASUS Eee Pad Transformer Prime & NVIDIA Tegra 3 Review
by Anand Lal Shimpi on December 1, 2011 1:00 AM ESTThe Dock & Keyboard
Despite what ASUS originally told us when it launched the first Transformer, the Prime does not work with the old dock. Admittedly you wouldn't want to use the sleek new tablet with the clunky old dock, but I'm just not a fan of being used to convey incorrect information.
The new dock matches the Transformer Prime perfectly. The docked Prime isn't as elegant as the Zenbook and I'd argue that the dock does take away from the tablet's beauty, but if you need to hammer out long emails or a big document the dock is a great solution.
The dock's beauty isn't just that it's convenient (it behaves just like a notebook once mated to the tablet) but that it acts as a second battery for the Eee Pad. ASUS has also done the necessary customizations to Honeycomb to appropriately track battery levels in the dock and the tablet. There's also a little animation indicating that the dock is charging the tablet. To the best of my knowledge, the tablet will never be used to charge the dock.
Scrolling is rarely as smooth as I'd like it to be via the dock's trackpad. Many times the gesture just won't register on the trackpad or the trackpad will detect my two fingers but it won't scroll. With the screen inches away I found myself preferring to use the touchscreen for scrolling and stuck to using the dock for typing. You can control pointer speed and cursor style in the OS now, which is a nice addition.
The typing experience itself is great on the dock. The keys are big enough (around 15mm x 14mm) to type quickly on and feedback is good. The keys were a bit taller on the old dock, but as the new model is thinner the keys went on a similar slimming process.
Using the dock on a desk is fine, but use the dock on your lap and you'll have to keep applying a little bit of downward force with your wrists to keep the system from leaning backward. The dock is angled forward so if you're not typing on a flat surface the system might pivot backwards. The correction is simple, you just need to push down with your wrists/palms a bit while you type. I even have to do that a bit on my 11-inch MacBook Air. The difference is the MBA has enough surface area for me to comfortably rest my wrists, the Transformer Prime's dock does not. While I don't notice much fatigue while typing on my MBA, my wrists do feel it when I use the Prime + dock on a couch.
My dock had a connection issue between the Prime and the dock itself, which ASUS insists shouldn't be happening. Tilt the Prime towards you when in the dock and the screen would occasionally go white. It feels like a manufacturing issue, although I'm apparently the only one who has reported it.
Android is still not beefy enough to be a full blown laptop replacement, but the Prime does come with enough apps to at least let you do some basic word processing and spreadsheet work. If you're going to do a lot of typing on your tablet I'd easily recommend the dock, it's the best way to get your thoughts into words on the Prime. Otherwise, the $150 adder just adds bulk and cost to the platform. The Prime is really great to use on its own. If you want an alternative to the dock, ASUS will have its own clone of Apple's iPad smart covers at some point in the coming weeks.
ASUS' five row virtual keyboard is back on the Prime. While it doesn't look as good as the standard Honeycomb keyboard, I do like having the numeric row visible above the rows of letters. Nuance's T9 Trace is still supported by the keyboard (Swype-like continuous text input) although I'm not personally a fan. You can disable Trace as well as revert to the stock Honeycomb keyboard if you'd like.
Facebook
Twitter
RSS
204 Comments
View All Comments
MiSoFine - Thursday, December 1, 2011 - link
my 2 cents...get a Kindle fire. Easier UI for non tech parents & it's still android; cheaper also. Or a Vizio vTab.I got my Mom a Kindle Fire, kids a vTab (they will at least attempt to try to figure it out) & myself a (preordered) Prime.
steven75 - Saturday, December 3, 2011 - link
Considering the complete lack of Android tablet apps, that doesn't seem wise.Enkur - Thursday, December 1, 2011 - link
What is that android app that shows the per core CPU activity in the screenshot above?Lucian Armasu - Thursday, December 1, 2011 - link
Anand, just remember to note, or even test the real world performance when iPad 3 and other high resolution tablets arrive.In your benchmarks they should be showing even faster performance at 720p with the upcoming faster chips, but that might not be the case in the real world. Remember how low FPS the iPhone 4 got with its 4x the resolution over iPhone 3GS, when tested at native resolution?
That should be happening to iPad 3 and the others, too, even if the chips get faster by then. I would wait until at least 2013 to get a 2k resolution tablet, so I won't be that significantly impacted by it.
Lucian Armasu - Thursday, December 1, 2011 - link
Also is there a way to compare the graphics between Tegra 3 and iPad 2 without comparing the benchmark numbers? Like comparing the best graphics on Tegra 3 versus the best one on iPad 2, and notice the differences between them? I really don't think the benchmark numbers tell the whole truth.I think Tegra 3 games may even look/work better than A5 games, thanks to its quad core CPU, too, but I figure you should be able to tell that better than me since you have both.
vision33r - Thursday, December 1, 2011 - link
I disagree, in PC and Console world, the GPU is the determining factor in game graphics and performance.You can take a Core i7 using HD3000 integrated graphics and compare it with a Core i3 with an ATI 4850 and it will spank the Core i7 in gaming performance.
That's what's happening here is the Tegra 3's GPU is underwhelming from a graphics chip maker.
Very few mobile games imo need even dual core, they need the proper graphics acceleration and that's where Android fragmentation has hurt game development.
They have to code games for the lowest common denominator instead of optimizing games for Tegra.
metafor - Thursday, December 1, 2011 - link
That doesn't necessarily translate to the mobile world. On the desktop side, CPU's have gotten so fast that just about any task a game can throw at it -- physics, AI, audio, etc. -- can be done without bottlenecking the game while the shading/rendering on the GPU is still being pushed.On the mobile side, this may not be true (yet) as the CPU's are -- comparatively -- fairly underpowered against their desktop counterparts. Couple this with the fact that the GPU is taxed to push out less pixels and one could easily see situations where the CPU becomes the bottleneck.
As mobile CPU's get faster -- especially with the A15/Krait generation -- this will become less and less of an issue especially as games make use of NEON to do their computationally heavy tasks and we'll get to a point where the GPU is the only bottleneck left.
But I don't see that happening until we hit the ~2.5GHz dual A15/Krait level.
vision33r - Thursday, December 1, 2011 - link
Very few Android games that I've seen are properly optimized unless they got that Optimized for Tegra logo. Otherwise most games do not take advantage of GPU acceleration.On iOS almost all games has some sort of GPU assist. Take Plants vs Zombies, the iOS version is perfect. The Android HD version has lower animation and graphics.
Almost all Gameloft games perform smoother on iOS than on Android.
metafor - Thursday, December 1, 2011 - link
Well yes. But the point is that with a higher performance CPU or group of CPU's, it is possible to have things that would be bottlenecked in a mobile device -- such as physics, AI, etc. -- be more complex and provide better visuals.Whether or not that has been done is another story. But you can hardly blame application devs for pouring more focus into iOS. The iPad is still what, ~90% of the tablet market? Moreover the App Store brings in way more revenue -- which the developers get a cut of -- than Android Market has thus far.
That will hopefully change over time.
steven75 - Saturday, December 3, 2011 - link
The problem with that theory is iPhones still bring in vastly more revenue for developers than android phones, despite the latter having higher market share.