Closed Bug 1093932 Opened 10 years ago Closed 10 years ago

[System] No Information displays within 'Device Information'/'More Information' in Settings; 'Operator Services' at bottom of Settings

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 unaffected, b2g-v2.1 affected, b2g-v2.2 verified)

VERIFIED DUPLICATE of bug 1105511
Tracking Status
b2g-v2.0 --- unaffected
b2g-v2.1 --- affected
b2g-v2.2 --- verified

People

(Reporter: onelson, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [2.2-Daily-Testing])

Attachments

(2 files)

Description:
When user is using their phone in the v188 base in the latest master 2.2 build, they may observe a non-reconcilable 'Settings' error after registering a FxA account: no device information displays in the 'Device Information' or 'More Information' tabs. The 'Developer' tab also does not display within 'Settings'. Attached logcat.
Issue MAY resolve upon restarting phone, not 100% repro.
Observed after signing up for FxA accounts twice; upon finishing last UI screen and awaiting email, 'Settings' closed to home.
Observed FM Radio displaying 0 MHz frequency and being unusuable.

Repro Steps:
0) Base phone to v188.
1) Update a Flame device to BuildID: 20141104040207
2) Open 'Settings' menu.
3) Scroll to bottom -- observe 'Operator Services'.
4) Enter 'Device Information' -> 'More Information'.
5) Display UI.
  
Actual:
Phone reveals no information within 'Device Information'/'More Information' tabs.
  
Expected: 
Phone displays all relevant information within appropriate UI.
  
Environmental Variables:
Device: Flame 2.2 Master [Shallow Flash]
BuildID: 20141104040207
Gaia: 3c50520982560ccba301474d1ac43706138fc851
Gecko: 54d05732f29b
Gonk: ** shallow flash **
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
  
  
Repro frequency: 3/4
See attached:
logcat
screenshot
Flags: needinfo?(pbylenga)
Very similar issue had been observed before, bug 1061510
QA Whiteboard: [QAnalyst-Triage?]
Whiteboard: [2.2-Daily-Testing]
It's a regression but adding qawanted for branch checks to determine reproducibility rates between shallow/full flashing and to confirm 2.1 is unaffected.
QA Whiteboard: [QAnalyst-Triage?]
Component: Gaia::Settings → Gaia::System
Flags: needinfo?(pbylenga)
Keywords: qawanted, regression
I haven't been able to reproduce this on Flame using:

Gaia   3c50520982560ccba301474d1ac43706138fc851
SourceStamp 54d05732f29b
BuildID 20141104040207
Version 36.0a1
Base image: v188

How did you get register for FX Accounts? I am hitting the black keyboard bug which makes it impossible to type anything in Settings.
Tested with Shallow Flash on 319mb using Engineering builds

This bug repro's on Flame KK builds: Flame 2.2 KK

Actual Results: Seeing the Operator Services message and settings information missing after a reset or a fresh flash. A reboot will fix the problem however.

Repro Rate: 3/3 after a fresh reset or flash.

Environmental Variables:
Device: Flame 2.2 KK
BuildID: 20141105043145
Gaia: bc843fbf8973c8e124e5668bb2752f5d025fb488
Gecko: 72ae882fce1a
Version: 36.0a1 (2.2) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

-----------------------------------------------------------------
-----------------------------------------------------------------

This bug does NOT repro on Flame kk build: Flame 2.1 KK, Flame 2.0 KK

Actual Result: Not seeing the Operator Services message or missing information in Settings.

Repro Rate: 0/5

Environmental Variables:
Device: Flame 2.1 KK
BuildID: 20141105063632
Gaia: 445656e36d14054d46a8f201dc68d76da8cfa281
Gecko: e7efb38a6477
Version: 34.0 (2.1) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
-----------------------------------------------------------------
Environmental Variables:
Device: Flame 2.0 KK
BuildID: 20141105063630
Gaia: e19ba2a049f192a560c6e63a0cc213b0353f1a02
Gecko: 2c2d1f552ff6
Version: 32.0 (2.0) 
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

-----------------------------------------------------------------
-----------------------------------------------------------------

Bug does NOT occur on Full Flash on 2.2.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
QA-Wanted to get a video of this issue
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
Video Link:
http://youtu.be/1ezv0bewchE

For some reason today I'm rarely being able to get this issue to happen even on the same build used yesterday when it was happening all the time. Adjusting the repro rate.

Repro Rate: 2/8
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Contact: croesch
[Blocking Requested - why for this release]:

Using the steps found in 1103178, let's find a regression window.

This is a bad functional regression that can cause lots of issues.
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage+]
QA Contact: pcheng
Please retry this on a full flash of 2.1, over v188-1, and if you can still reproduce out of 10 times, then we should continue finding a window.
Keywords: qawanted
Component: Gaia::System → Gaia::Settings
(In reply to Tony Chung [:tchung] from comment #10)
> Please retry this on a full flash of 2.1, over v188-1, and if you can still
> reproduce out of 10 times, then we should continue finding a window.

Using the STR provided in bug 1103178, the issue is reproducible on latest Flame 2.1 nightly full flash.

Repro rate: 1/2 (I found that setting wallpaper the first time doesn't repro it, setting it the second time repro's it almost 100% during my window-finding).

Device: Flame (full flash, 319MB mem)
BuildID: 20141125001201
Gaia: 1bdd49770e2cb7a7321e6202c9bf036ab5d8f200
Gecko: db893274d9a6
Gonk: 48835395daa6a49b281db62c50805bd6ca24077e
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


Continuing the window now.
Flags: needinfo?(jmercado)
Keywords: qawanted
Flags: needinfo?(jmercado)
The repro rate decreases greatly as we go back in KK Central. We've been testing around builds in early October and we would a get repro rate of 1 out of 24 attempts or even more attempts. We came to a couple windows that their pushlogs are incorrect. I don't think finding a window is plausible for this bug.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Flags: needinfo?(jmercado)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
See Also: → 1105511
Flags: needinfo?(pbylenga)
Flags: needinfo?(timdream)
Could you tell me what is needed from me here? Thanks.
Flags: needinfo?(timdream) → needinfo?(pbylenga)
Is this a duplicate of bug 1105511, we're unable to get a solid regression window and this renders the phone unusable.
Flags: needinfo?(pbylenga) → needinfo?(timdream)
Kyle, is this bug a dupe of bug 1105511?   if so, please mark it
Flags: needinfo?(kyle)
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(kyle)
Resolution: --- → DUPLICATE
Kyle beats me to this!
Flags: needinfo?(timdream)
blocking-b2g: 2.1? → ---
Can QA please help verify this one on tomorrow's nightly to confirm patch in https://bugzilla.mozilla.org/show_bug.cgi?id=1105511, indeed fixes this.
Flags: needinfo?(pcheng)
Keywords: verifyme
With the STR defined in bug 1103178, I was able to see the lack of information and Operator Services missing.

With the current master[1], I can't reproduce the steps in bug 1103178. 


[1] Gaia-Rev        e04ab7651b1e0c67516e1cef7aa4bc6072529885
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/0cf461e62ce5
Build-ID        20141210160208
Version         37.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  39
FW-Date         Thu Oct 16 18:19:14 CST 2014
Bootloader      L1TC00011880
Status: RESOLVED → VERIFIED
Flags: needinfo?(pcheng)
Keywords: verifyme
Depends on: 1110872
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: