TL;DR: My Find X9 Pro was getting about 7h SOT per charge while people here report 10-12h. I connected it to Claude Code on my PC over ADB and let it audit the phone. The hardware was fine; background apps weren't. The biggest find was my Santander UK banking app keeping the gyroscope and accelerometer at 400 Hz in the background, and it never showed up in Battery usage. Also found that ColorOS's battery toggle didn't actually restrict apps at the Android level for me; I had to use a hidden Android menu. Fixed with a few toggles, no root. Early days on the results, see below. I just wanted to state that I'm not a heavy user, I don't game or stream videos, just causal browsing and social media.
UPDATE: A full step by step guide can be found here https://www.reddit.com/r/Oppo/s/gPC7YKLsCh
Phone: Find X9 Pro (CPH2791, EU), ColorOS 17.0.0.102, 7500 mAh, 122 cycles, battery health Good.
Method: With USB debugging on, Claude read battery stats, wakelocks, alarms, background jobs and sensor registrations through dumpsys, then asked me before changing anything.
WHAT IT FOUND
Santander UK: background sensor leak
- The app bundles a fraud-detection SDK (BioCatch), plus a periodic IBM Trusteer job (TasService, every 15 min) that relaunches the app in the background.
- When the process starts that way, with no screen open, BioCatch registers the accelerometer and gyro at 400 Hz, rotation vector at 200 Hz and proximity at 1 kHz, all unbatched, and never unregisters them.
- Android cuts off delivery to the cached app, but the sensors stay switched on at the hardware level.
- That day I'd opened the app once, for about 40 seconds. It was relaunched 14 times anyway, and Android killed it twice for "excessive CPU usage".
- A/B test (unplugged, screen on, 6 alternating rounds): +21 to 23 mA, about 7% more drain while it was running. Sensor-HAL CPU dropped from 204 to 13 ticks per 30 seconds once it was stopped.
- Opening the app normally is fine: BioCatch unregisters its sensors 8 seconds after you leave. Only the background relaunch leaks.
2) Instagram background Reels prefetch (ClipsTabBackgroundPrefetchWorker)
- 25 min of job time and 15 min holding a wakelock in under 2 hours on battery, mostly with the screen off. About 3.6h a day in the background.
3) WhatsApp (XmppLifecycleWorker)
- 36 job runs in under 2 hours, 26 of them with the screen off. It was on "Don't optimise".
4) OPPO-preinstalled Facebook services (App Manager / Services / Installer)
- System-exempt from Doze, about 114 wakeup alarms a day.
6) Google Play services Bluetooth scanning
- 19 min in under 2 hours with Bluetooth off, via the "Bluetooth scanning" setting under Location services.
WHY BATTERY SETTINGS NEVER SHOWED IT
- The cost lands on the system, not the app. Santander's sensor drain was billed to Android's sensor service, so batterystats blamed Santander for 0.19 mAh in a window where it was costing about 22 mA whenever it ran.
- The battery accounting itself looks broken on this phone. It seems to ship a generic power profile: its CPU frequency tables are Snapdragon values, on a MediaTek chip. In one session Android could only attribute about 60 of 298 mAh (around 20%) to specific apps; the rest went unattributed. So "Battery usage by app" can't be trusted to show what's actually draining.
THE HIDDEN ANDROID BATTERY MENU (AND WHY THE COLOROS TOGGLE WASN'T ENOUGH)
ColorOS replaces Android's battery screens with its own. Android's original per-app battery page still exists, with the real "Allow background usage" switch and the Optimised / Unrestricted choice, but you can't reach it from the normal ColorOS menus.
In my case, turning off background usage for Instagram through ColorOS's normal App battery management did NOT restrict it at the Android level. Its background jobs, including the Reels prefetch, were still allowed to run. The restriction only took effect once the switch was off on Android's own page and I backed out of it.
How to open the hidden page:
- Without a PC: install Activity Launcher from the Play Store, search "AppBatteryUsage", open Settings > "Battery optimisation" (.Settings$AppBatteryUsageActivity). You can also make it a home-screen shortcut. It opens Android's own list of every app, with a filter for All / Unrestricted / Optimised / Restricted. Tap an app for its page.
- With ADB, the whole list:
adb shell am start -a android.settings.IGNORE_BATTERY_OPTIMIZATION_SETTINGS
- With ADB, one app's page:
adb shell am start -a android.settings.VIEW_ADVANCED_POWER_USAGE_DETAIL -d package:com.instagram.android
On that page, the switch on the right is "Allow background usage" (off = Restricted). Tapping the words instead lets you choose Optimised or Unrestricted. Back out of the page afterwards; the change only commits when you leave.
How to check it actually worked:
adb shell cmd appops get com.instagram.android RUN_ANY_IN_BACKGROUND
"ignore" means restricted; "allow" or "No operations" means it isn't.
adb shell cmd appops query-op RUN_ANY_IN_BACKGROUND ignore
That lists every app that's actually restricted.
WHAT I CHANGED (NO ROOT)
- Santander and Instagram: Allow background usage OFF on Android's own battery page, confirmed restricted (their background jobs are now blocked)
- Every third-party app moved back to Optimised
- Disabled Facebook App Manager, Services and App Installer (pm disable-user)
- Location: Wi-Fi scanning and Bluetooth scanning OFF
RESULTS SO FAR
- Before (10-day average): about 7h SOT per 100%, about 52h per charge, screen-on drain about 9.3%/h, overnight standby 0.6-0.95%/h.
- After, day 1: 1h16m screen-on with 90% left.
CHECK YOUR OWN PHONE
BioCatch is used by a lot of banks, so if you have a banking app installed, it's worth running the sensorservice check.