1009443 - [OpenC&Flame][V1.4] Cannot get MCC/MNC

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[William Hsu [:whsu]]

Attachment: RIL_Debugging_2014051316

* Description:
  Now, we cannot use following command to get MCC/MNC.
  - adb logcat | grep -E 'MCC|MNC'
  This bug happens on flame and OpenC device.
  Other devices don't have this problem.

  Attach the log. (RIL_Debugging_2014051316)

* Reproduction steps:
  1. Enable RIL debugging.
     - https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#RIL_Debugging
  2. After you restart the device, please use following command on the terminal to get MCC/MNC
     - adb logcat | grep -E 'MCC|MNC'

* Expected result:
  - Can get MCC/MNC

* Actual result:
  - Cannot get MCC/MNC

* Reproduction build:( OpenC - Firefox OS V1.4 inside)
 - Gaia      2f89c43e798ccba631025bedc47a1fb24e830cf2
 - Gecko     https://hg.mozilla.org/mozilla-central/rev/4b6d63b05a0a
 - BuildID   20140512160204
 - Version   32.0a1

Comment 1

[William Hsu [:whsu]]

It works for me after enable RIL debugging

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

For testing single variant, this bug causes issues as the only way we can see the MCC/MNC on our builds is through turning RIL debug on prior to boot.

This is not a vendor issue as 1.3 OEM v122 will show the mnc/mcc without RILdebug turned on:
12-31 17:21:04.759: D/ICCRECORDS_QC_B2G(656): MCC = 310, MNC = 410

Comment 3

[Jason Smith [:jsmith]]

Naoki - Is this a test blocker to test single variant on 2.0? If so, we probably should be nominating this to block.

Comment 4

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I didn't nom it because I do have a work around as per comment 1.

I am hesitant, because I thought that we're not suppose to do RIL work on the flame any more...

It would benefit us greatly not just for single variant testing, but for anything else that uses MCC/MNC such as marketplace and Cost control, I think.

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Sorry, you're right.  the work around only works for 2.1; I can't get the work around to work for some reason on 2.0

E/RILQ    (  345): (0/345): RIL[0][cmd-22(336)] qcril_cm_ss_convert_gsm8bit_alpha_string_to_utf8: Invalid parameters for GSM alphabet to UTF8 conversion, input len = 0

Comment 6

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Seems you were using the command |adb logcat | grep -E 'MCC|MNC'|? 

I suggest trying again with "adb logcat | grep -i -E 'MCC|MNC'" because most mcc/mnc messages are in lower case. Gecko prints capital MCC/MNC only in the IMEI message which is almost printed once after boot-up. That might explain why this issue doesn't exist if turning RIL debug on prior to boot.

Comment 7

[Jason Smith [:jsmith]]

Can we verify that this can happen on 2.0 with https://wiki.mozilla.org/B2G/QA/Customizations#Build_Setup?

Comment 8

[Jason Smith [:jsmith]]

(In reply to Jason Smith [:jsmith] from comment #7)
> Can we verify that this can happen on 2.0 with
> https://wiki.mozilla.org/B2G/QA/Customizations#Build_Setup?

i.e. check to see if you can flash a SIM customization & see SIM-specific data (e.g. blue or red wallpaper).

Comment 9

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I spoke with Alberto and he mentioned that what I might be seeing when testing single variant is bug 1031164 instead of this bug.  bug 1031164 that he is seeing when testing single variant on the flame.

To note : I tried 
adb logcat | grep -i -E 'MCC|MNC'
on 2.1 and I did not see the MCC/MNC values.

Also to note that I did have SIM PIN when trying to get the single varant for 2.0 and 2.1.  2.0 showed something different for me.

Comment 10

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

After talking it over with Jason, there's ways to work around this by analyzing MCC/MNC via mozMobileConnection which Jason has a test app for.

We'll track bug 1031164 for my main issue.

This bug does occur still, Jason and I agreed it's not a blocker.

Comment 11

[Edgar Chen [:edgar]]

Clear ni? due to comment #10, please feel free to ni? me if anything I can help.

Comment 12

[BMO Automation]

Firefox OS is not being worked on