One: Background & related Flow
MTK Operator name display is divided into two types in the phone:
1. SIM Card Name:
According to the IMSI read from the SIM card on the boot to Spn-conf.xml (if it is MVNO card is virtual-spn-conf-by-***.xml) matching the name, will be saved in Siminfo this database, The name of the subsequent SIM card is obtained from this database
You can refer to the following FAQ for MVNO:
id:faq09811
[NW] How to differentiate between MNO and MVNO
Usage scenarios:
Setting under Simmangement siminfo, etc.
2. Name of the network on which the registration is registered:
This section shows the main sources of the string used below, and the string between them eventually shows which source is based on the network and the rule determined by the content of these sources (if currently roaming, whether the currently registered PLMN is in ef_ SPDI, there are flags in the EF_SPN to show the SPN ... ）
About rule:
Please refer to the GSM SEC 51.011 ef_spn part also cphs spec;
Code section, please refer to simrecords. Getdisplayrule and Gsmservicestatetracker. Updatespndisplay:
(1) SIM card files, such as EF_SPN, EF_OPN, EF_SOPN, EF_OPL, EF_PNN, ef_spdi ...
(2) PLMN of the network to be registered, corresponding to Spn-conf.xml
(3) NITZ, that is, the name of the network issued
The rule summary defined by EF_SPN in Spec 51.011 is:
1. The name is divided into SPNs and registered PLMN (including eons, cphs (i.e. ons), s-cphs, NITZ, PLMN; priority descending)
2. If there is no SPN file, then the registered PLMN is displayed
3. If there is an SPN, the registered PLMN is HPLMN or registered PLMN in the SIM card file Ef_spdi, then
(1) If an SPN is present, the SPN will be displayed
(2) If the SPN is bit1 = 1, you need to display the registered PLMN at the same time, if the bit1=0 of the SPN, you do not need to display registered PLMN
4. If there is an SPN, the registered PLMN is roaming PLMN and the registered PLMN is not in the SIM card file Ef_spdi, then
(1) Display registered PLMN
(2) If the SPN is bit2=0, you need to display the SPN at the same time, and if the SPN is bit2=1, you do not need to display the SPN
The part of the customer that can be customized is spn-conf.xml/virtual-spn-conf-by-***.xml; in other words, if you modify the relevant XML does not take effect, it should be shown by the spec higher priority name (EONS, cphs, NITZ ... ）
If a higher priority name is displayed by spec, rather than an XML configuration, then the name of the XML you want to display must modify code flow and cause the rule to break the spec definition (since this is the generic rule for spec definition, the SIM card needs to be follow when it is actually done). Spec rule)------Such a custom is likely to lead to test fail such as CTA/FTA, and follow the spec of the SIM card display will also be problematic; it is suggested that this part is spec-compliant, and do not make the custom in addition to XML
Second: How to deal with problems when they are encountered
If some operator do not follow the GSM Spec, but define their own rule, please handle it as follows:
(1) If the operator has a formal spec, please provide detailed technical documentation;
(2) Put the card in the same place at the same time (ensure the same network condition) in the SAMSUNG,HTC and other contrast machine to reproduce the problem, provide contrast machine performance
(3) Put this card in the MTK phone to reproduce the problem and provide a recurring problem of the boot mobile log
Android Network operator name display rules (lock screen, drop-down list)
