I installed 5.1.0.11 over the 5.1.0.10. The update was small and really fast, no problem.
I tried to create a Nextcloud account once again and it still failed because of the calendar… But, when providing /remote.php/dav/calendars/bananaMixer/ as the optional calendars path, it worked!
My phone seems smart once again!
Many thanks @dcaliste for the time you took to help, to debug and to fix the issue. And many thanks to the Jolla team for this update.
5.1.0.11 would not connect to my car handfree using the existing pairing (previous updates have just worked without repairing)
I had to delete the pairing.
When I got it to pair, the phone’s name in the car’s bluetooth list is blank. This is a new bug, though I have not had to re-pair the phone to the car for several years.
The first issue is that it does not pair.
The cause is that SF does not prompt for PIN, but silently uses it’s own default PIN (0000). This would only be a minor issue if SF actually said it was “trying to pair using default PIN 0000”
(I recall this is a long existing bug)
What SF displays is:
Pair with Hands Free System
waiting for other device
problem with pairing
could not pair the devices
Viewing log (note that “devel-su journalctl -u bluetooth” shows nothing)
[defaultuser@Xperia10III ~]$ devel-su journalctl
Jun 14 11:18:30 Xperia10III lipstick[3052]: [D] unknown:0 - BlueZ agent: RequestPinCode() "00:0A:30:AC:12:8D" "Hands Free System"
Jun 14 11:18:30 Xperia10III lipstick-bluetooth-ui[32845]: [D] agentAction:72 - Bluetooth pairing: try pairing with preset PIN
Jun 14 11:18:30 Xperia10III lipstick[3052]: [D] unknown:0 - Accept Bluetooth request from "00:0A:30:AC:12:8D"
Jun 14 11:18:30 Xperia10III lipstick[3052]: [W] unknown:0 - PendingCall Error: "Authentication Failed"
Jun 14 11:18:30 Xperia10III lipstick[3052]: [D] unknown:0 - Pairing finished with error: BluezQt::PendingCall::Error(AuthenticationFailed)
Jun 14 11:18:30 Xperia10III lipstick-bluetooth-ui[32845]: [D] finishPairing:94 - Bluetooth pairing: preset PIN failed
Jun 14 11:18:35 Xperia10III lipstick[3052]: [D] unknown:0 - Pairing finished with error: BluezQt::PendingCall::Error(InternalError)
So from my understanding Sailfish 5.1 migrated fron ConnMan DNS to systemd-resolved. How much memory is resolved expected to consume? In my case it seems rather high (100-200MB, but I’ve seen as much as 450 MB once)
I’m happy you get back your calendar data on the phone. But you should not have to provide the calendar path yourself. It should be autodetected… So there’s still something with a malfonction.
During weekend I experienced completely new bug, Xperia 10 III (5.1.0.11), audio worked otherwise, but during phone calls I didn’t hear counterpart and they couldn’t hear me. Tried to restart from utilities “Mobile network” and “Audio”. Neither fixed the problem, but rebooting phone did fix it. I have experienced this before, but then the audio haven’t worked at all. Now it seemed to be only affected in phone calls.
It is possible that Android 13 base is causing problems as Jolla only recommends android 12 as a base. Would need to reflash for android 11 and update OTA to android 12, but haven’t found time yet.
Is it just me, or has the general stability of SFOS really improved by updating all the low-level libraries and components? Since upgrading my Xperia 10 III to 5.1.0.8 end of May, not a single occurence of the famous “lost audio” or “lost mobile connectivity in AAS” bugs anymore. No ofono restart, no audio restart necessary in 17 days of uptime.
Generally I would say OS is much snappier and faster! But unfortunately I still have lost audio and no internet in AAS bugs present. Can I ask, what base android version (11/12/13) and blobs are you using with 10 III?
First of all, WPA3 SAE does not work with 802.11r fast roaming, and WPA2+WPA3 Mixed mode is least to say dubious and different implementations handle it differently.
SonyX 10 I does not have functional WPA3 SAE but can support the WPA2+WPA3 mixed mode networks. We had to disable WPA3 SAE on it as the implementation in driver is lacking the full support to utilize WPA3.
SonyX 10 II does have functional WPA3. That error could be looked further, we changed to systemd-resolved, so if you have some own changes related to resolv.conf it might affect. Or any other networking tweaks. Do other apps work then, like the browser, or is it just the Store app?
SonyX 10 III also to our surprize does not support WPA3 at all. It should, but there is something either with the sony blobs or the kernel WLAN driver. As of now it can support only WPA2 at max.
EDIT: the configuration is at /etc/connman/main.conf.d/10-<device>.conf as key WifiWPA3Support = none|mixed|full where none = WPA2 at max, mixed = WPA2+WPA3 mixed at max, full = WPA3 SAE at max.