Samsung
Galaxy S7 (SM-G930F)
herolte
before: 2.2-s-20240716417774-stable-herolte
now: 2.3-s-20240816426374-stable-herolte
Not Rooted
… all well so far
One minor issue: in 2.3 Bliss Launcher crashed once after cleaning cache of all apps and restart of phone … but has not done so again since another reboot.
(I only mention this because it is the first time I experience a crash of Bliss)
Thanks a lot for keeping that hardware alive! 
Vendor Name: Xiaomi
Device name: Redmi Note 9s
Device CodeName: miatoll
Version of /e/OS or Stock which existed previously: 2.2-t-dev
Is the device Rooted / Not rooted: not rooted
Everything OK.
SaftyNet still can not be passed. It was passing on S versions and fails on T versions as reported in separate post.Please rename kernel to not containe “lineageOS” to be able to pass.
FP5, not rooted; 2.2-t-stable → 2.3-t20240820426372-stable
All fine ! 
Apps tested - no problem: Mullvad VPN, easybank (AT), Digitales Amt (AT), Firefox, KeePassDX, Signal, FreeOTP+, Aurora, f-droid, ÖBB Scotty, Open Launcher
Remark: Got the update only today 27.
Vendor: Murena
Device: Teracube 2E
Code Name: Emerald
Version of /e/OS previously: 2.2 stable
The device is: Not rooted
OTA update no issues. Device works correctly.
Hi
I write on behalf of my wifes FP5, bought from Murena.
The update process was not smooth. The download of the update went very slow and did crash over and over again. Finally I did download the .zip file and installed it.
The issue now is, that the webdav accounts on my internal network are not working anymore. It says no connection possible and too many logins. So I did delete the accounts and now I am not able to set them up again. Error: no carddav or caldav service recognized. Guess I have to reinstall 2.2 stable with the annoying reboots.
My FP4 works without any problems, so it is a FP5 issue.
The phone has suffered these reboots from when it was brand new. I doubt clutter is the issue.
Even worse, it just happened again but in a worse way: Before the Murena logo, this time I got a bootloader requiring me to ‘pick a boot option’ - chose fast boot…
seriously… 800 euro phone :-/.
That is more than annoying! I can only tell you what I would try: Update to 2.3 - and then do a complete factory reset. Then set up the mobile phone again. If these reboots still occur, there is definitely something wrong with the hardware!
I also have a Murena FP5 and used to have these resets, sometimes several times a day. But not anymore, after I did a factory reset on V.2, as I reported.
*Vendor Name - Google
*Device name - Pixel 5
*Device CodeName - Redfin
*Version of /e/OS or Stock which existed previously : 2.2
*Is the device Rooted / Not Rooted - Not Rooted
Updated to 2.3 smoothly. No issues so far. Many thanks to the dev team
Does anybody know, where I can find the 2.2 s version for the fp5? I need to go back to a functioning version.
Info: on 2.3 the service recognition (webdav) does not work.
I did download davx5 to try to create carddav and caldav accounts. But there the same issue like in the systemapp accountmanager.
Samsung S9+ “star2lte” bought at Murena
SM-G965F
updated to /e/OS 2.3-s-20240816426374-stable-star2lte
previously running with /e/OS 2.2 (S, stable)
not rooted
Works very well,
Thanks!
Did you install the 2.3 update from August 16 or from August 20? The August 16 version is reported to have issues (beyond the ‘usual’ reboot issue), as can be read in the above comments.
Too early to comment on that. My FP5 on 2.2 did reboot several times a day. Will see how 2.3 works.
Thank you for your time and answer! I did install the update from the 20. Aug. So this is not the case.
stable/official: /e/OS stable FP5 download
dev/community: /e/OS dev FP5 download
Here’s how to find out what you are running … [HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc
Reverting to an older version means to install the older version from scratch. User data will be wiped.
Thank you for providing this information about the wiki (how to)! So I will not go back to the version 2.2 because of losing user data.
Vendor Name : Fairphone
Device name : Fairphone 5
Device CodeName : FP5
Version of /e/OS or Stock which existed previously : 2.2T
Is the device Rooted / Not rooted : Not rooted
Update was ok but there are (still) some things that dont work or are missing:
App related issues:
Vendor Name: Fairphone
Device name: Fairphone 4
Code name: FP4
Version of /e/OS which existed previously: 2.2-t
Is the device Rooted / Not rooted : Not rooted
As previously reported for 2.2:
Very dissappointing, that previously working things are not fixed with the next release…
Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Version of /e/OS or Stock which existed previously: /e/OS 2.2
Is the device Rooted / Not rooted: ?
After e/OS 2.0 + e/OS 2.1 + e/OS 2.2 → i installed e/OS 2.3-t → still Random crashes to bootanimation + back to lockscreen!
Isn’t the FP5 one of the most important mobile phones for Murena? Fairphone supports Murena out of the box, and the e/OS on FP5 hasn’t been working properly .
I am disappointed, still no solution after so long 
Chance does not agree with your statement. It would imply that many FP5 users have the same issue with their hardware, and it also does not play well with the fact there is a known bug for this exact issue with Murena.
The phone has been exhibiting this behavior:
I can additionally tell you, as I have posted before, that the issue (for me at least) ALWAYS coincides with app updates that are triggered either directly before the reboot or directly after one. Since I have not found a way to disable automatic app updates, I’m at the mercy of Murena here. If I could disable that, I could pick my own moment to deploy app updates to test my theory, but at this point I’m reasonably convinced the issue lies somewhere in this corner, connected to the automatic app updater.
I’m far less convinced a hard reset would help since the phone was brand spanking new to begin with (new, clean purchase from Murena) when it was already exhibiting this behavior. It would also be a major pain in the neck for me since I have a lot of custom stuff set up on it, up to and including 2FA auth apps that all have to be reset to do this.
So yes, I’m becoming a bit impatient with Murena (not) dealing with this. It cannot be that their flagship phone has a crippling issue that is not resolved for 4 versions in a row.
If using App Lounge,
Open App Lounge > Settings, bottom right > Untoggle Automatically install updates.