34 replies to this topic

[gerard999]

Hi :

Dreambox 800hd se seems come out these days with a new remote: RC10, From the box, the remote does not seem to facilitate the timeshift option. In the "regular dreambox remote" this used to be the yellow button.

In the rc10 remote this timeshift function can be added with a keymap.xml, and then the button to press would be the play/stop button, which seem to replace the yellow button on the "old" remote.


Works very good, although some times if it does not work, we have to open another channel, and then back to original channel.

However, if we update the software, or re-install openpli, we have to replace the keymap.xml again. Maybe the devellopers can find a way to do this automaticly during update and/or installing openpli image.

This keymap.xml should be transferred to user/share/enigma2, and the dreambox unit should be restarted.

Attached Files

•  keymap.zip   2.87KB   75 downloads

[pieterg]

Can you show the modifications you had to make in keymap.xml?

[davvag]

Does anyone know if this is going to be included in the image? It´s a bit annoying to modify keymap.xml after each update.

Edited by davvag, 25 October 2012 - 13:51.

[hemertje]

First we need the modification

[davvag]

I changed map context "InfobarTimeshiftActions" and "InfobarTimeshiftActivateActions" to look like this:

<map context="InfobarTimeshiftActions">
<device name="dreambox remote control (native)">
<key flags="b" mapto="timeshiftStart" id="KEY_YELLOW"/>
<key flags="m" mapto="timeshiftStop" id="KEY_TV"/>
</device>
<device name="dreambox advanced remote control (native)">
<key flags="m" mapto="timeshiftStart" id="KEY_PLAY"/>
<key flags="m" mapto="timeshiftStart" id="KEY_PLAYPAUSE"/>
<key flags="m" mapto="timeshiftStop" id="KEY_TV"/>
<key flags="m" mapto="timeshiftStop" id="KEY_STOP"/>
</device>
<device name="dreambox ir keyboard">
<key flags="b" mapto="timeshiftStart" id="KEY_YELLOW"/>
<key flags="m" mapto="timeshiftStart" id="KEY_PAUSE"/>
<key flags="m" mapto="timeshiftStop" id="KEY_STOP"/>
</device>
</map>

<map context="InfobarTimeshiftActivateActions">
<device name="dreambox remote control (native)">
<key flags="b" mapto="timeshiftActivateEnd" id="KEY_RED"/>
<key flags="b" mapto="timeshiftActivateEndAndPause" id="KEY_YELLOW"/>
</device>
<device name="dreambox advanced remote control (native)">
<key flags="m" mapto="timeshiftActivateEnd" id="KEY_PREVIOUSSONG"/>
<key flags="m" mapto="timeshiftActivateEndAndPause" id="KEY_PLAY"/>
<key flags="m" mapto="timeshiftActivateEndAndPause" id="KEY_PLAYPAUSE"/>
</device>
<device name="dreambox ir keyboard">
<key flags="m" mapto="timeshiftActivateEnd" id="KEY_REWIND"/>
<key flags="m" mapto="timeshiftActivateEndAndPause" id="KEY_PAUSE"/>
</device>
</map>

It works OK for me so far on the RC10 remote. But I have no idea if it messes things up on other remotes and I am not able to test it either.

[gerard999]

Re-reading my post and the comments :

I did not change anything on the keymap.xml . The way to find out what is different, is to check what is different on this file "new" remote, compared to the "old" remote (.xml), and would be to edit/check both the "old" and "new" .xml files. An expert could look at that.

Further more, if the help button is pressed on the rc-10, it shows an image of the "old" remote control on the tv screen. This looks a little silly for persons who own a new original dreambox 800se with pli, and this issue could be considered to show up in future updates of pli.

On the home page from Dreambox there is some more info about this remote, together with some pdf´s for download and info.

Regards.

[pieterg]

I changed map context "InfobarTimeshiftActions" and "InfobarTimeshiftActivateActions" to look like this:

what were the changed you needed to make?

[davvag]

It looked like this before I made the changes:

<map context="InfobarTimeshiftActions">
<device name="dreambox remote control (native)">
<key id="KEY_YELLOW" mapto="timeshiftStart" flags="m" />
<key id="KEY_TV" mapto="timeshiftStop" flags="m" />
</device>
<device name="dreambox ir keyboard">
<key id="KEY_YELLOW" mapto="timeshiftStart" flags="m" />
</device>
<key id="KEY_PLAYPAUSE" mapto="timeshiftStart" flags="m" />
<key id="KEY_PAUSE" mapto="timeshiftStart" flags="m" />
<key id="KEY_STOP" mapto="timeshiftStop" flags="m" />
<key id="KEY_TIME" mapto="timeshiftStart" flags="m" />
</map>

<map context="InfobarTimeshiftActivateActions">
<device name="dreambox advanced remote control (native)">
<key id="KEY_PREVIOUSSONG" mapto="timeshiftActivateEnd" flags="m" />
</device>
<device name="dreambox remote control (native)">
<key id="KEY_RED" mapto="timeshiftActivateEnd" flags="b" />
<key id="KEY_YELLOW" mapto="timeshiftActivateEndAndPause" flags="m" />
</device>
<key id="KEY_PLAYPAUSE" mapto="timeshiftActivateEndAndPause" flags="m" />
<key id="KEY_PAUSE" mapto="timeshiftActivateEndAndPause" flags="m" />
<key id="KEY_REWIND" mapto="timeshiftActivateEnd" flags="m" />
</map>

and I actually copied the new map contexts from the keymap.xml that gerard999 originally attached here. So I don´t actually exactly know what changes that are neccessary to do...

[pieterg]

I don't like the game 'find the N differences', especially when 'N' is unknown

[davvag]

Sorry but then I don´t think I can give anymore input about this since I´m not an expert in this... And it seems like we will have to live with this bug on the Dreamboxes with the RC10 remote if no one else can tell what to do...?

[ims]

added 3 lines to section InfobarTimeshiftActions:

<device name="dreambox advanced remote control (native)">
			<key id="KEY_PLAY" mapto="timeshiftStart" flags="m" />
		</device>

for timeshift

and add line to section InfobarSeekActions into dreambox advanced remote control (native):

<key id="KEY_PLAY" mapto="playpauseService" flags="m" />

for preview

it seems, rc10 works as advanced rc

[pieterg]

In that case, what you need is the 'KEY_PLAY_ACTUALLY_IS_KEY_PLAYPAUSE' define (which we introduced for the dm8k, in order to fix this particular problem)

Do the key events come out of the input device with the name 'dreambox advanced remote control (native)' ?
In that case, a simple modification in configure.ac will fix it.
We already use this hack on the dm8k and dm7020hd, but we might as well define it for all dreamboxes, because it seems all can use the 'advanced' remote.

[ims]

Do the key events come out of the input device with the name 'dreambox advanced remote control (native)' ?

I don't understand this...

[pieterg]

you have two input devices, one for the 'normal' and one for the 'advanced' rc.
If you can cat /dev/input/eventX, you might be able to try which one produces the output.
And if the old rc and new rc produce output on two different devices (and you might be able to find their names in some sys or proc entry), we can predict whether we can fix things by adjusting the configure.ac conditional.

[ims]

"cat" display nothing for all events

[pieterg]

one of the input devicenodes should produce output (that's how e2 receives the rc events)

[ims]

Tried for all 5 events and nothing was displayed, when i worked with RC, still empty line only...

Added: when i put lines under "dreambox remote control (native)", it dont worked=> it should be "advanced".

And if the old rc and new rc produce output on two different devices (and you might be able to find their names in some sys or proc entry), we can predict whether we can fix things by adjusting the configure.ac conditional.

root@dm800se:~# for i in /sys/class/input/input* ; do echo -n "$(basename "$i"): "; cat "$i/name"; done
input0: dreambox front panel
input1: dreambox remote control (native)
input2: dreambox advanced remote control (native)
input3: dreambox ir keyboard
input4: dreambox ir mouse
input5: IR-receiver inside an USB DVB receiver
root@dm800se:~#

Edited by ims, 12 November 2012 - 09:12.

[pieterg]

Added: when i put lines under "dreambox remote control (native)", it dont worked=> it should be "advanced".

ok, well that proves that the events come out of the 'advanced' device.

So we should be able to fix things by adding the KEY_PLAY_ACTUALLY_IS_KEY_PLAYPAUSE define for the dm800se.
Could you perhaps give this a try in a local build, to confirm it doesn't raise any new issues?

[ims]

ok, I will try it evening.

[MartiniB]

is there way to disable front panel buttons at all?
http://www.dream-mul...8028#post118028