Second that for my calDAV. Same settings as on my DD (10V, 5.0) are not working on my test device (10III, 5.1). It was always working but after the update I got “Check sign-in details and try again”. After new account creation I get “Could not create account - The network request was unsuccesful”
Deactivating calendars did the trick to set-up the account and my contacts are back. When checking calendars box afterwards I immediately get the unsuccessful network request message .
Can you try creating a new Nextcloud account with calendar checked, putting just the server URL (like https://domain.org), and putting /remote.php/dav as the webdav path (Chemin WebDAV in the French translation), or even /remote.php/dav/files/<username> ?
Doing so should be equivalent to what you have done through the dav-client command-line (at least hopefully!).
I have this on my Jolla C2 as well, but it corrects the brightness back up after a few seconds when automatic brightness is enabled under SFOS. I don’t know if that automatic brightness setting is taken into account in the preboot area.
Since I installed this update the battery life is reduced substantially. On my XA2 last night I went to bed with ~50-60% left and this morning it was at 18%. It did not used to be this bad, typically around 5% overnight.
Yeah @Keto can you enlighten us if anyone is looking into WPA3 failure reports here? It’s clear this new function isn’t working right. WPA3-only mandates MFP required.
Chazaq: Since I installed this update the battery life is reduced substantially.
Do you have Flashscore installed?
I have experience that suddenly after it have been closed that it start to use 15-20% of the CPU.
When you have a heigh drain then open the terminal and write “top” and the click return. You can then mabee see the reason for the heigh battery drain.
AAS Bluetooth (which worked fine on 5.1.0.7 and .8) stopped working on 5.1.0.10 on the Xperia 10 III. The AAS BT package from Jolla store is installed, the option to route binding requests to AAS is enabled in Bluetooth settings, to no avail.
On XA2 it continues to work correctly on 5.1.0.10.
EDIT: It started to work on the 10 III after restarting Bluetooth subsystem from Sailfish Utilities.
The initial lock screen is displayed fine, and at the same contrast as everything else on my 10 iii, 10 iv and 10 v.
It must be just specific phones that it doesn’t display properly on. There seem to be quite a few of these quirks. For example the reborn Jolla weather app works fine on my 10 iv and 10 v, but not on my 10 iii (it just opens to a blank white screen), whereas on other peoples’ 10 iii it works just fine.
As stated; i keep my brightness to the minimum almost all all times. Might be related…so perhaps not so much the device type, but some bug in the software side.
Hi, major problem after update 5.1.0.10. 2 days ago got a minor update and after reboot touch screen is unresponsive and can’t continue. Is reflash only option? Xperia 10 III.