For the time being the update has been backed out from Xperia XA2 devices, while we investigate how to detect and avoid the following boot issue:
On some Xperia XA2 family devices the device may boot to recovery mode after the update and refuse to boot normally. To fix this the boot mode flags need to be cleared.
This can be done in the recovery shell with command:
dd if=/dev/zero of=/dev/mmcblk0p64 bs=256 count=1
After running that, exit the shell and reboot the device from the menu.
This should not happen on other device, but if it does, note that the partition is model specific, so do not run that command on other device models.
Release highlights 5.0.0.71
Getting all the things we want in Sailfish 5.1 will still take some time, so we decided to pick some of the improvements as an update to the 5.0 branch. First and foremost to get those improvements earlier to you, but also to get a good base image for the next Jolla C2 batch.
These are the notable improvements of 5.0.0.71 compared to 5.0.0.70.
A lot of fixes in AppSupport for connectivity and other things.
Connectivity fixes mainly affect Jolla C2 with AppSupport 13 and AppSupportRadio implementation.
AppSupportRadio implementation treat mobile data as WLAN connection by default.
AppSupport 13 Chromium Webview update to 139.0.7258.143 version.
Settings > AppSupport has some new switches to control AppSupport behavior, so make sure to check that after the update.
Recovery mode enabled on Jolla C2, Xperia XA2, and Xperia 10.
To enter the recovery mode on Jolla C2:
Turn off the device and turn it back on
When the device vibrates at start, press volume up key
Press volume down key to confirm booting to recovery mode
To enter recovery mode on Xperia XA2 and 10:
Turn off the device
Hold down the volume down key and turn the device back on
Hold down the volume down key until the recovery mode text appears at the top of the screen.
For other Xperia devices the recovery mode still requires booting the recovery image with fastboot, but we are working to fix that too.
Factory reset enabled on Jolla C2
The reset can now be initiated from Settings > Reset device
If your device is from the very first batches, it won’t have the factory image on board and the reset will fail. To fix that see the flashing instructions, and flash the super partition with fimage.img001
Browser now remembers Find-in-Page search terms, excellent small contribution from the community!
All recent Sailfish OS release notes can be found here.
Upgrade FAILED on XA2. It has never ever failed before in 5 years..
After the upgrade I’m seeing some black console with the following text:
RECOVERY: Connect USB cable and open telnet to address 10.42.66.66
When I connect with telnet I get:
Jolla Recovery v2.0
Welcome to the recovery tool!The available options are:
1. Reset device to factory state
2. Reboot device
3. Shell
4. Perform file system check
5. Run sshd
6. Exit
Running the file system check results in:
Type the number of the desired action and press [Enter]:4
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
2 logical volume(s) in volume group “sailfish” now active
e2fsck 1.47.0 (5-Feb-2023)
root: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (229018, counted=229017).Fix? yes
Free inodes count wrong (117363, counted=117361).Fix? yes
root: ***** FILE SYSTEM WAS MODIFIED *****
root: 36239/153600 files (2.0% non-contiguous), 410983/640000 blocks
Opening encrypted filesystem, you will be prompted for your security code.
Enter passphrase for /dev/sailfish/home:
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Inode 133649 extent tree (at level 1) could be shorter. Optimize? yes
Inode 524148 extent tree (at level 1) could be shorter. Optimize? yes
Inode 917392 extent tree (at level 1) could be shorter. Optimize? yes
Inode 917398 extent tree (at level 1) could be shorter. Optimize? yes
Inode 929397 extent tree (at level 1) could be shorter. Optimize? yes
Inode 1050394 extent tree (at level 1) could be shorter. Optimize? yes
Inode 1052282 extent tree (at level 1) could be shorter. Optimize? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/luks-home: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/luks-home: 113389/1150560 files (6.9% non-contiguous), 2268072/4601344 blocks
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
0 logical volume(s) in volume group “sailfish” now active
Done
Press [Enter] to return to recovery menu…
In this case i would vote having the Feature/Bugfix for some weeks not translate is MUCH better than having it a week or two stalled For me the best decision Jolla could make!
First observation: Android connectivity is just fixed. That is huge for the C2. Hope, that the first impression holds up!
@sedric or anyone else with XA2 that booted to recovery after the update, it would help if you could check the oemandroidboot.xboot= value from /proc/cmdline.
And if you could run a couple of tests:
Boot to recovery by turning off the phone and then turning it on while holding down the volume down key.
in recovery shell check hexdump -C /dev/mmcblk0p64 and if it’s zeroes or has other content
reboot the device to see if it boots normally again
Do a “warm boot” to recovery by running reboot recovery from command line as root and do the same checks as for 1.
Update went smoothly on C2. Dunno if bugreport worthy but the android apps seem to be stuck in landscape mode after the upgrade. Following the situation. Prior to landscape-stuckness watched a youtube-vid with android web-browser and exited out of it after receiving a message. Now Im here.
Edit: fixed itself somehow. No longer am I mr. sideways.
Thanks for the reports, the good news is that it does not leave the boot mode information in the misc partition after booting again to the recovery mode. So probably those are some leftovers from the past.
I added this as know issue, and the fix, in the original post.
I did over-the-air update my both Xperia 10’s from 5.0.0.67 resp. 68 to 71 and rebooted. Everything’s fine.
Thank you Jolla!!!
edit: The power off bug is now solved on both devices. To switch the phone off, long press PWR button until device shuts down works. Device now stays off and doesn’t reboot any more.
But pressing PWR button a little bit shorter until Power button appears on screen and then press PWR button on screen still shuts down and then reboots immediately or within few seconds.
Long press PWR button and VOL UP at the same time until phone vibrates 3 times still works as an emergency option but not more necessary in normal usecase.
For the rest, everything works as before, that means fine. edit: see edit below
edit: Found a bug: Sound recording on Android apps no more works on both phones!
Apps: Oscilloscope & Audio Spectrum Analyzer from F-Droid.
Audio recording with Sailfish OS Audio Recorder app works fine.
Any ideas what do to fix this?
Thanks for any hint!
It probably isn’t the bootloader version alone, but also the the misc partition contents, and it’s not completely clear where it comes from. And it’s a bit difficult to reproduce and test as the older stock Xperia firmwares are not available for flashing.
For me the best decision Jolla could make!