Hey guys,
this thread is supposed to show you exactly, how you can change the charging voltage and charging current of the Xiaomi Redmi 5 Plus (vince). This could very well also work with other phones, as I first heard of them in a Magisk module, NOT related to this phone. This is my first thread on xda and I'm not a native speaker, so please excuse mistakes
So, there are two files associated with the kernel, that control voltage and current. For most kernels for vince, these files exist (DA, Zucc, Genom, and maybe also the others... doesn't work on Kirks Kernel) at the moment. Of course I don't know if these files still exist when a new android version is brought to this phone ^^
So let's start. The two files I mentioned are located here:
Current: /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Voltage: /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/voltage_max
For Linux 3.18 Kernels:
Current: /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max (stock value: 2000000 = 2000mA)
Voltage: /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/voltage_max (stock value: 4380 = 4,38V)
The values in constant_charge_current_max are measured in mA/1000. So that means, if you want to set 2000mA, you have to type 2000000 in this file.
The values in voltage_max are in mV, so if you want to set for example 4,2V as a maximum, you would have to type 4200 in this file.
MY RECOMMENDATIONS:
To set good values on these interfaces, we have to understand them correctly. Let's start with the voltage. The charging voltage (in order to charge) always has to be higher than the voltage the battery has. The battery of this specific phone ranges from 4,3V to 3,7V (4,3V on 100%, gradually going to 3,7V when reaching 0% (not sure about the 3,7V, correct me if you can )). I wouldn't change it. The voltage needs to be 4380 mA if you want you phone to charge until it's full. Even if you don't want that, I'd take another way to stop your phone from charging any further (there are good magisk modules that do exactly that, even with more features).
Now let's speak about the charging current, the holy grail of charging haha :laugh: Basically, if you want faster charging, go with values higher than 2000mA. I'd take 2500mA max, as the battery can get very hot. If you want your phone to stay cool while charging, which causes the battery to last way longer (https://www.sciencedirect.com/science/article/abs/pii/S0378775314004352), I'd recommend finding a charging current which keeps your temperature at about 25°C, which is the optimal temperature (see the reference, it's not a long text). For me, this is 1850mA, but if you live somewhere where it's very cold or hot, this can vary significantly. In the end, this is personal preference and should depend on how long you want to keep your phone, and how important charging speed is to you.
As for all kernel or /sys values, these will be reset on every reboot, so you'll have to find a way to set in on every boot. I tried creating a init.d file, but even though I set the permissions of the init.d file etc, it failed every time. So personally, I use Custom Controls in Kernel Adiutor, but I think EXKM has something similar. Of course I can only show the way with Kernel Adiutor and FKM in the following, as I don't have EXKM.
How to set these values with Kernel Adiutor:
For this, you have to enable the Custom Controls in Kernel Adiutor settings, if you disabled it previously.
Let's start with the current:
Go in the Custom Controls menu, click on the + and then "create". For this type of value, we need a seekbar. The title is irrelevant really, I'd choose "Charging Current". As a min, choose 0, and as max, choose the exact same value you want to use (if you're still unsure, just take 2000000/2500000, depending on if you want to increase it or not). I do this, because it is very hard to get the seekbar to an exact value (for example 1850000), because the numbers are so high. So i just set the max to what I want, and just max out the seekbar.
In "Progress", you have to put in exactly this:
For 3.18 kernels:
#!/system/bin/sh
head /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max
Press test to confirm you typed it in correctly. Otherwise you also won't be able to set this control
in "Applying", put in exactly this:
#!/system/bin/sh
progress=$1
echo $progress > /sys/devices/soc/qpnp-smbcharger-18/power_supply/battery/constant_charge_current_max
Don't forget to delete the # before the second line (progress=$1), otherwise this will set nothing.
For 4.9 kernels:
#!/system/bin/sh
head /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Press test to confirm you typed it in correctly. Otherwise you also won't be able to set this control
in "Applying", put in exactly this:
#!/system/bin/sh
progress=$1
echo $progress > /sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
Don't forget to delete the # before the second line (progress=$1), otherwise this will set nothing.
That's it, you can use this control now ^^ But if you want this to set on every boot, after setting it up, you have to click on the 3 dots of this control and check "On boot".
Basically, for the voltage, I'd take 0 as minimum, and 4400 as maximum, and change the file location to the voltage (on progress and applying), and the rest is the same!
So, that's it! It's possible that someone will write a magisk module for that some day, but until then, I think this is a very easy solution. Have fun with it!
How to set these values with Franco Kernel Manager:
These screenshots are provided by @Niamotullah
{
"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"
}
Good job mate! Keep up the work!
8t really works and I get full control over charging speed now.
So i setup everything in kernel auditor and there is no save button besides in progress and applying fields, and when i press back button no custom control appears. Am i doing something wrong?
bot88 said:
So i setup everything in kernel auditor and there is no save button besides in progress and applying fields, and when i press back button no custom control appears. Am i doing something wrong?
Click to expand...
Click to collapse
Probably you didn't press "test" after typing in everything in "progress"
Doomkopf said:
Probably you didn't press "test" after typing in everything in "progress"
Click to expand...
Click to collapse
Yes i did press test but nothing shows up underneath.
I can't find files
mutlubas said:
I can't find files
Click to expand...
Click to collapse
What kernel and rom are you using?
bot88 said:
Yes i did press test but nothing shows up underneath.
Click to expand...
Click to collapse
Can you attach a screenshot? Can't help you this way ^^
Doomkopf said:
What kernel and rom are you using?
Click to expand...
Click to collapse
ı using global beta rom kirks kernel
mutlubas said:
ı using global beta rom kirks kernel
Click to expand...
Click to collapse
Then that kernel probably doesn't have those files, I'm sorry ^^ I'll add it to the thread so people know
Doomkopf said:
Then that kernel probably doesn't have those files, I'm sorry ^^ I'll add it to the thread so people know
Click to expand...
Click to collapse
Which kernel supports these files.
Can I set the charge rate with Kirks kernel kernel auditor
mutlubas said:
Which kernel supports these files.
Can I set the charge rate with Kirks kernel kernel auditor
Click to expand...
Click to collapse
Look at the OP. Zucc currently doesn't work, but it used to and the dev told me that he tries to implement it in the Linux 4.9 Kernel again.
With Genom and Dark Ages it works.
IDK about Kirks Kernel, never tried it. But you told me it doesn't work ^^ Check with your filemanager if you have those files please
Doomkopf said:
Can you attach a screenshot? Can't help you this way ^^
Click to expand...
Click to collapse
Sorry my bad, when i checked those files manually i figured the kernel "dark ages" i was using doesn't have those files, now I'm using "genom" kernel which is much better and stable. Also gives me default charging rate of 1800mah without modification of any files. After settings up this control 2500mah as maximum i tested different charging rates at different states of battery. As follows
34% = 2470mah
47% = 2240mah
69% = 1800mah
88% = 1430mah
96% = 836mah
4.2 volts in all states.
Given results are pure observation without any specific app made by just looking charging info given at lockscreen (feature provided by some custom ROMs in this case Havoc os2.1)
Thus i can't confirm if they are consistent throughout whole charging cycle.
Charger used: a third part charger rated at 5v 2.4amps.
You mileage may vary, my test also confirm that cables can also affect outcomes. Such as original one plus one cable from (1+1 first generation phone) does not go abve than 1500mah even when suitable charger is used. Only cable which works for me is a $15 cable i bought from store the other day, which is quite expensive but quality speaks for it self.
:good: :fingers-crossed: peace out
bot88 said:
Sorry my bad, when i checked those files manually i figured the kernel "dark ages" i was using doesn't have those files, now I'm using "genom" kernel which is much better and stable. Also gives me default charging rate of 1800mah without modification of any files. After settings up this control 2500mah as maximum i tested different charging rates at different states of battery. As follows
34% = 2470mah
47% = 2240mah
69% = 1800mah
88% = 1430mah
96% = 836mah
4.2 volts in all states.
Given results are pure observation without any specific app made by just looking charging info given at lockscreen (feature provided by some custom ROMs in this case Havoc os2.1)
Thus i can't confirm if they are consistent throughout whole charging cycle.
Charger used: a third part charger rated at 5v 2.4amps.
You mileage may vary, my test also confirm that cables can also affect outcomes. Such as original one plus one cable from (1+1 first generation phone) does not go abve than 1500mah even when suitable charger is used. Only cable which works for me is a $15 cable i bought from store the other day, which is quite expensive but quality speaks for it self.
:good: :fingers-crossed: peace out
Click to expand...
Click to collapse
Dark Ages doesn't have it? That's weird. I think I used lastest stable version and it worked
Yea, the problem is 4,2V I explained in my voltage recommendations why 4,2V is problematic. The voltage has to be a certain amount higher than the voltage of the battery (which I also mentioned in the OP). I'd recommend setting it to the standard, 4380(mV), so your battery charged faster when at higher percentages.
Wow, thank you very interesting information. True, I’m afraid to overclock the charge strongly so as not to squeeze the battery hard.
As you guys may have noticed, Linux 4.9 got ported to our device. It broke my setup (Kernel Adiutor said it can't get an integer value out of the file), but it still works! The symlinks got changed, so these are the new paths to the files:
/sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/constant_charge_current_max
/sys/devices/platform/soc/200f000.qcom,spmi/spmi-0/spmi0-02/200f000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smbcharger/power_supply/battery/voltage_max
Enjoy!
Is there any way to do this thing without root ?
Maybe by changing some files through twrp and adb.?
tanuj_mehta said:
Is there any way to do this thing without root ?
Maybe by changing some files through twrp and adb.?
Click to expand...
Click to collapse
I'd say no, because those values always reset after a reboot so they shouldn't stick if you set it in twrp and reboot to your system Maybe there is a way, but I don't see one :/
Thanks.. it's really helps me..
I did it using franco kernel manager
Niamotullah said:
Thanks.. it's really helps me..
I did it using franco kernel manager
Click to expand...
Click to collapse
Thanks again for providing the screenshots! They have been added to the OP
Related
So i decided to make a thread for all those of us who have a huge battery leakage... After putting Unofficial CM7.2 from alquez...
I was draining battery on my phone for about 4.5 to 5 hours to 5 % ... from 100%... so just lets get this moving ...
I
The first thing i did, was calibrating battery ofc... and i tought it will help ... but the battery didn`t last any longer.. This step is unnecessary. Okay, not unnecessary, IT'S USELESS.
[edit] Now when we know the truth, here is why it didnt work : http://forum.xda-developers.com/showthread.php?t=1445643, because it was just a myth
To make sure, you are making any change to your battery, i would reccomend you guys download, the app from user profete162.
It analyses your battery and gives you average battery drain in % per hour ...
Here is the xda link to it : http://forum.xda-developers.com/showthread.php?t=1483448
And a market link : https://market.android.com/details?id=com.WazaBe.android.BatteryDrain
I was using Battery Callibration , it`s free.
Link : https://market.android.com/details?...xLDEsImNvbS5uZW1hLmJhdHRlcnljYWxpYnJhdGlvbiJd
II
After this, I installed Juice Defender, i think its a GREAT app, and a MUST HAVE...I would recommend upgrading to Ultimate...
So next app is Juice Defender Ultimate
Link : https://market.android.com/details?...xLDEsImNvbS5sYXRlZHJvaWQuanVpY2VkZWZlbmRlciJd
III
Next thing was a little battery saving tip that I loved by user amraving ...
It can be found here : http://forum.xda-developers.com/showthread.php?t=1135301
[edit] User that i mentioned down, said that this just helps ppl in area where 3g is not availbe to save battery, so the phone would stop hunting for 3g networks... but i think when you put i to preffered it will just not search for 3g all the time, it will put it to gsm, and i guess it wont make any worse for members in 3g area with low signal... i hope i will get some feedback.
IV
If you are not having a data plan with your carrier, you can disable data acces over mobile network.
It can be done by going Menu/Settings/Wireless&Networks/Mobile Networks/Data enabled , untick ...
Or if you have a data plan with your carrier, you can use an app to control internet... With Juice Defender Ultimate you can set a lot off stuff and there is another app called LBE Privacy Guard. You will find a lot of usefull stuff in settings.
Link : https://market.android.com/details?id=com.lbe.security.lite
V
Next one was most annoying to me, its the LED in CM7.2 that turns on and flashes when u are on last 5% of battery, it kinda pissed me off and i think it also wasted my battery in critical moments for no reason.
So i got to an app called Light Flow, here you can disable all the stuff you want... I removed blinking on low battery, just left on sms and missed call... You can remove that too... So it doesn`t use LED at all...
Here is a ling to Lite version: https://market.android.com/details?...uc3VsdGluZy5hbmRyb2lkLmxpZ2h0Zmxvd2xpdGUiXQ..
There is also a paid version which i personally use.
[edit] This is what i didn't write, the best thing for your phone is not to discharge your phone totally at all. Because LithiumIon batteries are just made that way. Though I still think removing some leds will help, and if you really CAN'T charge your phone, that blinking led on <5% won't help anyway.
VI
And a last but not the least important, a little messing with cpu clocks...
You will need an app called SetCpu.
Here is link on market : https://market.android.com/details?id=com.mhuang.overclocking
It`s paid app.
So now when you have it i used advice from user playagiron. When you enter app, you set default cpu to 122 min/ 768 max, and set default governor to smartass. Then you go to profiles, and make profile for screen off, there u put smartass governor also, and clock 122 min / 245 max.
I also made third profile just in case, when temperature raises too much, to restore clock to 245 min / 600 max as it was by default, once again smartass governor.
So that would be it, i hope this stuff helps someone, if you have any further suggestions, or something is not ok here just send me a pm to change.
For me it worked, and i increased battery life to something like 16 hours moderate to high usage(including gaming wifi and so on..)...
[Update]:
Okay, i got what was sucking also battery out of my cm ... I couldnt beleive I didn't check that ....
In CM there is in Settings/Display settings/Automatic backlight, I used to keep it enabled, and also the 'Allow Light Decrease' was ticked. So, what i did is just disable all of it -
Disable Light sensor filter totally
Untick Use custom
Untick 'Allow light decrease'
when you do that you can go settings/display and set to automatic, OR simply leave it on 30% as someone suggested, i guess it's just the way you like it ...
Good luck with this one added
And a disclaimer, idk if i need it but, what the hell. (copied from somewhere around the forum )
THIS TUTORIAL IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS, SPONTANEOUS COMBUSTION, DEATH OF YOUR PET, WRATH OF GOD; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
b02 said:
i was draining battery on my phone for about 4.5 to 5 hours to 5 % ... from 100%..
Click to expand...
Click to collapse
And results ?
as i wrote up, like 16 hours or so... and im using a phone moderately... i disconected a charger in morning, 10 o'clock and used a phone, internet, wifi, and played angry birds on purpose for 2 hours ... now im at 60 percent battery... so i can say it all works ... for me at least
[edit] : now its 24 hours, battery is 5%... and i was using phone moderately to high ...
Next thing is, i got a suggesstion from a member CafeKampuchia, and I will be editing first post.
I will test this, i hope it works.. Thank you..
Thanks mate
I'm glad i helped, now the only thing that is wasting my battery remaining is games i think, that must be CM related, or kernel or drivers or w/e .... i hope next builds from alquez will fix it ...
refresh... though im glad i fixed the battery life, i didnt make it last enought ... i want MORE . anyone with some usefull suggestions to add here ?
What could u suggest , which options is best in justice defender?
or which would be the best way to use it?
szuladam said:
What could u suggest , which options is best in justice defender?
or which would be the best way to use it?
Click to expand...
Click to collapse
i use advanced, then set it as u wish, and as its best for you , depends how you use your phone i can send u my settings if u want but, its all individual ...
Hmm...
b02 said:
refresh... though im glad i fixed the battery life, i didnt make it last enought ... i want MORE . anyone with some usefull suggestions to add here ?
Click to expand...
Click to collapse
Don't overclock when running games as it runs ba||'s out while you are running them...Dim your brightness when playing games...Don't play games...
Get one of these and some anchor chain to go with it...
d33ps1x said:
Don't overclock when running games as it runs ba||'s out while you are running them...Dim your brightness when playing games...Don't play games...
Get one of these and some anchor chain to go with it...
Click to expand...
Click to collapse
If i wanted to kill someone with my phone, i would certainly get that battery... WTH its HUGE ...
i dim my brightness, it acts better now ... though... there is problem in cm for sure, since on stock it was running for more time.... i guess someone will find where is that thingy that sucks my battery
here are the proofs
i used the phone moderate, talking/texting, some wifi+internet surfing, had some bluetooth pictures sent, and after the screenshot it lasted like few hours more idk how much exactly... I think it was like 1 o'clock ... means 6 more more, so its like 35 hours...
{
"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"
}
Okay, i refreshed the thread, and added an update, which also helped a lot with saving the battery ...
I'm formatting the phone now. When the phone is ready, I'll try all the points and I will tell you my results.
DanHidalgo said:
I'm formatting the phone now. When the phone is ready, I'll try all the points and I will tell you my results.
Click to expand...
Click to collapse
long time no hear from you mate ?
I think disabling Background Data in Settings/Accounts & sync helps a bit too.
Thanks for your post
Thanks,
My mother use this phone, and she can use it more than a day now.
OnlyRinaldo said:
Thanks,
My mother use this phone, and she can use it more than a day now.
Click to expand...
Click to collapse
im glad it helped, i managed to use it more than 40 hours, though playing games will still kill it very fast
This mod fixes the cell standby values in the power profile for stock roms. this will be apparent when your cell radio is off (wifi is on, or background data is off), the cell standby will report higher than normal usage).
CM 10 is based off of the sgs2 and uses it's power profile values (at least it did last time I checked) so you don't need to flash this. most custom roms include this fix so you don't need it.
Installation:
Reboot to recovery
Make a backup of your phone (I'm not responsible for bricks)
Flash the zip file
Reboot
Files:
CWM-ModStandby.1.0.zip (based on the stock UVALEM framework res apk)
CWM-ModStandby.2.0.zip (based on the stock UVALH2 framework res apk)
CWM-ModStandby.3.0.zip (based on the stock UVALJ4 framework res apk)
if you don't want to use the cwm update zip or have a stock build other than one of the ones listed above and / or want to apply the fix yourself, you can do that bydoing the following the manual update steps:
Manual Update:
download this apktool set and extract it somewhere simple like c:\apktools.
copy your framework.res.apk from your /system/framework folder to your computer to the c:\apktools folder
rename apktool.jar.1.4.2 apktool.jar
open a command window and run the following commands
java -jar apktool.jar if framework-res.apk
java -jar apktool.jar d framework-res.apk
browse the decompiled folder structure to your res/xml folder and locate your power_profile.xml file
edit it in notepad/notepad++
locate the device/array[name=radio.on]/value node (there will be two of these)
change the value from 34, to 3.4
save
rename apktool.jar back to apktool.jar.1.4.2 and rename apktool.jar.1.4.3 to apktool.jar
back in the command window recompile the framework.res.apk by issuing the command:
java -jar apktool.jar b framework-res (this will likely display a lot of warnings about "no default translation yatta, yatta" which is fine)
this will re-compile your edited power_profile.xml file and place it in your c:\apktools\framework-res\dist folder (assuming you put things in this default folder)
open this file with winrar or 7zip (DO NOT EXTRACT IT) and pull out the compile the power_profile.xml file
open your original framework-res.apk (AGAIN, DO NOT EXTRACT) with winrar or 7zip, browse to res/xml, and drag the newly compiled power_profile.xml file (the one that you just pulled out of the newly compiled framework-res.apk. you can't use the one you just compiled as its missing all the important files that we didn't really extract) over on top of the existing power_profile.xml file inside the winrar window. this will replace the existing erred compiled power profile with the fixed one, and winrar will re-save it.
now reboot to recovery, adb shell, mount system, rename your existing framework-res.apk, copy this modified one over, then reboot. If you can't adb you can always take one of the cwm files I've posted, open it in winrar (open, don't extract it) browse to the /system/framework folder, and drag your new framework-res.apk over the top of the existing file and let winrar update the zip file. then flash that updated file on your phone (remembering to make a nandroid first just in case).
If you have another build that you'd like to include in a flashable form, send me your framework-res apk and I'll mod it and upload it up here.
almighty bob said:
First, I'm a pretty casual user (so if I've royally messed something up someone let me know, but I think I've got it all right), I came across the fix to this issue somewhere else (though I think the authors didn't document their source as coming from the intl. forum), created a fix for my phone, and came here to post the fix. I did a few searches to make sure nobody else had posted something similar when I noticed a few of the stock rom dev's have included it in their roms, so it looks like someone has also done a cwm fix for this at some point too, though nobody has one listed here in the tmo section (wish I had searched for it before making my own cwm installer).
anyway, as some of you may or may not know, the power profile for our phones has a pretty aggressive value in its settings for standby power consumption which drains the battery pretty fast when on standby. this fix sets it back down to a much lower value (similar to something the s2 uses) which results in a much better battery life.
I've been using it now for a while and noticed a pretty decent improvement.
As far as I know this'll just be for the stock tmobile roms, everybody else flash at your own risk.
Installation:
Reboot to recovery
Make a backup of your phone (I'm not responsible for bricks)
Flash the CWM-ModStandby.1.0.zip file
Reboot and enjoy some better battery life
Files:
CWM-ModStandby.1.0.zip
Click to expand...
Click to collapse
Thanks, just flashed. Let's hope this gets me through a day without charging!
almighty bob said:
First, I'm a pretty casual user (so if I've royally messed something up someone let me know, but I think I've got it all right), I came across the fix to this issue somewhere else (though I think the authors didn't document their source as coming from the intl. forum), created a fix for my phone, and came here to post the fix. I did a few searches to make sure nobody else had posted something similar when I noticed a few of the stock rom dev's have included it in their roms, so it looks like someone has also done a cwm fix for this at some point too, though nobody has one listed here in the tmo section (wish I had searched for it before making my own cwm installer).
anyway, as some of you may or may not know, the power profile for our phones has a pretty aggressive value in its settings for standby power consumption which drains the battery pretty fast when on standby. this fix sets it back down to a much lower value (similar to something the s2 uses) which results in a much better battery life.
I've been using it now for a while and noticed a pretty decent improvement.
As far as I know this'll just be for the stock tmobile roms, everybody else flash at your own risk.
Installation:
Reboot to recovery
Make a backup of your phone (I'm not responsible for bricks)
Flash the CWM-ModStandby.1.0.zip file
Reboot and enjoy some better battery life
Files:
CWM-ModStandby.1.0.zip
Click to expand...
Click to collapse
This DOES NOT improve battery life at all. This only changed the value for call standby calculation from 34 to 3.4 thus giving a more accurate reading of the cell standby usage.
Sent from my SGH-T999 using xda premium
I can confirm that this does not work on CM10
uoY_redruM said:
This DOES NOT improve battery life at all. This only changed the value for call standby calculation from 34 to 3.4 thus giving a more accurate reading of the cell standby usage.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
that's not completely true. if your drain rate is computed by cell standby, and cell standby reported way more power than it actually used, then your phone's going to show power loss at a greater rate than it actually is and you're going to end up charging it before you have to. Cell standby was the #1 draw on my phone every day until this was applied, now its way down on the list, so its had a pretty significant impact on the calculation of the draw on the battery stats.
this just puts the consumption settings where it should have been to begin with but the effect is that the phone appears to drain power slower (the way it should have, and actually did from the beginning but was falsely reporting with the original power settings).
solrac.dc said:
I can confirm that this does not work on CM10
Click to expand...
Click to collapse
Steve's already fixed this in CM10--has it set at 2.7 which I think was the settings used by the s2, which I don't think are exactly accurate given that the phone probably has a different power draw, but shouldn't make as much difference as 34->3.4 mA.
Does the tmobile variant really have the stand by power drain issue? I am running stock rooted debloated and see a sample below. This is with wifi always on, background data sync on, 3 emails and 4 widgets and spotty cell reception. I would like to flash this if there is really a standby issue, but doesn't seem like it.
{
"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"
}
Sent from my SGH-T999
yea, cell standby shouldn't be reporting that high of usage. that's what first got me wondering about this to begin with.
It should look something like this:
almighty bob said:
yea, cell standby shouldn't be reporting that high of usage. that's what first got me wondering about this to begin with.
It should look something like this:
Click to expand...
Click to collapse
My point is when the phone was on standby for 8 hours it drained only 2%. How can we check if the value is really set to 34 instead of 3.4 because in stock mode i don't really see big standby drain. I read that happened only for the international model.
Sent from my SGH-T999
Fixed mines. It's reading accurate now. It was at 17 hrs forever.
Sent from my SGH-T999 using Tapatalk 2
rakeshchn said:
My point is when the phone was on standby for 8 hours it drained only 2%. How can we check if the value is really set to 34 instead of 3.4 because in stock mode i don't really see big standby drain. I read that happened only for the international model.
Sent from my SGH-T999
Click to expand...
Click to collapse
yea but your cell standby in that screenshot there is 76%, which it shouldn't ever be. 2-5% is closer to what it should be.
you can copy your /system/framework/framework-res.apk from off your phone to your pc. open it with winrar, and browse to /res/xml/power_profile.xml and right click the file and select "view" the xml file is compiled inside the apk, but look for the "radio.on value which is set to 34 in the stock roms and will be set to 3.4 after this patch (my patch renames your old framework-res.apk to framework-res.apk.back if you want to compare the two files after the fact).
rakeshchn said:
My point is when the phone was on standby for 8 hours it drained only 2%. How can we check if the value is really set to 34 instead of 3.4 because in stock mode i don't really see big standby drain. I read that happened only for the international model.
Click to expand...
Click to collapse
Seriously, if you only lost 2% in over 8 hours, I wouldn't touch a thing on your phone.
I find it hard to believe those numbers, however.
overground said:
Seriously, if you only lost 2% in over 8 hours, I wouldn't touch a thing on your phone.
I find it hard to believe those numbers, however.
Click to expand...
Click to collapse
Best I got was 5% in 8 hours with it sitting overnight
Anyway i will just try this coz when i checked framework apk its 34 mv. Can this be flashed in TWRP recovery, or only CWM?
rakeshchn said:
Anyway i will just try this coz when i checked framework apk its 34 mv. Can this be flashed in TWRP recovery, or only CWM?
Click to expand...
Click to collapse
Either works fine.
While it's a nice gesture to release this to everyone, I strongly suggest not giving false hopes of increased battery life with this.
All this fixes is the read out for cell standby. It does not increase battery life.
Sent from my SGH-T999 using xda premium
uoY_redruM said:
While it's a nice gesture to release this to everyone, I strongly suggest not giving false hopes of increased battery life with this.
All this fixes is the read out for cell standby. It does not increase battery life.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
well after about 8 hours my phone was red-lined (I never go on wifi @ work) before the fix since the day I bought it. after the patch (if I charge according to the readout on the phone, which is what its there for IMO), I usually plug it in before I got to bed after about 14-16 hrs (hitting wifi @ home levels out the power usage counters).
so either I'm confused about the purpose of the power consumption counters, and how I should use them to base my phone charging, the phone is, or you are, because the phone is staying on (it's not cutting off suddenly when it says it's still got 30% left on charge), the counters are where they should be, and I'm not charging as frequently, so unless you can spell it out a bit clearer, I'm leaving it at that.
fact is, the power consumption of the radio standby isn't 34mA. the system that computes battery consumption (ohms law) uses that to tell you when to plug in and amp up, and if the value of one of the stats is off, then yea, you're going around thinking your phone is draining like crazy when it isn't. with this fix, you'll be closer to where it *should* be assuming the mfg got the math right for the hardware they put in here.
so unless you have some better explanation for the purpose of the power profile of individual systems, the os keeping track of the battery consumption and an order of a magnitude power loss in the radio standby calculation than that, then yea, they're getting "better battery life" IMO whether its just a matter of perception (now that the system is just calculating it correctly now) or not.
i just hate seeing standby at 27% so it made me happy.:laugh:
I'm going to put it to the real test soon by completely draining the battery and then recharging. I'll post a screen when I get done with it. I'm at 21% right now so I'll just turn everything on and kill the battery.
Sent from my Samsung Galaxy SIII
Now my stats won't reset. I unplug my phone and it still says 10 hrs on battery. Shouldn't change immediately to 1 sec?
Sent from my SGH-T999 using Tapatalk 2
were you on the battery screen when you unplugged? you have to hit the refresh button.
I expected it to be slightly more complicated than this but apparently not. I know that you can underclock with the use of applications but I thought I'd mention that it can be also be done this way too.
Note: I'm pretty sure this is modifying the Exynos but I've not had enough time to play with it yet so I'm not 100% sure.
WARNING: This modification will directly modify how the CPU works. As such I will not be held responsible for any damage this may cause. YOU HAVE BEEN WARNED.
Tested on
Samsung Galaxy S 4 i9500 (most likely will not work on the i9505)
Omega v4.0 ROM
Perseus Kernel
Requirements
I9500
Root Access
ADB command knowledge or a Root File Editor.
How to set the max number of active cores
1) Locate the file
Code:
/sys/power/cpucore_max_num_limit
2) Change it from 4 to whatever (you cannot set this to 0)
How to set the minimum number of active cores
1) Locate the file
Code:
/sys/power/cpucore_min_num_limit
2) Change it from 0 to whatever (you cannot set this to 4)
How to check it's working
1) Locate the file
Code:
/sys/devices/system/cpu/offline
This file should tell you how many cores are disabled (e.g, If you limit the active cores to 2, the 'offline' file will read "2-3".
2) You can double check with the
Code:
/sys/devices/system/cpu/online
file which will tell you have many cores are active.
How to underclock
[Pretty unnecessary as you can use various applications to do this bit for you]
1) Locate the file
Code:
/sys/power/cpufreq_max_limit
2) Change it to whatever you want (as long as it's a valid frequency)
You can also lock the device to 1.6GHz by editing the
Code:
/sys/power/cpufreq_min_limit
file
The Min and Max frequencies can also be changed by editing the files in
Code:
/sys/devices/system/cpu/cpufreq/ikcs-cpufreq
Things to Remember
1) These changes are not permanent. They will revert back to their defaults on boot.
2) Limiting the Exynos to 1 core causes the device to get rather unstable and can cause reboots.
3) I haven't tested this fully; any damage this may do I will not be held responsible for. Anything you do here you do so at your own risk.
Quadrant Scores
Device running on all 4 cores
{
"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"
}
Device running on 3 cores
Device running on 2 cores
Device running on 1 core
Device running on 1 core with CPU clocked at 600MHz (why not? )
Ok, but... Why?
Good question. For me, this mod is completely unnecessary. I'm planning on making an application for this in the near future if anyone's interested.
Interestingly, there's very little difference between 2 cores and 4 in general usage. This may extend your battery life somewhat and perhaps cool the device down for those experiencing overheating but apart from that it's fairly useless.
Enjoy!
You could easily echo the commands in init.d scripts. Set sleep first to allow device to boot smoothly
Sent from my GT-I9500 using xda premium
An application would be useful, very useful. If you could release an app, I'd be really grateful.
Sent from my GT-I9500 using Tapatalk 4 Beta
Nasty_z said:
An application would be useful, very useful. If you could release an app, I'd be really grateful.
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and knock one up quickly later on.
For the battery conscious among you I've been running my phone on 1 core all day by accident, I must have forgot to change it back, and it seems to have been both stable and pretty efficent, battery wise. I'll do a proper test when I next fully charge it.
Sent from my GT-I9500 using xda app-developers app
mate, the oc/uc can be easily done via either sytem tuner or nstool or any other cpu tools right?
bala_gamer said:
mate, the oc/uc can be easily done via either sytem tuner or nstool or any other cpu tools right?
Click to expand...
Click to collapse
Yup, I use CPU Master Free. Don't think anyone's made an oc capable kernel yet but you can just use applications to lower the cpu speed
Sent from my GT-I9500 using xda app-developers app
Meltus said:
Yup, I use CPU Master Free. Don't think anyone's made an oc capable kernel yet but you can just use applications to lower the cpu speed
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
did you note something odd? played with few of those values now my cpu always hangs arooung 1.6ghz regardless of cpu usage ignoring low cpu clk
edit: changed the minfreq again after a reboot, its back to normal
If i'm correct these changes only apply to the A15 cores not A7?
Meltus said:
I expected it to be slightly more complicated than this but apparently not. I know that you can underclock with the use of applications but I thought I'd mention that it can be also be done this way too.
Note: I'm pretty sure this is modifying the Exynos but I've not had enough time to play with it yet so I'm not 100% sure.
WARNING: This modification will directly modify how the CPU works. As such I will not be held responsible for any damage this may cause. YOU HAVE BEEN WARNED.
Tested on
Samsung Galaxy S 4 i9500 (most likely will not work on the i9505)
Omega v4.0 ROM
Perseus Kernel
Requirements
I9500
Root Access
ADB command knowledge or a Root File Editor.
How to set the max number of active cores
1) Locate the file
Code:
/sys/power/cpucore_max_num_limit
2) Change it from 4 to whatever (you cannot set this to 0)
How to set the minimum number of active cores
1) Locate the file
Code:
/sys/power/cpucore_min_num_limit
2) Change it from 0 to whatever (you cannot set this to 4)
How to check it's working
1) Locate the file
Code:
/sys/devices/system/cpu/offline
This file should tell you how many cores are disabled (e.g, If you limit the active cores to 2, the 'offline' file will read "2-3".
2) You can double check with the
Code:
/sys/devices/system/cpu/online
file which will tell you have many cores are active.
How to underclock
[Pretty unnecessary as you can use various applications to do this bit for you]
1) Locate the file
Code:
/sys/power/cpufreq_max_limit
2) Change it to whatever you want (as long as it's a valid frequency)
You can also lock the device to 1.6GHz by editing the
Code:
/sys/power/cpufreq_min_limit
file
The Min and Max frequencies can also be changed by editing the files in
Code:
/sys/devices/system/cpu/cpufreq/ikcs-cpufreq
Things to Remember
1) These changes are not permanent. They will revert back to their defaults on boot.
2) Limiting the Exynos to 1 core causes the device to get rather unstable and can cause reboots.
3) I haven't tested this fully; any damage this may do I will not be held responsible for. Anything you do here you do so at your own risk.
Enjoy!
Click to expand...
Click to collapse
Can I use this method to turn off some core on the stock kernel from SS? Im not using the Perseus kernel. Does this method working only on Perseus kernel or any kernel?
Thanks for the excellent work:thumbup::beer:
Spoiler
Phone: SGS2
Inviato da: Tapatalk 2
Rom: NeatROM 4.7 LITE XWLSS
Kernel: Apolo 4.6 v0 ←testing-
Modem: XXMS2
Battery: Stock 1650mAh
SD Ext. : 32Gb class 10
Inviato dal mio supermuletto :tank:
Wait for the APP of urs ... @Meltus sir
palash_6670 said:
Wait for the APP of urs ... @Meltus sir
Click to expand...
Click to collapse
Me too
Sent from my GT-I9500 using xda premium
palash_6670 said:
Wait for the APP of urs ... @Meltus sir
Click to expand...
Click to collapse
Zahid Ali said:
Me too
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Currently waiting to be sent an invoice to get my S4 repaired (the LCD screen cracked, possibly due to overheating as I never dropped it).
I could build you a quick app if you want but it won't have been tested.
It's fine, I can volunteer to test the app.
Meltus said:
Currently waiting to be sent an invoice to get my S4 repaired (the LCD screen cracked, possibly due to overheating as I never dropped it).
I could build you a quick app if you want but it won't have been tested.
Click to expand...
Click to collapse
Yeah sure why not
Sent from my GT-I9500 using xda premium
Meltus said:
……
Note: I'm pretty sure this is modifying the Exynos but I've not had enough time to play with it yet so I'm not 100% sure.
WARNING: This modification will directly modify how the CPU works. As such I will not be held responsible for any damage this may cause. YOU HAVE BEEN WARNED.
Tested on
Samsung Galaxy S 4 i9500 (most likely will not work on the i9505)
Omega v4.0 ROM
Perseus Kernel
……
Click to expand...
Click to collapse
The stock kernel can work fine with this way, in deep.
Good Job.
Ok, here's an app to do it for you.
Exynos Core Control
Should allow you to set the minimum and maximum amount of cores in use.
Requirements
i9500
Root Access and Busybox
Completely untested - Use at your own risk!
This is directly modifying how the CPU works. I will not be held responsible for any damage done to your device.
YOU HAVE BEEN WARNED
Now been using for almost four hours with max 2 and minimum 0 cores active. Used apps like camera etc, faced no issues so far.
Sent from my GT-I9500 using Tapatalk 4 Beta
There is no point in trying to turn the cores off by force, they are powered off by CPU idle C2 state. Same reason why the phone doesn't have usual hot-plugging anymore. All you're doing is limiting performance and probably even worsening battery life by not having the load spread out over many cores at low frequency.
Also I think this thread belongs in some other forum.
AndreiLux said:
There is no point in trying to turn the cores off by force, they are powered off by CPU idle C2 state. Same reason why the phone doesn't have usual hot-plugging anymore. All you're doing is limiting performance and probably even worsening battery life by not having the load spread out over many cores at low frequency.
Also I think this thread belongs in some other forum.
Click to expand...
Click to collapse
Not sure about battery life savings, didn't test it fully.
Running on 2 cores doesn't seem to impact much on performance in games but it does drastically reduce the overheating problem so I guess this could be considered a 'quick fix' until (or even if) Samsung sorts it out. I even said in the original post that this mod is pretty unnecessary but I thought I may as well post that it's possible to do.
Don't see why it doesn't belong in this forum either as it's a mod that no one's done before (as far as I'm aware) making it "Original". I guess it'd be at home in both Original and non-Original Development but the criteria for each aren't exactly clear.
I'm sure a mod will move the thread if they deem it to be misplaced.
ALL THANKS AND CREDITS GO TO THE ONE AND ONLY KTOONSEZ FOR HIS 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-SGS6E 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 find 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 S6 & S6 EDGE 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 {G92X} users
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
**********G92X**********
KT-SGS6 kernel features
•Must have a S6 model G920F and G920I and G920S and G920T and G920W8 and G925F and G925I and G925S and G925T and G925W8
•Samsung open source
•Optimized kernel configuration
•unsecure root adb
•Voltage interface
•Over Clocking
•Under Clocking
•KTweaker app for kernel control
•KTweaker Widgets
•KTmonitor app to watch your cpu cores current speed
Click to expand...
Click to collapse
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/Yo6i7SqAQS8zsAmg
Main kernel thread: http://forum.xda-developers.com/tmo...lopment/kernel-kt-sgs6e-ocv-ktweaker-t3099758
{
"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 Ktoonsez. As a proud member of Team Kernelizers, I am offering a variety of profiles specifically for S6 and S6 EDGE users with their personal needs in mind as it's pretty clear not everyone favors the same governor, scheduler, etc.. Any suggestions are always welcome. All future profiles will be added here for sharing and discussion. 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 role 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 per project. Make your selections based on your usage needs 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.
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!
IMPORTANT: Be sure to ALWAYS load your stock voltage table on BOTH CPU clusters IMMEDIATELY after applying a profile as most of these are based on an ASV10 CPU and may result in reboots!!!
1) Apply the profile
2) Quickly go to the CPU voltage for cluster 0 and click "more" and load default voltages, then click apply.
3) NOW go to the CPU voltage for cluster 1 and click "more" and load default voltages, then click apply.
4) Done!
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.
Coming soon....
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.
coming soon...
Dead By April
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 with it's heavy underclocking as well as it's higher thresholds and online blocks to prevent other cores from coming online too soon. Although It focuses very little on performance it manages to maintain a fairly smooth interface for your average daily use.
https://copy.com/oFLHg4ZG2MyvRzrq
Balanced
Balanced Bull v1
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/SKdHYHskn1NgLitp
ECLIPSE
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.
coming soon
Ktoonsified v1
These settings are my settings, This is a performance oriented option in which also offers a great deal of battery life. YOU WILL NEED TO LOAD YOUR STOCK VOLTAGE TABLE THOUGH since there are 16 different bins of CPUs!!!
Click to expand...
Click to collapse
https://copy.com/COP9WtEfLzTudZ2F
Ktoonsified {MOD}
This mod is intended to work as an alternative to the original Ktoonsified profile. It's specifically for the users experiencing issues such as screen wake and incoming call delays and media stutters on Ktoonsified v1 . Use this profile to repair most if not all of these issues.
NOTE: The adjustments text file will show you the few changes I've made from the original Ktoonsified profile.
https://copy.com/2bcvnievx8suWohD
SmoothManic v1
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/mgoNzpgrYn7TkLZO
Undisputed
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.
coming soon
Performance
Feed The Machine
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.
coming soon
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
coming soon
KTGaming v1
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/VwSaksMPwJGCfCux
SmoothGaming v1
This profile is based on SmoothManiac v1 but with performance enhancenents to provide a much smoother gaming experience while hotplugging is active. Some of 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.
NOTE: The adjustments file will show you the changes I've made to SmoothManiac v1.
https://copy.com/zI4c1TovjavAQBtI
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.
coming soon
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!
Ktoonservativeq governor adjustments explained HERE
Reserved
Reserved..
just in case
Are the Same
LuigiBull23 said:
**********T-MOBILE**********
Downloads
Touchwiz Lollipop 5.0 VERSIONS:
https://copy.com/NGddRACV6Nm1xulA
Main kernel thread: http://forum.xda-developers.com/tmo...lopment/kernel-kt-sgs6e-ocv-ktweaker-t3099758
Click to expand...
Click to collapse
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
fabioplata said:
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
Click to expand...
Click to collapse
Yes they are the same, therefore use the same kernel. Not sure about the firmware but you're willing to try. However, as I'm sure you know I take no responsibility of the end result.
fabioplata said:
Hello the G925W8 and G925T its the same phone? use the same Kernel, Can I flash my G925T with sotck G925W8 frimware with Odin? maybe this frimware ask about the unlock code..
Click to expand...
Click to collapse
+1. Let us know if it works especially the sim unlock. Thanks
what worst?
LuigiBull23 said:
Yes they are the same, therefore use the same kernel. Not sure about the firmware but you're willing to try. However, as I'm sure you know I take no responsibility of the end result.
Click to expand...
Click to collapse
What its the worst?? Maybe error in the Odin and need flash with the stock firmware or maybe I can damage the phone?
fabioplata said:
What its the worst?? Maybe error in the Odin and need flash with the stock firmware or maybe I can damage the phone?
Click to expand...
Click to collapse
The worst I'd say is probably a soft brick since the devices are nearly identical but I still can't guarantee a positive result for you. It's a decision you're gonna have to make among yourself.
dont work
LuigiBull23 said:
The worst I'd say is probably a soft brick since the devices are nearly identical but I still can't guarantee a positive result for you. It's a decision you're gonna have to make among yourself.
Click to expand...
Click to collapse
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
fabioplata said:
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
Click to expand...
Click to collapse
Attempt to boot into recovery and wipe your data.
fabioplata said:
Dont work, in Odin don't work, fail in Odin and now I have my phone in downloaded mode, stuck in this mode, I hope when de battery dies the phone start normally.
Click to expand...
Click to collapse
just press power+volume down and it will restart
thanks
batillojr said:
just press power+volume down and it will restart
Click to expand...
Click to collapse
Ok, thanks.. Works for me..
The phone start normally but with Sim lock :crying:
fabioplata said:
Ok, thanks.. Works for me..
The phone start normally but with Sim lock :crying:
Click to expand...
Click to collapse
i know, i received the unlock code but won't work , i tried different roms but always says unlock unsuccessful , s***t ! I'm giving up , i'm just going to sell it on craigslist
I can't
batillojr said:
i know, i received the unlock code but won't work , i tried different roms but always says unlock unsuccessful , s***t ! I'm giving up , i'm just going to sell it on craigslist
Click to expand...
Click to collapse
Oh no.. I can't do that.. I'm in Colombia, I can't sell the phone buecouse don't work with local company's.. ..
I hope a solution.
fabioplata said:
Oh no.. I can't do that.. I'm in Colombia, I can't sell the phone buecouse don't work with local company's.. ..
I hope a solution.
Click to expand...
Click to collapse
Ya se, estamos en una situacion muy dificil , ojala que exista una solucion pronto.. por mientras seguire usando mi nexus6
Very awesome
Good thread dude, loaded some of these on to my phone
I've been facing non responsive screen with my OnePlus 5T. The screen touch stops responding and only volume keys and power button are responsive.
Sometimes a reboot fixes the trouble but other times I have to dirty flash the stock Oxygen OS 10.0.0 zip file in TWRP recovery using OTG and mouse, to bring back the touch function to normal.
What should I do to permanently solve this trouble?
This has been a frequent problem as posted by many users here.
https://forum.xda-developers.com/oneplus-5t/help/touch-screen-5t-randomly-stops-t3888017
Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue
BlackRazor97 said:
Well, this problem is 100% a hardware one and it is caused by the fluid of the screen digitizer. One possible cause (apart from manufacturing flaw) is the prolonged heat that is encapsulated inside the phone. That's why most people with thick protective cases and protective plastic screen film had the issue appear as soon as 4 months of usage.
You can easily prove my theory: the next time it happens again leave the phone in the fridge (not freezer) for around 10 minutes, without restarting or doing anything to it. Then see by yourself if your touchscreen has come back to normal.
The most permanent solution is to replace the AMOLED screen and use a case that is as thin as possible. Other people had success by flashing a different custom kernel (probably one that lowered the Snapdragon's power consumption) but even then some reported that it reappeared after a few months. But I think that the screen's digitzer fluid has been permanently damaged by the heat over the years of use.
So to sum up:
1. Change screen for a new one
2. Use the thinnest possible case for the phone
Click to expand...
Click to collapse
Thanks for replying @BlackRazor97. Few minutes ago, I faced this trouble again.
My screen froze and I rebooted once. The screen wasn't responding. I gave a second reboot. It started functioning again. While it was booting, I came here and went through your post. I just went through your post. Getting the screen replaced is probably going to be an expensive affair. I would rather buy a new phone but still want to continue with this one without getting any hardware replaced.
I'll surely try the fridge trick the next time it happens.
BlackRazor97 said:
3. (my recommendation) Flash a slightly underclocked/undervolted kernel alongside a stock-android based custom ROM
The third step is just a precaution to prevent it from happening again.
Hope I helped to clarify the issue
Click to expand...
Click to collapse
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.
archz2 said:
I have never done underclocking/undervolting before. Wouldn't it make the phone slow? Can you please suggest any reliable slightly underclocked/undervolted kernel for stock oxygen os 10.0.0 as that's the one I'm currently on. Flashing a new ROM, restoring my apps will take a long time.
Click to expand...
Click to collapse
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.
BlackRazor97 said:
I have only used FrancoKernel myself but since it's not available for Android 10, I recommend you to flash blu_spark r209 stable kernel for Android 10. It should work fine for stock Android 10 OOS.
https://forum.xda-developers.com/oneplus-5/oneplus-5--5t-cross-device-development/kernel-t3651933
And then by using the FKM (Franko Kernel Manager) under "battery tips" you can underclock the CPU. You don't need to underclock it too much; set it to 2Ghz (instead of 2.45Ghz) for the big cluster and 1.2Ghz for the little cluster. You will see no big difference in performance and your battery life will improve too !
Always do a backup of your stock kernel, just in case something happens.
Please let me know if it helped resolve your issue.
Click to expand...
Click to collapse
I'm quite frustrated now. I'll try flashing the blu spark and do settings with Franco Kernel Manager.
Anyway, my experience with the refrigerator trick today.
First time it worked. The other time when screen issue came up, I rebooted my phone twice, hoping to solve the problem, but it didn't happen. Then I put it in the fridge. After ten minutes, I took it out the screen wasn't responding. I rebooted it. The screen started working.
Sent from my ONEPLUS A5010 using Tapatalk
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
{
"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"
}
Sent from my ONEPLUS A5010 using Tapatalk
archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?View attachment 5128013
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.
BlackRazor97 said:
Yes exactly. Let the minimums as it is and lower the maximum frequencies. FKM received a big overhaul update in version 4.0, which apparently I haven't used. The menus are different but the functionality must be the same. Also don't forget to enable blu_spark blu_active governor.
Let me know if the fix is a permanent solution for you.
Click to expand...
Click to collapse
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?
archz2 said:
@BlackRazor97
There's no battery tips tab.
I found these settings under the CPU tab of Franco Kernel Manager. Please see the screenshot attached. I should input the values suggested by you in maximum CPU frequencies options and let the minimum cpu frequencies remain with the default values and turn the CPU governor on.
Right?
Click to expand...
Click to collapse
Actually there is a battery tips tab.
And if you are interested, you can check the Lazy kernel
They say it's good.
archz2 said:
Okay. Thanks. I've done it. So far so good. I have set frequencies to 1248MHz, 2112MHz. These I selected from the options pop-up. There's no way to type frequencies manually. One small query. When I do any changes in franco kernel, I don't have to reboot to apply those changes. Or should I ?
Click to expand...
Click to collapse
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.
BlackRazor97 said:
Nice! Yes, I think you don't need to reboot for the settings to apply. You can check with another app like CPUZ to check if clocks go above 2112MHz. But I think you should be fine.
As for the Lazy Kernel, I don't know if it's compatible with stock Android 10 OOS. But here we don't go for the performance but we target stability and low thermals to resolve the screen issue.
Click to expand...
Click to collapse
Yah there is lazy kernel for stock OOS .
Those who flashed it has high recommendations and showed low ram usage .
Before flashing lazy kernel it was 700 mb free ram usage .
After flashing lazy kernel , attached screenshot.
Rom- derpfest
I haven't flashed it yet , I will when I get time
...........
@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.
archz2 said:
@BlackRazor97
Okay. Almost a week went by. I faced non-responsive screens in last 3-4 days but the issue got resolved by tapping mindlessly on the screen when it was locked and frequent screen unlocks. Yesterday came the issue where I rebooted the phone multiple times to make the screen respond. Today the issue also came, half an hour ago and frequent reboots didn't solve the issue. I rebooted in recovery and wiped the cache and dalvic. Then I started my phone. It responded fine. I went to Franco Kernel Manager. To my surprise, the frequencies were switched back to 2361 MHz for Big Cluster and 1824 or 1900 MHz (can't remember which one) for the Little Cluster. Now I've changed them back to 2112 MHz and 1248 MHz
How did these frequencies got back to higher number without me every touching the Kernel Manager? I didn't install any app, nothing in these days.
Click to expand...
Click to collapse
Did you set it to set on boot my friend?
When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
View attachment 5132257
archz2 said:
When I enable the CPU governor blu_active, I get the notification "set on boot:true", that's it. I didn't toggle any other setting. I just restarted, the frequencies are back to 2361 MHz. Is there some other place where I should set on boot ?
Click to expand...
Click to collapse
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me
This
rohithksaj said:
Do one thing this time.
Under clock both your CPU AND GPU.
Under battery life tips, check under clock both.
And click on the settings icon just near to it and set it on boot.
Check this for some days and tell me
Click to expand...
Click to collapse
Thanks. I've done it. I'll keep you posted.
The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.
archz2 said:
The situation became worse after underclocking. Had to reboot twice to get the screen working. I went back to the old settings.
Click to expand...
Click to collapse
DO NOT use the automatic underclock button. This also lowers the voltage to the point it becomes unstable and we don't want this to happen. Use the typical 2112 MHz and 1248 MHz (big and little cluster accordingly).
Unfortunately, it seems that the "set on boot:true" flag is bugged. So every time you shutdown your phone, you have to re-configure to the frequencies. Let me know if you have found any better solution to keep the settings.