yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] bunu:
So I just copy and paste the exact numbers into setcpu.txt? I'm asking this because the last time I used setcpu.txt there was a comma after each number.
[G1 Android Development] xillius200:
0o add the commas XD yeah there is meant to be commas after them except from the last one :)
[G1 Android Development] CLopez92868:
SetCPU.txt

Copy this. I copied it from mine. This works with mine.

19200,122880,128000,245760,384000,528000,614400,633600,652800,672000

This is one is it.
[G1 Android Development] bunu:
Grrr.....

It still freezes during the boot animation.

I am using the mytouch 3G so I cannot use console.

I have the latest setcpu and I know how to use the setcpu.txt

I have access to fastboot and adb.

So can anyone else help me? I would prefer to do it over adb or fastboot then using the phone's terminal emulator.
[G1 Android Development] CLopez92868:
SetCPU.txt

Mine froze at boot animation at first too.

you have this one right?> oc-cm-5.0.7-v2-boot.img

I can't paste(junior member).

try using the same commands on ADB. Try it like I said above.
[G1 Android Development] bunu:
ok.... (crosses fingers)
[G1 Android Development] ciervo5389:
i kept on getting texts saying like "re-read error at 0x00260000 (Out of Memory)"

saying theres no space left on my device when i know i have plenty.

edit: i just read earlier posts saying it doesnt work with terminal emulator or better terminal emulator......but i have a mt3g and cant use it recovery/console
[G1 Android Development] dumfuq:
[HOWTO] Overclock cm5.0.7-test1 for dummies ;)

First download the boot.img your gonna need

Next edit or create your /sd-ext/userinit.sh file (this is very important!)

you need to add the line:

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

to do this either

a) use vi or another text editor available on your phone or through adb shell

b) pull it off with adb, edit it on your computer and push it back

c) enter the following into terminal(only works if you don't have an exit statement in your script):

echo “echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq” >> /sd-ext/userinit.sh

or d) use your imagination just get that line in there.

If you don't have a /sd-ext/userinit.sh, you need to create one.

It can be as simple as:

#!/system/bin/sh
echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

Now after you have verified that the line is in your userinit script (and not after an 'exit') flash the image.

To do this there are two methods

fastboot method (preferred method)

from directory containing the boot.img type

adb shell reboot bootloader
fastboot flash boot oc-cm-5.0.7-v2-boot.img
fastboot reboot

obviously fastboot must already be set up for this to work and your phone must be plugged in to your computer.

terminal method

Place the boot.img at the root of your sdcard and type the following into terminal

su
flash_image boot /sdcard/oc-cm-5.0.7-v2-boot.img
reboot

When your phone reboots it will be time to find your frequency

You will either need to install setcpu or be comfortable within the terminal.

Setcpu Method:

install setcpu (available in the market)

the first time setcpu is run tell it to automatically scan for available frequencies or whatnot.

do not choose dream/sapphire

OR Terminal method:

type this in the terminal

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

except replace the 528000 with the frequency you want to test.

Available frequencies are:

122880, 128000, 245760, 384000, 528000, 537600, 556800, 576000, 595200, 614400, 633600, 652800, 672000

Test the frequencies (obviously just the ones above 528000)

Figure out what your highest stable frequency is and use the one just below it.

For example my phone runs 652800 with no problems so my magic number is 633600.

Now just make it permanent.

Either change the line we placed in your /sd-ext/userinit.sh file to reflect the frequency you want, or configure setcpu to set at boot or use profiles.

Reboot and your done.
[G1 Android Development] schtuka:
i guess we have to try it in fastboot.
[G1 Android Development] Barsa75:
Try to kill all applications in memory with a soft like task killer or estrongs task manager before launching the terminal and the flash_image command.
[G1 Android Development] bunu:
I managed to get this to work using the method on page 39. But everytime it is set above 528 mhz, my phone reboots like crazy. I managed to reset the cpu back to 528/528.
[G1 Android Development] ciervo5389:
Im pretty sure it worked, so after i type in the command and the only thing that pops up is the "#" that means it has workedcorrect?
[G1 Android Development] Ohsaka:
Is there any significance to the 19200 Mhz interval between the available frequencies at the high end? Like can I use frequency 650000 in my setcpu.txt file? Last time I did overclocking there was a FrontSideBus speed and Multipler on the CPU clock...
[G1 Android Development] tuffCookie:
userinit.sh file missing

i created a userinit.sh file as it was missing from /sd-ext

i included this code:

#!/system/bin/sh

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

now my problem:

i enable rw and copy the userinit.sh file to /sd-ext, but after i reboot the userinit.sh file is missing. i've tried using root explorer copy the file to /sd-ext and ADB to push to /sd-ext. the file just disappears and is no where to be found.

does anybody know what i'm doing wrong?

***** EDIT *****

is the /sd-ext folder looking for an EXT partition?

if this is the case, is it possible to place the userinit.sh file somewhere other than /sd-ext?

i never created an EXT partition on my sd card because i use a MT3G.
[G1 Android Development] dumfuq:
the numbers are significant. No you can not just put 650000 in the textfile.

However you do not need to use a setcpu.txt in this version.

just use the scan for available frequencies when setting up setcpu instead of the custom device option.

and yup just like your thinking

614400 = 19200 x 32

633600 = 19200 x 33

etc.
[G1 Android Development] schtuka:
yeah it does.
[G1 Android Development] dumfuq:
This is correct.

you have 5 options I can think of

1) create a ext partition

2) repack the rom with the command in an initscript or whatnot

3) set the frequency using adb while it's booting

4) let it boot at 672mhz and change it when your booted (won't work on many phones)

5) wait for someone to come up with a better idea

options 3&4 would have to be done everytime you booted
[G1 Android Development] tuffCookie:
ahhhh...ok. thanks for confirming.

i'll just do #1...:rolleyes:
[G1 Android Development] tissimo:
Im unclear on how to create the userinit.sh file? you just type that in a abd shell? or make it on the pc and with those lines in it and push it via adb?
[G1 Android Development] domenukk:
normally userinit.sh will also work if in system/bin folder o.O
[G1 Android Development] tuffCookie:
create it using a text editor such as Notepad++. save the file as "userinit.sh" (without the quotes). remove the .txt file extension if it appears on the file name.

then easiest thing to do is to ADB push it to /sd-ext. remember to set the permissions on it correctly!

chmod 755 if i'm not mistaken...
[G1 Android Development] dangambino:
fix_permissions first in terminal then flash boot.img. and follow instructions above. you will not get the "no memory message" if you fix_permissions first inb terminal;
[G1 Android Development] Naimand:
Could you change were it calls on the 20userinit file? That is where it tells you to put it on sd_ext.
[G1 Android Development] tuffCookie:
good idea...i'ma gonna check and report back.
[G1 Android Development] BopChie:
im a fail.. for the life of me i cant get this in.. i had it running like a champ on 4.2.14 but on 5.0.7 i get the out of memory errors if i flash in adb.. then in recovery through console it it says it cant fint the boot.img file (yes im typing it right "flash_image boot /sdcard/imagenamehere.img <enter>)

this is just killin me here .. and after it fails when i reboot i hang at my g1 screen and need to do a nand restore to bring it all back

:mad:

i'll keep reading/trying but any thoughts here?
[G1 Android Development] Naimand:
Did you mount the sdcard through console? Sorry if this is wrong it's been a while since I had a dream.
[G1 Android Development] tuffCookie:
ok, i just looked over the /system/etc/init.d/20userinit file and need confirmation as my coding skills are rusty. below is the original code:

#!/system/bin/sh
# call a userinit.sh script if it's present on the sdcard

if [ "$SD_EXT_DIRECTORY" = "" ];
then
SD_EXT_DIRECTORY=[B]/sd-ext[/B];
fi;

if [ -e $SD_EXT_DIRECTORY/userinit.sh ];
then
log -p i -t userinit "Executing $SD_EXT_DIRECTORY/userinit.sh";
busybox chmod +x $SD_EXT_DIRECTORY/userinit.sh;
logwrapper /system/bin/sh $SD_EXT_DIRECTORY/userinit.sh;
setprop cm.userinit.active 1;
fi;

if [ -d $SD_EXT_DIRECTORY/userinit.d ];
then
logwrapper busybox run-parts $SD_EXT_DIRECTORY/userinit.d;
setprop cm.userinit.active 1;
fi;

if i change the piece of code that is bolded to:

SD_EXT_DIRECTORY=/system/bin

will this work?
[G1 Android Development] tissimo:
Didn't get very far. My G1 would run ok at 576, but 595 run fine, but the SetCPU benchmarks weren't faster, 614 froze.
[G1 Android Development] Naimand:
It looks like that would be correct. Looks like it will call /system/bin/userinit.sh whenever things are executing.
[G1 Android Development] tuffCookie:
k, just wanted to make sure. testing right now. i just realized this probably won't be useful as most probably use an EXT partition. oh well...:p
[G1 Android Development] domenukk:
Most simple way: just add the line to the /init.d folder... :rolleyes:

try this for example:
[G1 Android Development] dangambino:
applied jit (found on cyan thread), and got this hack working at 613 mhz! over 4.1 on linpack score!!
[G1 Android Development] Sleepytime28:
Link to jit thread please.:)
[G1 Android Development] BopChie:
ok.. well i was on the pooper and tried it with the term emulater .. got a few mem errors but it completed and i am able to run @ 614.. not sure how it took with the errors though??

update: only pulling 2.65 in linpack does that seem right for 614?
[G1 Android Development] Nagoki:
Thanks alot, this is a useful little tutorial...:)
[G1 Android Development] domenukk:
worked fine for me. (instead of ext userinit :D)
[G1 Android Development] Ace42:
Yes...Compare it to 528, you arent running JIT so you dont have some crazy number. Dont be to concerned with these #'s if things are faster than you know the OC is good to go.
[G1 Android Development] teqvexed:
I have a MT3G running a fresh copy of Cyanogen's 2.1.

I followed post #402's instructions... worked successfully until I pushed it to 633 MHz, that gave me a crash and then I had to restore since it kept getting stuck at the android boot logo. It seems stable at 615 MHz.

Here are my benchmarks at 615 MHz:

Linpack score of 2.65 MFLOPS on average

SetCPU shortbench time of ~615 ms

SetCPU longbench time of ~10360 ms.

if i recall correctly, i was getting shortbench scores of around 615 ms under the previous build of cyanogenmod without any overclocking. I now get ~700 ms shortbench at the default 528 MHz.
[G1 Android Development] infinitybiff:
figured i'd host the OC patch for CM5.0.7

This is tested , working and stable on my htc dream with lastest radio and recovery

Download THIS zip file extract contents to where you adb.exe lives (same folder)

type the following commands in windows cmd

adb push userinit.sh /sd-ext

adb push ocboot.img /sdcard

stop here for a moment. I found that I needed to ensure I had all running apps closed before doing this. please nandroid before you do it. Its not my fault if you do it wrong and bork it. NEXT

abd shell

flash_image boot /sdcard/ocboot.img

reboot

Linkpack tests go from 2.3 to 2.7 with this patch. Phone is noticeably faster. custom set cpu file is required to clock this with set cpu. The userinit.sh automatically sets the clock to 633 max so you shouldn’t have to do a thing.
[G1 Android Development] gadget421:
I had this too.

in terminal push the menu button. push" reset term"

then flash oc boot.img

worked for me

mytouch 32b
[G1 Android Development] teqvexed:
***Issues:

Seems everything was okay so I decided to do a nandroid backup.

It wont successfully reboot, it restarts after a little while on the boot screen. Occasionally the lock screen will reappear, but it will be unresponsive. Thoughts? for now I've restored to my pre OC backup

***Resolved:

Followed post #433's instructions, but first wiped my SD card and repartitioned. I think there was an issue with that userinit.sh file and possibly my EXT partition.
[G1 Android Development] kristoff123:
Can someone post a kernel for cyan 4.2.15 with the in-between frequencies enabled? I think those freq's are going to be key in running this stable across the board - I will settle for 590 or whatever is around there. Thanks!
[G1 Android Development] cephasara:
eClair Laszlo overclock help

I cant get this to work with laszlo's eclair 5.2 rom with some modifications as posted by user "peshal". http://xdaforums.com/showthread.php?t=644529&page=16 I tried installing through recovery as well as I've tried to extract it and install it manually and no luck. I keep getting boot loops. The first time it wouldn't get to my boot screen. Now it gets there but keeps resetting the boot animation.

I don't know what kernel this is running, it isn't listed under settings nor do I speak Polish. ;)

Thanks for any help.
[G1 Android Development] BopChie:
thanks.. pulling 4.079 with jit now
[G1 Android Development] philosophics:
I just applied this and I would like to know, what is the recommended Max cpu speed with min speed?

Right now, I have it set on 633 max 528 min

Device froze then rebooted.

Question Pretty much answered but what is advised?
[G1 Android Development] BopChie:
my g1 likes 614max 128 min ... 528 min will eat ur batt like no tomorrow
[G1 Android Development] erlern:
Guys,

Would like to ask... where did you get the new JIT for CM5.0.7.? Cannot seem to find the references. Thanks in advance :)
[G1 Android Development] BopChie:
i used ...

http://droidbasement.com/db-blog/?p=249
[G1 Android Development] erlern:
Thanks! :)
[G1 Android Development] philosophics:
Thank you very much kind sir!
[G1 Android Development] BopChie:
no prob.. im s learning n00b here.. done a lotta reading here tonight lol
[G1 Android Development] philosophics:
Although, after I set the setCPU profiles, all with 128 as min the device crashed.

So I think I will try 614 instead cause 633 seems to be too much...

This is like having an entire new phone with all the ...Mods... I've done to it since yesterday.

Recovery is even faster!

Gonna try to 633 it now that I have a backup of the new setup...

Update:

Ya, phone no likie 633

Boot up is fine... kinda I guess. This is the first time I've used the bootanimation but that's a different topic

Logcat looks ok too so as long as it's at 614max 128min ...but I think I will set it to 245min cause that seems more speedy when battery is high and 128min when battery gets below 50% ...ya that's gonna be fresh!

Thanks to all mang's who had part in this!

p.s

battery is at 100.567.... F while charging. Just barely unplugged it and in the time it took for me to typr this, the battery temp went down to, 99.14 f

I'll look into that one and keep things posted if need be. Or if it's a known issue, I'll just keep my mouth shut. lol

20 mins later, device crashed after I plugged it back in, booted till the buttons lit up, then crashed. Complete self reboot.

Crazy stuff. Think I'll remove it for now, and come back to it when I have more time for it. Tues is next day off...
[G1 Android Development] pershoot:
Kernel 2.6.33.3 – OC-FP – Dream/Sapphire (32B) - http://droidbasement.com/db-blog/?p=253
[G1 Android Development] roccodaone:
Fantastic, thanks! :D
[G1 Android Development] pershoot:
forgot to make one change. want to reduce clock switching delay. will put out another tomorrow.
[G1 Android Development] kristoff123:
596 works for me. 614 will crash eventually.

I am guessing that devs will start including this in their releases, as long as userinit is set to max 528, you never have to worry. I just start setcpu after I log in to be safe.

THe new Cyanogen + this new OC have given my G1 a new lease on life. Next up: slim extended battery!
[G1 Android Development] tuffCookie:
same here. currently running 596 max, 128 min.

thanks domenukk, i got it working using your method.

pershoot, i saw in the change log that the frequency range is from 245-585. i haven't flashed it yet, but can you increase the range to be 128 to at least 596 (maybe higher for those lucky enough to get 614, 633, etc)?
[G1 Android Development] pershoot:
im really about releasing stable kernels that will fit for the masses. 128 seems to have an adverse affect at times (instability, wake up lag/scale up slowness for the lot, at times). 596 wasn't provided in the published source (which i gather has gone through some period of testing to derive the best fitting freqs, etc.), and this seems too close to that borderline of instability for the lot. 585 -> 596, you will not notice a difference (i may or may not increase things further across the board; we'll see how things go). there are other tweaks that have been added to try and increase your performance/efficiency, and maybe/probably more on the way.
[G1 Android Development] tuffCookie:
thanks for the response and explanation. not trying to rush you, but when can we expect the update with the reduced clock switching delay?
[G1 Android Development] tnpapadakos:
yep, 614 etc was no good for me...585 is stable so far thanx for all yer work bro
[G1 Android Development] pershoot:
this wknd most likely. want to also look at other things in source, to re-familiarise myself with things. have just turned back on my g1 (on a nexus now) after having it off since since 15.1 release, so its eager to be flashed, hehe.
[G1 Android Development] tuffCookie:
i forgot to mention that 596 came from dumfuq's recent oc kernel, which had 122880, 128000, 245760, 384000, 528000, 537600, 556800, 576000, 595200, 614400, 633600, 652800, 672000 frequencies.
[G1 Android Development] Ace42:
Do you guys thing you could make one for a sense rom possibly where the speed boost would be really significant?

(Would personally like a port for espresso)
[G1 Android Development] tuffCookie:
pershoot, i forgot to ask about the 2 zip files you provided. i'm assuming boot-cm_2633.3_ds-oc-xtra-fp-050110.zip (xtra version) contains everything boot-cm_2633.3_ds-oc-fp-050110.zip (original version) has and i don't have to flash both?
[G1 Android Development] pershoot:
correct. xtra is added configuration options and sched. i/o change.
[G1 Android Development] testing567:
Do the frequencies higher than 585 exist in the kernel so they can be accessed from SetCPU? Since different phones will have a different stable max frequency due to manufacturing discrepancies, it would make sense for 585 (or even lower) to be a safe default max frequency, but it would be nice to be able to bump it up using SetCPU or userinit.sh for the phones that can handle it.
[G1 Android Development] pershoot:
nope. it is clamped at 245 on the low end and 585 at the high end. setcpu autodetect will detect the range provided, properly. i have no plans of adding further frequencies past 585 at this current time, until further testing can be done, and i make certain observations about various devices.
[G1 Android Development] dumfuq:
Any chance you figured out how to set the default max in the new kernel? I couldn't find it in 2.6.33.
[G1 Android Development] Psych0_D0g:
hi, i tryed patching in the stuff into cyanogens eclair kernel, this is how my acpuclock-arm11.c file looks after patching, i left out all values considered not useable by purpose:

http://pastebin.com/xd8yaih9

after patching and compiling etc my g1 bootloops.

any ideas?

the update.zip can be found here:

http://dl.dropbox.com/u/2665083/update-cm-5.0.7-OC-Patch.zip

greets from germany
[G1 Android Development] pershoot:
MSM max/min is deprecated. i believe it hasnt been there since .31 (maybe even .30 as well). you could try setting userspace as default, and see if that works ok for you on this device, when your setting your values and it using them.
[G1 Android Development] testing567:
I don't know much about compiling kernels, but I was wondering about this. Are there any android devices on the market right now that use the same series processor as us and have a .33 kernel. Almost every mobile device on the market defaults to less than their max frequency. Maybe there's another kernel you can glance at for the answer to this problem. 2.1 Hero maybe?
[G1 Android Development] BopChie:
how does this differ from the other OC kernel for 5.0.7 in this thread?
[G1 Android Development] domenukk:
also I am running 122whatever to 595200mhz and its pretty darned stable.

on screen off i clock down to 122mhz performance. no freezes so far :cool:

plus great battery life (ondemand advanced settings: threshold to 65% and powersafe bias to 400 =) )
[G1 Android Development] CharonIDRONES:
Are there any boot.img's with the 'new' frequencies for .29 kernels? Also, might have to have my hand at attempting to compile the kernel too for SuperD as that is my daily driver still. Figured out how to extract the kernel and ramdisk, so off to a start . . .
[G1 Android Development] Ohsaka:
FYI, I have been running ZX Donut ROM for over a week now with 614Mhz max. Never get any reboots or freezes. And I use my phone at work to play Pandora for pretty much 8 hours straight (on a charger)...

So I think some phones will be able to pull off 614Mhz.
[G1 Android Development] dangambino:
I agree (w New Cyan and JIT - over 4.2 linpack. just running jit right now though w/ dr. cloverdales new theme)!
[G1 Android Development] dangambino:
Sorry.... just use search tool (SEARCH: JIT ) in new cyan thread, and it should be the first choice. jit zip, not made by me. but much appreciated:D
[G1 Android Development] erlern:
I would appreciate a default kernel at 633mhz max though. It is running stable for me. :)
[G1 Android Development] dangambino:
Im curious about stability of this hack and jit hack over a couple days (with cyan 5.07 )??:confused::confused:
[G1 Android Development] erlern:
I was using 4.2.15.1 with JIT and OC 633Mhz for the better part of a week with no problem at all... I suspect it would be the same with 5.0.7... though any sluggishness I experience (particularly the 3D Gallery) I would think is from the need to optimise the ROM, which will happen as cyanogen goes through the revisions :)
[G1 Android Development] pershoot:
-slight adjustment in WAIT period in between frequencies

-set userspace as default CPU governor (both oc-fp and oc-xtra-fp), to allow applications such as SetCPU to have full functionality and control

http://droidbasement.com/db-blog/?p=257
[G1 Android Development] panamakid:
hmmm would be nice to see this on a legend/eris/sense 2.1 port =/
[G1 Android Development] ttabbal:
Running great for me. Any shot of getting the download links without javascript? I like to keep that disabled on the phone's browser for performance. If only I could use noscript and just whitelist your site...
[G1 Android Development] BopChie:
hmm pershoot i only get a min of 245 and max 585?

just tried with custom and still no luck cant get past 585mhz
[G1 Android Development] pershoot:
That is correct. It is clamped at 245-585
[G1 Android Development] Sleepytime28:
Hmm for some reason after reboot setcpu will only show max @ 528 for me. Does anyone else have this issue?:confused:
[G1 Android Development] philosophics:
Any reason why we can't drop down to 128 like before or go up to 614?

I had sleep/standby set to 128max 128min and never had a problem.

Just wondering.

If you have time to explain, please cause I would like to learn more about the reason behind the new settings...
[G1 Android Development] gadget421:
did anyone try ramhack?

wondering if it would slow things up.