[Q] Do I Need SetCPU with DamageControl? - Hero CDMA Q&A, Help & Troubleshooting

Hi all, I'm AWOL from the EVO forum while I get my wife's Hero set up.
I just loaded up DC 2.09 (latest / final release) and I'm working through SetCPU, but I saw one user at least who said DC automatically scales the CPU all by itself. So do I need SetCPU to get some battery benefits? The phone is screen-off a lot, mostly used for just calls, texts, and camera other than that, so if it will kick down to 245 automatically, that should save a lot of watts.
So do I need SetCPU, or will DC underclock out-of-the-box?
(Edit: I guess SetCPU gives me the OVERclock, doesn't it? Still, I'd like to know about DC's background so I know how to set up profiles, or even if I should.)

I haven't used DC in a while, but I'm fairly certain it doesn't come with the ability to underclock by default....I'm pretty sure it comes with a stock or very-similar-to-stock kernel that wouldn't have any different cpu speed settings. I could be wrong but nothing in the main OP of his post (here: http://forum.xda-developers.com/showthread.php?t=656690) suggests otherwise. That ability might be available in the DConfig settings somewhere, but I haven't used/seen it in a couple months to remember. Check there first.
If you don't see anything, you probably will want to use SetCPU or the OC widget to scale down. I'd also recommend using the Screen Off profile in SetCPU, to lower the max speed when the screen is off. Sounds like it would be a useful one for you.
This may not work with the included kernel, so if you don't see any results try a different kernel built specifically for use with OC/setcpu:
This one: http://forum.xda-developers.com/showthread.php?t=750170
or one of these: http://forum.xda-developers.com/showthread.php?t=705074 for DC.
Hope this helps.

Related

Cpu Scaling

How would i go about changing the cpu speed tht the rom has set it at. Like if cyan's rom is at 528 n i want max to be 328...how would i do tht ? wht file to mod ?
Instead of touching mods, better off using either SetCPU or the Open Overclocker widget, both available on the market or here. Just run a search.
The open overclocker widget in the market is fantastic. On cupcake I have mine set to 128-384 and set to 128 constant when the screen is turned off to conserve power.
Not just to hijack the thread, but AdrianK, at those settings do you find wake up too slow? For example when you get a phone call? I used to do the same as you, now I have it as 245 constant when screen is off and 384-528 when on.
Hey guys i appreciate ur replies but i wanted a way to implement it in the rom itself so i dont have to run a widget...thnx though..
SetCPU isn't a widget, its an app that you only need to run once and that's it. However I'm not sure if SetCPU also allows you to set the screen off frequency though which saves you even more battery life.
As for editing the ROM yourself to set the CPU speed, I can't help you there I'm afraid. Not sure if it has been posted on the forum or not too but try a search.
NeoBlade said:
SetCPU isn't a widget, its an app that you only need to run once and that's it. However I'm not sure if SetCPU also allows you to set the screen off frequency though which saves you even more battery life.
As for editing the ROM yourself to set the CPU speed, I can't help you there I'm afraid. Not sure if it has been posted on the forum or not too but try a search.
Click to expand...
Click to collapse
Yes, SetCPU will allow you to have a screen off profile so you can set the speed while the screen is off, and when it is on. It does need to run in the background tho I think...

Question Regarding CPU Scaling

So I'm new to phone hacking, but an experienced software developer with a pretty strong Linux background... Anyway, I was rooting around the filesystem and found /sys/devices/system/cpu/cpu0/cpufreq/
I checked the values in scaling_max_freq and scaling_min_freq and they were both set to 528000. After doing some forum searching I see that some people mention using setCPU to let their CPU throttle down to 245 MHz when the screen is off, but when I tried to do echo 245000 > scaling_min_freq it doesn't ever change from 528000
I'm using Fresh 1.1, do I need to install a different kernel if I want my CPU to scale, and why can't I edit this file manually? I assumed that all setCPU was doing was editing /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and scaling_max_freq and scaling_min_freq
ASULutzy said:
So I'm new to phone hacking, but an experienced software developer with a pretty strong Linux background... Anyway, I was rooting around the filesystem and found /sys/devices/system/cpu/cpu0/cpufreq/
I checked the values in scaling_max_freq and scaling_min_freq and they were both set to 528000. After doing some forum searching I see that some people mention using setCPU to let their CPU throttle down to 245 MHz when the screen is off, but when I tried to do echo 245000 > scaling_min_freq it doesn't ever change from 528000
I'm using Fresh 1.1, do I need to install a different kernel if I want my CPU to scale, and why can't I edit this file manually? I assumed that all setCPU was doing was editing /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor and scaling_max_freq and scaling_min_freq
Click to expand...
Click to collapse
I dont know alot about linux or the kernel stuff but I do know that those of us that have been using SetCPU to adjust freqency have been installing a seperate kernel. Its Gumbo Kernel. Ill get you a link.
Gumbo Kernel
http://forum.xda-developers.com/showpost.php?p=5502421
Looks like there's a script in there that fiddles with the memory freer and sets the scaling_governor to performance instead of ondemand or msm7k.
Changes /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144
to 1536,3072,4096,21000,23000,25000 that's interesting.
edit: I'm not sure how useful that really is. Memory that isn't storing anything isn't doing anything, and so while it might make you feel better to say "Look! I have 90 mb free!" that really isn't as great as you'd think. If you run low on memory (ie the active process is needing more), then it's already going to kill and free up empty apps and content providers with no clients attached, so not really sure how useful that particular part really is.
edit2: So returning to my original question. If I want to change how low my CPU will scale down to, I need to install a new kernel?
ASULutzy said:
Looks like there's a script in there that fiddles with the memory freer and sets the scaling_governor to performance instead of ondemand or msm7k.
Changes /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,5632,6144
to 1536,3072,4096,21000,23000,25000 that's interesting.
edit: I'm not sure how useful that really is. Memory that isn't storing anything isn't doing anything, and so while it might make you feel better to say "Look! I have 90 mb free!" that really isn't as great as you'd think. If you run low on memory (ie the active process is needing more), then it's already going to kill and free up empty apps and content providers with no clients attached, so not really sure how useful that particular part really is.
edit2: So returning to my original question. If I want to change how low my CPU will scale down to, I need to install a new kernel?
Click to expand...
Click to collapse
Yes. Try the gumbo kernel. try scaling it to 160 just for fun. You'll see how slow it is, and it will prove that the cpu scaling works. try it at 528 also.

Speed up your Nook Color running ICS+

Hello all, today I will be showing you how to speed up your Nook Color a bit... these methods should work for CM9/CM10/CM10.1/Paranoid Android/etc., but I personally found these out while running PA ICS. The apps you may need to make your phone faster are Ram Manager (Free OR Pro) and No Frills CPU Control (In the case that your ROM doesn't have overclocking in settings). Basically, using these "tweaks" (minus overclock, as whenever I flash a ROM the first thing I do is overclock it), I went from a painfully slow (as in, I was ready to go back to Gingerbread) device to a somewhat faster device. I've seen huge differences in launching games and apps especially, and opening to app drawer seems to be smoother also.
CPU Overclock
Either using No Frills CPU Control or the built-in overclock, set your max CPU speed to the highest on the list (not exceeding 1200, but it shouldn't show anything above that anyhow). Change your governor to either Ondemand or Performance (I personally use Ondemand and have no problems with it). Most of you are probably already overclocked though, so please don't look at me like I'm stupid.
Swap Space
Open up RAM Manager and there should be an option to change your swap space at the bottom. I changed mine to about 48 and am content with that, although I must add it may make your SD card's life shorter. This will increase your RAM, thus allowing you to have more apps open at once.
Force GPU rendering
Open Developer Options in your settings app and check "Force GPU Rendering"... I'm guessing this is one of the biggest factors to my tablet becoming smoother, as from research it helps lower end devices achieve a better framerate, although it may decrease your battery life. Also, I cannot guarantee every app will run great with this. I tested a game (Dynamite Jack) with this setting enabled and it wasn't too shabby at all! But yes, I can definitely see a difference in the overall speed of my Nook Color.
Please tell me how these work for you
I tried these settings, but unfortunately didn't perceive any performance improvement.
Good call on RAM manager. Hadn't seen that before, its going on my NC and RAZR now
Can anyone tell me a good reason for that RAM Manager app to have the permissions it does? Location, Identity, and full network access?
Does NOT work. All this app " no frills CPU" does is provide a GUI front end for the settings already found for our nook color using CM 10+ in its "performace" settings. Also this app does not provide over clocking above our set 1100 MHz. You will need a custom over clocking kernel for the encore for this. Check over on the CM 10 kernel thread n the development section.

[Q] Overclocking/undervolting

I am using the latest Arrrghhhs anykernel along with ROM toolbox pro to underclock my min clock speed to 96MHz and overclock my max clock speed to 1890MHz. Im using ondemand as my cpu governor and row as my i/o scheduler. I have the option to overvolt and undervolt using ROM toolbox as well. I did some searching but cannot find any info specific to the Atrix HD. I was just curious if anyone has tinkered with this much and if so what have you found to be the best clock speeds/governor/scheduler/voltage combination. I've never really heard anything about overvolting, what if any benefits can come from this? Also what is the most you have been able to undervolt with causing a bootloop or other issues? On my old S3 I had a app that would test if your settings were stable by running different processes to put a heavy load on the device. You could run it as long as you wanted but I had learned if it reported no errors after 10 mins it was usually pretty stable at those settings. I cannot remember the name of the program and searching turned up nothing, I was hoping someone knew of it or knew of one that does the same thing. Thanks in advance for any help!

12 Hours of Screen On

AFTER DOING EVERY SINGLE ONE OF THESE INCLUDING THE OPTIONAL ONES YOU'LL GET 12 HOURS OF SCREEN ON TIME
IF YOU EXCLUDE OPTIONAL ONES YOU'LL GET MINIMUM 7+ HOURS OF SCREEN ON TIME
First,obviously, you need a rooted OP3 or OP3T
If your device isn't rooted check this out.
There is several steps to achieve this results,
TAKE A BACKUP
This is the most important. In case you mess something up or this guide doesn't quite work for you, you can always go back to your old setup.
Pick a ROM that works best for you in terms of battery life (I am using this ROM)
Pick a kernel that works well with your requirements and the ROM (I am using Boeffla Kernel)
So the key to achieve the best amount of screen on time is underclocking your CPU and GPU. An average user shouldn't have any problems underclocking but some users that play games or care about benchmarks shouldn't underclock. There is optimal values that I found while messing around in the config app.
After flashing ROMs and kernels don't boot yet! We have more to flash!
Download AKT profiles and flash!
After you've done these you can boot up your OP3/OP3T
Now we have several things to do on the device:
First thing's first, let's tweak the frequencies! The optimal values are around 844 MHz for the little and 1324 MHz for the big CPU and minimum frequencies should be at lowest possible. For the GPU the best value seems to be 401 MHz and again minimum frequency is lowest possible.
Next! Let's set our ROM's battery profile to performance! Wait hold up there wasn't I talking about longer screen on time how is performance profile is going to help? Here is the answer: Since we have already underclocked our CPU and GPU setting this profile to performance will allow things to be used up a little more. And it will make you feel good
Now remember when we flashed AKT Profiles? Now we'll set that to performance.. Oh wait what? Performance again? YES! But we'll pick the most smooth one. Set it to Fusion Performance!
(Optional) Now we have things to do with apps. Download Greenify to hibernate things when you aren't using them. Select apps according to your preferences and hibernate.
(Optional) Now we'll play with some wakelocks. Download a wakelock detector app and monitor the wakelocks. After some amount of time you'll see some useless apps waking your device every now and then. Go to your ROMs wakelock disabled and disable those wakelocks! Show them who is the owner of the phone! (For example you can block The File Manager HD's wakelock since it has no job when screen is off and MX Player's wakelock because again what can a video player app do when you aren't watching anything.)
After this point if you see more lag increase the CPU and GPU frequencies or reduce them if you see no lag and if you want more battery!
This method might not turn out the same for everyone! You might disable some wakelocks that are important for the device and mess up things so be CAREFUL and when hibernating note that all the hibernated apps will stop pushing notifications! So don't hibernate WhatsApp, Messenger etc.
There is a screenshot below as a proof.
I know I've done nothing but writing this but still if you want to donate here it is LOL
*UPDATE*: Blocking the useless wakelocks allow OP3 to survive 24 hours (if you aren't using it at all) only 3G on (no wifi, no GPS ONLY 3G)
what io scheduler and readahead values you use ?
tadessi said:
what io scheduler and readahead values you use ?
Click to expand...
Click to collapse
cfq and 1024 the defaults that came with Boeffla

Categories

Resources