"Thinkpad Thales eSIM" card does not show up in OpenEUICC if it has no eSIM profile on it #91
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello Peter,
not sure if that is an issue or not at least it's what I recognized while using the "Thinkpad Thales eSIM".
As long as I had no eSIM profile on it and the eSIM card was in the devices SIM slot, neither EasyEUICC nor OpenEUICC did recognize the card.
After adding a profile with an adapter and EasyEUICC (OpenEUICC did not work and ended with an error code),
OpenEUICC now sees the profile if the eSIM card is in the devices SIM slot. EasyEUICC still does not see card/profile.
In case you keep that as an issue, please let me know if you need more information and I'll try to help.
Thanks for your work!
Device: rooted (magisk) Samsung Galaxy S7, Lineage OS 19 (Android 12), magisk-module-openeuicc from AndroPlus-org
If it doesn't show up in OpenEUICC, it's because your OS refuses to let us open the ISD-R. I doubt there's anything we can do in OpenEUICC.
Some logs might help but again, I doubt there's anything we can do here.
If OpenEUICC could not open ISD-R (issuer security domain – root), how would you explain that I see profiles now.
As I wrote, a blank eSIM was not recognized, now with profiles on it, OpenEUICC sees the profiles and so the eSIM-card itself I assume? At least this would be my understanding from reading this.
I can send some logs. Could you please let me know how to do it/where to get it? Should I cut out information from the logs which would be private?
Here you go, I did also create a issue on the cheaper Thales app, but the ROM maintainer said they won't blindly add OMAPI as the OEM didn't do it. We can try to contact Lenova or their Motorola community manager if they can do some changes but it could be fruitless. But by looking at other examples, other cards would be better of or just buy a cheap esim phone.
this log file does not contain any valid information
So Verbose logs is needed or something else?
@BurhanBudak it seems to me you are highjacking my thread with nothing substantial to add!
Your first message is a weird blabla which to me has nothing to do with the issue I am reporting.
@PeterCxy , I was asking how you would explain that OpenEUICC could not read the "empty" Thales eSIM card but now that there are eSIM profiles on it OpenEUICC is able to show these.
Doesn't that speak against your assumption that my "OS refuses to let us open the ISD-R"?
Unfortunately I can not provide any logs of an empty Thales eSIM at the moment.
Hello,
I found a custom ROM where ISD-R seams to be supported. Nevertheless there are several problems to access the card:
Below you can find two logs from the first use case. Is there any reason why the card is only visible in the app if profile is enabled but not if it is disabled?
@AkteX
That is a limitation of some Android modem implementations. They do not recognize cards without a valid profile on it and does not even allow us to open an ISD-R channel. This is why vendors like eSIM.me etc. all implement a "dummy" profile when they ship the card so that it can be read by the device.
This is likely the same situation as @M0RT1M4R:
Unfortunately there is nothing OpenEUICC can do to fix this. Closing as wontfix.