Top menu, “Favorite ambiences”: My understanding is that only the fav ambiences show up in the “Top menu”. On my XA2 (test device) all of them show up… ???
And if XA2/10 remain 32-bit only, what’s the reason?
libicui18n.so.66 got updated to libicui18n.so.68. Several apps like osmscout-server will downgrade because of this. Guess it is waiting for the new sdk for a recompile.
Once again the update is huge and the available memory on the rootfs is tiny. I wish Jolla would give us some tool or at least a hint what to do to cleanup rootfs.
Instead I collect and move plenty of files and directories, such as locale
, i18n
, etc and risk that the system will end up in a unusable state.
So no big version bump of the browser engine with this update?
I did:
ln -s /usr/lib/libicui18n.so.68 /usr/lib/libicui18n.so.66 ln -s /usr/lib/libicudata.so.68 /usr/lib/libicudata.so.66 ln -s /usr/lib/libicuuc.so.68 /usr/lib/libicuuc.so.66 rpm -i --nodeps Downloads/harbour-osmscout-server-2.0.0-1.137.1.jolla_.armv7hl.rpm
I flashed two Xperia 10 ii without any problem with the free version of SFX. Thanks, the image is really apreciate, my XA2 and the X of my gf are dying.
Anybody having an issue with the screen going black when replying (and sometimes opening) an SMS message after the upgrade to 4.1.0? If so, any workaround or resolution for that issue?
EDIT: For anybody else experiencing a black screen upon text input (all Sailfish and Android apps), I found a resolution to the problem. While I had uninstalled OKBoard before starting the upgrade via rpm -e --noscripts okboard-full
, this apparently left something behind that caused issues. To fix, I reinstalled okboard via pkcon install okboard-full
, followed by pkcon remove okboard-full
to remove it once more. After this procedure was done, text input worked as it should.
My phone is stuck in the black screen showing the Sailfish OS logo and text and the progress bar that went to max. It is there now for 15 minutes. Should I enforce a reboot by pressing the power button?
On X10ii, I had the screen going black (not 100%, can still see what’s on the screen), after playing with the camera and going to the home screen.
Phone stuck, and I had to reboot with volume up + power.
Wait for another 15 minutes, just to be on the safe side. Then use the Power key.
If this is Jolla C then that kind of slowness is familiar. Xperias should complete the update faster.
@adekker: Thanks for reporting. I have removed the mention of System Monitor from the release notes now. Apolologies for the incorrect claim in the notes. The are indeed copy-pasted from the release notes of the previous release. We do not have resources for testing 3rd party apps and their different versions and combinations. What we can do is to remove (or add) the apps that do not cause or do cause problems - based on your reports. If this is done in the early access phase then most of the users will not see the incorrect disclaimers.
Power key didn’t do anything even pressing for 10+ secs.
So I pressed Vol+ and Power for several seconds and after a reboot everything seems to be fine.
Thanks for the support!
Btw it’s a XA2+
Things seems working quite fine on X10ii. I tested my keyboard layouts app in aarch64 and it’s a joy.
Thanks Jolla, great job
Waiting for the update with the android layer and predictive text.
What are the chances to brick an XA2 while testing not uninstalling packages before system update? I mean, where not even reflash would work?
@amaretzek: I have never experienced myself nor heard of such a total breakage. Flashing is a powerful tool.
I (try to) maintain YTPlayer, I’ll have a look at this (not today, but soon). Thanks for the tip!
Edit: I installed it and (sigh) entered my API keys. I was able to browse categories, but couldn’t play any videos, because youtube-dl is too old (it can’t extract stream maps). I have only .so.68
libs but didn’t have to symlink the .so.66
ones. I don’t know what’s (not?) going on, and I don’t seem to be affected, so I can’t really dig deeper… Installing harbour-ytplayer
did install a few dependencies, though, but I can’t recall which ones anymore.
@jovirkku can the XA2 no call audio bug please be added to the XA2 known issues section of the release notes?