READ EVERYTHING BEFORE ATTEMPTING ALSO DO SO AT YOUR OWN RISK.
Required. you must have an oc and voltage support kernel. jfbs stock roms have both oc and voltage. cars1189 stock rom does not but he provides link to kernels that do. Dont use exuv or uv kernels while doing this. well you can but if your new to this it is recommended to use regular oc kernel without uv/exuv. Also ram size does not matter.
What else do you need:
an app that allows you to change clock speed and voltages. if you dont already have one get performance control here (i use this thanks to jfbs for finding it).
*NOTE* never ever leave phone unintended when doing this until you find your chips sweet spot. YOU HAVE BEEN WARNED. otherwise if you listen and follow my advice you wont cause any major harm to your phone or any harm to your phone. Also do NOT have the settings apply at boot until you find all your settings. keep a pen or pencil and paper ready so you can remember workings settings.
1. remove case (if you have one on your phone) and battery cover. (this is just a safety precaution should your power button not work to pull that battery.
2. open up your overclocking app. (in my case performance control). set min and max frequency/speed to 245mhz
3. go to voltage settings and change the current voltage for 245760khz (really 245mhz) which is stock 900mV to 875mV (decrease by 0.25). close app out swipe around home screen and apps draw. open and close contacts list and see if phone freezes. we are not worried about phone running slow at this point until you reach 1ghz+ point of this. IF phone freezes/locks up hold power button to reboot phone or just pull battery and put it back in (personally i just use power button). if phone doesnt not freeze lower voltage again by 0.025 which should be 850mV. continue this process until phone DOES freeze so make sure you you wrote down last working voltage and as soon as phone freezes reboot or pull battery.
4. Once you found the lowest working voltage for 245mhz up the min and max frequency (speed) to 368mhz (368640khz)
5. Do the same thing as step 3 which is decrease the voltage by 0.025mV for the frequency for 365mhz. and repeat for each frequency up to 1ghz. Once you get to doing 1ghz voltage and above. The testing phone phase will be different but still flow the decrease by 0.025mV. for testing use any 3d game not candy crush type. and let it run for at least 10mins actually playing with phone plugged into charger. when you reach the spot where the phone freezes unplug both charger and force reboot/pull battery.
6. Once you find all of your working voltages for each frequency then you can set min back to 245mhz and your max to which ever you was able to hit. then set all of your volt settings in and save it for set on boot.
Note. 1.2ghz-1.4ghz seems to be a very good and safe battery to performance ratio. even more so if you followed my directions properly.
EDIT:
My settings for comparison.
Frequency Range: min.256mhz max 1401mhz(1.4Ghz)
Voltage scale:
122880KHZ - 700mV
245760KHZ - 700mV
368640KHZ - 700mV
768000KHZ - 925mV
806400KHZ - 950mV
902400KHZ - 975mV
1017600KHZ - 1000mV
1113600KHZ - 1050mV
1209600KHZ - 1100mV
1305600KHZ - 1150mV
1401600KHZ - 1200mV
pretty awesome you guys are still squeezing the juice out of the exhibit. XD
teerout said:
pretty awesome you guys are still squeezing the juice out of the exhibit. XD
Click to expand...
Click to collapse
i just got this phone only a year ago... also the guide should work for any phone that has oc and voltage control support. but thanks
my new phone, motorola droid, is not as developer friendly as the samsung. i should have done more research before getting it. motorola and verizon have it pretty locked down, no flashing and awesomeness. getting root privileges was a 15 step process.....oh for the days of flashing with the exhibit...i still have a red case and a green flowery case if anyone wants them.
teerout said:
my new phone, motorola droid, is not as developer friendly as the samsung. i should have done more research before getting it. motorola and verizon have it pretty locked down, no flashing and awesomeness. getting root privileges was a 15 step process.....oh for the days of flashing with the exhibit...i still have a red case and a green flowery case if anyone wants them.
Click to expand...
Click to collapse
any electronic can be overclocked and under/over volt. Over voltage is fine if electronic requires a outlet to run e.g pc. game consoles. while undervolt is best for battery operated devices as you would want to have long operation time between charging xD.
Updated OP with my personal settings for this phone.
Thanks for the guide, Will be giving this a try this weekend... Well this and possibly flashing that new Mahdi Rom for the exhibit
Thanks!
TripFX said:
READ EVERYTHING BEFORE ATTEMPTING ALSO DO SO AT YOUR OWN RISK.
Required. you must have an oc and voltage support kernel. jfbs stock roms have both oc and voltage. cars1189 stock rom does not but he provides link to kernels that do. Dont use exuv or uv kernels while doing this. well you can but if your new to this it is recommended to use regular oc kernel without uv/exuv. Also ram size does not matter.
What else do you need:
an app that allows you to change clock speed and voltages. if you dont already have one get performance control here (i use this thanks to jfbs for finding it).
*NOTE* never ever leave phone unintended when doing this until you find your chips sweet spot. YOU HAVE BEEN WARNED. otherwise if you listen and follow my advice you wont cause any major harm to your phone or any harm to your phone. Also do NOT have the settings apply at boot until you find all your settings. keep a pen or pencil and paper ready so you can remember workings settings.
1. remove case (if you have one on your phone) and battery cover. (this is just a safety precaution should your power button not work to pull that battery.
2. open up your overclocking app. (in my case performance control). set min and max frequency/speed to 245mhz
3. go to voltage settings and change the current voltage for 245760khz (really 245mhz) which is stock 900mV to 875mV (decrease by 0.25). close app out swipe around home screen and apps draw. open and close contacts list and see if phone freezes. we are not worried about phone running slow at this point until you reach 1ghz+ point of this. IF phone freezes/locks up hold power button to reboot phone or just pull battery and put it back in (personally i just use power button). if phone doesnt not freeze lower voltage again by 0.025 which should be 850mV. continue this process until phone DOES freeze so make sure you you wrote down last working voltage and as soon as phone freezes reboot or pull battery.
4. Once you found the lowest working voltage for 245mhz up the min and max frequency (speed) to 368mhz (368640khz)
5. Do the same thing as step 3 which is decrease the voltage by 0.025mV for the frequency for 365mhz. and repeat for each frequency up to 1ghz. Once you get to doing 1ghz voltage and above. The testing phone phase will be different but still flow the decrease by 0.025mV. for testing use any 3d game not candy crush type. and let it run for at least 10mins actually playing with phone plugged into charger. when you reach the spot where the phone freezes unplug both charger and force reboot/pull battery.
6. Once you find all of your working voltages for each frequency then you can set min back to 245mhz and your max to which ever you was able to hit. then set all of your volt settings in and save it for set on boot.
Note. 1.2ghz-1.4ghz seems to be a very good and safe battery to performance ratio. even more so if you followed my directions properly.
EDIT:
My settings for comparison.
Frequency Range: min.256mhz max 1401mhz(1.4Ghz)
Voltage scale:
122880KHZ - 700mV
245760KHZ - 700mV
368640KHZ - 700mV
768000KHZ - 925mV
806400KHZ - 950mV
902400KHZ - 975mV
1017600KHZ - 1000mV
1113600KHZ - 1050mV
1209600KHZ - 1100mV
1305600KHZ - 1150mV
1401600KHZ - 1200mV
Click to expand...
Click to collapse
Thanks a lot man! I still have this phone, and i am trying to squeeze out as much juice as possible. Going to be switching to the Oneplus one soon, or the nexus 5!
help
Hello i have an exhibit ii 4g running mahdi 4.4.4 kitkat can i just download the performance app and follow this instrccions or do i need to flash a kernel to overlock my phone?
Andresakapaco04 said:
Hello i have an exhibit ii 4g running mahdi 4.4.4 kitkat can i just download the performance app and follow this instrccions or do i need to flash a kernel to overlock my phone?
Click to expand...
Click to collapse
all of jfbs roms are overclockable by defualt so just download performance app and follow instructions. be save and watch temps if your overclocking keep it below 35c is possible or if battery gets really warm.
TripFX said:
all of jfbs roms are overclockable by defualt so just download performance app and follow instructions. be save and watch temps if your overclocking keep it below 35c is possible or if battery gets really warm.
Click to expand...
Click to collapse
Thanks for this response one more question what are the benefits of overlocking my phonr aside from more batery lifee??? ... i wana give this a try so i can keep using my exhibit
Thanks!
This will be helpful when undervolting my parents' phones.
undervolting will give you the better battery life while keeping the same performance
overvolting will drain the battery faster
underclocking will drop performance and save more battery life then just undervolting
overclocking will give you better performance
When it comes to any mobile device it is recommended to undervolt and overclock as you want as much battery life as you can while getting a performance boost or just to undervolt to save battery only.
Desktops are made to handle heat and voltage a lot better thus most ppl will overvolt and overclock to get the fast possible performance as you are always connected to a main power source.
@TripFX, thank you for the comprehensive OC & UV guide. I've been tinkering with the voltage settings for about a week via Performance Control and I think I've found a good spot for both my Exhibit devices.
Here are my settings (using cars1189 Christopher K^Kernel uv vhm 9-9-2014 build)...
EDIT: Updated voltage & CPU settings.
CPU Frequency:
Max. 1401 Mhz
Min. 368 Mhz
Voltage Settings:
122880KHZ - 750 mV
245760KHZ - 750 mV
368640KHZ - 800 mV
768000KHZ - 925 mV
806400KHZ - 950 mV
902400KHZ - 975 mV
1024000KHZ - 1000 mV
1113600KHZ - 1025 mV
1209600KHZ - 1050 mV
1305600KHZ - 1075 mV
1401600KHZ - 1125 mV
Btw, 750 mv is the lowest 122880KHZ, 245769KHZ, and 368640KHZ can be set to using the kernel mentioned above. If anyone wants to go lower, you'll need to try a different kernel or one of jfbs ROMs. cars1189's uv kernels seems to do okay (every device is different though, so be careful) but I would strongly advise against using exuv (both my devices couldn't handle exuv).
Also, device temp. has decreased by a couple degrees overall, couldn't be happier!
jajb said:
Here are my settings (using cars1189 Christopher K^Kernel uv vhm 9-9-2014 build)...
EDIT: Updated voltage & CPU settings.
CPU Frequency:
Max. 1401 Mhz
Min. 368 Mhz
Voltage Settings:
122880KHZ - 750 mV
245760KHZ - 750 mV
368640KHZ - 800 mV
768000KHZ - 925 mV
806400KHZ - 950 mV
902400KHZ - 975 mV
1024000KHZ - 1000 mV
1113600KHZ - 1025 mV
1209600KHZ - 1050 mV
1305600KHZ - 1075 mV
1401600KHZ - 1125 mV
Click to expand...
Click to collapse
I almost copied your exact settings for my T679 and it's running nice (I've set min/max to 245 MHz/1209 MHz)
However I was curious as to what you've set for Governor and IO Scheduler; I've just left it on default: ondemand and row. Any other special settings or tweaks?
I ask because temp has definitely lowered, but battery life *I think* seems to drain a bit faster (though I do have a bunch of communication apps that probably sync throughout the day).
ZHXS said:
I almost copied your exact settings for my T679 and it's running nice (I've set min/max to 245 MHz/1209 MHz)
However I was curious as to what you've set for Governor and IO Scheduler; I've just left it on default: ondemand and row. Any other special settings or tweaks?
I ask because temp has definitely lowered, but battery life *I think* seems to drain a bit faster (though I do have a bunch of communication apps that probably sync throughout the day).
Click to expand...
Click to collapse
as far as more tweaks to boost performance. if all the apps you use is art compatible then i'd suggest switching to art. massive cpu difference between davlik and art. least from my own experience. as far as battery drain i would recommend using an app such as greenify. for gov's and sched. mine i left ondemand but sched put it on sio. however i recommend reading over this as it will help you get a much better idea of what would work best for you. everyone uses the their phone differently so it should technically vary from person to person.
Just a heads up to anyone undervolting. Be careful undervolting below 750mv. I noticed on my phone that the battery started overheating at 725mv and below. 750 and above was fine.
Related
Hi there,
I'd like to overclock my IncS to 1,3 Ghz...
But I don't know the right settings.
Can you please tell me the right setting for best performance (e.g. oc to 1,3ghz) and best battery life?
thanks
does anybody know?
Set max to your desired, min to the lowest it will go and scaling to smartass.
I'm OCd to over 1.4 and no issues... UCd to 192 with smartassv2 governor
Sent from my Incredible S using XDA App
the best performance I have experienced in my INC is when I put oc / uv beater to the following:
wake gov: ondemand
wake mins: 245000
wake max: 1228800
Sleep gov: Conservative
my sleep: 245000
Sleep max: 691200
when I take a test in antutu nenchmark for I the following result.
score: 2729
If I clocked lower or higher, the result is lower
Overclocking depends entirely on your chip.
You should use whatever governor suits your needs.
I personally use ondemandx which speeds up on demand (as the name implies), conservative tries to keep the frequency as low as possible, interactive uses max frequency if min isn't enough, smartass is an improvement of interactive that keeps performance high while improving battery life (meaning there's little reason to use interactive).
You can find it in more detail here.
So basically, smartass if you want performance, conservative if you want battery life, ondemand if you want something in between. In reality though, I don't think you'll see much difference between them and I've seen no difference in idle power draws, so if you don't use your phone all that much, they won't be that different.
Once you've picked a governor, you should set min speed to 122000 (no reason to use any higher) and max to whatever you want. Your phone will probably crash or suffer from bad performance if you go over 1.5 GHz, but it varies a lot. Might happen even earlier.
Once you've found your desired performance level, you should start tweaking your voltages. You can do that under the UV profile. In there, you can adjust voltages at different speeds and the phone will automatically use them at whatever speed it's at. You should undervolt to increase battery life, so start by reducing all by 25 or 50 and then temp apply. Use it like that for a couple of hours and if it doesn't freeze, you're probably stable. You can either stop here or spend many hours tweaking it further, but that'll take many hours to get right.
This is my setting
Sent from my HTC Incredible S using xda premium
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Me4oKyX said:
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Click to expand...
Click to collapse
In my opinion, and I'm sure many others', Virtuous daemon is the best by far.
It comes standard in a lot of roms, and using the OC/UV beater
http://forum.xda-developers.com/showthread.php?t=1207546
it would have the best performance. I've set mine similar to yours and with this method, you can set the phone to underclock when battery reaches a low level
As some may now, the droid 4 can be overclocked already thanks to TEKAHUNA the link below is a link to his thread. All instructions and download links are there i currently am overclocked to 1388. All vsel controls are available also.
Link
tekahunas thread
After loading the modules you can use quickclock advanced to change ALL values.
Sent from my DROID4 using XDA App
Have you tried OCing higher? Or are you just keeping it at 1388 to be safe?
phrir1 said:
As some may now, the droid 4 can be overclocked already thanks to TEKAHUNA the link below is a link to his thread. All instructions and download links are there i currently am overclocked to 1388. All vsel controls are available also.
Link
tekahunas thread
Sent from my DROID4 using XDA App
Click to expand...
Click to collapse
If you check my Utility I added an Overclock Install option. It also has links to a better video guide to overclocking.
jgardner said:
Have you tried OCing higher? Or are you just keeping it at 1388 to be safe?
Click to expand...
Click to collapse
Yeah i was running 1.4 stable for a little while, but after a while i noticed lag here and there so i just dropped it down to 1388 to be on the safe side. After loading the modules i use quickclock advanced to play with all the settings.
Sent from my DROID4 using XDA App
Hi phrir1, mattlgroff,
Which file should I download for Droid 4? I cannot see it was listed there but only saw Droid 3 only.
BTW, is it no problem to running on stock 2.3.6 rom ?
Million thx!
I kept to use 2.3.6 because of webtop 2.0
Kent
I installed the two zip from recovery, but in the ommand-line, I have no "overclock" directory under /proc/.
Anybody can use that desription?
Adamyno said:
I installed the two zip from recovery, but in the ommand-line, I have no "overclock" directory under /proc/.
Anybody can use that desription?
Click to expand...
Click to collapse
please use the jbx kernel I posted in developers section
lucize said:
please use the jbx kernel I posted in developers section
Click to expand...
Click to collapse
I installed CM 11 Nightly, kernel 3.0, kernel_jbx, moto_init_d, mo_simp_1.5_spyde zip files, but nothing happens, I have no overclock directory
Adamyno said:
I installed CM 11 Nightly, kernel 3.0, kernel_jbx, moto_init_d, mo_simp_1.5_spyde zip files, but nothing happens, I have no overclock directory
Click to expand...
Click to collapse
On CM11 you can only use lucize's jbx kernel or dtrail1's jbx kernel to overclock, you're installing a bunch of things that shouldn't be used on CM11
I've been using stargo's CM11 with dtrail1's jbx kernel with the droid 4 overclocked/undervolted to 1.3ghz and GPU at 384mhz with good stability (certain settings like interactive govenor will make the device unstable though), lucize's kernel is based off dtrail1's kernel and should be more suited for our device.
I use KitKat 4.4.4 slimkat or CM11
and jbx kernel from lucize
to change cpu setting i use no-frills CPU or Trickstar MOD
but in this programs I can't go more then 1,3 GHz
from comand line I don't have /proc/overclock dir
where can I change proper CPU values ?
I only want to check if phone can work with bigger and to have few more point in Atutu :>
jaqjacek said:
I use KitKat 4.4.4 slimkat or CM11
and jbx kernel from lucize
to change cpu setting i use no-frills CPU or Trickstar MOD
but in this programs I can't go more then 1,3 GHz
from comand line I don't have /proc/overclock dir
where can I change proper CPU values ?
I only want to check if phone can work with bigger and to have few more point in Atutu :>
Click to expand...
Click to collapse
You have to use the MPU OC option to get above 1300mhz. Disable "Battery Friend" first otherwise it won't allow you to adjust the MPU setting.
CPU frequency is multiplied by the MPU, adjusting it will effect all CPU steps much like overclocking frontside bus on a PC, stock is 100, so think of the 1300mhz setting as a 13x multiplier, 300mhz as a 3x multiplier, and so on.
A good, easily achievable OC is 108 MPU
100 MPU x 13 = 1300mhz
108 MPU x 13 = 1404mhz
100 MPU x 3 = 300mhz
108 MPU x 3 = 326mhz
and so on... much beyond this you have to fiddle with the voltages a lot otherwise you will get random reboots, I found I needed a MPU voltage of 1420 (1.420v) to get 1404mhz completely stable. The other voltages are pretty generous and I have found they can be undervolted significantly while running 1.4ghz+.
With the phone at 1495mhz I managed to get just shy of 14,000 in Antutu but it was not stable because of voltages... roughly 1450mhz should be safe for a daily driver while maintaining good battery life and low heat once lowest possible stable voltages are worked out, maybe more, still testing it all myself.
Elanzer said:
You have to use the MPU OC option to get above 1300mhz. Disable "Battery Friend" first otherwise it won't allow you to adjust the MPU setting.
CPU frequency is multiplied by the MPU, adjusting it will effect all CPU steps much like overclocking frontside bus on a PC, stock is 100, so think of the 1300mhz setting as a 13x multiplier, 300mhz as a 3x multiplier, and so on.
A good, easily achievable OC is 108 MPU
100 MPU x 13 = 1300mhz
108 MPU x 13 = 1404mhz
100 MPU x 3 = 300mhz
108 MPU x 3 = 326mhz
and so on... much beyond this you have to fiddle with the voltages a lot otherwise you will get random reboots, I found I needed a MPU voltage of 1420 (1.420v) to get 1404mhz completely stable. The other voltages are pretty generous and I have found they can be undervolted significantly while running 1.4ghz+.
With the phone at 1495mhz I managed to get just shy of 14,000 in Antutu but it was not stable because of voltages... roughly 1450mhz should be safe for a daily driver while maintaining good battery life and low heat once lowest possible stable voltages are worked out, maybe more, still testing it all myself.
Click to expand...
Click to collapse
Thanks! 400 Points more on first try and still testing.
Could you share yours daily use cpu parameters ?
For example
1300 x MPU 108 1420
1100 x MPU 108 1380
.....
or just print screens from trickstar mod or any other cpu app.
I'm curies about battery level too.
Other thing on mys Milestone2 i have only 4 CPU Frequency step with custom changeable example: originaly was 1000,800,600,300 best for my 1200,900,500,300
On Droid 4 apps shows that I have more then 10 on Lucid Kernel
Does cpu governors use all of that steps ?
If there are only few of them can I and should I change those steps ?
jaqjacek said:
Thanks! 400 Points more on first try and still testing.
Could you share yours daily use cpu parameters ?
For example
1300 x MPU 108 1420
1100 x MPU 108 1380
.....
or just print screens from trickstar mod or any other cpu app.
I'm curies about battery level too.
Other thing on mys Milestone2 i have only 4 CPU Frequency step with custom changeable example: originaly was 1000,800,600,300 best for my 1200,900,500,300
On Droid 4 apps shows that I have more then 10 on Lucid Kernel
Does cpu governors use all of that steps ?
If there are only few of them can I and should I change those steps ?
Click to expand...
Click to collapse
These are my current settings. I'm still working on them because I adjust them then use the phone for 2 full days / charges to test the stability, not every stepping is adjusted completely down - I adjusted/tested the middle voltages in groups and only adjusted the top/bottom voltages individually. There's no quick way to test them because they'll test perfectly in a CPU stress test app then within 5min of browsing the device will reboot. These particular settings have been stable for a few days. I could not get even 1443mhz stable what so ever, even after adding +75 to all voltage steps, so maybe 1.4ghz is closer to a realistic limit.
Also the voltages on this device/kernel seem to have a limit of how low you're allowed to set it. I'm not sure if this is an artificial limit or a limit of the hardware, but 952 is the lowest voltage available for 300mhz even though the device could likely undervolt far more at this frequency. Since 100 and 200 also use the same 952 voltage, there is zero point in setting the minimum frequency to anything lower than 300, as they all use the same voltage.
I'm not allowed to post a link directly because I don't have 10 posts yet (this rule is stupid), but here you go: hxxp://i.imgur.com/01xb0Wp.png
The CPU govenor uses all steps provided you're using ktoonservative. I found I couldn't use most other governors because they would freeze the device (ie: switching CPU governor Interactive would freeze the device, switching the I/O governor from deadline to sioplus freezes, etc). There is lots to adjust in the ktoonservative governor for performance/battery life.
I'm currently using these settings right now with good results as a balance between battery life and performance:
up_threshold 80
up_threshold_hotplug 85
down_threshold 30
down_threshold_hotplug 25
sampling_down_factor 10
sampling_rate 35000
sampling_rate_screen_off 30000
freq_step 1
disable_hotplugging 0
freq_step decides how much the CPU ramps up, a setting of "1" ensures it uses all frequencies. If you use "20" it'll increase the frequency to the closest 20% each time instead of closest 1%. Set to 100 and the governor works identical to the "ondemand" govenor (ie: CPU will go straight from lowest to highest speed). The thresholds have to do with how much % the CPU utilization has to be at before it will increase or decrease the frequency, so lower numbers can increase responsiveness by having the CPU increase it's speed quicker.
I use yours governors conifg
and
MPU 108
1404 Mhz - 1302
1296 Mhz - 1300
1188 Mhz - 1275
1080 Mhz - 1275
972 Mhz - 1255
864 Mhz - 1210
756 Mhz - 1160
648
540
432 Mhz - 1117
324
216
108 Mhz - 952
those are my stable for now
but the battery isn't so good I can only dream about 2 days
It is how your say benchmark pass but open some app and chance for reboot is 50/50
Is there a way to see current voltage ?
Because phone shouldn't work on 1404Mhz x 1302v and i think that I miss something.
jaqjacek said:
I use yours governors conifg
and
MPU 108
1404 Mhz - 1302
1296 Mhz - 1300
1188 Mhz - 1275
1080 Mhz - 1275
972 Mhz - 1255
864 Mhz - 1210
756 Mhz - 1160
648
540
432 Mhz - 1117
324
216
108 Mhz - 952
those are my stable for now
but the battery isn't so good I can only dream about 2 days
It is how your say benchmark pass but open some app and chance for reboot is 50/50
Is there a way to see current voltage ?
Because phone shouldn't work on 1404Mhz x 1302v and i think that I miss something.
Click to expand...
Click to collapse
I am 3 days uptime on these current settings at 111 MPU with heavy use:
Code:
hxxp://i.imgur.com/17iPAZL.png
The phone rebooting is generally caused by voltage being too low. 1302 is way too low for 1404mhz and is probably why you're getting the reboots. The "1302" value translates to "1.302v" which is a perfectly normal CPU voltage, but it's really low and I can't imagine that being stable for you since I need "1390" for 1404. There isn't a way of checking the current voltage other than looking at the current frequency.
I have not further reduced the 1332 and 1221mhz settings yet as I found reducing them was causing my issues getting above 109 MPU. Probably in a week or two so of use and adjustments I'll post my final tuned settings after I squeeze all I can out of it, I just require a few days of solid uptime to verify stability because I can't seem to find a stress testing program that ensures total stability. it's just that I test each setting over a period of days. My settings might not work for you since all CPUs aren't identical in quality, but it should give you a ballpark of settings.
If you want to improve battery further try looking at adjusting the automatic screen brightness, I'm currently using these settings, although you could easily further reduce brightness:
Code:
hxxp://imgur.com/D3sKAIn
hey guys, just imported 2 droid 4s to the uk.
an amazing device still today i think.
Can anyone suggest how to get mpu oc to stick after reboot? It always seems to reset to 100.
The frequency oc sticks but drops to 1300 due to mpu not sticking.
Q&A for [KERNEL][D5803&D5833] AndroPlusKernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][D5803&D5833] AndroPlusKernel. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
Very nice kernel, fast and smooth - great work and port.
Anyone knows if it's possible to use any third party kernel app to boost the headset volume?
Working
Hi this is my first post, infact I joined so I could report my findings.
I would just like to confirm so far that V5 working on my Z3C using the .93 firmware. I didn't need to wipe cache/dalvik/data partitions either.
For purposes of settings configuration, I'll be using TricksterMod
For stress testing purposes I'll be using Stability Test 2.7
Overclocking
Overclocking seems to work, I'll stress test and report back with the results.
I was wrong, it is unstable when overclocking and stress testing, with the phone force rebooting 1-5 seconds in to the stability test which loaded all 4 cores. Tried 2899Mhz and 2880Mhz (were both unstable and didn't try 2.72, 2.75, 2.57 either - I might try stability testing them.) Was completely stable at 2.47GHz, and it actually stuck there, no throttling in place! I stopped the stress test when the CPU temp was around 77-80C as my hand was getting burnt! The battery temp reached about 46C. It took 10 mins of stress testing for this to be reached. When the stock kernel was in place it would begin throttling after about 1-20 seconds under full load. First 2.2GHz, then 2 then 1.7 then 1.5 and eventually 1.25 after about 2-4mins.
I couldn't do a single core test though. I suspect as most games use single core or dual cores it wouldn't get overly hot.
My opinion is that fast clocked phones should be marketed with 2 speeds. The highest it'll reach under a boost mode (turbo for Intel's i5 and i7 series), and a slower speed that it'll average out at under thermal pressure. The Z3Cs would be turbo: 2.5GHz and normal: 1.5GHz.
Governors
These are quick tests I'm performing here to provide a quick look at responsiveness and potential unnecessary CPU jump ups.
Wheatley - most of the time it's hovering at top speed when approx CPU usage is 9%, it'll occasionally hunt down to 300Mhz but then right back up to 2899MHz. This one is speedy though. Governor tunables available.
Lagfree - idles at 300MHz - 960MHz then hunts up to 2.2-2.9Ghz when needed and turns on the second core. It seems to slow back down to idle. This one seems to have fast scrolling, sliding notifications pane quickly). No governor tunables.
SmartassV2 - idles at 300Mhz, speeds up to 422-960 on core 0, and turns on core 1 at 1.2-1.5GHz for a few seconds under fast scrolling and notification pane opening. Seems quite responsive. Probably good for battery life hopefully with the responsiveness of Interactive. No governor tunables.
Lionheart - Idles at 960 MHz for a few seconds then slows down to 300MHz with the odd increase to 729MHz. Core 0 and Core 1 reaches 1.26GHz under scrolling, notification pane opening. As fast as the others. Governor tunables available.
Hotplugging
Intelliplug appears to work better than MP-Decision - now only one core is on during idle, instead of 2.
MP-Decision was disabled to avoid conflicts.
Undervolting
I've only undervolted 300MHz to 675MHz from 775MHz as of writing this post.
Tried quickly undervolting in trickstermod by setting them all about -75mV, stability tested it, appears stable. I'll tweak the voltages a bit better when I do a scaling stability test.
Issues I've experienced
Sound Control is the only thing so far that causes a reboot. However music still plays over the speakers and headphones. Equaliser works too.
Upon rebooting, the CPU top speed will set itself to 2.2GHz, despite being set higher and saved at a higher speed in Trickstermod. Certainly trivial though.
Strange thing I've noticed: On the undervolt part I've noticed that there is a freq called 3033MHz, but no 2899MHz freq. Just an observation.
Misc
Force Fast Charge confirmed working! Before flashing new kernel charge went up 5% in about half an hour. It's now up another 5% in a matter of 5-10mins. This is when plugged to my PC.
Vibrator strength - set to 20 from 31, much quieter on table and can still feel it.
I'd like to say a huge thank you to DooMLoRD and AndroPlus for developing this stable kernel. Now my Z3C is worth the £28 a month I'm paying for again. Since this silly lad decided to bork the camera, Bravia functionality etc by rooting it on the first day. I'll report back and edit the post with my findings.
Max won't go beyond 2.266 GHz, Min won't change.
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
pjmanalo said:
Hi All,
Firstly, great job with the kernel. Our Z3C is such a capable piece of kit and this just makes it that much better.
I'm running stock, 23.0.A.2.93, unlocked, rooted.
Problem:
I've tried using both SetCPU and No-Frills and while both show frequencies that are supposedly selectable above 2.266 GHz, neither app would actually respond. Meaning the max frequency will still only be 2.266 GHz even if I tried selecting something like 2.458 GHz (which should be selectable given that stock is 2.458 GHz.) See caps.
In addition, the Min value just won't change at all from 300 MHz. The frequencies scale up and down as the load changes but I can't raise the Min (again using both SetCPU and No-Frills) from 300 MHz.
Tried: I've tried turning off stamina mode and frozen apps that could control CPU activity (e.g. I use DS Battery Saver). I changed up Governors and Schedulers. I've tried re-flashing the kernel and it still doesn't change these behaviors.
Question/Need help: Just wanted to ask if anybody else have any problems setting the max frequency beyond 2.266 GHz and/or changing the minimum frequency from 300 MHz? Would appreciate any help resolving this behavior.
Thanks in advance!
Click to expand...
Click to collapse
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
DBCJoey said:
Try installing TricksterMod (from Google Play store, trust me, you'll love it!) Then go to General and set the max speed to 2.46GHz or higher, and try using the Ondemand Governor too. I noticed that it wouldn't stick properly sometimes when using Interactive governor. If it doesn't stick for you then turn Frequency Lock on. Then check in the info tab that it's hitting the higher speed. Personally I'd recommend leaving the min speed on 300MHz. If you need constant high speeds, select the performance governor.
Click to expand...
Click to collapse
Thanks! That did the trick!
Odd that my usual app for the job across 4 other phones - SetCPU - doesn't work on what should essentially be the same job. [emoji55]
Please make sound_control drivers work so its possible to boost headphone volume on the Xperia Z3 Compact... Thanks
Nice work, a lot of updates I like it!
Is it possible to add a change log?
Thanks!
kernel for d5803 with the .93 but not .105
i search a kernel for the d5803 with the last .93 french version of phone
.5.77
Works great! Thanks a lot
Link for Z3C_D5803_AndroPlusKernel_v10.zip is dead
Pls upload in another location.
Yay sound control is working, thank you so much you're the best!
How to make this?
Hi AndroPlus,
I'm trying to figure out how one would go about building this boot.img that you've created.
What platform and compiler are you using?
Where are you getting sources the for the kernel? This file?
c9af6fc647060fb85dd646798453ec8f 23.0.A.2.105.tar.bz2
How do you construct boot.img from zImage + recovery?
Sorry if these are dumb questions.
Edit: never mind, I figured this out.
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/ contains most of the information I needed.
The arm version of gcc that ships with Ubuntu 14.04 worked fine - arm-none-eabi-gcc (4.8.2-14ubuntu1+6) - no need to track down any mystery binaries. I did have to make several modifications to the kernel source to get it to build. Interestingly, some of the cpufreq stuff contained code that was incorrect. Someone at Samsung needs to go look up what "sequence point" means.
The hardest part was figuring out how to turn the zImage + ramdisk into something I could boot.
This: https://github.com/sonyxperiadev/mkqcdtbootimg was the correct tool to use - again, no need to track down any mystery mkbootimg or dtbTool binaries.
Hope this is helpful to someone. As someone new to Xperia dev, I found most of the information out there worse than useless.
dear modders
i just want to say i overclocked my htc one m7 cpu from 1.7ghz to 2.1 GHZ
with a custom kernel called ElementalX-m7-22.3-Sense
is this save can the phone run this without any stability issue's or shall i downclock it to 1.9
i use M7_Sense7_artmod_10.0 rom Lolipop 5.0.2 with sense 7 cause this is the only one without any bugs like no sound when you got called or sms sound's no boot sounds
i fixed my boot sound anyway on this rom
so my question is wont my phone be fried by this overclock cause i saw in the aroma installer that it can be overclock till 3 GHZ
greets Rubenownz
Overclocking the CPU in any system usually results in 2 main things:
a. Significantly shorter battery life.
b. heating issues.
sometimes (less frequently) you might experience a crash and fc here and there.
So yeah, it won't be all rainbows and butterflies.
PS: you probably won't reap the benefits of your now overclocked CPU without an app like no frills CPU or kernel Aduitor. Your device's performance isn't just about its CPU frequency, there's the min Max frequency your system is allowed to utilize, the CPU governor, and the I/o scheduler..
and
PPS: don't and I repeat DO NOT go anywhere near 3 GHz.
good luck.
I'm runnimg 2.1 Ghz OC for over 2 years without any issues. I would like to note that 2.1 Ghz on Elemental was not too stable for me, so I ran that on 2.0 Ghz. Anyway - i don't have any issues with my kernel, no overheating, battery lasts 100% same as stock frequency, no reboots, everything works as it's ment to work. If you really want to run on that frequency, make sure you set your voltage table to match your CPU clocks. Undervolting is not a good idea on such high clocks, so you might want to raise your voltages for higher frequencies a bit
monrokhoury said:
Overclocking the CPU in any system usually results in 2 main things:
a. Significantly shorter battery life.
b. heating issues.
sometimes (less frequently) you might experience a crash and fc here and there.
So yeah, it won't be all rainbows and butterflies.
PS: you probably won't reap the benefits of your now overclocked CPU without an app like no frills CPU or kernel Aduitor. Your device's performance isn't just about its CPU frequency, there's the min Max frequency your system is allowed to utilize, the CPU governor, and the I/o scheduler..
and
PPS: don't and I repeat DO NOT go anywhere near 3 GHz.
good luck.
Click to expand...
Click to collapse
ok mate
yeah i could raise also min clocks might turn that a noch up
just was wondering if it was possible without any harms
there are now on 384mhz 1 core is always active and 3 others are sleeping aid64 tells me
the temps are now 29 celcuis for 2.1 ghz
donkeykong1 said:
I'm runnimg 2.1 Ghz OC for over 2 years without any issues. I would like to note that 2.1 Ghz on Elemental was not too stable for me, so I ran that on 2.0 Ghz. Anyway - i don't have any issues with my kernel, no overheating, battery lasts 100% same as stock frequency, no reboots, everything works as it's ment to work. If you really want to run on that frequency, make sure you set your voltage table to match your CPU clocks. Undervolting is not a good idea on such high clocks, so you might want to raise your voltages for higher frequencies a bit
Click to expand...
Click to collapse
yeaah the kernel has those options in aroma installer it set it safe i ques
ill post later some picture's of what ive been doing
good nites
here are some pictures of my sense 7 5.0.2 android system dump of htc one m9 for htc one m7 xD overclocked
some temps and cpu tweaks and ofc of the system (dont mind about the girl on the screenshot its my girlfriend not me iam a boy
btw i removed phone number on call menu cause it's private
Greets Rubenownz
I have this tabled for a long time, but as i rarely used it i didn't bother with it much. From day one back in 2014 the tablet was sluggish and laggy, today is just unbearable even for browsing. So i have decided to take a look of what can i do.
I have installed the latest (10.26.2019) LineageOS-14.1-Deathly with gapps nano.
I have installed CPU Throttling Test from the play store and start testing to see what's going on. I saw that the CPU Throttle instantly (like in 10-15 sec max) from 1900mhz to 600mhz, and this is where the sluggishness comes from, the CPU is constantly throttled no matter that you are just looking at a simple web page.
I started playing with the Deathly Adiutor and under-voltage the cpu, set the max to 1400mhz and this is where it is stable as it is. At 1400mhz constant 100% CPU stress the CPU temps are around 90c (at 95 the cpu starts throttling). Anything above 1400mhz even with under voltages CPU results in throttling within 1-2 min, but even like that at 1400mhz and GPU set to be always used and at minimum of 480mhz (with setting in dev options to always use gpu for 2d composition) the performance was really much much better then the stock settings.
I have continued to play with it and noticed that if i apply pressure with my fingers on the back panel just below the camera where is the most hottest, the temps are dropping 10-15C, so i have opened it and i saw the issue.
The issue is that the metal shield radiators does not make a good contact with the thermal pad on the back panel, and thus can't dissipate the heat well. This may variety from user to user as some back panels will make better or worse contact, but its far from ideal.
Its good that i have some spare thermal pads around and i have applied them, and the result is perfect, drop in 12-17Cfrom stock setup under continues stress.
As a final result i have managed to bump the CPU from 1400mhz to 1600mhz with 1087mV voltage and at max 84C (down from around 90 at 1400mhz) at constant 100% CPU stress. The performance gains are around 100 to 150% (At around 42-47k GIPS up from 20-25k GIPS stock in CPU Throttling test). Additionally i have to say, its extremely easy to open the back cover panel.
Furthermore, i made an video to see how it runs and the settings i use.
https://youtu.be/_UJdjPDQB00
I'm attaching before and after the mod photos.
Quick followup, i have run 3D Mark benchmark and PCmark, see the screenshots below. Managed to achieve the world fastest Tab S, enjoy
Awesome.. I followed ur recommendations and set 1087mv at 1600mhz and its fasttttt
rihui said:
Awesome.. I followed ur recommendations and set 1087mv at 1600mhz and its fasttttt
Click to expand...
Click to collapse
Thanks mate. I'm glad it helps According to 3DMark, the performance now is slightly better then Galaxy Tab A 2019, it really bring new life to this tablet and its ready to rock another couple of years
how's your battery life with minimum CPU speed at 1600
Screen on & Standby time?
rihui said:
how's your battery life with minimum CPU speed at 1600
Screen on & Standby time?
Click to expand...
Click to collapse
Its not the minimum CPU frequency that gives you the performance boost, its the maximum frequency limit at 1600mhz down from 1900mhz, as i explained, to gain the performance, you need to avoid CPU from overheating and throttle down itself to the ground. That's why the max frequency with the thermal pads and improved thermals is 300mhz below the stock 1900mhz, and without the pads my max stable frequency were 1400mhz (500mhz below stock).
The minimum frequency will only smooth out initial animations and things like that, but don't have much of an impact on the overall performance. With that said, increasing the minimum frequency ofc will eat more battery and you don't need it, you can safely set it to 650mhz (as low as it allows) and depending on your kernel governor policy should have the same or better battery life. As i said, the main gainer is preventing the CPU from overheating at 1900mhz and throttle down to 650mhz where it sits most of the time with stock settings.
In fact if you limit your max frequency to 1400 or 1600mhz depending on your stable thermal results, and set minimum to 650mhz, you will see the performance gain AND significantly increased battery life due to that CPU does not go to 1900mhz and does not eat that much power and voltage. You really need to fine tune it depending on your needs, but at stock CPU throttling down to 650mhz and staying there is an manufacturer (Samsung) failure, and if i were discovered this when i bought it, i would wanted refund, as they advertise 1900mhz CPU which almost never works at that frequency.
I tested this method on other tablets and phones, and while it happens on other devices to throttle down after 5-7 mins (not after 15 sec), i have never seen to throttle more then down to 80% of the advertised frequency, but the Tab S goes almost immediately down to 35% where it stays and cripple the device. Its really really bad engineering from Samsung.
Going to try this.
Thanks
A lot better .
What thickness of thermal pad should I buy? Probably will buy from Amazon unless I need to make a trip to Microcenter. Thanks for this suggestion @nauvho
osutx427 said:
What thickness of thermal pad should I buy? Probably will buy from Amazon unless I need to make a trip to Microcenter. Thanks for this suggestion @nauvho
Click to expand...
Click to collapse
Well as you can see on the picture, the CPU bed already has one black pad by Samsung by default which is around 0.2/0.3mm i think, but it does not make contact, so i put on the CPU radiator 1mm pad and on the other radiators i put 0.5mm to equalize in case my pad is too thick. Your guide should be how easy is to close the back-plate, if you need too much force you may need thinner. So i guess you can take 0.3, 0.5 and 1mm pads.
effing A
Wow
Applied the same settings that you show in the video and WOW! It's like a new tablet. I didn't even put thermal pads.
joelcool69 said:
Applied the same settings that you show in the video and WOW! It's like a new tablet. I didn't even put thermal pads.
Click to expand...
Click to collapse
nice
just rooted t800 with MM + trw + SU.
added some thermal pads like in the pics.
installed Deathly Adiutor ....which said that doesn't like the kernel..and doesn't let to change the cpu max speed, and the voltage page doesn't even exist
installed Kernel Adiutor from playstore with which I can lower the freq, and for 1600 it works 1-2min at 27-28000GIPS then starts to throttle
louis_alphons said:
just rooted t800 with MM + trw + SU.
added some thermal pads like in the pics.
installed Deathly Adiutor ....which said that doesn't like the kernel..and doesn't let to change the cpu max speed, and the voltage page doesn't even exist
installed Kernel Adiutor from playstore with which I can lower the freq, and for 1600 it works 1-2min at 27-28000GIPS then starts to throttle
Click to expand...
Click to collapse
Why are you using MM? Also, did you noticed that center pad is thicker and side ones are tinnier? what are your CPU temps? Also probably due to MM, but I'm getting around 42gpis (average) at 1.6, but you should really check your pads placement, thickness and temps, put the CPU under load note the temps before throttling down.
nauvho said:
Why are you using MM? Also, did you noticed that center pad is thicker and side ones are tinnier? what are your CPU temps? Also probably due to MM, but I'm getting around 42gpis (average) at 1.6, but you should really check your pads placement, thickness and temps, put the CPU under load note the temps before throttling down.
Click to expand...
Click to collapse
I'm using MM since I don't know if it worth to upgrade; does this LineageOS work well...all features (cam, scanner, soud etc) works with it?
used 1mm pad over the cpu... 0.5 otherwise (china made); also removed the small factory pad and placed another pad patch there; the back cover heats well and I assume that the heat doesn't have where to go.
since it's not throttling at 1600MHZ (almost 100%, take a look at the pic)...from where to get more than 28GIPS?
louis_alphons said:
I'm using MM since I don't know if it worth to upgrade; does this LineageOS work well...all features (cam, scanner, soud etc) works with it?
used 1mm pad over the cpu... 0.5 otherwise (china made); also removed the small factory pad and placed another pad patch there; the back cover heats well and I assume that the heat doesn't have where to go.
since it's not throttling at 1600MHZ (almost 100%, take a look at the pic)...from where to get more than 28GIPS?
Click to expand...
Click to collapse
I don't think removing the stock black pad were a good idea, I did not removed mine, my pad is next to it. Also CPU throttle app is not reliable to monitor cpu temp (at least for me) , you should do it by starting the throttle test and then switch to deathly auditor and monitor the temp and clock there or other app like CPUz or Aida. Look at the video how I monitored the temp. The CPU will start throttle at 93-95c so your temp of 81 cannot be accurate if it throttle. Didn't you said that you throttle at 1.6 in your previous post?
Regarding the performance I think it might be eigher app difference between mm and 7.1 or due to MM itself. And yes everything is working perfectly for me with lineage, camera, fingerprint, everything is fine and it is mile better then MM imo.
installed 7.1
pcmark 4330 with your mods.
so the thermal pads doesn't matter on MM.
from my testings on 7.1 the boost in pcmark comes form setting max freq 1600 + undervoltage (3000->3500), and another boost...by setting the lower freq to 1600 (3500->4300)
louis_alphons said:
installed 7.1
pcmark 4330 with your mods.
so the thermal pads doesn't matter on MM.
from my testings on 7.1 the boost in pcmark comes form setting max freq 1600 + undervoltage (3000->3500), and another boost...by setting the lower freq to 1600 (3500->4300)
Click to expand...
Click to collapse
Nice.
About the pads, they matter only if the CPU temp under load drops when you apply pressure with fingers on the back cover as i explained in my first post, but idk if this apply to all tablets or just mine. The boost comes from not throttling the CPU down and being stable at maximum possible frequency. The CPU can go up to 1900mhz and beyond (2.1 by spec), but the cooling is not enough for that frequencies.
I think that adding an 0.5-1mm copper heat pipe thru radiators or copper heat pads similar to flagship phones might push it to 1.9, will order some someday and try it.
now it will be interesting ?% it's the termal mod in this boost, which means, performing the test in PCMARK only with steps 1+2:
1. LineageOS-14.1-Deathly
2. Deathly Adiutor (which requires step 1) + CPU max freq 1600 + undervoltage at that freq + CPU min freq 1600
3. Thermal pads added inside the box.
Since I started with thermal pads...I can say that in MM it doesn't matter.
-after upgrade to 7.1 as I said..PC...MArk around 3000 (thermal pads mounted)
-after setting max freq 1600 + undervoltage I got a boost in PCMark to 3600
-in addition, with min freq 1600...got another boost..to 4300; in this turbo state..the battery drains quickly, but the interface it's fast like the wind.
PCMark doesn't use CPU at 100%, it counts also how fast cand do certain short tasks...and this matters because if CPU it's in it's low power states..it loose time to rise its freq and do the calc at full power.
louis_alphons said:
now it will be interesting ?% it's the termal mod in this boost, which means, performing the test in PCMARK only with steps 1+2:
1. LineageOS-14.1-Deathly
2. Deathly Adiutor (which requires step 1) + CPU max freq 1600 + undervoltage at that freq + CPU min freq 1600
3. Thermal pads added inside the box.
Since I started with thermal pads...I can say that in MM it doesn't matter.
-after upgrade to 7.1 as I said..PC...MArk around 3000 (thermal pads mounted)
-after setting max freq 1600 + undervoltage I got a boost in PCMark to 3600
-in addition, with min freq 1600...got another boost..to 4300; in this turbo state..the battery drains quickly, but the interface it's fast like the wind.
PCMark doesn't use CPU at 100%, it counts also how fast cand do certain short tasks...and this matters because if CPU it's in it's low power states..it loose time to rise its freq and do the calc at full power.
Click to expand...
Click to collapse
Thermal mode does matter alot, CPU thermals is everything, the lower temps are, the higher frequency you can push the CPU, more frequency = more performance. As i said, without the thermal pads i could not get 1.6ghz to be stable, only 1.4 were stable-ish.
In stock rom, CPU governor and states are set according to the temps with the stock cooling. But if you don't change settings it wont change much. However Samsung engineers did a terrible job with those default settings, so as i explained in my first post only doing the software changes had dramatic impact on the performance because you get the CPU stable even at 1.4, but the thermal mod push it further to 1.6
The true performance benchmark is the 3DMARK (my screenshots 3 and 4 for score "ice storm unlimited" test and "Sling Shot" test) this will push your CPU and GPU to the max, PCMark is more about daily use performance and also can be used to measure battery performance between different settings.
Yes leaving CPU with minimum of 1.6 will drain battery more quickly naturally, is using more power, i leave mine at 1.2 as minimum, but minimum speed should not matter much in benchmarks if you are using the same as mine CPU governor. CPU governor basically tells the CPU how to behave, like how quickly to rise the frequency, for how long and etc.