That’s why I asked for Settings - About phone - Android version (tap on it) - /e/ version, which has all the necessary info in the same format like the filenames on the download pages … which isn’t short either, but leaves no questions open, and since Android 10 you can long-tap it and copy it to clipboard 
.
You’re on the stable release channel.
Thanks for the tip (the long-tap), good to know that!
I think the red message about data shouldn’t be there : when you see it, it’s too late to do anything anyway. And by the way, I didn’t encrypt my data partition… strange o_O
Thanks again for your help
Thank you for the precision, as you said it was the other way. 
But I cannot see the V0.23 dev. Maybe it is not available yet. Same when I check for update on the phone.
Now, when you check in Settings > Security, do you find that your phone is encrypted?
As a matter of fact I do… But I didn’t chose to encrypt my phone… And there’s nothing under users identifiers.
So TWRP is right, but I don’t know the password either…
TWRP has limited powers in an encrypted Samsung, so you noticed the warning about this. It seems at least a few people experienced this.
TWRP can still do some things … if it asks for a password, just press cancel. This applies defaut_password which is expected to have been applied.
/e/ users posts where they have experienced OTA Upgrade issues share the hashtag #ota-upgrade.
Great to know the cancel trick to apply the default_password!
And thanks for the link too.
You are right with that, it can be confusing if you don’t deal with TWRP for much else, but the bottom line for OS updates is that it’s harmless.
You can either ignore it, or if it really bothers you, you could try to install the /e/OS recovery provided on the ROM download page instead of TWRP.
(But I don’t have a Samsung device and even the manual OS install docs for starlte refer to TWRP when installing a custom recovery, so … pick your poison .)
Android did. In recent Android the data partition is encrypted by default. You can set your own decrypt method (password/PIN/pattern/…) for this by setting an unlock method for your lock screen.
… another user reported that if you change Settings > System > Developer options > Update recovery, to ‘yes’, then at your next update /e/ Recovery will overwrite the TWRP recovery.
I can live with it of course, as long as it doesn’t get me into troubles It’s just strange to see some kind of alerts about something you didn’t done… now, thanks to you, I know what this message means and where it come from. Again not a big deal : the phone works perfectly.
Didn’t know about the encryption by default on recent android.
Again, many thanks to you guys for your advices and informations!!
#ota-upgrade
No OTA Upgrade for my Galaxy S9+ star2lte
Android version: 0.22-q-20220228166119-stable-star2lte
The phone is not from the e-shop and I have installed it with the easy installer.
From that information, you are on Android 10 q and you are on stable ! There is no further OS Upgrade available !
Are you referring to Touch sensitivity - #2 by Polli ?
No 0.23 OTA upgrade for my S8 Dreamlte (0.22-p) too.
My son received 0.23-q OTA on his S9.
The dreamlte stable build is yet to be released.
Hi, still not receive v0.23
Curently on 0.22-q-20220226166118-dev-starlte on my samsung S9
Curent build e_starlte-userdebug 10 QQ3A.200805.001 eng.root.20220226.001011 dev-keys,dev-release
Why I can’t have update, it seems other people with the same phone have already access to the v0.23.
Is it something that i have missed ?
Thank for any help/explanation 
The same here, still on 0.22:
0.22-q-20220226166118-dev-starlte
e_starlte-userdebug 10 QQ3A.200805.001 eng.root.20220226.001011 dev-keys,dev-release
The Problem is, that many persons here, who are saying, that they already received 0.23 on their S9 or S9+ are on the stable channel.
Therefore it is very important to give this additional information in those statements, otherwise it leads to confusion.
My problem with the release politics by /e/ is, that there seems to be no official statements regarding the affected devices yet.
This is somehow disappointing, because it creates some loss of trust in the security of those devices. The state of the security update is 5th of january, in terms of security these are ages.
My S9 Plus is on 0.22-20220228166119
I keep manually searching on both my units, but no new updates found.
Yes. Still have those sensitivity issue. Thougt that it will be fixed with 0.23. So I stuck on 0.22 with these problem?