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.
ive been reading alot on here and people have been talking about the set cpu and over clocking. i tried searching but i cant come up with anything. i just wanted a quick explination of what it is exactly and what affect makeing a change in these settings has and how to change these settings. i just got the whole swap thing down so now im tryin to figure this out. im running the jacski/modaco 1.5.1 hero. i also know there is a set cpu app. should i use this or is it built into the rom already. thanx for the hlep guys
Never use "overclocking" apps on Hero, you will probably find that it will slow the phone down, aswell as drain your battery faster. CPU scaling is built in to almost all ROMs, so it's not really worth it at all.
It is referring to the cpu processor speed, it is supposed to be 528 and with you running a custom rom, then it already has it scaled to 528 so you do not need any adjustment
ok cool guys thanx for the quick info. im not gunna bother messin with it then. i was like oh man im gunna have to learn another set of commands and take down some more notes.lol
Well the custom roms r scaled up to 528. Buts its more like 346 to 528 instead of the stock 128 to 346. So over clocking will drain battery fatser but it will push the processor to the max. Like adriank said overclocking on hero won't give u more speed but bog the system more. Does anyone know why this is. I'm running cyan and I have 528 min and max with the overclock widget. I crave speed and fluidity out of my g1!
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.
Ok. i have refraind from asking questions for quite some time. I have lurked, and read and read and read. i learned how to flash roms and kernels and most otherthings i want to do without bothering anyone with noob questions...up until now.
I flashed the suckerpuch #50 kernel in attempts to try out 1.4ghz, but unless im completely missing something my phone dosnt ever seem to go above 1 ghz on this kernel. im not positive this is the case, but heres what leads me to beleive it:
cpu usage widget on my screen never shows above 1ghz, while a different 1.2ghz OC i tired shows it peaking up to 1.2 right after boot, and if i exit quadrant it shows 1.2 for a sec before dropping back down, same with any 3d game, when i quickly close it and look at the widget, it will show running at 1.2. Yet suckerpuch never shows above 1.0 UNLESS i run CPUsetting and set it to "performace" which it then appears to be running at 1.4 AT ALL TIMES, and the phone isnt stable so thats a no go.
am i missing some key piece of information here? did i flash it wrong? is there some other type of modification i need to do to get it to actually run at 1.4?
ive read through the suckerpunch #50 opening posts multiple times and i believe it tells me i need to modify some file or other, possibly, but im not understanding.
any info/help would be much appreciated!
P.S. this forum, the devs, and all the things supplied to make my phone awesome are absolutley great.
I believe SuckerPunch is set to 1Ghz as default unless you change the setting with Voltage Control (or SetCPU). Mind you that 1.4Ghz is not run well on a lot of devices and may cause freezing. And I'm glad some people take up reading before asking questions
p.p.s- im aware not to use set CPU.
honestly i cant see the point of it with any kernel. dosnt seem to do anything.
koreancanuck said:
I believe SuckerPunch is set to 1Ghz as default unless you change the setting with Voltage Control (or SetCPU). Mind you that 1.4Ghz is not run well on a lot of devices and may cause freezing. And I'm glad some people take up reading before asking questions
Click to expand...
Click to collapse
yeah im using voltage control- minus 125 on all and the phone seems to work well.
i just find it weird that the kernel peaks at 1ghz, where as another peaks at 1.2ghz (both without use of setCPU, and WITH use of Voltage control)
when i was using setCPU and putting it on performance, i could see it was running at 1.4, pretty much at ALL TIMES. MOST things ont he phone worked well, ultra fast. the problems i noticed is that neocore would freeze (which i understand to be a sign of instability) and speedtest would either give me REALY slow speeds, or force close every time. were as set on conservative it would work perfectly and neocore wouldnt freeze.
oFUNGUSo said:
yeah im using voltage control- minus 125 on all and the phone seems to work well.
i just find it weird that the kernel peaks at 1ghz, where as another peaks at 1.2ghz (both without use of setCPU, and WITH use of Voltage control)
when i was using setCPU and putting it on performance, i could see it was running at 1.4, pretty much at ALL TIMES. MOST things ont he phone worked well, ultra fast. the problems i noticed is that neocore would freeze (which i understand to be a sign of instability) and speedtest would either give me REALY slow speeds, or force close every time. were as set on conservative it would work perfectly and neocore wouldnt freeze.
Click to expand...
Click to collapse
I guarantee you you cannot run -125 at 1.4GHz, unless you have some kind of wonder-phone.
In Voltage Control, you're set to 1.4GHz, correct?
If you are, have you made sure to enable the 1.4GHz state in Voltage Control via the bottom menu as well? If you don't, even though you're set at 1.4GHz it will not run at that.
Auridran said:
I guarantee you you cannot run -125 at 1.4GHz, unless you have some kind of wonder-phone.
In Voltage Control, you're set to 1.4GHz, correct?
If you are, have you made sure to enable the 1.4GHz state in Voltage Control via the bottom menu as well? If you don't, even though you're set at 1.4GHz it will not run at that.
Click to expand...
Click to collapse
my bad, im running -125 on i think its the gb 1.2ghx kernel. thats working fine.
im going to reflash #50 and try what you said.....though im pretty sure i already had it set. i know i was setting the mv from 100 up to 1400
ok i flahsed back to #50, and went into voltage control. it DID cap my freq at 1000, i changed it and set 100 through 1400 to -75mv.
i ran stress test for about 30 seconds and exited, and my CPU widget shows 99% usegage at 1ghz
hmm
i flashed back to gb reorient 1.2ghz and during boot up as soon as the CPU widget loaded it shows 1.2ghz. ran stress test again and exited in the middle of it, widget showed 99% usage at 1.2ghz.
i realyl dont know what im missing here, but it does seem as thought the suckerpunch #50 is not running above 1ghz for me.
comparing all forms of benchmark type tests between the two kernels, everything EXPCEPT necore is scoreing better on the 1.2 kernel. neocore onthe 1.3 kernel is giving me 55.4 fps, whereas on the 1.4 kernel its giving me 65 and some change fps. i know benchmark scores arent that meaningfull in some cases, and on the #50 thread it even states that some may be lower on that kernel.......but i swear ive done something wrong because i dont see how it can be running at 1.4
oFUNGUSo said:
ok i flahsed back to #50, and went into voltage control. it DID cap my freq at 1000, i changed it and set 100 through 1400 to -75mv.
i ran stress test for about 30 seconds and exited, and my CPU widget shows 99% usegage at 1ghz
hmm
i flashed back to gb reorient 1.2ghz and during boot up as soon as the CPU widget loaded it shows 1.2ghz. ran stress test again and exited in the middle of it, widget showed 99% usage at 1.2ghz.
i realyl dont know what im missing here, but it does seem as thought the suckerpunch #50 is not running above 1ghz for me.
comparing all forms of benchmark type tests between the two kernels, everything EXPCEPT necore is scoreing better on the 1.2 kernel. neocore onthe 1.3 kernel is giving me 55.4 fps, whereas on the 1.4 kernel its giving me 65 and some change fps. i know benchmark scores arent that meaningfull in some cases, and on the #50 thread it even states that some may be lower on that kernel.......but i swear ive done something wrong because i dont see how it can be running at 1.4
Click to expand...
Click to collapse
Like I said in my previous post, are you actually enabling the frequencies or just selecting 1.4GHz as the max in Voltage Control?
You have to enable 1.4GHz in the "states" menu of Voltage Control for it to work, as well as set 1.4GHz as the max in Voltage Control. SuckerPunch does not overclock by default because a lot of phones do not play nicely with 1.4GHz.
Auridran said:
Like I said in my previous post, are you actually enabling the frequencies or just selecting 1.4GHz as the max in Voltage Control?
You have to enable 1.4GHz in the "states" menu of Voltage Control for it to work, as well as set 1.4GHz as the max in Voltage Control. SuckerPunch does not overclock by default because a lot of phones do not play nicely with 1.4GHz.
Click to expand...
Click to collapse
ha. this had me confused......there was no "states" menu. that got me pokeing around and then i realized i didnt have the newest version of voltage control(had 2.0 instead of 3.0). i do NOW. and i see the option to select the states. so, i selected 7 states up to 1400. and selected the max frequency of 1400. set a voltage for all, and applied.
still the same result. lol. its not running over 1ghz according to cpu stats. it SAYS it frequency range is from 100 to 1400. but it aint going over 1000.
*sigh* there has to be something else im missing
For suckerpunch's new builds, it's set to startup at 1ghz. After like 15mins. you can run some tests and it should be at max clock.
YESSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ITS WORKING! and dayum i see and improvement in stats! benchmarks look fantasitc, neocore isnt freezeing, phone isnt freezing on lockscreen.....will have to run stress test for a while to see for sure but it appears stable!
1400 -50
1300 -50
1200 -75
1120 -75
1000-75
800- 100
600-100
400-100
i really cant figure out the right way to do that, but it seems to be working so far
for one, i needed the newest version of voltage control.....for two, im thinking that i was supposed to wipe the davik cache before install, because it did a different song and dance when i did that. for three.....for whatever reson the 1000hz version didnt seem to want to work for me....and finally....waiting for a while after the phone booted up i did see the CPU start to jump up to 1.4.
thanks guys!