we try to use 3rd patry sim cards (with ubuntu/android). esim profile downloaded and installed successfully. we can see and manage it (enable/disable/delete). but device not starting registration process to network, we can see that using qualcomm diag (layer3), just listening network system information messages and paging messages.
PS: i can share QXDM full log to pm
Using QXDM i see some debug line :
DiagLogger.cpp 86 L [qcril_qmi_nas] RIL[0][qcril_qmi_nas.cpp: 15277] [DispatcherModul(1947,2020)] qcril_qmi_nas_util_convert_nas_srv_status_to_ril_reg_status: ... is_sys_forbidden_valid, is_sys_forbidden 1, 1
as i undestand :
is_sys_forbidden_valid = 1
is_sys_forbidden = 1
its mean that registration forbidden by policy ?
Hey @kn00wlege can you clarify which Ubuntu version you're using? 20.04 vs. 24.04 and which build?
HI @ericpietrowicz , using android . We need android for our project.
Can you share a small section of the QXDM section around the first registration attempt + reject?
Its a problem, no any registration attemps at all....
Sorry, you might need to clear the PLMN list and reboot the modem first to get these logs. I'm looking into how to do this...
From what I can find when a modem repeatedly gets rejected (SIM not active yet, roaming not allowed, wrong APN, wrong carrier profile, etc.), it can write the PLMN to the SIM’s “forbidden” list.
seems FPLMN list is empty
lahaina:/ # echo -e "AT+CRSM=176,28539,0,0,12\r" > /dev/smd7
lahaina:/ # cat /dev/smd7
+CRSM: 144,0,"FFFFFFFFFFFFFFFFFFFFFFFF"
OK
Hey kn00wlege
Some quick questions!
Thanks
Nick.
Hi @mrlambchop , thx for your attention ! We using self writed software based on OpenEUICC (and we try original OpenEUICC too) with android. All work like a charm when serving network mcc is 257/260 independent of sim IMSI. But when serving MCC is 250 - no any registration process (no any registration requests up to network at all) .
Hi there, just to confirm my understanding of what you’re seeing:
It sounds like the device works as expected when the serving network MCC is 260 (USA) and 257 (Norway), independent of the SIM IMSI. That’s great and aligns with what we’d expect.
One thing worth noting is that, depending on the country of operation, devices typically need either the **North America (NA)**or Rest-of-World hardware variant to ensure full and correct band support. Without the appropriate variant for the region, registration behavior can be unpredictable.
You’re also observing that when the serving MCC is 250, the device does not attempt to register at all - no registration requests are sent, full stop.
Unfortunately, we don’t have any direct knowledge or validation of operation on networks with MCC 250, and Russia was not included in the supported country / network band list when Tachyon was built. As a result, we’re not in a position to help debug or support that scenario.
That said, if the device is refusing to attempt registration entirely (rather than being rejected by the network), that does point toward a banding or regulatory configuration issue at the device or modem level.
Since there wasn’t any information provided about the specific country of use, hardware variant, or exact unit configuration, it’s difficult to go further in determining whether this is the root cause.
Hope that helps clarify things, and happy to look further if more detail becomes available
Thanks
Nick
Thx for your response @mrlambchop! But MCC 260 is Poland and MCC 257 is Belarus (europe), yes right 250 is Russia. But all this networks has same band configurations and frequency ranges. For example LTE bands 3/7/20 etc used for all this networks.
Or NA devices and ROW devices has different hardware part ?
Can i provide qxdm log for you?
Hi kn00wlege
We reached out to QCOM about any MCC lock. As you know, US -> Russia has export compliance that QCOM must handle, but I don't know their response sorry. I'll update when I hear back.
Thanks
N