This is to announce 4.3.0.12 SFOS update for Xperia Tama devices: XZ2, XZ2c, and XZ3. Please read release notes and description below before update.
The only major port specific change was an adjustment in OBS project organization. For users, it is mostly invisible. Exception is OTA update from older scheme to 4.3.0.12. The update requires few extra steps which have been made as convenient as possible and are described in dedicated HOWTO. As soon as these steps are done, proceed with the regular OTA instructions.
At the moment of writing (2 Dec 2021), only OTA has had a limited testing. So, early adopters, please report how it went. If someone preferred to flash the image, please report as well. For those wishing to be on the safer side, wait till more users would have a chance to test the release.
This release marks 2nd anniversary since the first public Xperia Tama Sailfish port release. Public releases started on 24 Nov 2019 with 3.2.0.12-alpha1. So, enjoy the occasion.
Other than some messages related to ofono (some engine, technology whatever thing) during the upgrade the process went smooth. Will test and report any issues.
Thanks a million
Edit:
WOW and it seems i can login to my banking website with whatever was fixed in the browser. That is HUGE for me. (other than password management which is another story all together)
gives Job for pulseaudio.service failed because the control process exited with error co de. See âsystemctl --user status pulseaudio.s erviceâ and âjournalctl --user -xeâ for d etails.
devel-su journalctl --user -xe
gives
no entries
and systemctl --user status pulseaudio.service
gives
Unit pulseaudio.s.service could not be found. lines 1-2/2 (END)
I tried devel-su zyppen in -f pulseaudio
and it was successful, but didnât fix.
I have pulseaudio working fine, pulseaudio.service available and running. Opposite to your commands. What has happened on your device is hard to tell. However, knowing that you had also some strange permissions issues which I havenât seen myself nor reported by others, I suspect that something is off in your config.
I updated by OTA from 4.2, no problems, sound works and thanks to ApB for the hint about banking, I can log in tooâŚalthough some pages donât scroll properly. The only problem I had with 4.2 was the camera not opening correctly first attempt, usually I had to close it and start againâŚthis seems to be fixed, fingers crossed. Thanks again to Rinigus et al for this great port.
Iâve started getting messages from openrepos and jolla store about âcritical problemâ and ârpm exceptionâ. The jolla store says I have no apps installed. Chum shows no packages and when I try pkcon refresh I get ârpm exceptionâ. Apart from that, everything works as normal! Camera works every time too.
I wonder if your storage run full during update. It is rather strange issue that you have. Maybe RPM database needs to be rebuilt, as we had for SDK. But it is an odd issue and I donât know how well does rebuild would work
also zypper:
[root@XperiaXZ2c defaultuser]# zypper ref
error: rpmdb: fop_read_meta: /var/lib/rpm/Filetriggername: unexpected file type or format
error: cannot open Filetriggername index using bdb - Invalid argument (22)
error: cannot open Packages database in /var/lib/rpm
Target initialization failed:
Rpm Exception
âŚso itâs starting to look more serious
Edit: running it on my XZ2 (as reported on the github repo) and everything works swimmingly, aside from the minor regression in jolla-messages related to MMS. I havenât tried it yet, but apparently downgrading jolla-messages and jolla-messages-settings to their previous versions solves it. Thread here. Iâll try it later and report back.
Edit: UPDATE: Following the procedure in the thread I linked results in a PERFECTLY functional MMS experience on this Tama port. Thereâs a regression in the jolla-messages app in 4.3.0.12 which makes MMS fail for varied reasons, with minimal indication (or no indication at all) in journalctl and ofono logger. Iâve been banging my head against this for a while, and this works 100%.
