For those of you who have used cooked WM6.1 ROM's, have you had to overclock your Wizards? If so, by how much?
i use battery status and use the CPUScaler option for minimum i use 121 and for origional 195 max 195 but for boost 260 this in my opinion gives me the best battery life to speed ratio
, Sorry, but I haven't understood a single thing you said there... So is overclocking necessary to have a useable phone? Or best to stick with WM5.0 if you don't want to overclock...
overclocking is not neccesary, but it does give a significant speed boost in most ROMS, regardless if they are 6.1 or not
How does this effect the temperature of the CPU? Does it get significantly hotter & thus likely to burn out quicker...
as far as i can tell ive been using my phone for over a year and have found absolutly no problem with over clocking besides the extra battery drain
And what i was explaining b4 was the options i used on the overclocking program batterystatus theres an option called CPUScaler that allows u to variate the cpu speed this gives u the best of both worlds ie when ur using it for something heavy it will increase the cpu speed to the level u specify but when its not under heavy usage it will underclock (ie go to a slower cpu speed thereby decreasing the drain on ur battery).
And yes overclocking does give a significant boost to performance on any of the roms even wm5. Theres no harm in trying it so give it a try and you would see for yourself, if u dont like the way it works just uninstall the program and your done no problems and no long term effects.
Hey everyone, there is an overclocking app in the market, anyone care to give it a try?
Edit: So I downloaded it lol. Here are some screenshots. BTW, is there anyway I can verify that the cpu freq is actually being adjusted?
*Just for fun I ran neocore to see if it would raise my FPS. lol.
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
For example, atrackdog would take me at least 20-30 seconds to load my full app list (184 apps)
After installing overclock, it loaded in under 5 seconds.
i'll run other programs, and post my results.
I ran droidgear (game gear emulator) before and after, and I can honestly say it was faster (not a placebo affect).
-Before: droidgear would take over 4 minutes just to get to the menu screen
-After: i was actually able to load a game in under 1 and a half minutes, I even let it sit to run the demo, and it is the fastest ive ever seen an emulator run on this device (compared to NesEmu, and GB emu)
It would probably actually be playable if tweaks were made to the application codebase, and android Open GL stack.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
well, i was too, and then i downloaded it and said "aahh, what the hell, if i break mine, ill just take my wifes haha..." probably not the best of plans but i installed it anyway
sooo i havnt burnt up my phone yet, but here is my issue with the app, does the app only work untill you reboot your phone?
because when i reboot my phone, it goes back to the default speed according to the app
also, my phone tends to hang up (stuck on the apps screen, no buttons work, screen wont rotate, power button wont shut screen off) when using the 528MHz
so far, i havnt found a reason to pay a dollar for it, but ill keep testing
[UPDATE]
resolution for all below tests is 320 x 480
i tried neocore like posted above, using the mid level setting, and i actually did raise my fps from
DEFAULT CPU (248 MHz): 20.5 (with sound off)
384 MHz: 25.0! (with sound off)
DEFAULT CPU (248 MHz): 14.5 (with sound on)
384 MHz: 20.8 (with sound on)
still havnt gotten the fast speed to work yet, but im still trying to figure that out, on another note, sweeter home does seem to load a little faster
[UPDATE]
Incase you didnt see my sig, im not running on a ADP1 phone, so that might by why the fastest setting doesnt work for me, but so far 384MHz is making a noticeable difference with NEOCORE and SWEETER HOME
andonnguyen said:
The app is called Overclock, you can argue with the developer about the name not me.
Anyways, I do notice a very nice speed increase.
Also, the camera loads instantly after pressing the camera button and via the icon in the home screen.
Click to expand...
Click to collapse
i use snap photo, which used to take FOREVER to load up on my g1 using the camera button, its significantly faster using the 384MHz setting, good observation
Ok, so so far here is a list of things ive noticed (using 384MHz vs 248MHz):
-FPS in NEOCORE increased on adverage 5 to 6 fps
-Sweeter Home doesnt lag NEARLY as much as it used to (ALOT less force closes)
-Snap Photo doesnt take a month to load using the camera button
-G1 Wakes up properly which was a issue my g1 (and others on this forum) had
-Even though the app says it will "kill" the battery, using 384MHz during normal use of the phone isnt "killing" my battery, however, doom (while runs better (even with sound on)) seems to be dropping my battery level faster, but the game is running faster, which is the trade off id expect when running these apps together
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
speoples20 said:
At this point is there really a need? My phone doesnt lag that much that I need to over clock not to mention my battery life sucks already.
Click to expand...
Click to collapse
all of our battery life sucks unless you have the extended battery, im not getting THAT big of a battery drain according to the system monitor app, and it DOES make a difference on g1's that have lag issues (running tons of apps like i do)
in other threads, people have complained about the g1 not waking up quickly sometimes, ive yet to have that issue since ive clocked mine up to the 384MHz setting
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
The program installs a script on your sd card called ocx_tmp.sh and adjusts it that way, it'll write to /system as -rw (from what I've discussed with someone) would probably cause instability.
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Try it before and after setting the cpu freq in overclock and you'll see what I mean =)
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Gameloft said:
just notice the difference in speed. If you notice please post. And its not overclocking its just clocking. Overclocking will be beyond 528 MHz
Click to expand...
Click to collapse
andonnguyen said:
@woot, you do know that the default cpu freq on the G1 is ~384mHz. So you might want to change in your sig that you're overclocked to 384mHz lol.
Click to expand...
Click to collapse
im not as familiar with clocking/overclocking so i wasnt sure if i was clocking it to 384, overclocking it to 384, or what, so what would be the proper thing to put in my sig? lol because according to my first quote, true overclocking wouldnt be untill i went beyond 528, so from the view of my first quote, im not OVERclocking, im clocking, wheras your saying im overclocked
andonnguyen said:
The program will reset the cpu freq back down to 384mHz after the phone sleeps. You can verify this in terminal emulator by typing:
$su
#cat /proc/cpuinfo
Click to expand...
Click to collapse
so is it infact the program thats changing the cpu freq or is it the phone? if its the program, is this to avoid overworking the cpu without the demand?
andonnguyen said:
.
The program will reset the cpu freq back down to 384mHz after the phone sleeps.
Click to expand...
Click to collapse
by sleep do you mean turning the screen off using the power button? because i saw no change in my cpu freq when doing so using your commands
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
dont know, but i found this over at the android community:
Technical Features
Supports WCDMA/HSUPA and EGPRS networks
Multimedia Broadcasting Multicast Service (MBMS)
Integrated ARM11™ applications processor and ARM9™ modem
QDSP4000™ and QDSP5000™ high-performance digital signal processors (DSP)
528 MHz ARM11 Jazelle™ Java® hardware acceleration
Support for BREW® and Java applications
Qcamera™: Up to 6.0 megapixel digital images
Qtv™: Playback up to 30 fps VGA
Qcamcorder™: Record up to 24 fps QVGA
Up to 4 million triangles per second, and 133 million depth-tested, textured 3D pixels per second fill rate
gpsOne® position-location assisted-GPS (A-GPS) solution
Support for third-party operating systems
Digital audio support for MP3, aacPlus™ and Enhanced aacPlus
Integrated Mobile Digital Display Interface (MDDI), Bluetooth® 1.2 baseband processor and Wi-Fi® support
maybe that info will help? if not sorry
I remember reading somewhere by someone that it runs at 384 by default, and I think the post above confirms that...
ivanmmj said:
I thought the the CPU ran at 528 MHz by default? Or is it clocked dynamically and this forces it?
Click to expand...
Click to collapse
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
gui fluidity is definitely increased, and sluggishness between app switches and when the translucent app drawer opens up is gone. i like it, but to the average person there probably is no need to do it.
keep in mind this is also not overclocking the cpu, it's clocking it to its default spec. as it is an embedded arm, it is designed to run hot, so i guarantee you are in no danger of hurting your phone.
also, do not listen to people that claim there could be no gain from overclocking, just because the bus speed is slower than the cpu speed does NOT mean there will be no improvement in system performance. if that were the case, there'd be no use for 4ghz desktop processors.
cache still runs full speed, and common execution paths stay in cache meaning no prefetch from system memory, meaning BIG improvement in many cases. (that's why cache exists.)
damnoregonian said:
no, it runs at 384 by default, and clocks down even lower in the idle loop.
i am curious how this program works, as the normal cpufreq interfaces are not compiled in the kernel.
i've been running my phone for several months now at 528mhz, at a fairly minimal detriment to battery life.
i did however notice that without modifying the idle loop, the amount of cpu frequency switches even while the phone is not sleeping drops your average clock within a 10 second period to somewhere closer to 400mhz.
after modifying the idle loop to not switch frequency so often, i was able to get 27.4fps out of neocore w/o sound, and 22.7fps w/ sound.
gui fluidity and responsiveness is greatly improved. sluggishness if app switching and the translucent app drawer are completely gone.
for many i imagine this means there isn't really any reason to clock the cpu up to its stock speed, but to each their own.
my overall caffeine benchmark score was 582.
battery life impact is there, but fairly small. phone lasts for about a day and a half now where it used to last for sometimes 2. under heavy use, this is of course dramatically reduced.
Click to expand...
Click to collapse
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Holy crap. Used this @528MHz with Haykuro's version 4.5 apps to sd ROM and the osk works SO MUCH BETTER!!!! Also I got 25.6 fps on neocore... very smooth
wootroot said:
care to write up a how-to for getting the 582 consistantly and changing the idle loop?
Click to expand...
Click to collapse
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
A modded version of JF's ROM would ROM.
I DO notice the sluggishness and it bugs the heck out of me. (I switched from a WING with a 200MHz CPU, and although it IS faster than the wing, it doesn't seem significantly faster and seems to much slower when I open up the camera...
damnoregonian said:
writeup? no. it's a big process involving the android dev environment, a modified version of mkbootimg and unyaffs.
i will gladly post the kernel modifications for those who want to recompile the kernel to do so.
the bootloader sets the clock speed, and the idle loop simply clocks down to a preset and back up to whatever it was previously after x milliseconds of inactivity (not to be confused with sleep) it's kind of a poor man's cpufreq arbitrator.
so on top of tweaking the idle loop to not drop down as often, you also have to explicitly set the frequency in the kernel upon bootup, or it will bet set at what it thinks is full speed, which is 384.
Click to expand...
Click to collapse
that involved eh?
thanks for this post though, now i understand more about the idle loop and why the cpu freq resets with each reboot
maybe someone can take this stuff further like he said, that kind of stuff would be worth the dollar, imo more than a dollar
well... i don't mind providing basic procedure and source, i just don't want to get dragged into level 1 support of the procedure.
i'll go ahead and package up some source, prebuilt boot images based on JF's RC33 (which is what i run) and a basic procedure.
Subject says it all, 200MHZ sometimes doesn't cut in, if we need the speed, what is the best app out there ?
Thanks in advance
Found the solution...
Thanks for looking at the thread ... It was shinny isn't it.
Don't waste your time, PPC CPU can't be overclocked
No?!?! look this!
xhtc said:
Don't waste your time, PPC CPU can't be overclocked
Click to expand...
Click to collapse
You really need to do some research my friend.
Alright, let me save your time. Just search for Omapclockkeep, you'll clear your old taboo.
Just for the information, i have happily cruised my VIVA's CPU at 250MHZ, battery life is ok, not much affected.
Battery lasts 2 days with occasional WIFI plus Bluetooth.
3 apps
I've seen 3 apps so far that promisses the posibility to OC ppc...
Omapclockkeep
(posted in this thread)
Speed Booster
_www .teksoftco. com/index.php?section=speedbooster_
Pocket Hack Master
_www .wizcode. com/products/view/pocket_hack_master_
and pocket hack master even says it can prolong battery life (they also have another app called Pocket Battery Analyzer that seems good)
Anyone tried the apps? do they really work?
su8044 said:
I've seen 3 apps so far that promisses the posibility to OC ppc...
Omapclockkeep
(posted in this thread)
Speed Booster
_www .teksoftco. com/index.php?section=speedbooster_
Pocket Hack Master
_www .wizcode. com/products/view/pocket_hack_master_
and pocket hack master even says it can prolong battery life (they also have another app called Pocket Battery Analyzer that seems good)
Anyone tried the apps? do they really work?
Click to expand...
Click to collapse
I am using Omap keep cause you can keep the default speed at ideal and as soon as you start using it, you can set the speed like 250 and gain the extra performance through overclocking...
I'm using Homescreen++, which has a great overclock utility called CPU Scaler. It dynamically overclocks the CPU when the phone actually requires it, therefore saving lots of battery life. It also reduces the speed when it's idle to save even more. You just give it a min, max and boost value(when apps are really demanding) and it does the rest. It also monitors power consumption(maH, mW) and CPU temp. Good stuff.
zuperxtreme said:
I'm using Homescreen++, which has a great overclock utility called CPU Scaler. It dynamically overclocks the CPU when the phone actually requires it, therefore saving lots of battery life. It also reduces the speed when it's idle to save even more. You just give it a min, max and boost value(when apps are really demanding) and it does the rest. It also monitors power consumption(maH, mW) and CPU temp. Good stuff.
Click to expand...
Click to collapse
I have used it and my personal experience of using PPC for last 5 years says anything that monitors eat battery...
haha, yeah obviously, but every bit counts, no?
http://forum.xda-developers.com/showthread.php?t=682663
I just wanted to point out the the leo/hd2 cpu speed app works on the expo.
Installed great, but I cant verify the reclock speed... Im not sure if it is running faster or not. What speed did you set yours to?
i just left my cpu at the default.
Interesting little program, found that my Expo was stable up till 1115, and anything above that it froze. But basically you have to be plugged in to use anything about the 900 MHz, so, unless you want to disable auto-scaling on the CPU it's not of much use.
yeah I am quite disappointed that lg did not make an extended battery for the expo.
Please read this first, I'm pretty sure the problem is linked to this accident:
http://forum.xda-developers.com/showthread.php?t=1056606
For a short time my phone is lacking performance when it isn't connected to something (slow menu animations, snatchy performance in games etc.). Quadrant Benchmark proofs that circumstance too. Without connection my device achieves 'bout 500 points, when it is connected it gets ca. 1000 points. With "CPU Master Free" I've clocked the SGS once to 1Ghz and once to 1,2GHz. In both cases the performance gets better, but still is not as good as when the phone would be charged. Only then it really runs smooth.
I hardly expect you guys can give me another solution than sending the SGS to the repair service, 'coz imho the GPU has suffered certain damage...
nidschki said:
Please read this first, I'm pretty sure the problem is linked to this accident:
http://forum.xda-developers.com/showthread.php?t=1056606
For a short time my phone is lacking performance when it isn't connected to something (slow menu animations, snatchy performance in games etc.). Quadrant Benchmark proofs that circumstance too. Without connection my device achieves 'bout 500 points, when it is connected it gets ca. 1000 points. With "CPU Master Free" I've clocked the SGS once to 1Ghz and once to 1,2GHz. In both cases the performance gets better, but still is not as good as when the phone would be charged. Only then it really runs smooth.
I hardly expect you guys can give me another solution than sending the SGS to the repair service, 'coz imho the GPU has suffered certain damage...
Click to expand...
Click to collapse
hmm, no idea about any of this so I might as well give you a bump
If I remember there was programs like SetCpu that would set different behavior on charge and no charge. But was a loong time ago. Since I have no idea what rom or kernel you use. Are you sure there is not program/setting/rom setting active that underclocks your SGS whilst not on charge?
Sorry, forgot to mention: I'm using Goatrip's ROM 1.9 with CF Kernel.
I just have a few apps installed, none of them would under- or overclock the system. And as I sad, i don't know how but for me it seems that the problem is linked to the accident. At least it's somehow related to the battery.