If the devices are hidden behind NAT you configured the APX incorrectly. If you configure it as a wireless bridge, everything will be visible.
Posts by chewitt
-
-
-
-
-
If it's crashing with the default skin then the issue is likely an add-on that's installed. The main approach to that is either disabling all add-ons and then (assuming that stops the crashing) you start reenabling them until you find the culprit; or you stop Kodi and move the current install out of the way (preserving it) so you restart with a clean setup. Now you can stop/copy/restart and progressively copy back stuff from the working install (or reinstall things) until you find the crashy thing. I personally prefer the clean-start approach as that generally exorcises or spring-cleans a pile of other Kodi related cruft that's accumulated over time too.
-
Find a spare SD card and see what happens when you clean-boot a fresh image. If it boots fine you narrowed the problem to software.
-
YouTube/Tubed require an API key. Follow guides in the Kodi forum support threads. It's not simple, but once done it's done.
-
From the description; the .deb package install requires sudo (root/admin) rights to be installed. It's not a backdoor password, but since it can be used to gain root rights on the host it's a credential to protect - hence the security best-practice advice of not using the same password for the admin user in TVH.
-
I'd add a second Ethernet NIC into the PC and run a cable to the router that the RPi4 is connected to (ISP2) then set the connection priority in Windows to use the NIC that connects to the ISP1 router as the primary connection. As the PC now has IP addresses in both networks you will be able to download on the ISP1 connection but also connect directly to the RPi4 in the other network to upload/transfer files. If you can't run Ethernet, get a WiFi card and have the PC join the WiFi network from the ISP2 router. As long as you set the connection priority for the NICs it will work the same (only slower than Ethernet). NB: For this to work, the routers must distribute IPs from different IP subnets, e.g. ISP1 router uses 192.168.1.0/24 and ISP2 router uses 192.168.2.0/24. If both routers use the same subnet the IP ranges will conflict.
-
Have a look at the LE 9.2.8 build that dtech created - his thread is pinned. The last official LE release was LE 9.0.2.
-
It's not that there's no interest, it's just something that's proven difficult to resolve (there are multiple attempts). RPi4 doesn't use MMAL decoding these days, so that's only applicable to older RPi devices and older LE/Kodi releases.
-
No idea, we will be using somewhat default Qt options and if there's a change it will be something Qt releated. Nobody on the project staff has much of a clue about Qt - which is why it's taken 2.5 years to respin an updated version of the app. If you can find someone with Qt skills who can take our sources and tell us explicitly what's wrong and needed to support Win7 (without breaking everything else) we'll re-add support. Anything that involves project staff needing to skill up on Qt to fix it won't happen (see prevous 2.5 years comment) and there's a lot more fun, interesting and needed things to do around the project.
-
I have a hunch the version of MariaDB (5.5) is too old. Perhaps try bumping that too.
-
As the screenshot also shows the addons folder size at a looks-correct 286MB value I'd guess "Windows is crap" ..
-
In short, nothing exists. I'd guess because people are either sat in-front of the computer running Growl *or* sat in-front of the TV watching something on the HTPC device. We have no package manager in the OS so you can't just install it. However, if the gntp-send binary is simple you might be able to simply copy it over from, e.g. RaspiOS, but if not you'll need to find a docker container (overkill, but works) or self-build a custom LE image with the package added - there are rather deliberately no instructions for that kind of thing.
-
I meant pushing to your own repo. All looks good, nice to see the work being shared
-
extremeaudio have a look at https://wiki.libreelec.tv/configuration/…figuration-hard .. the article needs an update to reflect the "toml" format being used with ir-keytable now, but basically it's the same process. Despite the "Configuration (Hard)" title, it's not that hard to capture the keycodes and create a custom keymap file. Lots of prior art (and all the kernel IR keymaps) can be found in /usr/lib/udev/rc_keymaps/ .toml files.
-
The best way to avoid HDR > SDR issues is to handle the conversation at the ripping stage, then you have SDR files.