Ticket #1952 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

[Systemsoftware] it wakes up from suspend but screen is blank time

Reported by: regina_kim Owned by: andy@…
Priority: high Milestone: Om2008.9
Component: kernel Version:
Severity: major Keywords:
Cc: testing@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible: always


rootfs : Om2008.8-gta02-20080901.rootfs.jffs2
kernel : Om2008.8-gta02-20080826.uImage.bin

Description + current result :
1) wait until goes to suspend.
2) press power button to wake it up -> screen is still blank time

correct result : it should turn on screen as well.

Change History

comment:1 Changed 11 years ago by zecke

What is this supposed to mean? Do you mean the device wakes up but the screen remains black? How do you know that it is waking up at all? Got a picture?

Sounds like ompower misbehaving.

comment:2 Changed 11 years ago by marek

Correct - the screen is blank but the device is running. They showed it to me. We could connect via USB and issue arbitrary commands. I mailed Andy several times to ask what kind of debug output might help. No answer so far ...

comment:3 Changed 11 years ago by zecke

blank as in black. So it is not white screen of death?

It sounds a lot like ompower leaving the backlight off or the kernel ignoring/resetting it. Sadly raster refused to cooperate with andy on this issue...

What you could test is trying to manually enable the backlight again.

cat /sys/class/backlight/pcf50633-bl/brightness (and put the brightness here)
echo 63 > /sys/class/backlight/pcf50633-bl/brightness (max brightness)

comment:4 Changed 11 years ago by marek

Correct - blank as in black. We did not find the famous WSOD. ;-)

Here some test results:

cat /sys/class/backlight/pcf50633-bl/brightness

The "echo 63 ..." does no change anything, of course.

But if you touch the screen after you woke the neo up it resumes fully. I guess we have a screensaver running that shows a black field.

comment:5 Changed 11 years ago by andy

So, who do we reassign this to who can do something about it then? It doesn't seem to be a kernel issue.

comment:6 Changed 11 years ago by regina_kim

  • Status changed from new to closed
  • Resolution set to fixed

kernel : 20080903
rootfs : 20080904

it has fixed.

Note: See TracTickets for help on using tickets.