Posts by siriusbox

    I've been also testing Hades 1.1 release and it has the same problem, I strongly thinks that the problems comes for the little margin the HDMI 18 gbps bandwidth has on those scenarios, Sony HT-A9 has a full 2.1 HDMI (FLR?), but the HTPC and, specially, the Hisense Projector (at the end of the chain) are both TMDS, in practice, the moment anything in the chain try to pass from 3840x2160/60hz/8bit (from the Kodi UI) to anything with a higher depth, the negotiation fails, maybe it tries first the depth change and then the frequency one, so the moment it changes to 10bit it doesn't matter how low the frequency is, even with the needed bandwidth the negotiation says no :D

    The way I solve the problem, not ideally, is by setting Kodi UI to 1920x1080/60Hz and forcing "compatiblity" mode for the HDMI port in the projector, which actually limits the signal to a maximum ok 4K/30Hz, not a problem in my case, since I don't have movie above that. And the only one that comes to my mind "Gemini Man" is not in my collection.

    But as I said, something different it has been done in OSMC since I never have that kind of problems with Vero V.

    A little offtopic CroqueMr now that I've tested latest Hades 1.1 release, I've found a couple of surprises for my particular needs:

    • Nvidia Shield TV Remote bluetooth connection problems are solved.
    • Is incredible useful to have Restart to LibreELEC and Restart to Windows in the LibreELEC shuthdown menu, for those, like me that make dualboot.

    Thanks as always for your work.

    Same HDMI negotiation issues here, in my case I've my HTPC connected to a Sony HT-A9. The same chain but with my Vero V doesn't have this problem, and it's also Linux based.

    In my case is not only fails sometimes when switching from BIOS prompt to LibreELEC is also happening when playing HDR10 movies, (not happening with Dolby Vision ones), my guess is some kind of bad negotiation when switching resolutions and bit depth modes, DV is tunneled through a RGB444 8bit, HDR10 sends 10bits, also in 444 (I think), which should be no problem for a 23.976 or 24 hz in terms of bandwidth, but something happens in the middle, I don't know. As others also commented, turn off and turn on, the deco make the image appear again, it's like at this moment the negotiation is correct.

    I didn't have the time to put any logs or open an issue, sorry, I will try during this weekend it that helps.

    Yep, the thing is it works without interruptions in Windows 11 and it also works in Vero V (which is Linux based too), I don't know if Vero V uses BlueZ.

    I've captured more logs with btmon and summarize them (well Claude did it for me :D)

    Any clues?

    Please share debug logs from the current LE13 nightlies - otherwise not much to guess at.

    This could help?

    wow, S24 HDR10+ works now :thumbup: it tell´ s something about missing curve, but I works and shows DV, no freeze/crash.

    jumping in chapters (Ryan FEL mkv) works great and fast.

    another mkv FEL (Nürnberg) is playing, but if I jump to the next chapter playback ends with an error, but no crash :thumbup: maybe a bad rip, in Hades build I can jump... I´ ll try more movies.

    I think CroqueMr and Hades should sit down together for a few days ;):S making a ultimate version

    There is a loooot of bad rips out there.

    Today is quite easy with AI to create scripts to test any kind of RPU sync problems, the most common source of problems, using dovi_tool, ffmpeg and ffprobe, I always suggest to do that in case of suspicious artifacts, flashes, laggy frameskipping, etc.

    Hi everyone,

    I'm experiencing persistent Bluetooth connection issues with my NVIDIA Shield TV Remote (2019) on LibreELEC x86_64.

    The remote pairs successfully and all buttons work correctly, but the Bluetooth connection keeps dropping and reconnecting repeatedly. Sometimes it stays connected for around 10 seconds before disconnecting, then reconnects after a few seconds, repeating this cycle indefinitely.

    I've also tested two different Bluetooth adapters and two different Shield remotes, with identical results:

    Bluetooth adapters:

    • Onboard Bluetooth: Intel Wireless-AC 3168 (ASRock B660 ITX/ac motherboard).
    • USB Bluetooth dongle: ASUS USB-BT500 (Realtek RTL8761B).

    Troubleshooting already performed:

    • Tested both onboard Intel Bluetooth and the ASUS USB-BT500 dongle.
    • Tested the ASUS dongle on a USB 2.0 port instead of USB 3.0 to rule out potential USB 3.0 interference.
    • Performed a full cold boot to ensure no residual Bluetooth configuration or state from Windows was affecting the onboard Intel adapter.
    • Disabled the Wi-Fi functionality of the onboard wireless card.
    • Tried manually pairing, trusting and connecting the remote through bluetoothctl over SSH, bypassing LibreELEC's graphical interface.
    • Tested both remotes and both LibreELEC builds.

    None of these attempts made any difference.

    Additional diagnostic information from the onboard Intel Bluetooth adapter:

    • USB ID: 8087:0aa7.
    • Bluetooth handled by btusb over xhci_hcd.
    • rfkill showed Bluetooth as neither soft-blocked nor hard-blocked.
    • Intel firmware patch was successfully loaded (patch num: 3c), with no obvious firmware or controller errors in the logs.
    • Kernel logs showed repeated HID device initialisations for NVIDIA SHIELD Remote (0955:7217).
    • During the connection failures, bluetoothctl reported Connected: no.

    System:

    • ASRock B660 ITX/ac motherboard.
    • Intel Wireless-AC 3168 onboard Bluetooth.
    • ASUS USB-BT500 (Realtek RTL8761B).

    For reference, the remote works perfectly without any interruptions under both Windows and OSMC Vero V. The problem only occurs under LibreELEC.

    At this point, I'm wondering whether this could be related to BlueZ, the Linux Bluetooth stack, HID handling, or a compatibility issue with the Shield Remote itself.

    Since the exact same behaviour occurs with two different remotes, two different Bluetooth chipsets and two different LibreELEC builds, I suspect this might be a software compatibility issue rather than a hardware fault.

    Why I'm particularly interested in getting this remote working is the Shield Remote 2019 has both Bluetooth and IR capabilities. This combination is particularly useful in my home theatre setup. I use Bluetooth for Kodi navigation and other remote functions, while IR is used to control the volume of my audio decoder.

    This makes it an ideal remote for setups where HDMI-CEC isn't available or cannot be used. It allows me to control both Kodi and my audio equipment with a single remote, without relying on CEC.

    I'd be happy to provide additional diagnostic logs or run specific tests if that helps identify the cause.

    Thanks!

    Khazar I've been experimenting similar issues with Nvidia SHIELD Remote, connected by bluetooth with an excellent range in my case, since my Asrock B660 ITX/AC uses antennas for both wifi and bluetooth. In my particular case, the remote pairs but then, it disconnet and connect continously, without any pattern, it's imposible is a problem with any kind of suspend mode y continuosly click buttons on the remote.

    I also tried with a ASUS dongle to discard a incompatibility of the Asrock mother board Intel controller. No luck, same problem.

    NVIDIA SHIELD Remote is particulary interesting since it integrates a IR too, so I can make volume on my a/v receptor works at the same time bluetooth works for the rest, you need SHIELD also to first programm that.

    I'm desesperante with theee disconnetions.

    Khazar I've been experimenting similar issues with Nvidia SHIELD Remote, connected by bluetooth with an excellent range in my case, since my Asrock B660 ITX/AC uses antennas for both wifi and bluetooth. In my particular case, the remote pairs but then, it disconnet and connect continously, without any pattern, it's imposible is a problem with any kind of suspend mode y continuosly click buttons on the remote.

    I also tried with a ASUS dongle to discard a incompatibility of the Asrock mother board Intel controller. No luck, same problem.

    NVIDIA SHIELD Remote is particulary interesting since it integrates a IR too, so I can make volume on my a/v receptor works at the same time bluetooth works for the rest, you need SHIELD also to first programm that.

    I'm desesperante with theee disconnetions.

    Regarding cmv2.9 and cmv4.0 and black crush, I would like to know if this is also could be related with L2 trims.

    Disabling L2 trims fixes washed blacks in some movies on my Hisense PX1 Pro, but I always find It strange that some other movies with L2 trims enabled looks ok. Maybe we are looking to the wrong place.

    I'm curious about from where the option to disable L2 trims comes in first place to Hades build. I have an open request for that feature on OSMC, but previous to that, I didn't find anything about this problem, I find it out as a conclusion from Claude and then testing myself by doing MKV samples without L2 trims, and also removing 100, 600 and 1000 blocks separately. In my case 100 seems to be the problem, but only on some movies.

    CroqueMr I've been testing your beta5 on my i3 12100, more than enough power I think...

    Two things I would like to ask:

    • Would be possible to have a switch to turn off L2 blocks like Hades build does?. Some projectors, like my Hisense PX1 Pro, have problems handling L2 trims and blacks are washed on some movies.
    • I've a NVIDIA Shield TV 2019 remote, it pairs successfully over Bluetooth, and all buttons initially work. However, the connection repeatedly drops and reconnects. I've a ASRock B660 ITX/ac which uses Intel Wireless-AC 3168 for both WiFi and Bluetooth, on Windows, connection with the remote is rock solid, but that's not the case for LibreELEC (it hapens also on Hades build), maybe an old drivers in Linux?

      Code
      Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth
      Code
      Bluetooth: Core ver 2.22
      Bluetooth: HCI device and connection manager initialized
      Bluetooth: HCI socket layer initialized
      Bluetooth: L2CAP socket layer initialized
      Bluetooth: hci0: Legacy ROM 2.x revision 5.0 build 25 week 20 2015
      Bluetooth: hci0: Intel device is already patched. patch num: 3c
      Bluetooth: MGMT ver 1.23

    Thanks your work on this.

    Hi everyone, first post!

    Anyone is using a dual boot solution? My problem is, I already have a relatively powerfull Windows HTPC NAS with a i3 12100 (that I could update to anything from there to top of the 14th) with 16 GB RAM, that I bought in the good times where hardware had reasonable prices :D

    I've all the tools there and I find a bit silly to buy another PC with lower specs when I can have it in the same machine.

    I already tried and it boots using bcedit, but I still need to fix how to keep bluetooth remote paired in both systems, and still not sure about need to switch from one to another.

    I'm looking forward for similar experiences.

    PD: I also own a VeroV, for me, at this moment, is something more like a backup, the huge diference I would say is the speed of the UI vs OSMC due limitations of amlogic SoC, and maybe how the HDMI chain is handled sometimes.