Related
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
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.
Yes, I FINALLY did it!!! I overclocked my G2X. I would appreciate if anyone could share their experiences with o.c. pros and cons... Should I retreat or stay where I am? Please some feed back!
Over 1300 seems to cause trouble on mine.
i dont think oc'ing is really that necessary with a phone this fast but if u must i wouldn't go above 1.3 (just seems unstable above that). I think the "Pros" come from being able to underclock. Setting up profiles for uc'ing when screen is off or as battery level drops etc really prolongs the life of the battery (at least in my case)
On my OG droid that came limited at 550 mhz, ya, oc'ing was def necessary but I cant really think of any "Pros" for oc'ing this phone.
each phone is different though so play around and you'll find a combination that works great for your phone, good luck
Well... you can get some serious bench scores... This thing rocks the Mandelbrot multithread test in smartbench 2011 at 1.5 ghz. Other than that it helps with games.
Sent from my LG-P999 using XDA App
wu_wei_lion said:
Well... you can get some serious bench scores... This thing rocks the Mandelbrot multithread test in smartbench 2011 at 1.5 ghz. Other than that it helps with games.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
What about the CPU not having enough cooling and frying the CPU over time. I presume its just like Desktop overclocking but without all the extra cooling you can add to make it safe for the hardware.
tombaker1 said:
What about the CPU not having enough cooling and frying the CPU over time. I presume its just like Desktop overclocking but without all the extra cooling you can add to make it safe for the hardware.
Click to expand...
Click to collapse
But what i really want to know is if oc could damage the phone. After all if there is that danger it's noy worth it...
In all honesty I used to be really into benchmark scores and OCing the heck out of my phone and under volting it in the process but that led to many battery pulls ect. What I've noticed is just keep it at stock and mild uving seems to be the best for me its stable decently fast just 2 cents though
Overclocking a cpu is the same as on a pc, only a bit more dangerous on a phone. (This phone already has overheating problems running at stock speeds ) On a computer, people pay a premium for parts that are easily overclocked, and have either very good fans/heatsinks or a liquid cooling rig.
Overclocking is dangerous, especially because not all chips are going to be made equal, even if they come off the same production line. These chips are designed to run at a certain voltage, and certain clock speed. As far as real world use, (NOT benchmarks. Sure, they look pretty and all, but benchmarks are never very accurate.)
Sure, you might get 2-3 more fps on your games, but is that worth the risk of shortening the life of your chip/phone?
(And just so you know, I've been building/overclocking pc's for years, but I also understand what you need to do to keep it stable, and it's *all about cooling*.)
If you're not convinced, try this. Don't overclock your phone, and use it for a few days. Tell me honestly that you really notice a real-usable difference with the chip overclocked or not. (Games set aside, but like I said, getting a couple extra fps on a game to me isn't worth the risk without a proper cooling setup)
For those of you that really don't understand what you're doing to your chips when you overclock, I'd suggest doing some reading about it. A good place to start would be here: http://en.wikipedia.org/wiki/Overclocking
So you think using fauxs kernel is not safe or reduces the life of the chip? I just flashed it and didnt oc or uv further then fauxs default settings...
Sent from my LG-P999 using XDA App
I'm not saying it's for sure, I'm saying there's a chance.
Plus keep in mind that these kernels have other really nice additions besides overclocking and undervolting. I'm using faux's stock voltage kernel ext4, and leaving it at stock settings, and it really works great.
I just posted this up because I see a lot of people more interested in quadrant scores (which to me are pretty useless) than stability of their phones. If you do overclock, and it works for you, more power to you. I just want to inform people. I'd HIGHLY suggest if you aren't sure, read that wiki article, it's a great place to start. (not all information is there, but it gives a very good general idea on how and what overclocking is.)
Thanks! i always like reading knowledgeable and informative posts!
Sent from my LG-P999 using XDA App
mstrk242 said:
I'm not saying it's for sure, I'm saying there's a chance.
Plus keep in mind that these kernels have other really nice additions besides overclocking and undervolting. I'm using faux's stock voltage kernel ext4, and leaving it at stock settings, and it really works great.
I just posted this up because I see a lot of people more interested in quadrant scores (which to me are pretty useless) than stability of their phones. If you do overclock, and it works for you, more power to you. I just want to inform people. I'd HIGHLY suggest if you aren't sure, read that wiki article, it's a great place to start. (not all information is there, but it gives a very good general idea on how and what overclocking is.)
Click to expand...
Click to collapse
OK, you definitely convinced me.... I have also faux (let me tell you exactly - Kernel Version 2.6.32.9 FR Faux 123-v0.03) on EagleBlood 1.05. Could you please tell me what I need to do set up in order to be safe? Thanks!
I'd just go to faux's thread in the development section (his froyo thread, not the cm7 one, since you're using eagleblood), and download his stock voltage kernel. (It's in the first post.) He's on .04 now, by the way.
Then reboot into recovery, and flash the file you downloaded. It'll overwrite your current kernel and modules with the new one, then reboot.
mstrk242 said:
I'd just go to faux's thread in the development section (his froyo thread, not the cm7 one, since you're using eagleblood), and download his stock voltage kernel. (It's in the first post.) He's on .04 now, by the way.
Then reboot into recovery, and flash the file you downloaded. It'll overwrite your current kernel and modules with the new one, then reboot.
Click to expand...
Click to collapse
I could not find this thread under G2X Android Development Section... I found threads Kernel Trinity, Kernel CM7, Kernel LGE Stock Froyo, Kernel Morphine... Which one is it...? Please do have some patience, at least I learn fast!
krekabl said:
I could not find this thread under G2X Android Development Section... I found threads Kernel Trinity, Kernel CM7, Kernel LGE Stock Froyo, Kernel Morphine... Which one is it...? Please do have some patience, at least I learn fast!
Click to expand...
Click to collapse
You passed right by it. LGE stock froyo. (That doesn't mean it's a stock froyo rom, it means it's *based* on one )
http://forum.xda-developers.com/showthread.php?t=1102720
Choose the stock voltage one. (ext3 or 4, depending on your preference.)
mstrk242 said:
You passed right by it. LGE stock froyo. (That doesn't mean it's a stock froyo rom, it means it's *based* on one )
http://forum.xda-developers.com/showthread.php?t=1102720
Choose the stock voltage one. (ext3 or 4, depending on your preference.)
Click to expand...
Click to collapse
Thanks you've been very helpful. That's why I made this post I hope this can help other people as well as it's helped me! )
krekabl said:
I could not find this thread under G2X Android Development Section... I found threads Kernel Trinity, Kernel CM7, Kernel LGE Stock Froyo, Kernel Morphine... Which one is it...? Please do have some patience, at least I learn fast!
Click to expand...
Click to collapse
And a lot of times the kernel will be credited to the developer. So if you see "faux's kernel" people are referring to kernels by faux123. Trinity kernels were developed by morfic. If you are having a hard time finding a specific one, look at the top left to see who started the thread and sometimes that will help find it. Does that make sense? I had to pull an overnight at work so I am a little loopy....
Sent from my butt using XDA Premium App
Hello,
I am running stock ROM with S-oFF and rooted. Ive got setCPU running via the methods used for temp root. (Basically pulled the code from the BAT files everyone used to overclock and temp root). It works alright, but after a reboot, I have to redo it.
I see people are running ROMs that include setCPU. How does a custom ROM manage to keep setCPU "set" after a reboot? Can the methods be used for the stock ROMers?
Also, I see that setCPU requests SU hundreds of times a day when I look at the SuperUser logs. Why is this? Is it bad?
Thanks,
Matt
They are using custom kernels and oc daemon.
Behold_this said:
They are using custom kernels and oc daemon.
Click to expand...
Click to collapse
thank you for the reply! Is this something that a stock rom could implement in its own? Or, should I consider flashing a custom rom?
Thanks,
Matt
Its a little hit and miss right now unfortunately. The kernels can still be buggy on some devices, though they, in theory, should work on a stock device. If you have issues you can always just flash the stock kernel back. Some love it and have no issues, others not so much. In fact some devs have stopped bundling their kernels with their roms and leave them as optional add ons because of issues.
Is cm7 expected do implement overclocking? If so, I may just wait for them to finish.
Matt
Not sure...they are playing cm7 for the sensation very close to the chest, lol, but I don't think so. Just a guess though.
Behold_this said:
Not sure...they are playing cm7 for the sensation very close to the chest, lol, but I don't think so. Just a guess though.
Click to expand...
Click to collapse
Ahh...I guess that only time will tell what sort of advancements come in the way of overclocking (reliably and efficiently).
My theory is that setCPU is the cause for my headaches and may be the cause of most others using it as well. (Crappy battery despite conservative governors as well as phone freezes and data connectivity issues). Seeing setCPU request SU a few thousand times a day seems suspicious. I have it frozen for now, well see how things go.
Matt
I don't know for sure either, but I suspect you might be right, at least to an extent.
hi...I have bigxie apex ics rom on my nexus s and when i flash matr1x kernel 19.5cfs it starts to freeze. Works just fine with the stock kernel. Also when i was using the cm9 it worked fine with the stock but when i flashed matr1x kernel it started to freeze and reboot. Please help!
His kernel is undervolted by default. The phone might not be able to handle the voltages. I have no idea how to fix it though since you can't even get past the full boot. Better off going with something else.
had the same issue, just use another kernel or raise voltages. i've got no idea why everyone recommends matr1x, UV by default just doesn't make sense since every cpu behaves differently. it's like selling "one size fits all" t-shirts. i recommend simple kernel or trinity, they are the most stable ones on my phone apart from stock obviously.
Aktifit said:
had the same issue, just use another kernel or raise voltages. i've got no idea why everyone recommends matr1x, UV by default just doesn't make sense since every cpu behaves differently. it's like selling "one size fits all" t-shirts. i recommend simple kernel or trinity, they are the most stable ones on my phone apart from stock obviously.
Click to expand...
Click to collapse
The most known product doesn't mean it's the more fitting for everyone. It just means it's popular. *shrugs*
I'd be willing to bet that a lot of the people using it don't even know it's undervolted, sadly.
thankyou for the replies...i will try the trinity kernel
You all argue about matrix yeah its undervolted so?? You need to raise your voltage to to make it stable because not all phones can handle undervolted values. It's been address millions times and you all still argue.? Goddamit!! (Bunch of noobs) try to solve the problem first before suggesting another kernel. It so irritating you all. I'm sure matrix dev despise you all because of your.ignorance.
Sent from my Nexus S®
chronophase1 said:
I'd be willing to bet that a lot of the people using it don't even know it's undervolted, sadly.
Click to expand...
Click to collapse
I am guessing most people do know that it is undervolted. If they don't, I wouldn't understand why. He plainly states that if you have freezing issues to raise your voltages right in the FAQ. I have been running the Matr1x since gb and have never had issues with the undervoting. Perhaps your phone can't take it.
If people aren't smart enough to read what the developer has to say, why would he set it to the higher voltages and expect users to move the voltages down themselves. You imply the common user is not smart enough to do it themselves. So what does that leave the developer to do? He can make it like he thinks it should be or make it for the idiots that can't or won't read the op comments.
People need to understand kernels run differently on every phone. So instead of whining they should just move on.
________________
Just Flash It !!!
did u wipe dalvik cache...
Skunk Ape1 said:
I am guessing most people do know that it is undervolted. If they don't, I wouldn't understand why. He plainly states that if you have freezing issues to raise your voltages right in the FAQ. I have been running the Matr1x since gb and have never had issues with the undervoting. Perhaps your phone can't take it.
If people aren't smart enough to read what the developer has to say, why would he set it to the higher voltages and expect users to move the voltages down themselves. You imply the common user is not smart enough to do it themselves. So what does that leave the developer to do? He can make it like he thinks it should be or make it for the idiots that can't or won't read the op comments.
People need to understand kernels run differently on every phone. So instead of whining they should just move on.
________________
Just Flash It !!!
Click to expand...
Click to collapse
Or that the common user is prone to not reading and just going ahead and flashing.
Seriously, coffees have "CAUTION: HOT!" written on them. I pretty much lost faith in "common users" a long time ago.
Skunk Ape1 said:
I am guessing most people do know that it is undervolted. If they don't, I wouldn't understand why. He plainly states that if you have freezing issues to raise your voltages right in the FAQ!
Click to expand...
Click to collapse
Exactly! Read everything first. Educate your self before attempting anything. Just because you can flash doesn't mean you should without understanding anything about what it does or will do to your phone. FAQ is there for you to become familiar with what issues have happened and might happen to you. Yes the Matrix thread is long but I read a lot of it to understand what it was, issues and what others are saying. Just like any ROM, Kernel or mod you plan on trying, read the thread first. :thumbup:
Hope I don't sound like I'm complaining but most threads are started or answered wrong because of this. Good luck :thumbup:
Sent from my Nexus S using xda premium
This is what I was getting at and it somehow got interpreted wrong. It wasn't a dig at mathkid and any of the regular users on here. There are a lot of new users on here and many flash stuff excitedly and don't fully read stuff. I've been there before. Its still a common mistake.
Sent by pocket technology.