@wetab73, no I didnât hide that. Actually just unhide it. Itâs a valid question. Iâve been saying many times that we keep community informed and I do my best to hold on that. Thank you for your understanding.
Thank you very much, @rainemak. Letâs hope that some information can be disclosed soon as literally the last units of 10 IV vanish from stores as we speak, and the 10 V is getting low on stock, too. Lots of us will be very grateful if we can make a conscious (rather than blind) choice of which phone model to buy while theyâre still available. Thank you.
P.S. It is not obvious whether the 10 V will be supported, considering that AOSP binaries for the 10 V have NOT been published by Sony yet, unlike 10 IV binaries available since 2022.
They announced it 20 October 2023: Sony´s Open Devices Program welcomes Xperia 10 IV and 10 V | Developer World
And released it 2 November 2023: Software binaries | Developer World
Oh, thatâs great, thank you. So it looks that the list on their Open Devices portal has not been updated.
https://developer.sony.com/supported-devices-and-functionality#secondary-menu-desktop
Indeed
Well, there isnât much differences between the IV and V so hopefully both will be supported. Anyway, for reasons that wouldnât interest anyone here so I wonât elaborate on them, I will need to make a blind choice and get one of them within the next few days⌠I hope itâll be a hit rather than a miss.
Come to think of it; should an EULA be acknowledged by the user?
I dont recall clicking on any âI AGREEâ buttons in the latest update? Is the EULA valid and binding in this situation?
In the EULA it is written in section Sailfish OS Terms of Use:
You agree to these terms by downloading or using Sailfish OS, any included additional components and all documentation (âSoftwareâ) or by clicking on the âAcceptâ button next to this Agreement when downloading, installing and/or using the Software.
You did though, when you chose âINSTALLâ after reading âBy installing this software update, you are acknowledging and agreeing to the terms outlined in the Sailfish OS End User License Agreementâ.
(At least Iâm assuming this is about what the update info said. I have no idea how it goes if you update through Terminal.)
That is correct, thanks!
In practice, I believe that the legally important change with the EULA update is this bit here:
-This is an Agreement between you and Jolla Ltd, including its affiliates
-and suppliers (collectively referred to as âJollaâ or âweâ).
+This is an Agreement between you and Jollyboys Ltd., including its affiliates
+and suppliers (collectively referred to as âusâ or âweâ).
The contractual partner of the end user has changed from Jolla Ltd to Jollyboys Ltd. I have no idea if the previous version would have allowed Jolla Ltd to assign the licensing agreement to a third party or not, but this at least takes care of that anyone could claim that they have not entered into a legal agreement with any entity known as Jollyboys Ltd and that Jollyboys Ltd or their representative has no legal competence in a matter that could arise.
I just found that you all also need to read new privacy policy.
At this point we wanted to take the opportunity to review our privacy policy, and the personal data we store about our users. The practical changes are not huge, but here are the key points:
- The legal entity changed from Jolla Ltd. to Jollyboys Ltd. We are still the same team, just under a new name.
- Added information about the 3rd party service providers we use, and clarified some wording of the privacy policy in general.
- Removed phone number and address from the Jolla Account information. We do not really need them, so there is no reason to keep them.
We would ask you to now read our revised privacy policy, and mark that you accept it by logging in to your Jolla Account and ticking the accept box.
I guess you will get the same email as I did.
Indeed, they should mention if IV and V will be supported. I guess that will come out with Sauna changelog and blog post 
@rainemak made the following posts last month regarding future devices:
I think Iâm right in saying that theyâve always been cautious about officially announcing support for new devices, itâs a shame Sony have yearly releases 18-24 month gaps would be ideal for our niche in terms of having a port ready before theyâre marketing the next device.
Isnât this âproblemâ easily solvable by supporting every second model? Letâs say that only odd (or even) models are supported by SFOS. Or, alternatively, whichever model is available (and suitable in terms e.g. availability of AOSP binaries) every second year.
Itâs been a month since then, so itâs not that weâre too impatient. Itâs just that soon itâll be a real challenge to buy those devices.
Hence the request wasnât to give official statements or commitments but just about any unofficial heads-up. Even something like âmost probablyâŚâ would be very helpful to make the choice.
Isnât this âproblemâ easily solvable by supporting every second model?
Yes and no - in that you are halving the device availability windows for any prospective SFOS customers, because Sony will still only be producing each device for one year.
Imagine the forums posts:
Enthusiastic prospective SFOS user: âd00d!, so excited to join you guys in the joyous world of mobile linuxâ
Grizzled old forum veteran: âcome back in 2026, second hand Xperia 10VIâs disappeared from ebay four months back.â
Oh, come on!
The never ending device discussions are off topic here. There are plenty of threads already!
You READ this far?!
Colour me impressed.
Oh, did someone mention hia favorite bug or tablet refund already? 
Like @attah kindy commented earlier, discussion is going off topic here. Whilst we normally do not close release notes topics, but this will be soon closed.