• Status Closed
  • Percent Complete
  • Task Type Patches
  • Category Remote
  • Assigned To No-one
  • Operating System Iriver H300 series
  • Severity Low
  • Priority Very Low
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by mmohr - 2006-04-24
Last edited by jdgordon - 2006-08-14

FS#5223 - main device backlight behaviour for NON LCD-Remote

As the name says, the NON-LCD remote doesn’t have a display.
So I think it would make sense, that for the NON-LCD remote
the remote backlight settings should affect the main device.
Or the settings for the main device should be additionally
used for the NON-LCD remote.

I mean - the main device should switch on it’s backlight,
when I press a key on the remote - at least when I navigate
in the fileviewer… (it does not need to switch on it’s backlight when I lower
or higher the volume though)

I’m not sure it can be called a bug, but I don’t think the
current behaviour is logical…

Closed by  bger
2006-08-15 07:07
Reason for closing:  Accepted
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


I *think* the idea was simply that if you’re holding the main unit, they expected you to use the buttons on it. I suppose it does seem logical for an option of ‘Linked’ in which the remote buttons affect the main unit, and vice versa (if there’s an LCD on the remote)

mmohr commented on 2006-04-26 18:41

Here is a small background story:

I clipped my NON-LCD remote to my car's steering wheel while my 
main device was in shot but not accessible.

I accidentily stopped the currently running song and then had to
navigate in the folders - but of course I wasn’t able to do it
with the remote, because the main device’s screen stayed dark.
So I had to put my hands off my steering wheel, stretch myself
to reach the main device and press a button to switch on the
After that I was able to navigate with the remote - for a small
thime until the main device’s timeout occurs and it goes dark
Same game again…

It would be no problem for any LCD remote but for the NON-LCD
remote it is a problem to navigate without backlight on the
main device :-)

petur commented on 2006-05-13 22:57

Do we want this always or configurable through a setting?

this patch _should_ work.. i dont have a non lcd remote, but i tested it by replacing the check for the nonlcd remote with my lcd remote and it turned the main unit backlight on correctly…

If you dont want this behaviour then set the LCD remote backlight to off.


Available keyboard shortcuts


Task Details

Task Editing