Sorry bro. I gotta correct myself. Testing right now SPECIFICALLY for the thermal throttle temperature (CPU Throttling test and Hktweaks split screen) I noticed that above 70C nothing happens. But at around the 3 minutes mark, the little CPU dropped from 2002 to 1794Mhz even though the maximum frequency was still set at 2002. Stopped the benchmark and after a while the 2002 started being used again. No 1950. Now benchmarking it’s back at 2002. I’ll check if the event repeats itself.i mean the "70C" doesnt exist in the sources, so it could be affected by say an increase in gpu temperature etc and thus triggered it . from the sources i found the 1st warning temperature is 85 if i remember it correctly. so chances that there were something else triggered, or as a result of something which prevent the cpu to arrive at the first warning temperature, cant tell at this point
besides, i found that the relationship between the cpu and gpu are very closed, meaning that if you oc the cpu, the gpu will be affected as well. that's why you may find that i have removed the gpu oc but left the cpu oc there
anyway, these will be addressed next
update: 2:30 minutes mark. Max GPU temperature registered is 58C. Max CPU is 74 under maximum stress. Throttling of the little cores happened at the 2:30 minutes mark at 72C CPU temperature and 57 GPU temperature. Little cores dropped for a short while to 1950 and then to 1794 remaining stable there. Maximum little core frequency is now forced at 1950.
@ykkfive (sorry for the second ping). This is getting more and more confusing lmao
update 2: No changes with disabled Samsung hot plug. At temperature 74C CPU at the 1:22 minutes mark, LITTLE cpu dropped at 1950 and forced max frequency at 1950. I am starting to think there has to be some kind of “timer” when cpu load is very high at this point. Or maybe it’s cache like that guy said.
I don’t think 85C can be reached unless there is 100% cpu and GPU usage. CPU at 100% usage barely reached 74. We have OC headroom. A lot too. But if we don’t figure out where this problem is coming from we can’t do much.
at this point…is this some kind of power throttling?