LibreELEC-RR 9.x [ Emulationstation | Retroarch | Pegasus | DolphinQT | Moonlight | Chrome | Spotify ]

Quote from HaLeXz

Thank you 5schatten

Here are the info.

setxkbmap -query | paste - http://ix.io/1fge

amixer | paste

in kodi: http://ix.io/1fgc

es launched: http://ix.io/1fgd

game dolphin launched: http://ix.io/1fgd

dolphin and es closed, back to kodi: http://ix.io/1fgd

rolled back volume to 100% with alsamixer (in alsamixer I find master volume to 18%, not 25% like RRconfig setting, not 44% like amixer pastebin says)

in kodi: http://ix.io/1fgc

es launched: http://ix.io/1fgd

es closed, back to kodi: http://ix.io/1fgd

rolled back volume to 100% with alsamixer

in kodi: http://ix.io/1fgc

pegasus launched: http://ix.io/1fgd

pegasus closed, back to kodi: http://ix.io/1fgd

I saw the it,us keyboard layout, but in libreelec configuration i cannot remove the second layout... so I changed the second to it too, but even after reboot it and verifying "setxkbmap -query | paste" - http://ix.io/1fgx the keyboard mapping is the same in retroarch (if I press the + button it recognize "rightbracket", if I press - button it recognize "slash" - in the + button I have the rightbracket corresponding to the AltGr combination, but in the - button I only have the _ )

Libreelec log file: log-2019-04-08-19.49.48.zip

Another test: if I leave the master volume to 18% in alsamixer and reboot the system, the alsa master volume rolls back to 100%.

Display More

The keyboard issue is related to Retroarch -> needs to fixed by them
[Linux] [Regression] Keyboard keycodes no longer take into account keyboard layout · Issue #8303 · libretro/RetroArch · GitHub

(Linux) Internationalized-Keyboards issues (tested x11/sdl) · Issue #8042 · libretro/RetroArch · GitHub

About the sound problem well it looks like it always sets back the volume to 44% no matter what you do. My scripts don't touch ALSA volume in any way so have you tried a clean install i.e. to an usb-drive to make sure it's not related to some quirks?

Quote from Lisko

Hi, in topic of keyboards, after an incident some years ago I got several problems to my hands. In the current situation I am way more comfortable typing on my phone than on a keyboard. For my others Linux pcs I use unified remote android app and it works fine. I got the server running on libreelec and with it I can use the mouse fine. The keyboard is almost working but it has an issue: while all the keys seems fine (eg I can type and send alt+esc to exit emulators) but if I try special chars like "@" it completely ignores them. This is a major issue in Chrome and spotify since there isn't an OSK and I can't even login. Do you know an alternative working app for remote keyboard and mouse? Can I help providing some logs? Which one do you need? Thanks for the patience.

Well did you consider a wrong layout? The @ sign might be located at a completely different position?

Quote from Lisko

Yes and it's not wrong layout and it's not a problem only with @ but with all symbols that aren't lecters (/#&...) but periods and commas work.

Well a # is a regular sign while / or & need a keyboard shortcut. So I guess you have to figure out how shift & alt-gr can be executed properly Anyway don't expect to much since the underlaying system does not support NLS for example.

Quote from HaLeXz

Well, I made a clean install with your release a few days after my first post on this thread (maybe less than 2 months) and on it I just copied the addon_data dirs related to the most important addons I had installed on official libreelec (amazon, netflix and tvheadend server) just to save my configurations and data.

All the emulation stuff is clean install of your release and the only things I modified are es config file and retroarch config file (after the last tests I tried to modify dolphin to set the volume).

So... I think the best way for me is to compare these three config files with the originals of your github. Isn't it so?

Really I would like to avoid reinstall it all again. Sure, I can test from a USB stick as you said too, but I think in the end I should compare those files to find out what's wrong.

I'll give feedback of what I'll find.

Thank you again

Display More

Non of my config files or scripts ever touched the ALSA volume so I suspect some malconfigured addon or leftover causes this. The only thing that is configured is the PulseAudio volume & only temporary. Since nobody else ever reported a similar issue I tend to expect it's not related to my build.

But to make sure it's not some weird quirk grab an usb-drive install the latest build and check if still the volume drops when you launch RA since this should start out-of-the box.

Quote from gsky

Installed 20190305-fed2e29 today on a nuc baseboard d33217ck and having audio issues. Audio works fine in kodi, but i cannot set the audio device in rr-config. also .config/asound.conf is not being generated.

http://ix.io/1fti

Well the Kodi debug log is somewhat useless if the problem is not Kodi specific. You can't select hdmi:CARD=PCH,DEV=0 in the rr-config tool? Because this is pretty much a standard output. Anyway upload a complete log zip.

Quote from gsky

I suspected it was kodi specific due to this line:

ERROR: RunAddon: unknown add-on id 'service.rr-config-tool', or unexpected add-on type (not a script or plugin).

I didn't see anything else relevant in any of the other logs.

Correct. When i try to select an output device nothing happens. All i can change is the backend settings.

Understood, when I run /usr/share/kodi/addons/service.rr-config-tool/bin/rr-config-tool.start manually, i was able to generate a .config/asound.conf and got sound. Also without selecting an output, pulse backend occasionaly (rarely) works if I autodetect.

https://drive.google.com/file/d/1akvpusntwlo85b68r45-tcpnkrg2cjt6/view?usp=sharing

Display More

So what did you actually do? You open the addon then select the field "Select audio device" and press enter? Then happens nothing?

Quote from gsky

Correct.

You use a quite old build? Have you tried a recent version?

Quote from gsky

20190305-fed2e29, which comes from the download link on the first page. I could not find the download link for the latest build, so I assumed you first installed this version and updated to the latest (which I have not done).

Follow the step as described in the first post & setup the update tool in libreelec settings.

Quote from andersos

Has the Kodi audio problem on HDMI been resolved? Audio on SPDIF works but I really need HDMI too.

Which Kodi audio problem in particular? The only problem I'm aware of is the faulty Nvidia 415.x/418.x series which screws audio output & that's solely Nvidias fault

Quote from andersos

I only saw some posts about no audio after an update some weeks ago. I used only SPDIF at the time. Now I was going to watch a Blu-ray and needed HDMI. But there was no audio. Before that mentioned update HDMI audio worked perfectly. I run LE on Intel without nVidia or AMD GPU. Do I have to adjust the asound.conf like I had to earlier thus winter?

Well if you use a recent Kernel 5.x build -> read the FAQ