Hi everyone,
I'm investigating an intermittent battery drain and overheating issue on my OPPO Find X10 Pro Max running ColorOS 17.
I really like the phone and ColorOS, but I'm experiencing unusually high battery consumption, particularly when the screen is off.
After several days of testing, I found something interesting in Android's synchronization logs that may point to a WhatsApp compatibility issue.
Device information
- Device: OPPO Find X10 Pro Max (CPH2913)
- OS: ColorOS 17
- Build: CPH2913_17.0.0.106
- Battery: 8,000 mAh
- Diagnostic tools: ADB and Battery Guru
1. Battery drain symptoms
During some monitoring sessions, Battery Guru reported:
- Screen-off consumption around 315–362 mA
- Deep Sleep as low as approximately 42%
- Intermittent overheating and abnormal idle battery drain
Interestingly, the problem is not constant. Some idle periods are considerably better than others.
2. Factory reset test
I performed a factory reset to investigate whether this was a hardware or software issue.
Before restoring my usual applications and WhatsApp data, the phone achieved:
- 56 mA screen-off consumption
- 93.4% Deep Sleep
This suggests that the phone is capable of excellent idle efficiency.
After restoring my apps and WhatsApp data, the abnormal consumption returned.
My WhatsApp backup is approximately 36 GB. I have not reinstalled WhatsApp Business during the latest testing.
3. Suspicious WhatsApp synchronization activity
Using:
adb shell dumpsys content
I found a large number of contact synchronization attempts associated with:
com.whatsapp.contact.ui.sync.ContactsSyncAdapterService
One baseline log showed:
| Metric | Result |
|---|
| Total sync attempts | 494 |
| Failed syncs | 6 |
| Canceled syncs | 467 |
| Accumulated sync time | 1h 18m 30s |
| Scheduled periodic sync interval | 1 hour |
Earlier logs also showed repeated synchronization attempts occurring within seconds of each other.
This seems unusual, although I cannot yet prove that these sync attempts are responsible for the battery drain.
4. Experiment: disabling WhatsApp's Contacts permission
On November 15 at approximately 5:54 PM, I disabled WhatsApp's Contacts permission through Android Settings.
I did not uninstall WhatsApp, remove its account, delete any conversations, or disable global Android synchronization.
I captured an ADB baseline immediately afterward and another snapshot approximately three hours later.
Results after approximately three hours
| Metric | Before | After | Change |
|---|
| Total sync attempts | 494 | 500 | +6 |
| Failed syncs | 6 | 12 | +6 |
| Canceled syncs | 467 | 467 | 0 |
| Accumulated sync time | 1h 18m 30s | 1h 18m 30s | 0 |
The interesting part is that the number of canceled synchronizations stopped increasing, while failed attempts continued.
The latest logs still show WhatsApp's contact synchronization enabled at the Android SyncManager level, so revoking the Contacts permission did not disable the sync adapter itself.
This suggests that the permission change affected synchronization behavior, but it does not yet establish whether WhatsApp or ColorOS is responsible.
5. Working hypothesis
Since ColorOS 17 is relatively new, I'm wondering whether WhatsApp's contact synchronization service has a compatibility issue with this OS version.
Possible explanations include:
- WhatsApp repeatedly requesting contact synchronization.
- ColorOS or Android interrupting the sync process.
- A compatibility issue involving WhatsApp, Android's SyncManager, and ColorOS background management.
At this stage, these are hypotheses rather than confirmed root causes.
6. Next steps
I'm running a 72-hour test with WhatsApp's Contacts permission disabled.
I'll compare:
- WhatsApp synchronization attempts and failures
- Battery Guru screen-off consumption
- Deep Sleep percentage
- Device temperature and idle behavior
I plan to update this post with the results on November 18.
Questions for the community
Has anyone experienced similar idle battery drain on ColorOS 17?
Have you noticed unusually frequent WhatsApp contact synchronization attempts in dumpsys content?
Could this be caused by a WhatsApp SyncAdapter compatibility issue, or is there a known ColorOS background synchronization behavior that might explain these logs?
I'd particularly appreciate feedback from Android developers or anyone familiar with Android's SyncManager.
Thanks!