• davidgro@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 days ago

    Initially I didn’t see it on the package in the image, so before reading the article it looked like a prank product, just an empty case to hold your eSIM.

  • IcePee@lemmy.beru.co
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 days ago

    Not gonna lie, if this were a real product, I’d be tempted. You see, for Android phones, ESIM registration uses propriety Google code. A programmable device that can present to the phone as a regular SIM would be a boon.

      • iturnedintoanewt@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 days ago

        Grapheneos people have said so repeatedly in their documentation. At least for the activation part. Once the eSIM is downloaded/installed, it’s no longer needed i think.

        • calm.like.a.bomb@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          7 days ago

          Oh, wait… I didn’t think about this and didn’t know it was closed source, even though when I think about what google is doing lately it’s no surprise.

      • pirat@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        8 days ago

        I’m not the person you’re asking, but I have some evidence to support the case that making it work without proprietary code is a problem. GrapheneOS, a privacy-oriented Android-based smartphone OS, write in their usage guide:

        By default, GrapheneOS has always shipped with baseline support for eSIM, where users can use any eSIMs installed previously on the device. However, in order to manage and add eSIMs, proprietary Google functionality is needed. This is fully disabled by default.

        eSIM support on GrapheneOS doesn’t require any dependency on Google Play, and never shares data to Google Play even when installed.

        Edit: The fact that they haven’t implemented eSIM functionality without using the proprietary Google stuff, indicates to me that it’s either impossible/blocked or simply too hard with practically nothing in return to have been prioritised (yet?)