Hi @breversa, just seen your message after upgrading a Samsung Galaxy A3 to the Q build and I got the same warning pop-up which keeps reappearing on every restart. However, like you, I just ignore it and apparently the phone works normally.
Was yours a new install or an upgrade? As I pointed out, there is a problem with the official upgrade instructions which seem to be similar for Samsung devices as they seem to require installing the e.zip file on a device already running Android 10. If I’m correct, as for the A3, the A5 has no stock image running a version of Android 10. Samsung in its usual way abandons older phones and has no upgrades. So my impression is that the message we have both seen is simply a Google reminder to get users to complain about not having the latest version of Android.
It would be interesting to have confirmation from /e/ developers if this is the case.
So yep, you’re correct : no Android 10 for that device. But again, the message only pops at boot and can be ignored. It’s a mere cosmetic issue on the surface.
@SuzieQ : yes, that’s the message I get. Thanks for providing screenshots.
I’d love to see if the message persists in newer /e/ versions.
Hello,
I just installed e-0.17-q-20210528117214-dev-a5xelte.zip on my Samsung A5 2016 and got this error message.
I confirm that it seems to be working fine.
Have someone another option than ignore it?
It would be great if you could report it occurring on your device. If you do not already have a Gitlab account and you have any difficulties with the login, you just need to send a request to support@e.email. Thanks.
Hi aibd, I can’t sign up to your Gitlab because my “Email domain is not authorized for signup”.
Here are the logs, straight after booting up and asking the “getprop” question over adb.
Interestingly user Rd Lr on Gitlab mentions the current /e/ recovery for affected devices is also corrupt.
Yesterday I flashed it to my S5 Neo from TWRP and got a black screen/possible boot loop, hard to tell while I was pressing buttons. I tried to access recovery with the classic button combo, as well as from “Advanced restart” in /e/. Reflashing TWRP with Odin was no problem.
Indeed, everything you report fits with the bug. Any recovery built on the “bugged” build is reported to fail too - it does not work for me on Samsung A3!
The /e/ recovery, while developed to be optional with /e/ is not required. OTA updates work fine with my TWRP. You should be offered an update to e-0.19 before long, I do not have the recovery update ticked. I hope you can now get on with enjoying the /e/ experience.
The failure to login seems to be experienced by many new users! My recommended solution will work.
I tried to access recovery with the classic button combo, as well as from “Advanced restart” in /e/. Reflashing TWRP with Odin was no problem.