I read an article, which said, that the Fairphone 2 is by far the oldest Android-Smartphone with Android Support and therefore got a new Android-Update.
Now, there is eSIM.me, which already equips the Fairphone 3 with eSIM technology. And as the compatibility with eSIM_me depends on the Android Version of a smartphone, there is a good chance, that the Fairphone 2 will support eSIM via eSIM_me.
If this is the case, the Fairphone 2 will be by far the oldest smartphone, which supports eSIM technology. And as we see the eSIM technology as a very ecological technology, we would see this as a tremendous sustainable approach.
So, can someone confirm eSIM_me running on a Fairphone 2? You will just find out by downloading the eSIM_me App (https://app.esim.me) and running it for the first time, as there is an automatic compatibility check.
If the compatibility check says it is compatible, please do not wonder, that you can not choose the Fairphone 2 on our site - we did not index for such old smartphone, yet.
I am excitedly looking forward to any response on this!
In principle all phones running Android 9 and higher should be compatible as it includes by default the OMAPI support.
We do not know why they are doing it, but some manufacturers âremoveâ the OMAPI functionality when they define the ROM - so if there could be an adjustment in defining the Fairphone 2 ROM, which would include OMAPI, the Fairphone 2 should support eSIM_me as good as the Fairphone 3 does.
I suspect that this is happening because the modem software from Qualcomm has not been updated for a while, and thus doesnât include any new features that were introduced in Android 9.
If you want @Max_eSIM.me I could submit a bug report for the A10 beta to find out whether this is the case.
Hi, that would be great!
All which needs to be done is to enable the system feature âandroid.hardware.omapi.uiccâ.
So, it is not really a bug, but it had been missed to specify this functionality in the system features of the Fairphone 2.
Adding android.hardware.secure_element@1.0 and SecureElement to the build leaves us with the following errors:
I SecureElementService: main onCreate
I SecureElementService: No HAL implementation for eSE1
I SecureElementService: No HAL implementation for SIM1
Much of the references to secure element I found were somewhat related to NFC and we neither have NFC support on FP2 nor do we have an actual embedded secure element - apart from the usersâ SIM card of course.
This is where I stopped investigation, unfortunately it doesnât seem to be trivial adding support for this feature. Itâs probably missing some plumbing in the telephony stack and possibly even in the modem firmware.
Conclusion: Itâs more work than just enabling a feature flag unfortunately
there was indeed a type, the system feature is âandroid.hardware.se.omapi.uiccâ and is part of Android since version 9. Is related to the HAL implementation for SIM1 (and potentially SIM2 on a Dual SIM device).
The NFC implementation can be ignored, as it is related to eSE1, which is not present as you write.
So if you could concentrate on the HAL for SIM implementation, is sufficient.
I am not sure if it helps, but FP3 has this system feature enabled, so maybe you can get some reference from there.