Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[vdr] Re: Nexus and remote plugin
Cyrille Grange wrote:
> ....
> I try like this and -P"remote -i /dev/input/event0", but no changes.
> It still doesn't work.
>
> In "remote.c", in the Start() function, i replace :
> > dsyslog("%s: using '%s'", Name(), devnam[i]);
>
> by
>
> > isyslog("%s: using '%s'", Name(), devnam[i]);
Ok, your syslog filters this message. No problem.
> and i can see in syslog :
> > mai 15 20:27:13 leila vdr[19012]: starting plugin: remote
> > mai 15 20:27:13 leila vdr[19012]: remote: using
> > '/dev/input/event0'
>
> but vdr still not asking me learning keys ...
???
If vdr doesn't ask for keys and remote plugin says 'using /dev/...', you
have already learned them. Delete /video/remote.conf and try again.
Verify that the file is gone before you start vdr.
vdr will tell you which remote control it likes to learn.
Until now I thought that vdr tried to learn keys but does not respond if
you press a key on your remote control. In this case you should verify
that you are using the correct device ('event0').
Use evtest to find out:
#./evtest /dev/input/event0
Input driver version is 1.0.0
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "DVB on-card IR receiver"
Supported events:
Event type 1 (Key)
Event code 2 (1)
Event code 3 (2)
Event code 4 (3)
Event code 5 (4)
Event code 6 (5)
Event code 7 (6)
...
Event type 20 (Repeat)
Testing ... (interrupt to exit)
If you press a key on your remote control, you should see:
Event: time 1053020925.392229, type 1 (Key), code 375 (Screen), value 1
Event: time 1053020925.506211, type 1 (Key), code 375 (Screen), value 2
Event: time 1053020925.750032, type 1 (Key), code 375 (Screen), value 0
Oliver
--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.
Home |
Main Index |
Thread Index