Is that worth doing? There’s nothing wrong with it at the moment and I’m not sure what might improve.
Its a pity that it still require such an amount of work. My Battery is dying from 18% to 61% Degradation in the last days if i can trust the BMS (Usage App from Storeman). You know theres this weird Battery-Level-Stall on this Port, my hope is that a newer kernel fix it. I have received a new Battery from Sony, sadly produced 20W47, so week 47 (End November) of 2020. Our Sony-Sparepart-Dealer told me Sony has stopped Battery production for the xz2 compact. I had ordered the C2 already but like my xz2 compact too much to let it go.
That Battery had far more Charge-Cycles like 86, but maybe not completely (0%-100% and 100%->0%)
I changed the battery to mine and works just fine. Never noticed extremely weird things with the battery.
Maybe its better to stay on Kernel 4.14 with this port because:
I successfully changed the battery. The charge cycles were reset, but it still shows the available capacity and degradation from the old battery. I tried to fully charge it to 100% and waited until the current was down to 14 mA, but I never received the ‘Battery completely charged’ message from SailfishOS. I also let it drain down to 2% when SFOS shuts down. Is there any experience with this unit regarding when the BMS will calculate the correct available capacity, or is there some kind of reset mechanism?
Added 06.09.2024:
Reset the Charge-Full-Value by Hand after Battery-Change doesn´t work:
[defaultuser@XperiaXZ2Compact ~]$ cat /sys/class/power_supply/battery/charge_full
1113000
[defaultuser@XperiaXZ2Compact ~]$ cat /sys/class/power_supply/battery/charge_full_design
2899000
[root@XperiaXZ2Compact defaultuser]# echo 2899000 > /sys/class/power_supply/battery/charge_full
bash: can’t create /sys/class/power_supply/battery/charge_full: Permission denied
After 33 charging-cycles the BMS doesn’t recognize the new Battery and still show the values of the old one. Conclusion is, the measuring of the capacity works only downwards and there seem to be a missing reset-mechanism in AOSP at least for this Hardware (Sony XZ2 Compact).
When receiving my C2, i will do some tests with the XZ2c regarding BMS-Reset and will share my knownledge here, how to do it.
Edit: Added 12.11.2024
Ok, so SailfishOS and/or AOSP seems to save this Data outside of the scope of Stock-Android on this Sony XZ2 Compact Device.
I first try to reflash verndor.img and dtbo.img to reset this → nothing changed
Then i flash Stock-Android on it and make some charge/discharges, see AccuBattery-Screenshot below, Battery-Capacity is calculated correctly.
At last i flashed back SFOS and it still shows the old Values!?!?
And the Emma-Tool doesn´t offer Battery-Recalibration after flashing Stock-Android to it.
Maybe a stupid question, but it is possible to ssu-update this port on the software-level to SFOS 5.0.0.62 or need it some more work to archive this?
No, that’s not a good idea - it could break something. I’ll be able to deal with it only in April, not before.
3 Likes
Ok, good to know, thanks for your response.
3 Likes
Wait. Didn’t tama moving to 5.x.x required a new port?
As far i understand, it requires a new port when
new Software-Binarys with updated Kernel were used. But in this case they remain the same, because never change a running system.
Why would it require new port? I may have missed something - was expecting that I would just need to recompile the stack against 5.x and we will be all set
Probably people are thinking of an update to the new aosp binaries.
1 Like
My mistake. Nevermind.
1 Like
@rinigus It seems the user (Stromfinger) from Jollauser.de was successfully able to upgrade his XZ2 Compact to 5.0.0.61 with the sfos-upgrade-tool.
So maybe no more work required from your side!?
1 Like
its not that much is needed on my side, but some changes maybe required. I maybe able to look into it at the upcoming weekend, let’s see.
Actually, maybe its time for one of the users to take over the port and deal with the next release. I am rather stretched and don’t plan to update my device any time soon. So, it would make sense to pass the port over to someone who is interested in it.
Update instructions are available in the port docs. So, it shouldn’t be too difficult.
1 Like
I did successfully updated from 4.6.0.13 → 4.6.0.15 → 5.0.0.62 with great sfos-upgrade tool!
Updated using sfos-upgrade to 5.0.0.62. Running post_sfos-upgrade showed that device adaptation repos were messed up, which as I understood will be fixed once OTA will be released by rinigus, and that chum is broken. Haven’t noticed any other issues yet.