Design and Concepts of Android Graphics
111 likes63,650 views
The document discusses various aspects of Android graphics architecture, emphasizing the importance of Binder IPC for inter-process communication and the role of OpenGL ES in rendering. It explains the use of shared memory and graphics buffering mechanisms like SurfaceFlinger, PixelFlinger, and Copybit. Additionally, it provides technical details on different systems and functionalities within Android's graphics framework.
Design and Concepts of Android Graphics
- 1. Android Graphics Jim Huang ( 黃敬群 ) Developer & Co-Founder, 0xlab [email protected] Sep 24, 2011 / Study-Area
- 2. Rights to copy © Copyright 2011 0xlab http://0xlab.org/ [email protected] Attribution – ShareAlike 3.0 You are free Corrections, suggestions, contributions and translations are welcome! to copy, distribute, display, and perform the work to make derivative works Latest update: Nov 20, 2011 to make commercial use of the work Under the following conditions Attribution. You must give the original author credit. Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. License text: http://creativecommons.org/licenses/by-sa/3.0/legalcode
- 3. Agenda (1) Binder IPC (2) Android Graphics (3) 2D and Accelerations (4) OpenGL|ES
- 4. Notice: Before looking into Android Graphics, you should be aware of the design of Binder IPC, otherwise you would get lost!
- 5. Binder IPC
- 6. Processes running on Android $ ps ... root 37 1 248 156 c00aef2c 0000875c S /sbin/ueventd system 42 1 768 260 c022950c afd0b6fc S /system/bin/servicemanager root 43 1 3824 564 ffffffff afd0bdac S /system/bin/vold root 44 1 3796 560 ffffffff afd0bdac S /system/bin/netd root 45 1 628 264 c02588c0 afd0c0cc S /system/bin/debuggerd radio 46 1 4336 672 ffffffff afd0bdac S /system/bin/rild root 47 1 62224 27576 c00aef2c afd0b844 S zygote media 48 1 16828 3736 ffffffff afd0b6fc S /system/bin/mediaserver bluetooth 49 1 1216 572 c00aef2c afd0c59c S /system/bin/dbus-daemon root 50 1 776 316 c02a8424 afd0b45c S /system/bin/installd keystore 51 1 1704 432 c02588c0 afd0c0cc S /system/bin/keystore shell 52 1 696 336 c0050934 afd0c3ac S /system/bin/sh root 53 1 3356 160 ffffffff 00008294 S /sbin/adbd system 67 47 172464 32596 ffffffff afd0b6fc S system_server system 115 47 80028 20728 ffffffff afd0c51c S com.android.systemui app_24 124 47 80732 20720 ffffffff afd0c51c S com.android.inputmethod.latin radio 135 47 87848 20324 ffffffff afd0c51c S com.android.phone app_18 144 47 89136 24160 ffffffff afd0c51c S com.android.launcher app_7 165 47 86136 22736 ffffffff afd0c51c S android.process.acore app_0 197 47 73996 17472 ffffffff afd0c51c S com.android.deskclock app_14 208 47 75000 18464 ffffffff afd0c51c S android.process.media app_3 219 47 72228 17652 ffffffff afd0c51c S com.android.bluetooth app_25 234 47 85336 17836 ffffffff afd0c51c S com.android.mms app_26 254 47 74656 19080 ffffffff afd0c51c S com.android.email app_27 266 47 74912 18100 ffffffff afd0c51c S com.android.providers.calendar app_1 285 47 71616 16280 ffffffff afd0c51c S com.android.protips app_19 293 47 72184 16572 ffffffff afd0c51c S com.android.music app_21 301 47 74728 17208 ffffffff afd0c51c S com.android.quicksearchbox app_28 311 47 75408 18040 ffffffff afd0c51c S com.cooliris.media shell 323 52 856 316 00000000 afd0b45c R ps $ More than 30 processes (200+ threads). 6
- 7. IPC = Inter-Process Communication Activity Activity Window Alarm Manager Manager Manager Kernel 7
- 8. IPC Abstraction More abstract Intent • Intent – The highest level abstraction AIDL • Inter process method invocation – AIDL: Android Interface Binder Definition Language • binder: kernel driver • ashmem: shared memory 8
- 9. Method invocation caller callee In the same process 9
- 10. Inter-process method invocation caller interface caller interface How? callee interface callee 10
- 11. Inter-process method invocation caller interface Proxy caller interface Binder in kernel Binder Thread callee Stub interface callee 11
- 12. android.os.Parcel Delivering arguments of method ”flatten” ”unflatten” transmit 12
- 13. UML Representation <<interface>> implements Proxy Stub 13
- 14. UML Representation caller <<interface>> calls implements Proxy Stub extends callee 14
- 15. AIDL Auto generated from .aidl file caller <<interface>> Proxy Stub callee 15
- 16. Use Case: Who calls onPause() in Activity? 2 Send message by Handler Activity 3 OnPause() is queue Looper called in main thread Activity Manager Main Binder Thread Thread #1 Kernel 1 Call ”schedulePauseActivity” across process 16
- 17. Binder • Multi-thread aware – Have internal status per thead – Compare to UNIX socket: sockets have internal status per file descriptor (FD) 17
- 18. Binder A pool of threads is associated to each service application to process incoming IPC (Inter-Process Communication). Binder performs mapping of object between two processes. Binder uses an object reference as an address in a process’s memory space. Synchronous call, reference couting
- 19. Binder
- 20. Binder is different from UNIX socket socket binder internal status associated to FD associated to PID (FD can be shared among threads in the same process) read & write stream I/O done at once by operation ioctl network Yes No transparency expected local only 20
- 21. Transaction of Binder binder_write_read write_size write buffer write_consumed write_buffer read_size read_consumed read buffer read_buffer if (ioctl(fd, BINDER_WRITE_READ, &bwt ) >= 0) err = NO_ERROR; else err = -errno; 21
- 22. Transaction of Binder Process A and B have different memory space. They can not see each other. Kernel Process B Process A Binder Copy memory by copy_from _user Then, wake up process B Kernel Process B Binder Process A Copy memory by copy_to_user Internally, Android uses Binder for graphics data transaction across processes. 22 It is fairly efficient.
- 23. Real Case Binder IPC is used for communicating between Graphics client and server. 23 Taken from http://www.cnblogs.com/xl19862005/archive/2011/11/17/2215363.html
- 24. Ashmem • Android / Anonymous SHared MEMory subsystem – system/core/cutils/ashmem.h – int ashmem_create_region(const char *name, size_t size) – int ashmem_set_prot_region(int fd, int prot) – int ashmem_pin_region(int fd, size_t offset, size_t len) – int ashmem_unpin_region(int fd, size_t offset, size_t len) • a named memory block shared between processes that the kernel is allowed to free. – This is notable as the kernel is not allowed to free standard shared memory. • Similar to weak reference of Java. Useful to implement cache. • Used in android.os.MemoryFile (Java), 2D memory allocator, etc. 24
- 25. Android Graphics
- 26. Surface Source: frameworks/base/core/java/android/view/Surface.java • /* Handle on to a raw buffer that is being managed by the screen compositor */ public class Surface implements Parcelable { public Surface() { mCanvas = new CompatibleCanvas(); } private class CompatibleCanvas extends Canvas { /* ... */ } } Surface instances can be written to and restored from a Parcel. Surface instances can be written to and restored from a Parcel.
- 27. Delivering arguments of method ”flatten” ”unflatten” transmit
- 28. Properties Android SurfaceFlinger Can combine 2D/3D surfaces and surfaces from multiple applications Surfaces passed as buffers via Binder IPC calls Can use OpenGL ES and 2D hardware accelerator for its compositions Double-buffering using page-flip
- 30. from SurfaceFlinger to Framebuffer
- 37. PixelFlinger : software renderer • Render functions: pointx, linex, recti, trianglex • Texture and color buffer: activeTexture, bindTexture, colorBuffer, readBuffer, depthBuffer, BindTextureLod • … • Device framebuffer functions: copyPixels, rasterPos2x, rasterPos2i • Optimizer: codeflinger (JIT assembler) I/SurfaceFlinger( 1931): OpenGL informations: I/SurfaceFlinger( 1931): vendor : Android I/SurfaceFlinger( 1931): renderer : Android PixelFlinger 1.2 I/SurfaceFlinger( 1931): version : OpenGL ESCM 1.0
- 38. GGLAssembler – GGLAssembler – codeflinger's JIT Assembler codeflinger's JIT Assembler
- 40. Skia • SkBitmap • SkBitmap::Allocator • GPU integration in Android 4.0
- 41. Case Study: WebKit rendering Fill rectangle FillRectangles() Set clip region Acquire font cache Show glyphs Blit(), memcpy() BatchBlit() Allocate font cache Surface composite Blit() Prepare / finish Clear() TileBlit() composite
- 42. 2D Compositing SRC SRC & DST Compositing 1 -asrc SRC & NO-DST DST NO-DST & NO-SRC 1-adst adst
- 44. Android Graphics (HAL view) Android Framework (Java) libandroid_runtime Surfaceflinger Copybit EventHub (service) (HW accelerated) LibGLES libui (libagl) libpixelflinger
- 45. 2D Accelerator for Android Graphics • libcopybit provides hareware bitblit operations which includes moving, scaling, rotation, mirroring, and more effects, like blending, dithering, bluring, etc. • Removed since Android 2.3 • Android has two copybit interfaces: – Blit: moving / blending – Stretch: scaling besides moving • libcopybit is called by libagl which can do swapBuffers to do the framebuffer page flipping that can also be accelerated by libcopybit. Copybit could improve the performance of page flipping Copybit could improve the performance of page flipping
- 46. Copybit operations Copybit: 2D blitter Copybit: 2D blitter
- 47. PMEM: Manipulate physically continuous memory • Hardware graphics/bitblt operations (blitter) needs physical continuous memory to manipulate. • Android use libgralloc to allocate pmem (physical continuous memory) for android native buffer. pmem driver can support up to 12 devices, we have only one for copybit (Android, android native buffer) • While running 0xbench, the peak size of the pmem allocated (mapped) is 25194496 bytes. Take Qualcomm MSM7x25 for example: Take Qualcomm MSM7x25 for example: • /dev/pmem • /dev/pmem • /dev/pmem_adsp • /dev/pmem_adsp – For multimedia codec, audio, video, camera – For multimedia codec, audio, video, camera
- 48. gralloc & pmem gralloc_alloc Offset = Alloc(size), PMEM_CONNECT, PMEM_MAP, memset If success, new private_handle_t(fd, size, flags); gralloc module gralloc_free PMEM_UNMAP, deallocate(offset)
- 49. pmem memory (mmaped virtual address)base master_fd (mmap size: 47MB) 0x49422336, c06c4000, 6c4000 Buffer 1 buffer base = base + fd when being freed, this offset will be closed Buffer 2 Buffer 3 Quantum Debug pmem, pmem /sys/kernel/pmem_regions pmem can have up to 12 devices..., we have only one for copybit (Android native buffer)
- 50. gralloc/copybit structure android_native_buffer_t buffer_handle_t handle; native_handle_t copybit_image_t native_handle_t* handle; buffer_handle_t libgralloc private_handle_t Fd (pmem dev) Android native buffer contains Offset buffer_handle_t Size Which is native_handle * , Base defined in system/cutils/ Flags virtual address lockState private_handle_t::PRIV_FLAGS_U SES_PMEM private_handle_t::LOCK_STATE_MAPPED
- 51. Functions in copybit HAL • BLIT (moving) • Stretch (scaling) • Alpha-blending – Unused in real case • Rotate – Unused in real case
- 52. OpenGL|ES
- 53. Key Concepts • Android is moving to OpenGL|ES accelerated rendering since version 2.x • Window systems already comprehend z-order • 3D != 2D with depth • OpenGL is object based – Describes a scene using its components and properties. Output quality is dependent on the renderer, not source
- 54. OpenGL Terminology • OpenGL An API from Khronos (from SGI), for constructing a 3D object, doing operations on the object, and displaying it • Primitives Triangles, Lines, Points, that can be specified through vertices to define an arbitrary shape • Texture Small (!) bitmap to make objects more realistic • EGL The EGL API defines a portable mechanism for creating GL contexts and windows for rendering into, which may be used in conjunction with different native platform window systems using the WSEGL layer
- 55. EGL • EGL (Embedded-System Graphics Library) is an interface between Khronos rendering APIs (such as OpenGL ES or OpenVG) and the underlying native platform window system. • EGL handles graphics context management, surface/buffer binding, and rendering synchronization and enables high-performance, accelerated, mixed- mode 2D and 3D rendering using other Khronos APIs. • EGL Surfaces – windows - on-screen rendering – pbuffers - off-screen rendering – pixmaps - off-screen rendering
- 56. from EGL to SurfaceFlinger hgl = hardware hgl = hardware agl = android software agl = android software OpenGL|ES OpenGL|ES OpenGL|ES renderer OpenGL|ES renderer