It’s a software implementation though, so if you have a rooted phone or use another Android OS, you have limited options in apps that implement eSim for you.
OpenEUICC is a good one, but sometimes requires magisk modules to work.
I remember it took me half a day of fiddling to get my eSim working under Lineage.
People forget that your phone supporting “feature X” means that even though it has all the hardware to do X, it still needs to software, which might not be part of the devicetree.
For example paying for items with your phone’s NFC does not happen because of NFC capability. There are no open source solutions to Google Pay. It’s an agreement brokered between Google and Banks that allow the bankcard to be “cloned” and used via NFC, not the NFC doing any cloning of your actual bankcard
Much more likely to be the phone vendor not releasing this “absolutely basic functionality” to customisers. Some vendors hate their customers having freedoms.
I don’t think it was a basic problem, but something to do with vendor’s implementation of it not being in the device tree and so it could not just be copied over as a binary blob
It’s a software implementation though, so if you have a rooted phone or use another Android OS, you have limited options in apps that implement eSim for you.
OpenEUICC is a good one, but sometimes requires magisk modules to work.
I remember it took me half a day of fiddling to get my eSim working under Lineage.
People forget that your phone supporting “feature X” means that even though it has all the hardware to do X, it still needs to software, which might not be part of the devicetree.
For example paying for items with your phone’s NFC does not happen because of NFC capability. There are no open source solutions to Google Pay. It’s an agreement brokered between Google and Banks that allow the bankcard to be “cloned” and used via NFC, not the NFC doing any cloning of your actual bankcard
That’s not a problem with eSims, that’s just a problem with your custom ROM not shipping with absolutely basic functionality
Much more likely to be the phone vendor not releasing this “absolutely basic functionality” to customisers. Some vendors hate their customers having freedoms.
I don’t think it was a basic problem, but something to do with vendor’s implementation of it not being in the device tree and so it could not just be copied over as a binary blob