Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Previous Version of /e/OS: 1.20-s (stable)
Rooted: No
I have not experienced anything wrong on my FP4, but just updated yesterday evening. I had one weird error with microG and my Amazon Music app, saying something about it couldn’t verify my license. I just hit ignore, and it went in just fine.
I’ll see if anything else happens today.
After about 10 reboots it seems to be more stable. Maybe there is some background work happening? I also got a strange notification from applounge saying that spotify want to install some further modules?
No problem with my FP4 
Ugrade from 1.17-s worked fine after having problems installing previous t Versions.
Device got stuck twice in the last 24 hours and needed to reboot. I will give it some time with that.
Also receiving the Spotify additional installation message.
Samsung
Galaxy S7 (SM-G930F)
herolte
before: 1.17.1-q-20240208379201-stable-herolte
now: 1.20-r-20240221382013-stable-herolte
Not Rooted
… no issues from what I see fo far …
(a bug has been solved as well: battery fast charging OFF now stays OFF after reboot…)
Thanks a lot for the upgrade and for keeping that hardware alive !!! 
Vendor Name: Google
Device name: Pixel 4a5G
Device CodeName: bramble
Version of /e/OS: e-1.20-t-20240222382228-dev-bramblep
Version of e-Recovery: recovery-IMG-e-1.20-t-20240222382228-dev-bramble
Device is Not rooted
| Pixel 4 (flame) | Pixel 4a5G (bramble) | Pixel 5 (redfin) |
|---|---|---|
| abl (1.0 MB) | abl (1.0 MB) | abl (1.0 MB) |
| aop (205 kB) | aop (197 kB) | aop (197 kB) |
| boot (67 MB) | boot (101 MB) | boot (101 MB) |
| devcfg (53 kB) | devcfg (45 kB) | devcfg (45 kB) |
| dtbo (8.4 MB) | dtbo (17 MB) | dtbo (17 MB) |
| n/a | featenabler (90 kB) | featenabler (90 kB) |
| hyp (528 kB) | hyp (528 kB) | hyp (414 kB) |
| keymaster (270 kB) | keymaster (250 kB) | keymaster (270 kB) |
| modem (85 MB) | modem (153 MB) | modem (85 MB) |
| product (619 MB) | product (594 MB) | product (619 MB) |
| qupfw (74 kB) | qupfw (57 kB) | qupfw (74 kB) |
| system (1.5 GB) | system (1.5 GB) | system (1.5 GB) |
| system_ext (442 MB) | system_ext (473 MB) | system_ext (442 MB) |
| tz (3.2 MB) | tz (3.0 MB) | tz (3.2 MB) |
| uefisecapp (127 kB) | uefisecapp (127 kB) | uefisecapp (127 kB) |
| vbmeta (4.1 kB) | vbmeta (8.2 kB) | vbmeta (4.1 kB) |
| vbmeta_system (4.1 kB) | vbmeta_system (4.1 kB) | vbmeta_system (4.1 kB) |
| vendor (905 MB) | vendor (781 MB) | vendor (905 MB) |
| n/a | vendor_boot (101 MB) | vendor_boot (101 MB) |
| xbl (3.4 MB) | xbl (3.6 MB) | xbl (3.4 MB) |
| ______________________ | ________________________ | ______________________ |
| Locking the bootloader | No binding specification | Locking the bootloader |
| /e/OS documentation | /e/OS documentation | /e/OS documentation |
According to the /e/OS documentation, the bootloader can be locked again on the Google Pixel 4 (flame) and Pixel 5 (redfin) - but not on the Pixel 4a5G (bramble).
The /e/OS*.zip for the Pixel 4a5G (bramble) contains the same part structure / file name as the Pixel 5 (redfin). Nevertheless, the bootloader cannot be locked again according to the /e/OS documentation.
The /e/OS*.zip for the Pixel 4 (flame) does not contain two files (featenabler, vendor_boot), but according to /e/OS documentation the bootloader can still be relocked.
Questions
Why can’t the bootloader be relocked on the Google Pixel 4a5G (bramble) with /eOS?
Is it just a question of the /e/OS documentation, i.e. has it just been neglected to specify “Locking the bootloader” here as well or is it not possible for the /e/-dev-team to lock the bootloader again for technical reasons?
Did anyone receive an update to e/os/ 1.20 yet? I know the rollout finishes only tomorrow, but I wonder why murena phones seem to be the last ones. Also I hope some problems to be solved with the updated.
Should have mentioned, I’m talking about about the murena 2.
Notification always come some days after the release (that is not yet be done)
https://images.ecloud.global/stable/two/
I understood it’s been released since February, 22
Well it’s very clear from the message you quote that the release is staggered and ends on Feb 29th. Since we are not yet Feb 29th, I would say everything is normal isn’t it.
As my original question stated I know it ends today, I was simply interested, if anyone already got it.
Release time was just extended until march, 4th.
Samsung
S6 Lite tablet (P610)
gta4xlwifi
1.19.1-r dev → 1.20-t dev
Manually upgraded without factory reset
No problems so far, all apps and data preserved
Cause you have a ‘stable’ build, you receive it the latest. If there are problems before, like major ones, you might not even get anything hence not having to bother with problems.
Gigaset
GS290
Version of /e/OS: 1.20-s-20240220382012-stable-GS290
Not rooted
Seems to be the case that since that update form 1.19.1 to 1.20 VoLTE is not working anymore, calls are working trough GSM (2G) only. Also, can’t find the settings for enabling VoLTE or WiFiCall anymore: Network & Internet → Calls & SMS → Calls and SMS both greyed out; Network & Internet → Sim-Cards → Provider → VoLTE, WiFiCall and Video call options are not listed anymore.
IMS-Status says “IMS-registration: not registered, Voice-over-LTE: not available, Voice-over-WLAN: not available, video-calls: not available, UT-surface: not available”
Samsung S10e
beyond0lte
1.19.1-s-dev → 1.20-t-dev, manually upgraded (without factory reset)
rooted
With the successful upgrade a donation will be done.
Vendor name: Samsung
Device name: Galaxy S10+ SM-G975F/DS
Device codename: beyond2lte
Version of /e/OS or Stock which existed previously: e-1.19-s
Is the device Rooted / Not rooted: not rooted
Everything seems to be working smoothly.
I have did firty flash.
I have another beyond2lte which I installed from scratch.
Fairphone | FP3+ | FP3 | previously on /e/OS 1.19-t-20240113373116-dev-FP3 | not rooted
For me it took a total of 32 minutes from first being shown the update as available until the completion of the reboot after the end of the installation process.
Vendor: Google
Device: Pixel 5
Device CodeName: redfin?
Version: 1.19.1-t-20240109372021-stable-redfin
Not rooted
I’ve not received any OTA updates since 9 Jan 2024.
Is this to be expected?
I also have no idea how I will update to 1.20 without OTA. Are there any guides on how to do this (without erasing my phone)?
Many thanks for all your work,
Daniel
If the build of /e/ 1.20 is now available for your phone, then you may update/upgrade it following the procedure given on Lineage website, for example S10e