Database Users

nueDynamicClock experiences? (Over-/Underclocking)

I've found this neat tool: http://www.nuerom.com/BlogEngine/page/nueDynamicClock.aspx
Has anyone used this on their X1 and did you notice any changes? I don't think you can use it for overclocking an X1. But I'm thinking about setting clock frequency to 19 MHz on Suspend, to get more out of my battery.

I've got this tool, not sure if it made much of a diff when I overclocked it to 528
( or just set it to the base clock speed since they have it underclocked @ 400 mhz ), wanna try the lower speeds, but not sure whether it will have a negative effect.

I uninstalled it..
found that any apps (such as gps cycle computer, audiomanager etc) that played with the screen on didn't work very well when the speed was lowered. Also had quite a lot of instances when the screen was corrupted after coming out of suspend..

I use it since yesterday, so i can't say anything about changed battery lifetime. But i got it working only after setting min-clock to 384MHz. With lower settings the phone got frozen in standby mode after a while. I'll try it for a few days for testing a (hopefully) enhanced standby time...
PS: i use 384MHz in suspend mode and after idle time of 5s, didn't change max clock or voltage settings (all to "auto"). Maybe setting idle time to 2s would care more battery life, but i don't know how the cpu will stand changing the clock so much often...

Been using it since v1.0. Seems to have some battery gain (10% over 8 hours better) - set to default 528MHz, down to 256MHz idle and 122.98MHz on suspend and screen off. Needed 123MHz for clean audio playback in standby.
Only screen corruption (inversion) issues I had was when set too low (19MHz) at standby. Now using these settings for a few days and no issues so recommended for use with TFlo3D2.
Unless you're running WM6.5 with WM7 titanium - makes it very slow to respond out of standby.
And it doesn't overclock - 528MHz is default clock speed.

I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?

Mark A Cilenti said:
I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?
Click to expand...
Click to collapse
I have a standard R2A ROM and it works for me. Can't tell you what's the problem with your installation, though.
Anyway, I found since I installed the tool my device is worse than before. It sometimes interrupts audio playback when display is off (ALthough frequency in that case is still at 3xx MHz!) and sometimes it takes very long (5 secs +) to suspend and to wake up again. So I think I'm gonna remove it.

I only turned down the voltage to 1.1 instead of 1.325 running on 528MHz.

We can now overclock our phones!

Couldn't really see any discussion on this yet, and personally it's in a location on the forum that I rarely visit but I've found an overclock tool that is slowly becoming very good indeed for our processors. Link to thread is here. I'm soo far up from 528Mhz to 748Mhz (been stable for the past 6 hours no problem). Just make sure to follow the thread (instructions are linked to ensure overclock remains applied through scripts and 3rd party apps). Should take no longer than 30mins for a well versed user to set up. Please don't try this if you haven't got a clue what you are doing as there is soo much scope for error and dead phones! You may also need to customise any scripts to your specific phone/software build. CDMA phones as usual are different from what I've heard. But anyway good luck, I'm gonna keep trying to push the Mhz up (aiming for 850Mhz ).

Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.

It's actually remained pretty cool, and when it's in my pocket it's only running at stock clocks anyway. Only when I'm using it does it get to the full 748Mhz. Running wifi router and charger and temps are not noticeably hotter than usual...

um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
recommendations: Download v1, not v2. ESP if you dont know what you're doing. Then download the zip im attaching, there's 2 mortscripts in there and a registry addition, THESE MUST BE IN THE STORAGE CARD ROOT. use the regisitry addition FIRST (just associate w/e regedit software you use, then run the .reg file in total commander), then go back to total commander, edit the .mscr "Toggle_boost" and adjust the value boost = "x" to whatever value you want the phone to OC at, eg boost = 41 is 787mhz which is stable for me, test yours out.
THEN, open and install rhodiumkbdcontrol (attached), reboot, go to settings>system>keyboard config> add key
1st pick which key you want to be the OC boost swtich, I have it mapped to my PTT button. click the plus sign, drop down menu, run program, then highlight "run program" in the list then click "..." then type in
Program: \windows\mortscript.exe
Arguments: "\storage card\toggle_boost.mscr"
This time you wanna use the power key.
same general instructions except
Program: \windows\mortscript.exe
Arguments: "\storage card\boost_off.mscr"
then plus sign again, drop down menu, default key action, and click extended emulation. THEN hit update config. should work like a charm, also autoover clocks to 610, the boost button with send you up the w/e the boost = "x" is set to, and then back again, most find 710mhz to be the stable point, and feel free to ask questions

sorry, heres the zips

wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs

I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!

miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Edit:
I just read threw the above links and guides and was wondering if there is a more automated way of setting this up rather than having to link it to a button press. I'm guessing this has not been figured out yet (or the guides would have mention of it ). Just curious.

dantegl36 said:
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Click to expand...
Click to collapse
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627

Check it!
Outlaw78a said:
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
Click to expand...
Click to collapse
I have used this, NRG also does. I have NEVER had any problems and mine is as high as 787 as long as I'm running it which is constantly.
XITruthiX said:
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
Click to expand...
Click to collapse
100% agreed. Been running at the highest speeds with NO problems, no batt drain, no heat probs, nothing.
XERO_Racer said:
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
Click to expand...
Click to collapse
Not unless you are having excessive heat problems. Since there are basically no people reporting these problems, I wouldn't worry.
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Once again as stated earlier, 100% agreed.

Do I have to keep plugged in?

miked79928 said:
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Click to expand...
Click to collapse
I thank you for this, but I'm not sure how to implement it. I have installed Mortscript, I've copied the code into a file I called overclock.mscr and modified the code reflect the reg values on my Tilt 2. and I've placed the script on the root on my SD card. I've installed MSM7kCpuSpeed on to my SD card. How do I make the script run automatically?
Thank you!

I take no responsibility for w/e happens to your phone with this advice.
Try putting a pointer in your start up to the over clocking script. Its highly unstable and could brick your phone or require a hard reset... thats why I do it with a toggle switch, i dont mind manually applying the OC with a hard key knowing its safe, esp because the situations where I actually NEED 787mhz are less common than needing to just wake the phone to answer a call or make a txt message.

I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution

dirtypiratehooker said:
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
Click to expand...
Click to collapse
Just a note, I'm not sure the insurance would cover burning a custom ROM into the phone, or overclocking the CPU. And if the chip is fried you can't burn the stock ROM back in. But then, they probably couldn't figure out it was updated without in stalling a new CPU. Umm, it would probably work.

Would a .cab for this ever be conceivable?

At this point, we have finally got a script that will work for most Rhodiums, Topaz (Diamond 2), and a few guys with other phones seem to be having good luck.
The device has to have Mortscript installed, and nettrip's MSM7 v2.
It is a single script solution that requires no pre checks in the registry, no key/button assignment, and you can change the speed settings from the script instead of the registry.
It throttles the OC up and down for calls, lock, and sleep, to avoid freezing on wake up and in a call. Some problems that still need to worked out by nettrip in the script. I don't envy him the work as the script(s) were bad enough. Four of us have hit that original script (by jpc) from about page 13.
You copy the script to the SD or the device root, create a shortcut to the file, copy the shortcut to Windows\Startup directory, reset/reboot the device and you are off.
You can use the MSM7 app to read the OC, but you should make sure to exit the app before sleep, lock, or power off, as it will error on reboot if left open.
To be honest, you never have to open the MSM7 app, as the script controls it in the background.
I believe the script is set for a low over clock. 691. My experience has been a 710 average, but a lot get a stable OC at 750+. I am running 748 and I think I will stop there. A 200MHz overclock will just have to do.The phone does not get hot, though with intense use, it does get warmer. Never warmer than when the battery is charging, tho.
I am running the nrg Sense Reference ROM, 23xxx based on Sense 2.5. I added the CHT 1.8x and the editor to save a few MHz, no biggy.
The overclock allows the Sense to work MUCH smoother, actually noticeable as even the weather animation is smooth.
And all the vid players seem to work better.
I have noticed NO extra battery drain than usual.
The script is only a stop gap measure until nettrip finishes his app, but it does work well with little effort. WAAAAY better now than even last week.
However, use the script at your own risk, as you can get too Medieval on the OC. Some guys are running 800+, more nerve than I have.
Anyway, if interested in the script or want to read some more about the app, you can start here
http://forum.xda-developers.com/showthread.php?t=725290&page=89
post #882 has the script.
Plenty of instructions on how to use (and make changes to the settings) in the last 30-40 pages.

Sorry if this is already explained, but can someone tell me in simple details how to keep my overclock at 729mhz even after screen lock or sleep mode? I've tried to follow previous posts but it keeps reverting back to 528mhz after locking and sleep.

Ok so this seems legitamite,everyones checking in with no problems.
other than the increased risk factor that always accompanys speed,
it seems our ppc's cpu was underclocked beforehand ?
i will try this and see if i get a gpu boost as well.
but ivr already experienced my phone overheating to the point
of shutting itself down,and the god-damned orange light is permenantly on...

You want better battery life? HERE IT IS!(24HRS moderate USE, still at 60%!!)

Sorry, not sure if this is int he right section but from the 1000+ hours i have used on this forum i decided to create my own post. Battery life on Android seems to be the evil culprit of MANY, i have finally found the BEST combo for battery life.
I have tried about 90% of the radios and android builds out there and this by far is the BEST. FIRST i wanna thank ALL developers, mods, beta testers and commenter's because without you all, this would not be possible(Android on the HD2)
My CURRENT setup(which i will probably leave on forever since its set now)
US Tmobile HD2
- Radio 2.12 (the latest one)
-Rom: Elegencia Rom (GTX version) --> http://forum.xda-developers.com/showthread.php?t=651729 So i dont get the robot voice anymore
- Android Rom ---> ▐HYBRID▐07.09.2010▐warrenb213 CM6 9/6-V1.5a T-Mo US Optimized▐ Kernel:mitchyprima r10▐ RMNET version http://forum.xda-developers.com/showthread.php?t=775150
- Special Settings in Windows Mobile: Turn off Auto backlight in windows mobile, turned of sync, weather, facebook, all that stuff that may secretly be on by default in windows mobile.
- Special settings in Android: Note: i turned OFF Auto sync for GMAIL email( since the FREE app called K-9 mail has MUCH better push email which uses much less battery than gmail's auto sync), no gps(sometimes wireless network location is used), no facebook sync, weather or news sync. You can set to whatever set cpu settings or sync settings you prefer, im just letting you know my configuration, the main thing to FOCUS on is the RADIO, the ROM(s) the Set cpu SCREEN off settings and the task killer settings.
1. Installed Set Cpu (Free to download on xda but i paid for the donate version to support the dev)
2. Set Cpu settings are in the PHOTO BELOW but as a recap
a. Click Autodetect
b. On MAIN tab, i set the max processor speed to about 652800 and the min to 245000, CONSERVATIVE SCALING, click SET ON BOOT
c. on PROFILES TAB, I added THREE profiles bt only ONE is necessary to get better battery life: SCREEN OFF profile, 384 max and 245 min, priority 100! POWERSAVE scaling
d. click on advanced tab, all the settings should be default, mines are
Sampling rate 200000, Upthreshold 80, down thresh 20, Ignore Nice load 0 and Freq Step 5, click APPLY and SET ON BOOT.
I also installed advanced task killer, not sure if it helps but my battery has been great since. Settings on there:
AUTO START checked, Show notification checked, Auto Kill Level: SAFE, AutoKill frequency when SCREEN OFF, Security level HIGH. OF COURSE you will have to put various apps on IGNORE so task killer doesnt kill them when the screen is off, so far i have ignored: App Brain, Advanced Task Killer(MAKE SURE TO PUT THIS ON IGNORE OR ELSE IT WONT WORK BECAUSE IT WILL KILL ITSELF lol), SetCPU, SUPERUSER, Google search, ad free, k9 mail and battery indicator pro.
All on ignore so they dont get killed, and i noticed ALOT of people use task killer but forget to put superuser, setcpu and advanced task killer on the ignore list so they may be getting closed out sometimes, which will make them ineffective for you.
Im in Chicago, my data has got up to about 1.5mb down with this rom, FASTEST speed i got yet! As you can see from the picture, I took my phone Off the wall charger around NOON YESTERDAY, it was on 100%, played word feud all day basically, browsed the web and tweeted, couldn't do much since i worked a 12hours shift but by 10pm when i left the office, i STILL had 88% battery left, used the device more when i got off, played angry birds, texted, tweeted, talked to a few people, fell asleep without charging and got scared that it would be dead, but i wake up at 9am...... STILL 68% i played more games, texted and tweeted, now im at 63% and its going on NOON again, so 24hrs decent amount of phone use and im at 63%, thats CRAZY!
My data is on H and 3g, DOES not turn off when the screen is off, i still get my WordFeud push notifications and K9 mail email PUSH when i get new ones(that also helped ALOT when i turned off the gmail push, and downloaded K9 mail, its FREE, has integrated inbox and is the BEST email app out there that ses the LEAST battery to have TRUE push notifications when people send an email to me.
Hope this helps you all, Give my combo a try, let me know your results, but so far this battery has lasted a full 24 hours and is not even HALF dead with moderate use.
side mentions:
NO BSOD
NO FREEZES
FAST DATA
WIFI TETHER WORKS
USB DATA WORKS
CAMERA WORKS
Every damn thing works lol thats what im trying to say. even if it has minor bugs which i have not seen yet, this setup and speed with battery life is the BEST, i dont even wanna risk something going wrong so i may leave this as my PERMANENT configuration.
*Edit* before you post saying the speed is slow, TRY IT OUT, Try the android ROM i posted with the set cpu settings i posted, and you will SEE for yourself* I tried the same settings on other android roms but they were just not good since battery was bad and data speed was bad so try that SPECIFIC ROM, see how you like it.

Thanks for the detailed info hakeem, I'm in Chicago too so I can use your exact configuration which is awesome.
Are you using PPP or RMNET build?
Which version of Miri rom? GTX/Max/CHT? Did you see Miri released a new Android launch Rom, here http://forum.xda-developers.com/showthread.php?t=778398. Wonder if that would give similar results with a quicker launch and more memory?

well considering you set the cpu to 1/2 what it's capable of, I'm not surprised you're getting longer battery life. At 600 mhz it runs like my Nokia N97; very poorly.
I've tried those settings before (minus the 600 mhz max) and they don't really give me much, if any real savings. I still get about 4 hours of heavy use or 8 hours of moderate. Not great but manageable.
I use Shubcraft 1.5 with 31 aug zImage on chuckydroid rom. It's the only setup that actually works for me. Data is intermittently flaky but it gets me 2000-3000++ kbps.
The only thing I would like to really have fixed is the G sensor and slightly more reliable data.

ounkeo said:
well considering you set the cpu to 1/2 what it's capable of, I'm not surprised you're getting longer battery life. At 600 mhz it runs like my Nokia N97; very poorly.
I've tried those settings before (minus the 600 mhz max) and they don't really give me much, if any real savings. I still get about 4 hours of heavy use or 8 hours of moderate. Not great but manageable.
I use Shubcraft 1.5 with 31 aug zImage on chuckydroid rom. It's the only setup that actually works for me. Data is intermittently flaky but it gets me 2000-3000++ kbps.
The only thing I would like to really have fixed is the G sensor and slightly more reliable data.
Click to expand...
Click to collapse
Try HyperDroid, Pongster just updated it. It's very similar to Shubcraft but I have the Gsensor on (and using it frequently) without a single screen freeze. Data has been solid and quick. I didn't like the Hi-res small image/text look that was built in but it was an easy fix to get that back to normal size, now the build looks and runs perfect.
Personally I like Sense, mainly for the email and agenda widgets, but the stock froyo builds are a lot more stable so I think I'm gonna stick with it for now.

"Sorry, not sure if this is int he right section but".....then why did you post it here instead of general section but thats your choice , second i would rather deal with a screen freeze here or there , than turn off auto sync and third that is really slowing your phone down with those setcpu settings , i agree with ounkeo thats half the phone speed...
but thanks any way

Thank you! I will follow your suggestion and feedback later.

Hey Im Chicago too!!! Well the burbs actually...
I solved my wake up issues by using setcpu and setting a profile for screen off 798 max 499 min scalingn demand and priority to 100
I know it high but from what I remember with the G1 and setcpu if you underclocked it it would freeze up. So thats what Im assuming with this as well. If its underclocked it will become non responsive eventually. I could be wrong but it my persoanl opinion and preference.

Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android

why bother ?
Might as well get a crap monochrome nokia then youll get 5+ days of battery life.
all you guys are doing is turning a smart phone into a dumb phone.

Do you have any issues with the internet on this setup?It seems on my set up the data indicator alternates between h and 3g all the time and can use any internet radio apps since it interrupts every few minutes.Also call quality would like to be a little louder.I have the stock radio 2.10.50.26,chuck rom lite for android and the latest 2.2 froyo stone 1.7.
Can anybody tell me what changes should i make ????

kardas666 said:
Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android
Click to expand...
Click to collapse
I am using shubcrafts 1.5 rmnet I get between 3-10ma while sleep. I wont except anything else. If i get the dreaded 40-60ma's I reset and I dont restart one its in the groove.
I noticed when I had the engadget widget going I would see 41ma in sleep mode.
I dont use auto sync because I can sync when I'm good and ready. I also dont turn off 3g anymore It isnt needed.
As far as the op's settings I think they are ok for him, I constantly clock my cpu at 768 as I have found it is responsive enough for me. I also use ondemand with a powersave bias of 500.

Hakeem5 said:
I also installed advanced task killer, not sure if it helps but my battery has been great since. Settings on there:
AUTO START checked, Show notification checked, Auto Kill Level: SAFE, AutoKill frequency when SCREEN OFF, Security level HIGH. OF COURSE you will have to put various apps on IGNORE so task killer doesnt kill them when the screen is off, so far i have ignored: App Brain, Advanced Task Killer(MAKE SURE TO PUT THIS ON IGNORE OR ELSE IT WONT WORK BECAUSE IT WILL KILL ITSELF lol), SetCPU, SUPERUSER, Google search, ad free, k9 mail and battery indicator pro.
All on ignore so they dont get killed, and i noticed ALOT of people use task killer but forget to put superuser, setcpu and advanced task killer on the ignore list so they may be getting closed out sometimes, which will make them ineffective for you.
Click to expand...
Click to collapse
Would someone please tell me how the f**k I could put apps o IGNORE?

the other battery thread found that having your keypad lights on before you boot into android and your sd card also impact heavily on your battery life.

vysus said:
Would someone please tell me how the f**k I could put apps o IGNORE?
Click to expand...
Click to collapse
when in the task killer app just hold down on the selected app to bring up menu

Thanx my friend

Good effort posting your findings, I'm sure it will help a lot of people...
I've played with SetCPU for a while trying a few things and found this setup to be the best for me:
I use the undervolted kernel from here.
I use SetCPU as follows:
Main Page
Max: 1113600
Min: 245000
Scaling: Interactive
Set on boot enabled
Profiles
Enable and Notifications checked
Screen off
max: 245000
min: 245000
scaling: interactive
Priority: 100
Charging/Full
max: 111300
min: 245000
scaling: interactive
Priority: 50
Battery < 25%
max: 652000
min: 245000
scaling: interactive
Priority: 50
Advanced tab
Min Sample Rate: 50000
I also have Autokiller installed with moderate settings. Remove all other task killer apps, including Advanced Task Killer...more info why HERE.
I use APNdroid to disable data connection when I'm not using it. But have wifi on all day.

kardas666 said:
Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android
Click to expand...
Click to collapse
I can confirm that having the keypad lights ON when starting up Android from WinMo does definitely keep standby at 3-10ma. The other thing you need to do to keep that level of drain is to switch off GPS unless you're using it.
My speculation tells me that there must be something wrong/missing with the gps and keypad light libraries after the dev's modified it to work on the HD2.
Oh yeah and this is on Darkstone's HD2Froyo v2.1

Hakeem5 said:
- Special settings in Android: Note: i turned OFF Auto sync, no gps, no facebook sync, weather or news sync.
1. Installed Set Cpu (Free to download on xda but i paid for the donate version to support the dev)
2. Set Cpu settings are in the PHOTO BELOW but as a recap
a. Click Autodetect
b. On MAIN tab, i set the max . . . .
Click to expand...
Click to collapse
nice try but with that "configuration" it would be better if i go back and use my
nokia of 4 years ago. thats no smartphone
Hakeem5 said:
Hakeem5 said:
- Special Settings in Windows Mobile: Turn off Auto backlight in windows mobile, turned of sync, weather, facebook, all that stuff that may secretly be on by default in windows mobile.
Click to expand...
Click to collapse
thats a better idea, this worked for me thanks for sharing us your discovery
Click to expand...
Click to collapse

kardas666 said:
Well, you got lucky with 3-10ma on standby, so your battery doesn't suck. Try few reboots and come back with the same numbers - GL on that.
So far I've tried every trick to get the magic 3-10ma on standby, and sometimes I get it, sometimes i don't. Simple reboot screws it up, and when it goes up to ~60, goodbye every-day use of android
Click to expand...
Click to collapse
hey bud, i was having the same issue as you. However, i'm pleased to say that doing the following has given me a 3-10ma standby over the course of a week with multiple reboots (just to check if it would work again). I pulled this from the "possible solution for heavy battery drain thread"
"If you start Android don't use WM at all, use auto-boot on 6 sec with Exceller Multiple Build Loader for Android/Ubuntu if you want to use windows, use it but reboot the phone before you start android."
I'm using this with an Energy Rom, 2.10 radio, and warrenb213's t-mobile us optimized build. Works a treat, hope you have the same experience
Ps... Doesn't matter if setcpu is enabled or not, I still get 3-10ma on standby, remember if you have autosync enabled you will occasionally get a spike while the phone syncs.

hazard99 said:
I am using shubcrafts 1.5 rmnet I get between 3-10ma while sleep. I wont except anything else. If i get the dreaded 40-60ma's I reset and I dont restart one its in the groove.
I noticed when I had the engadget widget going I would see 41ma in sleep mode.
I dont use auto sync because I can sync when I'm good and ready. I also dont turn off 3g anymore It isnt needed.
As far as the op's settings I think they are ok for him, I constantly clock my cpu at 768 as I have found it is responsive enough for me. I also use ondemand with a powersave bias of 500.
Click to expand...
Click to collapse
How can you see your power consumption in ma?

[Q] SetCPU causes phone to freeze when used to underclock when screen is off

So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?

rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off

rjmjr69 said:
More info.. What rom are you running? Are you sure your rooted? What settings are you applying?
I have not had any issues yet with setcpu and my screen being off
Click to expand...
Click to collapse
I'm running Baked Snack 1.1, doesn't matter what rom or kernel I use though, it still happens.
It doesn't matter if I use overclock widget or SetCpu, if I were to set it so that my phone underclocks to 200mhz or 400mhz while the screen is off it freezes and I have to pull the battery.

Same here im running stock and i've tried setcpu and no matter what i hav to pull the battery out everytime. So i uninstalled it.
Sent from my Epic 4G

I had the same problem set the cpu with min of 400 and max off 800 should fix your problem
Sent from my SPH-D700 using XDA App

It means that there is not enough voltage run that frequency on your phone. Some times these kernel developers undervolt the phone which all phone don't support at all. Try some other kernel like the xtreme kernel. That kernel actually work for me and I can underclock my phone without freezing.

rockethot said:
So no matter what kernel I use, when ever i use SetCpu (or overclock widget) to underclock my phone when the screen is off it causes the phone to freeze and I have to pull the battery out. I set it so that it goes down to 200mhz, tried 400mhz and experienced the same problem. Any ideas? Solutions?
Click to expand...
Click to collapse
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience

murso74 said:
wow.. i just posted something like this i had set cpu installed since i rooted my phone last week. today i was playing with the settings because my music was stuttering.. i thought it might be a underclockign problem so i changed the profile to "ondemand" it made the stuttering better and everything seemed fine. about 12 hours later i got home and was playing with the phone. i updated 3 programs in market and all of a sudden my phone would go to sleep and not wake up. had to do a battery pull. i uninstalled the 3 programs i updated but the problem kept going. just uninstalled setcpu. hopefully it resolves everything
using epic experience
Click to expand...
Click to collapse
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.

I'm running Baked Snack 1.3 and found it to be stable at 1.2ghz using OC Widget. With screen on I have it set to min 400 and max 1200. With screen off it's set to min 400 max 600.

I too am having this problem. No mater what rom or kernal I use. It seems as if Setcpu and Overclock widget sometimes cant read the frequencies and let the phone underclock to 19.2Mhz which is probably like trying to wake the dead!
I wonder if it has anything to do with the new Superuser.apk? it always seems like setcpu is trying to get permissions. Maybe, I dont really know. Can one of you really smart people look into this?
In the meantime the only profile that I have set is screen off Max 800 Min 400, maybe that will work?

same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.

What i've gathered over the last several months, is that SetCPU profiles are buggy with our phone. Its recommended not to use profiles.

I'm fairly certain that SetCPU should not be used without a custom kernel that allows for over/under clocking. If you're on the latest ViperROM then you are using a kernel that we have no source code for, therefore it doesn't support over/under clocking; rendering SetCPU useless and prone to cause problems.

mattallica76 said:
The use of profiles is not recommended on Galaxy S phones. The developer of SetCPU actually does not recommend using any other governor than conservative, even though we've been able to make Interactive work on some kernels.
Click to expand...
Click to collapse
My SetCPU is using conservative and I haven't had any problems so far. I am running BonsaiROM 1.14.

jemarent said:
same issues here. i'm running with my screen off at min 100 and a max of 800. If i change my max to anything lower, my phone won't wake up. I'm running the latest VIPERrom. I'm hearing some mixed feedback about this app so i would like hear your feedback.
Click to expand...
Click to collapse
If you have it set to under 200 with the screen off it won't wake up after a while.

I've had the same problem on all builds and ROMs that I've used. The only constant through all the different setups I've used were Advanced Task Killer and SetCPU. I stopped using ATK (with auto-kill on screen off, I use EStaskmanager for manual killing when phone is on) and the problem seems to be mostly fixed. It does still happen once in a blue moon though, say once every day or two.
Phoenix Kernel/Syndicate ROM 2.1
SetCPU: 100min/1200max
Screen off: 100min/200max
Batter < 30%: 100min/600max

A simplest solution for battery issue

Hi there,
I was very unhappy and was about to go back to 2.2.2 because the battery life was horrible after OTA upgrade to 2.3.4. Here is how I resolved the battery issue on my Atrix 4G. This was the simplest way for me and works great.
Pre-Condition:
-You must not a heavy user because this method is going to slow down your phone's performance.
-Rooted phone.
1. Download CPU tuner (free) from the market and install it
2. Under Settings (this will option will pop up when you run the app for the first time)
-Set "User Interface > Experience Level" to Power User
-Do not check "Enable CPU tuner"
3. Set Frequencies under Current tab to
Min: 216 MHz
Max: 312 MHz (you can increase this if you wish but it will consume more battery)
4. That's all
Although the performance is really slow, I still get calls, email and text.
When I need to do something, I just open up the app and increase the Max. frequency to 1000. And then, change it back to 312 MHz when I am done.
I do battery calibration once in a while with a free app from the market.
*** My battery is still at 80% after 12 hours of use. ***

Set your max to 216, it will last even more!

Actually to get the best battery life, I recommend turning off the phone. It will increase the battery life even more.

I paid for juicedefender a while back and didn't really use it until recently but it works great. Shuts off wifi when not in use, and turns off data when the screen is off. I still get texts and calls with no issues. I tried setting my max to 216 and it took like 10 seconds for the screen toturn on when getting a call....and a couple of times the calls went right to voicemail.

Phoneguy589 said:
I paid for juicedefender a while back and didn't really use it until recently but it works great. Shuts off wifi when not in use, and turns off data when the screen is off. I still get texts and calls with no issues. I tried setting my max to 216 and it took like 10 seconds for the screen toturn on when getting a call....and a couple of times the calls went right to voicemail.
Click to expand...
Click to collapse
I do all those things manually.
Sent from my MB860 using XDA App

I was too but I thought being it was automatically done whne the phone times out...it works great if you forget or don't have time to do. Just thought I share it...my battery is hit or miss with different ROMs but this seems to help without scaraficing time or functionality.

This is probably why I won't go GB on the Atrix. I had enough run with it on my SGS. Battery life is way too important to me...
Sent from my MB860 using xda premium

Try to disable/uninstall the CPU control software such as SetCPU and let the system to control the CPU. You may find the solution.
Sent from my MB860 using XDA App

Thank you for all the comments guys! It works for me at no cost so I just wanted to share the tip with others.

Yes, and turning off my engine and coasting down hills saves me gas.
Sorry, I just can't see crippling performance as a solution.

I use Temp + CPU Pro to monitor my CPU and most of the time it stays at 216, it switches up to 312, 456, then to 1 ghz occasionally but most of the time is at 216.
Over all I would have to give the 'lil fella credit for managing CPU speed automagically pretty well.
PS: Carlharsch I was visiting a vendor in China, and on the interstate the driver would cut the car off on hills, and I leaned forward to look at the limo gas meter and it was on E! I asked the interpreter WTF are we out of gas? Why the H*ll did you pick me up with an empty tank! She lied and said "oh no, the gauge is broken, haha". Of course I laid into the management at the company and at the end of the week the car was full when we left.
Talk about a nightmare being stranded on the interstate in deepest Guangdong.