Battery drained by mobile network, even with the dev setting on

I’ve been using e/os for a few months now on my Oneplus 9. I love it and plan to stick with it, but the battery usage is much higher than on the stock android. When looking into the battery usage in the settings, it appears that Mobile network is using by far the most battery, more than any app or other system process.

I read somewhere on the forum about disabling ‘Mobile data always active’ in the developer options, but that did not make much of a difference for me.

Is there something else I might have wrongly configured or that could otherwise impact this? Would love to debug this so my phone can at least last a day again, now it gets to about dinner time before I have to charge it again.

battery drain rate can be device specific. What device and version (full version string) is it?

there’s apps to diagnose, but also a good off-device debug option to look at drain rate

The ‘Openweather’ widget is set to 15minutes refresh interval, I’ve set it to 6 hours.
That made quite a difference in battery usage.
Tap on the cogwheel in the widget’s top right corner to set the refresh interval

The device is the oneplus 9, model LE2113. Version is: 3.1.1-a14-20250828521739-community-lemonade
I’ll look at battery historian later, when I’m home again.

@Gaea I don’t use that widget, so no improvements to be made there

1 Like

I had the same issue on FP6 with the latest v3.1.2 update. It seems to be fixed for me when I changed the network settings. Go to Settings → Network → Sim Cards → Click on your active SIM → Scroll down to the network section and turn off ‘Automatically select network’.

After that my power usage no longer showed tethering as by far the highest and it seems to be back to normal.

I have just used battery historian to get some more insights. I noticed RILJ_ACK_WL acquires a lot of wakelocks. The best I kind find about this online is this 4 year old thread, which unfortunately doesn’t help me along very much. Any other ideas perhaps?

there’s a reason for the RIL stack to aquire wakelocks, something further up the stack keeps it active. Something in userland or even a crashing modem stack. If you want me to have a look, send bugreport.zip to my username at e.email

This topic was automatically closed after 60 days. New replies are no longer allowed.