(05-04-2016, 05:50 AM)Luke Wrote:(05-03-2016, 08:46 AM)androsch Wrote:(05-03-2016, 08:41 AM)montero65 Wrote: androsch, I'm assuming he means 38°C, not °F. 38°C = 100.4°F.Yes, i hope so, even 38 degrees C are way too cool for this board? Mine is getting hot to above 80 degrees C of course and afaik longsleeps kernel stops the board about 110 degrees C! So i wonder how he constantly has below 38 degrees C?
I cannot speak for all imgs and OS, but under the most recent debian the cpu throttles at 80*C
[edit] more specifically, it hits 81-83 and then throttles back - so I'm guessing 80*C is it
That depends on the so called THS settings used and is only a kernel thing. Both TL Lim was correct reporting 38°C (since he operated his Pine64 boards back then in February with just one active CPU core any more -- for the reason see below) as well as you are right when you report throttling jumping in at 80°C NOW.
What happened? The community took over.
We all started with the usual horrible BSP kernel (still used with Android and RemixOS). The BSP kernel for A64 is pretty similiar to the one for H3/A83T so everything as expected. The original Allwinner settings lead to killed CPU cores after short load bursts. When using Android this results in a somewhat sluggish user experience but gaming and watching video still works flawlessly with just one CPU core left (due to working drivers that make us of Mali 3D GPU acceleration and CedarX HW accelerated video decoding that do not run on the CPU cores at all).
So what happened? Since the community already knew what to expect some started immediately to port over RPi-Monitor to be used with A64/Pine64, others looked into a way to bring back CPU cores when the horrible BSP kernel THS settings killed CPU cores and we all joined together and spent a lot of efforts on continually improving these settings so that both thermal behaviour improved and performance as well. The whole story can be found here: https://github.com/longsleep/build-pine6...-191982504 and below.
So when you experience really low SoC temperatures with Android or RemixOS the simple reason is that our community developed THS settings (kernel / device tree stuff) were not adopted and that Android/RemixOS already runs on a single or just two cores (this behaviour was pretty easy to reproduce in the beginning. Even short load bursts led to 2 or 3 CPU cores being shut down just like it was with H3 boards back in 2015 before we repaired the settings there).
And that you're now able to enjoy superiour performance within Linux (and maybe also Android/RemixOS) is the result of the aforementioned tuning process a few community members spent a lot of time on.
And the really sad part in this whole story is that OS images that do not adopt these latest fixes are still prone to bad overall performance and that developer's work has been thrown in the bin this way. All this is well known but the information won't be spread by the responsible people.
