If I'm not mistaken, Gingerbread has partial hardware acceleration in the UI. Now is this implemented into any Gingerbread ROM's out there right now? I'm running BAMF Sense 3.0 4.9 and I have no idea if hardware acceleration is implemented or not. Could someone elaborate more on the hardware acceleration on Gingerbread. I could totally be wrong.
Android phones have been using hardware acceleration for quite a while. They use OpenGL (just the embedded version) like most non-windows systems.
http://en.wikipedia.org/wiki/OpenGL_ES
http://www.khronos.org/opengles/
I use Motorola xoom MZ601, rom is tiamat 2.1 hammerhead.
Today, i see the video that vegacomb build no.6
that video's stock launcher has a gpu accelerated, so scrolling screen with live wp is smoother than xoom.
how can i make a xml with gpu accelerated to stock launcher with honeycomb??
Can somebody explain to me how the new Accelerated 2D drawing implemented into ICS is going to improve the quality of apps? will it improve the GUI/UI? If so how?
I know the basics about it, i just want to know the extend to which is can be used. Will better graphics and animations be possible?
Bump bump bump
It will make scrolling and animations look smoother and lagfree iirc
hey guys
can i know what is HWcomposer actually? what work it does? i know it doesnt work in JB but dont know what it does actually . what features i may miss without it?
ancilary said:
hey guys
can i know what is HWcomposer actually? what work it does? i know it doesnt work in JB but dont know what it does actually . what features i may miss without it?
Click to expand...
Click to collapse
HWcomposer enables UserInterface (UI) rendering via GPU
u can see the link below to understand more about the same
HW Composer
and can we dual boot jb and ics? is it possible?
Sun90 said:
HWcomposer enables UserInterface (UI) rendering via GPU
u can see the link below to understand more about the same
HW Composer
Click to expand...
Click to collapse
hi there! I have been wondering what this means too.
What are the effects of having HWcomposer not working? Laggy graphics?
Force GPU rendering isn't enabled by default, so how will this impact performance? Battery life?
Thanks!
According to the HW composer link HW composer is there since Honeycomb so how is it a JB enhancement all of a sudden?
So, SurfaceFlinger in Android is what actually puts together the different screens and surfaces, using OpenGL (the GPU).
Hardware Composer (HWC) is a little module that plugs into SurfaceFlinger, and helps offload some of the surface compositing onto specialized display hardware. Usually this is just a 2D GPU, but sometimes graphics parts have special "overlay" planes that can be used, instead. This lightens the GPU load in several ways, potentially improving performance.
It's been present since Honeycomb, but the API is updated once in a while to support more features. The [Android Sync infrastructure] was added in JB MR1, and requires a whole bunch of new APIs to be implemented for this explicit synchronization. It also relies on some Linux kernel APIs which are only present in v3.4+.
[Android Sync infrastructure]: http s://lwn.net/Articles/569704/
I have graphic acceleration issue in all the Rom based CM12.
grahpic moves very slowly in some games.
in stock rom it has no problem.
Is there any solution to fix?
I don't know if you saw my reply in the other thread but enabling force GPU rendering in developer options seemed to work for me.