Warning: Can't synchronize with repository "(default)" (No changeset 96d22ec3fa3ef6de3ea8dc0d7d398adc9aa071cf in the repository). Look in the Trac log for more information.

Ticket #333 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

Backlight times out regardless of activity, after pressing the touchscreen for "too long"

Reported by: hafting Owned by: mickey
Priority: minor Milestone: milestone5.5
Component: framework/general Version:
Keywords: Cc:

Description

To reproduce: Press the touchscreen - and keep it depressed for some time. A minute or so, perhaps longer than the usual backlight timeout.

After this, the backlight no longer comes on when pressing the screen. It can still be turned on by AUX button, power button, or plugging in usb. But it times out after 30s, no matter what I do with the touchscreen.

I discovered this playing the game liquidwar, where it is normal to press the screen for a long time.

I also saw this playing sudoku. A hard sudoku takes some thinking, so I rest the stylus on an unused edge of the screen to keep the backlight from timing out while I think. But suddenly it times out anyway, and then the touchscreen cannot turn it on again.

Also, pressing the aux button some times can get the phone into the state where touchscreen no longer turn the backlight on (or stop it from timing out.) I noticed this when SHR got ability to "lock" the phone by pressing aux. (In locked mode, the touchscreen doesn't do anything other than turn the backlight on - so no accidental pressing when the phone is in a pocket) This works well for a while, and suddenly it goes wrong.

I see this using the SHR distribution of 16.dec. I reported it on shr trac, and they redirected me to report it here.

Helge Hafting

Change History

comment:1 Changed 4 years ago by jluebbe

  • Priority changed from major to minor
  • Milestone set to milestone6

This will probably require changes to odeviced and/or oeventsd. Postponing to MS6

comment:2 Changed 4 years ago by mickey

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

That's a bug in illume's handling; you should leave backlight handling to frameworkd and turn it off in illume or fix it in illume. Closing as upstream.

comment:3 Changed 4 years ago by dos

  • Status changed from closed to reopened
  • Resolution upstream deleted

That's happening even with Illume handling off. It's not bug in dimming display - it's bug in detecting activity of touchscreen. Somewhere I had log from frameworkd with "Resource temporialy unavailable" about touchscreen device, but I can't find it now.

comment:4 Changed 4 years ago by daniel

That's a really good pointer. I'm currently trying to reproduce this problem (I've noticed this sort of thing before, but didn't know where it was coming from).

Would be great if you can find the log again.

comment:5 Changed 4 years ago by daniel

I've tried triggering this by setting a remote on the FR for a couple of minutes, but wasn't able to reproduce it...

comment:6 Changed 4 years ago by jluebbe

This might be fixed by the new idle handling, please retest.

comment:7 Changed 4 years ago by jluebbe

  • Status changed from reopened to in_testing

comment:8 Changed 4 years ago by daniel

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

I haven't seen this anymore, closing

Note: See TracTickets for help on using tickets.