Database Info

Overclocking your android msm7k device

Hi there,
A little cross-post from a post I made on Hero CDMA thread, as this patch applies to many android devices
Overclocking msm7k has been supported on wince devices' linux port for a long time now. (months for msm720xa, and maybe even more for 720x and 750x, I haven't see the details). So it's the same idea that has been implemented here.
Making it work was more difficult than for wince devices, because the radio software is way too clever on android. Still, we got past this difficulty, and it works.
It's actually even better than what ToAsTcfh actually got, he posted only older results which were bottlenecked at 620MHz, now this patch provide users with a 710MHz frequency.
And it should work for all msm7x0xa devices. (so that makes almost double speed for stock G1 ).
For people who wants even more overclocking, you can change the values:
the writel(0x25, ......) line,
This value is the multiplier from 19.2MHz to cpu frequency, 19.2MHz*0x25=710.4MHz
You can change it to whatever value you want, but the higher limit seems to be around 750MHz.
If you want to play with mem values, edit the line:
Code:
{ 528000, ACPU_PLL_2, 2, 1, 132000, 3, VDD_7, 160000, 0, 5, -1 },
Change the 3 after 132000, it's the divisor of memory compared to cpu frequency, -1 (with default settings, it's 132MHz=528MHz/(3+1)
The patch is attached, and also available at http://htcandroid.xland.cz/oc.diff.txt
Now the credits, thanks to bzo for the idea, and the implementation on wince devices, and thanks ToAsTcfh for the tests (it really needed a lot of time, even if the patch looks damn simple now, stupid radio software!), and for making me remember he exists.
Basically, all devices from HTC from before 2009 should be supported (all versions of G1, G2, G3), LG GW620, samsung galaxy, and many others.
To noobs: To get this patch working, you need to build the linux kernel for your phone. Basically, wait for you rom modder to do it.

Has anybody tried this with the Huawei U8220 aka T-Mobile Pulse?
It's not from HTC and manufactured after 2009, but the kernel source looks "patchable".
Greetings,
BigBear

so this overclock will work on sprints cdma hero?
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

vinny8030 said:
so this overclock will work on sprints cdma hero?
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
It already works on it, it's the base of all tests...

Hi
I am new here. I am using XDANDROID 2.2 AOSP 1.7.10, can you pliz explain a little bit more for a noob on how to over clock with your patch.

hey,
is a patched kernel available?

isRaZZe said:
hey,
is a patched kernel available?
Click to expand...
Click to collapse
Haha ^^ which u want? ^^

urgent help!
i have to admit,i am a noob,and i.need serius help on my gsm touch pro,i installed android 2.1 with htc sense ui,my devise is now screaming because it is very slow,i need HELP!(sorry,i have poor english )

I just wanted to say thanks for this thread. Managed to get the changes into the Huawei U8110 kernel source and managed to overclock my U8100 to 691.2MHz (rebooted on 710.4) and I have the benchmarks to prove it. Thanks again.

lorenzork said:
Hi
I am new here. I am using XDANDROID 2.2 AOSP 1.7.10, can you pliz explain a little bit more for a noob on how to over clock with your patch.
Click to expand...
Click to collapse
seems you need to compile the kernel

likounin said:
seems you need to compile the kernel
Click to expand...
Click to collapse
Yes, you need to compile the kernel.

somebody who tast it with touch diamond
did somebody overclock his touch diamond GSM im lil bit scared to make go of it :S
danks for help

i am running my touch diamond (diam100) on 633MHz very stable. I get SOD approximately every second day, but i don't know what causes this. So now i am testing at stock CPU ratio to see if SOD still appear.
Interesting thing is, that i got much more SOD wit lower frequenzies, such as 614Mhz and 594MHz. So 633MHz is very stable and the rare SOD would be ok for me.
Thanks to the great developers!
I am currently using FRX05

so do I just put this "oc.diff.txt" on the root of my sdhc or what is process of implementation? Thanks

Is there a ROM out there for the Diamond that I can use?
I'm using andboot and the only thing I'm good at is changing the "system.ext2" file...
Building a linux kernel is a bit out of my league.

Thanks for sharing , it's very helpful.

[1.267GHz!!!] [Devs] Overclocking/undervolting patches (update 6/15)

I got an EVO myself and managed to overclock it to 1.267GHz. We could probably go even higher, but that requires more extensive changes. Here are the changed source files: http://dl.dropbox.com/u/36553/supersonic_oc-uv.tar.gz
It also includes an undervolt courtesy of pershoot (a whole 0.1V lower when idle, which should help battery drain a lot!). Here is a test update.zip: http://dl.dropbox.com/u/36553/supersonic_oc-uv_signed.zip (working WiFi). Make sure to do a nandroid backup first!
Sensors/camera do not currently work in this kernel because the source is not yet complete.
There is an overvolt on the highest frequencies. It should not cause any issues. Thanks to toastcfh for his source, Herver for creating the first booting overclocked kernel on the EVO, all the kernel devs in the N1 community, especially pershoot and kmobs, richardtrip from the Desire community, koush for anykernel updater, and all who helped to root the EVO. Enjoy!
Update 6/15: Fixed 950mV undervolt. Raised voltages from 1228800 above to improve stability. Source files updated and update.zip uploaded.
old said:
I posted these in an earlier thread, but I think I should bring this to everyone's attention. Here are some simple patches that will overclock the Evo up to 1.267GHz (though by any means it's not guaranteed to get that high!):
Edit: please don't flash the below update.zip, as it doesn't seem to boot. Devs, the patches are still below, and a zimage is in the anykernel update zip.
Update: I compiled it myself. Here is an update.zip: http://dl.dropbox.com/u/36553/update-oc_signed.zip. This uses toastcfh's sources, Koush's excellent anykernel updater and a config.gz pulled from a stock Supersonic. If this doesn't boot, no damage will be done to your phone. Just reboot into recovery and reinstall your ROM. You can test overclocking by grabbing SetCPU from my sig or changing the cpufreq values if you know how. Once we get this working, I will create an undervolted version for battery savings. I'd get an Evo, but it's sold out everywhere T_T
http://dl.dropbox.com/u/36553/supersonic_oc.zip
cpufreq.c and acpuclock-scorpion.c are in arch/arm/mach-msm, and supersonic_defconfig is just the config. I don't have an Evo, so I can't test these out, but these should work with the source files toastcfh posted earlier: http://forum.xda-developers.com/showthread.php?t=686240.
Undervolting can be achieved simply by adjusting the voltages (in mV) in the acpu_freq_tbl table in acpuclock-scorpoion.c. For those not familiar with his work, you can see pershoot's safe (but lower) voltages for the N1 here: http://github.com/pershoot/nexus-kernel/blob/master/acpuclock-scorpion.c. If you want to overvolt or go under 1000mV, you have to make one further adjustment to the voltage regulator in board-supersonic.c.
Note that the N1 and the Evo are completely different devices (with similar processors), so what may work for the N1 may not work for the Evo.
Click to expand...
Click to collapse

Awesome... until I am sure this is stable, I will wait, but I must have overclock

jigglywiggly said:
Awesome... until I am sure this is stable, I will wait, but I must have overclock
Click to expand...
Click to collapse
I don't recommend overclocking, the devices already can run warm at current settings.
But then again, you are entitled to do as you wish.
Options better than overclocking are to remove the Sprint bloatware and strip down parts of Sense, this speeds things up alot by removing excess background applications.

Well it ain't too bad, my Droid at 1 ghz(550 stock) runs great.
So this should be good too.

I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...

phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.

Well, I agree with the benchmarking comments but on the subject of Froyo... Froyo is designed to be even faster on equivalent hardware than 2.1... and 2.1 on my Evo is smooth as silk. And the Evo handles most Flash I can throw at it, so I'm not sure. I have however noticed a small performance difference with live wallpaper running, so maybe OCing will clear that up a bit.

Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
You know, this is an excellent point and I feel like I failed the developer community in some small way when you had to bring it up. You shouldn't have to provide a reason for wanting progress, it should happen for its own sake.
Proceed.

Jus10o said:
Some people love to run benchmarks. Try to improve on them over and over. Others like the feeling of just going faster. Also some apps or some in the future might require a faster running phone. What better way to achieve that (other then buying a new phone) then OC.
Also in the future, are you not gunna buy a 1.5ghz processor phone running 2.1 because a 1ghz processor can already do it? OC has many benefits, just not to everyone, most because they dont understand the consequences or benefits.
My htc hero clocked to 768mhz can run 2.1 and everything near instant. Still doesnt keep be from wanting a 1ghz or higher.
Also one more thing, 2.2 will be out soon. With full flash support, i have a feeling its going to require a lot of CPU. An OC Evo would probably run many things from 2.2 a lot easier.
Click to expand...
Click to collapse
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far

Roman G said:
Agree with everything you just said, and I am less than excited about the benchmarks with the EVO thus far
Click to expand...
Click to collapse
HAHAHA.. im sorry but i had to laugh at your sig.

Jus10o said:
HAHAHA.. im sorry but i had to laugh at your sig.
Click to expand...
Click to collapse
Ya I sold my hero a couple weeks before the EVO dropped, and had to use my wife's old phone.

phinnaeus said:
I like overclocking as much as the next geek, but on the Evo... WHY?
This phone has yet to respond anything slower than instantly to my input and I expect a difference of .26 ghz would not make it so it could read my thoughts.
Undervolting, on the other hand, could help with the abysmal battery life...
Click to expand...
Click to collapse
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL

thebluecoat said:
I'm not trying to start an argument at all but you have to think broader mathematically. If the processor runs at 1000Mhz or 999mhz (In the case of my N1) a .267 increase is 267mhz, a 26.7% increase in computational performance... That's pretty raw especially in cellphone terms, that have no way to vent or displace that kind of heat.
Has anyone noticed how much hotter the kickstand gets? I bet you that it's attached to something the cpu is connected to. $5 bucks says we will see KICKSTAND HEATSINK + FAN MOD 2GHZ OC! LOL
Click to expand...
Click to collapse
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.

coolbho3000 said:
This is a patch for developers, not a discussion thread for the merits (or lack thereof) of overclocking.
If you don't want to overclock your phone, nobody is making you.
It has worked out fine in the Desire and Nexus One community.
Click to expand...
Click to collapse
how do i apply this ???????
can u make it flashable?

mccurt29 said:
how do i apply this ???????
can u make it flashable?
Click to expand...
Click to collapse
need to follow the directions in the first post. the .c files need to be loaded into the kernel source (right now just have toast's soruce) and the kernel has to be compiled with them.
if somebody wants to compile up a kernel with these, we could start testing. if i get some free time i'll help out here and compile a kernel but somebody else will prob beat me to it!

please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.

madunix said:
please someone let us know how this works out for your evo 4g... benchmark, test results... anything to show better/worse performance, whether your got ALOT warmer, or just a lil, etc.. ne information would be greatly appreciated it, i'm not a 100% noob, i just know how to follow instructions very well, doesn't mean i understand everything that's going on, just the basic concept of what i want. thank you in advance.
Click to expand...
Click to collapse
I'm waiting for someone to compile this first.
If nobody steps forward, I'll make my own attempt, but I'll be working blind with no test hardware.

I'm pretty sure most devs are waiting on the htc source kernal before playing with this. I can't wait but I understand them being hesitant to do too much with this for now. Still awesome of you to post it and have it rdy for when that time comes!

sounds good.

madunix said:
sounds good.
Click to expand...
Click to collapse
Your signature says you have a radio of 1.32.651.6, just to let you know that is not a radio, that is an HTC software OTA update. My radio is 1.39.00.05.31 for example

[DEV] Overclocking the GPU !!

Take a look at this link
The GPU has been overclocked to 200 MHZ result from stock 25 fps to 36.5...
The desire(+-27FPS neocore) has the AMD Z430 GPU wich is also on the acer Liquid running at much higher 34,6 FPS @ the same resolution 800x480 but UC cpu768 MHZ although it still preforms much higher on neocore !
I'm sure that some of you developers with the knowledge are prepared figuring this out to get the desire GPU preforming better !..
(tnx to beidl) for those who're trying to find the changes: http://git.linuxtogo.org/?p=groups/m...8a6a0dfe5ba912

The Snapdragon Processor holds the CPU and GPU in one chip... i dont know if youre able to do that...
EDIT: maybe changing some clocking and voltage values in kernel???

More performance can somehow be squeezed out of it tho. Its just not good enough with the power it holds
-------------------------------------
Sent via the XDA Tapatalk App

I Agree there is more..

and it will drain the battery some more...

pina_ said:
and it will drain the battery some more...
Click to expand...
Click to collapse
I don't think people that wants to get the best benchmarks.... care? lol goto maximum overclocking.... possilbey higher than 1.27GHz..... after you benchmarked and got your name in the list.... go back to UVOC lol

atomfix said:
I don't think people that wants to get the best benchmarks.... care? lol goto maximum overclocking.... possilbey higher than 1.27GHz..... after you benchmarked and got your name in the list.... go back to UVOC lol
Click to expand...
Click to collapse
Yeah thats why im no 1
Come get me mate lollol
JD

JupiterDroid said:
Yeah thats why im no 1
Come get me mate lollol
JD
Click to expand...
Click to collapse
lol, well if Richard would like to make a temporary kernel that would restore the volt and try 1.4GHz maybe more. HTC Desire could be getting the No.1 spots in benchmarking

for those who're trying to find the changes: http://git.linuxtogo.org/?p=groups/...;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
looks like only some parameters and 2 functions (pc_clk_enable and pc_clk_disable) were changed.
I don't have much experience with kernel developing, I'm just a stupid java dev. lol
But I'd like to see this added to the 2.6.32.9 kernels, and since we would be able to
change the clock frequency somewhere in /sys/module/clock/, something like a "SetGPU" would be a nice project to do.

beidl said:
for those who're trying to find the changes: http://git.linuxtogo.org/?p=groups/...;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
looks like only some parameters and 2 functions (pc_clk_enable and pc_clk_disable) were changed.
I don't have much experience with kernel developing, I'm just a stupid java dev. lol
But I'd like to see this added to the 2.6.32.9 kernels, and since we would be able to change the clock frequency in /sys/module/clock_7x00/parameters/gpu, something like a "SetGPU" would be a nice project to do.
Click to expand...
Click to collapse
That would be sweet

Sounds good to me Im up for throwing my Desire in the firing line
JD

JupiterDroid said:
Sounds good to me Im up for throwing my Desire in the firing line
JD
Click to expand...
Click to collapse
same haha

i'd totally do it too....

*Hopes that richardtrip will take a look at this thread* lol

i wont be happy till were above the n1 in linpack
and ...
till we have 1800 in quadrant (n1 best so far is 1750)

Stay on topic please!!

i wont be happy till were above the n1 in linpack
and ...
till we have 1800 in quadrant (n1 best so far is 1750)
Click to expand...
Click to collapse
True... we need to get ahead of N1 lol I'm ashamed of the performance it already shows lol
-------------------------------------
Sent via the XDA Tapatalk App

How many batteries do you wanna carry?

eezray said:
How many batteries do you wanna carry?
Click to expand...
Click to collapse
Solar Charger

Fstluxe,
First of all Thank you!! this is the Time and way to Inspire the devs that have the knowledge ,letting them bring this amazing Patch to the desire and maybe all the android Phones ! Great thank you for awaking the community..
So developers Please Come on Just try this out please!! i will putt my money on THIS project!!!!!

[KERNEL][GPL][ACS]Xtreme Kernel v1.2.0-Lucy-1.3GHz OC,Battery,Tweaked Voodoo(options)

ANDROID CREATIVE SYNDICATE​presents​XTREME KERNEL V1.2.0​
First of all, I want to put my thank yous up here at the top, so, here they are:
-geniusdog254 - My primary teammate, been helping me every step of way.
-nullghost - One really cool dude. Always on when I ask for help. Git would still be a scary thing if not for him.
-rjmjr69 - Funny, funny dude. Keeps me motivated to keep going
-The Voodoo Team - Your work is awesome!
-My beta testers - You were/are all great. Thanks for helping me with this!
-All the devs across the board - Seriously, you're all a bunch of absolutely awesome people.
-Anyone I forgot - You're all great!
Now, here we go:
THE STANDARD DISCLAIMER
I, DevinXtreme, AM NOT responsible for what happens to your phone, your cat, your house, or anything relating to you! If your phone bricks, OH WELL. Have a nice day.
This kernel has a MixUp kernel base. DI18, blah blah. I deviated once Interactive got working. I also removed the Voodoo color modification. So, there's that.
It is built and designed for Syndicate ROM, which will be out later tonight. Sickest ROM you've ever seen. The version released with the ROM is slightly different, but only for fun's sake
Changelog:
v1.2.0
-Removed the 1.6GHz step. The time machine is gone. Plus, was causing more problems than it was helping.
-Added 1.3GHz step courtesy Herver
-Switched from MPLL to APLL. Smoothness and speed increase. Thanks to nullghost for help on this.
-Added Voodoo color mod, tweaked version, courtesy Herver. I will be maintaining a no-voodoo version. I just haven't yet.
-Tweaked the light sensor, adding a new step and made it not jump to the brightest setting as much. Should save battery and transition smoother. Also pols a little more often.
-Tweaked scaling rules for 1.3GHz. Should scale there less, thus saving battery.
ADDITION: The file ending in 'nv.zip' is a no-voodoo version. The file ending in 'ov.zip' is the version for the original voodoo mod, not the tweaked one.
v1.0.1
-Fixed scaling. Linpack scores and tests work fine now.
-Disabled Carrier IQ in init.rc. Carrier IQ is essentially Sprint spyware. Kernel devs: This is really easy to do. Just comment out the iqmsd lines at the end.
v1.0
-Overclock to 1.6GHz!! Requires SetCPU which is, for some reason, defaulting to performance. Make sure you change it to conservative.
-Default governor without SetCPU is conservative with 200MHz-1GHz steps.
-Removed Voodoo
-Framerate unlocked (78-80fps)
-Built for ROMs with a custom boot. Makes stock boot look like garbage. We're working (still) to fix this.
-Undervolted
KNOWN BUGS:
-In spare parts, if you set the WiFi policy to never sleep, it still sleeps with the screen off. -skandranon314
-Some weird vibration thing going on when 1.6GHz is hit.
NOTES:
Linpack is being strange with this. I'm getting between 9.2 and 9.8 with some REALLY strange numbers. I'll have this fixed this weekend.
SetCPU sets the default governor to performance. If you use it, be sure to change it immediately for battery life.
FOR 1.2
-I recommend 200MHz-1200MHz. Some phones can't reach 1.3GHz safely.
-200MHz - 800/1000MHz is a great setting for battery and you should still have a very smooth experience.
For those who care, I get 1135+ in quadrant.
You can read my source here.
Thanks, guys. I hope you enjoy!

How stable is this??

When is the rom out?
Sent from my SPH-D700 using XDA App

Looking forward to trying this out!

1.6 GHz???????
That's awesome, though I don't think I'll crank it that high.
Is there any advantage to this vs MixUp running at 1.0 Ghz?

spitefulrain said:
How stable is this??
Click to expand...
Click to collapse
I've hit no bumps, neither have my testers.
joshottley said:
When is the rom out?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Give it a couple of hours.
SORRY, HAD TO TAKE IT DOWN FOR JUST A LITTLE BIT. EXPECT AT ~12:45AM MST.

Why take it down? I already downloaded and flashed, was that a bad idea??

I'm running it. Smooth so far.
Sent from my SPH-D700 using XDA App

Dusting the epic off now.

[email protected] said:
Dusting the epic off now.
Click to expand...
Click to collapse
Should have never abandoned dude lol.
Sent from my SPH-D700 using XDA App

Very smooth so far. got 1194 on quad, and 9.2 average on linpack. Wonder how the battery life will fare.

spitefulrain said:
Why take it down? I already downloaded and flashed, was that a bad idea??
Click to expand...
Click to collapse
Nope, just a tweak. Your phone is fine! XD
And I'll be in a movie, so I won't be able to get it up until then. Sorry guys!

DevinXtreme said:
Nope, just a tweak. Your phone is fine! XD
And I'll be in a movie, so I won't be able to get it up until then. Sorry guys!
Click to expand...
Click to collapse
Ok, good. I was worried for a sec
So would you recommend flashing the new one when it's up since you're tweaking it?

Hmm.. something's not right here. I just got 22 fps in Neocore with the removed kernel. What could I be doing wrong?
Edit: Switching from performance to conservative upped my results to 62 fps which is quite respectable.

spitefulrain said:
Ok, good. I was worried for a sec
So would you recommend flashing the new one when it's up since you're tweaking it?
Click to expand...
Click to collapse
Yeah, it'll be a good idea.

what kind of voltage are you giving it to get 1.6 stable? based on what im reading, anything above 1.3/1.4 is pretty much unachievable on these devices and is not really the speed that the device is running thus the unscaled rise in benchmark scores. iv been following hero_over and he couldnt get a stable 1.4 OC although he did get 1.3ghz on stock volts stable..which keeps me wondering if we really can hit 1.6 stable

illogic6 said:
Hmm.. something's not right here. I just got 22 fps in Neocore with the removed kernel. What could I be doing wrong?
Edit: Switching from performance to conservative upped my results to 62 fps which is quite respectable.
Click to expand...
Click to collapse
lol I was gonna say. I'm going good with Neocore as well.
d94 said:
what kind of voltage are you giving it to get 1.6 stable? based on what im reading, anything above 1.3/1.4 is pretty much unachievable on these devices and is not really the speed that the device is running thus the unscaled rise in benchmark scores. iv been following hero_over and he couldnt get a stable 1.4 OC although he did get 1.3ghz on stock volts stable..which keeps me wondering if we really can hit 1.6 stable
Click to expand...
Click to collapse
All of it is on my git. I release my source, as devs should with GPL. The problem is that the fsb isn't scaled properly, affecting the floating point processor, causing low Linpack scores. I'll have it worked out this weekend,

Bummer.... I missed the link the first go around..... Will be waiting
Sent from my SPH-D700 using XDA App

If this was a hero_over post, he'd be in trouble for a teaser post lol... just trolling lol. Had to have a smart ass comment

Quick. And stable so far
Sent from my SPH-D700 using XDA App

[REQUEST] Kernel W/CPU & GPU OC

I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36

while im no genius when it comes to this stuff, somehow i would suspect that people here are already looking into this.
i could be wrong tho lol

pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated

jlevy73 said:
The person to ask this to is Morfic. He's all about tweaking bus speeds to improve not only cpu but gpu performance as well. But much of what you've already requested has been incorporated
Click to expand...
Click to collapse
But where is he...??
G2X

CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.

gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it

crisis187 said:
gpu overclocking would be sweet... now my question would be has anyone tried to load Optimas 2x kernel/software on the g2x since they are pretty much the same hardware(in theory you would think it would work)... i might even try to load this kernel onto my phone when i get home from work so if i mess anything up ill have my gear to fix it
Click to expand...
Click to collapse
Please don't try to load O2x software on your G2x.

pyckvi said:
I was browsing the Optimas 2x forum today and ran into an awesome kernel with GPU overclock. which sounds pretty cool to me. also the dev mentioned something about overclocking "system bus" which improvers memory/2D/3D/etc. i think someone in this forum should take a look into this KERNEL and try letting us taste some of this goodness.
Here are the links:
http://forum.xda-developers.com/showthread.php?t=1119771
http://forum.xda-developers.com/showpost.php?p=14654927&postcount=36
Click to expand...
Click to collapse
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....

GideonX said:
Please don't try to load O2x software on your G2x.
Click to expand...
Click to collapse
have you tried it yet though is my question

im not worried if i flash a kernel and it doesnt work i can reflash my old kernel if it doesnt work and gets stuck into a bootloop

crisis187 said:
have you tried it yet though is my question
Click to expand...
Click to collapse
Someone in another thread tried this and it messed up their baseband. A restore doesn't fix it apparently.

Big rush dog, the tiamat kernel guru and Guy getting engadet headlines for oc the xoom to 1.7 ghz has gpu oc in his kernels. I will be honest though, I can't tell the difference except maybe video streaming works a little smoother. I personally don't think it is worth the devs time...
Sent from my LG-P999 using XDA App

Howdy! I'm the developer of that kernel
To be honest the GPU overclocks aren't all that beneficial. There is a little bit of a speed bump (I managed to get the highest score on nenamark2 for example). But the difference is was 27fps vs 32fps. If someone is interested in incorporating that into the g2x I'll be happy to show them the changes I've made. I haven't released the source because I'm lazy but there isn't too much to it.
Actually, if you look at the voltKernel sources for the O2X you'll see the same changes there.

chuckhriczko said:
CPU overclock is something that makes sense for us right now but what would a GPU overclock get us? To me thats just something that will lower the life of our phone with no real reward until games come out that our phone can't run. Right now our phone can run pretty much all games at full speed.
Click to expand...
Click to collapse
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.

Great!
@ fallout0 thank you i hope that you can help out one of our devs on this.
morfic said:
Yes, superficial benchmarks like quadrant can be pushed to 5400 only with max cpu oc.
However, did you notice how 1.2 thru 1.5 gets you the same fps with no added benefit than more heat created?
Pushing other things other than cpu should let us remove bottlenecks and not tighten them up.
If you want your G2x to life 20yrs, 1.5ghz is not the way to go.
I have no kernel ready for release, to notice changes, I stuck to 1.5ghz, but the final result will be more likely 1.2 or 1.3ghz.
Maybe with a "don't hold my hand, give me freedom or give me death" DBU version at 1.5Ghz later.
I'm not shy to increase vcore on a SoC. But unlike the Nexus S, this thing gets HOT, fast.
Avetny pointed out that thread, I'll see if fallout hit something I have missed so far.
The clocks get compared to chip defaults in many places, choosing the smaller of the two, so it's just tedious replacing them with sane defaults, unless I stick to my current approach of offsets instead of absolutes.
We'll see.
That's also the reason I don't update my kernel often. Right now commits in cm git are only preparatory, config changes that made things smoother I already used.
I'll release something if they finish their version of BLN.
Or if I'm happy with gpu/bus/ram oc/tweaks.
not going to make people flash a kernel for no reason. As jlevy can attest, kernel not following cm git, not even based on it can work very well.
Not having latest cm commit on kernels that take another approach is not always useful.
Especially if we track regressions that cm devs back out later, that's all this gains.
So yes, there will be a gpu oc, when it's ready.
Click to expand...
Click to collapse
thanks morfic i hope everything goes smooth with your kernel, i would love to test it out once u feel it is ready. and thanks for not rushing it.

faux123 said:
I remember reading a while ago that GPU/System bus overclocking was attempted by some kernel dev, then later on, the dev realized through extensive testing that GPU and system bus clocks were locked, the changes to the kernel source had no effect (hardwired). Now this was a few months ago when I was reading up on Tegra kernel development before I got my G2x. Now all these could have been obsolete, and maybe now someone has found a way to do the above via kernel source updates.
Another issue that most people don't mention here and many people have been guilty of, is the GPL issue. The guy who supposedly did this overclocking has not published his kernel source code anywhere (GPL/XDA rules issues), so no one can examine what he did and prove that it worked....
Click to expand...
Click to collapse
You should talk to Fallout0 he seems like he got past the system bus/GPU locked issue. both of you can maybe learn something new from each other. & it would be awesome if the both of you can work on a kernel together.

Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.

Would overclocking the gpu help run nds4droid any better? What else would ocing the gpu do? Everything seems to be very fast as it is lol
Sent from my LG-P999 using XDA Premium App

dkb218 said:
Wouldn't a higher clocked G2x cause more heat? Heat being the reason this things reboots so often? Maybe a slower G2x is the way to go.
Click to expand...
Click to collapse
Pushing cpu more I don't see useful other than keep up with your buddy's Nexus S' quadrant scores and make sure your hands stay warm in a cold Chicago winter.
I build kernels usually when things stutter or otherwise annoy me. The pushing the OC usually comes by request of those who just want more more more.
I do like to remove bottle necks.
The hardwired clocks. Well the.cpu ones are hardwired too.
The gpu/bus oc works, until boost and throttling kick in, where again values are compared to hardwired values. using offsets after the comparison would be the way around without killing boosting and throttling.
Guess main thing that stopped me is the heat at 1.5ghz, and the frowns over 1.2ghz and 1.3ghz kernels, without further "what else is in there"
Still hoping fallout can share what he/she has, it'll help making this a reality, sooner.
It's tedious. Most of all.