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.
Ok guys I have installed Zeus v7 ROM and you all know there is application called ZeusTweaker which allow me to change CPU frequency. So my question for you is: on which frequency did you set your max and min value, when did you set that frequency and are there any significant improvement that you noticed? Did you noticed any problems? And finally and most important.. is it worth it?
hi, frequency min 300 - max 1300 , undervolted -3, bench OB with antutu before overclock and after for see score.
if you don't play , maybe overclock is not necessary, battery eats more when OB is overclocked
Hi
My s5 default frequency CPU are 300 Min And 2400 max.
I have root. stock rom And kernel. I have Read about clocking And if i increase CPU sped in its Min values The CPU should be more reactive. (i have stock kernel for mantain knox To 0x0 And i don.'t need a overclock up 2400 because 2400 is enought i think..) So, if i have 300 Min And 2400 max which Min value Can i set without problems? 400?652?728?or 883?
Now i have 883.. It' ok for CPU or i should have problems ? I Can set more than 883?if yes what CPU Min frequency could i set?
I have set when The Phone is charging or screen is off or calling The CPU turns To normal values (300 Min 2400 max).
The governor i use is stock interactive scheduler row.
I dov'è care about battery. If The change drop fastly is Not a problem for me. I want The Phone more reactive And responsi possible without problems on the CPU ecc..
Shouldn't have any problems, you might experience a bit more battery drain, that's about it. Sometimes when my screen is on, my phone automatically adjusts to 1190 as min, so I don't think you need to do anything.
Stock kernel, rooted
883 is too Hight or i Can set more? Like 960 or 1036 or 1190?i think more that 1190 is excessive.
In My experience when you open setcpu And do Nothing normally The CPU is 300.when you simply touch The screen it increase To 1190 so The 1190 i think is the minimal value of CPU when you use The Phone for operations. So maybe i think i could be ok if i set 1190.
Upp
I can't use my vr gear for more that 10 minutes before the overheating message appears on the phone.
Has anyone found a fix for this?
I wouldn't do the cooling fan mod on the gear, too much hassle.
On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.
jedisurfer said:
On my note 4 I undervolt and set the cpu governor to 1100mhz max. I believe the VR is more dependent on GPU than CPU so undervolt and limiting the cpu speed keeps it cooler.
Click to expand...
Click to collapse
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!
Rayan said:
Do you mind sharing your voltage and clock settings?
How much additional time you achieve with your setup?
Thanks!
Click to expand...
Click to collapse
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.
jedisurfer said:
I can run it pretty much indefinitely I think, at least an hour. I usually stop every 30 min because my eyes get strained.
I have emotion kernel 21, running rapture rom using synapse to undervolt and underclock. I have the 805 variant so there is core 0, 1, 2, 3. Under hotplug I also disable core 3. It runs perfectly fine and does not jitter even with the cpu set that low and core 3 offline(the 4th core since it starts at core 0)
I run -100mv through all the speed steps (that's the most it will let me undervolt global if I want to go lower I have to manual set it for each speed)
268mhz - 600mv
300mhz - 605mv
345 - 610
422 - 615
499 - 625
576 - 635
652 - 645mv
729 - 655mv
etc each step I usually go up 10mv
1113 - 705mv
1190 - 715
1267 - 725mv
1344 - 745mv
my pvsX
qcom speed2-pvs13-bin-v1 I believe I got lucky with a high pvs13 your undervolts will vary. So please go slowly and don't try -100mv right away. I'd go -20, -40, -60 etc to test stability first. I also run it without the back cover just because I hate my chips heating up too much.
Click to expand...
Click to collapse
Funny I just did the same thing to my a10 7870k rig. Lowered vcore and over clocked gpu. Runs much better those a10s don't need 1.45 volts lol. I'm not sure if I could do that to my s6 tho as I'm nervous to root because of jump program.
Sent from my SM-G920T using Tapatalk
there is a bug in stock lollipop and also in stock mm.
when you restart moto g2, you can see with cpuspy that freq.min is set to 787 mHz and not to 300 mHz(787 mHz is so high)
if you open and close "fotocamera" app this bug disappears( i don't know why) and the freq. min is now set to 300 Mhz. do you have the same bug?
Why do you think 787 is high? It uses the same voltage.
zman01 said:
Why do you think 787 is high? It uses the same voltage.
Click to expand...
Click to collapse
for battery i mean
Doesn't make a difference :
Here an explanation by zakee94 -
From 96MHz to 249.6 MHz -> cpu operates at voltage1
From 300MHz to 787.2 MHz -> cpu operates at voltage2
From 998.4MHz to 1593.6 MHz -> cpu operates at voltage3
where voltage3 > voltage2 > voltage1 .
Hence,
* 96MHz takes up as much current as 787Mhz
Hope it helps.
therefore there isn't differences in term of battery if freq.min is 300 mHz or 787 mHz. ..right?
filip2805 said:
therefore there isn't differences in term of battery if freq.min is 300 mHz or 787 mHz. ..right?
Click to expand...
Click to collapse
Yes
If you have screen on the minimum freq is set to 787 for smoother experience but when you turn off the screen it will be operating @300mHz or it's in deep sleep