Closed
Bug 874366
Opened 13 years ago
Closed 8 years ago
[system] Device very unresponsive while update gets uncompressed/unzipped/unpacked, power button has to be hold/pushed very long if screen turned off
Categories
(Firefox OS Graveyard :: Gaia::System::Lockscreen, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: aryx, Unassigned)
References
Details
At the moment, if an update has been downloaded and is currently being uncompressed and screen turned off, you have to press the power button several seconds like when you want to shut down the phone. This can scare the users that the update failed/the device got bricked and is a bad user experience.
Updated•13 years ago
|
QA Contact: atsai
Comment 1•13 years ago
|
||
The updater process which performs the uncompression should be running with the lowest priority, and a low I/O priority.
So I'm guessing it will take some investigation to figure out what's going on.
Updated•13 years ago
|
Hardware: All → ARM
Comment 2•13 years ago
|
||
I reproduced this using a userdebug build on my unagi.
Running "top -m 10"
I'm seeing something like this:
User 99%, System 0%, IOW 0%, IRQ 0%
User 301 + Nice 6 + Sys 3 + Idle 0 + IOW 0 + IRQ 0 + SIRQ 0 = 310
PID PR CPU% S #THR VSS RSS PCY UID Name
470 0 97% R 33 195032K 81104K fg root /system/b2g/b2g
715 0 1% S 2 6476K 4864K fg root /data/local/updates/0/updater
854 0 1% R 1 1060K 420K fg root top
And the updater itself (which is the thing doing the uncompressing) is also being dramatically slowed down.
Comment 3•13 years ago
|
||
I tried to grab a profile, but b2g crashes when the profiler is enabled.
Depends on: 875453
Comment 4•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•