Hmn, interesting. I'll have to check this out, but as far as pushing the hardware's limit, nope, I don't do that. It's the opposite, in fact. I sample the temperature every 10 seconds -not every frame as most apps do and only when requested. That is true for all hardware related info, even the HD space isn't sampled every second. It's only queried when there's a file operation like coy and deletes.
The graphical power requirement of the dash is nothing compared to games which has to render several models consisting of tens of thousands of triangles at 60Hz.
Possible cause would be the way it's calculated. I'm just following the xbox-linux documentation. The value is already in Celcius, and the parameter required is an integer, so I don't know why Evox and some other app can output a non integer value, i.e. 55.4C. Heck, neXgen code was dividing the value by two. I'm outputing whan I'm getting directly from the readout. So, it must be what it is.
Also, 4C difference isn't 39.2F. If your baseline is 44C, it's 7.2F. Remember, we're talking of difference here, not the actual value. 4C is in fact 39.2F, but the conversion isn't linear, like 10C is 50.5F. The difference is 6C or 11.3F, but if you convert 6C, it will yield 43.3F -which ic the straight vonversion value -not the difference.