…Enter suggestions to improve documentation in this category. Do not raise bugs or issues here…
Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services
1 Like
Hello,
I installed /e/OS on a brand new SONY XPERIA 5 III (2021 model) 3 days ago.
The installation was done without any problems with a Linux PC (don’t forget to open the terminal in the folder containing the installation files).
The phone works very well, thank you.
Small downside, impossible to deactivate or uninstall the “mail” application and the “Bliss” launcher which both lack ergonomics and which I replace with “K-9 Mail” and the “Nova” launcher.
Is there a solution to deactivate/uninstall “unwanted” applications, whether in a future update or via “fastboot”?
Hello, I have just installed /e/OS 2.9 on this phone, Safetynet is working.
I had some issue during the installation with a bootloop, I solved that by pushing volume up (phone shutdown) in the same time I connect the phone to the computer, it allow me to get back control with fastboot and I restart the installation process just after the bootloader unlock process.
So the 2nd try was the good one.
Now everything is working great and fast.
Surely this can’t be right:
“Before following these instructions please ensure that the device is on the latest Android 13 firmware.”
Why such a hard-coded magic number? Is pdx214 forever stuck on having to have Android 13 as a base for installing any version of /e/ OS (currently a14)? This line isn’t in the instructions for pdx234, for example.
Earlier on the same page:
“… downgrading Smartphones on OS versions greater than the /e/OS OS version you plan to install, can cause instability or at worst brick some devices.”
I assumed it would be enough that the Android version (and its sub-version) isn’t any newer than the /e/ OS being installed.
Documentation Suggestions is perhaps not the right point for discussion,
but briefly
I do not know the device, but I did some work attempting to build for a Sony pdx series phone. In building a custom AOSP ROM for a device the developer must base his work on a certain foundation and specify it for others.
The original developer (in the case of Sony there is an active AOSP team) other devs plus Lineage and /e/ devs are involved.
Builds might use the foundation of a recent manufacturers firmware revision or select a reliably stable alternative point.
The build you are asking about seems to have been built from the foundation stated.