How do you "stop" the movie and do you exit the movie and then shutdown correctly? I don't use .iso but I have never had an issue with mp4, avi or mkv.
It's possible, because an .iso is just a container for the DVD file structure, that Kodi doesn't know where you left off
Having issues trying to download the link.
Does the file play locally - ie without the NAS
Access to SSH is explained in the LE wiki SSH
I have a feeling this is a MP3 tag issue, Can you post somewhere a snippet of an offending mp3 file - if legal.
Also can you try 8.90.003 and see if you have the same issue.
As my crystal ball is currently in for it's 10,000 numpty service, I'm unable to determine your H/W and as you haven't included a log, I have no idea how to reply.
Room temperature is about 20o but it's also in a cabinet so a bit higher. When you get the unit, check the temp via SSH with "cputemp" and also "top" to see what it is the main process that might be causing the issue - if there is one.
Do you ever have any issues with your Mecool M8S Pro+ running hot?
My Mecool M8S Pro+ runs at about 45 - 50o in a heated house. If you're above 60o then something is not right.
As LE 8 (Kodi 17) is now frozen, you will need to confirm that the issue exists in 8.90.003 (Kodi 18) otherwise there is no point debugging your issue.
Do you experience the same issue with 8.2.5? If not then it's a possible issue.
The Mecool KIII Pro looks good, but you will have to do the research to see if the tuner is supported or wait to see if anyone who has one answers this thread.
At the end of the day, the best way to get answers, is to do your own research and then ask if the box/tuner is supported. This is a good start Guide.
I've been looking at the Wetek Play 2 for ages, and it is always out of stock, so not too sure if it's a manufacturing delay or they no longer sell it.
AFAIK. Only Android boxes have integrated DVB-* but if you go for USB then your options are greatly increased.
Please direct your query to CoreELEC
I'd try a different HDMI cable and see if that improves things. How long is the HDMI cable and do you have an extension? Also double/double check the connections.
Do you get the same issues using another O/S like Raspbian?
The heat sounds like a problem to me. Have you got the correct thermal pad for the B+ on the case? (There is a difference in the size of the B & B+ CPU)
Also the output of dmesg | paste and top -b -n 5 | paste
You can monitor the CPU temp with
watch -n 10 cputemp
Anything over ~60o may indicate a problem. - Try the same without the case.
Of course I did this
For someone asking for advise, you're sailing close to the wind.
--------------------------------------------------------------------------------
After a bit of playing around, I think everything is working as intended.
By default (for whatever reason) the fsck at boot is disabled max_mount_count=-1. By changing this (in your case to 1) it means that a fsck will be run after every boot.
However, and this is where the confusion lays. The fsck is being run but only fsck (Check) not fsck -a (Check and repair) - this is why the e2fsck message is being shown. It's telling YOU to run the command for the reason given.
Can you try the latest 8.90.003 test release and see if you have the same issue.
1) RPi3B or B+. If B+ are you using the correct thermal pad on the case?
2) Try the latest Milhouse builds as these have improved hevc decoding and should be less CPU intensive - although still not perfect as it still has to be processed in software and not hardware.
3) Your only other real option is to use a fan. I've used 5V mini fans quite successfully which drops the temp by about 10 - 15o but this won't work with your case. I also found that they tended to be rather noisy but hooking them up to the 3.3v rail dropped it to an acceptable level.
4) N-itrogen (Banned word for some reason) cooling Here or water cooling Here but probably not serious contenders. (Cheaper to buy a AMLogic Box)
AFAIK - you have corrupted to bootloader and thus nothing will load. You need to search elsewhere for solutions - it MAY be possible to recover, but this is beyond the scope of this forum. Good luck.
As LE is a R/O system, any command you issue is unlikely to remain after a reboot (I'm surprised that you didn't see an error message) - so that might explain why it didn't work as expected.
Any reason you believe it didn't work?
However, AFAIK, LE does do a fsck before mounting, so maybe it's related to the USB. I assume it's formatted as ext4?
How did you move /storage to the USB device so that RPi mounts it?
