ESim-Slot not recognized (OpenEIUCC crashes when trying to access SIM slot mappings)

Apps & Core Settings
1

Hi,

I have a dual-sim Xperia V, which so far works fine. Now, I wanted to activate a second mobile provider and use the eSIM. Unfortunately OpenEIUCC doesn’t recognize the slim slot, although there should be one.
Under “About phone” in the settings menu I can see the IMEI for both slots, but device details are only available for the physical SIM slot (the box for the second eSIM slot is grayed out).
Inside the OpenEIUCC the box for “dual sim” is toggled on, but whenever I press “Slot mapping” the app crashes, so I guess there is some issue with the mapping. Is there a way to access the slot mappings via a terminal command and/or fix configs, if there is some misconfiguration?
Thanks for any hints!

1 Like
2

Can you make sure there are no updates to OpenEUICC? A month ago an updated version was published to help with a bug that had crept in preventing registrations. I believe iodéOS 6.9 should have the update included, but 6.8 did not, in that case the OpenEUICC update was made available from our F-Droid repository.

If OpenEUICC is updated, can you try resetting its data and ensuring permissions are enabled from “App Info”?

3

Hi rik,
thanks for your reply. I updated the app (which isn’t that easy once removed and reinstalled from the system apps), and tried to reset and reload, but without success. The app kept on crashing when pressing “Slot mapping” and the eSIM slot was not recognized (all permissions were granted). I even tried to untoggle “Dual SIM” and after a restart the button was gone and I couldn’t turn it on again, so it was stuck in single SIM mode.
In the end I had to reinstall the stock ROM, set up the eSIM and then reinstall iodeOS again and now it works. I have no clue where the problem resulted from, but it seems to me that OpenEIUCC was lacking some rights to access and alter the hardware configurations of the eSIM.

1 Like
4

Hi, there’s an issue with OpenEUICC on Sony devices. It will be replaced by the google esim manager in an upcoming v7 beta, which should be released in the coming week.

5

Replaced for all devices, or just for Sony devices?

If it’s the latter, will it be clear what we need to do when making unofficial Sony builds?

6

This would have to be just for Sony devices, I don’t see any discussion about needing to go away from OpenEUICC.

Sorry I don’t know what to say about what changes (if any?) are required for you to build your custom images. Maybe the iodé manifests are able to contain the device specific adjustments? I should maybe know that from my L4M building but don’t :slight_smile: