No battery, no (watch) life!!
summary
Small, concrete failures decide what to watch: OLED pixels cost lots of power and an always‑on screen causes ghosting; an endless UI spinner caused CPU to stay awake and led to thermal shutdown; inserting a one‑second pause cuts that workload and yields about a 30% drop in battery use. Diagnosis uses Battery Historian and a hacked 5 kHz power monitor (battery wiring replaced with a measurement box) and FFT analysis that found a 60 Hz display‑driver bug. Daily automated tests and converting mA to hours prevent regressions.
AI-written summary · about
chapters (5)
related talks
50mWhy Does My Smartphone Battery Die in One Day?
48mHow to Build Performance-Driven Android Apps
22mPower optimization for Android
34mPowering up your app performance & stability using App Vitals
17mCost of a pixel color
23mCreating Applications for Small Screen, Low Memory Android Wearables
35mHow to survive on Android and don't get killed
26mDon't let your app drain your users' battery