the cable is hdmi 2.0
That's fine. Please check whether different HDMI modes appear for each skin on video settings.
the cable is hdmi 2.0
That's fine. Please check whether different HDMI modes appear for each skin on video settings.
If it occasionally switches back to 30Hz, then go for that cable approach.
I had a short dev conversation about this issue. Dev says, it's fishy that the IR receivers doesn't get a USB number on boot process. So either the device driver is broken, or the device itself.
Try a regular Linux, like Ubuntu, to check whether it works there. If you also have issues on a regular Linux, I suggest to buy a new IR receiver. Don't ask me, which one, because we don't have a whitelist. If it works fine on Ubuntu, then it probably works on LE, too.
When LE boots, it grabs supported resolutions from the output device. If you use exactly the same HDMI mode (resolution, refresh rate, progressive / interlaced) for both output devices, then it should work without tweaks.
How can you chose a resolution of 1920x1080 (it doesn't matter if "i" or "p") on a Screen that is only "HD-Ready" and has a native resolution of 1366x786 ?
If it's really just an HD-Ready TV, then it's probably no cable issue. I think HDMI negotiation goes wrong here, and I suggest to create a custom EDID with supported resolutions.
I don't use Bluetooth, but I found this by using our search function: RE: Bluetooth audio reliability issues -- paired+connected, but no sound
Pro tip: If you use the search function (magnifier icon), always go to the forums main page first to scan all sub-forums. ![]()
Different volume levels for each headphone are also possible. Use something like this: Click!
You have to create your own config file, which will overwrite the default settings: Click!
...the behavior does not change when I use some other HDMI cables.
Please be precise here - look at the specs, if you find them somewhere. We already had a lot of users, who had the same issue when switch to a 4K TV. So make sure you are using an HDMI 2.0 or 2.1 cable. Those are ready for 4K data rate.
Think I've figured it out - it will play sound when I select interlaced resolutions (1920x1080i, 480i etc) but not when I use standard progressive scan ones (1920x1080p).
I was going to get a better TV anyway but thanks for all your help
You've been reduced HDMI data rate by doing so. Chances are your HDMI cable can't handle higher data rates, so it drops the sound. Get an HDMI 2.0 or 2.1 cable before getting a new TV.
I think network is too slow from time to time. You're lucky, because you use SSD instead of microSD. So you can increase the video cache without killing your microSD: https://kodi.wiki/view/HOW-TO:Modify_the_video_cache
Thanks, but how many Posts will it be ?
It's better not to make this public. We don't want to give spammers any target numbers.
Niceguy You didn't reached the necessary amount of posts, so you're still a moderated guy. Just continue to be nice. ![]()
Niceguy I also have an EeePC. I suggest to try Android-x86 or Ubuntu (where you could autostart Kodi).
No module returned any errors but the ir-receiver still doesn't work.
lsmod after start modules manually: http://ix.io/3LU1
lsmod after hot plug: http://ix.io/3LTY
Good, manual module loading worked. Restart Kodi after this by systemctl restart kodi.
Raspberry Pi OS has a tool to install firmware manually.
Firmware gets updated during LE's installation process. That's why DJ'ing LE cards fails.