- Status Closed
- Percent Complete
- Task Type Bugs
- Category Drivers
- Assigned To No-one
- Operating System Iriver H300 series
- Severity Low
- Priority High
- Reported Version
- Due in Version Version 3.0
-
Due Date
Undecided
- Votes
- Private
FS#4849 - hold button detection does not work 100% (H300 - NON LCD remote)
When my H300 NON-LCD remote is plugged in,
the hold sign of the remote “flickers” -
it randomly shows that the remote’s hold button
would be selected - but it isn’t.
This happens every few seconds and lasts for less
than a second.
It happens for both directions (when the hold button
is selected it shows that it would not be selected
and vice versa)
It happens on all screens (not only the WPS screen)
so I assume it must be a problem of the driver.
Maybe it could be “normalized” - so that a hold button
change needs to last for a minimum time (e.g. 1 sec)
before the change will be relayed to the screens…
Closed by mmohr
2006-04-27 14:10
Reason for closing: Works For Me
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
2006-04-27 14:10
Reason for closing: Works For Me
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
Seems to work now!
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
I don't recognize that behaviour lately - it seems to be fixed!
So I think this issue here can be closed!