No log = No problem
Posts by chewitt
-
-
It's hard to comment. My Slice CM3 box died (suspect kids or wife plugged the wrong PSU into it) so I cannot test anything, but I never had issues with the RF remote before. It's not a general issue - else other users would be flagging the problem.
-
Thread moved to the Amlogic section
-
Current pi firmwares show a thermometer in the top-right corner when thermal protection kicks in, and even then the pi is capable of running at very high temperatures for an extended period. In other words, if you didn't see the thermometer and it wasn't insanely hot (which is unlikely in a case with heatsinks etc.) the hang was probably software induced and not related to heat.
-
Kodi debug log please, and any logs from the add-ons itself (if they exist). The add-on was updated the other day to current latest in Kodi github.
-
Start boot the box, wait a few mins for all the tvheadend stuff to settle, demonstrate the problem, then capture the log.
And please use the native "cat /storage/.kodi/temp/kodi.log | paste" function so we don't have to download stuff you attach to posts. It's easier for you, and over cumulative time, considerably less annoying for us.
-
not our sources or kodi sources, so we have no idea what modifications it contains. I built RPi2 from our sources several times in recent days without issues.
-
Is there anyway i check for network or HDD traffic before going to sleep, to prevent it when its being used remotelybasically, no
-
Nope. I haven't a clue about RTC issues/workings. Sorry.
-
I trust the kernel reporting of 100% usage over user claims of free space remaining. So does OpenVPN. Go delete some cruft from the filessytem, e.g. contents of /storage/.kodi/temp, and restart.
-
RPi0/1/2 have a limited CPU and the licenses are needed to use hardware decoding to get output. RPi3 has enough CPU to software decode things under normal conditions.
-
-
You can use the dispmanx add-on from our add-on repo if you want screen remote access, but please note that this is totally insecure and should never be used over an internet connection.
-
put an arrial.ttf with Thai font support in /storage/.kodi/media/Fonts/ and reboot
-
If you run "dmesg | paste" and share the URL, we should be able to see the BT firmware that's missing.
-
Err, yes.
-
LibreELEC.tv/linux.arm.conf at libreelec-8.0 · LibreELEC/LibreELEC.tv · GitHub
config for the driver is enabled in the kernel, so I would guess the answer is yes.
-
Share a kodi debug log and a sample of one of the problem files (30 second or so is enough).