You can use the usb-devices command, but I don't think it's helpful. There are not too many device classes in the keymaps folder, so I would trial-and-error to find the right XML.
Posts by Da Flex
-
-
Where do I locate the .xml for the volume knob?
You have to create a key mapping file. LE has default key mapping files.Those files are located at /usr/share/kodi/system/keymaps,
They are read-only. You can overwrite any of these files by creating your own version at /storage/.kodi/userdata/keymaps.
Read about key mapping details here: Click!
-
I can confirm the behavior with Generic. Legacy runs normally
For me it looks like all DRM streams are affected (Netflix , Amazon..).
Sometimes a stream starts normally without the flickering. After stop and start from the beginning the same stream flickers.
Sometimes the black level is also wrong (black is gray).
Newer hardware does not solve the problem (Intel I3 12.th Gen)
If you want to help to find the bug, give us a log file.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
The window manager also handles video output, so the story makes sense to me.
-
Link to error message doesn't work. Please edit your post.
-
Congrats
! Generic vs. generic-legacy doesn't affect the interface to your TV. It's just a different window manager (GDMGBM vs. X11). -
We are currently switching to 64 bit on LE 12, and you see the preparation of the add-on part.
-
Also, I did GUI update, so I think it updated to generic image, could legacy image help? Also, can I update to legacy without any problems?
If the update went from generic-legacy to generic, then it's a bug.
You should see the LE variant on the system info screen.
If it's not legacy, put the legacy image into .update folder by using wget, and reboot. That shouldn't cause problems, and hopefully fixes your Netflix problem.
-
That YT hack is doable, and worth the effort. Good luck!
-
Or create a /storage/.config/autostart.sh script containing the startup command.
-
In fact I’m thinking of bringing it back downstairs 😂
Because of the Windows driver it's a tinker project. I would solder connectors onto the speaker contacts to avoid that driver.
With a frequency switch you could also use the subwoofer. If you don't want to invest the time, bring it back downstairs.
-
Yep, the Magic 100 is one of the best DAC's you can get, and it's known to work with LE. I mentioned the UMC22 in case you want to connect the Bose speakers to a cheaper DAC that just works.
-
I'm using a Behringer UMC22 with my RPi3B+. Works out-of-the-box.
-
This guy seemed confident he had the issue resolved but didn't mention what model RPI he was using. Both the RPI3b+ and the Bose Companion 5 are USB2.00 devices. This really is a curious one. https://forums.raspberrypi.com/viewtopic.php?t=15872
The guy mentioned a quirks file for the kernel. If that file is missing, your quirk alias has no effect.
I suggest to try the same on Raspberry Pi OS. Maybe LE doesn't have that quirks file.
-
If you're coming from LE 9.x, you'll notice a smoother GUI now.
-
I search more powerful hardware to watch 2160p HEVC vids.
You mentioned to need a browser. Then x86 hardware (Intel NUC) is the way to go.
-
Currently the only way is installing LE Generic-legacy on x86, which supports the Chrome browser add-on.
-
i am sorry, this does not help finding a solution..
This means you have to compile your own driver, until it's in-tree.
