Related
Hello again,
Is there any risk with runnin my G1 at 528 constantly? I've got the big battery and its just so nice to not have to watch the lag all the time. Thanks.
Hi, there is absolutely no way your phone could be damaged. It's not actually clocking the CPU over it's native frequency, simply reclocking it. Also the voltage is left unchanged. To save battery the manufacturer (HTC) set the frequency much lower, but clearly that won't be an issue to you.
Thanks so much! I appreciate it
I have try this with 528Mhz, and i can say it's not very good for the battery.
only 528 Mhz - > max. 1 day
with dynamic CPU clock ~ 2 days
I use 528 max 376 min, its pretty good.
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.
Hello, I tried searching but didn't find a thread about this. Sorry if there is one that I didn't find. I'm playing around with SetCPU and trying to figure out optimal settings. I know its a matter of preference but I wanted to see what everyones opinion is and what they have theirs set as. I have:
CheckROM Revo noteHD v5
Abyss Kernel
On Demand governor set
Max 1500MHz
Min 200MHz
I want a happy medium between battery life and performance.
I set a profile for screen off to min 200 and max 500.
I've been reading mixed reviews as to whether or not lower speeds actually increase battery life. I originally had the min at 50 but increased it to 200.
Another question is what would be a good temperature to set the temp profile to? Not sure when the phone begins to get too hot.
Thanks in advance
I used FM kernel with ondemand with min of 500Mhz and max of 1400Mhz with 2nd core always enabled, didnt notice that much of a battery loss.
go for rocket rom v22 with abbys note 4.2 kernel
set cpu min 50 max 800
on demand (if u want both cores active)
abbysnote (if u want single core running and 2nd to be used only if required otherwise 2nd would be off)
i got normal usage batt backup of 3 days least
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.
I'm totally a rookie for modify the kernel, but i wish to get better battery life for my nexus 6. So i read often that changing the CPU Maximal/Minimum Frequency - for example for the franco.kernel or Lean Kernel or other kernel - almost everybody get a better battery life and no wake locks. At the moment i use the nexus 6 stock with no custom software, but the battery life isn't very good.
My questions now: How can i setting the right CPU Maximal/Minimum Frequency for the franco.kernel or Lean Kernel or other Custom Kernel? Are there specific apps? And the most important question: Which are the right numbers to set for the CPU Frequency?
Thanks. :good:
Erdiou said:
I'm totally a rookie for modify the kernel, but i wish to get better battery life for my nexus 6. So i read often that changing the CPU Maximal/Minimum Frequency - for example for the franco.kernel or Lean Kernel or other kernel - almost everybody get a better battery life and no wake locks. At the moment i use the nexus 6 stock with no custom software, but the battery life isn't very good.
My questions now: How can i setting the right CPU Maximal/Minimum Frequency for the franco.kernel or Lean Kernel or other Custom Kernel? Are there specific apps? And the most important question: Which are the right numbers to set for the CPU Frequency?
Thanks. :good:
Click to expand...
Click to collapse
first off, questions go into the q&a/help threads, not general. and there are many cpu control apps to use, some free, some paid. thats the way for you to setup your cpu anyways you feel like. and there is no such thing as the right numbers, you need to find the right numbets for your use. me, i overclock to 3033mhz, and still see 5.5-6.5 hours of sot.
Thank you!
You shouldn't necessarily change the minimum and maximum frequencies because they won't necessarily save you battery.
When you look at the mex frequency of 2650 MHz, that's how many clock cycles there are per second. 2,650,000.
Every task you do on your phone will complete within an amount of clock cycles. Let's make some things up to illustrate this. Let's pretend that it takes Facebook app 5,000, 000 clock cycles to open. That means it would take nearly 2 seconds. If you set your Mac CPU frequency to half of stock, that app is going to take twice the time to open. The question is, will running running at 1267 MHz for 4 seconds use less energy than 2650 MHz for 2 seconds?
Looking at the voltage table for elementalx, the stock voltages are 890mV and 1110mV so it seems to me that since the voltage for half the max frequency is a lot higher than half the voltage of max frequency, running a task for twice as long would use more energy than max.
Surely, there will be tasks that take significantly fewer cycles than max frequency, so in those instances it may seem a bit more balanced, but its one of those things you're going to have to just try for yourself. Some people seem to get better battery though personally I'm not tempted.
Thank you, too! Now i understand.
Should I flash only the Lean Kernel or franco.Kernel and then look again at the battery life? Is this enough to get a better battery life on my device?
Erdiou said:
Thank you, too! Now i understand.
Should I flash only the Lean Kernel or franco.Kernel and then look again at the battery life? Is this enough to get a better battery life on my device?
Click to expand...
Click to collapse
no. kernels generally wont give you better battery life, but they can help you. battery life is dependent on how you use your device, how you set up your device, what apps you installed and use, your brightness, and the quality of your phone/data connection. and much more other things that weigh in less then these on nattery life.
some apps you install can be badly written, and take lots of battery, even though you rarely use. dropping brightness can increase your battery life. i keep my brightness below 15% usually. if i raise it to 35-40%, ill see a whole hour less screen on time.