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
Related
Hi everyone,
This is the first time owning a Samsung device, so the pegasusq governor is a new thing to me, I read about what it actually is on a thread but I wanted to ask to fellow S3 owners what are they using for great battery life - performance ratio?
I'm running Omega 6.0, slipstreamed loads of crap that is not needed (from the "safe to remove" thread) with Apex Launcher. I'm only using 2 homescreens, dark wallpaper, etc, the typical works to try and improve battery life.
Now the thing is, with SetCPU I'm running the default pegasusq governor ranging from 200mhz -1400mhz. Is the pegasusq governor the right choice here? Isn't it basically a variant of the OnDemand governor but Samsung proprietary for quadcore CPUs? I also recall reading a mention of S3's freezing or not waking up when it's set from the lowest underclocking point (200mhz), is that right? I've been using this for a few hours and no problems yet, but just wanted to know what are everyone elses experiences and what's the best configuration that has worked individually for you!
Cheers! Hope I complied with the rules, I did do a search but didn't find anything of this nature apart from a few separate questions!
I use the same governor, 100Mhz - 1704Mhz. No issues. Works great.
Siyah kernel is using pegasusq so i think it is the best governer there is. if you're on stock kernel or lowest underclocking is 200mhz but in custom kernels you can use 100mhz.
I have set my SetCPU to 100mhz - 1200mhz and undervolting all 18-steps to -50mv. I seldom reboot my phone but not encounter any freeze on boot
You should try tweaks for improving the battery life and peformance. Like supercharger, zipalling , random build.prop tweaks.... Etc xD but yeah use the samsungs "for quad core"
Thank you for the prompt replies everyone!
I remember with my Desire the whole development community was pretty much "set in stone" if you will, so it was really easy to choose a kernel etc.
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.
I use Siyah clocked 100-1704 screen on. 100-300 screen off. No issues.
Sptz said:
Is there a kernel that you recommend? Is anyone using a "Screen Off" profile without any problems? If so what's the range you have it set at? That's what I was mostly scared as I remember on my Desire the lockscreen or taking calls would lag quite a bit but obviously this is a different beast altogether!
Click to expand...
Click to collapse
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
Sptz said:
I'm also using AutoKiller Memory with Extreme Settings and some tweaks applied as well.
Click to expand...
Click to collapse
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory
bordikun said:
I set mine to 100-600 not having any issues, when reiveng notification/phone calls doesn't lag at all. Just don't use "power saving" option.
3rd party apps don't to any good to battery life it only consumes more(for me) cause it's always running in your background which consumes memory and also battery life.
stock task manager is pretty good, been use it always. Closing all apps and clearing memory
Click to expand...
Click to collapse
Nah, Autokiller isnt a task manager.
Basically, Android automatically kills empty processes (etc) at specified RAM levels. It does this anyway. But on High end RAM packed devices, these values are too low to be of any use as the phone will seldom hit that low a level of free RAM.
Autokiller simply adjusts these values to be more useful for high end devices.
Actually, you don't need autokiller to do this. You can do it in an init.d script although I've not tested this on the SGS3 as I haven't seen a need.
Here is an example I wrote for my Desire AOSP ROM:
Code:
#!/system/bin/sh
echo "8192,16384,19200,23040,25600,30720" > /sys/module/lowmemorykiller/parameters/minfree
Default SGS3 is:
Code:
8192, 10240, 12288, 14336, 16387, 25600
These are for:
Foreground App, Visible App, Secondary Server, Hidden App, Content Provider, Empty App
ALL THANKS AND CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR THIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.
Welcome!
I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on specific kernel builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS5 kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for which users can experiment with and see which versions perform as intended on each of their respective device models. As on previous Samsung devices I am also bringing back the Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S5 users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for UNIFIED KLTE(G900) BUILDS
POST #3: Reserved for the KTWEAKER SHOP
POST #4: Reserved for TEST PROFILES
If at any given time you aren't already on the kernel and Ktoonsez hasn't updated his links, there'll be no need to flash previous builds when you want to receive OTA's as ALL posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
I will NOT be held liable for anything that may occur to your device nor will Ktoonsez. So please...
***FLASH AT YOUR OWN RISK***
If you encounter any suspicious issues when updating the kernel, follow my recommended procedure for the best possible results:
1) Backup current Ktweaker settings
2) Open any root browser (make sure it's mounted as r/w) then navigate to /system/app/ and delete the Ktweaker and KTmoniter apk's
3) Navigate to your sdcard and delete the Ktweaker folder OR rename it by adding a ".bak" extension without the quotes.
4) {Optional} Clear all Superuser logs
5) Reboot Recovery
6) Flash kernel
7) Reboot
8) Copy any saved profiles back into /sdcard/Ktweaker/Profiles/
9) Restore Ktweaker settings
10) Profit?
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945
**********KLTE**********
KT-SGS5 kernel features
•Must have a S5 model G900T or G900P or G900V (Dev Edition ONLY!!!) or G900F or G900M or G900W8
•Must have a Touchwiz Rooted ROM
•Must have CWM/TWRP based recovery installed
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•KTweaker app for kernel control
•KTweaker Widgets
•Schedulers (CFQ, BFQ, VR, SIO, NOOP, DEADLINE, ROW, FIFO, FIOPS)
•GOVERNORS (ktoonservativeq, intellidemand, msm-dcvs, wheatley, userspace, smartassh3, slp, powersave, pegasuq, nightmare, interactive, dancedance, conservative, badass, asswax, adaptive, abyssplug, performance, ondemand
•exFAT for Touchwiz and AOSP
•F2FS compatible with AOSP 4.4
Click to expand...
Click to collapse
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/nnRWaceoApyWveLV
AOSP Lollipop 5.0 VERSIONS:
https://copy.com/sPBzkxDrTUsdh08m
AOSP Lollipop 5.1 VERSIONS:
https://copy.com/kA6cUoKDCZWNSrG7
Touchwiz KitKat 4.4 VERSIONS:
https://copy.com/3jfvgKqLUKUr
AOSP KitKat 4.4 VERSIONS:
https://copy.com/IVmYJgQZWmD6
{
"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"
}
Welcome to the Ktweaker Shop!
Here you will find all of the pre-configured settings provided by myself and some of our fellow users. As a proud member of Team Kernelizers, I am offering a variety of profiles specifically for S5 users with their personal needs in mind as it's pretty clear no everyone favors the same governor, scheduler, etc.. Any suggestions are always welcome. All future settings will be added here for sharing and discussing our settings as well as gaining approval on a profile to be added into the built-in Shop in Ktweaker. Keep in mind that results will always vary per device regardless on the settings being used.
All profiles have been grouped into 3 sub-categories; "Conservative", "Balanced", and "Performance", which are used to classify each profile based on their overall performance and what they are expected to deliver to your device. The 4th sub-group is where you can find some of our best "Projects" in which offers 2 or more profiles for each. Make your selections based on your usage and apply what works best for you and your phone. We're here to help eachother out and with more options comes better experiences for everyone running this kernel. Big thanks to ALL who have contributed!
So shop around.. pick and choose.. load and go!!
Installation
Download links will include the specified profile(s) as well as an "Adjustments" and "About" file. The "Adjustments" file is just a simplified view of all the changes made to a profile compared to stock settings.
1. Download the file(s) to your phone.
2. Copy ONLY the XML(s) (DO NOT copy the "Adjustments" or "About" file) to "/sdcard/KTweaker/Profiles" using a file Manager of your choice.
3. Open the Ktweaker app and click on the "Profiles" setting at the top of the slider drawer OR scroll to the bottom and select "Profiles & Scripts" then click "Restore Profile from sdcard".
4. The file you just copied should be listed there. Select the one you want to apply and confirm.
5. Make sure the "Set options on boot" setting at the top of the slider drawer shows a little green boot icon below it, indicating the settings will be applied upon reboot.
6. Profit!
Conservative
Asking Alexandria
This is a battery driven profile in which focuses on saving as much juice as possible while also maintaining stability and providing an extremely snappy feel to your phone. It is quite possibly one of the smoothest and snappiest battery saving profiles available.
Why Asking Alexandria?
It's named after yet another one of my top favorite metalcore bands and I chose this because Alexander The Great basically ruled the world at one point and "Alexandria" is the female equivalent to that name, which has become known to mean the "one who comes to save warriors".
"Asking" was an addition to the title name as an indication in the sense that we are all asking Alexandria what she can really do to our phone.
https://copy.com/X8tAZauB2Nw7DDmF
Bless The Child
Based on Ktoonservateq and aimed towards battery. This is specifically for all the battery hungry users out there wanting to conserve as much power as possible. So don't expect the BEST but rather decent performance out of this one.
https://copy.com/DnyKoDtbGzFeBhKj
Dead By April v3 (updated: 5~7~15}
This profile attempts to bring some of the best battery life possible to your device. It is similar to Bless The Child but takes things a step further . It now focuses more on snappiness but still maintains it's well known battery conservation. It manages to maintain a smooth ui for your average daily use.
https://copy.com/YbVh8fJui0Wg
Balanced
Balanced Bull v4 (updated: 5~7~15}
These settings are very special to me as they were my very first, dating back to the Galaxy S3, and is a profile designed for my own personal usage pattern. It has become notable for it's fairly smooth interface and amazing battery life. If this stacks up to your standards then I encourage you to use it!
https://copy.com/XaUC96AHpYd0
ECLIPSE v3 (updated: 5~7~15}
This is a performance oriented option where great battery life is also expected to intervene. This not only will bring an incredibly stable, smooth, and snappy feel to your device but will also benefit towards longer lasting battery so you can love and enjoy your phone the way you were meant to.
https://copy.com/YolJstsJPAFb
Ktoonsified v4 (updated: 3~25~15}
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a performance oriented option in which also offers a great deal of battery life. Haven't tried these settings yet? then what are you waiting for!! Load em up and be prepared for one of the smoothest and snappiest experiences ever!
https://copy.com/VPykcXYipZea
Ktoonsified {MOD}
This profile is intended to work as an alternative to the original Ktoonsified profile. It was modified to slightly boost performance and is specifically for the users experiencing issues on Ktoonsified such as screen wake and incoming call delays, media stutters, or 3D frame drops. Use this profile to repair most if not all your issues and expect an even faster and smoother UI.
NOTE: The adjustments text file will show you the changes I've made from the original Ktoonsified profile.
https://copy.com/JgW2M2wjkmat
SmoothManic v2 (updated: 7~16~14}
This profile was put together by none other than the BOSS himself, @ktoonsez!
The idea with this is to get the CPU really high on 2 cores when screen is touched and then bring them both back down really quick so UI is super smooth but don't kill the battery by hanging out at that high Mhz step.
Click to expand...
Click to collapse
https://copy.com/G7m7dWYh9u6j
SmoothManic {MOD}
Smoothmanic v2 was slightly modified in order to bring the profile up to speed with the most recent kernel changes. It should provide a slight boost in performance but continues to follow a similar scaling mechanism as the original.
NOTE: The adjustments file will show you the changes I've made from the original profile.
https://copy.com/1hHIF7rtw1Rcqwz4
Undisputed 3 (updated: 5~7~15}
This is a universal performance setup in which combines the essential elements of other profiles by providing equal battery life, speed, performance, and stability to bring the ultimate experience to your device.
https://copy.com/nuMTnp4wkQpW
Performance
Feed The Machine v3 (updated: 5~7~15}
The exact opposite of Bless the Child. This is a performance oriented option for all hardcore users. If battery isn't a priority for you then this is a great option.
https://copy.com/FFvQ3DRRUbu1iedM
From Ashes To New
This is a straight performance profile. It's similar to Feed The Machine and Rebirthing in the sense that it syncs the cores to the boosted frequency on touch and almost instantaneously jumps right back down to 300MHz. The difference between the profiles is that this one makes better use of all the cores. However, due to the rapid scale down I think most people will find battery life to be surprisingly good for this type of profile
https://copy.com/WQRuc72k8Faarx4j
KTGaming v2
This profile was put together by none other than the BOSS himself, @ktoonsez! This is a super performance oriented option which allows me to play any game with ZERO LAG!!!!!!!
Click to expand...
Click to collapse
https://copy.com/q7URWZu7qnzV
SmoothGaming
This profile is based on the SmoothManiac MOD but with performance enhancenents to provide a much smoother gaming experience. These enhancements include a much higher sampling interval as well as offline blocks to allow frequencies to scale and hotplug at a more reasonable pace.
https://copy.com/qeqe7fw9o0Xs0gxw
Projects
Comatose
This project was inspired by the album of the same name by my #1 favorite rock band of all time, Skillet. It consists of 3 profiles of which are also named after 3 of my favorite tracks from this album (included in the "Extras" folder) and all focus on one key element; VARIETY.
As the name suggests, "Comatose" is geared towards battery conservation. It focuses on keeping CPU low for a prolonged period but utilizes 3 of the 4 cores on touch and the 4th on demand for fluidity. Sample rates have been decreased heavily as to increase polling and allow the other cores to quickly spike towards higher frequencies for a given task then immediately drop back down as if the component had been knocked unconscious.
The second profile is "Rebirthing". This profile will counteract the affects of Comatose by heavily boosting performance as a means to bring life and energy back into this profile that remains unconscious. Rebirthing is intended for those seeking a performance-based version of Comatose but who knows... For such a power hungry profile you may just be surprised by the great battery life it also delivers.
Some of you may not favor the heavy battery conservation that "Comatose" offers or the overall power consumption of "Rebirthing" and much prefer a mashup of elements delivered between the 2 and that is the purpose of "Whispers In the Dark". This profile is directed towards finding the right balance between these 2 profiles while still acting as a it's own profile. It utilizes most of the performance aspects from "Rebirthing" Like "Comatose" it uses a fairly high up_threshold for that extra boost in battery performance. The profile also idles at the same minimum cpu as "Comatose" but ALL profiles run at stock 2457Mhz.
All profiles maintain the same concept of rapid cpu polling. So yes, cpu will be working consistently but my theory here is that more polling will allow the kernel to rapidly check CPU usage, thus allowing CPU to change more frequently according to the load, which in turn will prevent persistent pegging of even higher frequencies and instead consume various amounts of power in various scenarios depending on your usage, consuming even less when a specific task has completed and immediately dropping the load.
This also applies to screen off states but that goes back to what was explained in this post regarding high vs low sampling rates and how they can greatly increase idle times depending on your screen off max.
https://copy.com/wzq0Edm2xueOxZJd
If you'd like to contribute to the Ktweaker Shop all you need to do is post the profile you'd like to share and include a brief description of it's purpose. It will then be tested thoroughly by the community and based on feedback will be submitted here in the Shop for approval and sent out to the dev so he can add the profile to the Shop in Ktweaker!
Useful Links
Information about profiles can be found HERE
Interested in learning how to fine tune this kernel but not sure of where to start?
Please refer to this Ktweaker User Guide (thanks to @Perseus71) and you'll be tweaking in no time!
HERE is a great app by @elesbb that will allow the end user to set individual governor options for Ktoonservativeq when turning on the screen, charging, or playing media.
Click HERE for a widget that will allow you to quickly change your charging mA current (thanks to @elesbb).
Ktoonservativeq tunables explained HERE
Reserved
Mine..
Just in case
Thanks for this great work [emoji106][emoji106]
Sent from my SM-G900T using Tapatalk
Wow tnx for you
work
Sent from my SM-G900T using XDA Premium 4 mobile app
Question,
Why do you state to wipe cache and dalvic 'after' flashing and kt said 'before' ?
I have always done it before flashing a new kernel so the new settings would be applied, I thought.
Thank you for your work and this thread @LuigiBull23
T-Mobile Galaxy S5
EDIT
I just read his OP on his thread and it states the same as yours about wiping AFTER install.
Is there an explanation as far as doing it before vs after?
---------- Post added at 06:37 AM ---------- Previous post was at 06:31 AM ----------
Post #2, the shop.
Typo? These are for the s5 right? Lol
[emoji12]
T-Mobile Galaxy S5
em0ney14 said:
Question,
Why do you state to wipe cache and dalvic 'after' flashing and kt said 'before' ?
I have always done it before flashing a new kernel so the new settings would be applied, I thought.
Thank you for your work and this thread @LuigiBull23
T-Mobile Galaxy S5
EDIT
I just read his OP on his thread and it states the same as yours about wiping AFTER install.
Is there an explanation as far as doing it before vs after?
---------- Post added at 06:37 AM ---------- Previous post was at 06:31 AM ----------
Post #2, the shop.
Typo? These are for the s5 right? Lol
[emoji12]
T-Mobile Galaxy S5
Click to expand...
Click to collapse
Wiping caches before flashing should have the same result as wiping after. It's just what KT recommends. I also have never had issues wiping beforehand.
As far as the typo goes, I copied and pasted that post from my S4 Thread and haven't completed my edits yet lol.
I was just busting your ballz about the s4 > s5 typo. I figured as much. Hehe.
Anyways, thanks for the explanation on wiping cache / dalvic.
I haven't had any issue in doing it before or after either, just wanted it to be clear.
Thank you!
T-Mobile Galaxy S5
Glad to have all the S4 KTweaker Shop folks here on the S5. I feel at home again. ;]
LuigiBull23 said:
ALL THANKS AND CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR THIS AWESOME KERNEL AND GIVING ME THE OPPORTUNITY TO PROVIDE THESE BUILDS.
Welcome!
I am in no way affiliated with Ktoonsez or his work. I’m just a simple member of the XDA community who happens to be a huge supporter of this kernel and its creator. This is just my way of giving back. I am aware of some of the issues that may occur on specific kernel builds for some users as well as the difficulties faced when fine tuning the kernel and this is my response to that:
This is by no means intended to replace any of the original KT-SGS5 kernel threads. The purpose of this thread is simply to work in conjunction with them by providing a variety of builds for which users can experiment with and see which versions perform as intended on each of their respective device models. As on previous Samsung devices I am also bringing back the Ktweaker Shop filled with tons of pre-configured settings compiled by myself and others in attempt to further assist S5 users with improving their overall experiences on this device or to simply use as a baseline to work upon tweaking further. So I’ve gathered just about all of the current and previous kernel builds I had hidden within my pc as well as all the various Ktweaker settings and am sharing them with the public. I hope this makes a difference for all you guys. ENJOY!! :good:
POST #2: Reserved for UNIFIED KLTE BUILDS
POST #3: Reserved for the KTWEAKER SHOP
POST #4: Reserved for SCRIPTS & TEST PROFILES
No need for flashing previous builds to receive OTA's as all posts will be updated regularly upon future releases. So please be sure to refer back here for all builds from this point moving forward!
I will NOT be held liable for anything that may occur to your device nor will Ktoonsez. So please...
***FLASH AT YOUR OWN RISK***
If you are manually UPDATING the kernel, follow my recommended procedure for best possible results:
1) Backup current Ktweaker settings
2) Navigate to Settengs > Apps > Ktweaker
3) Clear cache and data then force stop
4) {Optional} Open any root browser, mount as r/w, then navigate to /system/app/ and delete Ktweaker apk
5) {Optional} Clear all Superuser logs
6) Reboot Recovery
7) Flash kernel
8) Wipe cache/dalvik
9) Reboot
10) Restore Ktweaker settings
11) Profit?
NOTE: If at any point Ktoonsez no longer wants this thread open it will be closed without question.
Please visit original kernel thread for change logs, extras, etc...
If you like and support his work, donate with this link:
http://forum.xda-developers.com/donatetome.php?u=4325945
Click to expand...
Click to collapse
em0ney14 said:
I was just busting your ballz about the s4 > s5 typo. I figured as much. Hehe.
Anyways, thanks for the explanation on wiping cache / dalvic.
I haven't had any issue in doing it before or after either, just wanted it to be clear.
Thank you!
T-Mobile Galaxy S5
Click to expand...
Click to collapse
dynospectrum said:
Glad to have all the S4 KTweaker Shop folks here on the S5. I feel at home again. ;]
Click to expand...
Click to collapse
:) .[URL
[/URL]p
Anyone using dead by april? Just wondering how much better battery life it gets you. I've been running it for a couple days and I'm seeing a bit worse battery than stock.
aooga said:
Anyone using dead by april? Just wondering how much better battery life it gets you. I've been running it for a couple days and I'm seeing a bit worse battery than stock.
Click to expand...
Click to collapse
Depends on how you use it. The profile is intended for conserving battery by undervolting the CPU and throttling it. If you have cpu intense apps that require phone awake all the time, the results won't be great. In that case its not a profile for your usage pattern.
Perseus71 said:
Depends on how you use it. The profile is intended for conserving battery by undervolting the CPU and throttling it. If you have cpu intense apps that require phone awake all the time, the results won't be great. In that case its not a profile for your usage pattern.
Click to expand...
Click to collapse
Thanks a lot.
Can I use mobile Odin for this. Never used mobile Odin before
Sent from my SM-T230NU using Tapatalk
slicknsxy said:
Can I use mobile Odin for this. Never used mobile Odin before
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
It's flashable in recovery.
aooga said:
It's flashable in recovery.
Click to expand...
Click to collapse
Any way to go back to factory. Without restoring?
Sent from my SM-T230NU using Tapatalk
slicknsxy said:
Any way to go back to factory. Without restoring?
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
Back up just the boot partition in twrp. Then restore it.
I think that's what you mean. Correct me I'm wrong.
Sent from my SM-G900T using Tapatalk
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
TruWhite MOD for Overload Kernel by RandomDelta
I have put together my settings for extracting the best performance with minimal effect on battery life from our Le eco Le 2. I have calibrated the display to true paper white colors and increased saturation to emulate AMOLED displays. Some of you may not like that so you can turn down the color saturation. While changing Voltage settings, please note that not all processors are built the same and yours might not be able to withstand the overclock. If for some reason there are random freezes, Just lower the voltage by 5mv after rebooting. The color profile has been extracted from Le eco vivid color mode EUI 5.9 with boosted color saturation . Not all displays are created equal so the color profile may not be perfect for you. Just adjust RGB by ±5 to get what works best for you. Word of caution, while playing games the phone can get pretty warm. If it concerns you, lower the throttle temperature and Temperature limit under thermal at the cost of some performance. Screen on time is 8 hrs at 50% brightness and 6 hrs at 100% brightness. I recommend 90% for optimum usage. Download the attached zip and adjust settings as in the pictures. Performance Is up by 20% from stock settings and battery usage is 5%less than stock settings. Performance test screenshot is also attached.
Hope you like it . Do comment on how you like it
Suggestions and Requests are welcome.
XDA DevDB Information
TruWhite MOD for Overload Kernel by RandomDelta, Device Specific for the LeEco Le 2 (x52X)
Credits
renjian- for making Overload Kernel
RandomDelta - For Custom Settings and optimizations.
If you don't have Overload Kernel, you can download your preferred version from the link given below
https://androidfilehost.com/?w=files&flid=283143
Instructions
1. Download and flash preferred version of Overload Kernel in Twrp
2. Install Kernel Adiutor and give it Root privileges
3. Download and extract image files from the zip file for corresponding Overload Kernel Version in this post.
4. Compare settings in screenshot images in zip to the settings in Kernel Adiutor and set them to values mentioned in the screen shots. Set them to be applied on Boot. Wait for a few seconds and the new settings will have applied .
Notes:
1. Distribution of TruWhite Mod files directly is not allowed. You are requested to drop a link to this page on the thread you wish to.
2. This is not a flashable zip
3. .json files will be made available on request. Using the .Json file you can import it in kernel Adiutor (donate version),set that to apply on boot and hence apply the customizations in a single click rather than having to fiddle with various settings.
Donation
If you like my work, you can donate me a cup of coffee.
UPI: [email protected]
Changelog
v1.0
1.Smoother I/O performance than stock
2.Increased CPU and GPU performance than stock
3. Fine tuned color profile for a more color accurate vibrant display leading to a more enjoyable media playback experience and Better visibility of small targets in competitive games.
4.Tuned CPU voltages to further increase performance with minimal effect on battery
5. Thermals tuned for delivering maximum performance without thermal throttling .
6. Optimized Memory manager for multi-tasking
7. LKT is not recommended
8. Optimized only for Overload Kernel v4.14
v1.1
1. Increased I/O performance
2.Changed screen color calibration to reduce eye strain
3.Now compatible with LKT
4.Optimized for Overload Kernel v4.14 and v4.15
v1.2
1. Optimized for Overload Kernel v4.19
2. Optimized battery life further.
3. LKT balanced or battery mode suggested as add on.
4.Reduced I/O lag
5. Removed Performance test screenshot
6.Also applicable to Overload Kernel v4.17, v4.18 and v4.20
v1.3
1. Optimized for Overload Kernel v4.21
2. Improved Standby time
3. Improved peak performance by upto 7%
4. Changed screen color calibration to fix oversaturated yellows
5. I/O operations are now less battery intensive
6. Improved Network Performance for faster downloads
7. Optimized thermal performance further
8. Also applicable to Overload Kernel v4.22
9. Color Profile and Thermal calibration is no longer optimised on devices running June 2019 patch or newer due to updated libs.
v1.4
1. Fixed Color Profile and Thermal profile for optimum performance.
2.Tuned Kcal to be slightly warm to reduce eye fatigue.
3. Color Calibration based on Redmi Note 7 Pro Increased Contrast (Cool) display profile.
4.Improved Standby time significantly.
5. Reduced idle battery drain
6. Increased GPU performance while gaming.
7.Tuned Cpu Voltages to prioritise performance under heavy load and battery under light load.
8. Unable to fix I/O lag. Still looking into how to solve it. Help is appreciated. Virtual Memory needs to be tweaked further.
9. Optimized for Overload Kernel v4.23
This project has been abandoned as Overload Kernel is no longer being updated
Version information
Status : Stable
Current Stable Version : v1.4
Latest Version :v1.4
Final Version :v1.4
Created 25-01-2019
Last Updated 28-07-2019
Reserved
Can this for 4.15?
How about gaming?
Its good or nah?
Restian Rony said:
Can this for 4.15?
How about gaming?
Its good or nah?
Click to expand...
Click to collapse
Every Version of kernel is different from each other and features pop up and disappear with updates. So certain customizations mentioned in this guide may not be available in a different kernel version. Also, optimum values tend to differ from kernel version to version. So yeah, it'll work in v4.15 but you might not get the best results.
It's good for gaming coz you get a 20% performance boost over stock. You can improve performance further by changing CPU and GPU governers to Performance, increasing minimum CPU and GPU speed, increasing minimum number of big cores online and increasing the temperature limits but it will adversely affect your thermals and battery life.
RandomDelta said:
Every Version of kernel is different from each other and features pop up and disappear with updates. So certain customizations mentioned in this guide may not be available in a different kernel version. Also, optimum values tend to differ from kernel version to version. So yeah, it'll work in v4.15 but you might not get the best results.
It's good for gaming coz you get a 20% performance boost over stock. You can improve performance further by changing CPU and GPU governers to Performance, increasing minimum CPU mad GPU speed, increasing minimum number of big cores online and increasing the temperature limits but it will adversely affect your thermals and battery life.
Click to expand...
Click to collapse
Wow thanks mate
Love u ?
Update
V1.1 now available.
Will release performance biased mod shortly. Hope you all like it
I can not find the core control setting screen (the one attached)
Why not share the .json profile file directly?
danyel980 said:
I can not find the core control setting screen (the one attached)
Why not share the .json profile file directly?
Click to expand...
Click to collapse
Are you on Overload kernel v4.14. Please ensure that you are. Even if I share the Json file, that setting won't be applied because that setting doesn't exist for the kernel you are on. So it's pointless. Plus to apply the Json file, you need to have the pro version of Kernel Adiutor , which most of us don't. If you want the Json file, it's linked below.
It's the v1.1 Balanced profile
RandomDelta said:
Are you on Overload kernel v4.14. Please ensure that you are. Even if I share the Json file, that setting won't be applied because that setting doesn't exist for the kernel you are on. So it's pointless. Plus to apply the Json file, you need to have the pro version of Kernel Adiutor , which most of us don't. If you want the Json file, it's linked below.
It's the v1.1 Balanced profile
Click to expand...
Click to collapse
yes, I'm overloaded 4.14 but I can not find the screen in question.
thanks for the .json file, even if you say in effect it does not make much sense unless you can apply the whole configuration. I would like to understand why I do not find the setting, however
danyel980 said:
yes, I'm overloaded 4.14 but I can not find the screen in question.
thanks for the .json file, even if you say in effect it does not make much sense unless you can apply the whole configuration. I would like to understand why I do not find the setting, however
Click to expand...
Click to collapse
Maybe there was some error during the flashing process. You should redownload the kernel And flash it again. It should solve the issue.
Custom settings for Overload Kernel v4.19 has been released
Settings for v4.20 are the same as for v4.19. So I'm not reposting.
Settings for v4.21 will be released soon.
Thanks for the great work
Waiting for v21 TIA
TruWhite MOD v1.3 for overload kernel v4.21 has been released!
I will not be releasing performance biased mod because in my opinion the battery trade off associated is not worth the tiny performance gain.
RandomDelta said:
TruWhite MOD v1.3 for overload kernel v4.21 has been released!
I will not be releasing performance biased mod because in my opinion the battery trade off associated is not worth the tiny performance gain.
Click to expand...
Click to collapse
After downloading and flashing Ol 4.21, it is showing 4.20 of 17th Feb..... What to do?
MpS005 said:
After downloading and flashing Ol 4.21, it is showing 4.20 of 17th Feb..... What to do?
Click to expand...
Click to collapse
Don't worry . You are on v4.21. Renjian forgot to update the build release key description.
RandomDelta said:
Don't worry . You are on v4.21. Renjian forgot to update the build release key description.
Click to expand...
Click to collapse
but my last option for max frequencies for big cpu is 1478mhz. There's no 1800mhz or around it
MpS005 said:
but my last option for max frequencies for big cpu is 1478mhz. There's no 1800mhz or around it
Click to expand...
Click to collapse
It's for little CPU. You might be confused. Little CPU max out at 1478mhz in v4.21. Send screenshots . I might be able to help
RandomDelta said:
It's for little CPU. You might be confused. Little CPU max out at 1478mhz in v4.21. Send screenshots . I might be able to help
Click to expand...
Click to collapse
I sorted out. It was showing wrong info. It was showing 1478mhz in big and 1843mhz in small. LOL. I force stopped app and rebooted phone. Then, it was correct.....Wait for results now:fingers-crossed:
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