Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#937 closed defect (fixed)

screen dimming issue: lost "more light" events

Reported by: max_posedon Owned by: ainulindale
Priority: major Milestone:
Component: SHR Image Version: SHR-unstable
Keywords: Cc:


<max_posedon> phonefsod doing nice briteness magic: -20% after some "events less" situation
<max_posedon> and +20% on screen touch

  • thrashold (~europan@…) has joined #openmoko-cdevel

<max_posedon> so, briteness jump 80%<->100%
<max_posedon> but sometimes, "touch" event don't generate "increase britness event" (or its become overriden by next)
<max_posedon> so, from jumping 80%<->100%, you have 60%<->80% after
few mins, an then 40%<->60%, and... so on
<DocScrutinizer> anyway sounds like a race

Change History (7)

comment:1 Changed 8 years ago by MMlosh

And it eventually ends in (-10%)<->(0%) and I am boned..

some more clue:
When lcd brightness is changed by writing in its sysfs node, dimming procedures DO use that value.
loss of brightness happens usually when I tap the screen in the moment when it dims down.

comment:2 Changed 8 years ago by Heinervdm

  • Milestone set to MS1

comment:3 Changed 8 years ago by Heinervdm

Please check if this is a Dup of #922

comment:4 Changed 8 years ago by mrmoku

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

phonefsod does not try to adjust brightness anymore. Fixed.

comment:5 Changed 8 years ago by jama

  • Resolution fixed in unstable deleted
  • Status changed from closed to reopened

comment:6 Changed 8 years ago by jama

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

comment:7 Changed 7 years ago by morphis

  • Milestone MS1 deleted

Milestone MS1 deleted

Note: See TracTickets for help on using tickets.