More fun.
version --dup and the /usr/bin/rnd-dist-upgrade command it calls seem to do nothing. There’s no verbosity nor do I have strace on the phone to gain any verbosity.
I eventually did use curl to install sfos-upgrade as a cheat mode.
mount /sys
ssu re 4.6.0.11
/usr/bin/sfos-upgrade --verify
Of course that does (“does”) the same thing as version --dup, which doesn’t amount to much.
About strace? Anyone got an aarch64 build to put up on openrepos?
You’re running armv7hl userspace are you not?
A 10iii
~ # rpm -qa | grep armv7 | wc -l
0
~ # rpm -qa | grep aarch64 | wc -l
791
And Wireshark confirms, by eg. capturing device usb0 and displaying tcp.port == 443, that any curl requests show up just fine, but /usr/bin/rnd-dist-upgrade is just helping itself to a VSZ of 123m and sitting with it like there’s nothing more important to do.
Update for me whent fine on xperia 10 III & II
small buggs that i have encountered.
I’m eagerly reading your progress as I’m still copying over the whole home directory to the SD card. Could this be of any help? Especially the part about the URL resolver.
That’s somewhat old and I don’t have aliendalvik-control installed - I don’t even know what this - sorry
Hm, there’s a second part to the post that isn’t visible in the quote, I’ll requote it here:
If the update failed mid-way through and will not resume, then it might be the case that your libzypp package was updated while ssu wasn’t, which breaks repo resolution. In this case, people have had some luck running ‘cp /usr/lib/zypp/plugins/urlresolver/ssu /usr/libexec/zypp/plugins/urlresolver/’ as root, then trying to update again.
That’s actually more interesting! I don’t have anything named /usr/lib/zypp/ but I do have /usr/libexec/zypp/ which does contain /usr/libexec/zypp/plugins/urlresolver/ssu.
Is there something more I should know about the architecture of this thing?
Should I be able to use that somehow directly? I think not, because it hogs up even more memory than the other one and hangs around until I run out of patience and kill it.
I’ve been trying to find a statically built aarch64 binary of strace that I could add to the phone but no luck so far, as there doesn’t seem to be one for Sailfish.
I did look at the script a bit, because it does seem to do HTTPS trafficking on startup.
sailfishdocs_sfos_list="$(curl --fail --silent --show-error --insecure --location https://github.com/sailfishos/docs.sailfishos.org/raw/master/Support/Releases/README.md | cut -s -d '|' -f 2,5 | tr -d ' ')"
None of that doesn’t seem to matter, really. I got desperate enough to attempt a downgrade, which didn’t work out, but skimming through the script (because I don’t have too much time for this BS) it seems that I can give it the version I’m on now and it should work, even though it’s not listed.
Even running with bash -x /usr/bin/sfos-upgrade 4.6.0.11 it seems fine, I guess:
+ printf '%s' 4.6.0.11
+ sed 's/\./\\\./g'
+ grep -qx '4\.6\.0\.11'
+ '[' 4.6.0.11 '=' 4.6.0.11 ]
+ compar0=e4
The free trials should be due in june, then in august they have the subscription-based model;
or so I understood.
Might be I’m having this too. I have had some Android apps curiously shut down altogether when I’m trying to merely minimize them. Xperia 10 II.
Right. Thank you. 
Now it sounds good.
I don’t really know where to take this next. I can’t start dbus[0] to figure out PackageKit to maybe use pkcon to set everything on fire, nor do I have the resources to build strace, or anything.
I do wonder if ssu has some oddness - the flavour is supposed to be release, yes? Not “some-early-access-thing”?
[0] Because systemd hates chroots and I have no idea how to start dbus from the CLI - everything spews out the help text. Firmly in the “don’t have time for this BS” category now.
Yeah, I saw my Android email client close today in a way it never has before. Restarting fortunately worked fine. Keeping an eye out now.
I realized there was a cache for RPMs, like beyond what version --dup told me it was refreshing. It’s symlinked, though:
/var/cache/pk-zypp-cache -> /home/.pk-zypp-dist-upgrade-cache
The long and the short of it, the initramfs outside the rootfs has the tooling for this magic:
cryptsetup luksOpen /dev/mapper/sailfish-home sfhome
mount /dev/mapper/sfhome /home/
This is particularly tantalizing because
~ # find /home/.pk-zypp-dist-upgrade-cache/ -name \*rpm | wc -l
299
looks like it could be relevant to performing an upgrade the hard way.
And now when I say the hard way, it’s gonna be rough
~ # find /home/.pk-zypp-dist-upgrade-cache/ -name \*rpm | xargs rpm -Uvh
warning: /home/.pk-zypp-dist-upgrade-cache/packages/jolla/oss/aarch64/pulseaudio-modules-nemo-stream-restore-14.2.31-1.5.3.jolla.aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID 47394f23: NOKEY
error: Failed dependencies:
libapkd-config-parser.so.1()(64bit) is needed by apkd-plugin-notifications-fdo-ext-1.0.4-1.1.1.jolla.aarch64
apkd8 = 11.0.0.69.1-1.22.1.jolla is needed by apkd8-android-settings-11.0.0.69.1-1.22.1.jolla.aarch64
warning: /home/.pk-zypp-dist-upgrade-cache/packages/aliendalvik/aarch64/apkd-plugin-geo-qtpositioning-1.0.0-1.1.3.jolla.aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID 47394f23: NOKEY
error: Failed dependencies:
apkd8 = 11.0.0.15-1.18.1.jolla is needed by (installed) apkd8-android-settings-11.0.0.15-1.18.1.jolla.aarch64
apkd-plugin-notifications-fdo-ext is needed by aliendalvik-1.8.0-1.5.1.jolla.aarch64
nemo-qml-plugin-calendar-qt5 >= 0.7.2 is needed by jolla-calendar-1.1.15-1.11.1.jolla.aarch64
nemo-qml-plugin-calendar-qt5 >= 0.7.0 is needed by sailfish-components-calendar-qt5-1.1.15-1.11.1.jolla.aarch64
nemo-qml-plugin-calendar-qt5-lightweight >= 0.7.0 is needed by sailfish-components-calendar-qt5-1.1.15-1.11.1.jolla.aarch64
nemo-qml-plugin-calendar-qt5 >= 0.7.0 is needed by jolla-email-1.1.43-1.12.1.jolla.aarch64
nemo-qml-plugin-email-qt5 >= 0.6.30 is needed by jolla-email-1.1.43-1.12.1.jolla.aarch64
I was coming to rejoice but instead of rejoicing, there’s misery.
I resolved all the issues from the cached RPMs by splitting them into find | rpm -Uvh magic until the entire batch installed, yet there is still that “No apps running” notification after restoring the boot flashies and rebooting.
I found another thread where it seems to have been a very similar issue, where the person managed to get the phone working again from recovery. Is there anything in here that you haven’t tried?
Not really, as that also seems to be focused on aliendalvik-control.
I’ll see if I can find zypper somewhere, because I’m super confused about its role in the matter.
It’s some kind of diabolical mastermind behind packagekit-zypp in the upgrade log, maybe.
There are references to running it, but I haven’t seen it since I had the community port on the FairPhone 2 æons ago.
Have to see in a while.
Yes, I see it now with fresher eyes. This is what you get when you do the last second drive-by check on the forums on your way to hit the hay. You attention isn’t at the required level 
Update from 4.5 on my Xperia X III works fine via the normal update procedure. Can comfirm MeeCast Event Viewer issue.
Unfortunately it does not lock into into 5G network as expected plus failing to connect to 4G since the update and remains in a 2G mode. - (T-Mobile EU-Germany).
Any hint or ideas are welcome.
Update 2024-05-22:
Problem could be solved by this
solution from the documentation
Resetting oFono Settings
Trick #3
devel-su
systemctl stop ofono
rm -rf /var/lib/ofono/*
reboot
Anyhow the initial reason is not clear.