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...
Related
Has anyone noticed any long term disadvantages to overclocking the Wizard? Does the battery life permanently decrease? What speeds are you running yours at, and how long have you been doing it? Have you noticed anything at all which indicates it's not good for the hardware?
Cheers
reply
i believe that it's safe to overclock the mda...just set it at an acceptable rate (264mhz for me) and make sure not to run the battery all the way down...if you overclock the settings too high the device will freeze and reset (this is a fail safe procedure it goes through), so there is no need to worry...also don't overclock the settings too low as the phone becomes disfunctional when too low (about less than 132mhz for me)...the screen flickers because it's not being refreshed quick enough (my guess)...hope this helps...
I would set it to 240. I have done before, i'm just wondering if it's a bad idea leaving it permanently set to that level?
Cheers
yea you should be fine at that speed, but if you want you can overclock it higher if it will let you...just make sure that the phone is stable when using it...like i said in my earlier post my device is oc at 264mhz
Cool, thanks for your replies. How long have you had yours overclocked for? Do you use Smartskey?
Cheers
My self i ownly use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.
My self i only use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.
Mine is also set at 264 24/7. Battery still lasts me all day. Been doing it since the oc program was found which I guess has been a couple of months.
Don't forget, you're wizard is only overclocked when it is active (i.e. not in standby mode). When your wizard goes into standby, it automatically goes back to the default 180mhz. Only when you bring it out of standby does it overclock again (assuming you're running it with smartskey with the option of overclocking on wakeup)
i'm using smartkey to constantly run at 264mhz...i have been doing this for a month now...like i said there is not really any problems with the batt unless you run it down totally...there was a post about this in the overclocking thread...the process is set low so that the phone will have a longer batt life...this was also stated in the overclocking thread...theoretically there is more wear if you overclock it since you are making the processor work harder, so use it at your own risk! if you want to be on the safe side then use smartkey and the overclocking prog in the same directory...then use total commander's note pad (while the ini file is highlighted) and change the value lower when you don't want it to constantly run at 264mhz or whatever speed you want to overclock or underclock at...just use it when needed, but i overclock mine constant 264mhz with great results combined with tweaks2k2, registry wizard, and of course the tmobile custom rom ...internet is a blast...just wish i could get it to run like the IE in a pc
anyways hope this helps out a bit further...
activesync
your activesync will hang allot if you overclock, I have noticed this.
DOnt know why.
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.
Re: DOnt know why.
xSoNiCcRaCkErSx said:
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.
Click to expand...
Click to collapse
hey sonic, where did you get your copy of warcraft 2 for windows mobile ?
I've never heard of warcraft for Windows mobile, how does it run on a 240 MHz overclock?
I got it from the Wargus engine. i can email you the files if need be, i dont want to jeprodize this sites reputation. The game last time i checked was free though...
Actually I'm not sure if it's the overclocking issue or not but ...
For couple of weeks now my Wizard's red led is on all the time, not like it is when your battery is very low but about half of this brightness. I'm not really worried about that, it doesn't change much but it may be connected with overclocking (it was 240 for about a month).
Another thing - once I had sth like 110% speed of every tone played, either a phone call or an incoming message.
It doesn't really matter to me since it's still working fine but it may mean that overclocking isn't that safe as we might think.
TroLoo
PocketHack Master V4 is now out with Tytn support. Be warned that at it's highest setting of 440mhz i had to HARD reset my device.... Must start at a lower speed next time and work my way up!
I'm still in the middle of restoring!!
johnk1973 said:
PocketHack Master V4 is now out with Tytn support. Be warned that at it's highest setting of 440mhz i had to HARD reset my device.... Must start at a lower speed next time and work my way up!
I'm still in the middle of restoring!!
Click to expand...
Click to collapse
have you found a need to overclock the device then...., might works fine for what I use it for
Thanks for pointing this out... I updated the FAQs on the wiki.
It automatically scales the processor voltage onSamsung S3C2440 processors
so does this clock it over 440mhz, because an extra 40mhz doesnt really sound worthy of paying for software, especially when the TyTN is pretty snappy?
So... do you need to stick it in a fridge or anything afterwards?
I think the main idea of using the program is to allow a "super battery saving" mode, by underclocking the device it will use less power....obviously impacting performance-wise but still!
The main reason I wanted PHM was to help render web pages faster. My tytn downloads quicker than the works PC on normal broadband but the pages take longer to 'finalize' the page (i.e.. you can scroll down a page and it's still inserting images). This is a CPU speed issue.
I have finally got to play with PHM and it still needs more work! Just doing a test at tytn's default 400Mhz crashes my phone, never mind higher! I never got much higher than 300Mhz, how strange!!
Hack Master V4 not ready for primetime!
As others have noted, don't waste your time on Hack Master v4. I played with it, only to find it causes crashes, no matter what you do. Also, I found that it caused an incomplete Hard Reset. So, I had to do the manual hard reset twice, to get TYTN working again correctly.
Also, the Wiki should be updated to show there are still problems for anyone wanting to OC the TYTN.
I stupidly tried PHM too, and have just suffered a partial hard reset. Here goes the long and frustrating reinstall...
grayhaze said:
I stupidly tried PHM too, and have just suffered a partial hard reset. Here goes the long and frustrating reinstall...
Click to expand...
Click to collapse
aren't we allowed to take these people to court? False advertising and damaging my equipment? They must have had enough emails by now and yet the same program is still there advertising the same things, very poor...
We should probably change the title of this thread to say "OVERCLOCKING: DON'T EVEN THINK ABOUT IT..." :idea:
johnk1973 said:
aren't we allowed to take these people to court? False advertising and damaging my equipment? They must have had enough emails by now and yet the same program is still there advertising the same things, very poor...
Click to expand...
Click to collapse
They can get away with it through the fact that they tell you to backup your device before you use the program. Coming from an XDAII where PHM worked perfectly though, I stupidly assumed that the quality of the product would be at least the same or even better after numerous updates.
I'm pretty much set up again now, but I'll certainly be looking at purchasing a backup solution before I put my trust in something like that again.
Don't think about it, even with a backup... While trying to overclock my TyTN smoothly, it's now on the way to service (no more booting at all...)
Gx
Oops ... you should have read this thread before even trying overcloking ...
sorry for ya mate !!!
I find my Jasjam (Hermes) runs very fast and I don't see the point in over clocking it when it runs fast enough normally.
Have XCPU Scaler, in autoscale mode working up to 500mhz, on a cingular 8525 (HERM100), no resets, no problem.
>Edit
Also scaled down to 200mhz on the low side for super battery saver.
?Glitch
?Glitch that is amazing not just the speed but the fact that their is no problems!!!!!!!!
?Glitch said:
Have XCPU Scaler, in autoscale mode working up to 500mhz, on a cingular 8525 (HERM100), no resets, no problem.
>Edit
Also scaled down to 200mhz on the low side for super battery saver.
?Glitch
Click to expand...
Click to collapse
you'll be needing one of those new spangly batteries with extra life to cope with a processor increase like that.
@?Glitch: Can you post some screenshots?
That's awesome .. Has anyone else tried this program out? How's it working for you?
I'm using the XCPUScalar with its CPU load based setting.
Normally I set the speed to only 200MHz while on heavy load it speed-up back to 400MHz and 500NHz on very high load.
On day-to-day use it looks like extending the battery life (working on lower clock rate) whiles much quicker route calculation when using the navigation program.
Currently I faced now problem.
what is the highest that the wing can be overclocked and what would be the best program to do so?
rastlin said:
what is the highest that the wing can be overclocked and what would be the best program to do so?
Click to expand...
Click to collapse
You are prob going to be slammed with 'use the search feature', but, I'm bored as hell at work, so I thought I'd help.
You will find many people use different speeds, and different programs. The two I've used are batterystatus and Omap. Personally, I like batterystatus, and I've safely clocked mine to 299mhz.
BatteryStatus? Isn't that way old?
I highly recommend HomeScreen Plus Plus (which is the new version of Battery Status) just google it and you'll find it and download the Advanced verson not the Basic one.
And I safely overclock it to 299 with no problems. I went to 312 once but every so often the phone would rest itself.
HS++ is also good cause it auto underclocks and auto overclocks your device so when your phone is sleeping it saves battery .
buru898 said:
BatteryStatus? Isn't that way old?
I highly recommend HomeScreen Plus Plus (which is the new version of Battery Status) just google it and you'll find it and download the Advanced verson not the Basic one.
And I safely overclock it to 299 with no problems. I went to 312 once but every so often the phone would rest itself.
HS++ is also good cause it auto underclocks and auto overclocks your device so when your phone is sleeping it saves battery .
Click to expand...
Click to collapse
+1000000 this is awesome man! thanks
i want to thank everyone that had responded i did a little research and i was confused. ya see i am using batterystatus .04 and if i go above 260 my phone freezes and to be quite frank i had 2 wizards that i believe died from overclocking. they both one day randomly after a reset went to the bootloader screen and stayed. i had tried a hard reset and flashing the unit with no luck personally i dont have a clue what happened and with this one being my only source of 'net access i cannot mess it over once again thank everyone whom responded
-rastlin
Hmm wow I'm sorry for your Wizard but the Wings can go up to 299mhz without dying and the good thing about HS++ is that if you enable CPU Scaler and set the overclock to say... like 400 and your phone freezes, just plug in your charger and reset your phone. The CPU Scaler is disabled as long as you have a power cord plugged in your phone (your phone stays on it's native speed) so you can just go back into the CPU Scaler overclock settings and lower it and try again ^_^!!
So just use the CPU Scaler to find the highest overclock speed but never just set the overclock speed in the normal overclock menu. Use the CPU Scaler auto overclock option and you won't need to hard reset your phone.
thanks for the advice. so it is possible to kill a unit with overclocking i just wanted to be sure, cause when i asked in the wizard forms if i am not mistaken no one answered me. i had also asked hct via a number provided to me by tmobile and they said the stock "i dunno we will have to look at the unit and that will be $180" towhich i responded f**k!! that i can get a new unit for under 130 off of ebay then got a wing....
-rastlin
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?
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Sounds like simple bad karma, I suggest donating to a charity or going to church
Other than that, I'd have no idea, sorry. Seeing as its not totally regular, there'd be no good way to easily pinpoint the issue. Maybe see if the rom produces a last_kmsg?
-Nipqer
makken85 said:
Now I love my DZ; it is by far the most capable phone I've ever owned, but it has this nasty habit of failing me whenever I seem to need it the most.
For example, today I was stuck behind a huge accident on the highway with an exit coming up in a few feet. I thought, "hey I'll just see if I can find a detour around it from this exit." Pulled out my phone and quickly launched google maps. right then, it completely stops responding to all touch input; the trackpad and physical buttons work fine, but nothing was registering on the touchscreen or capacitive buttons. I eventually had to pull the battery to fix the issue.
It just seems that these things tend to happen whenever i need to lookup something quickly on the phone (when im just screwing around on it, it works perfectly fine) be it completely not responding to touch input, or something weird happening like getting stuck between 2 homescreens, or the notification panel gets stuck halfway down, or massive input lag (5+ seconds) to the point of it not being usable.
And everything goes back to normal after a reset; but by then, I usually don't need to lookup whatever it was anymore.
The most frustrating part is that I can't seem to figure out whats causing it. I'm running virtuous 2.0.0 without any sense 3 additions, and I generally only have 1 or 2 tasks going on on the phone at once (usually just music player + whatever I'm doing). I originally thought it was just a performance issue, so I've increased the clock up to 1.5ghz (using daemon controller) but it hasn't has of an effect.
Any ideas on what else i can try?
Click to expand...
Click to collapse
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
skulk3r said:
although people say roms are 'stable' and can recommend these ROMs as "dd" (daily drivers) you cannot say that will be completely reliable. This is because when people say a ROM is 'stable', it's only after using it for 2-3days; unfortunately, roms gather clutter and begin to slow down over time. Not a problem for many flashaholics, but a problem if you're a one-rom kinda guy (or girl). So if you're not one-night-stand rom kind of person, here are some tips:
Reset your phone regularly. Phones start acting funny when they've been on for too long
Try stock ROM with addons flashed on top of it, rather than baked in a new rom
Most reliable roms i've experienced are Stock Gingerbread or CyanogenMod. Try those
If you are flashing a new rom, use SuperWipe, this can help get rid of clutter from old roms
Click to expand...
Click to collapse
Hmm, so you believe that this is purely a rom issue?
I havent run a stock rom for a while, but from what i remember the experience wasnt that pleasant, there was significant lag almost everywhere in the ui. Although i will admit that was back with froyo; i havent tried a stock gb stock rom yet.
Ill probablygive cm7 a go. Ive just grown so used to some sense features that its going to be hard for me to give them up (mainly recent apps in notifications, news widget, t9 dailer+manually linking contacts, and remote ring and forward on htcsense.com)
Has anyone had similar issues running virtuous sense 2.0.0?
As far as recent apps goes, long pressing the home button is a standard feature of android that brings up the most recent. Stock is the last 8 (I think) cm7 can show 15.
Sent from my HTC Vision using xda premium
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I'd agree. I really wouldn't ever go over 1.2ghz for a daily driver personally.
I run my ROMs at 800mhz lol, so I don't see the advantage of a huge overclock unless you're just bragging about benchmark scores.
its funny when u wanna show off your phone and you take it out of your pocket acting all cool and stuff and when u press the power button it wont wake up or you get a blank screen
haha its just bad karma for u like nipqer said
Try the stock pre-rooted gingerbread...I just flashed t last week and it is way faster than my froyo was, and amazing battery life, for me anyways, I do have an extended life battery though lol. Anyways as far as speed it is snappy on 800 mhz
Sent from my T-Mobile G2 using XDA App
redpoint73 said:
Higher overclocking will make your phone LESS stable, not more. I'd stick around 1 GHz, as this is known to be very stable on most Z's, and usually does not result in any significant additional battery drain. OC may not have anything to do with your random hangs, but its probably not helping either.
Click to expand...
Click to collapse
I've noticed the random hangs / glitches @ 800Mhz and 1Ghz, so I'm hesitant to say that the OC is the cause.
What do you use for stability testing? I've been running quadrant nonstop to test new OCs, but I don't think that benchmark stresses the cpu enough.
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
swinderz said:
i am running Virtuous v2.0.0 w/ kernel unity v6 on it on desire z.
i've found bugs like
1/the top black bar ui, top left corner, some times i see the background wallpaper rather than the black bar. but it goes away if i pull down the notifications.
2/ the mail with microsoft exchange active sync, if i delete the mail it will automatically resync and downloads all mail including the on i deleted. but i got around that by using pop/imac instead.
all rather minor as i got ways to go around it.
i did have a similar issue where the touch screen goes unresponsive and i had to force close it, restart phone to get it back alive. but then i readjusted the clock speed and never had it happened again.
the phone is at around 825mhz with governor smart ass on wake time max, unless im watching 720p movies on the phone then i ramp it up at 1.4ghz.
sleep time on 368mhz max with governor at conservative.
i had it on like this since 11/09/11 (as i made a rom backup) and it never occured yet.
Click to expand...
Click to collapse
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
makken85 said:
I've been playing with the wake min and wake gov settings the past few days. I have it set at 600Mhz min, performance gov; I haven't noticed much difference in the battery life, but I'll have to do more extensive testing to be sure.
Performance feels slightly better, especially after a fast wake. can anyone give a detailed explanation of the behavior of the different gov settings? I can't seem to find much info on it.
Click to expand...
Click to collapse
http://www.droidforums.net/forum/droid-hacks/21309-setcpu-1-4-6-what-cpu-governor-options-mean.html