At this point I'm almost certain that discharging the phone to 0% and booting it from there has something to do with this. As I was using my phone I realized that it was on the charger because the battery died on my way home, so I checked the CPU stats. And behold:Thanks a lot for your detailed testing. I'm investigating on these problems, this reply may be updated later.
What I know for now
- The "force USB quick charging" driver makes USB charging faster (even faster than original charger), but also makes it unable to deep sleep during this period.
- According to the default core control configs, the big/little cores should be always online (see the value of "/sys/devices/system/cpu/cpux/core_ctl/min_cpus"), but it might also be offlined by thermal engine.
- Airplane mode or Power saving mode (in "Settings-Battery") may cause it unable to deep sleep. Also, the mobile signal may show 0% for about 1 minute after boot. If you turn on Airplane mode at this time or there is a phone call coming in (even if it shows no signal, it has surely got signal, so phone calls and SMS could come in), the deep sleep mode may not work. WLAN could also affect deep sleep, but the possibility is low after April rom update.
Cores are offline, deep sleep is broken. Discharging the battery to 0%, putting it on the charger and booting the phone seems to be a 100% guaranteed way to reproduce the "big cores are offline" issue. Whatever is disabling them gets triggered there, and is never overridden after several hours/days of use until the phone is rebooted.
The deep sleep issue is trickier, quick USB charging temporarily disabling it makes sense (and is a very minor bug, if even that) but there seems to be a way to "break" it permanently similar to the big cores. Some combination of turning radios on or off triggers it, and it stays like that until a reboot. In this case, most likely 21 minutes after I turned the phone on (maybe I switched from mobile data to WLAN or enabled Bluetooth by accident or something similar - I was NOT using USB charging). I'll try messing around with them and see if I can find a way to reproduce the bug reliably.
Edit: Just disabling/enabling WLAN, mobile data, location, bluetooth, battery saver, airplane mode or even the flashlight doesn't cause sleep to stop working, even temporarily. So it's probably a combination of things, or you have to be (un)lucky enough for it to trigger.
Last edited:
