1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

A Look At Android's Graphics Rendering Pipeline

Google

Published on 06 December 2011 08:24 PM EST
Written by Michael Larabel in Google
2 Comments

For those interested in Android and graphics, here's a look at their graphics rendering pipeline as written by a long-time Android developer.

Dianne Hackborn, an Android Framework Engineer going back to 2005, has written on Google+ various facts about the Android graphics pipeline. Dianne wrote this public posting to correct the information that's out there about Android graphics. Below are some of her more interesting comments.
- "Full" hardware accelerated drawing within a window was added in Android 3.0. The implementation in Android 4.0 is not any more full than in 3.0. Starting with 3.0, if you set the flag in your app saying that hardware accelerated drawing is allowed, then all drawing to the application’s windows will be done with the GPU. The main change in this regard in Android 4.0 is that now apps that are explicitly targeting 4.0 or higher will have acceleration enabled by default rather than having to put android:handwareAccelerated="true" in their manifest.

- Hardware accelerated drawing is not all full of win. For example on the PVR drivers of devices like the Nexus S and Galaxy Nexus, simply starting to use OpenGL in a process eats about 8MB of RAM. Given that our process overhead is about 2MB, this is pretty huge. That RAM takes away from other things, such as the number of background processes that can be kept running, potentially slowing down things like app switching.

- Because of the overhead of OpenGL, one may very well not want to use it for drawing. For example some of the work we are doing to make Android 4.0 run well on the Nexus S has involved turning off hardware accelerated drawing in parts of the UI so we don’t lose 8MB of RAM in the system process, another 8MB in the phone process, another 8MB in the system UI process, etc...

- ...To get 60fps animation, Android 3.0 and later use a number of tricks. A big one is that it tries to put all windows into overlays instead of having to copy them to the framebuffer with the GPU. In the case here even with that we are still over-budget, but we have another trick: because the wallpaper on Android is in a separate window, we can make this window larger than the screen to hold the entire bitmap. Now, as you scroll, the movement of the background doesn’t require any drawing, just moving its window... and because this window is in an overlay, it doesn’t even need to be composited to the screen with the GPU.

Read more in her Google+ posting, which is likely of interest to many Phoronix readers due to the graphics hardware focus.

As of this August, there's mainline support in Mesa/Gallium3D for Android too, but that's more relevant to Android for x86.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux Hardware Reviews
  1. Trying The Configurable 45 Watt TDP With AMD's A10-7800 / A6-7400K
  2. Sumo's Omni Gets Reloaded
  3. AMD A10-7800 & A6-7400K APUs Run Great On Linux
  4. Radeon Gallium3D Is Running Increasingly Well Against AMD's Catalyst Driver
Latest Linux Articles
  1. Open-Source Radeon Graphics Have Some Improvements On Linux 3.17
  2. CPUFreq Scaling Tests With AMD's Kaveri On Linux 3.16
  3. Enabling HyperZ Is Still An Easy Way For Faster RadeonSI Performance
  4. AMD Kaveri: Catalyst vs. RadeonSI Gallium3D On Linux
Latest Linux News
  1. GNOME 3.14 Beta Makes GLSL Optional, Supports Wayland Gesture/Touch Events
  2. KDE Software Compilation 4.14 Released
  3. The Many Things You Can Build With A Raspberry Pi
  4. AMD's Catalyst Linux Driver Preparing For A World Without An X Server?
  5. Khronos Publishes Its Slides About OpenGL-Next
  6. Qt5 Will Now Support LGPLv3 Modules
  7. Proposed: A Tainted Performance State For The Linux Kernel
  8. Systemd 216 Piles On More Features, Aims For New User-Space VT
  9. Mesa 10.2.6 Has Plenty Of OpenGL Driver Bug Fixes
  10. LXQt 0.8 Is Being Released Soon
Latest Forum Discussions
  1. Remote gui not accessible in Phoronix Test Suite 5.2
  2. The dangers of Linux kernel development
  3. Dead Island for Linux (?)
  4. Updated and Optimized Ubuntu Free Graphics Drivers
  5. AMD Offers Mantle For OpenGL-Next, Pushes Mantle To Workstations
  6. Next-Gen OpenGL To Be Announced Next Month
  7. OpenGL 4.5 Released With New Features
  8. Updated graphics drivers for Ubuntu 12.04 Precise LTS