I need help regarding the message of an app that the device is rooted or not certified.
I got a Galaxy S8 specifically to be able to install a “stable”.
Everything worked, update to version 0.19 is done.
Now I have installed my required apps and have encountered a problem.
The MyRenault app refuses to run.
It reports “The device is either rooted or not certified”.
It is impossible to acknowledge this message without killing the app.
Since I have another smartphone (an A3 2016 with beta 0.19 installed) I was able to test it.
There the app is running.
What is the reason that it does not run on the S8 with the stable version of /e/?
Stable or not stable /e/ has nothing to do with this.
The message is correct, even if a bit brief … /e/ is not a Google certified Android OS (that’s part of the point of it).
You might want to have a look at the microG settings and see whether you can activate something that makes the App think it runs in a certified environment, but I have no experience with this.
According to Aurora Store the My Renault App is GSF dependent (Google Services Framework), so it needs underlying Google services on the phone, which /e/ doesn’t have.
Even if you would get it to run using microG, you couldn’t count on it to reliably run forever either, Google might break compatibility on their side at any given time, with microG having to catch up again.
Thank you for your reply.
Perhaps I have expressed myself in a misleading way.
I apologize for that.
Personally, I don’t believe in the causation of Google services either, since the app runs on various platforms.
These would be /e/ (beta Android 10) on an A3 (2016), LOS 17.1, LOS 18.1 on an A5 (2017), Resurrection OS on an A3 (2017).
All these smartphones are set up without G-Services.
So it must be directly due to the OS that the app does not run on the stable version based on Oreo with this note, because on the beta which is installed on the A3 (2016), it runs.
I am currently, through the intensive testing of the system in interaction with my required apps, quite dissatisfied.
I don’t know why, during today’s test, the MyRenault app stopped working on the A3 (2016) on Android 10 as well.
It came the identical abort with the message posted above.
Curiously, when I tried it again, it suddenly worked on the S8 on Android 9 and then stopped working on any of the devices.
I then disabled the developer options on both devices so that the bootloader is not unlocked in any case. Then deleted the Dalvikcache and the cache partition in the recovery.
After repeated restarts, it now runs on the S8! but still no longer on the A3 (2016).
To me this incosistent behavior is inexplicable!
Update: a restart later it also no longer works on the S8!
This must be due to the system!
Disabling the Developer options doesn’t do anything with the bootloader. It just makes the Developer options invisible.
To lock or unlock the bootloader you would have to go through the locking or unlocking procedure on your device, and this would force a factory reset for security reasons in either case.
By the way, I have now deleted the Easy Installer installation under TWRP and manually installed the 0.17 version to track down the problem.
Same problem directly after installation.
Restart - App works.
Restart - App does not work with mentioned error message.
It seems that the problem is not with the 0.19 version.
Thanks for your answer.
Well, after further attempts, I’m no further, but quite disappointed by the inconsistency of the OS’s behavior on the S8.
After a radical delete and reinstall, the app works on the system only to display the familiar message again after restarting the device.
See picture 1 and 2.
The third image would show the app’s login screen, since obviously the app’s user login is deleted when the error message is acknowledged.
