Rockbox

This is the bug/patch tracker for Rockbox. Click here for more information.

Quick links: Bugs · Patches · Rockbox frontpage

Tasklist

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

Attached to Project: Rockbox
Opened by Matthias Mohr (aka Massa) (mmohr) - Monday, 24 April 2006, 08:14 GMT+2
Last edited by Jonathan Gordon (jdgordon) - Monday, 14 August 2006, 16:31 GMT+2
Task Type Patches
Category Remote
Status Closed
Assigned To No-one
Player Type Iriver H300 series
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Private No

Details

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...
This task depends upon

Closed by  Hristo Kovachev (bger)
Tuesday, 15 August 2006, 09:07 GMT+2
Reason for closing:  Accepted
Additional comments about closing:  Thanks
Comment by Paul Louden (darkkone) - Monday, 24 April 2006, 10:08 GMT+2
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)
Comment by Matthias Mohr (aka Massa) (mmohr) - Wednesday, 26 April 2006, 20:41 GMT+2
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
backlight.
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
again.
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 :-)
Comment by Peter D'Hoye (petur) - Sunday, 14 May 2006, 00:57 GMT+2
Do we want this always or configurable through a setting?
Comment by Jonathan Gordon (jdgordon) - Monday, 14 August 2006, 16:30 GMT+2
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.
(application/octet-stream)    non_lcd_backlight.patch (0.6 KiB) 
 firmware/backlight.c |    9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

Loading...