since the update the battery drainage of my XA2 Ultra is completely erratic
one day i may have it as low as 20% discharging in 24 hours
though at mostly 75% over 24 hours it is very high (much higher than previously)
in these 24 hours the phone usage is mostly the same, a few phone calls a few SMS and reading a few emails, a few web page opened, nothing else
what can be done ?
this added to a rather slower response of the web browser makes me wonder where is the improvement
Hey, I experienced massive battery drainage after updating my XA2 from 4.6 to 5.0. I couldn’t figure out what caused the drainage. After some days, I decided to reflash my phone. One hour of work and it works like a charm now. Way faster than with 4.6 and normal battery behavior again.
Look in Taskview with apps like Crest to see if there is a task or process that has a high CPU load or runtime
@teertinker
reflashing, why not but i do not know how to do that on a device with a running SfOs
@fingus
i thought Crest was not working since 4.* version (at least i cannot install it since that version)
Lighthouse does only show some process(some look like being not displayed) with almost 0% cpu usage
and i do no know of any other app doing this task
Top command with root?
So this is crying after a Long-Term Observation Tool or daemon that identifies the energy-hungry process(es)."
i managed to install Crest from openrepos version 1.12-1
i cannot see any app over a few percent
except sailfish-browser -prestart at 6% when the browser is open
yes and many other things
it looks every corrected bug induces something likes 2 new ones
I have xperia 10 lll and I praised battery drain after previous update. Now battery again drains very fast.
FWIW it could be the battery is showing signs of age, as it did with my XA2 Ultra.
I have a replacment lying around here since I switched devices, pm if interested
Works fine here. Installed from Openrepos.
But as far as I know CPU scaling etc. works differently on phones so a CPU usage of 75% might just be a sign of the system switching off unused cores.
i am restarting this thread as it seems to me things have gone worse with 5.0.0.67
before i had this high drainage one day out of around 5
now it is almost 4 out of 5
what is wrong?
could it be the sign of a tired battery?
Check if NFC is turned on, turning off NFC might help a bit
thanks for the hint
i will try out
I found out quite a while ago that there is a huge difference between my XA2 battery drain when Wlan is on and off.
Gonna test it later with graphs, but it seems like CPU is unable to sleep on screen off, when Wlan is on.
sfos will never suspend with screen on.
Mistype, I’ve corrected it. Also, I’d like to say it did not happen recently, I see the problem since about some early 4.x release. I’ve exchanged the battery for new with no noticable change.
Do you see a difference in battery drain when connected to a stable wifi vs. having wifi enabled but not in range of known networks?
I only ever use portable hotspot in close range.
But can test it too, I guess.
Drainage is about current drawn from battery, that why one needs to follow those figures.
For my Xperia 10 III the figures have been constant from 4.5 release to the newest 5.0.0.67 - between 100mA and 200mA drawn (idle, screen on, Signal app on, AppSupport on, no Wifi, no BT).
i may have found a way around
every time i could see the discharging rate going over, lets say 2%/h,
i turned wifi off, wait a certain time, around one hour
the discharging rates drop downs to a very small walue
turning wifi on again
and the discharging rate is again at normal value below 2%/h
this is with Mobile data off
and happens with XA2 Ultra since version 5 and going worse and worse with every new version
it does not happen at all with a Fairphone2 running SFOS3.3
Just poking around in the fog: My XA2 also has sometimes high battery drainage since 5.x. I experience a very high correlation with using bluetooth (speakers). After using them I usually switch bluetooth off - but it the battery keeps discharging at a very high rate. Restarting the bluetooth via help tools seems to solve the problem in my case. But I havn’t investigated the problem further.