Closed
Bug 796723
Opened 14 years ago
Closed 14 years ago
[statusbar] The headphone indicator won't show if boot the phone with headphone plug-in
Categories
(Firefox OS Graveyard :: Gaia, defect)
Firefox OS Graveyard
Gaia
Tracking
(blocking-basecamp:+)
RESOLVED
WORKSFORME
| blocking-basecamp | + |
People
(Reporter: ghtobz, Unassigned)
Details
(Whiteboard: [label:Enhancement][label:statusbar][LOE:0])
[GitHub issue by johnshih on 2012-09-25T03:34:21Z, https://github.com/mozilla-b2g/gaia/issues/5119]
## Environment :
Otoro phone, build 2012-09-24
Build info:
* "gaia" revision= 028b9eb35bc0fbbf2d31a0b766319b94997c8eb1
* "gecko" revision= 7de377e67a367f389b44fd3c0d1d6fd3f08f71f0
## Repro :
1. Turn the phone off
2. plug in the headphone
3. Boot the phone
## Expected:
* After boot, the headphone indicator will show on status bar
## Actual:
* won't show
[GitHub comment by nhirata on 2012-09-25T16:44:29Z]
@lissyx
[GitHub comment by lissyx on 2012-09-26T11:35:20Z]
Turns out that it seems that the event is not fired on boot. I can't debug more, I don't have time. See HeadphoneSwitchObserver class, Notify method in dom/system/gonk/AudioManager.cpp.
[GitHub comment by lissyx on 2012-09-26T11:48:59Z]
Someone will have to review https://bugzilla.mozilla.org/show_bug.cgi?id=794424
[GitHub comment by lissyx on 2012-09-26T11:52:11Z]
With the patch attached, I see the event being triggered, but statusbar not catching it on boot. I can't help more.
[GitHub comment by nhirata on 2012-09-26T18:14:35Z]
@autonome According to lissyx, someone that knows mozChromeEvent will be needed for fixing this bug.
[GitHub comment by autonome on 2012-09-26T18:18:25Z]
is there gaia work required, or will the platform fix address the issue completely?
[GitHub comment by lissyx on 2012-09-26T20:46:06Z]
No, the platform fix is needed I think, since we cannot have headphones status in gaia without having the event triggered at boot time, which is what the fix I sent does. But somehow, this event does not make it to the statusbar. I suspect some race condition between this boot-time event and the handler in gaia which is not yet installed. But I'm not a master of events, and I can't dig in right now, so better to let someone at ease with mozChromeEvent lifecycle look at this.
Comment 8•14 years ago
|
||
Is this still an issue? Works for me on my Nexus S.
Comment 9•14 years ago
|
||
Also works for me in otoro.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•