Hier soir, j’ai vu ce fil, mais je n’avais pas reçu de notification, et en recherchant de nouvelle mise à jour, l’updateur ne trouvait rien (il y a toujours un petit délais dans le déploiement sur les serveurs OTA).
Impatient, j’ai donc téléchargé moi-même le fichier depuis le site de /e/
J’ai installé sans probleme e-1.9-r sur mon Samsung Galaxy s4active (jactivelte) depuis e-1.8.1-r en utilisant
–>TWRP -->install
Toujours pas de barre de navigation sur cet appareil (utile pour l’utilisation de"scrcpy")
In English :
Yesterday evening, I saw this thread, but I hadn’t received any notification, and while searching for new updates, the updater couldn’t find anything (there is always a small delay in the deployment on OTA servers).
Impatient, I downloaded the file myself from the /e/ website.
I installed e-1.9-r on my Samsung Galaxy s4active (jactivelte) from e-1.8.1-r using
–>TWRP -->install
Issue : still no navigation bar available for this device in -->system -->boutons (usefull using “scrcpy”)
English version bellow
Je récapitule mes derniers essais
Téléchargement manuel de l’archive ZIP e-1.9-s-20230311268558-dev-gauguin.zip
Démarrage sous TWRP et installation du ZIP. => pas d’erreur
Redémarrage sour /e/OS => toujours en 1.8.1
suite à remarque de @piero sur le recovery, j’ai mis celui de /e/
Pas d’erreur dans la procédure de mise à jour mais résultat identique
Une idée pour la suite ?
Si je réinstalle le zip de la version 1.8.1, est ce que j’ai toutes mes chances que ça fonctionne en attendant la version suivante ou une 1.9.1 ?
Merci encore In English
I summarize my last tests
Manual download of the ZIP archive e-1.9-s-20230311268558-dev-gauguin.zip
Start under TWRP and install the ZIP. => no error
Restarted on /e/OS => still in 1.8.1 and mail application and notes “broken” with droid logo
following @piero’s remark about the recovery, I put the one of /e/
No error in the update procedure but same result
ny ideas for the next step?
If I reinstall the zip of version 1.8.1, do I have all my chances that it works while waiting for the next version or a 1.9.1?
Installed on rooted OnePlus 9. Took the update / install. Set Magisk to pre-flash itself in inactive slot (in-app setting), rebooted, and all is great. No hick ups, no errors. Buttery smooth.
I did an upgrade from /e/OS V1.6-r (Android R) with /e/Recovery to /e/OS V1.9-s (Android S) via adb sideload. The system boots, but the touch screen does not respond.
Pressing the power button brings up the menu with the four buttons Emergency | Power Off | Restart | Screenshot, but - the commands are not accepted.
Any screen touch is ignored by the system. The system cannot be turned off via the device key Power.
I could only get into the /e/recovery via adb reboot recovery.
I repeated the /e/OS ‘S’ upgrade via adb sideload. The result was just as erroneous.
A downgrade to /e/OS ‘R’ 1.8.1-r was not possible.
Of course I had not made a backup, but - my lifeline was LineageOS 20 by LineageOS Android Distribution.
I installed via fastboot flash dtbo dtbo.img fastboot flash vbmeta vbmeta.img
as well as fastboot flash recovery recovery.img
most recently lineage-20.0-20230314-nightly-hotdog-signed.zip.
The LOS 20.0 installation was flawless, the touch screen responds to input as it should. My installed apps and personal data remained intact.
bonjour à tous
je suis l’heureux propriétaire d’un xiaomi redmi note 7 mais la mise à jour n’apparaît toujours pas alors qu’elle est disponible dans la page dédiée à l’installation de e/OS pour cet appareil.
Y a (t’il un problème sur les serveurs ou sur mon téléphone?
Merci pour votre aide
hello to all
I am the proud owner of a xiaomi redmi note 7 but the update still does not appear although it is available in the page dedicated to the installation of e/OS for this device.
Is there a problem on the servers or on my phone?
Thanks for your help
FP4 here and exact same issue as 18yt8zhg.
The update is shown but pushing download brings the same errormessage (in my language).
Another push on the refresh button leaves the updater app and on restart the update is gone until another refresh.
If the update is first shown in the updater, and gone shortly after: for me it helped to clear the cache of the updater. After a refresh it was present again!