This is very sad, indeed. After that long time, I expected much more than some improvements in the browser. I expected a useable smartphone.
indeed, super sexy 10iii toy rather than super sexy 10iii phone.
I’m happy about every improvement.
The update worked well as always for me on my 10III
But after all the months, I know you people had summer vacation and so on, I had been happy about a camera update or at least a way to use all three cameras.
Plus 5G capabilities.
Those are things I could and would use.
I don’t need Microsoft things and I never used VoLTE.
Waiting for 4.5 with the hope for those functions
Update Sony Xperia 10 II Dual Sim worked well. But it’s not possible to create an account with the new feature Microsoft 365.
After consenting use of terms, the browser opens for a second and then closes. The accounts dialogue shows a message Not possible to create.account. Edit: this applies brfore I can choose any server.
The browsers history shows
http://127.0.0.1:45881/?error=invalid_scope&error_description=The provided value for the input parameter %27scope%27 is not valid. The scope %27https://outlook.office.com/.default offline_access openid email%27 is not valid - it refers to a resource which is not listed in the client%27s Required Resource Access and for which the user does not have any existing consent.&state=430225797
As some others reported, with an Xperia 10 ii, I needed to hard boot (Volume +, Power) to get the device to restart.
This has not happened on previous upgrades. Although, I must admit I’ve only been using this device for 6 months (it’s a backup device).
Proper license, no android stuff. Minimal installs but for my own applications for testing purposes.
@PrhggfCKfuQ4: thanks for the useful info from your nice investigation. Would you be able to share (either here or by Direct Message if you prefer not to make it public) the domain of your Exchange account? That could be useful for diagnosing it (no need to share account name or anything like that, just the domain).
Update on my XA2 went.fine, but I got the following issue:
- once used screen rotatatin (landscape and back) in Android apps e.g. Chrome browser is not working anymore. Before no problem. Any idea how to fix this?
My Xperia 10iii updated fine and now VoLTE sort of works. When making phone calls the phone stays on 4G - but SMS does not work when VoLTE is ON…
Try rebooting once more. Also had a strange issue with brightness on my XA2 after the first reboot.
Well, I hadn’t have the chance to fill any entry, the wizard stopped before that. - I formerly have had my companies account, which became useless here as they moved to azure cloud and changed to 2fa (and restricted access to very few trusted apps like iphones or thunderbird). Could there exist remaining config files I can’t see right now, which interfere with creating a new Microsoft 365 account?
On both the 10 III and XA2 Ultra pictures of selected (quite many) contacts disappeared after the update. What’s interesting, it’s THE SAME pictures (of the same contacts) on both devices.
Again??? Really? sigh
@flypig, please give Contact photos gone a.k.a. https://forum.sailfishos.org/t/5536 some love.
Funny how the very same contacts lost pictures on two different phones. So there must be something specific causing it, it doesn’t seem to be random.
I’m so happy that I had a recent backup. Just deleting all contacts and restoring them from vcf was the quickest way to get everything back.
P.S. There is also a GOOD NEWS: the browser fix has made its way to this update so that it no longer always starts with that search page or whatever it was.
Like always one of my devices wouldn’t properly upgrade from GUI and I had to refrain to an Upgrade via CLI, otherwise no problem noticed so far.
A current LTS-browser would have been nice, but well, it seems like we are always lagging at least one LTS-release behind current development.
Same here, updating two XA2’s at the same time. One went flawless (over wifi, standard filesystem, no PIN request at boot), the other one (wifi off, encrypted filesystem with PIN request at boot) was stuck at about 100%. First time I experienced a problem updating Sailfish in years.
15 minutes later I rebooted the stuck one using volumeup+powerkey (it took a few seconds to reboot) and everything got back to normal.
Deleting browser history was trick for me for this problem.
This happend to my Xperia 10 III, too. I waited over night, but in the end I had to press both the vol up key and the power key down.
Thank you for updating SFOS, any improvement is progress. Since everyone has their own priorities and preferences, it is also seen differently:
For me personally, two updates would have been particularly interesting:
-
Tags · sailfishos/bluez5 · GitHub has unfortunately remained at version 5.58+git4 (as of sept 2021).
→ This would certainly have brought progress with Bluetooth problems for many users. -
Fix typo - min_freq for gold cores not being set by JacekJagosz · Pull Request #19 · sonyxperiadev/device-sony-lena · GitHub
Especially since it was only a minimal change.
Thank you for this update. All went well on my Xperia 10 III. I would like to have smaller updates more often, rather than wait for 3 or 4 large updates a year.