[Issue] ThinkPad Thales eSIM doesnt show up in logs in OpenEUICC fork #34

Open
opened 2024-07-04 12:33:17 +02:00 by BurhanBudak · 6 comments

Device: Oneplus 7T Snapdragon 855+ with the X24 modem.

ROM: LineageOS 21 with Magisk and MicroG

Can be read by EasyLPAC on a Thinkpad SC Broadcomm reader.

Default SM-DP+ not set

Root SM-DS adress: lpa.ds.gsma.com

Manufacturer: French arms corp Thales

Certificate Issuer: GSMA - RSP2 CI1

{ "profileVersion": "2.1.0", "svn": "2.2.0", "euiccFirmwareVer": "66.81.1", "extCardResource": { "installedApplication": 0, "freeNonVolatileMemory": 518816, "freeVolatileMemory": 10885 }, "uiccCapability": [ "usimSupport", "isimSupport", "csimSupport", "akaMilenage", "akaCave", "akaTuak128", "akaTuak256", "gbaAuthenUsim", "gbaAuthenISim", "javacard", "multipleUsimSupport", "multipleIsimSupport", "multipleCsimSupport" ], "javacardVersion": "", "globalplatformVersion": "2.3.0", "rspCapability": [ "additionalProfile", "crlSupport", "testProfileSupport" ], "euiccCiPKIdListForVerification": [ "removed data as its personal" ], "euiccCiPKIdListForSigning": [ "removed data as its personal" ], "euiccCategory": null, "forbiddenProfilePolicyRules": [ "ppr1" ], "ppVersion": "0.0.2", "sasAcreditationNumber": "TS-CA-UP-0823 ", "certificationDataObject": { "platformLabel": "", "discoveryBaseURL": "" } }

Device: Oneplus 7T Snapdragon 855+ with the X24 modem. ROM: LineageOS 21 with Magisk and MicroG Can be read by EasyLPAC on a Thinkpad SC Broadcomm reader. Default SM-DP+ not set Root SM-DS adress: lpa.ds.gsma.com Manufacturer: French arms corp Thales Certificate Issuer: GSMA - RSP2 CI1 `{ "profileVersion": "2.1.0", "svn": "2.2.0", "euiccFirmwareVer": "66.81.1", "extCardResource": { "installedApplication": 0, "freeNonVolatileMemory": 518816, "freeVolatileMemory": 10885 }, "uiccCapability": [ "usimSupport", "isimSupport", "csimSupport", "akaMilenage", "akaCave", "akaTuak128", "akaTuak256", "gbaAuthenUsim", "gbaAuthenISim", "javacard", "multipleUsimSupport", "multipleIsimSupport", "multipleCsimSupport" ], "javacardVersion": "", "globalplatformVersion": "2.3.0", "rspCapability": [ "additionalProfile", "crlSupport", "testProfileSupport" ], "euiccCiPKIdListForVerification": [ "removed data as its personal" ], "euiccCiPKIdListForSigning": [ "removed data as its personal" ], "euiccCategory": null, "forbiddenProfilePolicyRules": [ "ppr1" ], "ppVersion": "0.0.2", "sasAcreditationNumber": "TS-CA-UP-0823 ", "certificationDataObject": { "platformLabel": "", "discoveryBaseURL": "" } }`
Owner

What is OpenEUICCID?

What is OpenEUICCID?
Owner

If you are using a fork, this is not the place to ask questions about it.

If you are using a fork, this is not the place to ask questions about it.
Author

If you are using a fork, this is not the place to ask questions about it.

Yeah but those who offer the ready to go module fork code from you, also the forks are more adaptive then EasyEUICC. But I also mentioned LPAC, which works. This is just general information on the card. Im trying to make it work but I meet some issues. Also the Lenova card is the cheapest card on the market comparted to 5ber, esimME and SYScom.

> If you are using a fork, this is not the place to ask questions about it. Yeah but those who offer the ready to go module fork code from you, also the forks are more adaptive then EasyEUICC. But I also mentioned LPAC, which works. This is just general information on the card. Im trying to make it work but I meet some issues. Also the Lenova card is the cheapest card on the market comparted to 5ber, esimME and SYScom.
Owner

Ok, I still don't understand what exactly you are referring to as a fork, but if this is actually OpenEUICC then please upload a log of the app when it cannot detect your eSIM. Without at least that there is no way for me to tell what is going on.

Ok, I still don't understand what exactly you are referring to as a fork, but if this is actually OpenEUICC then please upload a log of the app when it cannot detect your eSIM. Without at least that there is no way for me to tell what is going on.
Author

Ok, I still don't understand what exactly you are referring to as a fork, but if this is actually OpenEUICC then please upload a log of the app when it cannot detect your eSIM. Without at least that there is no way for me to tell what is going on.

Yeah, but the weurd thing is that my Snapdragon 855 Oneplus 7T doesn't show logs in the app, but my older 821 Oneplus 3T shows logs. Also, looking at the settings, my app, even after installing with Magisk, is an unpriv system app. Looking at euICCID probe I get this:

OnePlus HD1901

Android 14

eUICC System Service: Unsupported

System Features:

android.hardware.telephony
android.hardware.telephony.subscription
android.hardware.telephony.euicc
android.hardware.telephony.euicc.mep
android.hardware.se.omapi.uicc

System LPAs:

OpenEUICC (im.angry.openeuicc)

Open Mobile API:

Backend: Builtin
State: Unavailable
Bypass: CannotBeBypassed

So what's missing?

> Ok, I still don't understand what exactly you are referring to as a fork, but if this is actually OpenEUICC then please upload a log of the app when it cannot detect your eSIM. Without at least that there is no way for me to tell what is going on. Yeah, but the weurd thing is that my Snapdragon 855 Oneplus 7T doesn't show logs in the app, but my older 821 Oneplus 3T shows logs. Also, looking at the settings, my app, even after installing with Magisk, is an unpriv system app. Looking at euICCID probe I get this: > OnePlus HD1901 Android 14 eUICC System Service: Unsupported System Features: android.hardware.telephony ✅ android.hardware.telephony.subscription✅ android.hardware.telephony.euicc❌ android.hardware.telephony.euicc.mep❌ android.hardware.se.omapi.uicc❌ System LPAs: OpenEUICC (im.angry.openeuicc) Open Mobile API: Backend: Builtin State: Unavailable Bypass: CannotBeBypassed So what's missing?
BurhanBudak changed title from [Issue] ThinkPad Thales eSIM doesnt show up in logs in OpenEUICCID fork to [Issue] ThinkPad Thales eSIM doesnt show up in logs in OpenEUICC fork 2024-07-15 21:35:36 +02:00
Author

Oopps, it's my fault that I said OpenEUICCID, I meant OpenEUICC. I get ICCID from work as I work at a carrier so I automatically write it. The forks are from AndroPlus and hzy132. Or is this something my ROM maintainer should do?

Oopps, it's my fault that I said OpenEUICCID, I meant OpenEUICC. I get ICCID from work as I work at a carrier so I automatically write it. The forks are from AndroPlus and hzy132. Or is this something my ROM maintainer should do?
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: PeterCxy/OpenEUICC#34
No description provided.