Since Android 4.x supports hardware accelerated 2D rendering, it is
quite important to perform corresponding measurement.
rogeryi contributed a modified version of 0xbench:
https://github.com/rogeryi/0xbench_2d_hw
The work was forked from 0xbench.
Sincerely,
Jim Huang (jserv)
http://0xlab.org/
--
You received this message because you are subscribed to the Google Groups "0xlab-devel" group.
To post to this group, send email to 0xlab...@googlegroups.com.
To unsubscribe from this group, send email to 0xlab-devel...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/0xlab-devel?hl=en.
hi Roger,
Thanks for your work.
> 1, 2D(SV), rendering happens on a SurfaceView, through a SW canvas in
> an individual rendering thread.
> 2, 2D(HW), rendering happens on a normal View inside a HW accelerated
> window, through a HW canvas in UI thread.
> 3, 2D(SW1), rendering happens on a normal View inside a None HW
> accelerated window, through a SW canvas in UI thread.
> 4, 2D(SW2), rendering happens on a normal View inside a HW accelerated
> window, but the View has a SW layer, through a SW canvas in UI thread.
These cases seem to be what WebKit in ICS behaves. It is great to quantify.
What is the typical usage of condition (4)?
> more information you can found on my blog: http://rogeryi.wordpress.com/
> and this slide (include two test results, one from a galaxy tab 10.1
> android 3.2, other one from a Nexus S android 4.0.3):
> http://www.slideshare.net/rogeryi/android-hardware-accelerated-2d-rendering
> also this one: http://www.slideshare.net/rogeryi/beyond-android-views-windowsurfacespecial-viewsand-more
Nice materials. Thanks again for sharing.