[sw4y]

Actually I'm running a Libreelec Milhouse Build (#0426), Generic x86_64 on intel hardware and use a Harmony remote (configured as MCE Remote).
Works fine!

I found out, that the remote does not work, when resuming from suspend and automatically going back to the last tuned channel on live-tv.

The remote itself does work (connected through ssh, irw gives output as expected), but no reaction in kodi.

17:31:42.118 T:139984956856384 DEBUG: LIRC: Update - NEW at 9902:6c 0 KEY_DOWN devinput (KEY_DOWN)
17:31:42.118 T:139984956856384 DEBUG: OnKey: 167 (0xa7, obc88) pressed, action is Down
17:31:42.121 T:139984956856384 DEBUG: CDirectoryProvider[pvr://channels/tv/*?view=lastplayed]: refreshing..
17:31:42.122 T:139984956856384 DEBUG: CDirectoryProvider[pvr://recordings/tv/active?view=flat]: refreshing..
17:31:42.123 T:139984728225536 DEBUG: CPVRDirectory::GetDirectory(pvr://channels/tv/*?view=lastplayed)
17:31:42.126 T:139984845657856 DEBUG: CPVRDirectory::GetDirectory(pvr://recordings/tv/active?view=flat)
17:31:42.146 T:139984728225536 WARNING: CreateLoader - unsupported protocol(pvr) in pvr://channels/tv/Alle Kanäle/pvr.dvbviewer_48.tbn
17:31:42.147 T:139984728225536 WARNING: CreateLoader - unsupported protocol(pvr) in pvr://channels/tv/Alle Kanäle/pvr.dvbviewer_192.tbn
17:31:42.147 T:139984728225536 WARNING: CreateLoader - unsupported protocol(pvr) in pvr://channels/tv/Alle Kanäle/pvr.dvbviewer_196.tbn
17:31:42.148 T:139984728225536 WARNING: CreateLoader - unsupported protocol(pvr) in pvr://channels/tv/Alle Kanäle/pvr.dvbviewer_179.tbn
17:31:42.163 T:139984956856384 DEBUG: ffmpeg[7F50C9A09840]: [swscaler] Forcing full internal H chroma due to input having non subsampled chroma
17:31:42.873 T:139984956856384 DEBUG: Previous line repeats 3 times.
17:31:42.873 T:139984956856384 DEBUG: LIRC: Update - NEW at 10658:160 0 KEY_OK devinput (KEY_OK)
17:31:42.873 T:139984956856384 DEBUG: OnKey: 11 (0x0b, obc244) pressed, action is Select

This is a part of my debug.log, where you see, that lirc does work and onkey-demands are processed.

I went down back to Milhouse' first Kodi 18.0 build to make sure, it's not in his build.
But same reaction.

Kodi 18 alpha bug?

Maybe someone can report same behaviour or even tell, that it works.

greetz

[Milhouse]

I've possibly seen something similar on RPi - after it goes into virtual suspend it won't wake because all input is being ignored by Kodi (keyboard, remote control). Doesn't happen all of the time - it's random - and I'm not sure what triggers it (which makes identifying the cause _really_ difficult) but it may have started in the last 6 weeks. Maybe.

[sw4y]

@Milhouse

Are there any changes regarding the problem with a non-working mce remote after suspend and resuming to last tuned channel on live-tv between versions #0426 and #0430?

I did an update to #0430 but did not test that scenario again.

Did today and it works.

I did not change anything except updating to #0430.


*edit*

Forget everything.

After a complete reboot, remote does not work anymore.
This is strange...

[sw4y]

I've possibly seen something similar on RPi - after it goes into virtual suspend it won't wake because all input is being ignored by Kodi (keyboard, remote control). Doesn't happen all of the time - it's random - and I'm not sure what triggers it (which makes identifying the cause _really_ difficult) but it may have started in the last 6 weeks. Maybe.

On x86_64 wake by remote does always work, also does keyboard.

strange....

[sw4y]

@Milhouse

Maybe I found a solution:

Some time ago I was running an ambilight (Lightpack) which is connected through USB, using boblight.
But somehow boblight was not running well with Kodi Krypton, so I did not use the ambilight anymore, but left it connected to the USB ports.

I just set up boblight again (for fun) to see, if it performs better now.

With boblight configured correctly (adressing boblight the right usb devices), it seems, that after a suspend and tuning to a tv channel, the mce remote (using an USB receiver) does also work correctly.

After one of my last reboots, boblight did not work correctly, neither did the remote.

So I think there's somehow a connection between devices using the computers USB ports.

What do you think?

[Milhouse]

Not really sure as I know even less about Boblight than I do most other things. Presumably if you disable Boblight completely then you have no problem at all?

[sw4y]

No, sorry if you got me wrong.

I think it's not a problem with boblight, as I had not even installed boblight before today.
But the ambilight was still plugged into the USB ports, without using it.

With boblight installed, configured correctly but disabled, the remote does still work after a suspend.

It seems, that Kodi can't handle devices, that are connected via USB but are not in use somehow.
As if Kodi needs to know, where those devices are for.

Hope it get's clear what I mean.

I did not check, but I would bet, that the remote would work, if I disconnect the ambilight from the USB ports.