FP2 Battery Problems (drains quickly, CPU gets hot) - See batteryguide for workarounds

Now have a look at that! :open_mouth:

2% of the time, the screen is on, 98 % of the time, it is off, but the phone is still active. This makes me think “wakelock!” instantly, even though I’ve learnt that term only yesterday. :wink:

The output of Wakelock Detector makes me think that QKSMS might be the culprit:

As already mentioned in the thread QKSMS and incoming MMS, QKSMS is not able to receive MMS on my device. Perhaps it tries something and fails permanently?

Sounds plausible to me.
Maybe you could try to deactivate MMS for QKSMS? Though I have no idea if that’s possible.

In the newer release it doesn’t occur any more, but there, MMS do not work any more as well. :smiley: Sighhhhhh…

Well, as I read in the github thread link in the other thread here, it’s still a beta version.
There’s some hope, that the final version will offer a working MMS function…

It’s a long shot, but my battery reacted very badly to K9 mail. Many google-free people use that, maybe you do too?

:smiley: :smiley: … yes … Is it producing wakelocks, or what is it doing?

You can influence what it is doing e.g. by checking your account settings for how often K-9 checks for new emails.
I set checking for new emails to a 1 hour interval, and I have no problem with K-9’s battery behaviour.
Or it could be something else entirely :slight_smile: .

2 Likes

I had similar battery issues, recalibrating the proximity sensor as suggested here: Screen stops working during phone calls since new update fixed the problem for me.

2 Likes

Okay, I just set it to that. :slight_smile:

Thank you, will try that!

1 Like

I’ve similar problems just lately, without new apps installed etc. Phone gets hot, sucks battery. I thought it’s rather the mobile data than the Wifi (or malware?? How to find out? Suggestions?) Battery could be down from 100% to 1% as fast as in 20min. Funnily, when I set it in flight mode when at 1% and let it lie around, more often than not it’s back to 40 or 60% after a couple of hours without charging. So I believe there’s something wrong with the battery gauge, too, perhaps disturbed by the heat?

If the phone gets hot some apps are running amok. It might be interesting to get a logcat. Don’t let you confuse by wakelocks. They are ok, and only a sign of something running astray.
You might also want to install an app like osmonitor, which shows you the running apps and their cpu usage. Also, you’re using bbs, as i saw. Try to get an idle dump for as long as possible, then click on share and just save. This gives you a raw dump where one can see the most…
K9 is normally very good with battery (I’m using it for years now), but if it tries to send mail or scan the inbox, and at that moment your connection goes down (temporarily), it might spin for quite some time and eat battery. And then, the messaging app obviously did that also

1 Like

I use Watchdog Task Manager Lite to identify apps running amok when the problem isn’t related to wakelocks.

1 Like

My FP2 battery was 2.5 years older. I had to charge it often, usually just at night (with 5% left) but in critical days, two times. So I ordered a new battery, installed it, charged it and this happened on the first run:

(The drop at the end is me surfing this forum at 4 concurrent tabs speed)

1 day 18 hours (!) under Lineage OS 14.1, :scream: Also note that I completely disabled extreme battery saving mode (the thing that tints your bars orange), so real battery should be even better.

If your battery is old, consider getting a new one and keep your Fairphone 2 for longer! :new::battery::calling::sparkles:

1 Like

That´s a very good period. If I judge you correct you do a lot of tinkering with the phone. So considering the amount of charging cycles you may have had it´s a very good value.
My two batteries are about to reach this age too, but surely have a lot less charging cycles and still perform well.

That looks solid. I think it should be a value most users could live with.
But I believe you are a type being out of any troubles having battery draining apps running in the background.
There are users out there whom´s handset isn´t and they therefore tend to blame the poor battery performance, old SoC or OS. :face_with_raised_eyebrow:

1 Like

I however forgot to say that I don’t use GApps or any Gobble thing, practice which highly increases battery life, indeed.

2 Likes

Ok, yes that´s a point.
I can realize that if wanting to come close to your value GApps users would regularly have to keep the phone in flight mode which would then make it hardly useful.
So scrolling through the firewall log shows how active GApps are and I am wondering how the phone can ever reach deep sleep. (maybe the servers fall asleep when it´s time toooooooooo…:sleeping:)

AFAIK, Google Play Services (or whathever is now called the com.google.android.gms package) is specifically not battery-optimized. In fact, the whole point of Gobble pushing battery optimizations forward is forcing app developers to use Google’s push notifications, copying the Apple’s iOS model of centralization-or-GTFO (because noone wants to ask each of their users to disable something positive for their phone, although not for your privacy).

2 Likes

This is what my battery life looks like with my new phone (yes I know :frowning:)

I’m sooo happy! also my phone is fast and never reboots and everything works like a charm… I’m sorry I left the Fairphone movement but not sorry to have this amazing phone!!!

1 Like

Hi there,
I got a copy of BBS and got lots of dumps over a week. I tried with “WiFi off”, then “Wifi on, and Mobile data off”. I also set the ‘Keep Wifi on during sleep’ to ‘never’.
The phone always lost about 10% over 8 hours when idle, i.e. 1.2% per hour. This is quite a lot.
One common thread in the dumps is that there is often a bad connection. I also tried it in my workplace and had similar stats. Is there a problem with the phone that it loses Mobile signal when in sleep mode?
I posted my results to the BBS forum but the person who responded, said there is very little they can do, since there is not much development on Fairphone.
Does anyone here know how to address the issue where there is 75% poor signal?
See below a small part of the dump. The forum doesn’t allow me to upload a txt file. Google Drive link: https://drive.google.com/open?id=1asbcApL759E6-Ntrak4wciB1X-bGfSzp

============
Battery Info

Level lost [%]: Bat.: -8%(94% to 86%) [1.2%/h]
Voltage lost [mV]: (3821-3802) [2.9%/h]

Other Usage

Deep Sleep (): 6 h 14 m 35 s 95.1%
Awake (Screen Off) (): 19 m 14 s 4.9%
Screen On (): 9 s 0.0%
Doze Interactive Time (): 9 s 0.0%
Doze Idle Mode Time (): 5 h 7 m 77.9%
Doze Idling Time (): 5 h 31 m 31 s 84.1%
Sync (): 1 m 20 s 0.3%
Poor Signal (): 4 h 48 m 48 s 73.3%
Great Signal (): 1 h 45 m 11 s 26.7%
Screen dark (): 9 s 0.0%

P.S. I accidentally closed my browser but was able to get back to my draft message. Kudos to the team who run this forum!!

The forum software is called Discourse. It’s their team who made this possible - for free! Fairphone just downloaded the software and installed it on their own server.

4 Likes