yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Nagoki:
I agree. These overclocked kernels will definitely unlock new potential for our G1s. Could you refer me to a link that explains how to build a kernel. I would like to help. :D
[G1 Android Development] xaueious:
I followed these instructions for my build:

http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port

If you do not need the EBI1 option supposedly you just change that line. I did that and compiled a kernel but that didn't boot for people, so I am guessing I did something wrong or that this patch somehow kills it.

The option CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1 in .config specifically.

It takes about 10 minutes for my laptop to build the kernel from scratch.

If you do try it, try to change the diff file where the line says 'write(0x25...' to something lower. 25 is in hex, corresponding to the multiplier of 37. Or else you will encounter a lot of issues, particular with the G1. I think the myTouch might overclock a bit better than the G1, but for my phone even 614 MHz was a bit flaky. I didn't bother to recompile for something lower because I couldn't get the ramhack diff to patch properly in my custom built kernel.
[G1 Android Development] Nagoki:
Thanks, hopefully I have a bit of time tonight to try and build one.
[G1 Android Development] xaueious:
Here's a few more scenarios to try:

Overclock to 538 MHz (19.2*28), which is a minimal overclock, and see if it runs stable. This is to see if it freezes when a usb cable is plugged in.

Incrementally try different frequencies and fine a stable one for your device, and report back with your parameters as well as your device.

If the patch still doesn't work for you, as you can try flashing to the EBI1 kernel radio and just using the one I built straight up and seeing if that works for you. EBI1 kernel is closer to the Hero configuration, but I am not sure if this actually matters since I do not understand the source code. Anyways good luck.

Be prepared to possibly lose data, as the phone freezes up completely forcing a battery pull. I don't think it will damage anything, but it will quite possibly corrupt data when it freezes.
[G1 Android Development] kingklick:
if this is tested as real,

believe this is getting incorporated into my kernel(s)

:D
[G1 Android Development] anomalous3:
If I recall, the 32A uses the MSM7200A chip and the 32B uses the MSM7201A chip. The difference between the two I believe is in the fabrication size(the 32A chip is larger, 65nm process or so and the 32B uses a 45nm process). It is entirely possible that the reason it's working to some extent for the 32As but not for 32Bs is because one chip handles overclocking better than the other.
[G1 Android Development] erlern:
Yeah... I remember the discussion on this before. It basically says that the MSM7200A has a 'turbo' setting in it that enables it to be overclocked. This was why a few people in the Sapphire dev group found it possible to OC by mistake.

I somehow believe that it has also to do with voltage, as was mentioned before a few posts back. However, unless someone is able to help clarify this or to test this for G1 units, we are going to be doing this blindly. :(
[G1 Android Development] erlern:
Hey, I'm interested in phhusson's comment on PLL freq "The PLL frequencies aren't written in the stone, it's programmable by the software." This would mean that it is going to be a trial by error to get the patch to work with G1 right?

Can any other dev help in this?
[G1 Android Development] infinitybiff:
patiently waiting. :)
[G1 Android Development] JAguirre1231:
Any noticeable changes or is it just a quick fix (Flashing the image now anyway so it wouldn't matter either way)?
[G1 Android Development] Ohsaka:
Installed it. I see the "conservative" option now...

I am running 614/384 conservative now. I also changed the threshold to 75%. Now the phone shouldn't try to switch freq unless necessary...

Anyone have opinions or info on how low to set the minimum? Am I just imagining that someone said setting it all the way down to 122 was causing problems when the phone needed to ramp up fast?
[G1 Android Development] SilverSurfR:
I know this was a few pages back, but just wanted to say thanks for the info.
[G1 Android Development] pershoot:
is this working out for everyone?
[G1 Android Development] ceas909:
no issues yet.. ive ben running it since you released it last night
[G1 Android Development] ttabbal:
I'm running fine here with it. Thanks for the work Pershoot.
[G1 Android Development] animefans:
Need more experiement

I downloaded last night 051010

My last kernel from you was 050710

It seems like 050710 is more battery friendly than 051010. In another world, 050710 seems to give me longer runtime on battery

But I have been fuzzing around with various settings so I wouldn't say 051010 is bad

will use my phone longer before I make any conclusion

Thanks for your kernel build. It's the best one I have come across (including building my own)

The one request I have, which I know you won't do, is to increase the max to 633 or so :)

Still appreciate your work
[G1 Android Development] tnpapadakos:
actually working very well for me, i had been resigned to just using cm5.0.7's included kernel, but now, youve converted me back again

NOT using JIT right now, i cant say that it gives me anything i notice except higher linpack scores
[G1 Android Development] pershoot:
recalibrate your battery and monitor your useage. in testing it is the same more or less with the previous. remember, you will only save power in idle/close to idle. while your phone is in use and close to max, you will not save any power. nothing i can do about that...
[G1 Android Development] worldestroyer:
I can't seem to raise my clock any higher then 576, even if I manually import higher clock options in SetCPU. Same problems with your previous kernel as well.
[G1 Android Development] pershoot:
you cannot get higher then 576 with my kernels.

122-576.
[G1 Android Development] Ace42:
(SuperD)

I noticied with 576 max it goes...

160..352..480..576

This is my first time using your uv kernels and I was wondering if you have any Rhack versions, I dont use 3D apps so I could use the ram(alot of widgets)
[G1 Android Development] senab:
Thanks! Been messing with the conservative governor and researching values. After some research (mainly from the Pre forums who have been using conservative for a while) I've come up with these settings:

echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 672000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# 1 Second
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate
echo 75 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold
echo 15 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold
echo 5 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step

Needs some tweaking, but it's a start.
[G1 Android Development] pershoot:
not possible (10mb) with 2.6.33.3. hw3d needs the extra ram now (i tried already).
[G1 Android Development] Ace42:
I see..Guess I can live w/o it then, thanks for the great work though.:)
[G1 Android Development] dumfuq:
That's about what I've been using as well and it's been working good. I've been testing at 76/16. Haven't touched teh freq_step but it looks like default is 5.
[G1 Android Development] asb123:
hey, i notice that there are always 2 kernels to choose from, one has the word xtra in it and the other does not, what are the differences?
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

Scroll up in this thread or search on droidbasement for dream/saphhire and you'll get your answer.
[G1 Android Development] zimphishmonger:
Been using your latest (051010) xtra and its working quite well. No more reboots, kernel panics, etc. Thanks a lot, pershoot!

EDIT: Just got a kernel panic, attached my last_kmsg (added txt extension for XDA)
[G1 Android Development] kraftey:
Is there anyway you can throw one together with the hotfix along with the patch (linked here: http://code.google.com/p/cyanogenmod/issues/detail?id=1409#c39) for the 3g lag some people (myself included) are experiencing?
[G1 Android Development] senab:
I've changed my settings now to:

echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 672000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# 1 Second
echo 500000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate
echo 76 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold
echo 12 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold
echo 8 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step

I got a bit of lag with my last settings. The adjusted sampling rate and freq_step have helped with that. The reason I've increased freq_step is that 5% meant that it went through all of the frequencies up & down, which is fairly inefficient (as there are so many). A value of 8% meant that certain frequencies are missed out meaning that scaling up/down is a bit quicker.

I'm overall, very happy with this.
[G1 Android Development] Pfeffernuss:
Just flashed the Cyanogen Test4 Rom. Anxiously awaiting the overclock kernels for this Rom now :rolleyes:

Previously ran using 160/633Mhz on Test3 and all was well. During a 650Mhz stress-test overnight the phone rebooted. Will have to try an extended 633Mhz test as well :D
[G1 Android Development] pershoot:
Re: ToAsTcfh Overclock Kernel Patch :: Downloadable Kernels For G1/32B/32A

No refresh is needed for my kernel set.
[G1 Android Development] stormmonkey:
Works!

Just Flashed 32B boot-cm_2633.3_ds_32b-oc-uv-fp-051010.zip Over CM4.2.15.1 Zero issues, running perfectly at 576. Linpack is now 2.45 MFlops. Now Where's a Stable JIT compiler to make my MyTouch fly?!
[G1 Android Development] xaueious:
Did you notice any camera issues? I tweeted pershoot about using the kernel for CM4 and he mentioned that.

Also how is battery life?
[G1 Android Development] Pfeffernuss:
Okay, didn't know that! Thanks, 576Mhz here we come! :D
[G1 Android Development] stormmonkey:
I saw that post but figured I'd give it a shot. No camera issues, in fact it seems less laggy taking pictures.

As for battery, I only flashed this morning, but due to the scaling I don't see this effecting it much. Aside from games, which have a tendency to kill the battery anyway.

I did notice compcache won't enable anymore. But I'm getting a Class 6 SD card tomorrow, so I'll just figure out swap...
[G1 Android Development] pershoot:
the DS kernel is nice (-xtra). nice speed up, overall smooth and responsive (as much as my testing device (g1) can be), good power savings. im pleased, thus far.

the nexus kernel is nice too, but that's something i've been working on.
[G1 Android Development] xaueious:
Try pushing ramzswap0.ko manually from the zip to \system\lib\modules\ for using pershoot's kernel on a 1.6 ROM
[G1 Android Development] stormmonkey:
I know I've seen info on this..

but is one Kernel better than the other? I'm guessing the xtra is faster but more on the experimental side?
[G1 Android Development] pershoot:
it tries to get more efficient and boost performance wherever applicable.
[G1 Android Development] pershoot:
small update tonight, for lowmemkiller,etc., as per cy's git.
[G1 Android Development] BloodyWasHere:
http://forum.cyanogenmod.com/index.php?/topic/3320-bugs-cm-507-test-4/

Anything for test 4? or use test 3's?
[G1 Android Development] dumfuq:
oc825-cm-5.07-DS-test4-boot.img
[G1 Android Development] BloodyWasHere:
You are the man.
[G1 Android Development] kraftey:
Seconded. Thanks, seems to be working great.
[G1 Android Development] defconoi:
what patches and changes are to this kernel? Have you implemented cyanogen's changes?

Thanks

d e f c o n
[G1 Android Development] dumfuq:
no, I just recompiled it and changed the name. jk. only change to the kernel itself was in /drivers/staging/android/lowmemorykiller.c. other than some changes in the ramdisk.
[G1 Android Development] tuffCookie:
REQUEST:

can we get a kernel with pershoot's extra features (including the undervolting) with dumfuq's higher frequencies?

pleeeease :D:D:D
[G1 Android Development] Ohsaka:
Also, can eiher pershoot or dumfuq come mow my lawn? I promise I'll donate if you do! :)
[G1 Android Development] tuffCookie:
lol. i had to ask...;)
[G1 Android Development] dumfuq:
$100 per square foot. Naked even. Airfare not included.
[G1 Android Development] gadget421:
on mytouch 32b

is anyone using swap? 32,64,96

or just enabling comcache?
[G1 Android Development] dumfuq:
github update...

oc825-cm-5.0.7-DS-test4-v2-boot.img
[G1 Android Development] gadget421:
damn i just flashed v1....now v2 is there much difference?
[G1 Android Development] dumfuq:
No...not really
[G1 Android Development] tnpapadakos:
i think i just fried my ext...restoring backup now...was going stable at 633 on dumfuq's kernel and slid the max bar up to 825...it stuck...and well, here i am:eek:
[G1 Android Development] pershoot:
kernel 2.6.33.4 - dream/sapphire (32b/a) - http://droidbasement.com/db-blog/?p=379
[G1 Android Development] XxKOLOHExX:
Hey was just wondering,

If i where to make a nandroid back up with your Patch could i use the boot.img in the back up for a rom ? Cause this learning of how to compile is fustrating haha :P Just a lazy thought lol :P
[G1 Android Development] gadget421:
this will change the2.6.33.3 to.4, and oc, will everything still work correctly cmtest4 rom?
[G1 Android Development] pershoot:
yes.

......
[G1 Android Development] pershoot:
if you want to merge the zImage with a proper ramdisk, look in this thread.. someone posted an easy way to do it (if your not running linux).
[G1 Android Development] XxKOLOHExX:
awsome thank you :D
[G1 Android Development] xaueious:
Using pershoot 2.6.33.4 now on my Super D 1.10.2 ROM. Should be same for CM4 or any ROM based on that?

Rogers Dream (G1) on 3.x radio, so I used the 32A update.zip

Not sure if necessary, but I pushed ramzswap.ko to /system/modules/ramzswap.ko from your zip

I also unpacked and repacked modules.sqf after adding the contents of '2.6.33.4-cyanogenmod' into the lib folder in the squashfs folder. I have attached the updated modules.sqf that goes in /system/modules

I have no idea how Linux uses these files. If this was dumb please advise.

Also I haven't wiped dalvik-cache for my /data apps and everything seems to be running fine. Should I bother with wiping?

Anyways using your kernel seems okay on my phone. Lost ramhack though so I might not stick with this for the long term, or at least till I figure out where your source is on github so I can build one with ramhack if I bother at all. cyanogen hasn't updated his branch for it yet so I don't even know where to fetch 2.6.33.4 from.
[G1 Android Development] XxKOLOHExX:
This seems not to work for me :(

C:\kernel>adb push ..\kernel /cache/kernel
push: ..\kernel/zImage -> /cache/kernel/zImage
push: ..\kernel/unpackbootimg -> /cache/kernel/unpackbootimg
push: ..\kernel/nil -> /cache/kernel/nil
push: ..\kernel/mkbootimg.sh -> /cache/kernel/mkbootimg.sh
push: ..\kernel/mkbootimg -> /cache/kernel/mkbootimg
push: ..\kernel/dump_image -> /cache/kernel/dump_image
push: ..\kernel/autosign.bat -> /cache/kernel/autosign.bat
7 files pushed. 0 files skipped.
1164 KB/s (2263297 bytes in 1.898s)

C:\kernel>adb shell chmod 777 /cache/kernel/*

C:\kernel>adb shell /cache/kernel/mkbootimg.sh
/sbin/sh: /cache/kernel/mkbootimg.sh: not found

C:\kernel>adb pull /cache/kernel/newboot.img .\boot.img
remote object '/cache/kernel/newboot.img' does not exist

C:\kernel>adb shell rm -rf /cache/kernel

C:\kernel>echo "Your message here"
"Your message here"

C:\kernel>pause 1>nil
[G1 Android Development] vincom2:
@pershoot: it may just be me (especially seeing as I've only used each kernel for about 30 mins each), but I could swear your previous kernel (the one built after the test3 hotfix) was way more responsive than this current 2.6.33.4 one is (cm5.0.7-test4 for both). For instance, on that previous one I could open the keyboard and have almost an instantaneous rotate, while on the current one I have to wait, then watch the ugly redraw (where the right side of the screen is black).

I also flashed your 15 recent apps+invisible lockscreen today, which seemed to make my phone much slower, so I flashed test4 again it to get rid of it. That shouldn't have any bearing on the responsiveness of the phone since I got rid of it should it? >.>

Maybe tomorrow I'll try flashing your previous kernel back to see if I'm just imagining things...
[G1 Android Development] pershoot:
not from what i can see (and not from what has been reported to me). things are quite responsive as they were. you may be flashing too much. clear cache, flash rom + kernel update + gapps + optional: 15 recent apps, then reboot. you might want to give it one more reboot after it has fully loaded/booted.

let it sit in for a day and observe.

as for the rotation speed, it is always hit/miss on this device and eclair for me (was even that way on donut as well on the later releases for me). eclair takes up more resources, and the g1/mytouch really is being pushed to the max. there really is not too much that can be done about that, pitted with all the other things that need to be accounted for in the environment space.
[G1 Android Development] pershoot:
make sure you are setting up setcpu properly. ondemand, onboot, 122/576, no advanced, no profiles. dont use a userinit script and the like to dial in any advanced cpufreq values. this will override what i have set.
[G1 Android Development] xaueious:
My bogomips is going insane with your 2.6.33.4 patch. Something is wrong and the phone is a lot less responsive than before.

I have it on autodetect, and set to 576/176 MHz. It never stays there, instead trying to go to 460 MHz, 480 MHz, and other turbo mode frequencies
[G1 Android Development] whywhy1:
so the max is 576mhz?
[G1 Android Development] pershoot:
bogomips may not be as accurate with the newer kernel sets. it will jump up/down (according to the monitoring we are given). you need not be concerned about that.

use it at 122/576. no profiles, no advanced, onboot, ondemand. reapply the settings if it is acting wierd (i.e. getting stuck on a low freq.). make sure your on the latest setcpu. do not touch any advanced cpufreq settings. leave the way it comes.

you have something else going on if it is not responsive. i tested this numerous times yesterday night from sleep state to wake state. phone off for 30, wake up hit browser. comes right up. navigation, etc., all speedy (as can be on this dated device). this is what others have reported to me as well (thus far).
[G1 Android Development] pershoot:
go ahead and reflash clean as i wrote to the other user above and dont keep flashing to your heart's content. you may need to do this cycle twice (worst off with the nexus and flashing). let things sit and settle and observe.
[G1 Android Development] Jigga0o7:
I can definitely co-sign this as fact.
[G1 Android Development] xaueious:
Thanks pershoot

Your 2.6.33.3 for 32A does the same thing by the way. This might be working right for your 32B builds though

The 2.6.29.6 patch I made myself wasn't doing this or at least I didn't notice. Would have to flash back to check, that's why I am not sure what is happening with bogomips.

I'll try your suggestions. The advanced settings were working fine with the kernel I built in terms of responsiveness. But then it might just be ramhack as well.

This is the 32A version by the way.

cat /proc/cpuinfo keeps reporting 460.06 MHz when set to 576/576 MHz.

176/176 MHz, is reporting BogoMIPS of 140.57.

528/528 yields BogoMIPS of 421.72 MHz

480/480 yields BogoMIPs of 383.38 MHz

This is after autodetect.

I want to be using the updated kernel too, but I don't think it's working right
[G1 Android Development] pershoot:
i myself cannot test 32a, but i have heard back from 2-3 people on the 32a kernel, and they report good results and no issues thus far.
[G1 Android Development] xaueious:
Well I have the phone here in front of me. Not a 32A Magic though, but a G1 on a 3.x radio.

The weird thing is I don't even see those frequencies in your acpuclock.c table.

I might build my own again if it's bothering me enough. Not sure what's happening or if this occurs on the 32A Magic as well. I never built with the 2.6.33.x branch before. Hopefully not too different.

You 'could' flash your radio and see my results :P but that would be a pain

You don't get these irregularities with BogoMIPs on a 32B/G1 config?
[G1 Android Development] pershoot:
its acpuclock-arm11.c

i too thought TURBO_CONFIG 'may' cause an issue at some point (with 32a), and was going to disable the config specifically for those devices, but many reported success for it (32a'rs), so i did not disable it.
[G1 Android Development] pershoot:
i dont look at bogomips. i tend to look at the actual cpufreq stats if i have some doubt at what is ocurring.
[G1 Android Development] xaueious:
On 2.6.33.4

I didn't end up doing benches. I am back to my own kernel already. But the bogomips was not only reporting wrong frequencies, but the cpu was not settling down at the defined frequencies.

When I had my profile set to 576/176 MHz, the phone was not switching between the two frequencies. Bogomips was reporting a lot of fluctuations and never settling at the 2 defined frequencies like it is supposed to. On low it was something like 140 to 160 MHz when it was supposed to be 176 MHz. Then in 576 MHz mode it was actually reporting between 460 and 480 MHz, jumping back and forth.

I'm back to the one I compiled based on cm-kernel 2.6.29.6 branch donut. My Bogomips works fine for the entire range of frequencies. I didn't include your version of cpufreq_ondemand.c on your github since I got compile errors with it when I tried to copy it in to my build.

All I did for that build was git pull 2.6.29.6 from cm-kernel, copy your acpuclock.c, and used a .config from beav_35's Super_D ramhack EBI1 kernel build. My version is still more responsive for my phone.

Not sure what's happening with your 2.6.33.x 32A builds. Hope someone on 32A can confirm. Something is not working right for sure.
[G1 Android Development] pershoot:
you cannot use my files on .29. they will not work. cpufreq_ondemand.c modifications are needed, otherwise you will receive lag from 122.

how are you running .29 on the eclair build without it 'possibly' breaking things?
[G1 Android Development] xaueious:
I'm running Super D 1.10.2 actually. So .29 doesn't break anything. Pretty much same as CM4.

I have a setcpu.txt in my /system/sd directory to dictate the frequencies.

I haven't noticed the lag issue at all. Might be because I'm not using 122 MHz. I am only using the frequencies of 576 and 176 MHz on my ROM for regular use, and 128 for sleep. I'll make a proper port when I can when I have a chance.

My up threshold is 65%
[G1 Android Development] pershoot:
if your using my kernel, do not play with up threshold (that is one of the cpufreq advanced settings i was speaking of).

but at any rate, superD.. isn't that a donut build? sorry man, this has not been tested at all on donut or its derivative, nor was it intended to be used on donut. until you flash up to an eclair build, i wouldn't use my kernel set.
[G1 Android Development] Ace42:
I've been using your UV kernels and haven't had any probs yet, 122-576.Everything works camera,vid(exc compcache of course)
[G1 Android Development] xaueious:
I know what you are saying. I'll do some testing on my end later then. Thanks anyhow.
[G1 Android Development] ceas909:
@preshoot

Is there a significant difference between your 32b and 32a kernel??

I ask because Im running your 32b kernel on my MT3G 1.2, which is a 32a.

So I also ask because I too can confirm some wierdness going on with your latest kernel such as xaueious was explaining to you.

Running on CM test4 build. And I have the setting as you advised.