yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] G Zero:
I can vouch for the fact, for the skeptics out there, it definitely works. Not everything is faster, but the things that are faster, are much faster. Screen draws and basically everything visual is definitely faster (and I expect bench # to illustrate that). Temp? What temp. I have a theory that more clock = less time working the cpu = less thermal retention, and I'm not gonna diefy that yet till more use, but my batt temps are LOWER than stock. 32C on batt @max 628MHz (never seems to call for over that), my g1 bone stock out the box ran @ 35 "Cool".

Ill keep tracking brogress, batt drain etc, but as of now I haven't seen the drawback yet.
[G1 Android Development] coolbho3000:
Okay. You sure it's 5, -1 all the way across?
[G1 Android Development] sahid1haha:
@Jaguirre

thanks a ton man appreciate it.:D
[G1 Android Development] phuKKah:
Well, <3 or not, I have no idea how to apply this to Cyanogen :3

I'll just wait, because I'm not too dev-savvy atm. I've only compiled one thing in my life... and it had instructions.
[G1 Android Development] Artysm:
Please some benchmarks between 528Mhz and 780Mhz !
[G1 Android Development] eugene373:
Yup... Played with it for 3 Days before got a Solid working Kernel that was able to Past 550Mhz..

Changing anything will cause a Lock-up & a Battery Pull will be Needed.
[G1 Android Development] coolbho3000:
Good work. I was too scared after trying 768 and it failed. :p
[G1 Android Development] eugene373:
Magic 32A Confirmed Working with Changes

Same Changes work for a Magic 32A

CONFIRMED:

http://img159.yfrog.com/i/overclock.png/
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Excuse my ignorance good sir, but is BogoMIPS: 975.10 suppose to be the clock speed?
[G1 Android Development] eugene373:
Yes :)

BogoMIPS is the Current Clock speed.
[G1 Android Development] phuKKah:
okay i'm jealous let me in on putting applying this to my current rom pl0x

Edit: lol I actually put this in all caps... fffuuuuu
[G1 Android Development] djluis48:
Hm...cant wait to see this added to a stable rom...

NoobQuestion: How to apply this to my current rom?
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Head Blown

Also are you constantly logging in and out to comment?
[G1 Android Development] JAguirre1231:
He's hidden
[G1 Android Development] phuKKah:
Oh Zalgo and your 4chan.
[G1 Android Development] Frito37:
So we cant have 780mhz on a cyanogen rom but it works on 2.1 @ 780?
[G1 Android Development] eugene373:
If Cyanogen wishes to add this in his Rom, that his Call... But, I'll leave it up to somebody else to compile it for a CMMOD rom for now.
[G1 Android Development] xaueious:
Would like to see this for OpenEclair. That's one ROM that can use this.

Other than that, I would like to see this for my EBI1 Dream
[G1 Android Development] napilopez:
I'm sorry, and not to be a nuisance, but how do you apply this to a ROM? I haven't been around the past few months so I'm trying to come to grips with everything... Is this just a simple flash or do I need to do more?
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
http://images.google.com/images?q=m...ent=firefox-a&um=1&ie=UTF-8&sa=N&hl=en&tab=wi

No, just me and Google. That's how we roll.
[G1 Android Development] BoomBoomPOW:
Already working for OE

http://xdaforums.com/showpost.php?p=5571768&postcount=196
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
This is not a ROM. This is a source. You would need to compile it to actually use it.
[G1 Android Development] eugene373:
What Rom is that?

Been awhile since I flashed somebody else Rom..

Got a link, looked cool :)
[G1 Android Development] JAguirre1231:
Openeclair is what you're looking at
[G1 Android Development] phuKKah:
780Mhz Cyanogen ftw! ...when it happens at least.
[G1 Android Development] Ace42:
Am I seeing correctly?

I would like to try it on Super-D but i'm a bit discouraged considering the Dream has terrible batt life as it is compared to Magic.
[G1 Android Development] kingklick:
thanks bro! great work. :)

going to try to incorporate into my kernel!

:D
[G1 Android Development] GTIChris04:
I can't wait!!!
[G1 Android Development] Frito37:
Someone compile a cyanogen or wg build with it please :D

Even with a ramhack and 780mghz eclair builds are SUPER slow.
[G1 Android Development] Ace42:
This would turn hero into real super-heros!

Cant wait till this is in hero eclair.

Hope no holes burn through my pocket.
[G1 Android Development] JAguirre1231:
Sorry, hoes are for pimps.... which you are not
[G1 Android Development] Frito37:
Phone get hot, Battery Explode, Battery In pocket, Man no have kids.
[G1 Android Development] SeEsAw12:
What eclair builds are you talking about!??!

King Klick's AOSP 1.4 is my daily driver, it's perfect!!

idk about incorporating this though.. I might have to buy that huge battery for it.
[G1 Android Development] Frito37:
Kings and open eclair are no where as fast the wg build I'm using.
[G1 Android Development] Ace42:
I fixed it didnt notice I put that.
[G1 Android Development] SeEsAw12:
They're not as fast yet.. but with the 780Mhz... They will be just as fast.
[G1 Android Development] kristoff123:
There are $30 normal size 1600mah batteries here:

http://www.fommy.com/view-full-page.asp?divid=T-Mobile&model=T-Mobile+G1&skuno=81931#

Assuming there is a stable rom released with the oc'ed kernel, I might get one and hang on to my G1 for another 6 months. That's a cheaper alternative than the $530 I've been considering plunking down for the Nexus One - although, yes, I will probably cave at some point and get that. But I will surely be keeping my G1 as backup phone for quite some time to come, even if it's just for a standalone gps device! I'm on the road 1000 miles a week for work, and I put a lot of thought into what mobile devices I'm carrying.
[G1 Android Development] Ace42:
You should look at some of the other upcoming devices:

http://pdadb.net/

I got my eye on the Shadow or MT-Slide.Would be nice to own a 4G device.
[G1 Android Development] kelvin216:
This is great work to all who were able to get this going can we get a kernal for jac 2.1 rom plz thank u
[G1 Android Development] Frito37:
Actually open eclair with 780mhz Which I tested for a while.

The menu scrolling is laggy.

swipin screen is laggy

basicly everything is laggy but the loading.

Edited again:

Why the hell is everyone wanting a 2.1 rom they suck very bad(Not devs fault.) in my opinion as a daily rom, I perfer speed and quality over shiny features.

The only thing I want is live wallpapers but I can live without it.
[G1 Android Development] JAguirre1231:
I can't live without them, my ADHD requires them now
[G1 Android Development] SeEsAw12:
Oh.

Well my experience without is great.

Scrolling through contacts is flawless with no lag at all same with screen swiping. It may take a while to open apps at times but I have alot of widgets running. Battery life is great.

I'm only comparing it to Super D's 1.8. Although Super D runs apps and browses the web faster it still lags when I scroll down my contacts and kills the battery fast.

You make it seem like it's pretty bad, it really isn't.. but okay.

I'm starting to doubt you've ever even used any Eclair ROM... but okay..

and Live Wallpapers work on King Klicks 1.4 but I don't really like them.
[G1 Android Development] Frito37:
Well its not bad.

There doing a great job but.. I like my phone to be smooth.

If you like or want eclair go for it but its speed its not to be compared to highly optimized 1.6 rom :P
[G1 Android Development] SeEsAw12:
That's true. But.. well I guess we'll see what King releases on his 1.5..
[G1 Android Development] Frito37:
There edited it to convey what I'm saying better :D

Anyways good work so far guys :D!
[G1 Android Development] bigdbag:
When exactly is HTC releasing eclair graphics drivers? Every day I wake up and refresh xda in hopes of news of graphics drivers... what a sad life I lead :(
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
I don't even know. Most 2.X ROM's that I've used either have WiFi and/or bluetooth issues and non have video acceleration.
[G1 Android Development] kristoff123:
Yeah, there's a lot of good stuff in the works.

Honestly, as far as futurephones go, I mainly have my eyes on the HD2 on Tmobile USA. Yes, it runs windows mobile, but there is active work on developing android ROMs for it on XDA, and who can turn down a 4.3" screen?

Also: I am now getting 250 kilobyte/second download speeds with low ping here in NYC. So I am willing to wait on 4g for now.
[G1 Android Development] kristoff123:
yeah, I mean, I would much rather have a fully functioning, stable 1.6 rom than a buggy, slow eclair rom with things that are still non-working. Call me a pragmatist I guess!
[G1 Android Development] linuxluver:
I've run several Eclair builds on my HTC Magic 32B at 528MHz (SetCPU)...and they definitely are not slow. OpenEclair 1.0 and 1.1.1 are right up there with some of the faster Donuts. I have a 64MB linux swap file on a Class 6 SDcard...maybe that helps.
[G1 Android Development] Ace42:
Ouch I get more like 500+

You could try dialing *#*#4636#*#* then goto phone info and do WCDMA only.

That will force you to stay on 3G but will eat your battery faster than you can load HQ videos on a eclair rom.
[G1 Android Development] Macrophage001:
lol I can imagine you with your phone xD
[G1 Android Development] panamakid:
not a dev..just tested

flashed @1:14pm today, phone has been running at 780mhz since, 6 hours later battery is barely at 85% ..the min/max set to 780mhz

This is on my default tmobile mt3g battery...right now my network is out (tmobile) in the houston area or atleast parts...

The overclock works great in my opinion, way smoother.
[G1 Android Development] kristoff123:
um do you mean 500+ kilobytes or kilobits?

250 kilobytes/ sec = 2000 kilobits per second.

I get 250 kilobytes per second - as in I can download a 1 gb file in one hour! On my phone!
[G1 Android Development] Ace42:
bytes

When I tried tether I got 300-500Kbs per sec but that made that phone too hot for me.

But the OC is very good on open eclair and LWPs.But if your smart you wont use 780 cause it has a high ms compared to 600MHZ and lower.
[G1 Android Development] pershoot:
with ondemand governor (booted with 384):

opening up browser, market and downloading from it:

# cat /proc/cpuinfo

cat /proc/cpuinfo

Processor : ARMv6-compatible processor rev 2 (v6l)

BogoMIPS : 778.75

Features : swp half thumb fastmult edsp java

CPU implementer : 0x41

CPU architecture: 6TEJ

CPU variant : 0x1

CPU part : 0xb36

CPU revision : 2

idle for a few seconds->

Hardware : trout

Revision : 0080

Serial : 0000000000000000

# cat /proc/cpuinfo

cat /proc/cpuinfo

Processor : ARMv6-compatible processor rev 2 (v6l)

BogoMIPS : 527.15

Features : swp half thumb fastmult edsp java

CPU implementer : 0x41

CPU architecture: 6TEJ

CPU variant : 0x1

CPU part : 0xb36

CPU revision : 2

Hardware : trout

Revision : 0080

Serial : 0000000000000000

so it is responsive in scaling. im going to try 'conservative' so the scale will be slower, then play with polling afterwards to try and get a good balance.
[G1 Android Development] pershoot:
for sure it runs warmer (battery/case/screen). from load to idle, needed to wait few mins for it to cool down. running this 24/7 might pose a problem. i will play with it, to see if i can get it so only when you really really really need it, itll pin it.
[G1 Android Development] kristoff123:
Wow, I've never heard of anyone downloading that fast. 500 kilobytes per second via tether is way up there! Where r u located? 500 kilobits = 62 kilobytes per second is still normal for tmobile 3g in the us. although parts of the network are faster, such as here in nyc.

So, just as a test, this means you could download, say, a 700mb dvdrip film in about 20 minutes? That is incredible!
[G1 Android Development] chicofiebru:
My conecting direct to a Back Bone with 66mbps :) 1Gb in 15min :)
[G1 Android Development] linuxluver:
If you're running wifi and 3G and overclocking....your phone will get warm. It gets warm without overclocking! It also runs the battery down fast so when it gets low, you plug in the USB or power adapter...and the phone heats right up nice and toasty warm.

I've taken the back off my tethered, charging, 528MHz-set HTC Magic 32B phone a couple of times after an hour or so of tethering as it was getting rather warm......and pointed a small fan at it.

Kept it cooler!
[G1 Android Development] jubeh:
Tomorrow in the news: Guys cell phone explodes in his pocket, burns out his testicles :eek:.

Great work here, and looking at the code, it's funny how this was almost done since September of last year, and just the kinks needed to be worked out (how eugene got the kernel stable by adjusting the scaling).

Which kernel was this built against? I'm checked out the code for 2.6.29-donut but I couldn't get it to build. Any links to a repo?
[G1 Android Development] kristoff123:
lol yeah, i usually put my phone inside my open / modded pc case, and next to a fan thats running there, keeps it from burning out. I tether for my internet connection, so I just plug it into usb and cool it on the same pc. I can play online fps games with no problem, about 100ms lag, which is playable. And my download speeds have tripled in the last 2 weeks thanks to tmobile upgrading their network in nyc.
[G1 Android Development] alan090:
I am able to get 500kb/s here on rogers 21+mbps HSPA network np since I moved to Toronto 3 months ago

Im looking forward to the new X10 as it has 10.2 MBPS HSPA+ radio///
[G1 Android Development] jubeh:
oh, I see, cpuset comes straight out of a 2.6.27 kernel. I'll try building 2.6.29 without cpuset
[G1 Android Development] eugene373:
Be sure to Search for 6 in the 2.6.29 cpuset

& Change

Mainly at ( cpus ) & ( mems ) change the 6 to 5, 5 is the the best Results I've found
[G1 Android Development] eugene373:
Null Post :(
[G1 Android Development] ultra spikey:
Is it a bad idea to set the Minimum to 550Mhz or faster? Setting a higher minimum speeds up the app drawer, home screen, and live wallpapers a lot.
[G1 Android Development] chicofiebru:
Can anyone help me on how i can use this zip file and put on my G1 so i can overclock it? please..im a noob :) but no too noob
[G1 Android Development] Geniusdog254:
Compile your own kernel with that patch applied ;) or you can just wait for ROMs to start using it. Its only been a few hours, just give it time. The KingxKxlicK AOSP 2.1 build is already using it.
[G1 Android Development] Uejji:
The CPU only clocks as high as it needs to. It clocks at the min speed and then when it encounters significant load it clocks higher until the load is complete and then downclocks again.

I doubt the "Refresh" function of setCPU is going to provide the CPU load to max the processor out.
[G1 Android Development] xaueious:
Rogers HTC Dream G1

SPL 1.33.2005

Radio 3.22.26.17

780 MHz shown?

Using setCPU 1.46 in conjunction with setcpu saved under /system/ with contents of:
[G1 Android Development] JamieD81:
which rom are you using for this?? eclair or donut?
[G1 Android Development] G Zero:
Update appears to be sufficient seeing as it gives you more MHz as you turn it up.
[G1 Android Development] daproy:
This edit doesn't make sense.

{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 550000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 560000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 570000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 580000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 590000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 600000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 628000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 650000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 660000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 670000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 680000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 690000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 700000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 728000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 750000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 760000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 770000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 780000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 790000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

{ 800000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

If you don't change the divisor the kernel isn't at a different clockspeed. You can set the first number in the table to any number you want it doesn't make the processor actually clock to that speed without changing the rest of the table. All those values are still clocked at 528000 in reality.

Just add the line:

{ 998400, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 },

and you have upgraded to a snapdragon chip!!!
[G1 Android Development] pershoot:
this is what i was thinking as well, but i did feel the device get warmer. maybe some placebo hit me, hehe!
[G1 Android Development] Frito37:
Hmm that would explain why 528mhz gives you the same benchmark speeds as 800mhz.

Lol so if what ur saying is true everyone who saw a speedboost is actually just imagining it?

If so there is major lulz to be had.
[G1 Android Development] xaueious:
CM 4.2.13

The dev is still testing the patch so it's not for release yet. It should be up sometime tomorrow afternoon for EBI1. The patch will work for all EBI1 devices and includes a built in setcpu config file.

But I too noticed that performance isn't all that great.

Benchmark pi

Edit (benchmarking):

total cpu scores

384/384: 17027 ms

550/550: 12593 ms

780/780: 12268 ms

edit2:

The patch does nothing for my Dream right now. Sad again.
[G1 Android Development] rafcac:
how do I install? thk
[G1 Android Development] sourcesociety:
Yeah, this mod doesn't do anything. At all.

I did a Pi and Linpack test before and after flashing a ROM with this patch. The results were actually worse with the supposed 'increased' clockspeed. To top it off, I'm having extreme difficulty getting another ROM to flash on my phone after using this. I'm not saying it's a direct result of it, but it is rather peculiar that it starts acting up after all this time.
[G1 Android Development] turboyo:
well I dont know if its the fact that i' ve never used the 10mb hack or setcpu in a while.. or if its all in the cpu overclocking but the 550/550 over on my CM .13 with av launcher is definitely faster, no bull (i've been on the rom since it came out like what? almost a month).. would love to try it w/o the 10mb hack to see if that's whats actually making the diff..
[G1 Android Development] kingklick:
haahahaah this is hilarious

how do all the people who flamed me for saying the SAME thing everyone is saying now feel?

classic!

:D

also, glad to see the word I originally used "placebo" is in full force

O.o
[G1 Android Development] Frito37:
Yes this extremely funny!

Also somewhat disapointing :(

LET THE LULZ COMMENCE
[G1 Android Development] kristoff123:
I guess that's why you included it in your newest ROM, hehe.
[G1 Android Development] Phil_McRevis:
lol so i was wondering about the changes that i was trying to adapt to the 32a board but i'm wondering if this is total bull or not... i mean the battery is getting hotter but the benchmark speeds are the same

http://xdaforums.com/showpost.php?p=5575762&postcount=24

and does this mean that that post is TOTAL bull? because he did say that his benchmark for 1ghz was 210ms and that for 528 was 530ms
[G1 Android Development] kristoff123:
I wouldnt count it as bull just yet. At the very least, this was worth looking into, so we know once and for all if the dream/sapphire cpu can go faster than 528mhz.

Let's get some more tweaking and benchmarking results in before we start pounding nails in the coffin lid, lol!
[G1 Android Development] IConrad01:
It's got to be doing /something/. My boot times are significantly reduced w/ this, the UI is decidedly snappier (items that were lagging above the noticeability threshold now seem instantaneous; etc.)

SetCPU benchmarking is also giving lower numbers while in the ~628 CPU freq (~550 best as opposed to ~720 best).
[G1 Android Development] linuxluver:
Agreed. I've got KingKlick's AOSP 2.1 v1.5 running on my HTC Magic 32B. He's using the Overclocking Widget. The advantage of that is you can set it to report the CPU speed every 10 seconds (if you want)...and the phone is *definitely* scaling up and down in response to loads. Try starting the "Fire" live wallpaper and watch the CPU reach for the skies - 759MHz - then set the phone to doing not much....and maybe go into standby....and then it's doing 245MHz.

Overall, it is beyond dispute (IMHO) that the phone is running faster. The network seems too go faster too. I've seen LAN through put close to 3.5 Mbps...whereas the norm is closer to 2 Mbps over wifi.
[G1 Android Development] markolo25:
Well from what i understand the CPU can go to 780 but like in PCs if you have a bottleneck like ram or chipset you will only go as fast as that. so we may be able to go 720-780 but ram is still limiting the speed of the data cycle. i think this is why cyanogen even though he couldve reached these speeds before, he just stopped at 520 because he saw no benifits beside a number bigger. so i guess the speed boosts are imaginary:) because my g1 slowed down after reading king's post but i was still happy to experiance happiness with my g1 ;) in an eclair rom. Also network and g1 speeds are faster because when i tether it is sofa king faster than what it used to be.
[G1 Android Development] xaueious:
Guys I'm not convinced that this is in fact NOT working. Or at least, it wasn't working for the frequencies I tested. Those frequencies include 550 MHz, and 780 MHz.
[G1 Android Development] markolo25:
it is working but now working to what we were expecting it to work like :D because i imagined the g1 doing nexus things at full speed, but if we do get hardware acceleration later on we will get a more massive speed boost.
[G1 Android Development] daproy:
The PLL2 hardware is clocked at 1056 MHz, hence 528000 comes from ACPU_PLL_2 / 2

{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 128000, 0, 5, -1 }

Changing the timer name from 528000 to 780000 or 998400 or whatever and not changing these values will not overclock the phone.

The BogoMIPS value shown in cpuinfo is calculated at boot time and then updated in /proc/cpuinfo bogomips by scaling the originally calculated value by the current processor clock timer (or whatever number you put above).
[G1 Android Development] markolo25:
i think what daproy is trying to say that changing the number dosen't do sofa king much to our devices. and only changes the number and dosent actually do much to cpu so we didn't really do anything. is this what you ment daproy.
[G1 Android Development] daproy:
The BogoMIPS value comes from loops_per_jiffy or lpj field in the acpu_freq_tbl which is in initialized in /arch/arm/mach-msm/acpuclock.c

/* Initalize the lpj field in the acpu_freq_tbl. */
static void __init lpj_init(void)
{
int i;
const struct clkctl_acpu_speed *base_clk = drv_state.current_speed;
for (i = 0; acpu_freq_tbl[i].a11clk_khz; i++) {
acpu_freq_tbl[i].lpj = cpufreq_scale(loops_per_jiffy,
base_clk->a11clk_khz,
acpu_freq_tbl[i].a11clk_khz);
}
}

As you can see it uses the a11clk_khz value (the first value in the freq table struct and the one being changed) and expects it to be honest.
[G1 Android Development] xaueious:
I know there has been a user reporting success with the overclock, but in my testing all speeds were same past 528 MHz.

I wasted time on this today. Devs don't bother compiling this.
[G1 Android Development] domenukk:
I've done some basic benchmark with setcpu and must say - it is faster!

On this (rather lame) openeclair rom I reached above 1000 ms for 520 and below 700 for 780!

So there definitively is a faster clock speed above 520mhz! :rolleyes: