G(PU) force
summary
Explains why Android hardware acceleration both speeds animations and creates device-specific bugs, showing concrete debugging steps: read the GPU rendering graph in Android Studio to spot 16 ms / 60 fps violations, use Layout Inspector and the overdraw visualizer to find redundant layers, run Systrace and rendering profiler to isolate long input/measure/draw/upload stages, and toggle hardware layers or prepareToDraw to fix jank. Gives real failures — a TV box with invisible UI and a “shredded” gallery — and explains API level differences (API 11/14/16, prepareToDraw on N) and memory pitfalls.
AI-written summary · about
chapters (10)
- 0:00Introduction to GPU force
- 2:54Why understand GPU hardware
- 10:17Hardware vs software drawing models
- 15:58Debugging GPU rendering tools
- 24:23Fixing GPU overdraw issues
- 31:46Optimizing view hierarchies
- 32:52Identifying GPU-related bugs
- 38:20Hardware layers and animations
- 39:04Custom view GPU optimization tips
- 40:53Q&A on GPU performance
related talks
38mGPU. The journey from code to pixel
40mAndroid Graphics Performance
33mUI profiling in examples. Where is my bottleneck?
26mIntroduction to Hardware Acceleration (en)
53mGraphics Something Android Something Performance
37mUI profiling in examples. Where is my bottleneck?
45mHigh performance in Android
36mDrawn out: How Android renders