Closed Bug 796550 Opened 12 years ago Closed 10 years ago

[system][performance] Powering off takes ~8 seconds

Categories

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

defect

Tracking

(blocking-basecamp:-)

RESOLVED WORKSFORME
blocking-basecamp -

People

(Reporter: ghtobz, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c=progress p= s= u=] [label:system][label:perf])

[GitHub issue by m8ttyB on 2012-08-27T19:39:40Z, https://github.com/mozilla-b2g/gaia/issues/3899]
## Environment
* Otoro, daily build 2012-08-270
* Gaia commit: a20b1694
* mozilla-central: 1bf80bf9

## Repro
1. Hold down the power key until power-context menu (which includes "power off" option), appears.
3. Tab "Power Off
 
## Expected
* Power off button, when tapped shuts the phone off immediately

## Actual
*  When tapped, power off button shows and the phone takes roughly 8 seconds to power off.
[GitHub comment by nhirata on 2012-08-27T19:52:01Z]
It actually does shut off but takes a while to shut off... also you get a grey screen... Perhaps this might be turned into a performance/user feedback issue instead?  It took about 8 seconds for it to do something else, about 28 seconds to completely turned black for me.
[GitHub comment by jammink on 2012-09-17T15:37:57Z]
Just checked again wtih 9/17 build; still takes between 7-8 seconds on three trials.
[GitHub comment by autonome on 2012-09-17T15:40:52Z]
Blocking-, wouldn't hold the release for this.
Component: Gaia → Gaia::System
Keywords: perf
Whiteboard: [label:system][label:perf] → [c= p= s= u=] [label:system][label:perf]
Depends on: 920773
Whiteboard: [c= p= s= u=] [label:system][label:perf] → [c=progress p= s= u=] [label:system][label:perf]
Powering off takes 4 -5 seconds on  Geeksphone Keon running 1.5 Git commit 2014.04.16 00:08:26 034050e5.
Priority: -- → P4
On a flame this seems to take less than 5 seconds. I think we are good here unless there's something more specific we want to look at.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.