Which rom before flashing Derpfest?Can't seem to get any Gapps to work with this. Flame results in a black screen and Nikgapps doesn't boot. Anyone else tried any other Gapps? @Schnedi - for simplicity any chance you could provide a GAPPS version as well as the vanilla one. It's less straightforward than expected to flash Gapps
Hello everybodyI moved from CrDroid to DerpFest in February and battery life on Derp had generally great back then. I flashed every new build when it came out. Then around april, I noticed a high standby battery drain similar to the one I described here. So I decided to clean flash that april build and I tested it for a few days, and after this the standby drain was good again. Then I didn't update my rom for 2 months which went suprisingly well. Battery life had been amazing for like 8-9 weeks and then it started going downhill again with the high standby drain which is why I posted it later in the thread. It's quite surprising because I was still using the same rom build and the same app setup. Then I flashed the 28-06 build to see if it would fix it but it did not. I could of course have clean flashed the rom, but I'm not sure if that would fix it. The increased standby battery drain already occurred when I didn't update my rom for two months, which implies dirty flashing was not the issue since I didn't dirty-flash a single build after that clean flash in april.
Now I still don't know why the standby drain suddenly occured again and I'm not sure if it's even related to the wakelocks because I've also had good battery life with the same wakelocks. I did notice that at the CrDroid rom thread people recommended to not use Pocket Detection because it would increase the standby drain quite significantly, I wouldn't be surprised if this rom has the same problem but I can't say for sure. I was also using Pocket Detection when my battery life was great so I'm not sure if it's that either.
However according to BetterBatteryStats, the CPU was running at 1.71 GHz for quite a long time. Why? I don't know. You'd expect the phone to be in deep sleep most of the time but my phone is running at 1.71 GHz 50% of the time and just 50% deep sleep when in standby. That could explain the issue but I don't know why the CPU would run at such a high frequency when the screen is off. On CrDroid I seem to have a similar issue so I don't know if the rom is the issue, it sounds more like the kernel is the problem.
Just flash new kernel https://forum.xda-developers.com/t/kernel-oss-aosp-11-nexus-kernel-v5-29-06-21.4286239/I don't know if it's just me but the standby battery drain is quite bad on this rom. I flashed the latest version today but it has been an issue before that. It appears that there are a lot of wakelocks caused by the android system, more specifically by "wificonnectivitymanager" and "job.deadline" as shown in the first screenshot. I have WiFi scanning disabled so I am not sure why there are so many of those wakelocks in the first place. I didn't use my phone at all for 5 hours and the battery still dropped 10% which is quite bad, it's like the system is not entering doze mode or something like that.
The second screenshot shows my battery on an 8 day window and it shows just how bad the android system battery drain really is, however the percentages are a little weird probably because those stats don't reset if I don't charge to 100%. The android system is consuming more energy than everything else, even the screen so there is clearly some kind of bug causing this.
I have had exactly the same issue before, with this rom a few months back. Then I was able to temporarily solve the problem by clean flashing the rom. However the bug came back for some reason even though I did not update my rom, purely to avoid the bug. Does anyone have any clue what could be causing this? In the meantime I think I'm going to try a different rom to see if I get the same issue.
EDIT: I've tried crdroid and it has the same battery drain issue for me, RIP... Even exactly the same wakelocks. So either this is an issue with both roms or it is an issue on my side. The former would be unlikely but I don't know how it could be an issue on my side either, since it doesn't appear to be an app causing this.
View attachment 5350177View attachment 5350175