Anyone with MTK Device (Helio X20 - X25) can use this modification to get stable performance with acceptable thermal (max 45 degree Celsius).
Need to be root :
disable perfservice in build.prop
set governor to ondemand using kernel adiutor
backup file /etc/.tp/thermal.conf
rename file /etc/.tp/thermal_config_03 to /etc/.tp/thermal.conf
With this setting I can play more than 1 hour of REmake without throttling using MTK Helio X20 phone (Redmi Pro)
(08-10-2017, 02:11 PM)Servlet Wrote: [ -> ]Anyone with MTK Device (Helio X20 - X25) can use this modification to get stable performance with acceptable thermal (max 45 degree Celsius).
Need to be root :
disable perfservice in build.prop
set governor to ondemand using kernel adiutor
backup file /etc/.tp/thermal.conf
rename file /etc/.tp/thermal_config_03 to /etc/.tp/thermal.conf
With this setting I can play more than 1 hour of REmake without throttling using MTK Helio X20 phone (Redmi Pro)
I've generally found my Redmi note 4 MTK has pretty good thermal performance, although MIUI appears to hate dolphin in terms of allocating CPU time.
(08-10-2017, 02:59 PM)Nintonito Wrote: [ -> ]I've generally found my Redmi note 4 MTK has pretty good thermal performance, although MIUI appears to hate dolphin in terms of allocating CPU time.
Generally MTK Xiaomi phone will stop at 41 degree Celsius and then throttling, making dolphin speed is half than normal. My setting enable it to go to max 45 degree Celsius. And with ondemand governor will make cpu not that hot.
(08-10-2017, 03:18 PM)Servlet Wrote: [ -> ]Generally MTK Xiaomi phone will stop at 41 degree Celsius and then throttling, making dolphin speed is half than normal. My setting enable it to go to max 45 degree Celsius. And with ondemand governor will make cpu not that hot.
Ok but that wasn't the issue to begin with, the issue is MIUI not treating dolphin as a high performance application. Not to mention the CPU governor won't help if it's working. Maxed out A72's run hot no matter what governor you use.
(08-11-2017, 10:12 AM)Nintonito Wrote: [ -> ]Ok but that wasn't the issue to begin with, the issue is MIUI not treating dolphin as a high performance application. Not to mention the CPU governor won't help if it's working. Maxed out A72's run hot no matter what governor you use.
But my phone did use A72 core while running dolphin. You can check with multi core observer that 1 of the A72 core always online. Ondemand run cooler than interactive since it will up the freq when needed, and this is what this thread topic, beating thermal throttling, not activating A72 core.
A72 core will turn off in case it hit 41 degree under normal thermal setting. Also thats why you turn OFF perfservice in build prop, MTK control the online core, if you turn off perfservice, hotplug gov will control online core, which will make A72 core online more often.
(08-11-2017, 11:48 AM)Servlet Wrote: [ -> ]But my phone did use A72 core while running dolphin. You can check with multi core observer that 1 of the A72 core always online. Ondemand run cooler than interactive since it will up the freq when needed, and this is what this thread topic, beating thermal throttling, not activating A72 core.
A72 core will turn off in case it hit 41 degree under normal thermal setting. Also thats why you turn OFF perfservice in build prop, MTK control the online core, if you turn off perfservice, hotplug gov will control online core, which will make A72 core online more often.
Doesn't mean the a72 core is being used to run dolphin. Generally core 0 is always seen as active regardless if it's used or not.
Use Resource Monitor Mini and enable the CPU frequency of first CPU Core, then run Dolphin to check if it's running at high clock speed.
(08-14-2017, 07:56 PM)Whatnoww Wrote: [ -> ]Doesn't mean the a72 core is being used to run dolphin. Generally core 0 is always seen as active regardless if it's used or not.
It is mean what it mean, I use multi core observer, have you try ? There is 2 core A72, 1 is always on, X20 have 2 A72, no other 2 pair core, other core is 4 pair per cluster.
And no A53 core can run REmake 30 FPS, it have to be A72, unless you believe SD 625 can run dolphin full speed.
(08-15-2017, 11:34 AM)Servlet Wrote: [ -> ]It is mean what it mean, I use multi core observer, have you try ? There is 2 core A72, 1 is always on, X20 have 2 A72, no other 2 pair core, other core is 4 pair per cluster.
And no A53 core can run REmake 30 FPS, it have to be A72, unless you believe SD 625 can run dolphin full speed.
I'm not sure what Remake is, but being able to run one app without throttling doesn't mean anything much when trying to run another.
A less demanding CPU application could produce less heat, as modern CPUs have power saving states that work on very short timescales, excluding frequency changes - an app that doesn't completely peg a core at 100% may use significantly less power (and produce less heat) than another that does, even if they're at the same frequency. On top of that, different instructions have different power characteristics, with some using more or less power even if the CPU is at 100% (see Intel's modern CPUs throttling on intense AVX workloads, for an example even in the much higher thermal headroom world of desktop CPUs)
Also, on modern SoCs the thermal budget is shared with multiple blocks, big ones being the GPU, display output blocks (that can have complex blending calculations to render the UI), DSPs (that can decode and play sound), video decoders etc. etc. Use cases that use those blocks more heavily may end up throttling the CPU further, as they all use energy and product heat when functioning. Similarly to the CPU, most of those have power saving features that can help when not at full utilisation.
So "Power throttling" is a lot more complex than simply CPU use %age, or current CPU frequency.
REmake refers to Resident Evil 1 Remake on Game Cube play using dolphin.It running 30 fps for 1st 10-20 minutes then drop to 10-15 fps after that.
With my setting, it can run 25-30 fps for more than 1 hour playing REmake. My setting did not disable thermal, it is making thermal throttle upper limit higher, but still reasonable (45 degree Celcius). It is for MTK only. I tested this on my phone using MTK Helio X20, it run cooler when not needed too thanks to ondemand governor instead default interactive, and disable MTK perfservice so ondemand governor used instead of MTK core pilot governor.
Its already stated for specific user only. And it beat thread starter method by disabling thermal throttle completely since its not safe.
Quote:Anyone with MTK Device (Helio X20 - X25) can use this modification to get stable performance with acceptable thermal (max 45 degree Celsius).
I hope it found useful for people with MTK Helio phone like Xiaomi Redmi Note 4 and Redmi Pro. Maybe also other Meizu, but they got Nougat, so better go with sustained performance maybe ?