[Asus  Eee Pad Transformer Prime] demandarin:
one thing though no one has mentioned, based off of Google engineer article, is that Ice Cream Sandwich will break alot of apps in circulation right now until developers update them to mesh well with ICS. That Dainne lady(Google engineer) said something like with ICS certain app processes or something will be forced to use hardware acceleration whereas before it was more of an option. with that she said it might cause alot of apps to act up since not written for the way ICS handles things. the degree to which the app breaks may be subtle to substantial.

She also debunked the hardware acceleration myth surrounding ICS. she said hardware acceleration has always been around in one form or another since Android 1.0. it wasn't until Honeycomb that full blown hardware acceleration got implemented. now going into ICS, the hardware acceleration won't be anymore "Full" than it was in honeycomb. The change comes with ICS that it will automatically have certain apps/processes look for ICS protocol and force Hardware acceleration. this is where not all apps might not mesh well until they are updated.

So hardware acceleration for the most part is not the magical thing needed or will make everything smoother automatically. there's more to it than just that. They have various tricks n such they use to help accomplish things better. software methods can be used to achieve faster frame rates(60fps). She did also mention how faster more powerful hardware will smooth things out more. its more so dependant on the GPU and the memory bandwidth size and speed. The Gpu is a fixed function component and handles the tasks of graphics n rendering alot better than the CPU and also using less power. I KNOW SOME CERTAIN MEMBERS GONNA BE LIKE I TOLD YOU SO...LOL.

This is where Tegra2 got slammed at. because of the bottleneck that was occurring those points plus Tegra2 not having Neon instruction sets. A lot of times the Gpu/CPU commands/instructions come out at a more faster rate than what the memorybandwith can support at once. Thus creating the bottleneck.

My take on it is that Tegra3 gpu is beefed up alot more and the memory bandwidth speed got increased dramatically also. that coupled with the Quad core/5 core CPU and we really have a nice setup. sure it may not be as high spec as future tabs we are hearing about down the road. the fact remains this is out now and its one helluva setup for something never attempted before. plus Nvidia does things differently than other chipmakers. Nvidia has tricks up their sleeves to help overcome any processing challenges that may occur. So in fact, regardless of what people may think, The Prime is truly a next generation device. having 2gb of Ram and a higher resolution doesn't constitute next generation. its all about power of device really and how it handles things. with that said Tegra3 fills that title very well. I can't wait till ICS drops because it will seem like an amped up experience. with better coding and better/updated drivers for various things, ICS will feel right at home on Tegra3 platform. although hardware acceleration is the same as it is in Honeycomb, everything is just going to mesh so well together. Also can't wait till down the road when these other tabs drop to do real life comparisons to Stock Prime and then a modded Prime running a custom rom and/or overclocking.

one tip the engineer said from now on is to always pay close attention to the GPU power and memory bandwidth size/speed. those will determine how good the system runs. Tegra3 is more than able to handle anything thrown out at it. Also slot of this still boils down to be mainly a software thing. bigger spec are being thrown at devices because of faults and rushing that Google engineers did in the beginning with the framework and coding. we can have apple to blame for this..lol. once iPhone dropped it forces Android to release like it was and there was no turning back. remever Android was conceived and developed before iPhone ever came around. Android was meant to compete with blackberry and symbian. when iPhone released, Android ran out the door as is to compete with them. there was no turning back from there and Android has been a constant work in progress since then. trying to find solutions n such for being rushed out the door as is to be competitive.

Just my take on ICS and everything from reading the original article, then the one from Google engineer, and another developer mentioned. sorry for the wall of txt..lol

---------- Post added at 09:36 AM ---------- Previous post was at 09:28 AM ----------

it is perception. in fact Android opens up apps and renders web pages just as fast or even faster than apple. they both handle the tasks differently therefore making perception of who's faster is different.

Apple gives UI top priority during all processes really. Android gives UI more of Normal priority. Like a web page for example loaded on both devices. while its loading if you touch or try to scroll around on apple device, the loading basically stops and gives the UI interaction top priority. if you do the same on Android, it tries to accomadate your scrolling while still loading the stuff up in the background. its really just more of how these two devices accomplish the same tasks differently. it doesn't make Android any slower. its the way Android goes about doing things, from being rushed and constantly being a work in progress. ill give Android more props because its doing alot more at once vs. IOS devices.