UE behavior with plastic eUICC » History » Version 3
laforge, 02/21/2024 06:45 PM
1 | 1 | laforge | h1. UE behavior with plastic eUICC |
---|---|---|---|
2 | |||
3 | This page exists to documents the UE behaviour when inserting a plastic (2FF/3FF/4FF) eUICC into a SIM slot. |
||
4 | |||
5 | Rumour is that some UEs will treat such an _external eUICC_ just like an internal one, i.e. their normal LPAd would be able to manage and/or download eSIM profiles to it. |
||
6 | |||
7 | 3 | laforge | |_.Vendor|_.Model|_.Code|_.Software Ver|_.Modem Ver|_.Slot|_.EasyEUICC works?|_.Observation| |
8 | |Samsung|Galaxy S9|?|||SIM1|yes|No built-in eSIM support| |
||
9 | |Samsung|Galaxy S22|SM-S901B/DS|UP1A.231005.007.S901BXXS7DWL3|S901BXXS7DWL1|SIM1|?|No request to SM-DS or SM-DP+ at barcode| |
||
10 | |Samsung|Galaxy S22|SM-S901B/DS|UP1A.231005.007.S901BXXS7DWL3|S901BXXS7DWL1|SIM2|yes|SIM manager shows eSIM profiles on plastic eUICC| |
||
11 | |Google|Pixel 3a XL|?|||SIM1|?|eSIM installation fails with _operation code 9, error code 1001_ (probably tried to use the internal eUICC instead of the external one)| |
||
12 | |Google|Pixel 4a 5G|?|||SIM1|yes|eUICC is recognized and listed by internal SIM manager; switching profiles on a sysmoEUICC1-C2T resulted in an error which made that plastic eUICC disappear from both the built-in SIM manager as well as EasyEUICC-SGP.26. Moving that same eUICC to another phone works just fine. However, moving that eUICC back to the Pixel 4a 5G shows the problem persists. Even another sysmoEUICC1-C2T would not even be recognized by EasyEUICC anymore. Its almost as if the plastic-eUICC functionality has been bricked| |
||
13 | |Google|Pixel 7|?|||SIM1|yes|eUICC is recognized and listed by internal SIM manger| |