Nexus 9 To Be First Device With Android L And Nvidia Denver CPU
Tags:
-
Android
-
Google
Last response: in News comments
Anonymous
October 14, 2014 10:59:28 AM
The Nexus 9 will be announced tomorrow according to a Google source. The device will be the first to come out with Android L on board and also the first to use a 64-bit Denver CPU from Nvidia.
Nexus 9 To Be First Device With Android L And Nvidia Denver CPU : Read more
Nexus 9 To Be First Device With Android L And Nvidia Denver CPU : Read more
More about : nexus device android nvidia denver cpu
-
Reply to Anonymous
HardyHarHar
October 14, 2014 11:11:22 AM
a1r
October 14, 2014 3:48:36 PM
You should take Nvidia's internal benchmarks with half a grain of salt. Nvidia is known to fudge it's driver benchmark results by various means. The real world performance is an unknown.
That said benchmarks on a tablet are pretty useless to begin with. Tablets are normally single use devices where you're doing only one interactive program at a time. So long as it will play video smoothly, display readable text, and replay music without chop a tablet is no different now from the first generation android tablets.
The entire question isn't how fast it is, rather it's how stable it's software will be. That is a complete unknown with a new generation processor AND a next generation software stack.
I might leave Samsung for a Nexus 9.
I might leave Samsung for a Nexus 9.
That said benchmarks on a tablet are pretty useless to begin with. Tablets are normally single use devices where you're doing only one interactive program at a time. So long as it will play video smoothly, display readable text, and replay music without chop a tablet is no different now from the first generation android tablets.
The entire question isn't how fast it is, rather it's how stable it's software will be. That is a complete unknown with a new generation processor AND a next generation software stack.
Quote:
Android devices keep getting better!I might leave Samsung for a Nexus 9.
Quote:
Android devices keep getting better!I might leave Samsung for a Nexus 9.
-
Reply to a1r
m
-1
l
chuckydb
October 14, 2014 4:19:03 PM
-
Reply to chuckydb
m
-2
l
ThisWasATriumph
October 14, 2014 4:34:36 PM
jasonelmore
October 14, 2014 4:39:29 PM
Thomas Serruques
October 14, 2014 5:17:48 PM
Barry Fliegelman
October 14, 2014 6:32:31 PM
gdfrisco
October 14, 2014 8:42:31 PM
fyend
October 14, 2014 9:51:02 PM
dragonsqrrl
October 15, 2014 2:50:28 PM
chuckydb said:
I hope this screen resolution isn't accurate, cause it sucks.8inch tablets now have 2560*1600 screen. The nexus 10 had that 2 years ago.
Going lower than an ipad iwould be a big dissapointment.
If they want a 4:3 screen, then they should go just like a chromebook pixel with 2560*1700.
It actually has the same resolution as the iPad. And 2560x1700 is not 4:3...
-
Reply to dragonsqrrl
m
1
l
dragonsqrrl
October 15, 2014 2:51:59 PM
somebodyspecial
October 15, 2014 5:31:17 PM
a1r said:
You should take Nvidia's internal benchmarks with half a grain of salt. Nvidia is known to fudge it's driver benchmark results by various means. The real world performance is an unknown. That said benchmarks on a tablet are pretty useless to begin with. Tablets are normally single use devices where you're doing only one interactive program at a time. So long as it will play video smoothly, display readable text, and replay music without chop a tablet is no different now from the first generation android tablets.
The entire question isn't how fast it is, rather it's how stable it's software will be. That is a complete unknown with a new generation processor AND a next generation software stack.
Quote:
Android devices keep getting better!I might leave Samsung for a Nexus 9.
Quote:
Android devices keep getting better!I might leave Samsung for a Nexus 9.
You apparently missed all the shield tablet scores. K1's scores are not an unknown, and Denver will probably just match it+better battery life due to in house cpu. That's not a jab, that would still be an awesome soc, just saying what I expect. The best part is nobody has to retool as it is pin compatible, so anyone making a K1 design now, should be able to just slot in the Denver version and boom, selling 64bit shortly after. Very wise on NVs part doing this. Regarding the problems, you're forgetting everyone will have the same issues with new software/stack etc and everyone will be moving to 64bit (hardware and software).
-
Reply to somebodyspecial
m
0
l
somebodyspecial said:
Regarding the problems, you're forgetting everyone will have the same issues with new software/stack etc and everyone will be moving to 64bit (hardware and software).Since most of Android is simply Java running on top of Dalvik/ART, there is not much "64-bitness" for software beyond the core OS and runtime to worry about.
-
Reply to InvalidError
m
0
l
somebodyspecial
October 15, 2014 9:50:19 PM
InvalidError said:
Quote:
Regarding the problems, you're forgetting everyone will have the same issues with new software/stack etc and everyone will be moving to 64bit (hardware and software).Since most of Android is simply Java running on top of Dalvik/ART, there is not much "64-bitness" for software beyond the core OS and runtime to worry about.
I didn't say it was difficult (or not), just that everyone deals with the same thing here. Not sure why your post says dragonsqrrl said it, I did
Not that I think he'd be offended by thrown under my bus in this case...Just saying...He wasn't even in my post or quoted in it. Odd he got slapped with my comment...LOL. -
Reply to somebodyspecial
m
0
l
somebodyspecial said:
Not sure why your post says dragonsqrrl said it, I did
Not that I think he'd be offended by thrown under my bus in this case...Just saying...He wasn't even in my post or quoted in it. Odd he got slapped with my comment...LOL.Evil comment editing: every time I quote a message but do decide to not post a reply, the text from all the unsent quoted messages get prepended to the next messages I reply to until I post a reply. Since the quote blocks only contain numeric message IDs, quotes get screwed up if I remove the wrong parts while cleaning up that mess of stray quotes.
Not sure if that is a feature or a bug. I'd have to try it from Chrome or IE to see if this is a server-side or browser-side thing.
-
Reply to InvalidError
m
0
l
somebodyspecial
October 16, 2014 2:32:15 PM
InvalidError said:
somebodyspecial said:
Not sure why your post says dragonsqrrl said it, I did
Not that I think he'd be offended by thrown under my bus in this case...Just saying...He wasn't even in my post or quoted in it. Odd he got slapped with my comment...LOL.Evil comment editing: every time I quote a message but do decide to not post a reply, the text from all the unsent quoted messages get prepended to the next messages I reply to until I post a reply. Since the quote blocks only contain numeric message IDs, quotes get screwed up if I remove the wrong parts while cleaning up that mess of stray quotes.
Not sure if that is a feature or a bug. I'd have to try it from Chrome or IE to see if this is a server-side or browser-side thing.
ROFL...It's a feature...Honest...
Just like the double posting etc etc...Really tomshardware has the worst software out of any website I've been on in years (for comments and forums at least, and those dang picture slideshow reviews - instant move along response from me since they are such a PITA to read). Or maybe it's really OK software, but just mismanagement of it's use. Either way something is wrong. I have to try many times reloading etc just to get the ability to see the comment button (so I'm not just commenting on the post, but to get into the forum side I mean). I could go on and on with errors that I see routinely but it would likely fall on deaf ears.Anyway, I get your point
Not shocked at all by your response...Toms has "issues".*grits teeth tries not to swear*
-
Reply to somebodyspecial
m
0
l
!