yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] BopChie:
Runnin about 9hrs @614 no issues on cm with my tmo g1....

fumbled right off the bat tho.. i acidently banged the slider to 672 and insta reboot loop.. nandroid restore and set to 614 and good to go from there.
[G1 Android Development] erlern:
Anyone on 653 and stable?

I think 614 is most stable, but 633 gets things done faster... and swiping between screens has NEVER been faster. Unfortunately, if I multitask a bit too much, that proves too much for 633 and it'll give me an instant reboot T.T
[G1 Android Development] Pfeffernuss:
On my 32B MT3G 633Mhz also seems a bit too much. It all looked stable when casually using the phone but when zooming and scrolling through Google Maps the phone froze.

Using 614Mhz it's all pretty stable though.

But got to admit that the difference between 614 and 528Mhz is not incredibly noticable (YMMV ofcourse). So for that reason I went back to 528 ;)
[G1 Android Development] kraftey:
Hmm.. maybe I'm doing something wrong or missing something, but every time I reboot the overclock goes away. That is, setCPU only allows me to go to 528MHz. Is that expected?
[G1 Android Development] erlern:
No, it is not expected. Did you customize SetCPU for the higher frequencies? Did you use the latest kernel patch (just a few post before) that fixes as default at 633 or 614?
[G1 Android Development] kraftey:
I'm using the no ramhack boot image from this post, and I added the frequencies to setcpu.txt:

I've also tried applying the zip on the original post but that doesn't seem to do anything. The loss of the overclock is confirmed with linpack scores.

I'm running Fasttest 3.1.1 (Xperia) which probably makes a difference.
[G1 Android Development] erlern:
You do know that the kernel patch is for CM right? :P I have not heard of Fasttest 3.1.1. Man, there really are a lot of ROMs out there for G1/Dream.
[G1 Android Development] kraftey:
I do know. In a related note, anyone want to put one up for Fasttest 3.1.1? :D

Also on a related note, I recommend 3.1.1 if you are okay with Xperia theme. It's my favorite fasttest so far (and fasttest is currently my favorite of all the ROMs).
[G1 Android Development] alongenemylines:
A kernel is pretty much universal for any rom out there. The init files are where there can be major differences that can keep your rom from booting.

Just unpack one of these OC'd boot.img's, unpack your rom's boot.img, then repack it with the OC'd kernel and your rom's ramdisk.

That's really all there is to it. make sure to grab wlan.ko and ramzswap.ko that was compiled with the kernel, and place them where they need to be for your rom.

I've been running at 614MHz on SuperFast 1.3 for about a week now. Just when I think I'm about ready to save up for a new device, someone keeps making the G1 better.
[G1 Android Development] EpicFail236:
Have been playing around with the various patches in this thread, ramhack or no, and so far I've not been able to get my phone to stay stable and booted for more than about twenty seconds before a force reboot on this. Seems I got the most luck with patching it immediately after a clean install of CM with a wipe, but still it wasnt up long enough to warrant normal usage. Think it just may be my hardware though, as my G1 has caused me other odd problems in the past.

Congrats to those who got it up, at any speed, but it looks like I'm out of luck.
[G1 Android Development] G1ForFun:
Yep your not a lone my friend, the hardware in my G1 is incapable of running 614mhz or more as well.:(
[G1 Android Development] erlern:
Guys, would we be able to apply this to Cyanogen's Eclair ROM? What modifications do we need or would it just work? I suspect it wouldnt since the kernel is different... am I wrong? Thanks! :)
[G1 Android Development] xillius200:
anyone able to overclock it higher than 670mhz yet? 0o
[G1 Android Development] tnpapadakos:
i would guess that since its modifications that are made to an existing kernel to do all this, they can modify the new kernel used in cm5 much the same way, maybe :confused:
[G1 Android Development] BlackTigerX:
The 633Mhz noRH variant is running great here, no FCs so far! Yet I can't start WLAN, so could you please provide the modules.sqf/wlan.ko? Thanks!
[G1 Android Development] dumfuq:
I'm not gonna be home for a day or so, but I didn't compile a new wlan module anyway (or any modules for that matter). You should be able to use the ones in the rom itself. If your not using cm-4.2.15.1 just pull them out of that rom and add them.
[G1 Android Development] gadget421:
what rom are you using that is working 614?

what 614 boot.img are you using?

trying to figure out which one is working for everybody.

using mytouch 32b
[G1 Android Development] Ace42:
It will not work for everyone, as you can see some are unable to OC at all and others have better luck...
[G1 Android Development] gadget421:
i'm running xd 2.5.1 jit/ramhack/614 or 633

works awesome

but, on my fiances phone can't get it to work, same phone a mytouch 32b.

for me i been trying each boot.img since this blog was started and lost track of which boot.img i flashed.

that why i asked those questions.
[G1 Android Development] Jedipottsy:
is there a CSDI overclock boot.img?
[G1 Android Development] gadget421:
ok i have 2 mytouch3g phones

both set up the same(kernals,oc,rom)

one works

onw doesn't

bought at the same time

lucky the one that works is mine:)

running

xd 2.5.1

jit

ramhack

614 all the time, nofc

633 sometimes fc

652 forget about

any suggestions on the one that doesn't work?
[G1 Android Development] toastcfh:
ive updated the overclocking source for the turbo devices on my gihub eclair heroc tree. the changes can be easily merged to the the 7200 devices. all i would suggest although i dont own ur devices. is to make freq tables like the turbo ones are. the code works much better and makes it possible to scale the freq and use setcpu to adjust on the fly. also see the wiki there for TODOs and maybe i can get some help. anyhow thats the spew heres the link

http://github.com/toastcfh/htc-2.6.27-heroc/commit/e695630112493f90314ce31c22fd95568e79c335

enjoy :D

also im in need of some help with getting camera to work in eclair. ive tried to backport .29 msm_camera to .27 and am having issues. if anyone can give me a hand or suggestions i would be extreamly excited. as one might assume camera is masive. i seen u guys managed to get it working using libqcamera. my only issue with being able to do that is our libqcamera isnt a msm_camera. its pmem and a pain in my @#%. anyhow im glad u guys are having luck. the hero ocs to 767.6 with no issues and stable.
[G1 Android Development] ivanmmj:
Check out Cyanogen's GIT or talk to him directly. He fixed the camera fully on the 32b. (Although, he hasn't released it, yet.)
[G1 Android Development] toastcfh:
Will do. Although I've never had much luck with Cyanogen replying to pm's. But I understand he prolly is a busy dude. But ill try again
[G1 Android Development] xillius200:
ignore ths post mistake post XD
[G1 Android Development] dangambino:
applied hack to cyanogen 4.2.15, with JIT! getting linpack scores of 4.00, consistently!! awesome! (high is 4.203). best linpack scores on my device to date! just flashed though.....curious about stability!?

flashed 15 min. ago, 1 reboot so far
[G1 Android Development] kristoff123:
using SetCPU, it seems more stable with 245 as a min rather than 128 as a min, if that helps. Also, set to ondemand and not performance. Hope that helps.
[G1 Android Development] xillius200:
Damn yeah compiled and am running pre cm 5.0.7 with OC at 670mhz now thats whack :P also I agree with kristoff123 thats the best settings :)
[G1 Android Development] erlern:
Can you please make a boot.img for us to apply when CM 5 is out for us? :) thank you!
[G1 Android Development] xillius200:
Yeah sure :)

update: Might have made an error partly works XD but ill fix it :P
[G1 Android Development] gophergun:
Are there any frequencies available between 528 and 614? None of the 614 patches are working for more than a few seconds for me.
[G1 Android Development] CharonIDRONES:
I hope someone makes a boot.img for SuperD soon so we can use wifi . . . Looking into how to pack a boot.img right now actually, probably time to find my Ubuntu CD somewhere
[G1 Android Development] tnpapadakos:
yes it would be nice to have a frequency or maybe two, in between 528 and 614
[G1 Android Development] dumfuq:
Toastcfh's updated patch (last page or so) included frequencies between those. It just needs to be compiled for us. So essentially, its gonna happen.
[G1 Android Development] gophergun:
Fantastic, thanks for the response.
[G1 Android Development] coolbho3000:
I suggest re-basing to the newest CyanogenMod kernel (2.6.33.3) if you haven't already. You might have to make the changes manually as there are some changes to cpufreq.
[G1 Android Development] gadget421:
just install the new cm 5.07

flashed oc hack

works, running 614 nicely with ramhack

pushing 2.6 mflop without jit,614

tried jit, wouldn't boot

live wallpaper works awesome, haven't found a problem yet.

p.s. works good on 633 also, doesn't lock up as much as it did on xd2.5.1
[G1 Android Development] kraftey:
Which oc hack did you use? I tried flashing and it just kept looping the android screen.

edit: Scratch that, seems to work now... (using the oc672-cm-4.2.15.1.img one)
[G1 Android Development] Karboush:
Is it OK to flash CM 5.0.7 with bootimg from 4.2.15 OC?

If there are some kernel code changes between those 2 versions, could it be a problem?
[G1 Android Development] vincom2:
Well, someone before you said the 4.2.15.1 image worked...

although I think one of the big improvements in CM 5.0.7 is kernel 2.6.33 (as opposed to the 2.6.29 that was in 4.2.15.1). Decide for yourself whether OC>new and improved kernel?
[G1 Android Development] alongenemylines:
I'd wait for someone to compile the new kernel with the OC patches
[G1 Android Development] gadget421:
J

Lost Bluetooth/wifi

With oc,everything else works,running 614
[G1 Android Development] xillius200:
lol test gallery failed last time I tried the old boot.img with cyan the gallery stopped showing pictures XD probably cause of 3D support or something :/
[G1 Android Development] gadget421:
no problem theres a app for that.

works for me:)

i need a kernel or img file for bluetooth kernel 2.6.29.6

i think the bluetooth isn't working because the kernel is the new 3.XXXX

anyhelp would be appeciated

running oc w/ramhack with cm 5.07

no jit, old jit don't work

oc file ramhack-oc-672-boot.img in the earlier posts

mytouch32b

also i love live wallpaper, i have fish!!
[G1 Android Development] dumfuq:
cm-5.0.7

alright, here is one with the cm-2.6.33-ds kernel branch.

I added more frequencies between 528 and 614.

Currently however I am unable to set the max freq as I did for the 2.6.29 kernel. This might cause problems for some of you since it defaults to the max allowed which is 672mhz. So unless you know your phone runs at 672 alright, you need to edit your /sd-ext/userinit.sh or whatnot to set the max yourself.

so for example to set max at 528mhz

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

available frequencies are

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

oc-cm-5.0.7-boot.img

sorry but no ramhack.

here's my diff file of the cm-2.6.33-ds kernel branch as well
[G1 Android Development] dangambino:
cant wait... let us know!! thanks!!!
[G1 Android Development] farmatito:
-	{ 12, CPUFREQ_TABLE_END },
+	{ 13, CPUFREQ_TABLE_END },
};

This will fix it. :D
[G1 Android Development] dumfuq:
sweet. thanks. new one up in a sec
[G1 Android Development] alongenemylines:
dumfuq, thank you so much for the new kernel! It's like I have a whole new device!

Stable up to 652 for me!
[G1 Android Development] dumfuq:
well I fixed that, but it still won't let me set the max freq in the config.

so userinit.sh is still required for most people.

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

available frequencies are

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

oc-cm-5.0.7-v2-boot.img
[G1 Android Development] BopChie:
i hate to ask..[noob] how does one edit the userinit.sh [/noob] ? i know mine cant take 672 but 614 was kosher
[G1 Android Development] testing567:
Is this correct for userinit.sh?

#!/system/bin/sh
#
echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
exit 0
[G1 Android Development] ttabbal:
Terminal/adb shell

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

that should do it.
[G1 Android Development] BopChie:
thanks.. so,

1.flash the kernel

2. adb or term

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

3.reboot and thats all.. right?

Thanks
[G1 Android Development] ttabbal:
That should do it. Just to be complete, flash with "flash_image boot <filename>" from terminal.

Heh.. 633 worked till I tried to run a game, reboot. :) Good thing I told setCPU not to apply settings at boot. :)
[G1 Android Development] Ohsaka:
The file is fairly small, can someone just add a ".zip" to the end of the filename and attach it here? I cant goto rapidshare/mediafire type sites from work...
[G1 Android Development] IConrad01:
Rocking stable at 595 MHz. (Couldn't get 614 to work w/ previous versions) on CM 5.0.7. I am a happy IConrad01.
[G1 Android Development] dumfuq:
its not a zip.
[G1 Android Development] Ohsaka:
Thanks, the new broswer in CM5 kept aborting at the end of the download from mediafire. It was also seeing the file as a .txt file...
[G1 Android Development] Ohsaka:
WOW!!!!

Is this for real????

C:\Documents and Settings\sm58149\My Documents\Downloads>adb shell
# cat /proc/cpuinfo
cat /proc/cpuinfo
Processor : ARMv6-compatible processor rev 2 (v6l)
BogoMIPS : 670.92
Features : swp half thumb fastmult edsp java
CPU implementer : 0x41
CPU architecture: 6TEJ
CPU variant : 0x1
CPU part : 0xb36
CPU revision : 2

Hardware : trout
Revision : 0080
Serial : 0000000000000000
[G1 Android Development] dumfuq:
yes. but probably not stable. mine can hold 672 for about 10 minutes before a reboot. your probably gonna want to figure out what your phone can handle and set it in userinit.sh
[G1 Android Development] Ohsaka:
LOL, froze already... Last time I tried 650 it froze in like 5 seconds... So when it lasted more than 30 seconds I got excited....

Oh well, even 614 was showing improvement.
[G1 Android Development] kristoff123:
Not sure how helpful this is, but the new Cyanogen can run 670 for me for 5 minutes before reboot - whereas with cyan 4 I couldn't run it at all. Experimenting with other freqs to see if they respond differently - hoping for at least 650 stable!
[G1 Android Development] slackberry:
is it possible to get the new CM kernel as a flashable zip? my mt3g will not accept it through fastboot.
[G1 Android Development] dumfuq:
that should be

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

unless you have an 'exit' at the end of your userinit.sh. cuz then youll want to use a texteditor
[G1 Android Development] dumfuq:
use

flash_image boot /sdcard/nameofboot.img

from terminal
[G1 Android Development] Ohsaka:
I dont normally do this because it clutters up threads....

But...

GOOD WORK! :)
[G1 Android Development] xillius200:
aw damn great work man XD still not sure why it didn't work for me XD anyway geat work yeah!!! finally 670mhz with cyanogenmod-MODDED XD :P
[G1 Android Development] mittolo:
i think overclock isn't so usefull...

can't you make an "undervolt" kernel like many kernel's for the nexus1?

the battery can last more!...

(sorry for my english, if you don't understand say it to me and i try to write better ;))
[G1 Android Development] erlern:
Well, for me overclocking will make simple things go smoother and quicker, like getting my dialer or contact app up immediately rather than the 1 - 2 seconds delay every time. :)
[G1 Android Development] Meltus:
I thought it was literally impossible to overclock the G1? :confused:

I was under the impression that anything higher than 528 just crashes the phone?
[G1 Android Development] Jedipottsy:
the same processor and motherboard on other phones can overclock so its not a chip issue.
[G1 Android Development] erlern:
Noob here. Yes, I know the consequences :P Okay, I tried flashing the zip file "xau-superd1102-cm-kernel-614MHz-ebi0" from recovery and it hangs at the T-Mobile startup. I think 20 minutes is a bit too long, and restored my backup. I am using CM's latest. How do I apply this? Do I need to push the files using ADB? Please advice. Thanks.
[G1 Android Development] infinitybiff:
flashed and got stuck at the G1 logo. Using super D 1.10.3. Was able to restore from a nandroid backup and get back up and running. I'm certainly up for testing this... not sure what I may have done wrong?:rolleyes:
[G1 Android Development] G1ForFun:
Well anyone who knows anything about overclocking knows that no two chips overclock the same...so saying that the same hardware is doing good elsewhere is irrelevant.

What we need is to be able to control the voltage...and we need spec voltages (so we know how far out of spec we are getting when adjusting). That is the only way we will overclock a G1 and have it still be stable.....

Overclocking = More Voltage
[G1 Android Development] infinitybiff:
anyone flashed this sucessfully?
[G1 Android Development] phhusson:
First of all, if I made a thread in "android general", it's because all of your questions aren't G1 specific, and I even answered some of them.

You can clock from 19.2MHz to 746 if you want..

If you can't get more than 600MHz, it's definitely not worth it.

Easy, just change VDD_X values in the table. But it doesn't seem to change much

You can't, the hardware voltage control is totally stupid, you just have 8 levels, VDD_{0..7}, and 528MHz is already at VDD_7
[G1 Android Development] G1ForFun:
So then we would need to edit the voltage values contained within the VDD's....specifically VDD_7....unless you can add VDD's and make a VDD_8.

Obviously its not that easy since it hasn't been done...but I am just wondering if the possibility even exists for adjusting VDD values.
[G1 Android Development] phhusson:
I don't even know who is in charge of applying this VDD, the MSM chipset or the PM one ...

Looking at the comments about it in acpuclock.c, it seems these VDDs are everything but reliable or predictable.
[G1 Android Development] G1ForFun:
BTW I tried flashing the proper version over a fresh clean flash of Defanged Base ----> Super D 1.10.2

Hung on G1 screen for over 5 minutes now....3 finger salute it is.

edit: 3 finger salute didn't even work...had to pull my battery.
[G1 Android Development] Jefmeister:
No boot

No succes here either, flashed it over the newest cyanogen, but just hung at the t-mobile screen for 5 mins :(
[G1 Android Development] BlackTigerX:
Flashed the "xau-superd1102-cm-kernel-614MHz-ebi0.zip" over my latest installed SuperD version (guess .2 kernel should work on .3!?).

Anyway, I am stuck at the boot screen aswell :p
[G1 Android Development] infinitybiff:
It would be really great to get some type of overlock working... i have some hero/sense roms that i'd like to have run smoothly ....
[G1 Android Development] G1ForFun:
Oh you mean all of them ;)
[G1 Android Development] infinitybiff:
indeed i did :)
[G1 Android Development] rynosaur:
No dice on a 2.6.29.6 Cyanogen kernel either--Dr. Cloverdale's newest build (1.3). Perhaps the new radio is to blame? This OC lockup reminds me when I would overclock my old Athlon XP beyond the voltage that the Abit board/BIOS could give it. Lockup city. Me thinks voltage control is the key to a good overclock. It's like putting a turbo on a motor without giving it more fuel!
[G1 Android Development] xaueious:
The only reason you guys are stuck on the boot screen is because I didn't build the kernel properly.

My G1 isn't running your radio at the moment so it makes it a bit of a pain to test. I'll build it again but if someone else can chip in and just build the thing it really isn't that hard.

I'll make one for Super D again, but if someone else with more experience can just try this that would make a lot more sense -_-

I wanted to get the ball rolling on this one that's all
[G1 Android Development] erlern:
Thanks a lot. If it's not too much trouble, you can let us know how to build the kernel for ourselves. :) Or point us to a tutorial to do that. Btw, there are two radio versions that most of us are using; 2.22.23.02 and 2.22.19.26I, that means at least two for each ROM (SuperD and CM), if you didn't already know. THANKS!
[G1 Android Development] slackberry:
that worked..almost..got massive out of memory messages.
[G1 Android Development] bunu:
Can someone make a .zip file for CM 5.0.7 for the g1/mt3g.

I flashed the boot.img on page 37/38 using fastboot

fastboot flash boot boot.img

It sent the boot.img and it flashed the boot.img.

But now I can't boot. It goes into the boot animation but then it freezes.
[G1 Android Development] tuffCookie:
same here.

mine freezes at the boot animation and after about 2-3 minutes, it'll reboot itself.
[G1 Android Development] bunu:
Just flash the original boot.img from Cyanogen 5.0.7 .zip file and you will boot up again. It worked for me.
[G1 Android Development] bunu:
Can someone who got this to work for the latest eclair cyanogen for the g1/mt3g please post a step by step guide on how you made it to work?
[G1 Android Development] tuffCookie:
thanks, already did it. :D
[G1 Android Development] dangambino:
foolow steps at end of previous page. it works. kernel is now differst in settings.... lets see......
[G1 Android Development] bunu:
I'm not sure about you but I can only follow instructions when it is in a certain order

For example like this

1)

2)

So if anyone can help me, then please do.
[G1 Android Development] Ohsaka:
I think the problem is that it boots up in super fast mode and crashes.

Try installing original boot image and then uninstalling setCPU before you install the new kernel. Then when you first run setCPU, set the max down to 528 real quick before the CPU overheats and locks up...
[G1 Android Development] tuffCookie:
here's what i did. please correct me if i did something wrong.

1) download dumfuq's overclock boot image

2) move the file into the root of your sdcard and in terminal type:

flash_image boot /sdcard/nameofboot.img

3) then type the following code:

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

4) then type reboot

in step 3, instead of 528000, try setting to any of the available frequencies below:

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

after i did the above, my phone froze at the boot animation, rebooted, froze at boot animation, rebooted, etc

*********EDIT**********

i'm assuming the code is incorrect in step 3...?

i just saw dumfuq's latest post and the correct code for step 3 should be:

echo "echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" >> /sd-ext/userinit.sh
[G1 Android Development] Ohsaka:
AAAAH, I bet step 3 is very important, or else it might default to the highest possible value! Good call!
[G1 Android Development] CLopez92868:
It works for me.....

1.) I downloaded the file from quote #362

2.) Put in root of sd card and renamed it (boot.img)

3.) Reboot recovery(better terminal dosn't seem to work with cyan's rom, I fixed permissions and nothing.)

4.) console

5.) flash_image boot /sdcard/boot.img

6.) Reboot

7.) Make sure u have the setcpu.txt in root of your card.(if using SetCPU), copy and paste in there.....

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

In setCPU choose custom frequencies at the begining... Mine works fine at 652800, 672000 force closed on me a few times....
[G1 Android Development] Ohsaka:
To clarify, when it asks you to pick your device... there is an option to use custom frequencies... I didn't get the point the first time I used setCPU.