I donât own an /e/ phone yet. I wanted to make sure that my bankâs app can be downloaded on an /e/ phone, so I asked them. Itâs included in this list, but they told me that âtheir apps are very strict with securityâ and /e/OS are problematic because their apps depend on Google services (micro G) regarding security, notifications and geolocalization. So arenât some apps not fully supported? I guess the only workaround is either changing my bank (not interested) or having two phones. Miss the times when no phones were needed to transfer money.
Hi @Cajun, applications with a high level of security such as bankâs ones can run on /e/OS today and an update of the application can change that.
Which banking app do you use? Its users could report their experience on this subject.
Here is the reason I got from Finom on why it doesnât work on /e/os:
To be fully transparent, the issue stems from important security protocols we must follow.
Our application requires a highly secure environment to authorize payments. While we appreciate the privacy-focused approach of /e/OS on your Fairphone 6, unfortunately, Finom is not able to support this operating system at the moment.
Hereâs a bit more detail to explain why:
The Security Requirement: For custom operating systems, financial apps rely on a public list of verified boot key fingerprints provided by the OS developers. This helps our security systems confirm that the device is secure and running a trusted build, even in a âSelfSignedâ state.
The Comparison: For example, operating systems like GrapheneOS publish an official, up-to-date list of these verified boot key fingerprints for each device and build. This allows developers like us to safely verify and support those devices.
The Current Issue: Unfortunately, the developers of /e/OS do not currently publish an official list of these verified boot key fingerprints.
Because this list is not available, our system cannot verify the security integrity of the operating system. For strict security and regulatory reasons, we are unable to bypass this requirement.
Capture a debug information from /e/OS
Note that there are two methods on this link. Using adb logcat on a PC, secondly Capture a bug report from a device
Iâve recently bought an FP6 with Murena e/OS/. My bank company in Spain is Mediolanum. Iâve installed it but it would not login. It gives an error message (âsomething isnât working. We are working to fix itâ) that is not very informative. I would kindly ask for guidance. Is it better to ask the bank company to make the app compatible with e/OS/ or is it a task the e/OS/ developers should do?
It means: This can only be installed from the official app store, it refers that only can be installed from the Google Play Store. I guess there are more users suffering this, isnât it?
Just want to mention that as of 3.7, with the latest S-PushTan version (5.2.0 (31004) from 2.4.), it no longer works. According to the MicroG github, there might be a fix in upstream MicroG, which isnât included in 3.7 yet, as thatâs lacking behind multiple microg versionsâŠ
The German BBBank has lately integrated itâs app for contactless payment (âDigitales Bezahlenâ) into the banking app (âBBBank Bankingâ). Still works flawlessly with e/OS 3.7.3 official on my FP6.