cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as "SIM1

davecres1
Valued Contributor
Valued Contributor
 
Affected Devices: OPPO Find X10 Pro Max (CPH2913) & Google Pixel 11 Pro XL
OS Version: Android 17 / ColorOS 17
Network: EE UK (MCC 234 / MNC 30)
Summary of the Issue:
When inserting a valid, active EE UK physical Nano-SIM card into SIM Slot 1, Android's SIM Manager / Carrier Services immediately displays the message "SIM1 has been converted to an eSIM" and disables the physical SIM slot. The physical SIM has not been converted to an eSIM.
Steps Taken to Isolate the Bug:
  1. Tested multiple EE SIMs: Tested both the original EE SIM and brand-new EE replacement physical SIMs—every EE physical SIM triggers the exact same error.
  2. Tested on non-Google SIM stacks: Inserted the exact same EE physical SIM cards into an iPhone and an Honor Magic 8 Pro. Both devices register on EE and work normally, confirming the physical SIMs are active and unconverted.
  3. Tested another UK network in the same slot: Inserted a Three UK physical SIM into SIM Slot 1 on the OPPO Find X10 Pro Max—it registers immediately with zero error messages, confirming the phone's SIM reader hardware is working properly.
  4. Cleared local caches & updated firmware: Reset mobile network settings, cleared Carrier Services / telephony caches, and installed the latest device updates, but the issue persists.
Technical Conclusion for EE Network Engineering:
Because this occurs across different Android 17 devices that rely on Google's native SIM Manager / Carrier Services framework (Pixel 11 Pro XL and OPPO Find X10 Pro Max)—and only triggers when EE UK (234-30) physical SIMs are inserted—there appears to be a mismatch or erroneous eSIM entitlement flag inside EE's Android 17 carrier configuration bundle.Please can EE's technical/carrier-config team investigate and push an updated carrier configuration bundle to Google Play Services / Carrier Services so EE physical SIMs are no longer locked out on Android 17 devices?
 
1 SOLUTION

Accepted Solutions
Northerner
EE Community Star
EE Community Star

Hi @davecres1 

Firmware is from the manufacturer and therefore report the issue to them.

https://community.oppo.com/

I think the oppo is a known issue. You should disable the eSIM option maybe. 

Pixel

https://support.google.com/pixelphone/community?hl=en&sjid=5028686896141054233-EU

Thanks 




To contact EE Customer Services dial 150 From your EE mobile or 07953 966 150 for mobile and 0330 123 1105 for Broadband..

EE standard opening hours are Monday to Friday, 8am to 9pm - Saturday and Sunday, 8am to 8pm.

View solution in original post

5 REPLIES 5
Northerner
EE Community Star
EE Community Star

Hi @davecres1 

Firmware is from the manufacturer and therefore report the issue to them.

https://community.oppo.com/

I think the oppo is a known issue. You should disable the eSIM option maybe. 

Pixel

https://support.google.com/pixelphone/community?hl=en&sjid=5028686896141054233-EU

Thanks 




To contact EE Customer Services dial 150 From your EE mobile or 07953 966 150 for mobile and 0330 123 1105 for Broadband..

EE standard opening hours are Monday to Friday, 8am to 9pm - Saturday and Sunday, 8am to 8pm.

Thank you for the response and I have informed both Google and Oppo. But as I said "Because this occurs across different Android 17 devices that rely on Google's native SIM Manager / Carrier Services framework" its an issue with that.

Point to note even with Esim turned off as soon as an EE Sim is put in it comes up with"SIM1 has been converted to an eSIM" in either Google Pixel or Oppo Find X10 pro its the same issue. My Friends Honor Magic 8 pro doesn't use Google's native SIM Manager / Carrier Services framework but its own and not have an issue.

 

 

By the way already spoken to Tech support whilst in EE store. They said it was a faulty device and advised the store to replace and when they turned their demo device on they had same issue not just with an Oppo Demo but a pixel as well.Tech support said they would refer to Google the matter to google.oppo internally.

Both Oppo and Pixel do not have the issues if an Esim is used its just when the network reads any 234-30 (EE physical sim) same things happen.

Ill await a response from Google and Oppo and anything that pops up on here from EE

Ali_A
EE Community Support Team

Hi @davecres1 

It seems a very strange situation you're experiencing, especially as you're able to recreate it. 
We've not had any other reports of customers seeing this, so if you haven't done so already, I'd recommend giving our customer service team a call on 150 from your handset where a guide in the technical team can raise a ticket for this to be investigated further. 

Ali 

davecres1
Valued Contributor
Valued Contributor

Ticket was raised whilst I was in store on the phone to tech tier 2. They had not seen it before and put it down to a handset fault as they couldn't see any issues at their end even when re-sending / refreshing configuration file. They couldn't work out why no issues on a Honor android phone until I pointed out they don't use google sim manager

Issue doesn't occur when sim is converted to Esim but as Oppo can only run 1 Esim and 1 Physical sim in the phone at same time I can't use two esims. 

Since talking to them my store has replaced both the physical sim and the Esim (different numbers) so I only have two Physical sims. Now both show they are converted to Esim when they are not . A friend of mine has a pixel and we tried separately each of the new sims in his and immediately came up with the  converted to Esim but phone and data worked just like mine.

In various external forums they say its a known bug "Because Google Messages relies strictly on Android's SubscriptionManager—which ColorOS 17 / Android 17 marks as inactive due to that false "SIM1 has been converted to an eSIM" state—Google Messages will continue hiding SIM1 completely until EE UK and Google push an updated 234-30 carrier configuration bundle."

Hopefully will be sorted out soon and I can revert back to the google messages app which is the only one that supports RCS as am having to use a third party sms app to send messages