Develop Bugs

[HOWTO]Undervolt to Save Battery and GN2 Results! with pictures

Hey all, this is a thread for how to undervolt your CPU and also post your Galaxy Note 2 specific results. The purpose of doing this is to save battery life by reducing the amount of power that the CPU draws while still overclocking, this helps alot! Please post your core speed and amount of mv you were able to undervolt for others to see. Shall we get started?
Prerequisites:
1. Must be rooted. http://forum.xda-developers.com/showthread.php?t=1980644 and recommended kernel= Perseus
2. Download and install System Tuner
3. Download and install Stability Test
Steps:
1. Open System Tuner and select CPU
{
"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"
}
2. Drag the slider shown in the picture to overclock or underclock CPU. In this picture we are overclocking to 1.8ghz
3. Select Voltage at the top to get to CPU voltage settings.
4. Ok, here select the buttons as they are in the picture.
a. Select the Green circled button to save current stock default settings.
b. Select the Yellow circled button 4 times exactly to reduce the millivolts by 100.
Stability Testing:
Now we really should make sure that it can handle it under load right? :silly:
1. Open Stability Test and select CPU+GPU Stability Test.
2. Select Full Details - Proceed.
3. The app will now start stressing your cores. I waited until at least 10 cpu passes before quiting the app...
Cliffnotes:
-By default, your settings will revert back after you restart your phone. You can set them to load at boot, but don't do this unless your absolutely sure that they're stable!
Open System Tuner - CPU - Menu key - Settings - Active Tweaks - Reapply CPU Settings - On Boot Completed
-Whenever i tried to lower the mv more than 100 below stock at 1.8ghz, my phone rebooted
-I am in no way responsible for anything that might happen after performing the above, even if you start your sentence with the word "but"
-here's stock settings in case you need to revert

lmike6453 said:
Hey all, this is a thread for how to undervolt your CPU and also post your Galaxy Note 2 specific results. The purpose of doing this is to save battery life by reducing the amount of power that the CPU draws while still overclocking, this helps alot! Please post your core speed and amount of mv you were able to undervolt for others to see. Shall we get started?
Prerequisites:
1. Must be rooted. http://forum.xda-developers.com/showthread.php?t=1980644 and recommended kernel= Perseus
2. Download and install System Tuner
3. Download and install Stability Test
Steps:
1. Open System Tuner and select CPU
2. Drag the slider shown in the picture to overclock or underclock CPU. In this picture we are overclocking to 1.8ghz
3. Select Voltage at the top to get to CPU voltage settings.
4. Ok, here select the buttons as they are in the picture.
a. Select the Green circled button to save current stock default settings.
b. Select the Yellow circled button 4 times exactly to reduce the millivolts by 100.
Stability Testing:
Now we really should make sure that it can handle it under load right? :silly:
1. Open Stability Test and select CPU+GPU Stability Test.
2. Select Full Details - Proceed.
3. The app will now start stressing your cores. I waited until at least 10 cpu passes before quiting the app...
Cliffnotes:
-By default, your settings will revert back after you restart your phone. You can set them to load at boot, but don't do this unless your absolutely sure that they're stable!
Open System Tuner - CPU - Menu key - Settings - Active Tweaks - Reapply CPU Settings - On Boot Completed
-Whenever i tried to lower the mv more than 100 below stock at 1.8ghz, my phone rebooted
-I am in no way responsible for anything that might happen after performing the above, even if you start your sentence with the word "but"
Click to expand...
Click to collapse
Thats my exact settings. Got great battery on it since I got my note 2

Is that the PRO version? Cause on my phone it doesn't show the voltage setting

cophyor said:
Is that the PRO version? Cause on my phone it doesn't show the voltage setting
Click to expand...
Click to collapse
Nope it's the free version. You should definitely see it if you selected CPU after opening System Tuner.

cophyor said:
Is that the PRO version? Cause on my phone it doesn't show the voltage setting
Click to expand...
Click to collapse
Flash the perseus kernel to get voltage to pop up, thats the only way I could do it.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

My results..perseus kernel.Stock rom .overclocked 17.04 undervolted -100 its very stable excellent battery life..couldnt complain for a screen this massive. Used the stability test app shown in op..no errors thru 10 cycles. Thanks op

For people that don't know, undervolting is probably the single biggest thing you can do to improve battery life on a mobile phone. Good write up!
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
---------- Post added at 12:31 AM ---------- Previous post was at 12:24 AM ----------
Can someone post stock voltages for me? Like a dummy I lowered voltages and forgot to save the stock settings. Much appreciated.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

powerwagon said:
For people that don't know, undervolting is probably the single biggest thing you can do to improve battery life on a mobile phone. Good write up!
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
---------- Post added at 12:31 AM ---------- Previous post was at 12:24 AM ----------
Can someone post stock voltages for me? Like a dummy I lowered voltages and forgot to save the stock settings. Much appreciated.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Here's stock settings
Sent from my SGH-I317M using xda app-developers app

lmike6453 said:
Here's stock settings
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Thanks man.. very much appreciated
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

I would love to see an ondemand/ interactive governor for this phone so I could use the frequency scaling test.
Easier to check for stability across all frequencies this way.
Thanks to the dev's though for being able to undervolt at all. Definitely one of the best mods for any phone, tablet or computer.

lmike6453 said:
3. Download and install Stability Test
Stability Testing:
Now we really should make sure that it can handle it under load right? :silly:
1. Open Stability Test and select CPU+GPU Stability Test.
2. Select Full Details - Proceed.
3. The app will now start stressing your cores. I waited until at least 10 cpu passes before quiting the app...
Click to expand...
Click to collapse
Thank you for the StatbilityTest app info.
I used it to test my setting after OC'ing to 1800 and undervolting by 100 on many frequencies.
I ran over 25 CPU passes and 80 GPU passes and no error at all. Satisfied!

Underclocked to 1000ghz
Undervolting -125mV from 200ghz-1000ghz (Not every chip is created equal, so your device may not be able to run my settings)
Satbility test ran for 10mins with cpu 16 passed, gpu 97 passed,No errors
:::UPDATE:::
Phone is rebooting when undervolting -125mV from 700ghz+ it goes back to normal when its undevolt -75mV below
---◆-----◇------◆------◇-----◆-----
☆★☆★☆★☆★☆★☆★☆★☆★
Device:T889 Galaxy Note 2
Rom: Xquizt N2 v6+Kitchen Aroma v6
Kernel: Perseus-alpha26.1

I was thinking the same JUST for the scaling stability test so I can find MIN stable voltages But today Note2Core 1.02 came out and that has ondemand as a govenor. Except currently you cant alter the voltage for 200 300 or 400 mhz
Sent from my Transformer Prime TF201 using xda app-developers app

powerwagon said:
For people that don't know, undervolting is probably the single biggest thing you can do to improve battery life on a mobile phone.
Click to expand...
Click to collapse
I have to strongly disagree with that statement.
In fact, based on actual testing as well as theory, the only scenario I've found where undervolting had a significant impact is when the phone was forcibly prevented from going into deep sleep while the display was turned off. For example, while listening to music.
If the phone is in deep sleep 90% of the time that the display is turned off, it would be nearly impossible to even measure the overall impact of undervolting by 100mA on all frequencies (and many of these devices can't reliably UV to that degree.)
When the display is turned on, the display will use (by far) much more power than the processor will use. When data or voice is being used, radio will also use much more power compared to the processor.
To improve battery life, attack what drains the most first: The display. Lower the brightness and use dark backgrounds (AMOLED uses 0 power to display black.) Turn off the display when it's not used. Minimize background data usage. Find and resolve issues with wakelocks.
Gary

garyd9 said:
I have to strongly disagree with that statement.
In fact, based on actual testing as well as theory, the only scenario I've found where undervolting had a significant impact is when the phone was forcibly prevented from going into deep sleep while the display was turned off. For example, while listening to music.
If the phone is in deep sleep 90% of the time that the display is turned off, it would be nearly impossible to even measure the overall impact of undervolting by 100mA on all frequencies (and many of these devices can't reliably UV to that degree.)
When the display is turned on, the display will use (by far) much more power than the processor will use. When data or voice is being used, radio will also use much more power compared to the processor.
To improve battery life, attack what drains the most first: The display. Lower the brightness and use dark backgrounds (AMOLED uses 0 power to display black.) Turn off the display when it's not used. Minimize background data usage. Find and resolve issues with wakelocks.
Gary
Click to expand...
Click to collapse
Ohhh,learn something everyday,hey do you know if UV affect the phone temperature?
---◆-----◇------◆------◇-----◆-----
☆★☆★☆★☆★☆★☆★☆★☆★
Device:T889 Galaxy Note 2
Rom: Xquizt N2 v6+Kitchen Aroma v6
Kernel: Perseus-alpha26.1

Lord_Kaizer said:
,hey do you know if UV affect the phone temperature?
Click to expand...
Click to collapse
Can potentially lower temps.. less voltage, less wattage, less heat from the cpu.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

garyd9 said:
Can potentially lower temps.. less voltage, less wattage, less heat from the cpu.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
ah ok thanks,that's pretty much the main reason i UV because i play alot of HD games that requires constant connection which causes the phone to go way about 100°F.So i just wanted to verify,Thanks again
---◆-----◇------◆------◇-----◆-----
☆★☆★☆★☆★☆★☆★☆★☆★
Device:T889 Galaxy Note 2
Rom: Xquizt N2 v6+Kitchen Aroma v6
Kernel: Perseus-alpha26.1

gary, totally agree. especially when battery usage shows that the screen takes up 60-80% of the overall usage time.
powerwagon said:
For people that don't know, undervolting is probably the single biggest thing you can do to improve battery life on a mobile phone. Good write up!
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
---------- Post added at 12:31 AM ---------- Previous post was at 12:24 AM ----------
Can someone post stock voltages for me? Like a dummy I lowered voltages and forgot to save the stock settings. Much appreciated.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
garyd9 said:
I have to strongly disagree with that statement.
In fact, based on actual testing as well as theory, the only scenario I've found where undervolting had a significant impact is when the phone was forcibly prevented from going into deep sleep while the display was turned off. For example, while listening to music.
If the phone is in deep sleep 90% of the time that the display is turned off, it would be nearly impossible to even measure the overall impact of undervolting by 100mA on all frequencies (and many of these devices can't reliably UV to that degree.)
When the display is turned on, the display will use (by far) much more power than the processor will use. When data or voice is being used, radio will also use much more power compared to the processor.
To improve battery life, attack what drains the most first: The display. Lower the brightness and use dark backgrounds (AMOLED uses 0 power to display black.) Turn off the display when it's not used. Minimize background data usage. Find and resolve issues with wakelocks.
Gary
Click to expand...
Click to collapse

garyd9 said:
I have to strongly disagree with that statement.
--snip--
Click to expand...
Click to collapse
Fair point, but those all require a change in behavior. Undervolting does not. Granted that's not what powerwagon said but if you look at it in this context then can you think of anything besides undervolting that can achieve battery increases without changes in user behavior?

jbrechtel said:
can you think of anything besides undervolting that can achieve battery increases without changes in user behavior?
Click to expand...
Click to collapse
Lower the screen brightness.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

[Q] OC problem

i've heard some people can OC their GIO to 921MHz stable, but on my gio it can't even get stable on 883Mhz. on 864MHz is somewhat stable but i still get hung or FC randomly, im super stable at 844MHz.
Why does my phone can't be OC like them other guys?

Not all devices are made exactly the same. Processors can behave differently as do the batteries and other hardware.

bogdanwp said:
Not all devices are made exactly the same. Processors can behave differently as do the batteries and other hardware.
Click to expand...
Click to collapse
is there nothing i can do? i've tried many ROMS, on some i can get to 921 for a few seconds, but still the same. will changing kernel help?

Why not stop overclocking ? Just find a very fast rom and then you can save the overclocking , hence the instability and hotness and draining battery. That way you will have longer life on your Gio.
L.E. : just change the minimum frequency to 245 and refrain from using roms that are heavy right now , like CM 10.1 , try anything based on gingerbread like Adrenaline or Enhanced 2.3.6 or DebianDroid for example , or AOSP ICS wich i find very fast.

bogdanwp said:
Why not stop overclocking ? Just find a very fast rom and then you can save the overclocking , hence the instability and hotness and draining battery. That way you will have longer life on your Gio.
L.E. : just change the minimum frequency to 245 and refrain from using roms that are heavy right now , like CM 10.1 , try anything based on gingerbread like Adrenaline or Enhanced 2.3.6 or DebianDroid for example , or AOSP ICS wich i find very fast.
Click to expand...
Click to collapse
well currently im using AOKP milestone 6 CM9 based, i use conservative governor 245-844MHz, installed adrenaline engine 4.4, and pim my rom and set my OOM and LMK to medium settings. battery is drained only when im using data or playing games obviously. actually this ROM is superb for me performance wise, its just, i feel like i can squeeze a bit more of it for playing games you know. its like i see this slight lagging and i thought if only i could use a little more CPU power, the lag will be gone

Even you can overclock a 1st gen AMD Duron to 2Ghz with liquid nitrogen, it just doesn't make sense doing it

AW: [Q] OC problem
i can oc my cpu to 960mhz but i think it makes no sense... you don't feel the extra speed in normal use only in benchmarks... my cpu is set to 480mhz because it's enough for every app i am using (facebook, whatsapp, xda, browser and so on).

[Q] DoomKernel v14 doubts

Hello guys i'm using Doomkernel v14 and i have a lot of doubts about it, first of all sorry for my english i'm latin american xD, and i love this comunity i have learn a lot of it... i mean about changin roms, kernels and etc.
ok, i have doomkernel v14 since the begining of this year but since i installed it i notice that the battery last a lot less than when i was using stock and is very annoying because i like this kernel and i m using it with True Ancestor LE 1.6 ROM that is very complete and i want to know if much peopple has this problem and if it has a solution because i dont want to change this kernel and i dont understan the undervolting thing is very confuce to me is with the same O.C app or with something in the computer?? because i saw some console windows in some posts screenshots and i didnt understan it, and other thing the cellphone heats when im playing MC4 and heroes of order & chaos and some other games.
and a few more information about my problen is that when i have the screen active it consumes about 1% of battery each 5 minites with the wi-fi off and with the wi-fi on 3 minutes i cant find help because not too much peopple has unlocket bootloaders

J0z31911 said:
Hello guys i'm using Doomkernel v14 and i have a lot of doubts about it, first of all sorry for my english i'm latin american xD, and i love this comunity i have learn a lot of it... i mean about changin roms, kernels and etc.
ok, i have doomkernel v14 since the begining of this year but since i installed it i notice that the battery last a lot less than when i was using stock and is very annoying because i like this kernel and i m using it with True Ancestor LE 1.6 ROM that is very complete and i want to know if much peopple has this problem and if it has a solution because i dont want to change this kernel and i dont understan the undervolting thing is very confuce to me is with the same O.C app or with something in the computer?? because i saw some console windows in some posts screenshots and i didnt understan it, and other thing the cellphone heats when im playing MC4 and heroes of order & chaos and some other games.
and a few more information about my problen is that when i have the screen active it consumes about 1% of battery each 5 minites with the wi-fi off and with the wi-fi on 3 minutes i cant find help because not too much peopple has unlocket bootloaders
Click to expand...
Click to collapse
did you check your current cpu governor? you will really use more battery life if the settings of your phone is OC you will get more performance but lesser battery life, can you maybe provide a screenshot of the current gpu settings and its governors?

fritzbored said:
did you check your current cpu governor? you will really use more battery life if the settings of your phone is OC you will get more performance but lesser battery life, can you maybe provide a screenshot of the current gpu settings and its governors?
Click to expand...
Click to collapse
how do i take it ? from the O.C aplication? i use setcpu the setcpu not even detect the battery stats and i tried other apps and the same they dont detect battery stats i tried antutu cpu master, no frills cpu (i didnt like it), incredi control, and setxperia

here is a screenshot
{
"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"
}

J0z31911 said:
how do i take it ? from the O.C aplication? i use setcpu the setcpu not even detect the battery stats and i tried other apps and the same they dont detect battery stats i tried antutu cpu master, no frills cpu (i didnt like it), incredi control, and setxperia
Click to expand...
Click to collapse
Try volume down + power

J0z31911 said:
here is a screenshot
Click to expand...
Click to collapse
Ok here are the list of things that you can possibly do.
1.) check how many running background application is there on your phone you can do this by going to settings>apps>running and try to close down those which are really not needed.
2.) try to remove task killers if you have them instead of saving power they ussually consume more because they kill system process and the phone restarts them in which will use up more power.
3.) try to use lesser brightness on your screen display instead of using automatic detect.
4.) try to use a battery calibration script you can find it in this thread http://forum.xda-developers.com/showthread.php?t=991276 (this is self proven by me and it worked perfect im not responsible for any issues that may cause after running the script)
5.) and lastly try to lower down data traffic and gps use they are bigger killers than wifi
By the way your CPU settings is at minimal not in OC so its a bit of mystery why this is happening to you maybe there are a lot of bloatwares on your phone try to check them

fritzbored said:
Ok here are the list of things that you can possibly do.
1.) check how many running background application is there on your phone you can do this by going to settings>apps>running and try to close down those which are really not needed.
2.) try to remove task killers if you have them instead of saving power they ussually consume more because they kill system process and the phone restarts them in which will use up more power.
3.) try to use lesser brightness on your screen display instead of using automatic detect.
4.) try to use a battery calibration script you can find it in this thread http://forum.xda-developers.com/showthread.php?t=991276 (this is self proven by me and it worked perfect im not responsible for any issues that may cause after running the script)
5.) and lastly try to lower down data traffic and gps use they are bigger killers than wifi
By the way your CPU settings is at minimal not in OC so its a bit of mystery why this is happening to you maybe there are a lot of bloatwares on your phone try to check them
Click to expand...
Click to collapse
Thanks for your answer,look i have my screen brightness almost at minimum my xperia play has true ancestor with. 58 baseband and is a r800a and the FW changed it to r800i
And what are bloatwares? Can you explain me please and that script that you used can be reverted? I guess i dont have to worry because i have a nandroid and by the way i don't have the data traffic and gps activated all the time
Sent from my R800i using xda app-developers app

fritzbored said:
Ok here are the list of things that you can possibly do.
1.) check how many running background application is there on your phone you can do this by going to settings>apps>running and try to close down those which are really not needed.
2.) try to remove task killers if you have them instead of saving power they ussually consume more because they kill system process and the phone restarts them in which will use up more power.
3.) try to use lesser brightness on your screen display instead of using automatic detect.
4.) try to use a battery calibration script you can find it in this thread http://forum.xda-developers.com/showthread.php?t=991276 (this is self proven by me and it worked perfect im not responsible for any issues that may cause after running the script)
5.) and lastly try to lower down data traffic and gps use they are bigger killers than wifi
By the way your CPU settings is at minimal not in OC so its a bit of mystery why this is happening to you maybe there are a lot of bloatwares on your phone try to check them
Click to expand...
Click to collapse
by the way what are u using in your divice?? and what model is? i will try to configure it as u to try to get better battery life

J0z31911 said:
by the way what are u using in your divice?? and what model is? i will try to configure it as u to try to get better battery life
Click to expand...
Click to collapse
I am currently using an xperia play r800i, when i say bloatware these are basically software that has been preloaded on a rom or custom rom that runs in the background, you may not generally see it running but it is there, now with the battery calibration script if you run that it will basically refresh your battery stats and provide you with an almost 100% accurate report of your battery percentage, my phone last upto a whole day with basic wifi browsing and normal operations last for atleast 6 hours with heavy game usage, i would also try to suggest an app called juice defender it (the pro one if you got the wallet to spare) it is a good app you can customize how your applications behave on normal and screen off condition it may be confusing at first to try to play around with it..hope my advice helps you in even a simple way

fritzbored said:
I am currently using an xperia play r800i, when i say bloatware these are basically software that has been preloaded on a rom or custom rom that runs in the background, you may not generally see it running but it is there, now with the battery calibration script if you run that it will basically refresh your battery stats and provide you with an almost 100% accurate report of your battery percentage, my phone last upto a whole day with basic wifi browsing and normal operations last for atleast 6 hours with heavy game usage, i would also try to suggest an app called juice defender it (the pro one if you got the wallet to spare) it is a good app you can customize how your applications behave on normal and screen off condition it may be confusing at first to try to play around with it..hope my advice helps you in even a simple way
Click to expand...
Click to collapse
i installed lupus v6 last night i did it because it is more updated than the doomkernel whish lupus are u using ? i asking because i saw your signature main is r800i but the firmware changed it to r800i xD i read that i have to calibrate the battery each time i change the rom, and i saw that u are using gin2jellybean i read that gin2jellybean drains the battery a lot but that was with doomkernel maybe with lupus the thigs change

J0z31911 said:
i installed lupus v6 last night i did it because it is more updated than the doomkernel whish lupus are u using ? i asking because i saw your signature main is r800i but the firmware changed it to r800i xD i read that i have to calibrate the battery each time i change the rom, and i saw that u are using gin2jellybean i read that gin2jellybean drains the battery a lot but that was with doomkernel maybe with lupus the thigs change
Click to expand...
Click to collapse
I am currently using the lupus v6 Gingerbread, Gin2jellybean is a smooth and fast rom, but it does have it flaws on my own opinion which you are right that it does consume a bit more battery than others, ive used lupus GB/ICS together with Gin2jellybean and it was a good experience however battery was only lasting for 6-7 hours of normal daily use without gaming.. heres a TIP. if you are planning to have your phone into a gaming machine better stick to GB and install GB Roms as well. But if your planning to have your phone with sleek and your after eyecandy in UI you can install ICS..

fritzbored said:
I am currently using the lupus v6 Gingerbread, Gin2jellybean is a smooth and fast rom, but it does have it flaws on my own opinion which you are right that it does consume a bit more battery than others, ive used lupus GB/ICS together with Gin2jellybean and it was a good experience however battery was only lasting for 6-7 hours of normal daily use without gaming.. heres a TIP. if you are planning to have your phone into a gaming machine better stick to GB and install GB Roms as well. But if your planning to have your phone with sleek and your after eyecandy in UI you can install ICS..
Click to expand...
Click to collapse
yes im more into gaming than other things but battery drain problem makes me a bit sad i would like to get one of those extended batteries but i dont think i can find one on my country xDD

and other thing how do i install that script?? there are a lot of downloads on that post is very confusing for me i dont see any instructions D:

better battery stats report
i will post my bbs report to see if some one can help me by finding whats wrong with my divice

Mi max cpu frequency stuck.

I got really annoying problem here...is anyone check this or never encounter the problem i faced...it seems i cant get the most out of my mi max when needed...when playing games and watch 1080p video, small core stuck at 1017mhz and big cores stuck at 1190mhz..ive change it several times but nothing happened...because of this i got stuttering when playing video and games....ive check the temp throttle, and dissable all of it...but the problem still persist...ive test it with miui globerom and mm rr....same problem with both rom...
how can i get small cores to min 400mhz, max 1401mhz and big cores 400mhz, max 1804mhz when i needed it...
Here some sample image when im playing games and watching 1080p video.
{
"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"
}
And also my big and small cores setting...i dont fiddle with anything on it..

As much as I see your cores do reach peek clock frequencies I also see a lot of bad configured tunables in interactive governor setup you are using especially timer rates.
Don't have much time now to explain or adjust it me by later today. & I don't know from where you got your config as it have CPU frequencies that are not supported by S65x SoC's so plenty of problems there to start with.

Zola III said:
As much as I see your cores do reach peek clock frequencies I also see a lot of bad configured tunables in interactive governor setup you are using especially timer rates.
Don't have much time now to explain or adjust it me by later today. & I don't know from where you got your config as it have CPU frequencies that are not supported by S65x SoC's so plenty of problems there to start with.
Click to expand...
Click to collapse
It reaches peak at normal usage from time to time but when playing games oland watching videos, the cores stuck at 1017mhz for small cores and 1190mhz for big cores...small cores max have 1401mhz and big got 1804mhz...so there s a difference in performance when in trottle down like that...ive ask some other users....but they also have the same config as mine...this is the stock config for globerom and ive never change it....
If you can give a screenshots of your config, i would be glad to test it if it work on my device...
Sorry the first 2 pictures doesn't show clearly...

Why dont just stay with stock settings? The little cores are configure really bad

donalberto17 said:
Why dont just stay with stock settings? The little cores are configure really bad
Click to expand...
Click to collapse
I dont know what stock setting config are...this is the setting i got when flashing the rom....so probably its the roms fault?...or maybe some mode causing this....if i flash the rom again, maybe it will be fixed...?
Can i get any example setting for me to fix it...

Put;
Above high speed delay
40000 900000:60000
Go high speed load
90
Min sample time
20000
Boost pulse durilation
40000
Hi speed freq
900000
Target loads
90 600000:95 900000:97 1100000:97
(delate other entries in target loads)
Timer slack 40000
For the big cluster do it like this:
Above high speed delay
40000 1382400:60000
Go high speed load
90
Min sample time
20000
Boost pulse durilation
40000
Hi speed freq
1382400
Target loads
90 1382400:97
Timer slack 40000
Should be much more snapper, balanced, power aware with a good performance.
Don't charge anything else & in a couple of days tell me how you feel about it.
Have to add that used Interactive is rather old & doesn't have some tunables.
Best regards.

And one more thing...is it advisable to use L speed to improve the cpu load....or might it interfere with the manual setting...

martin132014 said:
And one more thing...is it advisable to use L speed to improve the cpu load....or might it interfere with the manual setting...
Click to expand...
Click to collapse
My advice is that you don't use anything that you can not check in code what exactly it's doing. L speed shifted away from using scripts long ago so I don't recommend using it.
Edit:
You can try HEBF if you wish it still uses scripts.
http://forum.xda-developers.com/and...ebf-tweaking-battery-saver-optimizer-t3401341

Zola III said:
My advice is that you don't use anything that you can not check in code what exactly it's doing. L speed shifted away from using scripts long ago so I don't recommend using it.
Click to expand...
Click to collapse
Thanks...ive used your setting, and test it to the extent of my phone....the performance is great...but unfortunately, it still the same...the cores will gradually tuned down automatically to 1190 big and 1017 small, max value....even everything i do, it will stay in that state...and also, one of the big cores will offline for no reasons...so i just have to operate my phone with 5 cores online only for any big resources app....in the end, stuttering will appear...
Ive also checked that i cant change the governor either...it stuck at interactive....this things occur if the battery and cpu heats up to 38-40°....at 40°, all cores is lock away from any setting...ive tried to diactivate all the temperature throttle...but its the same...no effect...still lock....then if the rom is the culprit, then ive used RR rom and Miui GlobeRom...2 of a different Rom all together...still persist this problem...so im stuck to dont know what to do rather than flash unmodified stock rom and see whats happened...

martin132014 said:
Thanks...ive used your setting, and test it to the extent of my phone....the performance is great...but unfortunately, it still the same...the cores will gradually tuned down automatically to 1190 big and 1017 small, max value....even everything i do, it will stay in that state...and also, one of the big cores will offline for no reasons...so i just have to operate my phone with 5 cores online only for any big resources app....in the end, stuttering will appear...
Ive also checked that i cant change the governor either...it stuck at interactive....this things occur if the battery and cpu heats up to 38-40°....at 40°, all cores is lock away from any setting...ive tried to diactivate all the temperature throttle...but its the same...no effect...still lock....then if the rom is the culprit, then ive used RR rom and Miui GlobeRom...2 of a different Rom all together...still persist this problem...so im stuck to dont know what to do rather than flash unmodified stock rom and see whats happened...
Click to expand...
Click to collapse
First of all all monitoring apps aren't real-time secondly they some times have the problem with displaying correct informations for 2,3,4th cores on the big cluster (I don't know why) falls displaying how they don't work but believe me they do. Tried to do a bit of monitoring my self & depending of game & or video player the cpu utilisation varies but little cores do meet their max frequency when needed & big ones do stay around 1200MHz when used but if you ask me that is perfectly normal & desired actually if it whose otherwise you would got thermal throttling. So this doesn't have to do anything with thermals nor CPU governor, it's probably imposed by the cpu ctr driver. I don't know where you got idea how any of this is crucial for either gaming or (good forgive) video playback; for GPU its crucial that one of CPU clusters (or with hot plug at least one core) scale along as it determines the RAM frequency, on the other hand video decoding (for supported formats) it's done on a DSP so it's desirable to CPU's actually stay as much as they can on active idle frequencies (periodically syncing system tasks) if you use unsupported video compression or for some other case choose to use software video decoder then CPU's jump to full frequency as they get utilised.

Zola III said:
First of all all monitoring apps aren't real-time secondly they some times have the problem with displaying correct informations for 2,3,4th cores on the big cluster (I don't know why) falls displaying how they don't work but believe me they do. Tried to do a bit of monitoring my self & depending of game & or video player the cpu utilisation varies but little cores do meet their max frequency when needed & big ones do stay around 1200MHz when used but if you ask me that is perfectly normal & desired actually if it whose otherwise you would got thermal throttling. So this doesn't have to do anything with thermals nor CPU governor, it's probably imposed by the cpu ctr driver. I don't know where you got idea how any of this is crucial for either gaming or (good forgive) video playback; for GPU its crucial that one of CPU clusters (or with hot plug at least one core) scale along as it determines the RAM frequency, on the other hand video decoding (for supported formats) it's done on a DSP so it's desirable to CPU's actually stay as much as they can on active idle frequencies (periodically syncing system tasks) if you use unsupported video compression or for some other case choose to use software video decoder then CPU's jump to full frequency as they get utilised.
Click to expand...
Click to collapse
For monitoring real time cores, i go to development option and select Show cpu usage option....that i think doesn't lie....the problem im facing is that why doest the cores doesn't stick to selected frequency....ive never seen it do that on other phone before...even when the phone heats or overclock...theres always for us to change it manually if we want to..so for my case, its not like that...it persistently selected what it want...
The problem im facing is in fact a video playback...Hevc x265 1080p 24fps.....so if your aware, hevc is a new encoder for video playback with lower size but better quality...but to run it, it needed more processing power...ive tried with same format but with 720p only...it runs flawlessly...so i assume 1080p will do the same....but in this case...its not....yes the video only support software decoding...and i used mx player for it...since it support it, ive set it to run at max performance....to run all cores to play video...
Ive run the video at 34° battery and cpu...small cores run max clock...and also 2 big cores run max 1800mhz....the video runs smoothly...until the temp reaches 37° the big cores start to slow down to 1600mhz....then after a while 39° 1190mhz....then the video start stuttering badly until in unwatchable....
So this behavior of big+small cores is for me kinda unnatural or is it, it supposed to be acting like that...i dont know...this is the first cluster core phone i ever used...so if it supposed to be acting like that, then are we getting the most out of the phone performance if it always dumb down like that...

Monitoring does lie (check by running Volumark bench when it happens) & that temperature/frequency down scaling is not normal behaviour.
I do know what H265 is (& even how it works) I also know both hardware (QC) and software (Google) libs on firmware are broken for it (surprisingly Vp9 just works fine). I still think how H265 full profile FHD culd be a little to much for a CPU alone.

Zola III said:
Monitoring does lie (check by running Volumark bench when it happens) & that temperature/frequency down scaling is not normal behaviour.
I do know what H265 is (& even how it works) I also know both hardware (QC) and software (Google) libs on firmware are broken for it (surprisingly Vp9 just works fine). I still think how H265 full profile FHD culd be a little to much for a CPU alone.
Click to expand...
Click to collapse
That's why im scratching my head all this time...ok ill do some research more and post if anything new or if im able to solve it...thanks for the knowledge...

Just for curiosity...i ran Volumark at cool temp 32° and all cores run well....got 72 at Volumark.
But i run again with temp 38° and my cores, like i said earlier, big cores max at 1200mhz and the other one offline...got 39 at Volumark.

martin132014 said:
Just for curiosity...i ran Volumark at cool temp 32° and all cores run well....got 72 at Volumark.
But i run again with temp 38° and my cores, like i said earlier, big cores max at 1200mhz and the other one offline...got 39 at Volumark.
Click to expand...
Click to collapse
As I told you that isn't normal behaviour. I would re flash firmware or better yet if you have a full backup in recovery if I whose you.

This is my logcat...if someone have some free time or care to help me solve my problem, care to take a look...
Im hoping someone could provide me an answer for me to fix my problem im having...i dont think i can live with a phone that behave like this...
Im not able to read it and hoping someone can...just post it here.
I take this log out from kernel audiutor...so i hope thats ok..
https://drive.google.com/folderview?id=0B5jpDdyf-VE_bC13T0lValF2d1U

Uffff. Log didn't show much at least not reasonable to me. There are cuple of IO denials at the end. Did look last cuple of pages. It's really hard to get to the bottom of this, actually impossible regarding how much potential problematic things you are using, from xposed framework to the fact that you are on beta MiUI relase to the fact you used various tuning apps that changed the behaviour. Sorry but I cant really help you. If this persist after flashing full official stable firmware freshly then try to catch the fresh logcat right afterwards down frequency cpu happens along with screanshots, post it hire and fail the official bug report at MiUI forums (with a screanshots & logcat attached).
Best regards.

https://drive.google.com/folderview?id=0B5jpDdyf-VE_bC13T0lValF2d1U
Well, i did a fresh install but using latest Official dev Rom, did not touch nothing or change anything on the rom after install...just install couple of apps and do the test....but unfortunately, the problem still there....
Here are the fresh log cat, if your wanna take a look and feedback...this is the last time i think...i will try to contact post it on Miui forum as well.

Touch screen randomly stops functioning

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.