every tool I like to monitor the system seems to be able to work correctly at this system (I know there exists also newer versions )
'Cpu Temperature' v1.5
'CPU Monitor' v5.8
'System Tuner Pro' v3.0.9
But I'm not sure about this tool because I can't get 100% CPU utilisation, maybe because of big.LITTLE handling (by the Android-system)?
'StabilityTest (ROOT optional)' v2.7 => classic test
First shot
This SoC is also temperature sensitive like the amlogic S802 http://www.freaktab.com/showthread.p...-Test-Scenario (instead of the RK3288 http://www.freaktab.com/showthread.p...-Test-Scenario ) and early begins to throttle ...
At CPU utilisation/usage all the tools seems to have problems to calculate the right values at the moment.
E.g. 'Cpu Temperature' v2.0 shows at peak 285%
But at the main part it is useful because I think the temperature value is correct (btw: the curve is also running/monitoring/determining if the app is running at background)
Interactive
At this governor 1 or more LITTLE cores (A7) a often offline (I'm using 'CPU Monitor' v5.92 to see it at a curve):
Here is the monitoring
Throttling
> 60°C -> 1.6 GHz at big (reached really fast / nearly directly)
> 75°C -> 1.41 GHz at big (maybe after ~7 minutes)
> 85°C -> 1.2 GHz at big (maybe after ~20 minutes (BUT not really sure), but at the beginning most at 1.41 and at the end of the monitoring (after 60 minutes) 50:50 jumping between 12 / 1.41 GHz)
What I don't understand is the much different CPU Load (usage/utilisation) but maybe all these tools at the moment not 100% optimized to this SoC???
Also I don't know what I have to think about the way how they/it determine the temperature value.
If you have a look at the 5 min cool-down you can see it decreases in order to ~13 °C nearly at 1-2 sec and after that maybe ~10 °C during the next ~10 sec, so I can't belief that they work with hw-sensors but they calculate it ... BUT at the other hand the big heatsink and the alu-case... (also if I have a look at the first 5 min stress-test)???
3 min idle
5 min stress-test
10 min stress-test
~30 min stress-test (not easy to catch the right moment to get 1.2 GHz at big )
60 min stress-test
5 min cool down
Comment