I’ve recently been prompted that a new /e/OS was available for my Google Pixel 3a: /e/OS 2.1-t-20240605406922-dev-bonito (Android 13, 5 June 2024).
So I did the update: the new /e/OS was downloaded, it was pretty long, then I pressed “INSTALL” and the installation process started.
But after something like 20mn, the process was only at around 40% of completion. I thought it was weird as usually updating /e/OS is pretty quick. So I pressed “Cancel” as I thought something was wrong for some reason, and I pressed “Install” again.
But the same thing happened and the process was very very slow. So I cancelled it again.
My question is:
_ is it normal installing this update takes that long?
_ is it safe to install?
Thanks a lot for your help,
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services](https://e.foundation/)**
I don’t know if this is still a topic, but I let the screen on during an update. I mean I avoid that the display is going dark (this is an option in the Settings) during the update is running. This keeps also other parts of the device alive, they don’t go into energy saving mode. With this an update should normally be completed in less than half an hour.
Thanks.
I’ve set the display for not going to sleep, and was able to finish the update process. It took about 20mn to complete, but note that it started directly at 40%.
This issue (going into energy saving) is probably older than /e/. It’s inherited from plain Android. But I can’t imagine why it is so complicated that this can’t be automatically handled. When an update starts energy saving could be switched off completely, and after the update it can be switched on. Others (for instance good old Blackberries) did also suggest a cable while updating but I guess /e/ goes also into energy saving when a cable is plugged in. It’s just not intended to be user friendly in this aspect.
