Database Develop

Post your SetCPU Profiles

748/245
Temp < 50C 245/245 100
Screen Off 245/245 90
Charging/Full 719/245 80
Battery <40% 604/245 70
All ondemand

Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery <100% 768/245
that's listed by priority

Hungry Man said:
Temp > 42.1 528/245
Screen Off 528/160
Charging/Full 768/768
Battery
Click to expand...
Click to collapse

Screen Off: 245-480
**Stock is 245-245. 160 as a minimum seems to produce a LOT of wait time from when the call is coming in to when the phone lights up. More than 245 seems to whack the battery.
Keep in mind, when you wake up your phone, this Screen Off SetCPU Profile is active for at least a SECOND or two. The problem is that if you have your maximum at 245, you experience BAD lag trying to pull the lock bar down. At 245-480, the maximum is high enough that a) the lock bar pulls down as smoothly as a stock Eris, and b) even if SetCPU takes a couple of seconds to change the profile, at least you're at 480mhz for the first scrolling of the screen left/right (so you don't embarass yourself in front of iphone users). Anything higher than 480mhz is a different voltage. Almost the whole time your phone is 'Screen Off', it will be operating at 245 anyway. So 480 is a good setup for it to jump up when a call comes in (to play the ringtone and show the picture a little faster, and for the lock screen bar to pull down smoothly, and the first second of SenseUI to be smooth enough, until your phone changes the profile to your <100% profile.
Battery <100% 245-806
** Zanfur's take on how this processor clocks up/down its speeds will lend itself to a general wisdom that 768mhz isn't really slower than 806mhz, and that in instances of high variability of clock speed (aka you have some Power Save bias in SetCPU keeping it lower/higher at random, or you're doing very intermittent tasks), the processor rests at 768mhz more quickly, and wastes less time/'effort' changing speeds. Changing to 806 is another 'step' altogether, where 245 to 528 is one 'step', and that to 768 is another 'step'. Going to 806 is absolutely another step yet after that (which means your phone responds a LITTLE slower because it has one more step to 'throttle' up to). BUT, if you're doing a dedicated task, such as running a Linpack benchmark (which is a terrible benchmark anyway) your phone will move faster at 806, or if you're playing a game, or playing a video... generally the processor will stick at one speed (and not have to 'step' up or down), so 806 is faster. I clock friends' phones at 768 to avoid problems, keep it clean, etc etc. Some people put the minimum here at 160mhz, but I feel that this is too low (and another 'step', just like 806 is over 768, 160 is another step down from 245).
Charing (any) 480-806
** I keep the minimum here HIGHER than when the phone is on battery, because I'm less concerned about how much energy it's consuming, and having a minimum of 480 makes the phone very snappy no matter what, from the second you touch it
Overheating > 48C 122-528
** Clock speed here matters a LOT less than just getting your phone out of the heat. This phone doesn't overheat because it's overclocked, it overheats because you run it at an overclocked speed for a long time. MOST overheating instances are from wireless tethering and from broken charging systems (that keep trying to charge the battery and generate a lot of heat). The 'Failsafe' profile here provides a 'notification' option which I HIGHLY recommend.
My ex-gf's Eris actually CAUGHT FIRE, as in it looked like it was a zippo, right above the volume buttons. It used to overheat EVERY NIGHT that it was on the charger, excessively, so hot that you couldn't touch it. For a month or two it did this, actually, and caused no real damage to the phone. Since the night of the Flame (you can actually see the melted plastic and even on the outer case - she has a blue snap shell case on it that is melted as well), the phone has NOT overheated even one time on the charger. (Sorry for the story, it was a waste of time).
The point is that, the first time it happened, her phone System sound was on Silent, and she DIDN'T hear the notification that her phone was overheating. Apparently it doesn't matter (or she's very lucky her phone isn't damaged in terms of its operation!) how much it overheats for some people, but I like to have it warn me it's getting close to 50C. The notification's the important part there (so u can cool your eris), not the clock speed.

@pkopalek I like your settings you posted with a full description of each. I changed my settings to yours and give it a day or so and will report a status update as to performance quality

I've never lagged at 160mhz =p but that could just be my phones/ roms.

Hungry Man said:
I've never lagged at 160mhz =p but that could just be my phones/ roms.
Click to expand...
Click to collapse
my audio skips and it won't wake up when in a call at 160mhz. I keep mine at 245mhz minimum to keep phone working smoothly.

What does the different prioritys mean? Is that like what one its.focused on more?
Sent from my FroShedYo.V5 using XDA App

How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo

sgbenton said:
How do you guys clock your CPU so high? Whenever I try anything over 729 bad stuff happens. If I put it on 748 it lags and if i try 768 it freezes up. You guys are all using the droid eris right? What ROMs and kernels are you running? I'm on Kaosfroyo
Click to expand...
Click to collapse
When a processor is made at the factory, it will always have flaws in it. The chip is tested to see what frequency it is stable at. So that is the speed that is stamped on the chip and the frequency that it is set at to operate for the consumer and not have any problems. When you overclock a processor, you are bypassing the frequency that the chip as been deemed to be stable at. After that, there is no set speed that your processor can handle, because each one is different according to the flaws it might have.
So in short (what I'm trying to say), the processor in your phone just can't handle those without causing problems. That's why when you overclock it, it's kind of a trial-and-error process to see what speed you can get out of it, but be careful, because too high can cause permanent damage.

Using Interactive governor
Main: 787/710
Temp > 42.1 C: 480/245 Priority: 100
Screen Off: 480/245 Priority: 95
Charging/Full: 480/245 Priority: 90

[Q] dynamic overclocking

.
..

I use setcpu to do this.
Look into the governors, choose one.
Then choose the appropriate thresholds (in the advanced menu) for what you do.
It doesn't allow you to tweak per app, but tells the cpu governor at what %of cpu to move to the next cpu speed (up or down).
I set mine very low, as i care more about battery than performance. So my up threshold is like 95% or something.
But my down threshold is a lot more agressive.
But you do the opposite.
MuF123 said:
Hello,
my question is regarding dynamic overclocking. I've used the ones that raise the speed when under a load - but my question is -
Is there a way to return to stock clocks after certain time?
Explanation:
situation1: I want to check new single mail or open new single IM or check university's website for some news, I want the device to be FAST as possible, nevermind the battery.
situation2: I want to use maps/navigation/IM/games/web browsing for longer period of time (hours?) with the screen on. I don't need all the power when I play solitaire, text on IM or browse not-so-important news websites.
I think when I've seen the realtime clock displayed on my phone it jumped to max clock right after I've clicked almost anything on the screen. I want the speed-up, but after certain period of time to stop doing this in favor of the battery life-time.
Any ideas how to do this? Thanks!
Click to expand...
Click to collapse
Sent from my Milestone using Tapatalk

Yes, just throttle the cpu to give you more power when you are sluggish. That could work for you.
Me? I have my droid do 110 when screen is off (works quite well!), and then I FORCE the unit to 1000 when plugged in. Besides that i throttle the cpu based on battery power: more cpu power with more battery life. Makes my droid last longer.
I might want to add a throttle up when sluggish and not in my personal battery red zone and a throttle down when the cpu gets too hot period.
Any cpu frequencies that you all would suggest?

..

MuF123 said:
Thanks for the reply, but - think about this, I will start a 3D game, it will use 100% of the cpu so it would always stay at the highest possible frequency (+highest voltage). I don't want that.
Click to expand...
Click to collapse
I dont get it?
You dont want max speed in game? Why do you overclock?
If the game requires 100%, the it will (and should) clock up.
As soon as the game doesnt, it will clock down (depends on your threshold).
The only other i could see, is to change the max clock rate in setcpu before you play the game. This will ensure it doesnt clock higher than your choice, but requires a manual step.
But seriously, if your cpu is pegged at 100, why would you not want it to step up the higher speed?
Sent from my Milestone using Tapatalk

..

MuF123 said:
exactly - I don't want minimum battery in game, that's why I don't want to overclock.
actually from the nature of 3d rendering I think every game will run at 100%, but the situation when the game hits the frame limiter (not likely on milestone).
I want snappy performance while doing few quick tasks:
e.g.: new IM comes, I want to unlock, load the application, get to the IM, reply, lock. (40seconds)
or
taking phone from cradle - I want the phone to load homescreen fast, rotate the screen, open phone app, to look at last missed call and call back (20seconds).
Battery life won't be affected by 40 or 20seconds of ~1100mhz, okay.
And then I start a game for a prolonged time. It will run smoothly even on 550MHz, the additional frames I see are just waste of battery = I don't want that.
So now I have two options - either run at max speed and it will be always fast and it will drain my battery when I decide to play for an hour.
OR
I can use default speeds for longer battery life for everything and I will wait an hour to rotate the screen in browser or IM app.
Click to expand...
Click to collapse
You could compromise and find a max speed that you could undervolt to make it drain battery like stock. My 800mhz vsel is less than the default vsel @550. So the battery drain is less...
It requires some trial and error, but most "slight" overclocks (700,800; depends on the phone) can be configured to drain less than stock.
Of course, if you feel you need 1000 or 1100, this wont work as it requires increasing the vsel (or at least not decreasing it).
Sent from my Milestone using Tapatalk

can i turn off s600's cores ?

hello
can someone help me ?
can i turn off s600's cores ?
from 4 to 3 or 2 cores

HTC One doing this automatically. Install CPU-Z You can see in this app activity of your cpu. In daily use most time Htc use 2 cores or 1.

Honestly there is no real reason to do this. Like xnobex said your device does this automatically to save battery. It only uses as much processing power as it needs to so its never at 100% load all the time and if it was it would be killed quick and overheating like crazy. Doing this would only mess up the experience and cause lag, with very little to show when it comes to improved battery life. Your device rarely ever needs to use a lot of processing power unless you're playing games. Your best bet is just to lower clock speed which the power saving mode does already setting it to 1.2 GHz when its normally at 1.7. Personally using custom kernels and under clocking helps my battery life. Also greenify is a life saver.
Sent from my HTC One using Tapatalk 4

[Q] CPU running at high clock most of the time

Updated section:
After clearing cache through recovery and doing a hard reset, the uAh has gone back to 3142000. Standby time seems good with the battery losing 7% overnight. It does charge quite quickly from 0-100 in about 2h. The previous heating issue remains with cpu monitors showing that the cpu jumps to high clock when I touch the screen. I don't see any change in which apps use the most battery with the screen taking up the most as before the problem started.
The heat appears to be what is draining the battery but I can't find any single app that causes it to ramp to max.
Pictures:
No-frills is set to stock settings to see how the phone handles the actions
2nd picture is when phone is idle
3rd picture is immediately after swiping through a few tabs and scrolling through some pages in the app which causes cpu clock and load to increase
Old sectionFor when battery uAh was low)
I've had this Z1 for about 11 months. I can only get around 2.5h on screen time with regular usage. The battery uAh was only 1848000 Recently it fell to the 1700s. Calibration appears to reduce the value further. The phone seems to heat up in about a minute or two no matter what app is running.
The phone is rooted on stock 4.4.2
I have tried updating to Lollipop before but received an error due to rooting, so I don't think anything changed.

bump

alantay11 said:
bump
Click to expand...
Click to collapse
sounds like it's time for you to replace your battery.

You may try to disable the "input boost frequency"
By default when you toch the screen, cpu frequency of two cores instantly jumps to around 1400 to preventing any lag but it seems to use more power and causing heat
I have disables this and since then I'm no longer have any heat issue and also the battery life is so much better now but you may exprience a little lag while scrolling on heavy web pages but thats all
Btw i'm on .157 and using Kernel Adiutor for cpu tweaks
You may disable this by the app mentioned above or by editing sys.somc.touch_perf_kick=1 from 1 to 0 in buid.prop or adding this line

Underclock CPU? [Snapdragon 660, MIUI 10]

Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.

daokris said:
Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.
Click to expand...
Click to collapse
Hello. It is normal for the processor to operate at its normal frequency while the phone is idle. There are plenty of processes in the background. If you have root rights, then you can download an application like (l speed) through this application, I put my battery my processor and the data in the background that allows me a loss of only 1% over a period from 10 am

If I'm not mistaken, your processor cores should go into deep sleep state when you turn your screen off. If they stay on 633/1113 then something is probably keeping the phone awake and battery is going to suck.
Download Dev Check to see how long the cores stay on certain frequencies. If you leave your screen off for most of the time, then most of the graph should show "Deep Sleep" instead of any other frequency.