Jolla knows why: Bluetooth obex push is using chunks of 666bytes while N9 is using 32K
Please fix your old bugs faster than introducing new ones.
@Jolla, i.e. please change your policy on this, otherwise SailfishOS will behave like an “early beta version” forever. Actually the late SailfishOS 2 releases (e.g. 2.2.1) were clearly less buggy, so this is a structural regression for long.
It’s only Early Access for now:
2024-05-20: OS version 4.6.0.11 was released to Early Access subscribers
I just checked on the Account Page — I am signed up for the early access. The update screen reports “waiting for connection…” until it gives up.
EDIT: yes, I can see the “update is ready to download” screen.
Xperia X: wording suggests 4.6 supports it, however, X is in the unsupported part of the table.
Please make it clear!
X10III: update itself went fine, but App Support is currently in an endless restart loop 
proceeding to investigate.
A “No” to both questions.
Just the original wording is slightly ambiguous:
It means that the only “official” way to obtain a root partition of 4 GB on an Xperia X, Xperia XA2, Xperia 10 and Gemini PDA is by flashing SailfishOS ≥ 4.6.0.
If one simply upgrades to SailfishOS ≥ 4.6.0 the root partition size will not be altered.
References: First message in “Sailfish Community News, 21st March 2024” and almost half of this discussion thread “Community meeting on 14th March 2024”.
Due to damage on X10 I now suffer Andy on new X10V. So I wonder is this “soon” in days or longer?
Is this final that for X10V the Required stock Android version 14 is unsupported?
Same problem here. I would’nt say “bricked”, as i think i’ll be able to reflash.
Is it possible to reflash a 4.6 directly ?
Not now in Early Access phase as full images are not yet available.
went fine without any issues on X10III for me. However, I do not have android app support on auto-start, and the first start took longer than usual. So behaviour might be different for users having app support enabled with device start.
Hi
I have the Same Problem
Same here - update went fine, AppSupport goes in reboot loop.
OS release 4.6.0 is the last one for Xperia X, Jolla C, Jolla Tablet and Gemini. So yes, we are rolling out the 4.6.0 update for Xperia X. But that is the last one.
In the table of UNSUPPORTED DEVICES, it is said: "The following devices are not supported any more after OS release 4.6:
Thanks for the confirmation. So i’m going through the install 4.5, then update to 4.6 route. In progress, seems to be running fine.
What is the CLI for performing the Early Access update?
The GUI does not provide the reason for my connection failure.
This is the loop I’m seeing with # journalctl -u appsupport -f
May 20 17:19:29 Xperia10III systemd[1]: Stopped AppSupport.
May 20 17:19:30 Xperia10III systemd[1]: Starting AppSupport...
May 20 17:19:30 Xperia10III systemd[1]: selinux: Unknown class service
May 20 17:19:30 Xperia10III systemd[1]: selinux: Unknown class service
May 20 17:19:30 Xperia10III kernel: new mount options do not match the existing superblock, will be ignored
May 20 17:19:31 Xperia10III appsupport-init[23196]: Waiting for hwservicemanager...
May 20 17:19:55 Xperia10III appsupport-init[23965]: Running hooks from start-post-hook.d...
May 20 17:19:55 Xperia10III appsupport-init[23965]: Running 50-setup.sh
May 20 17:19:55 Xperia10III appsupport-init[23965]: cmd: Can't find service: settings
May 20 17:19:55 Xperia10III appsupport-init[23965]: cmd: Can't find service: settings
May 20 17:19:55 Xperia10III appsupport-init[23965]: cmd: Can't find service: settings
May 20 17:19:55 Xperia10III appsupport-init[23965]: cmd: Can't find service: settings
May 20 17:19:55 Xperia10III appsupport-init[23965]: cmd: Can't find service: device_config
May 20 17:19:55 Xperia10III appsupport-init[23965]: cmd: Can't find service: settings
May 20 17:19:55 Xperia10III appsupport-init[23965]: cmd: Can't find service: settings
May 20 17:19:55 Xperia10III systemd[1]: Started AppSupport.
May 20 17:19:57 Xperia10III systemd[1]: appsupport.service: Main process exited, code=exited, status=1/FAILURE
May 20 17:19:57 Xperia10III systemd[1]: appsupport.service: Failed with result 'exit-code'.
May 20 17:20:00 Xperia10III systemd[1]: appsupport.service: Service hold-off time over, scheduling restart.
May 20 17:20:00 Xperia10III systemd[1]: appsupport.service: Scheduled restart job, restart counter is at 43.
May 20 17:20:00 Xperia10III systemd[1]: Stopped AppSupport.
So “F5121” should be in the supported part of the table, or not?!
I installed the update even though it recommended removing a few files.
Constant reboots started during recording. Successfully recorded after forced reboot. I haven’t tried everything, but everything seems to work.
X10iii
Microtube is gone 
And i can’t install again!
Seems to be the same here.