Closed Bug 1179679 Opened 10 years ago Closed 7 years ago

[Flame] Display is not turning on after a while

Categories

(Firefox OS Graveyard :: Stability, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: mark, Unassigned)

Details

Attachments

(2 files)

Attached file logcat_after_crash.txt
User Agent: Mozilla/5.0 (X11; Linux) AppleWebKit/538.15+ Midori/0.5 Steps to reproduce: 1. Waiting for device going to sleep 2. Wait a while 3. Try to wake up the device with pressing the power button Actual results: Display stays black, but I can connect with adb shell. When tracing in this state, I see that b2g has 0 wakeups. Attaching logcat output. I used the device around 07-02 06:45 Expected results: Lockscreen is shown.
Output of trace.sh from github.com:mozilla-b2g/B2G.git ./trace.sh -t --device NAME PID WAKEUPS RUNTIME NEW b2g 216 0 0 ms no (Nuwa) 474 0 0 ms no Homescreen 933 6 0 ms no Loqui IM 1072 180 53 ms no Calendar 1196 7 2 ms no Find My Device 1224 3 0 ms no Usage 1250 3 0 ms no Built-in Keyboa 1251 6 1 ms no Smart Collectio 1270 3 0 ms no (Preallocated a 8458 6 1 ms no
List of running processes on the device provided by top
Platform-Version: 41.0a1 Build-ID: 20150615010203 Update Channel: nightly Commit: 2015-06-13 00:22.05 1bf2da10 Buildnumber: eng.cltbld.20150212.043653
I haven't seen that issue after flashing to v18D-nightly-v3 some days ago. I used to run into it at least once a day before. So it might be fixed.
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: