hello to all, i noticed that my redmi note 3 pro KATE ( i am on globerom 8.1.1.0 stable) has the minimum clock for big cluster, setted at 883mhz , and little cluster 691mhz BUT i can select on kernel adiutor the min freq of 400/ 400 mhz.
QUESTION 1 about freqNow i am with L speed app , and applied battery profile, but i don't understand why it does not automatically set the value to the MINIMUM POSSIBLE. Is there a reason?
Is there any CON to set the minimum cloto to cpu at 400mhz? i don't understand why xiaomi.eu and globerom modders did not set this freq to lowest possible, is it maube harmfull for the device?
should i have to set it by myself in kernel adiutor app? please help me to use this app, i just suppose i must apply 400mh setting, THEN choose to apply to boot ( there is a toggle).
What if i set at 400 and NOT toggle it?
QUESTION 2 about differences L speed and gov tuner flashable zip.I am sorry to admit that i'm not such skilled into android development and i have difficulties to understand terms like init.d or script meanings.....
For what i know i found pre installedon globerom the gov-tuner project zip file, then i discovered that that optimizations to the GOVERNOR, are also incorporated in another app called L speed. so i uninstalled gov tuner in this way:
1) entered into console, and entered the letter to disable gov tuner. ok,
2)then rebooted into recovery and flashed the zip for uninstaller.
DELETED! and i can say with that mod my battery life was really good almost perfect.
then i installed L speed, but still being a nice app with lots of features and explanatiions for EACH of them, i just setted overall provile to BATTERY, and cheched some other tweaks....EXCLUDING THE ONES that are described as battery wasting.
Then i asked to officiial thread if i have to reboot to apply, they said no... but it's PREFERABLE. OK I REBOOT.
by now i have worse battery life ( much worse) and i can't understand why.
I tested with console if gov tuner is still present, but NO. so there shoudn't be any conflict at all
sorry....if this 2nd question is THE BIGGEST ONE, but i really need to read someone suggestion and a simple explanation to understand if it's better l speed or gov tuner to me.
L speed seems very much powerful and can mod much more things... but is it safe? maybe there are so much options and i choosed 1 or 2 too much, and now i see bad battery life. but it's nearly impossible what is the option that causes me this.
And last important thing.... is it the same thing to implement these script or optimizations at the boot (i think gov tuner do it so) or after the boot like do L speed? ( i noticed into app a setting to choose 10 seconds after boot to apply scripts, in fact i see after each boot a notification about these applied scritps)
Hello,
sorry I can only answer question 1 since I dont use Lspeed.
Set it to 400MhZ Dude!
Doesnt harm your device, its still not laggy or anything.
Set apply on boot option and you`ll be golden.
RN3 has awesome battery life just stock. If you want more, install skynet. (was on xda, moved to google+)
There is even a guide somewhere out there for setting it to 400Mhz.
Cheers mate
Introduction:
Hi everyone and welcome to another guide. Today I will be teaching you how to get the most out of that Exynos 9820, inside that S10 of yours. We will be focusing on three main things in this guide. Debloat, Mtweaks and DVFS (The ace up our sleeves). So without further ado, lets get right to it.
Requirements:
1. A OneUI ROM, or custom ROM, with Magisk - If the ROM comes pre-debloated, even better, you can skip Step 1.
2. MTweaks - https://github.com/morogoku/MTweaks-KernelAdiutorMOD/releases - Mtweaks is going to be controlling our kernel and helping us get extra power.
3. A root explorer - I use solid explorer, its the easiest and looks the nicest but has a trial date, although any explorer is fine.
Step 1: Debloating:
Now this should come as no surprise, that having a light operating system, will obviously benefit performance. Now I'm not gonna sit here, and type all the apks, permissions etc. that you have to remove. However the three apks that are essential to better gaming performance, are GameLauncher, GameOptimizingService and Gametools. I will explain why in the next section:
1. Gamelauncher: The app in itself isn't that bad, the main problem is its control on the performance of the device. It isn't the main culprit here, but any link that the service has to the kernel needs to be stopped for the future steps.
2. GameOptimizingService: This is the main culprit and the service I am referring to. GOS has this "feature" to control the performance of the device, and whether to focus on performance or focus on battery. After extensive testing, this app does the inverse of what it is supposed to do as it tends to throttle performance, regardless of what setting you place it on and for the steps I'm going to explain later, you will know anything linked to controlling the kernel needs to be killed.
3. GameTools: Once again, not the main culprit, but as I have stated before, it has a link to the throttling service, and unfortunately has to go, along with the other three apks.
The path for the three apks:
system/app/GameOptimizer
system/app/GameOptimizingService
system/priv-app/GameHome
system/priv-app/GameTools_Dream
system/etc/permissions/privapp-permissions-com.samsung.android.game.gamehome.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gametools.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gos.xml
I know that most people love the organization skills of Game Launcher and the functionality of Game Tools, but all I ask for is a little leap of faith here, when I say they aren't good for gaming performance. Of course you can continue the guide without the removal of these apks, but I cannot guarantee the performance I promised at the start of the guide.
Step 2: Disabling DVFS
The second step on this journey is going to be the disabling the absolutely horrible thermal throttling system on any Samsung device known to man, called DVFS. It is singlehandely the main reason, why your exynos chipset cannot play games at the same framerate as a Snapdragon chipset from two years ago, and is also why AOSP tends to not throttle like OneUI does. Today we will be killing it, and restoring the CPU and GPU performance of your device.
Note: Disabling DVFS will have lots of obvious benefits which will be very noticeable, but does come with its own sets of downsides. Once killed, you have to reboot the device to re-enable DVFS as with DVFS disabled, there is nothing telling the kernel to be conservative and therefore, there will be a slight increase in drain while using apps. All you have to do to fix it, is reboot the device and DVFS re-enables itself.
Note 2: Every time you reboot, you will have to repeat this process as DVFS does re-enable itself, so keep this guide handy, or memorize the steps.
Lets get started. (I will post screenshots of me using solid explorer)
1. Open up your root file explorer, grant Magisk permissions and goto the root folder (or main system directory)
2. Once you are in the root directory, goto the folder called sys
3. Then goto the folder called devices
4. Then goto the folder called platform
5. Now search the word "mali"
6. Press on the first folder you see
7. Now look for three files, dvfs, dvfs_max_lock and dvfs_min_lock
8. Press and hold on the file dvfs and goto its properties
9. Now goto its permissions and disable all its permissions. There should be a single tick mark on any of the permissions.
10. Now save the file and do the same for dvfs_max_lock and dvfs_min_lock
Thats it. You have now disabled the thermal throttling system on your device. Now remember, by doing so, your device won't throttle until its hit the chipset thermal limit (which is a lot higher than DVFS's thermal limits), so don't run the overclock we plan on using unnecessarily (You don't need max performance to scroll through Instagram XD)
Step 3: MTweaks
What is MTweaks? Mtweaks is a kernel manager that was built by @morogoku specifically for exynos based devices. Now with this kernel manager, you now have access to your CPU and most importantly your GPU. When we killed GameLauncher, Gametools and GameOptimizationService, we removed the ability for GOS to throttle the device in advance. When we disabled DVFS, we set the kernel free of the five year old messing with the settings, when things got a bit too intense, and now we have the ability to fully utilize our kernel.
Now after extensive testing, touching the CPU frequencies tends to have the inverse effect unless your underclocking to save power, so we're not going to adjust its frequencies. The GPU is going to be the main area of improvement. Before you go-to play whatever game you want to play, if it is something light, set the minimum frequency to half of the maximum frequency. So if its something light like candy crush, set the GPU's minimum frequency to 325mhz and the GPU Power Policy to Always ON. If you plan on playing something that's going to require a lot more horsepower, like lets say, PUBG Mobile with UHD and all settings maxed out via GFX Tools (Yes I am a madman), put the GPU's minimum frequency at 702mhz and the GPU Power Policy to Always ON, and thats it, your done. You should now be able to outperform or at least match the performance figures given in your Antutu Benchmark. Keep in mind obviously the thermal restrictions, and as a rule of thumb, check Mtweaks once in a while to check your temps. The main temp I've noticed to take an increase is the battery, and keeping it below 45C is optimal while gaming. The GPU and CPU don't need to be monitored.
Disclaimer: I will not be held responsible for any nuclear explosions because you pushed your device too hard by using this guide. Please be responsible and be aware that your phone is a phone, not a gaming PC with a huge fan to cool it off
Conclusion:
I will post a screenrecording of my s10's gameplay of PUBG Mobile on UHD with all settings maxed out on GFX Tools, and screenshots of MTweaks and solid explorer. I hope this guide helped you achieve the gaming performance you desired out of your Exynos based Galaxy S10. Hit the thanks button if I helped you
Well, it seems to do the job very well. No lags for now, im playing full graphics with wqhd+ display settings (like never before, it really fly). Cons: a little more battery consumption and more heat (but no so much really). If this was an S7 it will burn your fingers for sure. So, i think this mod on S10 can't damage the phone, only the battery life can be shortened on a large-term if the use is heavy. But... is one thing on another.. i prefer playing good. Thank you for the guide.
Skulldron said:
Introduction:
Step 1: Debloating:
Now this should come as no surprise, that having a light operating system, will obviously benefit performance. Now I'm not gonna sit here, and type all the apks, permissions etc. that you have to remove. However the three apks that are essential to better gaming performance, are GameLauncher, GameOptimizingService and Gametools. I will explain why in the next section:
1. Gamelauncher: The app in itself isn't that bad, the main problem is its control on the performance of the device. It isn't the main culprit here, but any link that the service has to the kernel needs to be stopped for the future steps.
2. GameOptimizingService: This is the main culprit and the service I am referring to. GOS has this "feature" to control the performance of the device, and whether to focus on performance or focus on battery. After extensive testing, this app does the inverse of what it is supposed to do as it tends to throttle performance, regardless of what setting you place it on and for the steps I'm going to explain later, you will know anything linked to controlling the kernel needs to be killed.
3. GameTools: Once again, not the main culprit, but as I have stated before, it has a link to the throttling service, and unfortunately has to go, along with the other three apks.
The path for the three apks:
system/app/GameOptimizer
system/app/GameOptimizingService
system/priv-app/GameHome
system/priv-app/GameTools_Dream
system/etc/permissions/privapp-permissions-com.samsung.android.game.gamehome.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gametools.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gos.xml
Click to expand...
Click to collapse
If only disable the packed with some app It's same?
xaloundros said:
If only disable the packed with some app It's same?
Click to expand...
Click to collapse
While I haven't tested this myself, in theory it should work, however further testing could be required
If you are annoyed by your device switching refresh rate to 60FPS or that you are unable to record a video for more than 2 minutes say no more! According to my findings
Sony maxed out all the frequencies without any throttling during camera usage and applied kill switch at 55C.
As for any other use case scenarios, there is an aggressive throttling and forcing screen back to 60FPS, with an exception of using Xperia Stream or Endurance modes. As you may have guessed that these limitation are not to protect the device, but avoid any law suits from people who burned their hands.
Behold!
I present you thermal config mod that will make your device usable and keep your hands warm.
Of course at your own risk, I do not take any responsibility for broken devices, burned hands, radiation sickness or any other catastrophic events.
Description:
During your normal usage (not gaming or camera) the throttling will remain the same, BUT your screen won't switch back to 60FPS.
If you add your game/app to the game enhancer and select "performance profile" it will throttle way less aggressively. Max temperature is changed from 56C to 61C, screen refresh rate will only drop if the display itself will reach 45C.
In "balanced" profile the temperature limit is set to 58C, frequencies are limited to 1574Mhz (Little)+1651Mhz (Big)+2054Mhz(Prime)+545Mhz(GPU).
"Battery mode preferred" is set to 57C with the following limits: 1267Mhz+1325Mhz+1728Mhz+492Mhz.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Camera related profiles are set to 63C.
Video recording profile is set to endurance mode (66C temp limit) with a little bit of throttling to cool device down
During recording device will show warning, but won't disable camera functionality. However if the camera module itself will reach the limit temperature (untouched by me), the recording will stop. Additionally modem might be temporary switched off to cool device down.
Is this safe?
As safe as using endurance mode.
I took thermal profile for Xperia Stream dock thermal limits from endurance mode, so it is relatively safe for the device, but may not be as safe for you, if you have sensitive skin.
I strongly recommend using stick/stand when recording high quality videos for a longer periods of time.
Instructions:
You need root and magisk.
Install this module
GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
Make system partition become read-write (it is also possible without Magisk) - GitHub - HuskyDG/magic_overlayfs: Make system partition become read-write (it is also possible without Magisk)
github.com
After rebooting go to oem/etc with any root file manager, enable R/W and replace the thermal-engine.conf and change.cfg for newer versions.
Make sure to set the same permissions and backup original files.
In the end you may want to go to /data/adb/modules/magisk_overlayfs and modify mode.sh to lock partition again (mode 2), this is done to avoid some apps detecting traces of modified system with Momo app.
Additionally I recommend undervolting GPU.
Thanks to @ragu24 for pointing at the right direction.
To do so:
Install konabess and select your GPU (should be in the middle).
Backup old image.
Then go to import/export.
Export your config (backup).
Import config txt that I shared.
Save GPU freq table.
And then repack and flash image.
After rebooting check the frequency table if the UV applied correctly.
Have fun!
Changelog
0.1 initial release:
Kill switch disabled
Applied Xperia Stream profile to Game Performance and camera
0.2 version:
Slightly raised screen temperature limit (it was lower in gaming mode)
Modified general camera profile (non stock app?)
0.3 version:
Disabled screen fps drop for other game profiles (unless screen itself is hot)
Returned kill switch (previous version will not stop unless other sensors show high temp)
Raised temperature till 64C for camera and game performance profile
0.4 version:
Less aggressive throttling for best performance (Game performance and camera profiles)
Raised temp to 66C for video recording and game performance profiles (endurance mode)
For other camera related profiles I limited temp to 63C
Switched modem to endurance mode on a game performance profile, however during long video recording modem may be temporary disabled to reduce device temperature
1.0 version:
Introducing modified "battery life preferred" and "balanced" profiles for Game Enhancer (Also thermal limit in custom settings should do the trick)
"Battery life preferred" temp limit: 57C, Max frequencies: 1267Mhz(Little)+1325Mhz (Big)+1728 (Prime)+492Mhz (GPU)
"Balanced" temp limit: 59.5C, Max frequencies: 1574Mhz+1651Mhz+2054Mhz+545Mhz
1.1 version:
Reworked game enhancer profiles to have dynamic frequency adjustment instead of aggressive throttling
Restricted limit for performance profile to 61C
Restricted limit for balanced profile to 58C
Disabled modem endurance mode for performance profile, since device doesn't heat that much anymore (back to stock change.cfg)
Made sure that underclocking kicks in instantly on balanced and battery safe profiles
Minor bug fixes
Also for xperia 1 iii with A13 ?
Pandemic said:
Also for xperia 1 iii with A13 ?
Click to expand...
Click to collapse
You have different frequencies and no Xperia Stream support, but we can use profile for endurance mode.
Share your config I will take a look.
V 0.2 Update
Slightly raised screen temperature limit (it was lower in gaming mode) and modified general camera profile (non stock app?)
0.3 Update
Disabled screen fps drop for other game profiles (unless screen itself is hot)
Returned kill switch (previous version will not stop unless other sensors show high temp)
Raised temperature till 64C for camera and game performance profile (same as endurance mode)
P.S.
Seems like Sony maxed out all the frequencies without any throttling and then just shut it it off after it reaches 55C during video recording. No wonder why it overheats lol
Thank you! just installed v0.3, you actually made me root my phone AGAIN just to enjoy this. wow.
i was wondering if i should keep stock and buy a stick for endurance mode or just root for free, and i chose the free and comfortable option.
ps. i also tried seeing what will happen if i flash different region firmware (54 on 72) - it seemed to work, and i could scan barcodes for e-sim cards, but unfortunately reception wasn't working with the different region firmware. now when i am rooted, i will see if it is possible to flash different MBN files to get VOWIFI working (LET+5G works)
Orof said:
Thank you! just installed v0.3, you actually made me root my phone AGAIN just to enjoy this. wow.
i was wondering if i should keep stock and buy a stick for endurance mode or just root for free, and i chose the free and comfortable option.
ps. i also tried seeing what will happen if i flash different region firmware (54 on 72) - it seemed to work, and i could scan barcodes for e-sim cards, but unfortunately reception wasn't working with the different region firmware. now when i am rooted, i will see if it is possible to flash different MBN files to get VOWIFI working (LET+5G works)
Click to expand...
Click to collapse
Haha, I rooted just to see if it will be possible to implement this mod and pure black background in apps.
Unfortunately you can't just buy any stick and enable endurance mode, device needs to be connected to some external device via usb/hdmi. It almost seems like a way to encourage people to buy compatible accessories.
As for different regions I don't think you can enable e-sim on the device that doesn't has the module. Also if you flash Japanese firmware you will have voice recording for calls, but nfc module will break, because they use different technology.
As for enabling VOWIFI it might be possible. You newer know if the difference is in hardware or just limited by software. For example I converted my XZ premium to dual sim by flashing firmware and replacing sim tray.
You can either experiment with newsflasher or manually.
With overlayFS you can "write" to system partitions(unless it's root folder like system or oem), I think I saw something related to connectivity in /product partition.
Just use unsin tool to unpack part of firmware in open it with 7zip.
In case a failure it's nice to have a bootploop protector module, or you can boot in safe mode to disable magisk and start over. However my mod will need reinstallation too.
Suggestion - a couple of changes to the throttle behavior.
this is how phone throttles after 20 mins of CPU test with a fan on the case. as you can see - no dips, very high performance.
however, this is how the phone behaves when there is no fan attached to the phone (and the phone is without a case):
this suggest that some throttling adjustment is in order, as playing games with this amount of throttle will surely be noticeable.
for reference, this is how the phone throttles on stock profile:
if we can make the temp more consistent and less frame drops - it will be great (not needing to use a fan as well)
EDIT - Throttling behavior from stock is from the original firmware. it should be possible to extract the thermal engine from the initial catches of the Xperia 1 IV and apply them to the current software (currently the phone throttles more than it did in the past, to around 170k points)
app is CPU Throttling Test
@Orof , thank you for your tests! Frame drops are unavoidable, that's the "kill-switch". Without it temperature will keep rising and rising, CPU needs to cool down somehow.
How many threads do you use in CPU Throttling test? I don't think default is enough, as with Burnout Benchmark I was able to trigger modem overheat warning when I disabled kill-switch.
I am working on the new version based on endurance mode with throttling at 57C and kill switch at 66C( max for endurance). It may restrict modem when the temperature will be high enough (Happened during 30 minutes recording [email protected]). Gonna do couple of tests and upload it.
New version is up!
There are two files inside archive now, same logic applies with replacing and setting permissions.
Annnd still hitting the kill switch for some reason (using the new files)
I wonder why. I wish the throttling was more aggressive so that the kill switch wouldn't be met, while still gaining more performance than stock (215,000 according to gsmarena)
*EDIT -changed the threads amount from the default value (20) to 60, still the same.
Orof said:
Annnd still hitting the kill switch for some reason
View attachment 5916741
I wonder why. I wish the throttling was more aggressive so that the kill switch wouldn't be met, while still gaining more performance than stock (215,000 according to gsmarena)
*EDIT -remembered yo change the threads amount.was testing the default value (20). How many did you test?
Click to expand...
Click to collapse
I used 20 threads.
Maybe you have higher ambient temp?
Also it seems that every device is different for some reason. Some people can film for 15 minutes 4k120fps, others see the thermal warning while just taking photos.
Did you try limiting frequencies with FKM?
Doom Slayer said:
I used 20 threads.
Maybe you have higher ambient temp?
Also it seems that every device is different for some reason. Some people can film for 15 minutes 4k120fps, others see the thermal warning while just taking photos.
Did you try limiting frequencies with FKM?
Click to expand...
Click to collapse
I reckon that the higher ambient temp is the issue here, though it doesn't mean that it throttling cannot be initiated sooner or harder to avoid the kill switch, for those who live in a higher temp locations
Will try limiting via FKM. Can already confirm that via the default perf setting (without the mod), score stabilize at around 170-180k with no sudden jumps, so it is something we should be able to do with a bit more tinkering.
Thanks for all the work! I really appreciate it.
Orof said:
I reckon that the higher ambient temp is the issue here, though it doesn't mean that it throttling cannot be initiated sooner or harder to avoid the kill switch, for those who live in a higher temp locations
Will try limiting via FKM. Can already confirm that via the default perf setting (without the mod), score stabilize at around 170-180k with no sudden jumps, so it is something we should be able to do with a bit more tinkering.
Thanks for all the work! I really appreciate it.
Click to expand...
Click to collapse
With aggressive throttling it will be very similar to kill switch. It will lower frequencies until device will slightly cool down and will do it again after it will heat. On stock it just happens very soon a major performance cuts that's why it's stable on the benchmark. Same can be achieved by locking frequencies with FKM for a specific app/game.
Doom Slayer said:
With aggressive throttling it will be very similar to kill switch. It will lower frequencies until device will slightly cool down and will do it again after it will heat. On stock it just happens very soon a major performance cuts that's why it's stable on the benchmark. Same can be achieved by locking frequencies with FKM for a specific app/game.
Click to expand...
Click to collapse
Thanks for the explanation, I understand now why it behaves this way on stock
I wonder if I can fine-tune the frequencies by editing the thermal-engine.conf (and maybe the change file as well) without needing to use FKM. already tried to make some changes to version 0.3 with no meaningful success. will have to dig deeper
Cheers!
Orof said:
Thanks for the explanation, I understand now why it behaves this way on stock
I wonder if I can fine-tune the frequencies by editing the thermal-engine.conf (and maybe the change file as well) without needing to use FKM. already tried to make some changes to version 0.3 with no meaningful success. will have to dig deeper
Cheers!
Click to expand...
Click to collapse
Try the uperf mod in combination with the modified thermal config file!
It's dynamically able to adjust the frequencies on the fly - just like FKM but dynamic! Combined with the higher thermal limits it should allow for a smoother experience
ragu24 said:
Try the uperf mod in combination with the modified thermal config file!
It's dynamically able to adjust the frequencies on the fly - just like FKM but dynamic! Combined with the higher thermal limits it should allow for a smoother experience
Click to expand...
Click to collapse
Thanks for the suggestion, but when trying to install it on the Xperia using Magisk, installation failed because "Taro is not supported". will try different versions of it ans report back
Orof said:
Thanks for the explanation, I understand now why it behaves this way on stock
I wonder if I can fine-tune the frequencies by editing the thermal-engine.conf (and maybe the change file as well) without needing to use FKM. already tried to make some changes to version 0.3 with no meaningful success. will have to dig deeper
Cheers!
Click to expand...
Click to collapse
You can try, just make sure to reuse the frequencies from the config like from game save profile.
Basically we have a choice either to have a higher performance with a little bit of drops or lower performance, but more stable.
On default profiles CPU just cust performance in half when it reaches 53C. Which happens like after 1 minute of CPU Throttling Test.
Anything below that reduction will not prevent CPU from building up the heat, but will slow it down. Without external cooling best you can do is to prolong that performance drop moment or castrate your CPU and "enjoy" stability.
Drops are necessary to keep device from going above maximum temperature (when I completely disabled thermal engine it easily went above 70C) because device sucks at getting rid of heat passively.
Main motivation to create this mod was to prolong video recording time, get rid of annoying screen refresh rate switch, as it causing flickering and squeeze a bit more fps out of emulators with prolonging the moment when the CPU gets castrated.
These synthetic tests do not reflect normal usage. If any game or app behaving like that it means poor optimization with an exception of emulators. It's up to users to configure each game to find a balance between stability and better graphics/more fps.
I'am planning to eventually edit balanced and battery safe profiles inside game enhancer, but don't expect miracles.
Meanwhile if anyone wanna contribute, you may lock frequencies with FKM and run the thermal throttling test on each, to find the one which is more stable, so I can use this data in modified balanced game profile.
Orof said:
Thanks for the suggestion, but when trying to install it on the Xperia using Magisk, installation failed because "Taro is not supported". will try different versions of it ans report back
Click to expand...
Click to collapse
I use this one - one of the latest
New version is up!
Basically it eliminates the need to have FKM, as balanced and battery life profiles in game enhancer will castrate frequencies as soon as possible , which will slow down heating (what the point of having maximum performance for a minute anyways? ) and result more stability.
Frame drops may appear sooner or later, depending on your ambient temperature, if you are using my undervolting profile, phone case (all my tests run in aramid carbon fiber case) and in general it seems that it's random for each device.
Battery safe profile
Balanced profile