Powering up your app performance & stability using App Vitals
summary
App Vitals adds an excessive partial wake lock metric that flags apps when background wake locks run three or more hours in 24h for >5% of sessions and a wear OS battery drain rule (>1% sessions over 4.4%/hr). The talk shows concrete fixes: replace manual wake locks with WorkManager/JobScheduler, name wake locks consistently, always release with try/finally or timeouts, debug with system traces analyzed in Peretto, and capture field profiles programmatically using Profiling Manager.
AI-written summary · about
chapters (16)
- 0:00App Vitals introduction
- 1:02Excessive battery metrics
- 2:03Wake locks and impact
- 4:12Wake lock use cases
- 7:02Wake lock best practices
- 9:31Debugging wake locks
- 10:15Debugging weather app
- 13:08Debugging health app
- 15:15System traces for debugging
- 18:59Perfetto SQL analysis
- 21:53Profiling Manager field
- 25:30Core Vitals stability
- 26:12Debugging ANRs
- 29:43ANR dashboard insights
- 31:32System profiling ANRs
- 32:59Summary resources
related talks
30mBoosting Performance Through App Quality Improvements
33mIs my application taking up too much power?
38mHow to keep your app awake in a GSM phone app
21mImproving battery life with restrictions
34mDon't Kill My App: Android survival guide
26mDon't let your app drain your users' battery
40mAndroid vitals: Debug app performance and reap rewards
22mPower optimization for Android