FP4 battery life got worse after Android 13 update

Hmmm how much more? More than 10%?

I can try getting some numbers this week, if you do the same we can compare :slight_smile:

Do you have cell connectivity issues where you live? Sounds like your phone is desperately trying to (re)connect to the cell network all night long. Replacing cell service with WiFi (which I suppose is local, and thus reliable) fixes this. It would explain why only airplane mode fixes the battery drain.

My own FP4 has bouts of battery draining (all day) too, but I’m currently at a location with spotty cell access, so I guess that’s the main reason. It doesn’t do this usually (at least I haven’t noticed so).

I considered this being a possibility, but I’ve literally moved to a new apartment and I’ve had the same issue in both of them.

It also happens at work and I definitely don’t have any connectivity issues there.

For me the battery drain happens at the location of my office as well as at home. And it happens in flight mode (with no connection at all) as far as I noticed by now.

Okay, so it’s not the general cell service. Could it be the antenna connection inside the phone has developed a contact problem (got oxidized or some such)?
Just brainstorming. :thinking:

Now that would disprove my theory of antenna connection problems.
On the other hand there is no certainty your problem has the same causes either. :man_shrugging:

.
Battery discharging too fast problems have usually one of those 3 causes:

  1. Spotty cell service forcing the phone to send a lot more connection requests
  2. Some app doing overtime (intentionally or due to a bug, in which case rebooting helps)
  3. Battery has developed a defect and can’t hold the charge anymore

I don’t think I forgot something. Now the question is, which one it is…

For me the cause is shown as ā€œCellular Connectivityā€ in SystemPanel2 or as kernel wakelock RMNET_DFC in ?BBS

The first could indicate problematic net work.conditions while the second rather points to a kernel problem.

I have no idea. But to be honest I’ve all but given up on this phone.

I’ve done some tests 3 nights in a row now

Airplane mode with WiFi:

iPhone 13: 1%

Fairphone 4: 4%

Airplane mode without WiFi:

iPhone 13: 1%

Fairphone 4: 2%

Mobile data on with WiFi on:

iPhone 13: 5%

Fairphone 4: 42%

So yeah. Looks like I’ll be switching to my iPhone 13 for a while to see if they will ever fix the issue.

I’m gonna try with some battery apps when I have time, in the hopes of seeing if I have the same issue as the other guy.

1 Like

For the record, I do experience lately some random battery drain periods (lasting a day or two, then going away again), and SystemPanel2 (my go-to app for such questions) tells me the biggest offender is ā€œQuickstepā€ (the FP4 launcher) with 96% of battery use (and almost 2 hours of running in 24h, which is huge).
This is very strange given I lately only use my phone for a few calls/day (no app use). I had pinpointed ā€œQuickstepā€ as a potential battery hog earlier too, but much less (maybe because at that time I was using my phone’s apps more, so it didn’t stand out that much?).
Anyway, there is something strange going on. Unfortunately I’m afraid it’s some software (OS/launcher) bug, and thus very unlikely to be fixed anytime soon.

At least you found the evil process @KurtF :+1:
Have you tried to clean the cache of Quickstep launcher?

I regularly clean cache and system storage and I use Nova Launcher instead of the stock one of FPOS. Actually since my Galaxy S1 I haven’t used any other launcher, For me SystemPanel2 (I also still have it in use :wink: ) still says it is ā€œCellular Connectivityā€ in first place.

1 Like

Oops, no, I didn’t think of that.
Thanks, I’ve tried it, let’s see if it changes something.
Cache was pretty small, some 400-500 kB.

Probably not, but you never know. Then you could still try to use another launcher, instead.

Nah, I really need this phone to work. I am constantly traveling right now and my phone is my main means of communication (for voice and Internet).
I can’t afford experiments, not now!

Trying another launcher app is not really an experiment, as it is very very easy to get back again, IMO. It’s rather like trying on a new pair of trousers and if you do not like them, you use your old ones :wink:

Anyway, it was just an idea what to do, if the Quickstep launcher runs wild from time to time.

1 Like

Still, I don’t like to change trousers in the middle of the street… :smile:

Seriously, it’s not that big a problem for me, it just sometimes discharges in a day around 20% more than usual.

1 Like

It really is safe to switch. Even if the new launcher crashes instantly, the status bar and settings are still available, so switching back to a launcher that works is trivial.

1 Like

Thanks guys, but still… :grin:
I really, really depend on my phone working right now I’m thousands of km from home, and I don’t fear the big obvious crashes as much as I fear the little insidious random malfunction which will (obviously) happen when I dearly need the phone to just work (very important call incoming and such)…
Since it is just a small yet noticeable drain*, but neither constant, nor strong enough to hinder normal use, I will wait this out till I’m back home.

.
*) Between 10-20% less charge than usual after 10h of pure standby. But not always, even in an identical situation. BTW, mostly good cell reception for both providers (double SIM). :man_shrugging:

I had higher consumption since this summer during the night (airplane mode, screen off), it was in deep sleep but consumption was 2%+ per hour.

I’ve changed from quickstep to Nova launcher and I have seen dramatic improvements, from 2% to 0.5% consumption in deep sleep.

Something is off with the shipping launcher ā€œquickstepā€. I recommend everybody to try and change the launcher to see if their battery life improves.

1 Like

But if I am not wrong QuickStep should still be kept enabled because of the app switching. Wouldn’t that still make it consume the battery? Or just setting a different default launcher is enough.

FYI:
Since we’re here complaining about Quickstep, there is also another thread about this issue:
Charging Bug of FP4, with similar conclusions.

Clearly Quickstep has a problem since A13, and apparently this is not a FP4-specific issue, since it also happens on the FP5 (ā€œQuickstep is chewing through my battery on my new FP5ā€).

I am using Nova Launcher since the first day with my FP4 and for me the high battery consumption comes from ā€œcellular connectivityā€ and started from the day of the A13 update. This is something that has been ignored in my support request from the first day I opened it.

1 Like