I have updated to v4.0 on my device and it is working well
I updated to v4.0 but I am having issues (Please share the issue details on this thread)
I am not able to update to v4.0 (Please share the issue details on this thread)
0voters
To report issues with the build or applications raise an issue on gitlab. Ideally first discuss the issue here and check if users of the same device on this build are having the same issue.
When sharing your feedback or issues, Please add the following details
Vendor Name
Device name
Device CodeName
Version of /e/OS or Stock which existed previously
Refer this guide to share more details in your feedback
Do not share test build information on the forum or in this thread
This thread has been created specifically for posting information on official and community /e/OS builds.
To understand the difference between build types refer this guide
Please do not post information or links to /e/OS test builds on the forum.
The test builds are as yet untested and under development and may in some cases cause user devices to soft brick.
Such information can confuse other users who do not see these builds in the updater.
Remember not all users who come to this forum are experts in installing and formatting custom ROMs and can end up seriously damaging their devices by trying out these test builds
If you are genuinely interested in helping with the testing activities and also understand how to fix and do some minor level of testing on custom ROMS, you are welcome to join the testing team
As part of the testing team you can share your comments on the dedicated testing telegram channel.
Hello,
My main device is an FP6 running the official version 3.7.3, purchased from Murena.
I also have a test device—a Samsung S10—which was running the 3.7.3 A16 Community Edition.
I haven’t installed many apps on it yet; it’s still a fresh setup.
No accounts have been configured yet, either.
I just managed to update it to A16 version 4.0—so far, so good.
However, the message I received during the update gave me pause.
It stated that the device would restart in recovery mode to install the update.
That is a bit confusing.
Is it correct that the update leaves the existing configuration—apps, settings, and accounts—intact and simply updates the existing system?
I have quite a few apps, accounts, and settings configured on my FP6, so it would be really annoying if I had to set everything up again from scratch.
will 4.0 become part of an ota-update anytime soon for current a15-users? if yes, will this update a15>a16 ota?
or is a manually update a15>a16 with the 4.0-image the only way to get 4.0 / a16? if this is there a way to preserve current userland? or would this flash everything?
Vendor Name: Xiaomi
Device name: Redmi Note 10 Pro
Device CodeName: Sweet
Version of /e/OS existed previously: v3.7.3
Is the device Rooted / Not rooted: not rooted
Installation was smooth and fast.
Everything is working perfectly so far, with no issues encountered.
Big thanks to the team for all the hard work and dedication. Your efforts are greatly appreciated!
Please note the v4.0 release is a staggered release like all our releases.
Which means every day a small set of devices are released. The reason we do our releases in this manner, is we support 250+ devices.
If we release all builds at the same time the servers will crash as we will have thousands if not millions of simultaneous hits on the servers.
Official builds usually get released during the last days of the release process.
The release process usually takes about 7 to 10 days. For example, for v4.0 we started the release on 11 June and it will complete for all devices around 22 June.
In the first instance, just wait for the Updater (aka System updater) to offer the update when you press the Refresh button.
Official devices (Murena purchased and other) do not recieve updates in the first half of the release cycle so there is no need to be anxious that it has not arrived.
Staggered Release: 11 June to 22 June
Do not share test build information on the forum or in this thread
