Linked by Thom Holwerda on Tue 6th Dec 2011 22:16 UTC
Google Dianne Hackborn has posted on Google+ about some common myths regarding Android's graphics rendering pipeline, and we have a rebuttal to that one as well. Interesting stuff, but I want to talk abut something related: Android's gaphics performance. I'm hearing a lot of talk about how Android's effects and transitions and such aren't as smooth as those on iOS, but on my Galaxy SII, everything is super-smooth. So, I'm wondering - what's it like for you?
Permalink for comment 499265
To read all comments associated with this story, please click here.
Comment by kovacm
by kovacm on Wed 7th Dec 2011 09:23 UTC
kovacm
Member since:
2010-12-16

you ask "why is Android laggy, while iOS, Windows Phone 7, QNX, and WebOS are fluid?" ... ?

here it is:

"If you want to achieve 60fps, you have 20 milliseconds to handle each frame. This is not a lot of time. Just touching the flash storage system in the thread that is running the UI can in some cases introduce a delay that puts you out of that timing window, especially if you are writing to storage."

thats why! because of bad design, bad code, poor control of superiors inside Google Android group, bad decisions...

prove:

"As of Android 3.0, the browser now uses tiles, so it can maintain a consistent frame rate as you scroll or zoom..."

after 4 years that decide to go with tiles.

I really hope that Google will be better at software quality than Microsoft (often it is)...

and again:

"Nexus S CPU can easily draw the tiles to the window at 60fps"

Dianne think that if CPU can draw that it is the best way ?!?! - but is it most efficient way? they need to work a lot at Google to change this type of thinking...

Reply Score: 1