Posts by HiassofT

Thanks for the info!

Can you check if this build fixes the IR repeat issues?

libreelec-rpi2.arm-9.0-devel-20181020140428-bd467bb.tar

so long,

Hias

Can you please post a link to your full dmesg dmesg | paste and the output of ir-keytable? If you are using the crazycat drivers can you please also test if you get the same issue with crazycat disabled and the standard kernel drivers?

so long,

Hias

Hmmm, the remote doesn't seem to follow the rc5 protocol too well - or there's some bug in the IR receiver driver of your card that then causes rc-5 decoding in the kernel to fail.

On quickly repeated button presses you should see the toggle bit flipping instead of getting different scancodes for the same button. eg

799.923295: lirc protocol(rc5): scancode = 0x1015 toggle=1
800.183294: lirc protocol(rc5): scancode = 0x1015

But that's no big deal, you can work around it with 2 scancodes for the same button in your keytable - like you already did.

The more problematic thing is that the signals seem to arrive at about 250ms interval instead of 110ms which is the standard for the rc-5 protocol. Therefore the kernel will interpret the scancode as distinct button presses and the normal repeat handling won't work.

You should be able to work around this by increasing the IR receive timeout with eg ir-ctl -t 200000 - you can play a bit with the value, 150000 should probably work as well and give a bit better response or you can go up a bit, eg to 250000. Just test what works best for you.

so long,

Hias

Can you post the ir-keytable -t output of a ~1second button press?

so long,

Hias

Thanks for the logs!

It's quite certainly a race between kodi and eventlircd and we are already working on it - see also this thread: Remote control troubleshooting

so long,

Hias

Thanks a lot for the info!

This seems to be a race between kodi and eventlircd grabbing the input device and if you're unlucky (and kodi "wins the race") the OK button won't work. So far this hasn't shown up during testing.

We'll have a look how we can best solve this issue and hope we have a fix soon.

so long,

Hias

Thanks for the info! Can you please post the output of lsof | grep /dev/input? dmesg would be helpful as well and we'll need to know which system (RPi, x86, ...) you are using.

Please test if restarting kodi and eventlircd, using the commands shown in this post LibreELEC 8.90.006 RPi Sony PS3 BT Remote limmited functionality. helps you get a working OK button.

so long,

Hias

What kind of IR receiver are you using, did your remote come with it's own USB dongle?

Please post the output of dmesg | paste

so long,

Hias

Could you please tell us which systems your are running LibreELEC on and post kodi debug logs where you pressed buttons that aren't working?

Please don't restart kodi / eventlircd, just enable debug logging in Kodi, reboot LibreELEC, then press buttons and if they aren't working grab the logfile and upload it

Provide Log File [LibreELEC.wiki]

so long,

Hias

FYI: Benjamin Valentin submitted a driver for the Xbox DVD dongle to upstream linux and also PRed it for LibreELEC

linux: restore Xbox DVD Movie Playback Kit support by benpicco · Pull Request #3015 · LibreELEC/LibreELEC.tv · GitHub

A few minor issues have to be ironed out, but this means support for the original Xbox dongle should be back soon.

so long,

Hias

Can you post the output of tvservice -m DMT and tvservice -m CEA?

Maybe your projector has a broken EDID, those commands should give some hints about that.

so long,

Hias

Add "ssh" to the end of /flash/cmdline.txt, after "quiet". Note that everything has to be in a single line and that there has to be a blank between "quiet" and "ssh".

You can also edit this on your PC, cmdline.txt is in the first (FAT) partition of the SD card. If you do this make sure the file is saved with unix lineendings, so eg use Notepad++ on Windows.

Or connect the RPi to some HDMI monitor and perform initial configuration there before switching to the problematic DVI cable setup.

so long,

Hias

ssh into libreelec and then run tvservice -s and post the output.

I'm using a HDMI-DVI cable on my test setup without issues and the tvservice output here looks like this:

state 0x120006 [DVI DMT (36) RGB full 5:4], 1280x1024 @ 75.00Hz, progressive

You should get a similar line, with "DVI" and "DMT" in there. If the HDMI cable is disconnected the RPi will switch to analog (CVBS) video output and you get a line like this:

state 0x40001 [NTSC 4:3], 720x480 @ 60.00Hz, interlaced

Note the "NTSC" in there, this means analog output is used.

If auto configuration via DDC/EDID doesn't work you might need to manually set the video mode, using hdmi_group and hdmi_mode parameters in config.txt - see the RPi config.txt docs for details: Video options in config.txt - Raspberry Pi Documentation

so long,

Hias

AFAIK a Kodi game frontend (plus all the kodi backend database stuff needed to manage this) had been planned for Kodi 18 / Leia but retroplayer / games turned out to be more work than expected, so this had to be moved to Kodi 19.

so long,

Hias

Quote from wwessel

15:35:13.799 T:140619617347328 DEBUG: LIRC: - NEW 16d 0 KEY_EPG devinput (KEY_EPG)

15:35:13.805 T:140619625744512 DEBUG: HandleKey: two (0x32) pressed, action is ActivateWindow(TVGuide)

Does it mean that the setting for key 16d has changed?

Yes, this was a fix in kodi. KEY_EPG should bring up the EPG / TV guide, previously it was mapped to the "title" action KEY_EPG is wrongly mapped to title instead of guide · xbmc/xbmc@5e3e056 · GitHub

You have to change your remote.xml if you want to map the EPG button to bring up the context menu.

so long,

Hias

Until Kodi gets a native frontend for selecting games the easiest way is to use the Internet Archive Game Launcher addon by zachmorris Internet Archive Game Launcher

A lot of more info is available in the retroplayer section of the Kodi forum Kodi Community Forum - RetroPlayer

Basically you just have to install a mame addon from the LibreELEC repo and setup your controller. Then use the game launcher or enter the konami code, setup advancedsettings so that zip etc files aren't associated with audio/video files and select ROMs via the file list in the Games section of kodi and open them via the context menu / play with...

so long,

Hias

Quote from hundrakg

Why is the Pi3b+ so much more unstable? or is it?

Quite a lot of kernel and firmware issues with the RPi3B+ have been fixed since 8.2.5 came out. If you are experience instability on your RPi I'd recommend switching to the latest alpha release (8.90.006).

so long,

Hias

The big rainbow screen appears for a short moment during powerup on all RPis. If you ubigse a too old OS, eg LibreELEC 8.0 or early 8.2 versions, on a RPi3B+ it'll be stuck on that big rainbow screen plus you'll have a lightning bolt in the top right corner.

So, the description is correct, only inaccuracy is that they shouldn't call the RPi3B+ just B+ as there also was a (RPi1) B+ model.

If your 3B+ boots fine into LibreELEC this means the OS is new enough. If you then occasionally see a lightning bolt in the top right corner it means the power supply (and/or power cable) isn't adequate and should be replaced.

After a lot of frustration with PS issues in the very early RPi days I switched to using only the official RPF power supplies a couple of years ago (also bought them from Farnell/RS)- and didn't have any issues at all with them. So that's a clear recommendation from my side.

so long,

Hias