That is not a problematic temperature for the Vero and should not lead to crashes.
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
Thanks Sam, I def saw the messaged today that it shutdown because it reached critical temperatures… I’ll have to try and get the debug logs off it… The problem is reproducing it unfortunately as it always happens when i’m not around… I’ll try and set the debug logs before i go to bed tonight and see if it’s done it over night.
Is there a way to have the debug log on without it displaying screen?
HI Sam, that’s exactly what happened. the screen dropped to command line, it said critical temperature (amongst other things) around 4 or 5 times then the screen went off and the logo went red.
I’ve got the logs on now, i’ll try and run them as long as i can in the hope something happens again… As I said, i have to repower it atleast once a day (I have it on a smart plug to make it easier) so hopefully it will do it.
I believe some of the views in that skin tax the GPU quite heavily and can cause high temperatures. The good news is that we have GPU throttling in our 4.9 kernel, so this will solve any issues you have with hard lockups.
It would be good to know if using the OSMC skin solves your problems,