Re: Help with harmony remote

[Juan <observer1@hotmail.es>]

Hi
I was using the web client hope this is better

El Mon, 21 Dec 2020 12:40:09 +0000
Sean Young <sean@mess.org> escribió:
> Hi,
> 
> First of all, your email is unreadable. It is very to see what I wrote
> and what you wrote. Please fix this.
> 
> On Sun, Dec 20, 2020 at 07:24:28PM +0000, Jesus wrote:
> > Hi
> > 
> > ________________________________
> > De: Sean Young <sean@mess.org>
> > Enviado: sábado, 19 de diciembre de 2020 9:27
> > Para: Jesus <observer1@hotmail.es>
> > Cc: linux-media@vger.kernel.org <linux-media@vger.kernel.org>
> > Asunto: Re: Help with harmony remote
> > 
> > Hi,
> > 
> > On Sat, Dec 19, 2020 at 01:56:50AM +0000, Jesus wrote:
> > > It's a Universal Harmony 350
> > >
> > > This one:
> > > https://support.myharmony.com/en-us/350
> > > https://assets.logitech.com/assets/54199/gallery-1.png
> > >
> > > It's programable, the remote selected for the mouse is named
> > > Media Center PC SE i believe is the mce, and for the other
> > > functions of the pc part I use a remote named Intel Media Player
> > > I believe is mce too but diferent set of keys selectable I've
> > > managed to make work every button I use in the intel media player
> > > remote, for the Media Center PC SE, I only use the mouse part
> > > thats what I have tested, the mouse movement works, the left and
> > > right click are the ones not working
> > 
> > That's interesting, I did not know there was any other device that
> > generates this IR.
> > 
> > > Some recording of the ir using "ir-ctl -r" would be useful too.
> > >
> > > this is the output for the left click:
> > >
> > > +2800 -200 +300 -300 +300 -250 +300 -300 +600 -600 +300 -400 +200
> > > -350 +300 -200 +350 -300 +300 -300 +600 -300 +300 -600 +300 -250
> > > +400 -200 +400 -200 +400 -250 +350 -300 +300 -400 +200 -300 +300
> > > -300 +300 -300 +300 -300 +300 -300 +300 -300 +350 -250 +350 -300
> > > +600 -250 +350 -350 +250 -300 +300 -600 +350 -250 +350 -75800
> > > +2800 -200 +350 -200 +400 -250 +350 -300 +650 -600 +300 -300 +300
> > > -300 +300 -250 +300 -300 +300 -300 +600 -250 +400 -600 +350 -200
> > > +350 -250 +350 -250 +350 -250 +350 -250 +400 -200 +350 -250 +350
> > > -250 +350 -250 +350 -300 +300 -300 +300 -250 +350 -300 +300 -300
> > > +600 -250 +350 -200 +400 -250 +350 -600 +300 -250 +400 -75800
> > > +2800 -200 +350 -200 +400 -250 +300 -250 +700 -550 +350 -200 +350
> > > -250 +350 -250 +350 -250 +300 -350 +550 -250 +400 -600 +300 -300
> > > +250 -300 +300 -300 +300 -350 +300 -250 +400 -250 +350 -250 +350
> > > -400 +200 -350 +300 -300 +300 -300 +300 -250 +350 -200 +400 -250
> > > +650 -200 +400 -250 +350 -250 +350 -600 +300 -300 +300 # timeout
> > > 101600
> > 
> > Actually, that is the right IR for a left mouse button.
> > 
> > > > 688888.335099: lirc protocol(mcir2-mse): scancode = 0x3c
> > > > 688888.335117: event type EV_MSC(0x04): scancode = 0x3c
> > > > 688888.335117: event type EV_SYN(0x00).
> > > > 688888.475123: lirc protocol(mcir2-mse): scancode = 0x3c
> > > > 688888.475142: event type EV_MSC(0x04): scancode = 0x3c
> > > > 688888.475142: event type EV_SYN(0x00).
> > 
> > This is also the right scancode.
> > 
> > I think something else is going on. Please can you do the following:
> > 
> > echo 'file ir-mce_kbd-decoder.c +p' >
> > /sys/kernel/debug/dynamic_debug/control
> > 
> > Now press the left mouse button and see what there is in dmesg.
> > 
> > I hope it says something like:
> > 
> >         rc rc0: mouse: x = 0, y = 0, btns = L
> > 
> > This is what found in dmesg:
> > 
> > 
> > [754581.285199] rc rc0: started at state 4 (600us space)
> > [754581.285202] rc rc0: started at state 3 (267us space)
> > [754581.285208] rc rc0: started at state 4 (300us pulse)
> > [754581.285211] rc rc0: started at state 3 (0us pulse)
> > [754581.285221] rc rc0: started at state 3 (300us space)
> > [754581.285225] rc rc0: started at state 4 (350us pulse)
> > [754581.285229] rc rc0: started at state 5 (17us pulse)
> > [754581.390933] rc rc0: started at state 5 (101600us space)
> > [754581.390938] rc rc0: mouse data 0x00003c
> > [754581.390941] rc rc0: mouse: x = 0, y = 0, btns = L
> 
> I'm guessing you wrote this last thing, it all has the same quotation
> level.
> 
> So the mouse press is decoded; the issue is in the delivery.
> 
> > Please can you test the following patch.
> > 
> > I applied the patch and this is the output, it didn't worked:
> > 
> > 292.578486: lirc protocol(mcir2-mse): scancode = 0x3c
> > 274.264540: event type EV_KEY(0x01) key_down: BTN_MOUSE(0x0110)
> > 274.264540: event type EV_MSC(0x04): scancode = 0x3c
> > 274.264540: event type EV_SYN(0x00).
> > 292.676628: lirc protocol(mcir2-mse): scancode = 0x3c
> > 292.676647: event type EV_MSC(0x04): scancode = 0x3c
> > 292.676647: event type EV_SYN(0x00).
> > 292.816663: lirc protocol(mcir2-mse): scancode = 0x3c
> > 292.816687: event type EV_MSC(0x04): scancode = 0x3c
> > 292.816687: event type EV_SYN(0x00).
> > 293.080537: event type EV_KEY(0x01) key_down: BTN_MOUSE(0x0110)
> > 293.080537: event type EV_SYN(0x00).
> > 293.208540: event type EV_KEY(0x01) key_down: BTN_MOUSE(0x0110)
> > 293.208540: event type EV_SYN(0x00).
> > 293.336535: event type EV_KEY(0x01) key_down: BTN_MOUSE(0x0110)
> > 293.336535: event type EV_SYN(0x00).
> > 293.464540: event type EV_KEY(0x01) key_down: BTN_MOUSE(0x0110)
> > 293.464540: event type EV_SYN(0x00).
> 
> This shows that the button press has been decoded, and sent to the
> input layer. Possibly it is being ignored by libinput.

I think is getting to the ui, when i presss the button the real mouse
moves but I can't click on other thing, I suppose is waiting for the
mouse up

> 
> > It didn't change, I'm quite sure I applied the patch correctly, is
> > there a way to know at runtime?
> 
> You can check uname -r, it should the exact commit if you commited
> the patch.

I rebuild a srpm, this what uname  says
5.8.12-200.st.fc32.x86_64
st is what i use to make them diferent

> 
> So how are you loading the mce_keyboard.toml? It should be loaded by
> putting an entry in /etc/rc_maps.cfg

I'm using this command to load:

 ir-keytable -c -p rc6_mce,mce_kbd -w
 /etc/rc_keymaps/mce_keyboard-mouse.toml ; ir-keytable -v -t -p
 rc-5,rc-5-sz,jvc,sony,nec,sanyo,mce_kbd,rc-6,sharp,xmp,mcir2-mse

The real mouse don't click until I load the original file:

ir-keytable -c -p rc6_mce -w /lib/udev/rc_keymaps/mce_keyboard.toml

> 
> Thanks
> 
> Sean

Thanks again