<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as &amp;quot;SIM1 in Android Devices</title>
    <link>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654515#M94656</link>
    <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Ill await a response from Google and Oppo and anything that pops up on here from EE&lt;/P&gt;</description>
    <pubDate>Tue, 17 Nov 2026 22:04:08 GMT</pubDate>
    <dc:creator>davecres1</dc:creator>
    <dc:date>2026-11-17T22:04:08Z</dc:date>
    <item>
      <title>Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as "SIM1</title>
      <link>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654392#M94653</link>
      <description>&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;STRONG&gt;Affected Devices:&lt;/STRONG&gt; OPPO Find X10 Pro Max (CPH2913) &amp;amp; Google Pixel 11 Pro XL&lt;BR /&gt;&lt;STRONG&gt;OS Version:&lt;/STRONG&gt; Android 17 / ColorOS 17&lt;BR /&gt;&lt;STRONG&gt;Network:&lt;/STRONG&gt; EE UK (MCC 234 / MNC 30)&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;STRONG&gt;Summary of the Issue:&lt;/STRONG&gt;&lt;BR /&gt;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 &lt;EM&gt;"SIM1 has been converted to an eSIM"&lt;/EM&gt; and disables the physical SIM slot. The physical SIM has &lt;STRONG&gt;not&lt;/STRONG&gt; been converted to an eSIM.&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;STRONG&gt;Steps Taken to Isolate the Bug:&lt;/STRONG&gt;&lt;/DIV&gt;&lt;OL class=""&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Tested multiple EE SIMs:&lt;/STRONG&gt; Tested both the original EE SIM and brand-new EE replacement physical SIMs—every EE physical SIM triggers the exact same error.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Tested on non-Google SIM stacks:&lt;/STRONG&gt; Inserted the exact same EE physical SIM cards into an &lt;STRONG&gt;iPhone&lt;/STRONG&gt; and an &lt;STRONG&gt;Honor Magic 8 Pro&lt;/STRONG&gt;. Both devices register on EE and work normally, confirming the physical SIMs are active and unconverted.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Tested another UK network in the same slot:&lt;/STRONG&gt; Inserted a &lt;STRONG&gt;Three UK&lt;/STRONG&gt; 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.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Cleared local caches &amp;amp; updated firmware:&lt;/STRONG&gt; Reset mobile network settings, cleared Carrier Services / telephony caches, and installed the latest device updates, but the issue persists.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;DIV class=""&gt;&lt;STRONG&gt;Technical Conclusion for EE Network Engineering:&lt;/STRONG&gt;&lt;BR /&gt;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 &lt;STRONG&gt;EE's Android 17 carrier configuration bundle&lt;/STRONG&gt;.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?&lt;/DIV&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Tue, 17 Nov 2026 16:05:21 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654392#M94653</guid>
      <dc:creator>davecres1</dc:creator>
      <dc:date>2026-11-17T16:05:21Z</dc:date>
    </item>
    <item>
      <title>Re: Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as "SIM1</title>
      <link>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654425#M94654</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.ee.co.uk/t5/user/viewprofilepage/user-id/987594"&gt;@davecres1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Firmware is from the manufacturer and therefore report the issue to them.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.oppo.com/" target="_blank"&gt;https://community.oppo.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I think the oppo is a known issue. You should disable the eSIM option maybe.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pixel&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.google.com/pixelphone/community?hl=en&amp;amp;sjid=5028686896141054233-EU" target="_blank"&gt;https://support.google.com/pixelphone/community?hl=en&amp;amp;sjid=5028686896141054233-EU&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 18:10:29 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654425#M94654</guid>
      <dc:creator>Northerner</dc:creator>
      <dc:date>2026-11-17T18:10:29Z</dc:date>
    </item>
    <item>
      <title>Re: Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as "SIM1</title>
      <link>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654513#M94655</link>
      <description>&lt;P&gt;Thank you for the response and I have informed both Google and Oppo. But as I said "&lt;SPAN&gt;Because this occurs across different Android 17 devices that rely on Google's native SIM Manager / Carrier Services framework" its an issue with that.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Point to note even with Esim turned off as soon as an EE Sim is put in it comes up with&lt;EM&gt;"SIM1 has been converted to an eSIM" in either Google Pixel or Oppo Find X10 pro its the same issue. My Friends&amp;nbsp;Honor Magic 8 pro doesn't use&amp;nbsp;&lt;SPAN&gt;Google's native SIM Manager / Carrier Services framework but its own and not have an issue.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 21:48:22 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654513#M94655</guid>
      <dc:creator>davecres1</dc:creator>
      <dc:date>2026-11-17T21:48:22Z</dc:date>
    </item>
    <item>
      <title>Re: Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as "SIM1</title>
      <link>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654515#M94656</link>
      <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Ill await a response from Google and Oppo and anything that pops up on here from EE&lt;/P&gt;</description>
      <pubDate>Tue, 17 Nov 2026 22:04:08 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654515#M94656</guid>
      <dc:creator>davecres1</dc:creator>
      <dc:date>2026-11-17T22:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as "SIM1</title>
      <link>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654959#M94659</link>
      <description>&lt;P&gt;Hi &lt;SPAN style="background: var(--ck-color-mention-background); color: var(--ck-color-mention-text);"&gt;&lt;a href="https://community.ee.co.uk/t5/user/viewprofilepage/user-id/987594"&gt;@davecres1&lt;/a&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It seems a very strange situation you're experiencing, especially as you're able to recreate it.&amp;nbsp;&lt;BR /&gt;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.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Ali&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2026 13:40:24 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1654959#M94659</guid>
      <dc:creator>Ali_A</dc:creator>
      <dc:date>2026-11-19T13:40:24Z</dc:date>
    </item>
    <item>
      <title>Re: Bug Report: Android 17 / ColorOS 17 falsely reports EE UK physical SIMs as "SIM1</title>
      <link>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1655002#M94660</link>
      <description>&lt;P&gt;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&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;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 &amp;nbsp;converted to Esim but phone and data worked just like mine.&lt;/P&gt;&lt;P&gt;In various external forums they say its a known bug "&lt;SPAN&gt;Because Google Messages relies strictly on Android's &lt;/SPAN&gt;SubscriptionManager&lt;SPAN&gt;—which ColorOS 17 / Android 17 marks as inactive due to that false &lt;/SPAN&gt;"SIM1 has been converted to an eSIM"&lt;SPAN&gt; state—Google Messages will continue hiding &lt;/SPAN&gt;SIM1&lt;SPAN&gt; completely until EE UK and Google push an updated &lt;/SPAN&gt;234-30&lt;SPAN&gt; carrier configuration bundle."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;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&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Nov 2026 16:06:37 GMT</pubDate>
      <guid>https://community.ee.co.uk/t5/Android-Devices/Bug-Report-Android-17-ColorOS-17-falsely-reports-EE-UK-physical/m-p/1655002#M94660</guid>
      <dc:creator>davecres1</dc:creator>
      <dc:date>2026-11-19T16:06:37Z</dc:date>
    </item>
  </channel>
</rss>

