yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] buttkicker:
I know this method works.

You can download "Neocore" from Market and test it.

Neocore is an OpenGL graphics performance benchmark tool.

I'm posting the before and after screenshots for reference.

The benchmark was run without audio.

The CPU was overclocked to the following setting.

MAX = 528000

MIN = 128000
[G1 Android Development] buttkicker:
You are welcome and thanks for creating an app.
[G1 Android Development] andonnguyen:
i tested neocore and my fps was 26.4 =]
[G1 Android Development] KyleK29:
Question. What init.rc are you editing?

I remember a few builds (of official Google) there was a system/init.rc as well as a /init.rc. On Haykuro, I don't seem to have a system/init.rc . Are you editing the /init.rc ?

Does it matter where that is? Mine has tons of scripts in it (not mine, from Haykuro's build).
[G1 Android Development] reuthermonkey:
Does the Open Overclocker app stay active after a reboot? Or do we need to re-set our preferred settings each time re reboot?
[G1 Android Development] buttkicker:
I did not modify any init.rc

I mentioned in the original post that I dont know how to do this.

Right now I am using GScript to apply settings after reboot.

Alternatively, you can download the app from the Application sub-forum.
[G1 Android Development] KyleK29:
Ahh, I see. I didn't know that the JF builds differed on the init.rc's. Explains why I am missing the system one which I had on the JF build.

I was going to do it with a GScript. I assume you're just hitting a home-screen shortcut after rebooting?
[G1 Android Development] buttkicker:
Yes, I am launching GScript and executing a saved script.
[G1 Android Development] darrin0101:
I'm curious to see what it averages over several benchmarks, because while it is a 10% increase, 2fps really isn't that much. Unless the scaling really isn't working, then it should show a little higher by bumping the min up.

Not that there are really any intensive games out there yet. :(
[G1 Android Development] APrinceAmongMen:
Do NOT use 128/528. It hurts battery life and the processor. The jump between 528 and the idle frequency is big enough to require extra circuits to be switched on. That does two things... slows down the gain of the processor speed and hurts battery life more than simply running permanently on 528. I'd suggest keeping the range jump shorter. Just make a script and run that script whenever you are going to need the speed boost.
[G1 Android Development] ultimind:
Seems like its going to take some experimenting to find a good balance between speeding up the phone and extending the battery life.
[G1 Android Development] kusotare:
Yeah, I've got Openoverclocker running right now and my jump is 128-384. it's only a twofold jump, so I'm going to test it over the next day or so and see how my battery life fares. If it doesnt show any kind of marked improvement, I''ll fiddle with some other speeds.
[G1 Android Development] KyleK29:
I see. I've been trying that myself, but I can't get GScript to execute the script. It just sits there. I'm assuming it might be from the lack of a superuser whitelist, as none of my scripts work.

Did you have to do anything to the Haykuro build to get Gscript to work correctly?
[G1 Android Development] ultimind:
If you want to see a difference in speed, set the min/max to 528mhz, then use the onscreen keyboard (Running 5.0.2H). Now set it to 128/128 and use the keyboard again. HUGE difference in responsiveness.

The keyboard is amazingly responsive when set to 528mhz.
[G1 Android Development] SpyderMS:
I see no such app on the Market :(
[G1 Android Development] MarcusMaximus04@gmail.com:
Odd... it's under applications->tools. Alternatively if you really can't find it anywhere go to Dream Applications and Games here on xda-developers and I have it available for download.
[G1 Android Development] MarcusMaximus04@gmail.com:
Hmm I've been noticing while playing around with my app, it seems like no matter what you set it to, it won't go to one of the "in between" speeds. I set min/max to 400MHz and it consistently shows 527.15 in /proc/cpuinfo. Seems as though there's only a limited number of cpu settings the operating system will actually take...
[G1 Android Development] robpet2:
just saw this app a few min ago ( overclocker app ).. checking it out now... it was only a matter of time before a overclock app came to the light.
[G1 Android Development] CardinS2U:
tried that echo stuff..it worked out wellll very very fast

I got the giant/extend battery so dont mind running thi sall the time. love it

but is there an optimal settings for its?

having it always run like this in sleep mode is wate of power
[G1 Android Development] andonnguyen:
maybe this thread will help?

http://xdaforums.com/showthread.php?t=470967

or this one?

https://groups.google.com/group/and...hread/ede9ba8c787661a1/3b763f027a41ff56?pli=1

Or probably not, im not sure haha.
[G1 Android Development] buttkicker:
I did install superuser whitelist.

That app is needed for this to work.
[G1 Android Development] jriley60:
i wonder when it will be possible to make the phone overclock only when using specific apps. like set to 528 when vk is open ect... to bad i didn't stay in school : )
[G1 Android Development] ultra spikey:
I'm trying this on a JF build and when I try the commands on the 1st post, I get a "directory nonexistent" error. Any ideas?

Also, openoverclocker does not work either.
[G1 Android Development] buttkicker:
Can you post the output of this command.

Make sure you are running as su.

ls -l /sys/devices/system/cpu/cpu0/cpufreq
[G1 Android Development] ultra spikey:
Ran as su..."no such file or directory"
[G1 Android Development] BSDADON:
i have the same issue "no such file or directory". i also tried setcpu and that froze my phone when i set 528MHz. could it just be a hardware issue?
[G1 Android Development] buttkicker:
Strange...what firmware are you running?
[G1 Android Development] MarcusMaximus04@gmail.com:
hmm just a blind guess but I'd bet that if they ran the other overclocking command(ripped from the overclocking app that was first on the market) it would work. I think in my next version I'll just run both and whichever one doesn't work just won't go through :D
[G1 Android Development] ultra spikey:
I'm on JF RC33 1.43
[G1 Android Development] cyricc:
Try running

# find /sys -name *freq

and look for scaling_max_freq and scaling_min_freq in the output.
[G1 Android Development] BSDADON:
i got this when i typed that. didnt get anything else

/sys/class/i2c-adapter/i2c-0/0-0062/grpfreq
[G1 Android Development] BSDADON:
where can i find those commands?:confused:
[G1 Android Development] MarcusMaximus04@gmail.com:
Try doing this:

mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mkdir /system/debugfs
mount /system/debugfs /system/debugfs -t debugfs
echo '528000000' > /system/debugfs/clk_rate/acpu_clk

And let me know if it changes.
[G1 Android Development] BSDADON:
that worked. is that going to stay at 528 during sleep mode also?
[G1 Android Development] MarcusMaximus04@gmail.com:
I'm not actually sure, that was pulled from a script in another app. I think it might have said somewhere in that thread but I'm not really sure. Thread is at

http://xdaforums.com/showthread.php?t=501986

I'll look into it tonight and if I can get it to work reliably I'll throw it in my app to make it a bit easier.
[G1 Android Development] KyleK29:
Yeah, I installed that yesterday. *edit* removed the other part, I got it working. For some reason the SU Whitelist took a few reboots.
[G1 Android Development] BSDADON:
this worked then my phone froze. just tried it again and it froze it again. havent even been able to run neocore to see the difference, as soon as i go back to the home screen it locks up on me
[G1 Android Development] reuthermonkey:
What are the results you are seeing from setting your max to 528? I have mine set at 128 min - 384 max, and it nicely seems to be jumping back and forth easily (ie 128 when idle, 384 when playing music). I haven't tested battery life just yet, but it seems stable.

For those of you with 528, is your phone running stable? How much worse is your battery life? Is your battery getting even hotter?
[G1 Android Development] KyleK29:
Hey Marcus, can I make a few suggestions (may have already been covered) for this app?

- Option to "apply on startup"

- Option to "minimize on startup" (so when you launch the shortcut, it applies and goes to the background or closes)

- Ability to save the settings once they're set. Just a simple txt file on the SDcard or something.

- Meter showing the Processor's current speed.

I have mine set at 384-528. So I'll let you know if I see anything.
[G1 Android Development] MarcusMaximus04@gmail.com:
Heh thanks for the suggestions, I've actually said in a couple posts around these forums all of those are planned for the next revision... so when that time comes you should be pretty happy :)
[G1 Android Development] andonnguyen:
Been running at 528 constantly for the past couple of days, battery life is better, and the phone is roughly the same temp as setting the cpu at 384 only (as reported by my any cut shortcut), and the phone is faster.

Side note: all the emulators on the marketplace are actually playable now. =]
[G1 Android Development] MarcusMaximus04@gmail.com:
Holy crap you're right!! Mario isn't in slow motion anymore!!!
[G1 Android Development] KyleK29:
Did someone say Mario?

I may actually have to see what emulators are out there now.
[G1 Android Development] buttkicker:
I'm on 5.0.2H

I'm going to test on other builds tonight and see if it works.

I will report back later.
[G1 Android Development] buttkicker:
Ok, I can confirm that this method works on all Haykuro's builds.

The system on JF builds is different and does not have the same files.

This will need further research.
[G1 Android Development] MrOuch:
works great on my g1, any possibility of a program that does it at startup?
[G1 Android Development] qingcai:
I set the scale low to 128, scan high to 256M, works fine.
[G1 Android Development] coolbho3000:
Maybe that isn't such a good idea. If the phone suddenly decides to be unstable (for any reason) at 528MHz, it could cause you to freeze at every startup, then you may have to wipe to recover your phone.

I'll be updating setcpu to support the android 1.5 too (while maintaining its freezing compatibility with 1.1), and post the apks in a separate thread, and if I get to cleaning the source I will release that as well.

I've found that only the following frequencies actually work on the dream, in kHz:

19200 (unbearably slow)

122880 (really slow)

128000

245760

248000

384000

528000 (very often freezes by 1.1 method (overclock/setcpu))

Unfortunately I could not find any "middle ground" between 384 and 528... it was all or nothing. If anyone manages to find any more, please pst them.
[G1 Android Development] reuthermonkey:
i've been using this pretty well on the g and h builds, and the h build definitely sees an improvement with the higher settings... Makes it much more responsive
[G1 Android Development] KyleK29:
Agree. I took my phone off the charger at 7:30am. It is now 5pm. I'm at 85% with light use (reading email, quick browse of the network, 15minutes of playing with NesEmu). Not bad for 9.5hrs.

I'm using 384(min)/528(high)
[G1 Android Development] unrafa:
Min speed 81920

Max 528000

I espect to double battery life, since im checking and phone is runnning at only 81920 when sleeping (instead of default 248000) that is less than half the speed. Phone running very nice, jumping to 528000 when using screen and going back to 81920 sleeping. I'll post back to tell how it goes.
[G1 Android Development] coolbho3000:
81920 works? Do you know any other frequencies that work?
[G1 Android Development] AbsoluteDesignz:
I tested it at 750....and it would not go above 527.15

I kinda like that
[G1 Android Development] dwang:
So people have set the speed to 528 mhz and have actually gotten better battery life?

how is that possible?

What is the best max and min combination? Somebody said 528/128 isn't good for the battery life because it takes more effort to go from 128 to 528 and then back down?
[G1 Android Development] dwang:
This would be great for the power manager app.

When plugged in set the cpu to 528 mhz.

When on battery set speed to dynamic.

When battery is low, set it to 128 mhz.
[G1 Android Development] unrafa:
Yes, and i am changing values.

echo 19200 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo 528000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

As long as i know cpu speed ranges are:

19200, 91920 122880 245760 384000 528000

Once given Min: 19200 Max 528000, android kernel module "ondemand" should take care of speed automatically "on demand". So the cpu will switch automatically between all speeds ranging from 19200 to 528000 as needed.

I think the phone will run always at 528000 when touching screen doing things, it will run at 19200 when sleeping, and it will run maybe at 91920 or 122880 if its playing mp3 with screen off. It all belongs at how well does the kernel managing the speeds.

Best way to know all frequencies available is looking at the source code, wich im not wishing to do because i am lazy, but it is there, source code changes almost every day so we will have to look at source code of new releases as we install it to know possible new or deleted frequencies.

In source code file is clock.c and search for word "CPUFREQ_TABLE_MAX" and you will find the frequencies table.

Now somebody have to come up telling us how to make it permanent, editing /init.rc doesn't work because / is ramdisk and clears after reboots, it cant be difficult to figure out where is the original init.rc to edit and make those speeds permanent...
[G1 Android Development] buttkicker:
Based on this post, the available frequencies are

19200

61440

81920

96000

122880

128000

176000

192000

245760

256000

264000

352000

384000

528000

However, when I tested the operating frequency did not go below 122880 when in standby.

Right now I am testing at 176000/528000, as according to the linked post, these two frequencies use the same clock.

I will report back on the battery life in a few days.
[G1 Android Development] thulinhlun:
Ur idea is really good but if u put like that, there will be no progarm running base for it ( to put the needed CPU for the things are running) so there will be even slower.

Beside....this is PHONE's CPU, not computer cpu that are super good, u making it need to keep changing the cpu freq = Slower (time to change the speed), killing the CPU (CPU freq keep changing from slowest to fastest), and die faster (it cost alot of battery in an amount of time to change the speed).

THis is just my idea ( i dont really know about it) so correct me if im wrong
[G1 Android Development] sino8r:
Anyone have missed/delayed calls due to underclocking while in standby yet? I know it used to be an issue with WM6 and 6.1 with certain ported roms on my htc wizard. Currently, I am just overclocking when needed. Overclocking too high upon boot is dangerous to me but I'm sure that has already been stated and is therefore is a redundant statement.
[G1 Android Development] unrafa:
After some testing i see setting Min Speed below 128000 makes /proc/cpuinfo reporting a wrong speed of only 19.2 (lowest possible value) also making the phone unresponsive when unplugged from the computer, but not showing bad simptoms when plugged in via usb.

looks to me like a bug or not yet well implemented cpu scaling. I hope its fixed in future releases.

Im using saphire port 5.0.2.Hr2

Linux localhost 2.6.27-04102009-daproy #4 PREEMPT Fri Apr 10 21:47:46 PDT 2009 armv6l unknown
[G1 Android Development] unrafa:
You can be right i dont know, but i think it doesn't make sense programmers writing down a currently used table with all those frequencies in the source code and expect them to fail if used. I think if the frequencies are there and still fail is because the code isn't finished yet.. but its all a guess..
[G1 Android Development] MarcusMaximus04@gmail.com:
To some degree this makes sense. If you're constantly switching between 528 and some other frequency it'll kill battery life just in the effort to constantly change the speed. By comparison, just keeping it at 528 isn't that big of a deal. You could probably get even better battery life if you force it to stay at 384MHz always.
[G1 Android Development] KyleK29:
Been running at 384/528 for the past few days. No issues to speak of. Phone is running great, and the battery seems good. Haven't noticed any increased draw.
[G1 Android Development] daproy:
These settings can be made permanent by setting them at kernel compile time. I had them set to:

CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX=384000

CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN=245760

in the haykuro build kernels. If other values yield better performance without any downside I can change these and recompile for the next release.
[G1 Android Development] dwang:
I don't think these values should be changed in the kernel until we get more statistics on stability and battery life.

I noticed some weird slowdowns and crashes when I changed max to 524. I can't be sure if its due to the cpu speed change or something else though.
[G1 Android Development] Liquid602:
don't want to sound like a noob or anything but... what does overclocking do??

EDIT

eh, just googled it, sounds a bit too complicated for me to dive into at this point. lol
[G1 Android Development] buttkicker:
@daproy

I have been running at 128/528 for about 2 weeks now. No issues yet.

I am willing to test the new kernel with above values, if you can compile one.
[G1 Android Development] daproy:
Not sure if this is correct. The switch between speeds is done in a stepwise fashion between the set of available frequencies.

From acpuclock.c:

while (cur_s != tgt_s) {
/*
* Always jump to target freq if within 256mhz, regulardless of
* PLL. If differnece is greater, use the predefinied
* steppings in the table.
*/
int d = abs((int)(cur_s->a11clk_khz - tgt_s->a11clk_khz));
if (d > drv_state.max_speed_delta_khz) {
/* Step up or down depending on target vs current. */
int clk_index = tgt_s->a11clk_khz > cur_s->a11clk_khz ?
cur_s->up : cur_s->down;
[G1 Android Development] daproy:
Seems to me like this is the most "sane" setting. Table stepping up/down is optimized for 256mhz jumps while staying on the same PLL. So of the currently used frequencies in the kernel:

{ 19200, ACPU_PLL_TCXO, 0, 0, 19200, 0, VDD_0, 30720, 0, 0, 4 },
{ 122880, ACPU_PLL_0, 4, 1, 61440, 1, VDD_3, 61440, 0, 0, 4 },
{ 128000, ACPU_PLL_1, 1, 5, 64000, 1, VDD_3, 61440, 0, 0, 6 },
{ 176000, ACPU_PLL_2, 2, 5, 88000, 1, VDD_3, 61440, 0, 0, 5 },
{ 245760, ACPU_PLL_0, 4, 0, 81920, 2, VDD_4, 61440, 0, 0, 5 },
{ 352000, ACPU_PLL_2, 2, 2, 88000, 3, VDD_5, 128000, 0, 3, 7 },
{ 384000, ACPU_PLL_1, 1, 1, 128000, 2, VDD_6, 128000, 0, 2, -1 },
{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

It should jump between 176000 to 352000 to 528000 and vice versa.
[G1 Android Development] emms007:
Hello Daproy,

Are you personally running a kernel with those settings set by default as you showed before?

I like to consider that this is not really overclocking as it's the design cpu speed for phone hardware. Plus everything seems to be doing it without any glitch.

I wonder if once set in the kernel this settings could be over-righted once again by any the overclocking apps for a specific situation ie: low battery.

By the way, different topic, I wonder if you have you tried to include the Multitouch patches to synaptics_i2c_rmi.c with latest kernel versions? Is there any problem with that?
[G1 Android Development] sandshrimp:
Overclocker on Power Manager

What would be ideal is to have an overclock feature in Power Manager so you can set a profile to overclock when the phone is plugged in or when at high battery. If battery goes below a certain point, then it will lower the CPU.

I use the phone in my car for both music and navigation (which takes a lot of CPU). In the car i have the phone plugged in with the profile of screen bright and always on. The CPU addition would be key and would pay more money for this app.

If you agree send the developer an email. His site link is below. I also asked to make it work with 1.5:-)

This is our grassroots movement;-)

http://nettogo.net/powermanager/
[G1 Android Development] dwang:
I'm definitely noticing issues when running at 528 mhz.

The browser seems to crash more often and dxtop will return to a blank screen quite often.

Switching back to 384 mhz and all the issues disappear.

I'm guessing there are some timing issues when running at the higher clock speed.
[G1 Android Development] chamelieon:
cofirm this overclock command works on adp 1.5H
[G1 Android Development] Dutchmda:
confirmed this works on JACHero 1.4 rom as well, actually helps a lot with the lag, and force close issues at this time in that build. great work, i mean leaps and bounds everyother day with android i love it.
[G1 Android Development] CoopZor:
Guys, its have been a while now.

What are your thoughts on this topic ?

Do you still use the overclocked settings ?

I like to know, a little bit more MHz wont harm my beloved G1.
[G1 Android Development] buttkicker:
it is integrated into several roms at this point.

also. maximus has an app that does this.

You don't need to use these commands.
[Touch HD Themes and Apps] stpete111:
I do realize that the RAM usage could vary greatly with WAD2 depending on what skin you use, but I'm just looking for an alternative to Manila, as it really seems to use quite a bit of RAM.

Thoughts/recommendations on the other 2 mentioned, before I purchase?
[MDA III, XDA III, PDA2k, 9090 ROM Development] mercantigo:
Hi guys!

I searched and didnt find this information...

I just bought a used HTC Blue Angel / Qtek 9090.

But it comes with no memory card.

So, I'll have to buy one. I was wondering about a 8 card...

But I heard that the BA only support 2 gb card, but on WM 2003. This limitation is true on WM 6?

Does it have support to 8gb SDHC cards?

Thanks in advance!
[MDA III, XDA III, PDA2k, 9090 ROM Development] Chef_Tony:
no it does not have any support for sd2.0 or sdhc cards, meaning even 4gb is also out of the picture as long as it's labeled sdhc, there are, however, 4gb sandisk cards that are not sdhc, that should work just fine. as there are no 8gb or above sd cards in the old sd standard.
[MDA III, XDA III, PDA2k, 9090 ROM Development] egzthunder1:
You seem to be new to the forums. Thank you for joining XDA-Developers.

Please take a minute to go over the Rules and Regulations of the forum.

Also, it seems that you are a Blue Angel owner, in which case I will encourage you to go over the BA forum regulations here

For questions, please use the search function in the site or simply Google for an answer. More than likely, your question has probably been answered before and the answer is floating around somewhere in the site. That being said, unless you are contributing to the site with either skins, roms, ports, new applications, programs, games, etc., please [highlight]do not[/highlight] open new threads. However, if you do have questions, you can post them either in the General Q&A section.

Thanks.
[MDA III, XDA III, PDA2k, 9090 ROM Development] mercantigo:
Thanks for your quick reply!

So, if I buy a non-SDHC card, only SD, with 4 gb, it will recognize 4gb, and not 2 gb?