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 Articles & Reviews
  1. Linux Compiler Benchmarks Of LLVM Clang 3.5 vs. LLVM Clang 3.6-rc1
  2. Intel Broadwell HD Graphics 5500: Windows 8.1 vs. Linux
  3. Linux Benchmarks Of NVIDIA's Early 2015 GeForce Line-Up
  4. NVIDIA GeForce GTX 960: A Great $200 GPU For Linux Gamers
  5. Disk Encryption Tests On Fedora 21
  6. Xonotic 0.8 Performance With The Open-Source AMD/NVIDIA Gallium3D Drivers
Latest Linux News
  1. Chromebook "Rush" With 64-bit Tegra SoC Support Lands In Coreboot
  2. 2015 X.Org Elections Get Underway For Board Members, SPI Merger
  3. Linux 3.19-rc6 Kernel Released: LInux 3.19 Final In Two Weeks
  4. Ubuntu's Mir Gains Server-Side Platform Probing
  5. Broadwell Linux Ultrabook Running MUCH Cooler Than Haswell
  6. LZHAM 1.0 Lossless Data Compression Codec Released
  7. LibreOffice 4.4 Is Coming Soon With New Features
  8. Linux Users Upset By Chromium's Busted HiDPI Support
  9. BPF Backend Merged Into LLVM To Make Use Of New Kernel Functionality
  10. Dying Light Is Headed To Linux, SteamOS
Most Viewed News This Week
  1. Windows 10 To Be A Free Upgrade: What Linux Users Need To Know
  2. Google Admin Encourages Trying Btrfs, Not ZFS On Linux
  3. TraceFS: The Newest Linux File-System
  4. My Initial Intel Broadwell Linux Experience With The ThinkPad X1 Carbon
  5. Mozilla's Servo Still On Track For 2015 Alpha Release
  6. Fedora 23 Likely To Pursue Wayland By Default
  7. Keith Packard Leaves Intel's Linux Graphics Work
  8. A Proposal To Go 64-bit Only With Fedora 23