Danish users of Fairphone E-OS

Dear Danish users of Fairphone e-OS, besides not being able to install Mobilepay app on my new phone, I can´t install Rejsekort app either, when i get to the point where i shall use MIT ID an error message occurs. Have any of you being able to install Rejsekort app? And what did you do to make it work?

KInd regards Stella

1 Like

Hello there, im not Danish and i have no idea what those apps are for but you may need to clarify further, do the apps install and not work? Do they install and once you open them they close right away? In any case i tried both apps on samsung s9 (official e/os) and poco f6 (unofficial build) and they install aswell as open fine, if you could discribe your issue further i may be able to help.

Is the phone on A15? And is the bootloader locked?

Those apps are using the integrity API and I believe require a ridiculous amount of google safety circus BS. I am not totally sure how it works on A15, but I believe they force the integrity API on A16.

I would be very interested If these apps can run on e/os

Hi giancapp

Thank you for your answer. MIT ID is a digital tool we use in Denmark for apps we can pay with, so the Rejsekort app do get installed, but to use it I identify my self with MIT ID, and I can´t get pass that step. I guess it is easier to understand if you are danish and used to MIT ID.

1 Like

Hi wm.inter. It gets to technical for me I can´t find information about A15 or A16 on my E-os Fairphone 5, sorry.

KR Stella

From your reaction it sounds like you bought the device from Murena (and you didn’t install it yourself hence not high technical knowledge :smiling_face:).

Just to verify what version of operating system you have could you please do as explained here:

Hi @Stella

I am Danish and use the DSB app instead of the Rejsekort app. You can also check in with Rejsekort in this app.

When you try to use Mobilepay do you then have problems installing the app or is it logging in with MitID that is the problem?

Mobilepay, MitID and so on work fine om the FP4 here, but I had to uninstall the default browser, which required a lttle technical skill. Ive previously helped others do the same, though I cant guarantee, the same will ve a fix for you. Feel free to reach out in DM.

2 Likes

I can confirm the same solution works on the FP6 as well. I followed Thaulow’s instructions and got MobilePay working after disabling the default /E/OS/ browser and installing Brave instead.

This only applies to MobilePay — I haven’t tested MitID or other similar apps. The guide was written to a Linux setup, but as far as I know, the required tool also works on Windows and macOS.
https://community.e.foundation/t/mobilepay-app-has-stopped-working-since-app-update-on-fariphone-4/70674/9

I got Mobilepay working without uninstalling the default browser. I have a FP4/ running v. 3.1.4. I did the following, maybe it can work for you too:

  1. install Vivaldi browser

  2. set Vivaldi as default browser

  3. clear cache of Mobilepay (or uninstall and reinstall)

  4. run Mobilepay. Go through initial setup until you see this screen

  1. Instead of logging in with MitId on this page you press the three dots in the upper right corner

  2. this drop down menu will appear

  1. press the “open in Vivaldi browser”. The MitId login screen will now open in Vivaldi

  2. now login with MitId as you normally would.

I hope it can work for you too.

PS. I don’t use the MitId app but the key code generator (kodeviser) but I don’t think this will make a difference

Hi Mihi

I bought an FP5 e-os, so Murena was installed when I got the phone. Thanks for the link.

The idea of the link was that you post your version and others can be more helpful… I tried and failed I would say

Hi Macro

I read about the problem with the browser and Mobile Pay elsewhere, but the info was also that some had to install and make updates several times per week to keep it working.

You’re right, however, I haven’t had to re-login for months now.

Hello Danish users! Today, just prior to installing 3.2 on my A15 (E/os installed manually), Sundhedskort App stopped working. I was at the doctor with my daughter, and the app suddenly wouldn’t start saying “your phone is most likely rootet”. I’ve used the app without issues a few weeks ago.

Only change since then was to install and use the Lawnchair launcher for a few hours, but after my banking app wouldn’t start with Lawnchair launcher installed, I deleted that. I then installed KISS launcher, and both my banking app and Mobilepay are working with KISS launcher.

I tried setting the BLISS launcher as default again, but Sundhedskort app still complaints about root access.

Is it possible the Lawnchair or KISS launcher have made changes to the system, that the app now sees as root access? Where can I check up on that?

I can’t see that KISS launcher have any special access - the only half critical is access to notifications…

Thanks for any help or suggestions!

Martin

Thanks @autobahn

This worked for me too. I’m using the Qwant browser for my standard.

Does this point to the e/os browser as the culprit?

Solved this my self - sorry for the time wasted. However, the solution have solved some other issues, so I better share: I rolled back the app one version (using Aurora Store). (Was updated 6th Oct). This procedure have solved some other apps over the last past month (incl SAS airlines app and a few others). Without knowing, I suspect that google have implemented some hidden check-features or google security requirements to PlayStore apps recently, and we’re now seeing them implemented in various apps. For the same reason I’m not updating MobilePay for now.

Martin

Or the developer started putting it into the app :wink:. Google is pushing that change in the apps surely for months

Exactly. Om suspicios if Google being behind, as we’re seeing this implemented across many apps over the same time span…

Hi Autobahn

Thank you for the support. After the last update to 3.2 on my FP5 E-OS, I cant install any apps, even though I have disabled various privacy settings. I´m starting to regret having bought the FP5, as it seems you need to be a serious hobby IT developer to make the phone work with everyday needed apps.