Database Info

[APP] LeoCpuSpeed v4, control cpu speed & overclock

As some folks had already discovered by finding some test versions, I've been making an app to control the speed of the CPU. Started out as a test to determine if the "1ghz hack" was genuine or not, and ended up to be able to control cpu speed and to overclock to some degree.
First of all. This app is NO LONGER BEING DEVELOPED. You can use it as-is and at your own risk. And no, I won't make a WP7 version.
Features
- Updates CPU speed every half second (calculated from the processor registered directly! not from some driver)
- Can stress the CPU to show you that it goes up to 998mhz under load (when idle speed is less than 998mhz)
- Disable autoscaling so that you can control the speed yourself
- Select the speed you want by moving the slider or pressing 768/998 presets
- Automatically disable autoscaling and set speed at boot (via menu)
- Overclocking
Notes on auto-apply speed at startup
1) Disable autoscaling
2) Select the cpu speed you want
3) Menu > Apply speed at boot
Notes on overclocking
1) Obviously overclocking is completely at your own risk, as you could harm your device. Luckily, in most cases, your device will just lock up and you'll need to restart your device (remove battery, re-insert and turn on again).
2) The green buttons were the overclock settings that have been succesful 9 out of 10 times. The orange speeds have been succesful like 5 out of 10 times. The red speeds have never worked for me yet.
3) The higher the speed, the more unstable. This is mainly because I don't have a way to increase voltage of the core.
4) Overclocking only works on AC power! When on battery power, the overclock will work but will be undone within 500 milliseconds by the OS. Something within the OS, or a driver, or the radio rom, enforces the proper CPU speed every 500ms.
Notes on battery
I have seen only very very miniscule differences on battery usage when using 998MHz all the time. You really wouldn't notice the difference if it were at 998MHz all the time, or at 768MHz (default). The only thing you _do_ notice, is that it feels snappier.
Try playing a decent movie in TCPMP or coreplayer with autoscaling on, and try again with autoscaling off and at 998mhz. Huge difference. (Note that some ROMs already have autoscaling disabled and will run at 998MHz all the time, like CleanEX. You won't notice a difference there obviously.)
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Versions
v4
- For advanced users only: call LeoAutoCpuSpeed.exe with a custom performance level to set that speed (and disable autoscaling if enabled). So, calling "LeoAutoCpuSpeed 12" will set it to 768MHz. And FYI, 18 = 998MHz.
v3
- Add overclock
- Add auto-apply at startup
v2
- Add speed control by slider
- Enable/disable autoscaling
v1
- Initial version (only read cpu speed & stress cpu)
Known issues
Q: Current CPU speed reads 4294967 MHz, that's amazing!
A: Read here why that happens. It's at 128MHz or 256MHz when it shows this.
Q: CPU speed is at 921MHz and pressing 998MHz doesn't change it to 998MHz.
A: Click the 768 button, then the 998 button. It'll be at 998MHz now (has to do with the internals of the driver).
Download
HERE

Thank you! Absolutely must have, works brilliantly.

NICE!!!! Thxs for the update....will test...

THX! I'm already using the v2 and it works well. The only thing I would want to know is how the autoscaling is handled. Sometimes it just stays at 998 MHz and there is no autoscaling(of course autoscaling enabled) and sometime it works. Sometimes it even dropped to .294967 MHz(I think this is the funny thing you mentioned in the other thread as it only happened on AC).

thx, thats a great app

Cab does not work. Just downloaded and installled the cab file. it says that the file "Could not find LeoClockLib.dll" And it exits me.

Fixed: I copied the .dll file from V2 into the startmenu folder under windows and then re-installed V3's cab. it works now. werid.

great app... thank you very much!!!!
do you think there will be a way to leave the overclock on in battery mode and not ac only ?
thank you
for all your work

thank you netripper, was waiting for this

Hey Netripper
first of all thx for this great tool.
I have been playing a bit with the new v3,and I found an extrange behaviour,overclock doesnt seem to work even when the HD2 is in AC/ charging,it displays the overclocked speed and quickly reverts back to 998,but if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
i can change on the fly the overclocked speed as long as the stress cpu is going on, so its prettty pointless at this stage, but im wondering, either LeoCpuspeed gives the wrong speed and does the stress at 998 displaying wrong overclocked speeds or it does indeed work and keeps the overclocked speed at all time as long as the cpu is doing something.
Im using Chucky rom

Thank you for this great program! It would also be great if you could find a way to maintain overclocking on battery power.

Great app.
​

miko3d said:
Hey Netripper
if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
Click to expand...
Click to collapse
I can confirm it. As long as the cpu Stress is activated you can overclock on battery. But stopping it reverts it back to 998MHz. Another thing I noticed, is that as soon as you press the screen, it goes from .4294967 to 768MHz. But if you click with mymobiler, it doesn't change(only when clicking on a button etc.).

miko3d said:
Hey Netripper
first of all thx for this great tool.
I have been playing a bit with the new v3,and I found an extrange behaviour,overclock doesnt seem to work even when the HD2 is in AC/ charging,it displays the overclocked speed and quickly reverts back to 998,but if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
i can change on the fly the overclocked speed as long as the stress cpu is going on, so its prettty pointless at this stage, but im wondering, either LeoCpuspeed gives the wrong speed and does the stress at 998 displaying wrong overclocked speeds or it does indeed work and keeps the overclocked speed at all time as long as the cpu is doing something.
Im using Chucky rom
Click to expand...
Click to collapse
I am using artemis rom and i also noticed this behavior.

Something I noticed:
Freshly hard reset phone, 1.72 base, WM 6.5.
When running at 998 MHZ the taskbar is updating noticably slower. Just tested a few times to make sure. When pressing the startbutton, showing the start menu, and closing it with the X-button in the corner, the taskbar icons update. With 998mhz, this takes a few moments longer, resulting in a small stutter (pretty much the same as with the weather update). With scaling off and running at 768mhz, the update is definitely faster and stuttering is pretty much gone (as used to).
anyone can check with their device?

Working great, auto-apply at startup was the only thing I was missing in V2. Thanks for a great app.

very nice release! works very well, and loving the new features. thank you!

lemonspeakers said:
Fixed: I copied the .dll file from V2 into the startmenu folder under windows and then re-installed V3's cab. it works now. werid.
Click to expand...
Click to collapse
Glad it works now, but it sounds really weird. You shouldn't need a dll in \windows\startup, only a shortcut (if auto-apply is enabled) to the leoautocpuspeed.exe. The app creates this shortcut when you enable auto-apply. Maybe it conflicted with someleft-overs you had from v2? Dunno otherwise.
radiohead7778580 said:
do you think there will be a way to leave the overclock on in battery mode and not ac only ?
Click to expand...
Click to collapse
I've been trying to figure it out for a while. Also tried patching coredll but I can't find the correct function to patch.
miko3d said:
I have been playing a bit with the new v3,and I found an extrange behaviour,overclock doesnt seem to work even when the HD2 is in AC/ charging,it displays the overclocked speed and quickly reverts back to 998,but if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
i can change on the fly the overclocked speed as long as the stress cpu is going on, so its prettty pointless at this stage, but im wondering, either LeoCpuspeed gives the wrong speed and does the stress at 998 displaying wrong overclocked speeds or it does indeed work and keeps the overclocked speed at all time as long as the cpu is doing something.
Click to expand...
Click to collapse
Thanks for that observation. That's a nice find. First of all it's weird you cannot overclock on AC the normal way, but it sounds related to the same problem on battery. It's weird that the device stays overclocked when under load. But it might help me localize where to look to fix this.
chalid said:
When running at 998 MHZ the taskbar is updating noticably slower. Just tested a few times to make sure. When pressing the startbutton, showing the start menu, and closing it with the X-button in the corner, the taskbar icons update. With 998mhz, this takes a few moments longer, resulting in a small stutter (pretty much the same as with the weather update). With scaling off and running at 768mhz, the update is definitely faster and stuttering is pretty much gone (as used to).
anyone can check with their device?
Click to expand...
Click to collapse
Are you sure you just disabled autoscaling, and did not press "start test"? To be absolutely sure, start the app, disable autoscaling, set it to 998mz, and press "exit" (the app does not need to keep running). If you still notice the performance hog, it's really weird.

thanks for the fast reply netripper!
continue your great work

I like this tool but now I love.
thanks a lot.

NSTools and SetCPU Set on Boot

If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2

why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor

Jamin13 said:
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.

i guess setcpu makes it easier to change cpu frequencies quickly through the widget, ns tools doeesnt have a widget so its "harder"

qtwrk said:
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Click to expand...
Click to collapse
SetCPU won't control the Backlight Notifications and Dimmer.
Harbb said:
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
Click to expand...
Click to collapse
I'm just a bit OCD about battery life some days. I'd rather use the app than making my own scripts. I kinda derped with the profiles earlier today. All is good now.

I wish the two would play better together too - and I don't see how "just don't use them both" or saying SetCPU is no longer needed is acceptable answers. Especially since many of us actually paid for SetCPU...
Now that it looks like we'll only get two governors in MathKids kernel (what a crock)... saying you are picking the wrong one is a bad answer too. Ondemand certainly isn't the best for battery life, and for those of us who have tested and measured battery life we know just picking one isn't a solution either.
So what is the actual answer? Because setting the governor parameters at boot isn't the problem. It's switching between profiles - and the governors that give you the best battery life and giving acceptable performance need to be tweaked from their defaults.
With OnDemand I'm looking at using over 16% battery per hour under 4.1, even with considerable screen off time. Not being able to set it to Wheatley on screen off is killing the battery.
I will say the problem seems to lay directly with SetCPU and I'm going to contact the dev and see what I can find out. I don't see why it should be changing the parameters back to default on profile change.
But people who use neither or just one probably just not comment. Not to flame, or fight, but it's not helpful to add nothing.

Looking for a truly wise governor

Hi,
I have Xperia Neo V, GB 2.3.4, rooted, NightElf 10, codename_ei8ght, OC: 245-1400 MHz. Usually I use SmartassV2 + SIO (I don't know why SIO - I've been told to choose this one, so I did). I've also briefly tested many other governors, but to tell the truth, I don't see much real-life difference between them (apart from the CPU Spy logs).
The problem that bothers me is that I need to manually change the OC settings, each time I want to use an app or a game that don't need 1400 MHz. For example - when I want to play AngryBirds. The game works perfectly on 1000 MHz, so why waste the battery power and generate lots of heat? But any governor I know, will "give" 1400 MHz to this game. That's why I need to switch down manually before playing. The same thing with many other apps, like, for example - navigation. It's absolutely enough to navigate on 1000 MHz, but any governor will set the CPU to 1400 MHz when Navigation is running.
Looking for a truly wise governor, that would give as much MHz as needed for an app/game to run smoothly, but not more. Is such a governor even possible to create?
Thank you.

illinoi for
from my observation SmartAssV2 tends to change frequency too much: up, down, up, down. As I mostly want to get best battery life I decided to switch to Conservative - the phone is still responsive (i can't notice difference) but when I dont do anything seems to keep the frequency lower.
I still have problem what governor to choose for sleep state - now im testing PowerSave (so it keeps minimal frequence) so far seems to work (even worked while playing music).
IMO writing too complicated governors could only slow down the system, so it is hard task to decide in real time which frequency is still sufficient for smooth play and at the same time as low as possible.

Do all governors have "deep sleep" mode? Is it governor-dependent at all?
I have some problems with refreshing news widget - I discovered that it is never refreshed in deep sleep mode.
Can I disable deep sleep mode?
Thanks.

[APP] Battery Saver [FEATURED ON BEST APPS OF 2012 ON XDA]

I found this on the xda top apps of 2012...a battery saver ...will try and revert back...for thise who want to try:
http://forum.xda-developers.com/showthread.php?t=1947559
For those too lazy to go to the link [some people like me ]
One Power Guard is a unique battery enhancement tool designed to conserve your battery power an increase uptime on rooted Android smartphones/tablets. One Power Guard will decrease your charging time and increase your device performance while also increasing your uptime. One Power Guard will also protect your device from faulty applications that can: cause over-heating (decreasing your battery lifespan); run down your battery; prevent your device from deep-sleeping; and, use unneeded resources such as WiFi and Cell Data. By selecting any one of the six customized power-saving modes, you are able to match your power savings needs to your lifestyle. There is no need to purchase extra batterys or a larger battery, just use One Power Guard.
Features
1. Extends stand-by time and battery life; optimizes charging parameters
2. Optimizes system kernel and CPU usage to improve device performance
3. Six (6) customized power-saving modes to suit different scenarios
4. Proactively guards from power-killer apps and safely shuts down useless power-consuming programs
5. Fast ON/OFF settings for 100% system customization
6. Intelligently switches to/from WiFi/Cell data to preserve battery life
7. Professional Tips on power optimization
AI Mode: Artificial Intelligence Mode. Learns from how you use your device.
By default, this mode uses the Ondemand governor - under increasing system load, the CPU is immediately set to the maximum frequency of the kernel. As system load decreases, the CPU frequency slowly decreases to the minimum frequency of the kernel.
NOTE: If your kernel supports over/under clocking you may want to change the upper/lower frequency bounds to stay within safe limits.
By default, AI Mode uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices. Changing the governor and the I/O scheduler are permitted but, that defeats the benefits of the AI mode. Use Custom mode, if you want to explore different settings.
Powersave Mode: A balance between device usage and power saving.
By default, this mode uses the Powersave governor - keeps the CPU frequency always at the minimum, it is the least power-hungry and the least responsive.
By default, this modes uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Game/Video Mode: Useful mode for playing games and watching video - enjoy smooth operation and a smooth video experience.
By default, uses the Performance governor - sets the min. frequency as max. frequency, this mode is the most power-hungry, but is also the most responsive. If your kernel support overclocking you can set a higher frequency.
By default, this mode uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Daily Mode: Useful for day-to-day operation, featuring responsive and reasonable power usage.
By default, this mode uses the Ondemand governor - under increasing system load, the CPU is immediately set to the maximum frequency of the kernel. As system load decreases, the CPU frequency slowly decreases to the minimum frequency of the kernel.
NOTE: If your kernel supports over/under clocking you may want to change the upper/lower frequency bounds to stay within safe limits.
By default, this mode uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Standby Mode: Useful for maximum battery conservation.
By default, this mode uses the Powersave governor - keeps the CPU frequency always at the minimum, it is the least power-hungry and the least responsive.
By default, this modes uses the CFQ (Completely Fair Queuing) I/O scheduler - delivers balanced performance and excels on multi-processor devices.
Custom Mode: You choose everything: the governor, the min and max frequencies, and the I/O scheduler. Do a Nandroid backup first. Have Fun!
Test One Power Guard for yourself?
1. Fully charge your battery before you go to bed. In the morning, check your battery status and note how much is remaining.
2. After installing One Power Guard, fully charge the battery before you go to bed. In the morning, check your battery status, you will be impressed by the power savings!
3. To compare the optimization results, you need to restart the phone so that you have a clean environment.
First of all, what are the common complaints with android smartphone devices? Issues such as: system halted; application crashes; slow booting; and, battery life.
A year ago, I purchased my first android phone and installed CM ROM. Within months, I became very
annoyed that my battery did not last the entire day. I could go to bed, with a full battery charge, and awake in the morning to find that the battery charge had dropped significantly overnight. I found this situation to be unacceptable! To solve this, I downloaded power-saving applications.
Every day I would install a different power saving application, charge the battery to full power before bed, and then check the battery in the morning. After a month of testing power saving applications, I didn't find a satisfactory solution and some of the so-called power saving apps even made the battery drain faster. So, I thought I would create an app for myself, that could tweak system parameters and help save my battery. Nine months ago, I started writing a power tweaking application for myself. I studied the intracies of the android power management mechanism and within a few months I had the basis for an application that could optimize my power management. Everyday, I tweaked the power optimization parameters and tested each night. One morning, I awoke and was thrilled to discover that the battery charge had only decreased by a small amount. So, I turned my personal power saving tweaker into a user-friendly power saving application that anyone could use. I am sharing my application, One Power Guard with you.
If you would like to try One Power Guard, Download from onexuan.com
To save power, One Power Guard do some optimization:
1. Extends stand-by time and battery life; optimizes charging parameters
2. Optimizes system kernel and CPU usage to improve device performance
3. Six (6) customized power-saving modes to suit different scenarios
4. Proactively guards from power-killer apps and safely shuts down useless power-consuming programs
5. Fast ON/OFF settings for 100% system customization
6. Intelligently switches to/from WiFi/Cell data to preserve battery life
7. Professional Tips on power optimization
Why do you need One Power Guard? and Test One Power Guard for yourself.
1. Fully charge your battery before you go to bed. In the morning, check your battery status and note how much is remaining.
2. After installing One Power Guard, fully charge the battery before you go to bed. In the morning, check your battery status, you will be impressed by the power savings!
3. To compare the optimization results, you need to restart the phone so that you have a clean environment.
Why does it run in the background?
We have a "safe clean" technology, primarily in order to protect your battery. Needs to run in the background, to periodically safe clean.
What is a safe clean?
Android has a app process management mechanisms, when a process is killed by third-part applications, the android system will determine whether the process will be run again, if it is, th e process will run, the kill process will repeat thereby creating an infinite loop, resulting in increased power consumption. Therefore, you should consider uninstalling third-party process management software.
Why is my device slow after setting a mode?
I want to talk about this story. One night, a user contacted me about an issue that came up after installing the 2.1 version of One Power Guard. He said his device lagged in Standby mode. I told him that we can work together to solve his problem. After work, I went back to my dorm. I started to write a test interface for him and 1.5 hours later, we started testing. He began to test my ten-step interface - each step ran well. But the issue was not resolved. I asked him to select AI mode - his device lagged. What we found is that his device did not support changing CPU frequencies. So my judgment was that this was an I/O scheduler issue, it was set to "CFQ". I asked him to try changing his I/O scheduler. (His Rom Only support CFQ and Noop). He changed to "Noop" and the lag went away - issue resolved!
Final conclusion: Tweak the settings until your device performs to your satisfaction.
The software allow the common user to gain the benefits without having to understand the technical stuff thus the 6 modes for common uses like gaming. Any "battery saving program" is truly just a front end to tweaks and settings changes that can be done manually. The point is it makes making those changes much easier.

what about a phone without a root...suggest a nyc baatery saver...in need of it??
Sent from my HTC Wildfire S A510e using xda app-developers app

ajiinkya said:
what about a phone without a root...suggest a nyc baatery saver...in need of it??
Sent from my HTC Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
Try juice defender or ds battery saver both are nice and effective
HIt tHnX iF i hElP u
Sent from my GALAXY RoYaL

i wud try it n feedback u soon
Sent from my HTC Wildfire S A510e using xda app-developers app

it works really well! Improved my backup 5x on 10.1 !!
Definitely use it guys

F3niX said:
it works really well! Improved my backup 5x on 10.1 !!
Definitely use it guys
Click to expand...
Click to collapse
Glad I could help!
Nokia 2110-->Sony Ericsson k750i -->Nokia 5233 --> Samsung Galaxy R

It's really nicest, best battery saver
Thanks buddy
Sent from my GT-I9103 using xda app-developers app

thnks for d link buddy:good:
its really works good.

d2dprajesh said:
It's really nicest, best battery saver
Thanks buddy
Click to expand...
Click to collapse
TUSHARKATE007 said:
thnks for d link buddy:good:
its really works good.
Click to expand...
Click to collapse
Friends can some one please tell me what are the setting's you are using because i haven't seen any improvement ....

mj.vikram said:
Friends can some one please tell me what are the setting's you are using because i haven't seen any improvement ....
Click to expand...
Click to collapse
Neither do I. If you already have set up setCPU profiles to automatically adjust the cpu freq and governors according to diff situations then you don't need this, coz essentially its doing the same thing. For those who have never explored setCPU and don't want to manually do things, this is a good alternative. I've always used a combination of SetCPU and tasker to get the most juice out of my battery. I never rely on "Battery Saving Apps" that keep running in the background. Just my opinion.

This app really save's your battery life and here is the proof!!https://www.dropbox.com/s/tk7tx9yi19i5jra/Screenshot_2013-01-21-19-29-38.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
I am using standby mode and 54hrs have completed with out a charge and still 60% is left..
---------- Post added at 08:42 PM ---------- Previous post was at 08:40 PM ----------
The-Droidster said:
Neither do I. If you already have set up setCPU profiles to automatically adjust the cpu freq and governors according to diff situations then you don't need this, coz essentially its doing the same thing. For those who have never explored setCPU and don't want to manually do things, this is a good alternative. I've always used a combination of SetCPU and tasker to get the most juice out of my battery. I never rely on "Battery Saving Apps" that keep running in the background. Just my opinion.
Click to expand...
Click to collapse
[/COLOR]I am using standby mode and 54hrs have completed with out a charge and still 60% is left..

Hi, thanks for this info about your personal battery journey Its super cool. I gots 2 questions,
1. What if a user like me doesn't know what kernel I gots and don't want to damage the phones anything, so I have not a clue about setting to prevent over clocking (never cared about it anyways) should a basic user like myself stay away from this application, if it could damage it somehow?
2. If I want to keep my cell from going into deep sleep because then my tethering application automatically turns off, and no way to stops that. Does this application have the reverse ability to prevent it rather then prevent from preventing it. (You know what I am saying)

CM10.1 CPU frequencies not sticking

I'm currently using CM10.1 AOSP [KANG] from the thread here -- http://forum.xda-developers.com/showthread.php?t=2115520. In essence, I cannot raise either the minimum or maximum CPU speeds above 384MHz.
I just tried restoring my phone using a RUU recovery.exe file, then re-rooted, S-OFF'd, unlocked the bootloader and then updated the firmware. Right after flashing CM10.1, I am still having issues with changing the CPU speed. The maximum and minimum CPU speeds I can choose are either 192MHz or 384MHz. I can go into settings > performance then change the maximum CPU speed to anything higher than that, but almost instantly after I select it the maximum CPU speed drops back down to 384 MHz. The same goes for trying to raise the minimum CPU speed above 384MHz. It makes the phone nearly unusable, as it takes multiple seconds to open almost any application and also reboots randomly quite often. Is there any way I can fix this?
Thanks!

Anyone have ideas/insight? Sorry to bump this!

Right. Here's what I did last time. I used something called SetCPU. Ticked the Set On Boot then it worked. But I unticked the ones in the Performance option.
This is what I do. Hope I help.

if you want do this also
go to system>etc>init.qcom.post_boot.sh and put this line(you can edit with simple text editor)
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
do the same for cpu1 if you want to have the same frequency in both cpu