yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] coolbho3000:
Using the setcpu custom config option is the "proper" way to add support for new frequencies. It just so happens that 550MHz is a valid frequency on the Droid as well, leading to the initial instructions. I hardcode available frequencies in as there is no way to detect them on older kernels.
[G1 Android Development] eugene373:
Guys, imo Please Support SETCPU, It was only used for Testing & is a Great Utility to have. Plus, the Price is affordable :)
[G1 Android Development] bunu:
I will love you always (no homo) if you can make a flash-able kernal (kind of like bfs xxx for hero roms) and it is compatible with eclair and donut roms (maybe hero if we are lucky)

This is amazing! I can't wait until devs put the highest cpu settings in their roms (like they can scale it up to 528 mhz but people can change it to like 550 mhz or above using SetCPU)
[G1 Android Development] sitimber:
FROM TWITTER ]

charansingh MY MAGIC 32a running at 1ghz , f u nexus

http://yfrog.com/4foverclockp
[G1 Android Development] borodin1:
I surely did, and wouldn't have any other way.

This update seems to break multi-touch. Is that right or did I do something wrong? Open Eclair 1.0 on G1.

At any rate, it's worth it. Thank you everyone who was involved.
[G1 Android Development] Frito37:
Tobad the nexus is still much faster :(
[G1 Android Development] eessel:
Yeah..because of the ram it has. The lack of ram over 200MB is what is holding the g1 back from just being a comkpetitor with the droid/magic/hero
[G1 Android Development] jubeh:
So you basically just updated the kernel with new available frequencies, these happened to be compatible with the Droid's multiplier, and it worked?

I guess I can see that, but it kind of throws off everything we knew before about how the msm7k worked.

You're the one who made this? What's your take on why it's reported that it "only works on eclair"? isn't the kernel just the kernel? From what I've seen, only the wlan module and a couple libraries are kernel dependent, so everything else should still work fine, or is it just people trying to use the whole boot.img instead of just the kernel?

And, you said that SetCPU is the proper way of setting the speed, care to elaborate? What if I wish to make a rom with intelligent scaling from 128 to 528 with stops at 780 every now and then, what would stop me from doing it?
[G1 Android Development] kingklick:
I dont see how it could only work on eclair ?

I just added it into a donut-based kernel and compiled and used my kernel just fine

also, on a side note, not to be a ****, but Im sensing that him saying that is a little biased..........

isnt he the creator, seller of the app???

lmao
[G1 Android Development] JAguirre1231:
Eugene actually made this, and it doesn't work on only eclair. It just happens that it is only a noticeable boost on eclair and people took this as "only eclair".
[G1 Android Development] eugene373:
:D Glad Somebody Listen to me... I've said many of time is works on 1.6 & eclair... Should work fine on 1.5 as well :)

Saw you added it into your 1.5 build :)

Hope it works out Perfect for you :)
[G1 Android Development] zachattack052:
exactly how would you apply this to a rom other than OE?
[G1 Android Development] coolbho3000:
Honestly, if you don't want to use SetCPU then echo the values into cpufreq yourself. SetCPU is for application-based automatic and manual control of CPU frequencies after boot.

To clarify, I said using the SetCPU custom frequency config was the proper way to tell it the frequencies to use, rather than improvising by using the Droid config. I didn't say it was the proper way to set the speed, period. You don't have to use SetCPU if you don't want to. If you want to, SetCPU can help you out with profiles and manual control. Btw, it's free on XDA anyway.

Nothing, but I would like to ask that you implement it as a separate CPU governor rather than slapping it onto ondemand (like HTC did with perflock).
[G1 Android Development] JAguirre1231:
And that's why I included it with the openeclair, if it wasn't free I would've told people to buy it because that is how awesome it is :D
[G1 Android Development] jubeh:
i see

beware that 2.6.29 kernels break camera in stock cupcake (havent tested on hero cupcake)
[G1 Android Development] eugene373:
I agree 100%, but Support is Nice :) & it a Perfect app I can't live without..
[G1 Android Development] jdwash11:
do you have a link to this build? I did a search and am not finding any builds by the name of "WG-Build Y" so I'm not sure what to download.

would like to give it a try though :D
[G1 Android Development] Frito37:
Tested on newest wg build and

with the pi benchmark

384mhz 17s

528mhz 12s

550mhz 12s

780mhz 12s

800mhz 12s (idk It let me move it to 800 and it said it was on 800)
[G1 Android Development] jdwash11:
nevermind I found it

http://xdaforums.com/showthread.php?t=592466
[G1 Android Development] G Zero:
Hmmm ...me thinks something strange is going on here.

I noticed my g1 never asks for a frequency above 628, so I figure hell, might as well turn it down to 628. You'd figure it'd still ask for 628MHz right? Nope! 528 max. Turned it up to 670, it maxed at 550, 728 = 590, and 750+ = 628.

I dunno. I don't get it. Check it out for your self. Open setcpu and input the amnts I show you, then keep pressing Update.
[G1 Android Development] Phillzug:
Which kernel did you use? JAguirre's? I tried flashing that on Y-2.6 and it hung at the 1st boot screen
[G1 Android Development] phewizzo:
so wait. how did you get to do 600+ mhz with 1.6? i see u only released 550mhz kernel for 1.6 and 700 for 2.1.. how can i try out more then 550mhz on a donut rom? can u post the kernel? i try going past 550 and it stays at 550 even though i set it higher. Thanks.
[G1 Android Development] Frito37:
I flashed wg donut build.

Then flashed the kernel for the eclair rom..

It booted up fine and overclocked to 800mhz after I edited the setcpu.txt

Stuff like usb teathering didnt work obviously.
[G1 Android Development] phewizzo:
im also on the WG donut build... I flashed the kernel. Its on 550. I edited the setcpu.txt to numbers greater then 550mhz. but when i push it past 550mhz using the custom scaling. the BogoMIPS stays at 549.12 no matter how high i set the max MHZ to.
[G1 Android Development] atgrande1:
Just curious to know if anyone has compiled this Jac's for X-rom Eclair, I hear everyone talking about every other rom but that one, and if someone has I would greatly appreciate if someone could steer me in the right direction thanx?!:confused:
[G1 Android Development] Kutttt:
Could the video driver be implement into this ROM. I am unable to use the NBA showtime and TV apps that I paid for and it is a real shame. I know KiNgxKxlick just implemented video playback so please put it in for the sake of the community include this if it is not a big deal, thank you.

P.S. Donations are on the way.
[G1 Android Development] Frito37:
NEWS FLASH :P

THIS ACTUALLY DOESN'T DO ANYTHING SO THERES NO POINT TO INSTALL ANYTHING POSTED IN THE THREAD SO FAR.​

:( I'm disapointed.
[G1 Android Development] lotherius:
Ummm dude, the bold and huge print is uncalled for. And yes, it DOES do something if you install it right, even on the G1...

I have done extensive benchmarking on this (not seat of the pants "feels like"), and have written that up here: http://xdaforums.com/showpost.php?p=5576729 with numbers and everything.

Will it make your G1 as fast as a Nexus? No.... does it do something, yes.
[G1 Android Development] kingklick:
thanks for the link to your test runs bro

just tweeted the link, so over 1500 people can see what is hopefully the truth!

:D
[G1 Android Development] xillius200:
Even though the benchmarks don't change much you can see the difference. Running live wallpapers on eclair at 780mhz it doesn't freeze running at 550mhz it doesn't freeze at 528mhz and below it does. Playing games are more smooth as well same for opening apps but im using 780mhz as there is not even a bit of lag 780mhz seems better than 550mhz for live wallpapers YOU CAN SEE THE DIFFERENCE :)

Running htcmusic.apk at 550mhz it is better at loading and running it at 780mhz it's straight up :)
[G1 Android Development] Deicist:
No eclair roms have video drivers yet. King's new rom has youtube low quality playback, as do most 2.0 roms (as opposed to the 2.1 roms that most people are pushing out).
[G1 Android Development] Pfeffernuss:
Unfortunately your "extensive" benchmarking is rather bogus. The biggest "difference" you encountered was with the higher CPU result.

Well, when running a STOCK 528Mhz Rom I have the exact same result as your "628Mhz" test (value: 161). Meaning: 628Mhz is ZERO percent faster as 528Mhz.

As has been mentioned multiple times. Run the benchmark again and see for yourself. But no, people "notice a difference" so it múst work. Unfortunately it does not, as has been told by other people, who actually tested it (properly) as well.

The overclocking tool does... not... work. It's all in the mind. It does nothing. If you do notice a difference, nice, placebo effect at full force.
[G1 Android Development] JAguirre1231:
It does do something (I've run numerous tests), it just doesn't do as much as we would hope. If you're running a donut rom, Eugene has already said that it is not noticeable (and I'm guessing won't show in tests), but it DOES make a difference in Eclair roms. I've never seen smoother lwp's
[G1 Android Development] eugene373:
I understand why you Would be Hating on the OC, but the Truth is, the 32b boards are limited to memory Bandwidth, SO any PI benchmarks & Most Benchmarking Utility's will not show much Difference in a Benchmark Untility.

Mainly the CPU can Load things Faster, but that about all the 32b Boards can Gain with the OC due to Memory Bandwidth.. SHEESH!!

With that being said, There is a Huge Benchmark Gain In the Following Phone's Overclocked...

Cliq, Magic 32A....

Don't Like the OC, then get a Phone that can Really Put use to It & stop Complaining.
[G1 Android Development] Pfeffernuss:
Tried it on Eclair as well. Same thing. No *noticable* difference.

Run some tests, show us the results. Subjective things don't matter.
[G1 Android Development] eugene373:
LTD= Learn TO Read!
[G1 Android Development] Pfeffernuss:
People are "noticing" stuff on ANY type of phone. That is what is so annoying. It just isn't true. It's *subjective*.

Complaining is fair enough as it's the same kind of thing that they are proclaiming.
[G1 Android Development] JAguirre1231:
I'll have to do it once I get home, (on my phone and no ddms... or ability to upload pics), but what app is that?
[G1 Android Development] Pfeffernuss:
a) I do not fully understand how LTD translates in Learn To Read.

b) When you look at the time I posted it you *might have guessed* that our responses overlapped each other.

So LOOK before you post such things, sjeesss.
[G1 Android Development] therealmarv:
About 550Mhz on CyanogenMod:

It is strange, the benchmarks say to me that there is no speed improvement in CPU.

BUT: When I'm really stressing my smartphone (doing alot of things) it feels a littlebit snappier. The freezes, non-responsiveness of the phone is shorter (about one or half a second shorter) than before!!

So I can confirm that there is something. But really not much!
[G1 Android Development] eugene373:
Awe, You are Correct.

Sorry about that.

In the Case with the 32B Boards, Mainly what is happening is, Well, Just because the CPU can Proc things Faster, there's a major bottleneck between the CPU & the Memory that don't exits on the Cliq and the 32A. A shame I know, but the tools was a simple Cross Uni between other Phone's as well.

Sadly, even though the 32a & cliq user's are having great success than the 32b, it's still a great tool to have for other phone.

We're just left in the cold regard how much bandwidth 32b can handle..
[G1 Android Development] Pfeffernuss:
No biggie ;) Just find it annyoing that people are noticing things that might not even be there :D But I guess that's human.

I also "think" some things are snappier then before, but I truly believe it's (mainly :cool:) subjective (32B MT3G).
[G1 Android Development] domenukk:
where did you get this information from?
[G1 Android Development] fabsn:
That's absolutely true. BUT:

Benchmarks aren't that significant either.

Synthetic benchmark results do not represent the phone's capabilities in real life tasks.
[G1 Android Development] Pfeffernuss:
True, but when you find zero evidence of *any* form of speedup (CPU, memory, graphics and so on) it's rather odd that somebody would notice anything, don't you think ;)

So for the meantime (using a 32B device) I still think it's more subjective than measurable ;)
[G1 Android Development] eugene373:
http://www.arm.com/products/index.html
[G1 Android Development] eugene373:
http://xdaforums.com/showpost.php?p=5576729&postcount=690
[G1 Android Development] Alucardis666:
After reading through all the pages on here. I've found that this is quite an interesting little find, I will be following the progress of this mod heavily and waiting to see how far we can push it. Thanks for the find OP
[G1 Android Development] nebochenezzar:
This post is exactly what i was thinking concerning the G1 ram clocks....for sure makes the 700+ a little risky if anything...i would run at 628, and look to see how 600 does, it seems like the OP in the link did enough testing for me to believe that higher cpu clock speed CAN and WILL out grow your RAM clock, anyone who has build PC's over the years would know that though....
[G1 Android Development] zachattack052:
10mb ram hack, 550mhz, 780mhz; whats next? 1ghz
[G1 Android Development] frankencat:
This is cool.
[G1 Android Development] Frito37:
I tested it 4 times with 3 different frequencys and only saw a speed boost from 384 to 528

528 to 6xx didnt do anything

and 528 to 800 didnt do anything
[G1 Android Development] lotherius:
What method of testing did you use? Speed increase is small at this level, as my testing showed. At least I made clear what method I used for testing. Any test that depends heavily on memory, graphics or filesystem will show little to no improvement, does not mean improvement is not to be found in certain situations.
[G1 Android Development] Pfeffernuss:
You do know that the hack does not work at all don't you? Already confirmed by the programmer, no less.

And yet you still are noticing differences? Amazing. But very nice for you, nonetheless :D
[G1 Android Development] lotherius:
I guess I didn't post in enough threads for you that I could not again reproduce the results I benchmarked yesterday. Unfortunately, Android appears to be quite unpredictable. I repeated benchmarks 4 times at each speed yesterday, and the results showed improvements. Today I did the exact same thing on the same phone, and no improvement. The difference? Apparently something was slowing down my phone during some of the tests yesterday, despite my having made sure to kill any background tasks.

I already posted this in other threads, now I've posted it here. I couldn't reproduce my results. I hate being wrong, but hey, it happens.
[G1 Android Development] damnoregonian:
that's the nature of benchmarks, and definitely the nature of embedded devices running full scale operating systems where a significant amount of processor time is spent doing simple housekeeping.

the trick is large enough sample size.

anyway, a simple evaluation of the code will show you that it does in fact do nothing, except change a number that is used for a few calculations. (bogomips, likely, and probably setting of the scheduler timer), a number that is never ever used to set the clock registers.

guy's, please stop this. it was a fun ride, but let it die.
[G1 Android Development] DarkOne951:
Just to give you people a heads up who are flaming about bottlenecks and such on your phones.

Have any of you ever overclocked a CPU?

Well, if you haven't let me give you a rundown.

A bottleneck is present when one component of a computer runs faster than the rest, or when one specific part is below par.

Concerning memory bottlenecks:

You can have a set of 4GB DDR2 667 memory with timings of 9-9-9-26 and your processor overclocked from 2.6GHz to 3.5GHz. You will see HUGE benefits. Even though the memory is a substantial bottleneck.

Now, same scenario, different memory. Say you have a set of 2GB DDR3 1333 memory with timings of 6-6-6-20 and your processor is, again, overclocked from 2.6GHz to 3.5GHz. You will see marginal benefits.

A CPU is more dependent on how much RAM it has to work with than how fast that RAM is. A low amount of RAM will cause a huge bottleneck on a device faster than slow RAM will. Hence, why some are saying that 32A boards and phones with a higher amount of RAM are having better experiences.Also, when overclocking components, it is very common practice to loosen up the timings on RAM and to decrease its speed to achieve a higher CPU clock. A faster CPU will almost always outweigh slower RAM, though it is good to balance the two out so a bottleneck does not occur.

Lastly, if and when you get your CPU clocked higher, benchmarks WILL show benefits. Especially in benchmarks like Benchmark Pi - It is all CPU dependent. Those that are saying it is subjective, you are correct. I've tested the "hack" out, and while it does seem to have its benefits, I can say for certain that the overclock is not taking place if the benchmarks are not showing it. Benchmarks are BUILT to show things of the sort.
[G1 Android Development] domenukk:
Maybe it's improving something on MultiTasking?

As most people pointed out it is increasing speed for the live wallpapers and when the phone is stuck and does not respond for a certain time - so there is always more than one thread running, whereas afaik benchmark tools do one thing after another.

It might just be because the CPU is scaling to 528 faster, but eaven if it's just that - its worth being included in roms. It doesn't hurt, most argue its faster (everybody but the ones that actually benchmarked it) and it is just better to live in a dream world where dream has a higher clock speed than the iphone 3gs... (it has a 1ghz prozessor that runs on 600mhz due to battery thingi)

Let us users beleave... include it in roms please :D

BTW: Far better to include something that seems to increase anything rather than a ramhack that decreases performance where needed the most (in games :P)!
[G1 Android Development] BopChie:
can any1 point me in the direction of the 550 kernal with NO ram hack for cm4.2?
[G1 Android Development] domenukk:
580MHZ w/o ramhack would be even sweeter :D
[G1 Android Development] Frito37:
No because it doesnt do anything so why look for it.
[G1 Android Development] domenukk:
580 did work imho.

so look for it.

and if it doesnt - its no harm.
[G1 Android Development] Janis:
Hmph

I tried it. I didn't notice much of a performance improvement over the CFS 10mb RAM hack + 128mb swap set at 20 (I know, it never gets used, but it wears less of a hole, theoretically). At first it was barely noticeable, but it was noticable.

What I got was a few apps force closing, inclucing a couple of acore force closes, and erratic speeds. Sometimes it flew, but other times, not so much. Pretty miserable, actually.

The kernel by itself, after a nand restore, brought my battery from about 10 hours however I usually use it, to 3-4. I seem to remember people complaining about battery on some of the later 4.1 CMs, and early 4.2's. Considering I've got a 1700mAh, that's pretty bad, but after the restore the force closes and erratic stuff stopped.

I'm flashing back to the latest CM. I was/am actually pretty happy with the speeds I'm getting with what I've got. I also clear out my dalvik-cache evry few nights, and that seems to speed things up if I'm getting frutrated.
[G1 Android Development] redmdc:
is it really worth over - over clocking the phone for an extra 23Hz??

i wouldnt risk frying mine for that
[G1 Android Development] 2leaponover1:
Is it worth bricking your phone to be able to customize your rom? Seriously, that was a dumb question.
[G1 Android Development] vegaman:
Why is this thread not dead or locked or something?

It doesn't do anything!

So can people please stop digging this thread up.
[G1 Android Development] linuxluver:
Michael Huang, author of SetCPU, explained why and how this "overclocking" isn't really happening.

Yes, Android does report a higher clock speed - whatever you tell it to report. But the processor ignores all that as it uses values that can't be changed by the hack. The only speed that has actually set above 528MHz (and not by this hack) as 768MHz...and no phone is known to last more than 20 seconds without locking up hard and requiring the battery to be pulled.

So all anyone was doing was clocking the phone to 528MHz...and perhaps keeping it there. It *is* pretty fast at 528MHz! :-)
[G1 Android Development] Janis:
I could use some help.

Since I did this, I haven't been able to get my old battery life back. It seems to be draining full force no matter what's running. It even charges slowly, like 20% per hour.

I've reflashed CM 4.2.14.1, reflashed the CFS 10mb RAM hack, checked my apps to make sure nothing is different there, including uninstalling SetCPU, although I didn't do this until after I flashed back. It doesn't seem to matter if Wifi is on or not, or if Airplane Mode is enabled. And I have yet to wipe and restore, since I haven't used a backup app that really restores all my data properly, and there's just way too much of it, it's a huge hassle for me to wipe, so I'd rather snipe this than bomb it.

Yeah, I kinda thought this was a bit pie in the sky, but you know how it is with hobbies, you just like to try stuff just to try it. Just feel lucky you're not one of my fish in my fishtank.
[G1 Android Development] Ace42:
Just:

1.Turn phone off

2.charge till led is green

3.Goto recovery and wipe battery stats after 2
[G1 Android Development] zachattack052:
ya theres a reason why they say there not responsible. sounds like you need a new battery
[G1 Android Development] Janis:
Not until the damage is undone. And hey, half the point of a forum is to talk, the other half is actually useful stuff.
[G1 Android Development] zachattack052:
ya, it kind of pisses me off that it didnt work, and all it did was piss people off
[G1 Android Development] Janis:
I did that, although I'm not sure the phone was charged all the way to 100%, it was close. I'll try it again at what can't be less that 100% and see what happens.

Thanks so much for the really fast and if-I-would-have-said-enough-helpful response.
[G1 Android Development] Kutttt:
Wow, this thread must have broken the XDA record for longest amount of time a thread stayed alive when it should have been eliminated. Enjoy!
[G1 Android Development] Janis:
Amen. Can that be the end?
[G1 Android Development] KingSkeme:
Been on the mytouch screen for about 5 mins so far.....
[G1 Android Development] KingSkeme:
-_- dont think it works if you just put the img in and then resign
[G1 Android Development] Lyute:
Really hoping that Dwang will make an update with this in... :)
[G1 Android Development] KingSkeme:
If someone shows me how to put this into roms correctly ill put it in every rom possible
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Hey guys/gals how do I check the CPU frequency via ADB?
[G1 Android Development] linuxluver:
Full ROM from Eugene373

I just downloaded "Full4231_550Mhz_Kernel.zip" and I'm flashing it.

(HTC Magic 32B from Vodafone)

Completely wiped phone.

- Got first splash screen

- Got CM boot animation rolling

- Phone came up fine. 3G works.

- Started SetCPU. It shows top speed as 528MHz. Thinking maybe I shouldn't have started SetCPU?

How do I see what the actual clock speed is? (Probably a dumb question, but it's the one I'm asking).
[G1 Android Development] JamieD81:
as said in the OP do this with SetCPU
[G1 Android Development] Z҉A҉L҉G҉O̚̕̚:
Did you make sure to set SetCPU to Motorola?