Closed Bug 1009443 Opened 10 years ago Closed 6 years ago

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

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-, b2g-v2.0 affected, b2g-v2.1 affected)

RESOLVED WONTFIX
blocking-b2g -
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: whsu, Unassigned)

Details

(Whiteboard: OpenCrun1.4-3, [2.0-flame-test-run-2])

Attachments

(1 file)

* 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
Whiteboard: OpenCrun1.4-3
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Whiteboard: OpenCrun1.4-3 → OpenCrun1.4-3, [2.0-flame-test-run-2]
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
It works for me after enable RIL debugging
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
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
Status: RESOLVED → REOPENED
Flags: needinfo?(echen)
Resolution: WORKSFORME → ---
Naoki - Is this a test blocker to test single variant on 2.0? If so, we probably should be nominating this to block.
Flags: needinfo?(nhirata.bugzilla)
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.
Flags: needinfo?(nhirata.bugzilla)
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
blocking-b2g: --- → 2.0?
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.
Can we verify that this can happen on 2.0 with https://wiki.mozilla.org/B2G/QA/Customizations#Build_Setup?
Keywords: qawanted
(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).
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.
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.
blocking-b2g: 2.0? → -
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Clear ni? due to comment #10, please feel free to ni? me if anything I can help.
Flags: needinfo?(echen)
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 10 years ago6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: