Hey I was using eOS as a daily driver for 5 years on 2 FP devices one after the other. Banking apps worked flawlessly, but A few months ago Revolut
Flagged eOS as a non supported os. I have to use Revolut daily so I had to go back to stock Fairphone OS. But this android version is a pain in the a$$, in UX perspective. Lag, missing functions, and so on.
I talked to Revolut about that Fairphone is selling it’s devices with the option of eOS as the official operating system, but they said there are some things that have to be checked to accept eOS as one official Operating system.
I attach the list below.
Is there any way to meet these criterias so I can go back using my so loved eOS? I think if these point are met, it will be useful for other apps too not just Revolut.
"Of course! For our automated checks to recognise e/OS as an official firmware, the developers would need to ensure it meets the following criteria:
- It should use Fairphone’s original cryptographic signing keys and secure-boot chain, exactly as in the manufacturer’s stock firmware.
- It must pass Google’s Compatibility Test Suite (CTS) and SafetyNet attestation without any manual overrides.
- Security patches and OS updates must be delivered through Fairphone’s official update channels, not via manual flashing or sideloading.
- It must require a locked bootloader with no root access or unlocked-bootloader options available.
Once a future version of e/OS meets all of these technical requirements, our automated checks would no longer flag it as modified, and the Revolut app should run normally."
With muuuuuch love to e/Os and the developers.
Have a nice day.
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
2 Likes
I’m impressed they answered this in detail, not just pointing to the stock OS and be done with it, although the solution still is to use the stock OS and be done with it.
There’s a Revolut fix upcoming in /e/OS 3.1 supposedly, but if this App working is so crucial for you, of course after this current malfunction and fix would just be before the next malfunction and fix (if there would even be a fix), so I totally get you want this resolved for good.
Sure, if Fairphone took over /e/OS development as well as deployment at least for Fairphones and completely reversed the degoogling, totally defeating /e/OS’s purpose.
Most user perspective in this regard is on the launcher, did you try a different launcher already?
Which functions are missing?
1 Like
This company (Revolut) is a joke, Safetynet is dead so no-one can be safetynet compliant anymore
And no bootloader option mean no more de-googled ROM
Do you mean the prominent fake news lately, which got debunked? … Directive 2014/53/EU and custom ROMs … GrapheneOS: "This EU law banning unlocking story was untrue. T…" - GrapheneOS Mastodon
Of course, it stays within every phone vendor’s power to allow bootloader unlocking or not. It seems Samsung switched over to the “not” bunch, but they were increasingly Custom ROM hostile anyway.
Nothing to do with the recent fake news, I only react to the original message of Revolut where they ask to have a locked bootloader without any option to unlock it to be compliant with them.
You probably miss the first message of this topic.
1 Like
Ah, thanks for clarifying.
Of course they would require this. How else are they as much as any other banking App supposed to assume a safe environment for the App to process most sensitive user data in?
This doesn’t mean users with unlocked bootloaders will not try to work around this, so the App in question doesn’t detect the unlocked bootloader, but once the App detects it nonetheless, it will refuse to work, as it should.
There’s nothing new to see here in that regard.