I already checked it, information is there only sometimes after the release has started. I asked only if there is anything special about this new release (rather than just bug-fixes).
I could have looked in the closed tickets for this release but that wasn’t the point.
The release notes will be there eventually, and they sometimes really contain important stuff, updating without heaving read them is not the most clever plan available anyway (ahem, reminder to self).
I’m not in favour of handing out redundant summaries, else users will just complain they weren’t told something in the summary which was in the release notes.
Wait for the release notes. Read them. Then update. Simple for everybody involved.
Device CodeName: gta4l
Version of Stock which existed previously: T505XXS7CXB1 Binary BIT-7 (seven)
The device is Not rooted
The installer does not recognize the existing stock Android 12 firmware (binary 7). Therefore, the /e/ installation process of e-2.1-t-20240605406922-dev-gta4l is aborted with the following message, although stock firmware Android 12 is installed::
The same error message is displayed when trying to install with Stock Android 12 firmware T505XXS7CXB1 ~ BINARY-7:
e-2.0-t-20240508399779-dev-gta4l
e-1.21-t-20240324389105-dev-gta4l
lineage-21.0-20240506-microG-gta4l
lineage-21.0-20240510-nightly-gts4lv-signed
The bug was recognized and corrected by the LineageOS Android Distribution (LOS) and since version lineage-21.0-20240517-nightly-gts4lv-signed a problem-free installation is possible again.
Vendor Name: Motorola
Device name: Moto G 5G XT2113–3
Device CodeName: kiev
Version of /e/OS which existed previously: e-2.0-t-20240508399779-dev-kiev
Version of Recovery which existed previously: e-2.0-t-20240508399779-dev-kiev
Device is Not rooted
Manual update via Local Update worked flawlessly, ven if the package installation took a few minutes.
But only you yourself could have given this answer to you, because you singling out this one modification is subjective, others might find other things notable, see above .
Xiaomi
Redmi Note 7
Lavender
No root
/e/OS UPDATE for 2.1
I performed the update via OTA on my Redmi Note 7 Lavender, using image.recovery 1.21, because as previously reported, image.recovery 2.0 is not functional (at least on Lavender). So far, everything seems to be working normally, but something that was a little discouraging was the persistence of the security patch, still the same as on “February 2nd” while we are in “June”. If there is any news, I will report back. For now, thank you for the exhaustive work and congratulations to the MurenaOS Team.
Vendor Name Motorola
Device name moto g32
Device CodeName devon
Version of /e/OS or Stock which existed previously e-2.0-t-20240507399779-dev-devon
Is the device Rooted / Not rooted rooted