[Samsung Galaxy Nexus] dhruvraj:
The source was the rather unfriendly : http://appadvice.com/appnn/2011/12/android-lag-attributed-to-core-system-framework-here-to-stay

Read the explanations. Then yes the guy's (an ex google intern who has worked on the UI) theory is questioned and made to look incorrect, by Diane (current google employee working on the UI) - whose post are also interesting [she gets bashed by users left right n center about lag and has no answers by the end of it. She also says she hasnt touched an iOS device :) - which is kind of funny and ironic that she is defending Androids lag]

Anyway, here - one user on how the lag is there even in htc one X - How many cores will Android need before it is consistently smooth throughout?﻿

HTC One X Hands-on - MobileSyrup.com

http://www.youtube.com/watch?v=gWC4l2EsGSU&t=6m58s

iPhone http://www.youtube.com/watch?v=vUw9eppD4-0

"The big issue is that ICS and better hardware has NOT fixed the issue. I tried out the Transformer Prime, the new TF300t, and the Acer A510 over the last week. These are the top of the line - ridiculously overpowered machines. The UI was choppy throughout the home screen and every application.

Google Maps, ironically, is superior on the iPad 2. It's not just list performance. It's systemic. Well, from an end-user prospective it's systemic and that is ultimately what matters. "

And seriously, you dont even need any article or anyones proof - you can see it yourself! This was just an explanation of WHY the problem in android is SO deeply ingrained, that even Google - after the project butter, can not eliminate the lag which still persists, and is pretty clearly evident if you can observe carefully in most of the actions - swiping home screens app drawers, esp while you were using the phone for some other activity at the same time.

Whether the explanation is correct or not, is hardly of any big consequence - problem remains, and project butter does not tackle it head on - instead gives minor hacks and adjustments to eyewash users with apparent smoothness - while there are major, and consistently jerky performances out there - which point to a deep rooted problem with Android.

It has to be deep, if Google can not solve it with all its might yet

---------- Post added at 01:59 AM ---------- Previous post was at 01:53 AM ----------

iOS might stutter 5% of the time, to androids 30% of the time - so your point number 1 is pretty much worthless to make. (The percentages dont matter but android lags significantly more than iOS - besides I'vent seen iOS stutter but I take your word that it still might some times)

On point number 2 I do agree - a high speed camera with an iPhone 4s and galaxy nexus would pretty much settle it. Responsiveness of home screen swipes, application openings, keyboard - all would be out to be seen.

Additionally, Android's framerate should really be measured on overall use of the device. It would just be shameful in comparison to iOS in my opinion.

Not for no reason you see iDevices trouncing all the android phones out there when it comes to graphics benchmarks. They really r*pe android devices - and in every single way possible!

And you really should just go out and search on that one... here are a couple of starters :

ICS benchmarked on galaxy nexus : http://www.anandtech.com/show/5310/samsung-galaxy-nexus-ice-cream-sandwich-review/9

now you would say oh its ICS, not jelly bean

so jelly bean benchmarked, and with Tegra3 nexus 7!

http://www.phonearena.com/news/Google-Nexus-7-gets-the-benchmark-treatment_id31710#3-

http://i-cdn.phonearena.com/images/articles/61895-image/google-nexus-7-benchmark-3.jpg

http://i-cdn.phonearena.com/images/articles/61896-image/google-nexus-7-benchmark-4.jpg

These numbers are there, for a reason.