@espen, thank you for your reply.
The common theory about the Android base one uses for flashing SailfishOS making a difference is, that firmware components residing on some of the many partitions on internal FLASH memory become updated. This could be some DSP firmware (so calls or any other audio might be affected: echo, distortion, loudness etc.) or firmwares for Bluetooth, WLAN, GPS etc. Some of these firmwares are in the “Sony software binaries” one uses for flashing, but I have never seen an analysis which, and this could change from model to model. Also Jolla only utilises a single, old version of “Sony software binaries” for each Xperia model (and tests have shown that other versions do not work well), so this is a constant factor.
Long story short: If the Android base which was installed before flashing SailfishOS makes a difference, no SailfishOS update is going to change that; only reflashing to a different Android release and then flashing SailfishOS again is going to alleviate such an issue.
Are you still absolutely sure that the first Xperia 10 II you owned did not show this Bluetooth issue in exactly the same scenario (i.e. really nothing else changed, but the Xperia 10 II device)?
P.S.: If you want to know for sure, you can backup your SailfishOS partition by dd
onto SD-card via recovery (for Xperia 10 II and III this requires flashing the SailfishOS recovery onto the boot_a
partition), then flash an older Android version via Emma (a free trial install of Windows in a VM seems to be sufficient), boot Android once for a few minutes (or longer, if you like to play with it), flash the boot_a
partition with the SailfishOS recovery again, restore the SailfishOS partition with dd
from the backup on SD-card and finally flash the regular SailfishOS boot code onto the boot_a
partition again.