yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] damien667:
My patch sets it to 0x20... not 0x22... you must not be using my patch (unless that was a typo).

diff --git a/arch/arm/mach-msm/acpuclock.c b/arch/arm/mach-msm/acpuclock.c
index 7a413e3..eadd57c 100644
--- a/arch/arm/mach-msm/acpuclock.c
+++ b/arch/arm/mach-msm/acpuclock.c
@@ -115,6 +115,7 @@ static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 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 },
+ { 614400, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 160000, 0, 5, -1 },
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
};
#endif
@@ -127,7 +128,8 @@ static struct cpufreq_frequency_table freq_table[] = {
{ 3, 245760 },
{ 4, 384000 },
{ 5, 528000 },
- { 6, CPUFREQ_TABLE_END },
+ { 6, 614400 },
+ { 7, CPUFREQ_TABLE_END },
};
#endif

@@ -200,10 +202,23 @@ static int acpuclk_set_vdd_level(int vdd)

/* Set proper dividers for the given clock speed. */
static void acpuclk_set_div(const struct clkctl_acpu_speed *hunt_s) {
- uint32_t reg_clkctl, reg_clksel, clk_div;
-
+ //OC HACK uint32_t reg_clkctl, reg_clksel, clk_div;
+ uint32_t reg_clkctl, reg_clksel, clk_div, a11_div;
+
/* AHB_CLK_DIV */
clk_div = (readl(A11S_CLK_SEL_ADDR) >> 1) & 0x03;
+
+ //OC HACK
+ a11_div=hunt_s->a11clk_src_div;
+
+ //if clock is more than 528000, set multiplier to (19.2 x (0x20) = 614.
+ // all_clock_source_divider is always 0 for 614400
+ if (hunt_s->a11clk_khz>528000) {
+ a11_div=0;
+ writel(0x20, MSM_CLK_CTL_BASE+0x33C);
+ udelay(50);
+ }
+
/*
* If the new clock divider is higher than the previous, then
* program the divider before switching the clock
@@ -226,7 +241,8 @@ static void acpuclk_set_div(const struct clkctl_acpu_speed *
/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~0xf;
- reg_clkctl |= hunt_s->a11clk_src_div;
+ //OC HACK reg_clkctl |= hunt_s->a11clk_src_div;
+ reg_clkctl |= a11_div;
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
@@ -245,7 +261,8 @@ static void acpuclk_set_div(const struct clkctl_acpu_speed *
/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~(0xf << 8);
- reg_clkctl |= (hunt_s->a11clk_src_div << 8);
+ //OC HACK reg_clkctl |= (hunt_s->a11clk_src_div << 8);
+ reg_clkctl |= (a11_div << 8);
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
[G1 Android Development] dumfuq:
I've successfully gotten my phone to run up to 672mhz with this technique.

672 had random reboots

691.2 rebooted immediately (removed)

710.4 locked up immediatly (removed)

currently I'm running the 652.8 with no problems as of yet

Here is the boot.img I am currently running.

cm-4.2.15.1

ramhack

default max set at 614 min at 245

633.6, 652.8, and 672 are available after booting.

The patch is essentially the same except instead of the main block of code I put in this switch statement:

switch ( hunt_s->a11clk_khz )
{
case 614400:
a11_div=0;
writel(0x20, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
break;
case 633600:
a11_div=0;
writel(0x21, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
break;
case 652800:
a11_div=0;
writel(0x22, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
break;
case 672000:
a11_div=0;
writel(0x23, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
break;

}
[G1 Android Development] phhusson:
I guess writel(unt_s->a11clk_khz/19200, MSM_CLK_CTL_BASE+0x33C); doesn't waste enough memory space.
[G1 Android Development] dumfuq:
sorry for not being eloquent and living up to my name.

here's one using your suggestion

boot.img
[G1 Android Development] farmatito:
It was of course a typo.

+ * if clock is more than 528000, set it to (19.2 x (0x20) = 614.4)
+	* all_clock_source_divider is always 0 for 614400
+	*/
+#if PERF_SWITCH_DEBUG
+	printk(KERN_DEBUG "ORIGINAL a11clk_src_div: 0x%x khz %d\n", readl(MSM_CLK_CTL_BASE+0x33C), hunt_s->a11clk_khz);
+#endif
+	if (hunt_s->a11clk_khz >= 528000) {
+	a11_div = 0;
+	writel(0x20, MSM_CLK_CTL_BASE+0x33C);
+	udelay(50);
+#if PERF_SWITCH_DEBUG
+	printk(KERN_DEBUG "CHANGED a11clk_src_div: 0x%x khz %d\n", readl(MSM_CLK_CTL_BASE+0x33C), hunt_s->a11clk_khz);
+#endif
+	}
[G1 Android Development] farmatito:
Are you sure the code in the switch statement is ever executed?

As i was unable to see a value higher than 528000 in hunt_s->a11clk_khz.
[G1 Android Development] dumfuq:
I'm not positive no. However, a just compiled one that comments outs that chunk of code and everything worked great. It claimed to be at the right frequencies and all but the benchmarks sucked. I couldn't get it to go over 2.228 with linpack. With the code I never get one below 2.5 and up to 2.9.

due to phhusson's suggestion the switch statement is now

if(hunt_s->a11clk_khz>=614400) {
a11_div=0;
writel(hunt_s->a11clk_khz/19200, MSM_CLK_CTL_BASE+0x33C);
udelay(50);
}
[G1 Android Development] tnpapadakos:
i'm 4.1- 4.3 consistently with 614 but anything above 614 immediately locks everything up

battery pull reboot

i'm loving what you've done, though...this is awesome, i thought it couldnt be done

when cm 5 is out, please add this to it
[G1 Android Development] dumfuq:
I ran the linpack benchmark 10x on each frequency my phone would run and the numbers came out as expected if it was working properly.

528mhz

average=2.19

median=2.25

614mhz

average=2.55

median=2.56

633mhz

average=2.62

median=2.64

652mhz

average=2.7

median=2.72
[G1 Android Development] erlern:
Is it possible to apply your patch without Ramhack?
[G1 Android Development] Daneshm90:
Is it possible for someone to patch it to a 32a kernel ? i wanna try it :)

Im referring to the new ones you guys are working on. I tried the one on original post. Not much of a difference.
[G1 Android Development] CharonIDRONES:
Was wondering if you could possibly upload your newly compiled boot.img? Also, you mentioned that there were random reboots at 672, how is the stability of 633.6, 652.8 with your new boot.img? Thanks, loving the progress being made! Also, slight user request if possible of a no RAM hack version, as some do play games . . .
[G1 Android Development] Daneshm90:
When i try the kernel for 653mhz as posted in op i get a +.7 boost in linpack. But when i cat /proc/cpuinfo i still see 527mhz and even in setcpu. Any thing im missing ?

Also for some reason my 3d games dont work :( They're all VERY laggy.
[G1 Android Development] erlern:
That seems like Ramhack which doesnt work well with 3D games. Just be patient and the devs will get a stabler version out.
[G1 Android Development] Ace42:
This is what i did:

1.flash file

2.open setcpu

3. choose custom freqs

4.set to 614 max then done

My ms is 500-600 now

The one I found has no 10mb hack in it
[G1 Android Development] Daneshm90:
Hmm k didnt know there was a 10mb hack for 32a magics lol. Anyway imma flash the 614 one and see if it solves issues. Thnx

Nope 3d is still broken. Imma wait then for something better :)
[G1 Android Development] Ace42:
Meant to say 32b
[G1 Android Development] CharonIDRONES:
Which is the one that you are using? And what ROM are you using? Also, if you can, is your wifi working?
[G1 Android Development] Ace42:
-SuperD .13

-wifi dont work, was made for cyan tho

-http://xdaforums.com/showpost.php?p=6283025&postcount=210

Speed is great though
[G1 Android Development] xillius200:
Hey try ZX donut implimented 650mhz and the wifi works no problems stable as only thing im guessing is ramhack will be bad for games but papijump still plays alright without lag XD
[G1 Android Development] CharonIDRONES:
Ah okay, cause I looked at your posts and saw that you were running Super D so thought you might have had one with a working wifi somehow. But thanks for the info :) Actually flashing Cyan's right now, haven't been off of Super D in a bit but I use my phone as a remote for my XBMC set up, while I do have it enabled to run through a hostname too, just much more responsive when on local. Thanks tho' for the input.
[G1 Android Development] Ace42:
I don't use wifi so it doesnt bother me that it doesnt work.
[G1 Android Development] gadget421:
doesn't work

anything over 614 freezes.

mytouch32b

thanks for the 614, i believe you will make a workable 672.
[G1 Android Development] bigdbag:
I'm wondering if Firerat could make a quick kernel patch for CE2.x without the ramhack...
[G1 Android Development] erlern:
I found the 653 didnt work well. The performance increase was minimal and erratic. Not stable beyond that. Crashed twice. Am now back to the old 614Mhz. :)
[G1 Android Development] dumfuq:
same as before. Defaults to 614, pushable to 672.

only difference is I made one without the ramhack

cm4.2.15.1-noRamHack

cm4.2.15.1-w/RamHack

frequency list to add to setcpu.txt or whatnot

614400,633600,652800,672000
[G1 Android Development] tnpapadakos:
thanks for all your work dude

really enjoying experimenting with this
[G1 Android Development] uiterlix:
Can someone compile one for SuperD 1.10.3 with ramhack and working wifi ?
[G1 Android Development] Jefmeister:
You're awesome man, thx. Been trying it out, but 652 gives me too many reboots. We really need a way to regulate cpu voltage, preferably software :)
[G1 Android Development] domenukk:
No Ramhack. YEEha! will definitly try this out on some 3d games :cool:
[G1 Android Development] erlern:
the maximum 672 freezes and gives me an instant reboot... 653 is also unstable. Usable, but does not provide any improvement in linpack benchmarking. In fact, I suspect it is at this frequency that the voltage is lacking. But that's okay... 633 seems very stable (like 614). :) Am loving the new stable frequency. :)

Update:

633 failed on me in playing divx movie. It was worst than 614... movie lagged and suddenly halted (dunno whether its the new frequency or the new update for yxflash that is the culprit).

633 was good in Gameboid, playing Alien Hominid smoother than 614. Jimmy Neutron which stuttered a bit in 614 was surprisingly smooth.

Sticking back to the old 614Mhz for now :)
[G1 Android Development] Karboush:
Thank you for this.

In some apps I can see a huge difference. Homerun 3d is almost playable but after playing like 20-30 minutes battery went from 100 to 74.

One weird thing happend with wifi. I had it ON before using new bootimg, then flashed it and after rebooting couldn't put ON or OFF.

After nandroiding and putting wifi OFF before flashing new bootimg, I could use wifi again.

G1 with Cyan 4.12.15.1@614.4Mhz, compcache, no jit, no ramHAck, no swap.

Edit:

Max after 10 tries

Linpack@528.0: 2.287

Linpack@614.4: 2.636 (+15,5%)
[G1 Android Development] Daneshm90:
Can someone patch these to a 32a kernel ? thnx
[G1 Android Development] xillius200:
lol my phone working at 670mhz without reboots or any lag :P XD if you don't believe me ill make a video lmfao :) now that is just messed up XD
[G1 Android Development] lbcoder:
Enough with the overclocking. You are NOT going to increase your phone's capabilities. The bottlenecks are MEMORY speed/size, and STORAGE transfer speeds.

The ONLY thing you're going to accomplish is to increase battery consumption, and burn your chip due to excess heat.
[G1 Android Development] phhusson:
Memory bus (ahb one) = cpu speed/4.

And tell neocore that there is no benefit at all, while it's the application that is the most unlikely to see any benefit from a cpu overclocking.

And again, there is no overvoltage, there won't be "excess" heat, nor great increase of battery consumption.

And on WVGA devices it really helps a lot.

Concerning storage transfer speeds, you're half wrong:

It's true that linux' MMC handling is a bottleneck, but the mmc bus can do >10MB/s, the problem is in the FS used.
[G1 Android Development] Izord:
How to apply this to Super-D 10.4? Is there a patch or does it need to be applied to the ROM before flashing?
[G1 Android Development] Ace42:
For the one posted before i did:

flash_image boot /sdcad/boot.img

i have sd 10.3
[G1 Android Development] vincom2:
Er, I think you meant flash_image boot /sdcard/boot.img

lol
[G1 Android Development] Ace42:
yea that thnks for save

but make sure to make txt with these

19200,122880,128000,245760,384000,528000,614400,633600,652800,672000
[G1 Android Development] coolbho3000:
To the devs: to make autodetect work, apply this patch: http://android.git.kernel.org/?p=kernel/msm.git;a=commit;h=163a6fc98e1796c0edf1e11041fe1b6ae06f2154

I can't support all of the overclock kernels manually, I'd have to do far too many compatibility updates as new kernels are released, it'd be a mess.
[G1 Android Development] fstluxe:
HMM??

Hmm this is really nice !!! but a litle bit confusing if yo Read THIS !!

So the Question = this the BogoMIPS overclock ?
[G1 Android Development] xillius200:
0o question did you get that from the non working overclock in the past also that overclock was done differently this one actually works XD
[G1 Android Development] fstluxe:
Nice ! I'm Really happy hearing this, even though i have a 32 A device:)
[G1 Android Development] coolbho3000:
This one is real.
[G1 Android Development] Daneshm90:
Plz someone patch this to a 32a kernel :)
[G1 Android Development] Ace42:
Rom:Super-D .13

-Battery drain is abt 1%-5% more

-much lower avg ms

-more resp apps

-higher linpacks

-faster boot undr min

-no glitches so far

-no heat(temp in low 80's)
[G1 Android Development] testing567:
This is possible, although it will not work for most people. The reason for this is not all processors are equal, even if they are the same type of processors. Every one of them can be clocked to a different max due to minor imperfections in the manufacturing process. You basically just won the CPU lottery. LOL ;)

Just remember that the flip side of the coin is also true and there can be a few processors out there that are unstable at any speed over 528mhz. That's one of the reasons Cyanogen refuses to package his rom with an overclocked kernel on the nexus one forum.
[G1 Android Development] dumfuq:
since i've been running 633 for a while quite happily now, I decided I wanted a kernel with 245/633 defaults.

I also added the autodetect patch coolbho3000 mentioned so setcpu can properly detect the frequencies and people can skip the setcpu.txt file.

614-cm-4.2.15.1-boot.img

614-ramhack-cm-4.2.15.1-boot.img

633-cm-4.2.15.1-boot.img

633-ramhack-cm-4.2.15.1-boot.img
[G1 Android Development] Ace42:
the 633 have some instability probs on super-d for me, trying 614 now
[G1 Android Development] CharonIDRONES:
All hail!

Now we just need someone to pack the SuperD one's so we can have working wifi on there - Or just provide the wlan.ko. Great job tho' dumfuq! Haha seems silly saying that.
[G1 Android Development] CharonIDRONES:
Also, on that note - 633 is completely unstable for me. Reboots within the first two minutes of have it on. I was however running it at 633 constant. Didn't reboot to the G1 boot screen, but the Android screen which I thought was peculiar. Seems more like a kernel panic to me. 614 is working stable for me tho'. Running CM 4.2.15.1 (Factory+Dalvik wipe coming from SuperD). NoRAMhack version.
[G1 Android Development] gadget421:
what boot .img are you using?

xd2.5.1?

ramhack?
[G1 Android Development] erlern:
Thanks for the patch! :) Great to finally see this working (OC).

I wonder whether Cyanogen knows about this?
[G1 Android Development] CharonIDRONES:
Also - Reboots when using fix_permissions, my GameBoid is forceclosing when trying to launch a ROM, thought it might be a permissions problem, and then experienced that crash. Reinstalling the program worked tho'.
[G1 Android Development] erlern:
I totally agree seeing that my phone doesn't seem to overheat at all and battery consumption is not that great since apps are performing faster :)
[G1 Android Development] erlern:
Thanks for the latest images. But just one comment, is it me or mediafire seems to be downloading awfully slow for me? Anyone else having downloading problems? :(
[G1 Android Development] gadget421:
I would agree this works.

614 works all the time, possible reboots.

633 and up is unstable(2min max,or freezes ups) on mytouch 32b

at least on mine.

anyone else?
[G1 Android Development] xillius200:
lol im not that stupid I know all this XD
[G1 Android Development] jcdusse1981:
Hello, what should i download for a G1 with 2.22.19.26I radio on a SuperD 1.10.3 ?
[G1 Android Development] vincom2:
Incredible. I got a linpack score of 2.492, and also another of 0.1xx (don't think I've ever seen a score below 2 from my phone before). Hilarious, really :D

... I do wonder what went wrong though heh. But the phone does seem to work fine (and possibly a little speedier).
[G1 Android Development] Sleepytime28:
what are you setcpu settings? check your minimum cpu freq in set cpu. If your set to on demand mode you may have run linpack during a low freq. cycle which would cause a low linpack score.

I have also been running jit with absolutley no problems and I'm getting nothing below 3.8 on linpack.
[G1 Android Development] vincom2:
Min 128MHz, max 614MHz. Yeah, I realised that, but 0.1xx is really rather ridiculous, don't you think? o.o

(um btw, doesn't cm downclock to 128MHz in periods of low activity by default too? Or am I mistaken?)

Btw, I tried running linpack with setcpu in "performance" mode, but I found this gave me terrible scores of 1.5-1.8 consistently, so I switched to on demand instead.
[G1 Android Development] BopChie:
+1 i skimmed over the thread and i am worried about 2 things...

1st is the wifi

2nd.. I am running latest cm along with some skinned items (black search and notification bar with black lockscreen) Will flashing this kernal knock out the skinned stuff back to stock CM or not and what do i need to flash for the 614, no ram hack and keep wifi live.

Thanks in advance, i will gladly test this out on my g1 (2.22.19.26I radio and death spl)
[G1 Android Development] Sleepytime28:
Yeah I just noticed that when I auto detected in set cpu it set my min. really low I had to adjust. I got one reading real low like yours but have not seen one since.
[G1 Android Development] IConrad01:
Wish I could use this. Really do. I've tried pretty much all of dumfuq's kernels -- ever since the RAMhack itself first came out and he started publishing them.

But these OC kernels just aren't usable for me. Even when I *do* manage to get uptime from them, everything is at least 3x as laggy as normal. (What took 1 second before now takes 3 and half the time causes a kernel panic.) The phone somehow "forgets" what viable connection types my bluetooth headsets have, crashes -- not even force-close, but straight up *crashes* -- 50% of any actions taken while in any app that connects to the 'net...

And that's all just at 614 MHz. 633, and I get a pretty picture on a brick that requires a battery pull to reboot.

I'm pretty pissed 'bout this, mind you. I was stoked 'bout the OC'd goodness. Good for you folks that can actually get anything out of this.

>_<
[G1 Android Development] BopChie:
one very small tip here... call+menu+end should reboot you so you dont need to pop cover and pull batt

sorry that all i have, i will try it out when i get a little info per my Q here

http://xdaforums.com/showpost.php?p=6315556&postcount=295
[G1 Android Development] treperio:
in the first post is write that this overclock patch ebi it's for the no ramhack version of the super D roms, then it not work in the ramhack version?
[G1 Android Development] gophergun:
That won't work in a true crash/lockup like what would be caused by an unstable OC.
[G1 Android Development] IConrad01:
1) I'm fully aware of the three-finger-salute. Doesn't do you any good when your device is seized and unresponsive.

2) Regarding your questions: theoretically speaking there shouldn't be any change in WiFi performance. (My bluetooth & wifi issues not withstanding; they are "mysterious failures".) The driver modules aren't touched by this stuff. Some people have reported issues -- and I suppose I'd be one of them. But I *am* able to sync with my wireless router, and to pull data through it -- it's merely unstable. But that instability doesn't seem to be at the wifi level, but rather at the app level.

3) It's a kernel image. I dare say that if you aren't alert enough to the fact that a kernel image isn't going to overwrite the rest of your ROM, you really shouldn't be screwing around with it. Go back through the forums -- or basic computer theory -- and study it for a while, and then come back when you have some... somewhat more intelligent questions. Changing the kernel *never* overwrote your desktop environment, man. It's like asking about if switching to Golden Delicious apples will change the texture of the zest of your favorite oranges.
[G1 Android Development] tnpapadakos:
"It's like asking about if switching to Golden Delicious apples will change the texture of the zest of your favorite oranges."

ouch
[G1 Android Development] IConrad01:
Was I a bit too harsh? Sometimes I get cranky. It's amazing how many people can't figure out that the same exact process you use to flash a boot.img file is the same process you use to flash the old one. It's like they think it's a whole ROM in less-than-2-MB. <facepalm>
[G1 Android Development] gophergun:
Can't remark on slowness, but 614 without ramhack isn't downloading for me.
[G1 Android Development] Destriant:
Short answer: yes.
[G1 Android Development] tnpapadakos:
its all in good fun, i think, we're not solving world problems here, just modding phones, right?
[G1 Android Development] BopChie:
yeah i know.. thats pretty cute and all...

but i was gauging from the OP and a few other posts in this thread

e.g .......

owell some people just keep a sandy vag, so be it..... i understand how computing works but i'm more schooled on windows and hardware so i havent had to deal with kernels till now for the most part... but thanks for the suggestion.

was just a question, i played with the 1st OC mod that was a spoof.

anyways in a nutshell thanks? for your reply.... I'll give this a whirl later and report back

[/SAND]
[G1 Android Development] IConrad01:
Bonus points for keeping level-headed. :)

As to the WiFi -- if the kernel version provided specifies what ROM version it is compatible with, you can freely assume that the proper kernel-modules are already provided.

Now, if you were flashing a *different version* of the kernel, your WiFi modules and the like would be susceptible to compatibility issues. (I.e.; the 2.6.32 kernel-version as opposed to the 2.6.29 kernel-version.)

For what it's worth; I apologize for being "Flame-batey". Cthulhu knows that these forums have a bad enough rep for that as it stands.
[G1 Android Development] BopChie:
see was that so hard??

-kidding

thats what i was looking for, fairly dumb questions i know... i skimmed over this thread last night and i guess didnt want to grab my pooper scooper to start digging though some threads here to find my answer lol.

I know what you mean, i moderate a forum and am a member for a douche filled forum so no offense taken, i was just playing along ;)

anywho.. thanks for the info, thats exactly what i needed and will test my luck after work.
[G1 Android Development] erlern:
I ended up using a download manager to get the files from mediafire... yes... I hate using download managers, but they worked... all for 2MB! hahaha... the irony.

Anyway... it's worth the effort. :)
[G1 Android Development] phillyboi47:
ughhhh

I'm getting sick of this.

Ok i'd greatly appreciate anyone willing to help me.

I have a mt3g

I've gone thru several different overclock patches and every single one makes my phone extremely unstable and/or I lock up in setcpu

My phone won't stop restarting

I'm running super D 1.10.3 does anybody know the best patch for that?

and It ALWAYS lock up in Setcpu. Does anyone know how to to fix this issue?

I've just got a feeling I must be doing something wrong if a good amout of ppl are having great results
[G1 Android Development] gadget421:
I have a mytouch working awesome with 614. been 48hrs no problems

My fiance wanted a faster rom, i did it, then since i bin messing around with oc files. i can't find the right one that works...frustrated.

there are like 6 files on this blog.

once i figure it out. i'll post it, don't think it was just one flash.