Closed
Bug 795860
Opened 12 years ago
Closed 12 years ago
[Otoro] System Message API attempts to launch Settings app before Homescreen
Categories
(Firefox OS Graveyard :: Gaia, defect, P1)
Tracking
(blocking-basecamp:+)
VERIFIED
FIXED
blocking-basecamp | + |
People
(Reporter: timdream, Assigned: timdream)
Details
Attachments
(1 file)
1.60 KB,
patch
|
vingtetun
:
review+
|
Details | Diff | Splinter Review |
Since in window_manager.js we treat the first launched app as the home screen app, this results a stuck switching window animation (which attempts to switch the apps "null" to "home screen") when the home screen is later launched.
This is not reproducible every time the phone boots. More like 1 out of 3.
Further inspection in Gaia showed that the mozChromeEvent is not an activity (|evt.detail.isActivity| evaluates to false), so whatever tried to launch the Settings app it is might not something in Gaia.
Proposed resolution:
1) Does anyone know who is trying to launch Settings app? First run exp? If so, make sure it launches after the home screen launches (listen to the first appwillopen event in Gaia). If it's not something in Gaia System app we will need to find other event to listen to.
2) Check |evt.detail.isActivity| before assign some app as the homescreen app... this can be served as workaround first but I really want to find out (1).
Assignee | ||
Comment 1•12 years ago
|
||
I guess we should do (2) regardless; there are infinite possible route to trigger a system message mozChromeEvent from Gecko. We need to make the logic more robust. I'll submit a patch soon.
Assignee: nobody → timdream+bugs
Assignee | ||
Comment 2•12 years ago
|
||
Resolution (2) fix.
I am told that we should resist the temptation of making clean up changes that could result regression at this point so this is the minimal change required I think.
Attachment #666509 -
Flags: review?(21)
Comment 3•12 years ago
|
||
Comment on attachment 666509 [details] [diff] [review]
Gaia patch v0.1
Review of attachment 666509 [details] [diff] [review]:
-----------------------------------------------------------------
Glad you found it. It happens more and more and starts to be really annoying.
Attachment #666509 -
Flags: review?(21) → review+
Assignee | ||
Comment 4•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•12 years ago
|
||
I think found the mystery: the system message that tried to launch Settings app should be the icc-stkcommand message, part of SIM Card Kit.
Even if this bug is solved, we ended up launching Settings app in background during phone startup :-/
Comment 7•12 years ago
|
||
Can someone provide steps to verify this is fixed?
Assignee | ||
Comment 8•12 years ago
|
||
(In reply to John Hammink from comment #7)
> Can someone provide steps to verify this is fixed?
It's not worthy the time to verify this, but here you go.
STR:
1. Boot up a phone with an unlocked SIM card
2. Unlock the lock screen
3. Restart until you see the behavior described in "actual" below
Expected:
1. Home screen
Actual:
1. Two "cards" stuck in the middle of app switching.
Updated•12 years ago
|
blocking-basecamp: ? → +
Priority: -- → P1
Comment 9•12 years ago
|
||
Otoro daily: 10-11-2012
* gaia: 2667536e3b06e46dd193aa6d76ba08dad2d867be
* gonk: 6ec34aa3d66331054de37eabc594ad923654b27c
According to the steps, I'm actually observing the correct behavior. Thanks for the STR, Tim! Marking "verified".
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•