17-11-2026 04:05 PM
Solved! See the answer below or view the solution in context.
17-11-2026 06:10 PM
Hi @davecres1
Firmware is from the manufacturer and therefore report the issue to them.
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
17-11-2026 06:10 PM
Hi @davecres1
Firmware is from the manufacturer and therefore report the issue to them.
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
17-11-2026 09:48 PM
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.
17-11-2026 10:04 PM
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
19-11-2026 01:40 PM
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
19-11-2026 04:06 PM
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