yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] eugene373:
eclair is in the Very low 200ms on 32a Magic boards..

btw, the 32b Boards don't support the PLL that people think they do..
[G1 Android Development] domenukk:
I hate 32a boards :P

But on other roms (the one with supsetup) I get about 700 ms for 528 so this might as well be 600 with faster clock speed... :p

Anyway, faster CPU speed doesn't hurt and just sounds cooler :cool:
[G1 Android Development] infind:
interesting... so let me ask this

is it possible (in theory) to OC the memory as well?

im assuming thats where the bottleneck resides, no?
[G1 Android Development] ctso:
My thoughts on this, seems like it actually may be legit, but the benchmark tests I did probably didn't include enough data.

http://ctso.me/2010/02/g1mt3g-780mhz-overclock-hoax-or-reality/

Either way, we should thank Eugene for the contributions he makes to the community.
[G1 Android Development] Klyentel:
Let me ask ya something...when you flash a rom, and test to make sure your calls/text/camera/audio/ringers/apps/market/and graphic display work....and you find that is, are you imagining that? If someone post on the thread that a "known error" is in effect for the current rom you are using, and that error is Calls dont work, cant receive or dial out, and 10 other users who flashed agree to the same thing, but as you are reading, you are actually on a call with your mother, and your friend is beeping in right now through call waiting.....hmmm, is that your imagination? Are you really speaking to your mother? Or have you gone nuts, because you were excited about the capabilities of the new rom and wanted it to work so bad you ended up talking to yourself?

I dont think so!

So regardless of how many facts, videos, tutorials, educated guesses or benchmark numbers get posted,

if there are users experiencing good results from this cpu hack, then I believe it has some use for the good.

Devs, continue to compile.
[G1 Android Development] ivanmmj:
I wonder if the msm chip allows you to control the FSB speed? (If it even has an FSB...)

Same question for the Arm9 Co-processor...
[G1 Android Development] vixsandlee:
I must admit my phone feels faster.

Is it a placibo, well maybe, but it feels faster when using this hack.

So I am reserving judgment.
[G1 Android Development] eugene373:
Yes I know... But, as I said before. The PLL you would think that would work are not supported..

Sorry, but there Not & will never work that way.
[G1 Android Development] Alucardis666:
THANK YOU

this almost seems un-real!!!!! I've wanted snap dragon for so long, only to constantly wind up reading the short-cummings of the failboard that is the Droid's kb, or the lame 3g reception on the Neck-E-Sauce, Wun. I believe this is the best soloution to making my mt3g the best phone ever.

I mean first it was ext3, the ext4, then compcache, then the 10mb ram hack, bfs, cfs, and now over clocking beyond the 528mhz barrier?!?! This is too awesome.

Thank you.
[G1 Android Development] daproy:
What do you even mean? The PLL you would think that would work are not supported?

The PLL is set in the hardware. You can't change that. You change the divisor to get a new clock speed. If you don't change this = you don't change the clockspeed...sorry.

7201a chip (on G1) the PLLs are set to:

PLL0(mpll):245.76

PLL1(gpll):768

PLL2(bpll0):1056

7200a chip (on Hero)

PLL0(mpll):245.76

PLL1(gpll):960

PLL2(bpll0):1056
[G1 Android Development] daproy:
We already tried to actually change the clockspeed in September last year by changing the divisor for PLL1 to 1 = 768MHz / 1 = 768000 but it was unstable.

You can read about it here.
[G1 Android Development] eugene373:
Oh F*k sake, I understand what you're say... But you have it already in your mind that I'm wrong & this is a Hoax so just forget it.

Those PLL's Don't work Period on a 32b board and never will, get that through your ( I'm Right, you're Wrong Think Head State of mind ).
[G1 Android Development] protomanez:
Only on the open eclair rom :(?
[G1 Android Development] JAguirre1231:
No, it runs on any rom that implements it
[G1 Android Development] Hero_Over:
hey eugene. btw ive always thought you and ur buddy barakin are by far two of the most innovative android devs we got left. but i would expect your knowledge of software to be somewhat matched by knowledge of hardware. The performance of a computer depends on the interface between the processor and the memory. Memory Bandwidth is The rate at which the memory system can service requests from the processor. Thus, in short, it refers to the amount of data that is transferred in each access. In Laymans terms our processor can be sending 5ghz processes to memory but the memory has to be able to return that in a timely manner. aka your processor will be "waiting" on your memory which is the same as ur cpu taking longer to process it to mem. 32A's seem to have a higher memory bandwidth which means better performance from overclock.

morale of the story. buy a Nexus One and try to remember why we put up with 192mb of slow RAM and a 528mhz processor which was outdated on release!
[G1 Android Development] eugene373:
Yup, Nothing didn't know there. Thanks for the Kind words :)

Yeah would much rather get a nexus, but me & barak are Both Strapped for cash.. No way in hell Will I ever ask for a Donation now.

But, yeah It's highly Limited, but does work with other Phone's with better Memory, Proven on the 32a already. At this point it was only a Proof of concept that got blown into a bigger issue than I thought it would be... Oh well..

Thanks again though :)

~Eugene
[G1 Android Development] IConrad01:
@Eugene;

The way I look at it, the work you're doing is helping those of us whom were early adopters not feel like assholes for failing to acquire the latest-and-greatest thing to come out every six months or so.

I mean, half the point of modding firmware is so that you get the most function out of a device as you can. And the way I see it, if you devs can get next-gen functionality from a device, then that saves the rest of us from having to upgrade *with every new thing that comes out*.

It's only once the base specs of a device /vastly outstrip/ the modded specs that I bother doing an upgrade. Because I want an upgrade to //be// an upgrade *out of the box* compared to the work I've done to make the old thing better.

I mean, why constantly re-invent the wheel?
[G1 Android Development] snellx:
Sounds logical to me. I am quite sure, that daproy is right. I just flashed back the normal 4.2.14.1 w/ 10mb hack and it is not slower...

Any Chance to get an stable (real)overclocking-level between 528 and 768?
[G1 Android Development] daproy:
I'm pretty sure you don't understand what I was trying to say. I never attacked you or said it was a hoax. I was merely commenting on the validity of the code you posted.

It has nothing to do with what board you have, because your code doesn't actually change any PLL settings.

I thought XDA developers was for developers, ie. people who want to work together to develop some useful code.
[G1 Android Development] Hero_Over:
Yes I believe if we had a larger outline of our devices specs this all could've been avoided.

had to get this off my chest

One thing that I see and despise so far with Android phones is their exclusivity. g1 comes out oct. 2008 to tmo-us, 4 months later is 32A magic with upgraded specs but unavailable in the us. 3 months after that mytouch is released and fools people into thinking it has upgraded specs which it didnt (htc refused to release RAM specs until everyone found out). then a couple months later htc releases the highly envied hero with touchflo3d in europe unavailable to US 3g services. Then htc makes its respective cdma heros which are unavailable to us gsm'ers. then we get nexus one which unlocked cost an arm and a leg and is unavailable to upgrade with family plans which people rely on. it seems to me like htc and google want us to buy a new phone every quarter then make us suffer when newer/better models release

why so serious?
[G1 Android Development] kingklick:
haha I think we've both decided this over a bowl or 2.........

or 3 or 4......
[G1 Android Development] pershoot:
hi daproy. do you think its possible to derive a resulting frequency from another clock entirely, or are we solely tied to PLL1/2? i was having this discussion over the weekend on irc, and want to extend it here for thoughts.

your thoughts?

thx:)
[G1 Android Development] eugene373:
Sorry man, I felt like you was attacking..

I've tried every pll combo I can think of, sadly these are the only pll combo that will let the phone even boot, and clock up.

Very sorry, just tired of the jerks on the forums..

I'm all for Dev. with other's, but I know what's Ive tried, & what doesn't work/boot on the phone at all.
[G1 Android Development] Ace42:
I doubt this is a hoax of any kind, this kernel is a step up from the standard and would like to see more if not all roms using it. But I hope a version is made with 10MB R-hack also.
[G1 Android Development] narunetto:
I don't feel like an idiot for buying the G1! I wanted to be an early adopter for a reason, latest and greatest tech. The G1 met and exceeded what I thought Android was going to be, and has become. I still love the phone to this day and won't be giving it up until the Nexus One becomes available at a T-Mobile store or lets me upgrade early on the Google site.

The Development for the phone is so great and I love that we have an "open market" of ROMs so we can pick and choose what is best for the phone.
[G1 Android Development] pershoot:
let's all work together to try and find a common balance on these aging devices. try not to listen to others who misjudge or attack you and your intentions in a negative construct (i know it's tough to do sometimes; against all odds). it will only sway you from the common cause, in my opinion.

thank you for your efforts. this is all anyone asks, is for people to try, try and do more trying:)

we have gotten our g1's quite far in a years time, let's see if we can push it a bit further before an upgrade is inevitable (or we blow it up in the process! hehehe)).

-pershoot
[G1 Android Development] legend1222:
Real numbers...

I ran every benchmark I could find (4 programs on the market) on my 32A Open Eclair 1.1.5 kernel at three different speeds via setcpu.

I don't know what all the tests mean, but it seems to me that larger is better for these. The two mem tests were just for fun, but the results are interesting.

Before running setcpu, "Stock" is reported on the widget as 245-580 and 579.07 Bogomips

Set to 768 the bogomips reports 758.78.

Set >768 the bogomips reports 527.15.

Since the 998 Mhz tests were worse on all of them (As expected) except the LinPack mflops where I saw an increase (flawed test?), I left off the 998 numbers to save room.

Numbers rounded; percentages not.

B = The program named "Benchmark"

Heres what I saw:

Test Stock 768 % change
-----------------------------------------------------------
B Total 138.95 154.49 10.05%
B MWIPS DP 10.39 11.03 5.82%
B MWIPS SP 10.63 11.76 9.57%
B MFLOPS DP 2.03 2.02 -0.55%
B MFLOPS SP 2.73 2.94 6.89%
B VAX MIPS DP 6.32 7.49 15.55%
B VAX MIPS SP 6.48 7.68 15.52%
B Total Mem 101.80 105.22 3.25%
B Copy Mem 92.51 95.61 3.25%

Benchmark Pi 13769 13732 -0.27%
CPU Benchmark 868.66 864.33 -0.50%
LinPack Mflops 2.22 2.23 0.72%
LinPack Time 2.44 2.42 -0.83%

So I'm not sure what to make of this. But, to me, it seems like the program Benchmark is the most legit from what I know. If thats the case, then were looking at an average increase of 8% per test on my phone.

I understand about multipliers and things like that, and I agree that the overclocking concept that is apparently being using doesn't make sense with what I've learned, but to me the numbers don't lie (unless i'm interpreting them wrong). It does seem more responsive, but again, that could be a placebo effect as others have pointed out.

I'd be interested in any incites anyone wants to give. For now, I guess I'm leaving my phone at 768.
[G1 Android Development] charnsingh_online:
For all on my 32a the first kernel overclocked seriously overclocked seen in benchmarks, but after testing for hours Wat I conclude that it is just a placebo effect, its not overclocking, I get same CPU benchmarks, Wat we need is real overclocking to save our money n devices
[G1 Android Development] xaueious:
See I ran those benches too and it doesn't make any sense. I ran the benches are 550 and 768 with the same results. If we can figure out how this benchmark program work we might know what is happening, but at the moment even the devs are doubting the validity of this 'hack'.

As you said the Linpack numbers were wrong. There's no reason for me to believe that this entire benchmark program has some bug in it that makes these results completely irrelevant.

I'd prefer someone with expertise be clear about this issue.
[G1 Android Development] daproy:
Yeah you can use any of the PLLs installed to derive a clockspeed. This is where are the stock clock speeds come from ie. (128000, 245760, 352000, 384000, 528000) from (PLL1/6, PLL0/1, PLL2/3, PLL1/2, PLL2/2).

PLL0(mpll):245.76

PLL1(gpll):768

PLL2(bpll0):1056

The problem comes in trying to get a clock speed between 528000 and 768000 (we know PLL1/1 locks up the phone as soon as it scales up to 768000).

I never got around to trying non-integer divisors (if they'll even work), which might be worth trying, but I sold my G1 and picked up an N1. Still interested in where this goes though, but I can't test anymore.

Something like PLL2/1.5 = 704000 or PLL1/1.2 = 640000
[G1 Android Development] xaueious:
Those are some weird divisors even for a desktop computer. Someone want to give it a shot?

How about PLL0/.5 first = ~590 MHz?

I honestly doubt that we can even hit 640000.

I just figured out how to build kernels so I wont be making this patch for a while.

I have a G1 to test with, but I am on EBI1 so I have to either wait for bcrook or build my own.
[G1 Android Development] Hero_Over:
I took a look at what tasmanian droid has done on the Droid/Sholes and it seems as if standard clock speeds can be replaced. Unless it is possible it is only for that chipset. He removed the lowest clock from the kernel (which in our case i assume is 128mhz) so if we could use clocks listed : 245,352,384,528,660. My power supply gave out on me a couple weeks ago and I gotta use my moms pc lol so I am of no use. But I would like to see this hope become an actuality.
[G1 Android Development] gringo69:
hehehe....n here i was thinkin i was gonna need a new phone....then i read about the Davlik Turbo thats coming out.....and i see we can now overclock our G1's........

****s lookin good in the world of android hehehe.... :D

ima wait a lil to get busy on overclockin though....i wanna see how this goes for u brave ppl 1st:D
[G1 Android Development] atgrande1:
Hey people can call it what they want but I know it makes a difference with my phone, I've had the g1 since it first hit the market and I think I know how my phone runs when it comes to opening apps eg. gallery, browser, or even with boot times etc. So it may be placebo effect for others but for me, I KNOW it made a difference. For those that tested it and it didnt make any differences on their device, hey who am I to tell them that it did, I think they would know their own personal hardware far better than I do so hey, to each his own...just my $00.02 and IMHO?!:confused:
[G1 Android Development] goofyog:
What about hero rom can we just add this and it will run?
[G1 Android Development] Ace42:
No, it will work for Eclair or donuts only excluding and hero of sorts.
[G1 Android Development] Hero_Over:
Think first ace. U know wat a boot.img is? It is a kernel and a ramdisk.

Have you ever unpacked one? Try it. If a kernel works on any rom it

Will work on any other rom. Thought you had a rom? Develop much?
[G1 Android Development] G Zero:
Here a million dollar question for you...

If Over Clock doesn't work...

Why does the battery die much much faster?

Aachhhaaahh [/eddie murphy jew]
[G1 Android Development] Käptn.Karacho:
testing atm and working really fine

thx for this great piece of work

by

KK
[G1 Android Development] goofyog:
Im runing 800mhz right now, just click on snapdragon n1 in setcpu all max and that gave my 800. 605, 630,650 in benchmark(stock 680+) fantest rom, incres in browsing is about 2 seconds in lite pages and 5 sec in big(internet browsing).
[G1 Android Development] eugene373:
Hey Buddy, I really really hate to Admit when Wrong, But.... You're Correct, Sadly I just confirmed it's not overclocking....

But, with Bad New's Comes Good new & would love your Help!

590Mhz is almost ago!! :) it simple can't handle the load though... So I'm thinking of Trying like from 528 to now 580Mhz.

Just wanting your input on this, as it's clearly trying to work at 590Mhz.

Also, Just to clarify, the OC that Currently working is Upping the through put, but basically bottoms out when really try to run at those speed, that's why it does seem faster, but not much is going on :) So, in Reality it's Running as Fast as the Multiplier will let it on that Current PLL which is why there is a speed boost, but not much :(

btw, I am sorry I snapped... Was just trying to help the community & felt like it was worthless post.. But, we do have something on paper now at 590Mhz...

Thanks again & very sorry..

~Eugene

Really Slow but man is it sure try..
[G1 Android Development] xaueious:
Can you clarify what your patch actually 'can' do then in the first post of this thread? People are just running in here wild because they think their G1 is running at 800 MHz.

Also, does actually over clock to 590 MHz (PLL@245MHz/0.5)? That's a good improvement if true.
[G1 Android Development] eugene373:
Well, I tested your multi that you was thinking of trying out being Bord... Surprising it work, but man is it trying like hell to lock up.
[G1 Android Development] BoomBoomPOW:
I'll take 590Mhz over what we got now. Add in the Dalvik Turbo..

590Mhz + Dalvik Turbo = :D
[G1 Android Development] eugene373:
Um? You have Gtalk.. We might get something stable tonight if you have time..
[G1 Android Development] erlern:
Respect! :)

All the best. I'm sure one way or other, there will be significant development for you and all our faithful developers on XDA on this. :) Really made me read through all the technical aspects of overclocking. Thanks guys!
[G1 Android Development] daproy:
Probably because the kernel is continually trying to step up the clockspeed by changing PLL when each of those settings are all the same PLL and divisor.
[G1 Android Development] daproy:
I see one problem with this... 245MHz/0.5 is 490MHz not 590MHz. But all the same, I'm curious if it'll run with a non-integer divisor at 491520Hz.
[G1 Android Development] eugene373:
How would one set a non-integer divisor?

I had a Good read over the Post you linked. First time I saw that, So don't shoot me here, just trying to further understand this now.. And at least try an make good on an OC kernel.. Might be why it was sluggish, though. Just trying to make since of this after reading that post.

Once again, sorry about that.

In reality I was the on with the I'm right att.

~Eugene
[G1 Android Development] daproy:
Good question. It's not that straightforward. At first I was thinking you could just add it to the table. Like:

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

But this doesn't make sense for two reasons. First it probably won't compile because a11clk_src_div (the number i have bolded in the struct) is defined as an unsigned int. Secondly, a11clk_src_div is one less than the number to divide by ie. for 528000 take PLL2 (1056) / 2 so a11clk_src_div = 1. So to divide by 0.5 a11clk_src_div = -0.5??? This doesn't make sense? But hey I don't know...hehe.
[G1 Android Development] eugene373:
See that's the thing, even though I understand like OC Computer CPU's..

Have a bit of a time Grabbing the Straw on this on... On the PLL table and Calculations.

Is there a Go to Chart that breaks the Division up on how to do the correct math?
[G1 Android Development] Geniusdog254:
Not quite clear on the whole unsigned integer thing (been a while since I messed with C). But if it is one less than the actually number then couldn't you set it at PLL0 /1.5 which would equal PLL0 / .5?
[G1 Android Development] daproy:
Not that I know of. Qualcomm doesn't want us knowing too much...hehe.

it's defined as an unsigned int

struct clkctl_acpu_speed {
unsigned int	a11clk_khz;
int	pll;
unsigned int	a11clk_src_sel;
[B]	unsigned int	a11clk_src_div;[/B]
unsigned int	ahbclk_khz;
unsigned int	ahbclk_div;
int	vdd;
unsigned int	axiclk_khz;
unsigned long	lpj; /* loops_per_jiffy */
/* Index in acpu_freq_tbl[] for steppings. */
short	down;
short	up;
};

You could of course change this but I think it will mess up the divider setting function.
[G1 Android Development] daproy:
The divider setting is handled here, but it's some lower level stuff like writing directly to the ARM11 clock control and select address? It's beyond me, but I'm afraid that A11S_CLK_SEL_ADDR can only handle integers. In which case we are screwed. Our best bet then was the PLL1/0 = 768000.

/* 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;

/* AHB_CLK_DIV */
clk_div = (readl(A11S_CLK_SEL_ADDR) >> 1) & 0x03;
/*
* If the new clock divider is higher than the previous, then
* program the divider before switching the clock
*/
if (hunt_s->ahbclk_div > clk_div) {
reg_clksel = readl(A11S_CLK_SEL_ADDR);
reg_clksel &= ~(0x3 << 1);
reg_clksel |= (hunt_s->ahbclk_div << 1);
writel(reg_clksel, A11S_CLK_SEL_ADDR);
}
if ((readl(A11S_CLK_SEL_ADDR) & 0x01) == 0) {
/* SRC0 */

/* Program clock source */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~(0x07 << 4);
reg_clkctl |= (hunt_s->a11clk_src_sel << 4);
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~0xf;
reg_clkctl |= hunt_s->a11clk_src_div;
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
reg_clksel = readl(A11S_CLK_SEL_ADDR);
reg_clksel |= 1; /* CLK_SEL_SRC1NO == SRC1 */
writel(reg_clksel, A11S_CLK_SEL_ADDR);
} else {
/* SRC1 */

/* Program clock source */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~(0x07 << 12);
reg_clkctl |= (hunt_s->a11clk_src_sel << 12);
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock divider */
reg_clkctl = readl(A11S_CLK_CNTL_ADDR);
reg_clkctl &= ~(0xf << 8);
reg_clkctl |= (hunt_s->a11clk_src_div << 8);
writel(reg_clkctl, A11S_CLK_CNTL_ADDR);

/* Program clock source selection */
reg_clksel = readl(A11S_CLK_SEL_ADDR);
reg_clksel &= ~1; /* CLK_SEL_SRC1NO == SRC0 */
writel(reg_clksel, A11S_CLK_SEL_ADDR);
}

/*
* If the new clock divider is lower than the previous, then
* program the divider after switching the clock
*/
if (hunt_s->ahbclk_div < clk_div) {
reg_clksel = readl(A11S_CLK_SEL_ADDR);
reg_clksel &= ~(0x3 << 1);
reg_clksel |= (hunt_s->ahbclk_div << 1);
writel(reg_clksel, A11S_CLK_SEL_ADDR);
}
}
[G1 Android Development] coolbho3000:
Basic C guys. 0.5 can't work because you can't set an unsigned int to anything besides an integer. ;) By the way, the dividers are a 4 bit value. It can hold an integer from 0 to 16.

Edit: oops, already mentioned

If any of you want the Qualcomm MSM7200 docs, just PM me.
[G1 Android Development] eugene373:
Okay thanks... I'll keep playing with it for now & try to make things right.