Yes, perhaps. Eg., for Xperia IV is SW_binaries_for_Xperia_Android_13_5.4_v2b_murray. I don’t know the differences between A 13 and 14.
It should be easy just to unlock boot loader and install SFOS without any backing of Android. I’ll keep Xperia 10 V as Android so far due to Samsung Galaxy Watch. Perhaps change to SFOS after 2-3 years, too.
IV and V sold in the shops here are specified to have A-12 and A-13 respectively, and one don’t need to update that, I think.
Hi community,
I was installing the update without any error messages on my Xperia 10III. Unfortunately now the Chum GUI does not show my installed apps any more. Additionally in the branch Category and Applications there is no installable application listed. A Update Repository command in the GUI runs without error message, but does not change anything. I already tried devel-su pkcon refresh with no success. The logfile in /var/log does not show any indication for a problem. Is there a way to repair this?
Go into the Chum GUI settings and override the repository.
This seems to be the case with my 10 II, too.
This IS the case with EVERY updated device until CHUM is updated as well.
Symbolic links have been added for the Chum repositories for the .25 release, so they should now work without any modifications.
I cannot install. Updater says “no connection” although there is a connection.
I had same issue, found an old post where problem fixed by delete cashe files from /etc/zypp/repos.d/* and after a few reboots managed to install using manual method.
Thank you.
@Jolla:
Since my most pressing issue with 4.5 is the now dysfunctional weather service and I have no trust in the new business owners yet, I decided not to risk the good state on my devices by installing updates that don’t do anything for me. I wish you good luck and will wait and see what people say about 4.6.
I got a message that i need to remove or revert ca-certificates before upgrading.
How do i revert ca-certificates to the stock version?
As a wise man once said 
Only fools rush in. +++
Thanks, the first time it didn’t work and i got that it wasn’t able to upgrade.
The second time the upgrade worked as expected without doing anything about ca-certificates.
We have switched the rpm compression from xz to zstd on 4.5.0.
Malicious commits found in xz.
XZ-utils in sailfish is 4 years old, so this is irrelevant as far as sfos is concerned…
Not really:
(still kinda unrelated as x86 machines running sfos are like… Handful, so doubt someone spent 2 years to target them)
Still much older than the (known) affected versions.
Look at the crossed title in screenshot: 5.6.1the exact backdoored version, luckily our openssh is not the patched one from rhel/debian
