yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Icebergxx:
Just ****ing quit being so egotistical @everyone arguing about whatever dumb ****.

Your job in life isn't to educate you're not a teacher you're just some idiot that's mad on the internet trying to push lines of red rovers back because you say A and someone else says B. And while you're at it quit thinking in terms or "Right" or "Wrong" and try to ****ing LEARN for once.

This is what I have to contribute to this thread haha sorry just saw some people arguing and it bothered me the way it went about.
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
OH HELL YEAH!
[G1 Android Development] JAguirre1231:
Might as well get a little tongue while we're at it
[G1 Android Development] legend1222:
Speed

Great explanation. BUT, aren't the bogomips listed in /proc/cpuinfo the radar gun sitting on the side of the road saying that this is definitely faster?

Bogomips don't lie as far as I know, do they? Thats the clear answer I would like (with intelligent proof, not religious conviction)
[G1 Android Development] JAguirre1231:
The bogomips are a lie
[G1 Android Development] BoomBoomPOW:
LOL @JAg & Zal made my day.
[G1 Android Development] bbrown0179:
can't seem to get working

i downloaded the speed kernel source but what do i do with it tried restarting phone by pressing home and power but it said that it wasn't signed so it didn't apply. so what now
[G1 Android Development] Ace42:
You don't flash it you must build a kernel in linux to actually use it.
[G1 Android Development] coolbho3000:
Oh yeah, totally fake. That's why it's been used since April of last year, that's why I've spent so many hours on it. :eek:

In short, SetCPU thinks the CPU is running at those speeds (look at BogoMIPS! Don't you go on saying that's fake too!), but in reality, it isn't.

Really, don't go on talking about something if you don't know **** about it.
[G1 Android Development] BoomBoomPOW:
Translation

"Don't ever mess with a black man's radio!" - Rush Hour
[G1 Android Development] JAguirre1231:
I think you over-reacted
[G1 Android Development] BoomBoomPOW:
Hahahahaha
[G1 Android Development] digitallysick:
I'm not talking about the Mod'd kernel , The everyday normal Kernels, how do we know that setcpu actually works and isnt doing the same thing? If the cpu speed is set at the hardware level

No need to take it as an insult, I would like to think that it works but what is the difference in this kernel not working and the normal setcpu with the average rom , how can you overclock when the chip is set at a specific speed on a cell phone.
[G1 Android Development] Geniusdog254:
How hard is it to understand??? The kernel normally has the PLL set up to work with 528Mhz. That is completely normal, the difference is the cpu scaler is set to only got to 384 max & 245 min. The only exception is Roger's Dream kernels, which are for some reason set to 528 max 245 min OOTB. SetCPU just changes the cpu scaler to work with the built in PLL levels.
[G1 Android Development] coolbho3000:
Benchmark it. Anything. Use benchmark, benchmarkpi, even setcpu's own benchmark at different frequencies. Load some cached webpages at 528 and again 245, and time it.

Again, please do the least bit of research before posting baseless speculation.

kthxbye
[G1 Android Development] Ace42:
before you become one with the wind, can you explain why ms is lower with 580 then with 528?

I know everyone says its just the place thing.
[G1 Android Development] coolbho3000:
Probably experimental error. Try it ten times, performance governor (or ondemand with both max/min at the same speed) at both speeds and average all of them out.

I've worked with the kernel source quite a bit, and from what I know about how CPU scaling works, you can't use speeds that are not derived from the output of the PLLs. You are free to prove me otherwise.
[G1 Android Development] shadowmike:
exactly. even at 780Mhz benchmark drops drasticly. 528Mhz 1000's range 780Mhz 600 - 700
[G1 Android Development] Ace42:
Im not saying your wrong was just wondering why the ms was lower.
[G1 Android Development] coolbho3000:
And I said it was probably experimental error. There are a lot of things that can affect benchmarks.
[G1 Android Development] digitallysick:
I don't think its baseless, setcpu when overclocked on this kernel provides good numbers as well, but its been proven it doesn't work

So clearly the benchmark tool can say its working, and that doesn't mean that it is.

Could you explain to people such as myself, how it overclocks if the chip is locked at a specific speed, without any type of voltage mod?
[G1 Android Development] Ace42:
On a side not, I read some where the Dream has a Dual-core but one is used as a gpu. Can that core also be modified in anyway?
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Just to add my 0.02$ (double-dollars) I ran some benchmarks with Neocore.

780/128Mhz - 22.2fps

550/128Mhz - 21.1fps

I only ran two tests (I'm that lazy), so interpret that anyway you want to.

But in other news my Dream has been running since 4:30AM CST and is at 46% now.
[G1 Android Development] Geniusdog254:
See my post at the bottom of page 23. I seem to have quoted your last post, and answered that exactly.
[G1 Android Development] coolbho3000:
I'm one of the people saying it isn't working. Are you saying that I'm reading the CPU speed and then using it to fabricate a benchmark score? ;) Try benchmarking with another tool if you doubt the integrity of SetCPU, or write your own benchmark (I'll give you props if you can even get anything to compile ;)).

Again, don't talk about something you know nothing about.

The CPU has PLLs set at certain speeds. We do not know how to the speeds the PLL runs at yet. There is one PLL running at 1056MHz, another running at 768MHz, and two slower ones. To derive CPU speeds, we have to divide these PLL speeds by whole numbers. 1056/2 = 528. 768/2 = 384. 1056MHz and 768MHz are theoretically possible, but daproy and I have tried 768MHz and this froze both our phones (no voltage increase either). Read our prior research into this issue.

This kernel mod defines frequencies that are not possible. You can tell SetCPU to try to set these frequencies, and it will, and the kernel will report that these frequencies are being set too. But they aren't.

Again, set it to performance governor, run any benchmark several times, take the average, make sure all your other variables are the same between the trials (same kernel, same ROM, same background apps). If you can consistently get a considerable and statistically significant percent increase from 528 to something higher, then this mod works and what we understand about PLLs is wrong.
[G1 Android Development] daproy:
This was tried a long time ago. Phone locks up and you have to pull the battery.

http://xdaforums.com/showthread.php?t=557863&page=2
[G1 Android Development] houseonfire:
I do not notice a significant increase past 550mhz. I really wanted it to work at 780, but it doesnt.
[G1 Android Development] daproy:
I AM NOT RESPONSIBLE IF THIS FRYS YOUR PHONE! CONSIDER YOURSELF WARNED!

Here is a boot.img for CM 4.2.14.1 containing a kernel with the overclock coolbho3000 and I tried a while back. It caused our phones to lock up and require pulling the battery.

WM users gave mixed results, some had it work for 20 sec, some not at all, some only on AC or with the radio off. I am curious if this works for anyone without freezing?

Here is the altered acpu_freq_tbl:

/* Table of freq we currently use. */
static struct clkctl_acpu_speed acpu_freq_tbl[] = {
{ 19200, ACPU_PLL_TCXO, 0, 0, 19200, 0, VDD_0, 30720, 0, 0, 4 },
{ 122880, ACPU_PLL_0, 4, 1, 61440, 1, VDD_3, 61440, 0, 0, 4 },
{ 128000, ACPU_PLL_1, 1, 5, 64000, 1, VDD_3, 61440, 0, 0, 6 },
{ 176000, ACPU_PLL_2, 2, 5, 88000, 1, VDD_3, 61440, 0, 0, 5 },
{ 245760, ACPU_PLL_0, 4, 0, 81920, 2, VDD_4, 61440, 0, 0, 5 },
{ 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, 8 },
{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },
{ 768000, ACPU_PLL_1, 1, 0, 128000, 5, VDD_7, 128000, 0, 6, -1 },
{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
};
#endif

#ifdef CONFIG_MSM_CPU_FREQ_ONDEMAND
static struct cpufreq_frequency_table freq_table[] = {
{ 0, 19200 },
{ 1, 122880 },
{ 2, 128000 },
{ 3, 245760 },
{ 4, 384000 },
{ 5, 528000 },
{ 6, 768000 },
{ 7, CPUFREQ_TABLE_END },
};

You can force it to scale up to 768000 with:

# echo 768000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

# cat /proc/cpuinfo

or using coolbho3000's excellent SetCPU.

http://www.mediafire.com/?2gdeym1nm2z

Please don't try this unless you are willing to risk your phone in the process!
[G1 Android Development] daproy:
Sounds like No2chem tried this with PLL2.

"1) I’ve tried to see if I can adjust the output value of PLL2. It appears that a clock control register under the control of the ARM9, DCPLL1_L_VAL_REG, controls what the output frequency of PLL2 is. It appears to be a multiple the TCXO 19.2MHz clock – the default value is 0x7, and when I set it to 0x1, the device operates as if it is running at 19.2MHz. 0x2 – 0x6 causes crashes."
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Sooo... anyone gonna try this?
[G1 Android Development] Pfeffernuss:
Stock 528Mhz is also around 700. 780Mhz is no way 35% faster. Impossible.
[G1 Android Development] kingklick:
why would anyone want to try it after he just said all it does is lock your phone up

:rolleyes:
[G1 Android Development] kristoff123:
Possible to add a 704mhz freq to this (= 176 x 4)?

- It seems the phone freezes up when approaching 800mhz, maybe 704mhz would be more sustainable if it works.
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Ah too late. My curiousity got the better of me :p. It did in fact freeze my Dream on boot :D. Good thing I backed up eh?
[G1 Android Development] Enrapha:
I'm Confused

So I have gone through this entire post trying to figure out exactly how to overclock my cpu past 580 in my mytouch 3g. So far I get a bunch of giberish and no support. can anybody post a thread or e-mail me to help me know what I am reading? I downloaded the kernal but how do I implement it into my existing kernal?
[G1 Android Development] kristoff123:
So, from what I gather, the clock freqs are multiples of either 128 or 176, right? so maybe implement 5 x 128 = 640, or 4 x 176 = 704? Maybe those are more sustainable / stable?

Sorry, I know it's just basic math. I just hadn't seen these frequencies mentioned, I'm sure I might be misunderstanding something.
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Honestly, I don't even know. But what you're saying does sound logical.
[G1 Android Development] lotherius:
2 things here.

1) See the topic title? It says [Rom Cookers].. Are you a Rom cooker? No... I don't think so. It doesn't say "End user support for a well-completed & stable feature" eh?

Okay and the real answer:

2) This doesn't work. There is no support because it doesn't work, it was all a mistake. We thought it worked, then we proved it didn't. So your MT3G cannot go past 528mhz. End of story.

Finally - maybe someone should edit the original post to clarify this doesn't work for those coming in late?
[G1 Android Development] kingklick:
I thnk this is hilarious

if you guys look at the thread, I was the first to label this a complete placebo, only to be flamed by numerous "know it alls" who clearly knew NOTHING lol

maybe this is one step closer to you all seeing that "big bad meanie king" truly isnt always trying to stir trouble :p

EDIT: I labeled it a placebo in the other thread, "Prepare for stable 550Mhz ROMs"
[G1 Android Development] kristoff123:
Kingclick, maybe you were right, but for the wrong reasons - there were things we didn't understand about the freq tables until this thread was started.

And, then again, maybe you were wrong - look at the last few pages - there is a different freq table than the one we had been using that definitely does SOMETHING (i.e. crashes the phone) when clocked up to 780mhz. We are wondering if it can be rewritten with new multipliers to clock a little lower instead. I think this is going to be hashed a bit more before there is a definitive answer.

In either case, no need to rub it in, this isn't a competition of who is right or wrong, it's a scientific experiment which would go a lot more smoothly if we had more complete data from Qualcomm.

And, finally, in case you hadn't noticed, you are STILL including the kernel in your latest ROM - why do you keep doing that if you are so bloody sure about it?

If you're not contributing to this thread, please just back away and observe, rather than trying to steer it into a premature shipwreck. Thank you.
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
The reason no one listened to you or labeled you a "know it all" is because of your attitude. You came in this thread calling the overclock a placebo without giving any logical or scientific reason all while sounding arrogant and down right idiotic.

And if you're going to sound like that no one is going to listen to you even if you are right or wrong.

​
[G1 Android Development] kingklick:
lmao

sorry guys didnt realize pointing out benchmarks ARE EXACTLY the same from 528 to 780 was being arrogant

;)

P.S.

why would I change out my kernel when it does NOTHING at all, making my kernel THE SAME as the one before it without the cpu "hack"
[G1 Android Development] kristoff123:
Too funny!
[G1 Android Development] Klyentel:
So the fact that it works is no longer a debate, Its official that it does not work.

but what about the performance increase? I myself and other users have and still are experiencing that...

so just because it doesn't work for you, devs are not going to put in any future builds??:confused:
[G1 Android Development] Frito37:
Well when its proven fact that it does nothing you move on because it would be completely retarded to include something that does nothing in a build.

You my friend are in g1 denial.
[G1 Android Development] Klyentel:
Makes sense.

What am I denying? If it makes my phone faster, it makes my phone faster. I don't have to lie about it, to myself or anyone else for that matter.
[G1 Android Development] Frito37:
It doesn't make ur phone faster its impossible. So by thinking it actually is after you know its not, is being in g1 denial.
[G1 Android Development] Klyentel:
Hmm..? Your point stands valid.

Yet in this case, I will have to agree to disagree.

It's makes my phone faster, hands down :cool:
[G1 Android Development] ivanmmj:
It makes your phone ramp up to 527mhz faster and stay at that speed longer. Download SetCPU and just tell it to keep your phone at those speeds. Problem solved.

The Arm9 is used as a coprocessor for a lot of stuff already.

It's not a true dual core in the sense of Desktop Dual Cores.

CPU is set at the hardware level by the kernel. If the kernel reports that the CPU is going a 2GHz, then SetCPU will think it's going that fast, even if it isn't.
[G1 Android Development] legend1222:
Ok... I realize this is a G1 forum... BUT ... i do this on my 32A, simply because people claim setCPU is kinda bogus (I don't), and I get the exact same results with setCPU. IT WORKS.

So again, joking aside, is the cake a lie?

"Proof:"

# find . -maxdepth 1 -name "*" ! -type d
./cpuinfo_min_freq
./cpuinfo_max_freq
./scaling_min_freq
./scaling_max_freq
./affected_cpus
./related_cpus
./scaling_governor
./scaling_driver
./scaling_available_governors
./scaling_setspeed
./scaling_cur_freq
# find . -maxdepth 1 -name "*" ! -type d -exec cat {} \;
19200
800000
245760
580000
0
0
ondemand
msm
ondemand performance
<unsupported>
580000
# echo 768000 > scaling_min_freq
# echo 768000 > scaling_max_freq
# find . -maxdepth 1 -name "*" ! -type d -exec cat {} \;
19200
800000
768000
768000
0
0
ondemand
msm
ondemand performance
<unsupported>
768000
# cat /proc/cpuinfo
Processor	: ARMv6-compatible processor rev 2 (v6l)
BogoMIPS	: 758.78
Features	: swp half thumb fastmult edsp java
CPU implementer	: 0x41
CPU architecture: 6TEJ
CPU variant	: 0x1
CPU part	: 0xb36
CPU revision	: 2

Hardware	: sapphire
Revision	: 0080
Serial	: 0000000000000000

Obviously you have to be able to understand the above command lines.

I tried 800000 but that falls back to 527....
[G1 Android Development] ttabbal:
Someone posted the code where the bogomips value is calculated, based on the values in the frequency tables. On our ARM based phones, the bogomips value means nothing. It's not derived from anything other than the values in those tables, which the hack changes. Garbage in, garbage out.

For those seeing a speed increase, it's likely sticking the CPU at the higher speeds more of the time as mentioned. Also, at least with the SuperD kernel hack, Compcache doesn't work. Disabling Compcache results in the same speed increase on my device at the standard 528Mhz settings. IMO, compcache doesn't work well on a G1 due to the memory bandwidth and CPU speed issues.

I've been running with OpenEclair 1.1.5 for a couple days now. I noticed it getting slow and disabled compcache. Checking "free" for a while till it slowly went away, and the phone was significantly faster while SetCPU was set to 128/528. Swap has some potential, but we use the SD for so much already, I'm concerned about bus contention slowing access to the SD card.

Now if we could just get a Nexus with a keyboard. I'd be all over that.
[G1 Android Development] Klyentel:
Amen to that! That's the only stand back between me and the Nexus...a keyboard.
[G1 Android Development] sunjon:
CompCache is working on SuperD 1.8, you just don't have the ability to disable it from Spare Parts atm. See below:

Sunjon
[G1 Android Development] georgegreco86:
I can guarantee that you will see a signifigant change in speed on your phone if you set it up to standard, it might be better if you go with the SuperD rom, i am using that and it runs like a damn nexus, its crazy..

theres a foroum on here thats specifically for that .. Carlospants its called, simple zip, and flash, reboot, than load SetCPU with the custom setcpu.txt. My phone hauls some serious ass.
[G1 Android Development] legend1222:
Thank you. I apparently missed that. Scientific proof always wins out against belief in my book. :D
[G1 Android Development] coolbho3000:
damnoregonian mentioned that only the ARM9 is supposed to control the L values. Isn't this set in the radio firmware? If so, unless someone's willing to risk a 99% chance risk of bricking their phone to test it, there might be no way (until we can jtag flash the radio firmware). Perhaps we can compare the radio of a Turbo device with the radio of a normal device, then make the necessary modifications.

Again, editing the radio equals a truly bricked phone (radio boots first, so you get no access to SPL or anything) if everything does not work perfectly the first time. Best to wait for jtag unless we can figure out how to properly write the L value in the kernel.
[G1 Android Development] ttabbal:
I'm aware. The overclock kernel breaks the compcache module though, so it can't load up and thus no compcache if you install it.

If you want to see if the stock speeds vs. the (reported) overclock speeds make any difference, just tell setCPU you have a G1 and set min and max to 528. That made the phone run the same at setting it to 780 for me. Devs smarter than me, including Eugene, have stated that it's not actually clocking the CPU faster, just changing the display value. Maybe they will find a way to do it, it would be a cool way to get a little more life out of our G1s. Maybe we can keep them going long enough for a worthy successor to be released.
[G1 Android Development] Frito37:
Wow even after being **** you still have a educated response to me.

You my friend are rare find on a forum, I understand your point completely though.

I would kill for a nexus one with a g1 keyboard. *Drools*
[G1 Android Development] Krovee67:
Is anyone else having problems flashing this kernel with thier G1?

Ive tried flashing it while SetCPU was installed then I tried flashing then instaling SetCPU

I get an error

E:No signature (6 files)

E:Verification failed

Installation aborted

Anything im doing wrong or should be doing?
[G1 Android Development] AngioNicholai:
How can i check how much mhz im running, is there a adb command or something similar?
[G1 Android Development] BoomBoomPOW:
adb shell cat /proc/cpuinfo
[G1 Android Development] lefeudedieu:
set cpu

hello i'm french

I can not have my dream overcloker BEYOND 528MHz but I setcpu.txt create the file in SD, I just change the frequency to 800MHz in setcpu but he was always up to 528MHz?

what about increase the cpu?

Please help me

DREAM

Radio: 2.22.19.26I

haykuro's SPL + Recovery-RA-dream-v1.5.2

Rom: CyanogenMod 4.2.14.1 RoustEd v1.6-2beta
[G1 Android Development] macher91:
You can't. It was mistake and it no increase power
[G1 Android Development] lefeudedieu:
sorry

but i see this :

youtube.com/ at 800mhz

it's possible no ?

thanks
[G1 Android Development] Firerat:
in setcpu use menu button , device selection

at the bottom of the list is the custom setting ( use setcpu.txt )

BUT

528 is the max, no point going beyond this

I did some crude tests and performance levelled out at 528.

( average time taken to gzip a 10mb file that I created with dd and /dev/urandom, , ok ok so in itself not conclusive)
[G1 Android Development] lefeudedieu:
ok thanks for your answer

I understand BEYOND overclock of 528 mhz does not improve performences the dream is so useless!

by Toulouse France
[G1 Android Development] HazzBazz:
Im trying to work out what happend to eugene...his twitters deleted and he hasnt been on xda for aaaaaages. Got driven away again. King said that the hack wasnt doing anything...does that mean it was a scam or had it no performance increases? Because apparently the freq hacks on the nexus are working really really well!?
[G1 Android Development] domenukk:
he stated that 580 mhz is possible... last statement to this overclocking thing I think
[G1 Android Development] Firerat:
NO not true !!!

The Dream beats Nexus One at having a keyboard

do ctrl+a if you don't belive me
[G1 Android Development] ivanmmj:
The nexus one had hacks involving changing the CPU multiplier and voltage. This hack including changing the title of the SAME multiplier (no voltage) to say it was running at a higher speed. He didn't realize that it also required a multiplier change. (Which we can change, but the next step up is not stable.)
[G1 Android Development] lefeudedieu:
Is there a ROM that is already overclocked?

or add files has to go further than 528MHz?

kernel?

I do not understand I created the text file setcpu.txt the frequency I just go from 128 to 780 but does not appear in the top left menu setcpu rest to 528

it exceeds 528MHz in the top right

Yet I have seen on youtube this frequency in the top left unchanged!!

Excuse me for my bad English spoken

DREAM

Radio : 2.22.19.26I

haykuro's SPL + Recovery-RA-dream-v1.5.2

Rom: CyanogenMod 4.2.14.1 RoustEd v1.6-2beta
[G1 Android Development] zachattack052:
this dosen't work
[G1 Android Development] ivanmmj:
Read one post above yours.
[G1 Android Development] 1wingangel:
Why does this thread keep getting dug up?

I thought we confirmed that it doesn't do anything,or is there new development or something?
[G1 Android Development] Firerat:
because its not been locked and people think it is quicker to ask than to read :(

it doesn't work

no new development, just new people watching old youtube

hmm, maybe new youtube detailing proof , Link BIG, close thread.
[G1 Android Development] coolbho3000:
The reason it's not scaling past 600 some MHz is because the steppings need to be changed, I think. Ondemand should push the processor to max as soon as that up threshold is reached.

daproy explains it here:

http://xdaforums.com/showpost.php?p=4501464&postcount=12
[G1 Android Development] kristoff123:
I'm glas you started a proper thread for this, eugene373. Now you get to deal with the likes of kingclick trolling around in your thread, telling everyone how useless this is ;-0

Great work though - my theory is that this will make compcache and apps2sd faster as well, essentially giving eveyone's g1 a ram, rom, and cpu boost!
[G1 Android Development] eugene373:
The Stepping are Fine...