this may be posted in the wrong section but i would like everyone running froyo to test this out
HERE IS THE LINK TO GET THE LATEST SETCPU
http://forum.xda-developers.com/showthread.php?t=505419
So I have been doing some experiments on ways to save battery life....I think i have made a break through it is not fully tested i would like for some of you to try it out.
with the latest updates to your ROM itself, setcpu, superuser, and the addition of cache cleaner and the incredible AUTOKILLER (a must have) i have been able to run extremely low setcpu sleep profiles without any noticeable loss of performance.
Believe it or not i have my sleep profile down clocked to 19200mhz with out "noticeable" performance loss
i would like for some of you if possible to try these profile out for a while and see how it works out for you
DEFAULT 480min---whatever you want max (mine is 787) ondemand (for performance)
OR DEFAULT 245min---whatever max (for even more battery savings)
SLEEP 192min---480max ondemand (works great even without sleep to wake lag)
it works dont believe me then check out set cpus new feature "time in state"
open setcpu
go over to info
scroll down a little and you will see the times in state your phones cpu runs in the most
you should now see values at the lowest state of 19200
if this works in theory we can benefit from longer battery life
and faster charging
please try these out and report back to the post or PM me...this could be good
Thanks
UPDATE 8/22 EDIT: some users are having success running an even lower default 19min--whatever max (thats even more savings) will be looking into it
try these even lower profiles
DEFAULT 122min--whatever max (screen ON cpu does not drop below 122mhz)
Screen OFF 19min--245max (no lag just ran pandora and cardio trainer at the same time here no lag from sleep to wake either)
or Screen Off 19min--480 max for more performance
REMEMBER not to have conflicting profiles and to have SCREEN OFF at your highest priority
please post here your own findings and results
Thanks again
UPDATE 08/24/2010
after experimenting with other speeds i have finally settled on these speeds for my personal taste on performance and battery savings
MY FINAL SETTINGS...
DEFAULT 19MIN---786 or whatever MAX on demand
SCREEN OFF 19MIN---480 MAX on demand (highest priority) think deeply about why this is the highest
TEMP <40 19MIN---528MAX (screen off overrides this which cools anyway)
BATT <40 19MIN---604MAX
next more into advanced settings....coming soon
UPDATE 08/26/2010
im almost at the holy grail here
try this set up
SCREEN OFF 19--480 (95 priority)
TEMP <40 19--580 (90 priority)
ADVANCED SETTINGS
SAMPLING RATE---100000
UP THRESHOLD---98
ignore nice ---0
power save bias---0
hit apply (if you like it check set at boot)
ALL CPUS ARE NOT CREATED EQUALLY WE ALL KNOW THIS SO DONT EXPECT MY EXACT SETTING TO WORK FOR EVERY SINGLE PHONE
I CAN ONLY OFFER A STARTING POINT BUT ITS UP TO YOU TO TWEAK IT BUT ITS WORK
I HOPE THIS HELPS
things to notice....
in the main screen in setcpu watch the main frequency values bounce up and down...after a few seconds the values seem to stabilize at the lowest frequency of 19
in time of state screen even when screen on most of the time the 19 freq get the most values
i need a few guys to run, test and monitor the values that i just posted ^^^HERE^^^
this may further the battery life once we stabilize the frequency to 19 most of the time while keep the SAME performance which i think i may have did
run some linpacks and quadrants with those setting
i got
5.4 linpack running 787max
431 quad running 787max
then it drops back to 19 and stabilizes
hope this works and please post all your feed back and setting so we can learn this and get it perfect
thanks
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
thisisreallygay said:
I even use 122 and 480 for my screen off profile.. And I don't have any lag at all.
Click to expand...
Click to collapse
19 is even lower try it
Oh 19200? Wow I wasn't paying attention well enough. I'll try it.
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
I wonder what it's like when receiving a call. I just set it and I'm not having any lag with just turning it on or anything. I'll test it out with other things. I hope this greatly improves my battery.
roirraW "edor" ehT said:
Almost from the beginning of my rooting in May and using SetCPU, I've been using 19.2- 748.8 (on demand) with the screen on (sometimes higher but recently reduced the max to see if it helped with some FC's I was having - still haven't determined if it was the profile or the ROM that fixed my FC's).
I use 19.2-245 for screen off. I'd venture that there's about a one second delay for the caller ID to work once a call rings in, but it's more than bearable and worth it.
I have it go to 19.2-528 when the battery is less than 25%,and 19.2-480 if the temperature is above 49 degrees celcius.
Click to expand...
Click to collapse
shame on you for keeping that secret all to yourself
SHAME
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Search for it on his website, idk what his website is you'll have to search for it. Or download a ROM with it already in it.
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
thisisreallygay said:
By the way why did you say froyo roms specifically? I'm trying this on tainted tenzo and it's working. I'm usually on a frooy ROM though.
Click to expand...
Click to collapse
hmm last time i was on sense rom sense fell apart if you clocked lower than 245
epically receiving a phone call
but i only test this method on froyo
I've heard that too. Although I don't know what is bad about it.
sh_mohanna said:
Hi Guys,
Can you please tell me how to get setcpu? I can't find it in the market.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
HERE
http://forum.xda-developers.com/showthread.php?t=505419
eklipze said:
im on froyo 30 and was unable to get the 19.2 to show on time in state with screen off profile set to 100 priority at 245/19.2
i was however able to have it start using that frequency by using 710/19.2 as my default setting, then enabling the 245/19.2 profile as screen off.
ive read its not too good to have the cpu jump more than 300mhz per profile though so im not sure how this will work out.
Click to expand...
Click to collapse
i heard that too but all froyo dev have a 245 to 710 stock on their roms
thats why i kinda spilt the two profiles and why 245min--- is experimental
leave your screen off for a while and see if the ime of state shows up
also make sure not to have conflicting profiles running in setcpu
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
thisisreallygay said:
Hmm. Well tainted is vanilla but has some sense elements (like sense dialer) So idk. It seems to work. I'll test out calls.
Click to expand...
Click to collapse
oh ok tainted is not vanilla
tainted IS sense with sense removed with vanilla remaning hence the word tainted
some sense is still there
i think
Yeah it's got sense contacts and stuff but vanilla messaging. But it has the sense dialer so I think it would also have lag with calls if the sense ones were having lag. And I just tested it and it took a lil while for it to recognize whose number it was but it still gave me plenty of time to answer the call. I'll be testing to see how it improves battery. Thanks for the find
Im also testing setcpu Advanced settings batery life (without performance loss)
What settings are those?
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?
I have been using nearly all the build out there before settling on Hyperdroid 1.7
On all of them I have been having the problem with the screen not waking up when you push the power button - the lights come on but the screen never wakes.
Now I know that some people have been saying this is due to the light sensor and holding the device close to a birght source does seem to wake the device up properly.
But I have been using 1.7 now for two days and found an almost instant on every time without any black screen of death or requirement of holding the device up to a light source.
I had/have always been using both Juice Defender and SetCPU - and tried on both the CPU scaling functionality - but both caused lockups.
Until - I change the LOW value of any profile to 422 and max 998.
Changing the low value from 245 up to 422 seems to have cured things for me. With the new 1.7 Michy kernel I still get 4-7ma in standby as reported bu currentwidget - and overnight my battery went down just 8% in 10 hours!
The only other piece of software I have installed is Taskiller which I have set to kill on screen off - and have put all the usual suspects on the "ignore" list.
Device has been working perfectly over two days now completely stable and not a single reboot - except for one very strange issue where the wifi (which is turned on and off with the screen via Juice) said it was turning on and then failed - leaving it greyed out and "turning on" but never did.
This only happened once and other than that wifi has been turning on and off perfectly.
My only reason for raising the lowest CPU setting was something I remember from the TD2 I had before - that too hated going to some of the very low frequencies and caused lock ups etc but if you scaled up a bit everything was fine.
Hope this helps.
I have same issue, I am using nexus built 2.2, I had guess Set CPU might responsible for this issue, can please specify your set CPU profile settings
I have changed builds many times since posting this as there were odd errors on almost every build - I have it down to the usual two now. Screen freezes vs data drops.
I am using tytung NexusHD2-FRG83 V1.6 PPP + RMNET - Release Date: 8.Nov.2010
Default settings which uses the hastarin 8.1 kernel.
No setCPU.
I no task killer but have system panel installed to help with the odd runaway app.
Link: http://forum.xda-developers.com/showthread.php?t=793924
But am keeping my eyes on the PPP development for the data freezes as once this is sorted PPP will be a fully working build - unfortunately it doesn't appear that as much work is being done on the RMNET route - so it's just a wait and see game.
Hope this helps.
rparmar said:
I have same issue, I am using nexus built 2.2, I had guess Set CPU might responsible for this issue, can please specify your set CPU profile settings
Click to expand...
Click to collapse
the OP did mention to NOT set your minimum to 245 mhz but about 400 mhz. whatever your profile is, try to avoid setting the minimum to 245
I have rooted abdroid 2.3.4 with cyanogen 7 and in the settings there is one that i can change the maximum value to cpu...Now is at 998....what value above that is the safest to choose with out the phone have any problem???
depends which rom it is
some can go up to 1.5 and some cant
Can also depend on the phone, I have 2 hd2s, one chuggs along nicely at 1075mhz, the other gives random slowdowns / hangs (4-5 a week,not lots but enough to be a pain) at any setting above 921mhz. Same rom,same installed apps, same data.
Well here are the Phone Info
Model
HTC HD2
Andorid
2.3.4
.......
15.42.50.11U_2.15.50.14
Kernel
2.6.32.15_tytung_r10-gbdfeaac
Mod Version
CyanogenMod 7-05252011-NIGHTLY DESIRE
GRJ22
Anyone?
Sent from my HTC HD2 using XDA App
The best thing to do is scale up gradually, try each step above 998. OC then try it for 24hours, then try a step up and try it for 24 hours and so on. Do not check set at boot though just in case you pick a speed that causes problems.
What can go wrong???How do i see that it cant support a number??We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????
What can go wrong???
It coukd stop booting and require a hard reset/backup restore.
How do i see that it cant support a number??
It will start to give force closes, hang, reboot, feel sluggish..
We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????
Do a cwm backup and just try it, worst case scenario is it doesn't boot and you have to restore.
ntisco said:
What can go wrong???How do i see that it cant support a number??We are talking about maximum price and not all the time...???Someone that tried and have it overclocked????
Click to expand...
Click to collapse
I would guess that the majority of users are overclocked. I, for example, am running my phone smoothly at 1.2 GHz without problems, but to be honest I scarcely notice the difference with overclocking. Dorimanx's kernel with 1.61 GHz overclock didn't really perform any better than Tytung r14 at 1.2 GHz.
Just do as the others said and try it out whilst making sure to uncheck 'set on boot', but I think any speed should really be fine.
I don't know what the general opinion is on this (some devs say it isn't a good app) but use setCPU in order to create profiles if you want, thus being able to reduce your standby battery drain and stuff like that
In the quandra the info of the phone whrites that the cpu is up to 1190mhz and know is at 998.Is this true?Can it go that much?
If so we can put it at 1113 that its safe?
I know that i ask again and again but i dont want the phone to lose or damage
Youre best bet would be to download setCPU and try different clock speeds . the thing about setCPU though is it has a stress test . So after you set a speed . you can run the stress test to test if its too high a value or if you are safe to run at that speed . just dont tick the box that says "apply at boot"
My phone (currently Dorimanx ROM) is stable at 1536MHz. On Cyanogen it was similar. On 1612 it had freezen for a few times while watching a flash video on youtube. Set it to 1,4GHz, and it should work fine. Phone will not damage, data too. Just as they written above, do not click apply at boot.
And make stress test for more than 10 mins, because I have done it for 10 mins, and as I written, it had freezed during YT watching.
The topest that it has is 1190..that is the last option !!!I put it at 1113 for one day know and i made a profile to go 573 when i close the screen.
Tomorow i try the next option antil 1190 ...and we will see
Tytung r10? Why not upgrade to another Kernel?
I think that's the core issue. Dorimanx kernels i.e. can be clocked solid to 1.2ghz
Oh, I've completly forgotten. I have used Dorimanx kernel with Cyanogen. But it doesn't let you reinstall rom from settings (Factory reset). You need to reinstall rom from zip or restore backup in CWM. On 1190 it will work stable for ever