The latest OpenEUICC update breaks dual eSIM feature and IMS services

Apps & Core Settings
1

Hello.

I have a Google Pixel 9 with the latest firmware and I have two eSIM installed.

After the latest OpenEUICC update to version 1.6.1, IMS service can’t get registered at both eSIM. Furthermore, the app no longer can perform “slot mapping” at any configuration and returns the error "the specified mapping might be invalid or unsupported by hard…”

Also, if I disable one of the eSIMs, I am not able to enable it again either through OpenEUICC or through the standard settings.

To partially restore the eSIM functionality, I have to uninstall the updates (up to version 1.5.1). Then I can enable the second eSIM and perform the slot mapping.

I wrote “partial restore” because IMS can’t work on both eSIMs at the same time (even at version 1.5.1). IMS only registers on the eSIM in the first slot; a eSIM in the second slot cannot be registered under any settings.

Before the last IodeOS software update (OpenEUICC was kind of 1.4.x ver) IMS worked better. IMS could be registered on a eSIM that’s designated as the “primary SIM for mobile data” in the settings (settings - network & internet-SIMs - Your primal SIMs - Mobile data). After rebooting the phone, IMS services can register on the eSIM designated in the settings, while the other eSIM can’t register IMS. I mean that previously, the IMS could be registered on any eSIM slot with the correct settings configuration. But already couldn’t be registered both at the same time.

When IodeOS powered by A15 (don’t remember OpenEUICC version) everything worked fine (both esim could be activated, could perform slot mapping and IMS could registered at both esims at the same time).

I’d like to ask you to stop breaking the app :grinning_face: (it’s getting worse after every update) and fix it. I use the Pixel with IodeOS as my primary device, so not working basic functions are very critical for me.

If needed, I can send OpenEUICC logs or any other logs.

Additional: My eSIM carriers aren’t officially supported by the device (it’s a Pixel, after all). However, as far as I know, IodeOS has a bypass of such restriction.

2

So I’m not sure if what you are describing is part of an issue I’m seeing on a Brax3, with both and eSim and a Sim, but it sounds like a possibility.

I have been experiencing SMS issues when sending messages on my eSim line ONLY. Both lines are with the same carrier, so the APNs are all the same, just different numbers. I have consistnently over the last month had messages that indicate sent, but the received never recieved them. Phone calls work.

Anyway, I wanted to post in case this might be related. I’m also running 1.6.1

3

Hello.

It may be related. But I don’t use SMS, so I can’t say anything about this case.

However, I sometimes have issue with receiving incoming calls and making outgoing calls (rarely). But I’m not sure if this is a software issue or an operator issue. Anyway before A16, such a problem was not appeared either.

In my case, it’s usually issue with mobile data (IMS). I’ve been struggling with this for several months, to be honest. And now (1.6.1 ver) it is no longer possible to enable a second eSIM.

4

This sounds possibly like an issue with the number possibly being associated with RCS or iMessage? It could be eSIM related but I would suspect the other first.

5

I really need to get an eSIM for testing, just good old fashioned physical SIMs here so I am ignorant. But I do note on my Pixel 6 that I can map 2 eSIM slots (Slot 0 Port 0 and Slot 1 Port 0)?

Also I am not certain of your comment “My eSIM carriers aren’t officially supported by the device (it’s a Pixel, after all)”, I don’t know of Google restricting eSIM carriers at the hardware level?

To IMS registration, did your APNs possibly change between A15 base and A16 base? LineageOS did reformat how their default APN database and there have been some others that had this issue and needed to manually adjust their APN settings to get it working again.

6

Hi rik

I really need to get an eSIM for testing, just good old fashioned physical SIMs here so I am ignorant. But I do note on my Pixel 6 that I can map 2 eSIM slots (Slot 0 Port 0 and Slot 1 Port 0)?

I have Slot 0 Port 0; Slot 0 Port 1; Slot 1 Port 0. The system puts both esim into Slot 0, port 0 and port 1 (through standard phone settings) . OpenEUICC v 1.6.1 can’t map esim at any ports, always get error.

Also I am not certain of your comment “My eSIM carriers aren’t officially supported by the device (it’s a Pixel, after all)”, I don’t know of Google restricting eSIM carriers at the hardware level?

As I know it’s software restriction hat means that non-supporting SIM lack some features such as VoLTE и VoWIFI. There isn’t restriction for IMS registration anyway.

To IMS registration, did your APNs possibly change between A15 base and A16 base? LineageOS did reformat how their default APN database and there have been some others that had this issue and needed to manually adjust their APN settings to get it working again.

I’ve already reset ANP to default settings. I’ve also tried some custom settings. However, it had no effect. As I mentioned at first post, IMS can get registered with OpenEUICC versions 1.4.x and 1.5.1, but with some issues. These versions are already for the A16.

7

@rik IDK, and that is my fault as I did leave two important clues out… short messages, and ones with possibly an emoji, do not seem to be affected, almost like SMS vs MMS. So unless you are suggesting that short messages are handled differenly than long messages in RCS/iMessage, I’m not sure that would make sense.

The other part of this is that my primary number, which I have tasses back and forth between and iPhone and the Brax3, is not affected like this in any way.

Here is the other odd clue that I have noticed. When I send a message in the Messages app, on the eSim line, the messages that DON’T get through have a “double-checkmark” after the send. The ones that do get through get a “single-checkmark”.

Does that help supply any new ideas?

8

This is very likely an “iMessage hijacked your number and is swallowing your messages” issue: you will need to de-register it: Deregister and Turn Off iMessage - Apple Support

1 Like