Curious to know if anyone’s ever found a solid fix for this. I’ve just ran into the problem today, my phone will not charge from either the QC3.0 socket or the 5V socket on my Pinepower power supply, but charges without issue from the PD65W one. Tried a whole bunch of cables. Battery Buddy/CSD both show that the phone is “charging” but the Current is in the negatives and so the battery is draining.
I’ve even tried the quick fix listed on this thread, of rebooting the phone with the cable plugged in, and that doesn’t seem to do anything either. Port is (as far as I can tell) dust free and clean, and all the cables I’ve tried work fine on other devices. The Pinepower’s display shows that the socket is giving off 0.0A.
Using the PD65W socket is fine but I now limit the current via Battery Buddy as otherwise the phone gets hot!
In battery buddy a negative charge means discharging and positive means changing the battery.
I also have this strange dependency on the cable: with the same power supply some cables charge the Sailfish Xperia 10 iii, and after swapping to another cable on the identical power supply the phone doesn’t charge. This is reproducible and depend on the cable. I can’t tell which specifications the cable must meet to be able to charge. Additionally, I don’t know if this ‘charging refuse’ with some cables also occurs with Android on the affected Xperia 10 iii. Would be interesting to know, but reflashing effort is too time consuming for me right now to find out.
Well, guys, I reopen this topic because my Xperia 10 III started to dong charge, after a update to 5.0.0.67. Like others said, it simple dont charge, even whit the charger that always worked. Something suspicious is that the charge works, just BEFORE I enter my password; I have, them, a green light, pointing the charge, and everything works, but, if I put my password, the phone just don’t charge.
Hello,
I changed because a display crash from my good Xperia 10II to Xperia 10III and was frustrated about the bad battery performance. The X10II could hold up to 3 days but the X10III with a bigger Battery came max. up to 2 days.
The phone was new with Android 11 if I flash it with SFOS 5.0.0.67.
So I try some changes and found now the best settings. Now its hold 2days and 20h.
I want to share it with you:
I play with mcetool and found out, why the phone never charge full.
Apparently, it’s set that way by default, even if you deactivated the charging limit in the settings. It still showed 100%? Only in the Batterylog app I could see that it only fully charged when I charge it in shut down mode via the Sony kernel.
The secound thing was a hard reset with Power+Vol up = 3 times vibration. So I came unter 120mA. Unfortunately, a side effect was that some battery files were no longer being filled, and the battery log no longer worked. I hope this will work again someday. The files with no content are /sys/class/power_supply/battery/charge_full = 0 and /sys/class/power_supply/battery/time_to_ful_now = -1.
Nephros was so good and send me a update from batterylog and I changed also some lines to compare the missing charge_full variable and delet the Text for time to full. Now I can use it aggain.
Than I found out that the cpu scaling governor in performance is the lowes discharging not automatic or interactive - incredible but true for an X10III. mcetool --set-cpu-scaling-governor=performance
The next setting is mcetool suspend policy early/sdisabled/senabled:
Here are the best setting for my phone.
mcetool -senabled
I use also Situation to switch of Android and many other thinks in the night.
Maybe it hepls other users and we find out what with my missing file updates under /sys/class/power_supply/… is.
I think mce makes the major borders and if you go on 100% in battery budy the mcetool setting will end the charging at 90% but in other direction it will work. I changed because this both mce-settings at 100% now. I will see if I charge next days…