Are you signed up for Early Access releases?
i tought it unneccessary to de-activate the apps the updater messaged might be not compatible and running the update ended in a #bootloop. Guess I must re flash now.
After i unlocked the sd-card (cryptokey) the sd-card didnāt automount as before.
First i didnāt understand why my music (media) didnāt work until i saw that my sd-card was unlocked but not mounted.
Now i need to first unlock the sd-card then click it again and chose to mount it.
I also experience bugs with the phone app on my Xperia 10. The installation of 4.4.0.58 with sfos-upgrade worked without errors.
The first outgoing call on the X10 after restart works, but the phone app GUI crashes immediately. The call works, I can talk with the other end, but I cannot end it obviously without the app interface.
The second outgoing call on the X10 also crashes the app immediately. The called phone on the other side rings once, then shows a missed call.
An incoming call on the X10 also crashes the phone app. Meaning the phone rings without showing anything but the main screen.
Internet works both in native and android apps.
Several restarts didnāt change anything. version --dup finds no further updates. Any hints for solving this?
I did do that. I even did that again. Still a lot more space is used than expected.
Does anybody know what is /odm
directory for?
Solution to my problem:
devel-su zypper dup
Phone app is working again as intended.
Quote from https://source.android.com
ODM Partitions
Android 10 includes support for buildingodm
partitions using the Android build system.
About ODM partitions
Original design manufacturers (ODMs) customize system-on-chip (SoC) vendor board-support packages (BSPs) to their specific devices (their boards). This enables them to implement kernel modules for board-specific components, board-specific daemons, or their own features on hardware abstraction layers (HALs). They might also want to replace or customize SoC components.
In lower Android releases, such customizations prevented the use of a single vendor image for devices with the same SoC (or with different SoCs, but in the same family). In Android 10 and higher, you can use a separateodm
partition for customizations, which enables you to use a single vendor image for multiple hardware SKUs.
XA2 Ultra updated through the GUI just fine.
I have to say, after not using SFOS for a couple of years, this feels so mucher closer to a finished product. Yep, finally time to ditch Google and run SFOS as a full time daily driver. Fantastic work by the team!
Edit: Has anyone had an issue with other (not the included system app) linux music players not being able to access external sdcard storage?
What linux player do you use? so i can test if it works for me.
As i wrote before sd-card doesnāt automount any more after unlocking (cryptokey) so one need to press the icon for the sd-card one more time to mount it.
Maybe you need to mount the sd-card to use it.
Iāve tried daedalus music player, but that would be a great explanation as to why it wouldnāt read it. Let me try again.
Edit: Unplayer picked it up almost immediately. Iām a happy man.
is this update available also for the āfreeā version from cmd line?
Right now Iām hitting the:
REFRESHING CACHE AND DOWNLOADING PACKAGES
Resolving: 100%
Error: This request will break your system!
Finished transaction (status=2, runtime=61300ms)
UPGRADE NOT COMPLETE - Retry 1 of 9
Waiting 1 seconds before retry.
REFRESHING CACHE AND DOWNLOADING PACKAGES
and the os-info shows:
[General]
version=
codeName=
summary=
cover=
website=
lastChecked=1647896731665
downloadSize=-1
installSize=-1
removeSize=-1
downloaded=false
packagesToRemove=
Iām on 4.2.0.21 i did the:
ssu release 4.4.0
any hints?
Have you tried ssu release 4.4.0.58?
IIRC you have to go 4.2 > 4.3 > 4.4.
@tliquia right but still nothing:
REFRESHING CACHE AND DOWNLOADING PACKAGES
Finished transaction (status=1, runtime=90342ms)
UPGRADING SYSTEM
Finished transaction (status=2, runtime=246ms)NO UPDATES FOUND. Try again later.
@direc85 oh thanks, though 4.3 is not a stop release.
Updated an X compact to 4.4 and that now has the call issues my X10 ii used to have. Sometimes it just stops receiving calls, even though it shows an internet connection and mobile data works. Just doesnāt receive calls and people called me on my landline and said I was unavailable for some reason. Iām pretty sure 4.4.0 was supposed to fix exactly that, but it only seems to happen since this update on that device.
I heard otherwise:
https://forum.sailfishos.org/t/release-notes-suomenlinna-4-3-0/8495#stop-release-3
yes, just noticed.
=== post must be at least 20 characters
The first post of this thread says that every release of 4 series is a stop release. 4.3.0.12 was replaced with 4.3.0.15, but in general, 4.3 is a stop release.
well next question is what if the update stalled?
Finished transaction (status=1, runtime=129586ms)
UPGRADING SYSTEM
[67 %] [Install] patchmanager 2.3.3-10.41.1.jolla: [100 %]
updating to 4.4.0.58 now, itās like this for 5 mins I think?