1065028 - [Flame] Notification screen cannot be opened

Status: RESOLVED DUPLICATE of bug 1066557

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

Description

[Marcela Oniga]

OS version: 2.2
Platform version: 35.0a1
Build identifier: 20140909040219
master 

Steps:
1. Pull the notification screen down.

Expected results:
Notification screen should be displayed.

Actual results:
Notification screen is not displayed. User is unable to pull the notification screen down.

Comment 1

[Gregor Wagner [:gwagner]]

Can QA reproduce?

Comment 2

[Cody Roesch [:croesch]]

Hi Marcela,
   I'm using the build you listed in comment 0, but am unable to get a non-functioning notification window. It always pulls down for me as expected.

Can you give me a little more information on what else you were doing when you saw this?

1. Was the notification window EVER working for you on this build?
   - If it did work at some point, when did you notice it was broken?
   - Were you able to get the notification window to work again such as by rebooting the device?

If your answer to question 1 is (NO IT NEVER WORKED AT ALL), I'll need to know the gecko and Gaia for the build you were using.

Also please flash to the latest master and see if you still can reproduce this.

Thank you! Any help narrowing this down would be appreciated.

Build tested on:

Environmental Variables:
Device: Flame Master
BuildID: 20140909040219
Gaia: 4acd3e69b263b54f4111e3586ff4ade84b49b4da
Gecko: 6b8da5940f74
Version: 35.0a1 (Master) 
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Comment 3

[Marcela Oniga]

(In reply to Cody Roesch [:croesch] from comment #2)
> Hi Marcela,
>    I'm using the build you listed in comment 0, but am unable to get a
> non-functioning notification window. It always pulls down for me as expected.
> 
> Can you give me a little more information on what else you were doing when
> you saw this?
> 
> 1. Was the notification window EVER working for you on this build?
>    - If it did work at some point, when did you notice it was broken?
>    - Were you able to get the notification window to work again such as by
> rebooting the device?
> 
> If your answer to question 1 is (NO IT NEVER WORKED AT ALL), I'll need to
> know the gecko and Gaia for the build you were using.
> 
> Also please flash to the latest master and see if you still can reproduce
> this.
> 
> Thank you! Any help narrowing this down would be appreciated.
> 
> Build tested on:
> 
> Environmental Variables:
> Device: Flame Master
> BuildID: 20140909040219
> Gaia: 4acd3e69b263b54f4111e3586ff4ade84b49b4da
> Gecko: 6b8da5940f74
> Version: 35.0a1 (Master) 
> Firmware Version: v123
> User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Hello,

I've retested using flame device:

Gaia   855be6ade407c26e0596e7306a44deebc3f60933
SourceStamp f27ff178807d
BuildID 20140915040203
Version 35.0a1

I updated my device with this build (OTA) after that I took a screenshot and then checked the notification screen. Please see attached video.

Comment 4

[Marcela Oniga]

Since video is too large to upload it here, I used dropbox, you can find it here:https://www.dropbox.com/s/utqq7mp4hqso49w/VID_20140915_230936.mp4?dl=0

Comment 5

[Cody Roesch [:croesch]]

I've followed the comments and what I saw in the video. I OTA'd to the build in comment 3 but I'm still unable to get this bug to occur. I saw that you had 2 sims in your device and thought that might have something to do with it but still nothing. I'm going to leave this bug for someone else to try because I'm out of ideas.

Comment 6

[Michael Henretty [:mikehenrty][:mhenretty]]

Thanks for the video. Does this happen every time you boot your phone? Can you attach a logcat?

Comment 7

[joshua.purcell]

I have this same issue. I was able to finally get my notification bar to work after days of if never working (even after updating to more recent nightlies) by following the steps posted in this comment on another bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=1066557#c5

It's possible that bug #1066557 is either related to this bug or a duplicate. If so, then there are more details regarding the issue (as well as a patch) available in the other bug. Please post if either the quick workaround I mention or applying the patch to bug #1066557 solves the issue for you guys.

Comment 8

[Marcela Oniga]

Attachment: log.txt

Logcat attached.

Comment 9

[Guillaume Marty [:gmarty]]

I was able to replicate this issue 100% of the time if I have a no network SIM card in port 1 and a working SIM in port 2 (the other way around or any other configuration works OK).
Applying the patch from https://bugzilla.mozilla.org/show_bug.cgi?id=1066557#c6 fixed the issue.
So this bug and 1066557 are related and potentially duplicates.

Comment 10

[joshua.purcell]

My SIM config is identical to gmarty (comment 9 above). I have a non-working SIM card in port1 and a working SIM in port2. I haven't tested the outcome after modifying this SIM layout.

Comment 11

[Michael Henretty [:mikehenrty][:mhenretty]]

Marcela, thanks for all your help. Can you test this again against the latest master now that bug 1066557 has landed?

Comment 12

[Marcela Oniga]

(In reply to Michael Henretty [:mhenretty] from comment #11)
> Marcela, thanks for all your help. Can you test this again against the
> latest master now that bug 1066557 has landed?

I flashed my device with:

Gaia   e2d70bee03b5380ac327a145e5d694fb2443f018
SourceStamp 3b7921328fc1
BuildID 20140916040203
Version 35.0a1

The bug is still reproducing, same STR.

Comment 13

[Marcela Oniga]

Attachment: logNotif.txt

New logs attached

Comment 14

[Michael Henretty [:mikehenrty][:mhenretty]]

Unfortunately, that build does not contain the fix from bug 1066557.

We need Gaia 76ba0c3abb97258496ec2cd0a8c21a15874012e0 or later.

Comment 15

[Marcela Oniga]

(In reply to Michael Henretty [:mhenretty] from comment #14)
> Unfortunately, that build does not contain the fix from bug 1066557.
> 
> We need Gaia 76ba0c3abb97258496ec2cd0a8c21a15874012e0 or later.

It seems that using:

Gaia   d37950eb09e28aa18d0e01df9ff90574bd4337e0
SourceStamp 426497473505
BuildID 20140918040210
Version 35.0a1

the bug is not reproducing anymore.