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.
I understand where this is coming from, there being factors necessitating no statements at this point, and no one wants every thread being made about [that one hot topic], but… how should it not incite a general device discussion and make it very on-topic when the highlight in the very opening post is the dropping of support for the old device base?
I consider myself a know-nothing, but I would hazard to believe that if and as 4.6.0 will the final release for older devices, it would also be the release which has the overlap in the support for the old and the new supported device base.
Not that a 4.5.0 tail-end EULA wouldn’t be an exciting thing too, but…
The part about predictive text input isn’t clear to me. Will it stop to work when I install the update? It is an offline feature, right?!
If that is the case I don’t see any reason to install the update yet.
No, only if you buy a new license:
It’s most likely some kind of license issue with the package so if you already own it you should be fine:
Haven’t heard of tablet rwfunds for quiet some time…
sudo systemctl status ironydetectd
Sailfish Community News, 7th March 2024 - EULA
“… Jolla has hinted at the possibility of supporting the Sony Xperia 10 IV and V. Notably, the Xperia V running Sailfish OS made an appearance at the recent FOSDEM event.”
Hoping that Jolla shall take for granted that both Xperias IV and V have at the moment Android 14. Do we have to return to Android 13 or does 14 also fit?
@unmaintained I buy a new device, install sailfish on it, buy a new license but won’t get predictive text with it. Do I understand that right? @rainemak could you please confirm?
@Maximilian1st Do note that the situation is said to be a temporary one, and once solved, persons with a new Sailfish X license (are promised they) will be provided with working predictive text then. Whatever the solution to the issue may be.
Once we get predictive text input issues fixed, we provide it for users who are now buying Sailfish X license.
So I think your query maybe should read “I buy a new device, install sailfish on it, buy a new license but won’t get predictive text with it now.”
Substitute “in the foreseeable future” for “now”, if you will.