Over years not happy with battery life

[Olli_GT]

So I did the updated to V1.20. Still Android 12 “S”.
Crazy thing for me:
The 1st night after the update was much better 8h/9%. So I thought: Yeah, now !
But after that everything like before.
All the hope now to 13 “T” !

[Olli_GT]

@Olli_GT

All the hope now to 13 “T” !

I loose the hope. Will 13 T for FP4 ever come?

[AnotherElk]

Of course it will. They started distributing the Murena FP4 in the US with much fanfare (and rightfully so), it would be pretty wild to let it stay on Android 12, which will get security updates until early next year, supposedly.

[Olli_GT]

After one day with V2.1 T I am disappointed.
A little bit more worse. 24h with less using is all I get.
V2.0 S was even a little bit more worse than the V1.1xy / V1.2xy releases.
So wrong direction…

Is there a way to upgrade firmware?
Or know somebody: Is “/e/” doing some firmware thing ?

Else I think I have you leave e.
I have no patient anymore.

[MaMaTT88]

To help you further can you send some screenshots of the android battery graph for a full cycle? Then use again the BBS (BetterBatteryStats) app and show us what you get on a full cycle too? Could be some apps causing partial wakelocks (not only kernel wakelocks are consuming).

On my FP4 during a 8h night with flight mode my battery consumption is about 5% or less. So to me the first thing to look at is what apps you use and which ones are working too much in the background…

[Olli_GT]

Thanks but one question first:
Did you see the post from tcecyk above:?

Over years not happy with battery life

the “Screen Off Discharge Rate (%/hr)” in your bugreport.zip with ~4%/hr is well above 1-1.5%/hr what I’d see as problematic during “human sleeps”. You can rule out the apps, the drainrate originates from the modems behaviour or how the kernel interfaces with it. RMNET_DFC has 600 wakelocks per hour, as in 10 per minute. That thing doesn’t sleep. Your kernel version and build string point at you using Android 12 - there are commits addressing rmnet dfc behaviour in the kernel used for the Andr…

That was the 1st credible explanation I got…

And sorry, but flight mode power consumption is not important for me. Over night is just a good test, because nothing happens. If the night needs much power, it will a leak at day too, I think. Only less visible…
And my last tests with flight mode was disappointing, too. But I would repeat it now with V2.1 T.

[MaMaTT88]

I sure don’t have tcecyk’s expertise, just a two year experience scanning my battery life in detail with /e/ on FP4 and I have a cycle of 48h between charges, sometimes 3 days (with the same kernel and build version that you have I guess). Feel free to pursue the most credible explanation then and good luck.

[tcecyk]

sorry for my “dfc” hunch not having paid off. It’s a pity bugreport profiles for battery-historian aren’t that well suited to be public. A link that you post and withdraw after a day might work? you could post the original bugreport file that I saw and a new one for others to chime in.

If you want to get to the bottom of this and I’d be in your position, I’d reset my phone to defaults and establish a /e/OS baseline and check if LineageOS uses another kernel than /e/OS via their Fairphone partnership. @mungo does extensive long term monitoring for the FP3 - Fairphone - FP3 - FP3+ Documentation Suggestions - #59 by mungo - something that’d be great for other phones

[Olli_GT]

@MaMaTT88

I sure don’t have tcecyk’s expertise, just a two year experience scanning my battery life in detail with /e/ on FP4 and I have a cycle of 48h between charges, sometimes 3 days (with the same kernel and build version that you have I guess). Feel free to pursue the most credible explanation then and good luck.

Sorry. I didn’t wanna be rude. Only sure you get the whole thread .
Did you have popular apps or common preference for bad battery life tips or what are your “tricks”?

[Olli_GT]

Yes, your are my problem… NO, of course not. Thanks again for your time and thoughts.
I do now record new data and will see the next days.

[irrlicht]

An important step for you would be to go into the Settings → Accu section → Accu usage and to show the list of most accu consuming apps. The best time to do that is when the accu is almost empty. As long as you don’t know which app causes your accu consumption you (and we) can guess a lot.

[Olli_GT]

After a few days now with fresh data/experience:

Build in display of consuming apps:
One time 22% for Android OS, other apps all <3% (and not much apps)
Last night from 100 to 68%: 1% Mobile network (and nothing else !)
…For me a sign of a system thing!

I have check one night in flight mode. That was a good night: 100 >> 95%

Last night was a good example for my problem:
7,5h no use (just two missing call)
from 100% to 64% (linear until the missing call); >6h full “doze”
Wifi ON with good signal (Developer setting ‘Mobil data always on” is “OFF”)
Screen Off Discharge Rate (%/hr): 4.41 (Discharged: 38%)
(I don’t know/found “RMNET_DFC”…)

Here four files (old A12 problem night, new A13 problem night, day usage, flight mode night)

https://rapidgator.net/file/698d2c5be049f4373942bbec13985244/Olli_GT_FP4_Battery_2.zip.html

(In the moment I don’t have a history with WiFi off, but I will do this.)

And the percent display is realistic. If it shows 1 percent, the phone is off in the next 30min.
(There is not like on FP1 the wrong calculate problem “one complete day with constant 14%”)

Maybe is the akku already dying….

So three ways I see:

1. Buy a new akku
2. Install /e/ from the scratch.
3. Install Fairphone android. Test+compare and maybe install /e/ again…
   (Is that a way to get another modem firmware? I don’t know.)
   [and there are (or was?) reports that FP4 update to A13 T increase battery drain…]

Thanks in advanced for all helps and thoughts