Database Info

Can't overclock my Nexus S

Hey all,
I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right
1. Wipe data/cache
2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)
3. Boot
4. Flash kernel
5. Boot
I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late
Any help appreciated anyways, peacee.

Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.

I've tried this already dude, probably should of mentioned it in my steps cheers anyhows

risegeek said:
I've tried this already dude, probably should of mentioned it in my steps cheers anyhows
Click to expand...
Click to collapse
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?

kenvan19 said:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
Click to expand...
Click to collapse
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )

risegeek said:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms
I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock )
Click to expand...
Click to collapse
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon

I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing coming from a constantly slow and crashing iPhone 3G.
I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.
EDIT: Hasn't helped seems to be looping at the Google screen now.

Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.

What the heck? I keep hitting edit but it keeps quoting =( please delete.

sanketrino said:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
Click to expand...
Click to collapse
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe
EDIT: Thank you also for not posting a new thread about this Its nice to see people using the search function!

Blah please delete.

I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.

sanketrino said:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
Click to expand...
Click to collapse
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?

I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App

sanketrino said:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.

Some phones are able to run up to 1.4-1.5 without issues whereas some aren't due to hardware limitations (different batch,build quality etc).
Most however, from what i read in the forums, are able to clock up to 1.3 with either kernels (CFS or BFS, versions types etc) without facing the issue of random rebootings.
Personally, i'm only able to clock up to 1.3. I'll get random reboots if i run smartbench with a 1.4. Quadrant is fine for me at 1.4 though. Was able to get ~3500-3600 scores but in terms of real life situations, i can't tell the difference between a 1.3 to 1.4.

Hey guys,
seems my thread is still alive I flashed the newest version of netarchy the other day, I can manage 1.2-1.3 quite happily atm - I have to manually use SetCPU after each boot though, if I set on boot it will loop
ah well.

SetCPU and overclocking

Since SetCPU was updated today to support the tegra II chip, I thought I would just give you all a heads up. Hope to see some kernels compiled with overclocking slots soon.

coolestmage said:
Since SetCPU was updated today to support the tegra II chip, I thought I would just give you all a heads up. Hope to see some kernels compiled with overclocking slots soon.
Click to expand...
Click to collapse
Cant you overclock by hand without that?

There are a few other apps and methods to overclock. The newest version of setcpu is able to see the slots in clemsyn's kernel, but they don't exceed 1ghz.
Sent from my Droid using XDA App

Looks like the xoom is already OCd to 1.5. Can't wait to see some kernels for us too

Wrong section.
At any rate, I'm sure once coolbho3000 puts his overclock code in github, the kernel devs around here may be able to get these puppies overclocked as well. The difference being that the Xoom as a .36 based kernel as where we are still running .32 based kernels, so there is just as much chance that it doesn't port.
When posting, think of the content and context. This thread is about an app. But this section is for Guides, Kernels, and ROMs to be released. I know this section is where most folks spend most or all of their timing reading/posting, but there are 4 sections for a reason, to keep content organized and relevant. Let's help the mods do that by posting in the appropriate section.

miphonematt said:
Wrong section.
At any rate, I'm sure once coolbho3000 puts his overclock code in github, the kernel devs around here may be able to get these puppies overclocked as well. The difference being that the Xoom as a .36 based kernel as where we are still running .32 based kernels, so there is just as much chance that it doesn't port.
When posting, think of the content and context. This thread is about an app. But this section is for Guides, Kernels, and ROMs to be released. I know this section is where most folks spend most or all of their timing reading/posting, but there are 4 sections for a reason, to keep content organized and relevant. Let's help the mods do that by posting in the appropriate section.
Click to expand...
Click to collapse
Am I missing something? Isn't this in the general section?
Why do there seem to be so many self imposed forum police these days? Seems like half the posts I see are people *****ing at the op

There is a big difference between 36 and 32. Honestly, I only assume this from looking at the latest 38 rc commits and comparing the two. But it seems to be significant, even in its comments and verbosity. What's missing is cpu-tegra.c or the cpufreq driver for tegra written by Colin Cross (android dev) - instead we have NVIDIA's cryptic cpufreq.c .. I can barely understand what's going on with most code.. but it seems like our kernel version is from a time where NVIDIA's code was still being sorted thru by the aforementioned Google dev.

I have setcpu installed however I cant change the governor

collindv said:
Am I missing something? Isn't this in the general section?
Why do there seem to be so many self imposed forum police these days? Seems like half the posts I see are people *****ing at the op
Click to expand...
Click to collapse
Because we are supposed to self police ourselves otherwise the mods just close our forum.

grinch247 said:
I have setcpu installed however I cant change the governor
Click to expand...
Click to collapse
Because your kernel isnt set up to be changed

thebadfrog said:
Because your kernel isnt set up to be changed
Click to expand...
Click to collapse
however I can alter the speed up or down...and check off set on boot..

grinch247 said:
however I can alter the speed up or down...and check off set on boot..
Click to expand...
Click to collapse
Yes and so can I. I can also set the governor with a script or manually. They kernel for the GTab has 2 settings....performance and powersave... and as far as I know setcpu doesnt support the .32 kernel that GTab has. It does support the .36 kernel that the xoom has.

collindv said:
Am I missing something? Isn't this in the general section?
Why do there seem to be so many self imposed forum police these days? Seems like half the posts I see are people *****ing at the op
Click to expand...
Click to collapse
I (one of the two mods) moved this into the General section where it should be. It had been in the Development section which wasn't the right place.
And thebadfrog is correct - we (as a community) benefit when everyone helps everyone out - including making sure posts are created in the right spot, and aren't just another variation on a question that might have been asked 15,245,332 times before.

I apologise for posting in development. I wasn't even paying attention. Thank your for moving the thread for me.

Originally Posted by coolestmage  
Since SetCPU was updated today to support the tegra II chip, I thought I would just give you all a heads up. Hope to see some kernels compiled with overclocking slots soon.
Cant you overclock by hand without that?
__________________
| chuong trinh thiet ke web | Dịch vụ Quản lý website | cty thiet ke web | thiet ke trang website | lÃ*m website giá rẻ

You need a kernel that supports overclocking and the GTab doesnt have one yet

thebadfrog said:
Yes and so can I. I can also set the governor with a script or manually. They kernel for the GTab has 2 settings....performance and powersave... and as far as I know setcpu doesnt support the .32 kernel that GTab has. It does support the .36 kernel that the xoom has.
Click to expand...
Click to collapse
wondering if the xoom setcpu profile would jive w/ our tablets?

The gtbalet's benchmark is around 2,500. The overclocked Xoom got 2850. Standard Xoom @ 1Ghz got 2,150.
Am I missing something???? If the gtablet could be OC'd that would be huge.

grinch247 said:
wondering if the xoom setcpu profile would jive w/ our tablets?
Click to expand...
Click to collapse
Kayak83 said:
The gtbalet's benchmark is around 2,500. The overclocked Xoom got 2850. Standard Xoom @ 1Ghz got 2,150.
Am I missing something???? If the gtablet could be OC'd that would be huge.
Click to expand...
Click to collapse
The profiles won't until the AOSP frequency scaling is imported into the kernel sources - and that's not an easy process. Then the kernel will have to be compiled, etc.
Yes - it'd be nice to be OC'd - but battery life would be affected. It's a tradeoff in many ways....

jerdog said:
The profiles won't until the AOSP frequency scaling is imported into the kernel sources - and that's not an easy process. Then the kernel will have to be compiled, etc.
Yes - it'd be nice to be OC'd - but battery life would be affected. It's a tradeoff in many ways....
Click to expand...
Click to collapse
On my OG Droid I like being able to drop the speed for battery savings when the screen is off if it's not in use. So there's more in it than just big numbers.

[Tiamat kernel 1.4.1) Random reboots on Xoom

Hi all,
I've been having random reboots/freeze-ups ever since I rooted.
This happens regardless of whether I am OC'ed or at 1ghz. These reboots tend to happen when watching Youtube or when browsing.
Would just like to have a feel of the ground if any of you who are rooted experiencing this?
Maybe we can start off by stating the following:
Kernel:
Clock Speed:
OC app: Setcpu or Droid OC
Governor setting: Interactive, on-demand etc..
Last app you were in that caused reboot:
For me, I am on the following:
Kernel: Tiamat 1.41
Clock Speed: 1ghz or 1.2 ghz
OC app: Setcpu
Governor setting: Interactive
Last app you were in that caused reboot: Youtube, browser
Im not sure if this thread shld belong here but since this is Dev where most of us root and OC, I thought I'd ask it here and hopefully we spot some trends with regard to the reboots.
Pls dun flame me Thanks!

wrong section

Moved to Q&A.

I have the same issue - Canada WIFI version

same problem, Canadian WiFi Version.
Not sure if it's because I flashed 1.4.0 then flash 1.4.1 to get the external sd card to show up. But I noticed after I got the external sd card to work, my usbOTG started working too, but from what I've read that should have been removed in 1.4.1 for stability issues.

Same issue. Using the tiamat kernel. It happens with different apps so its not any one for me.
Sent from my Xoom using XDA App

Switch to Droid oc and delete setcpu. Worked for me. Interactive. On demand is junk on Xoom. I use on demand on DroidX.
The kernel will Max to 1504 causing reboot (on some Xooms). Some device can't handle 1504, mine included. Superuser will throw up an occasional user permission for Droid oc as it brings the MHz back down to user setting.

I was experiencing random reboots with the same kernel, mostly just browsing in Dolphin HD. I first stopped OC in setcpu but the reboots still occurred. Then I uninstalled/reinstalled Flash 10.2 and cleared Dolphin's data.
So far, it seems to be much more stable and even battery usage has toned down.

This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk

I installed temp+CPU and don't see two cores. Only one display for MHz and it cycles from 216 to 1200. Is there a screen I'm missing?

crauzz said:
This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100

bwcorvus said:
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100
Click to expand...
Click to collapse
Remove it? So no more overclocking? Can't a ROM allow OC and voltage control? But I guess it always comes back to the lack of source code.

Mandelbrot.Benoit said:
But I guess it always comes back to the lack of source code.
Click to expand...
Click to collapse
Kernel source is available. It's the rest of Honeycomb that isn't.

So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.

I had a harder time getting it to reboot with Droid OC so I think that's your best solution for now.
Sent from my Xoom using Tapatalk

ruvanist said:
So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.
Click to expand...
Click to collapse
Flash back the stock kernel.

solarnz said:
Flash back the stock kernel.
Click to expand...
Click to collapse
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk

crauzz said:
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.

ruvanist said:
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.
Click to expand...
Click to collapse
Yes. Go here > http://forum.xda-developers.com/showthread.php?p=13178555
Sent from my Xoom using Tapatalk

Inspire Question

What I am wondering and before you attack me I did research this and couldn't find anything specific to the Inspire. I want to know generally what is a good speed to underclock the inspire to achieve maximum batter and before you say every device is different I'm asking for a general idea not a specific one. Also do you think that overclocking has a big impact on batter I am overclocking right now at 1.3 ghz do you think that I'll notice a difference. And I know I have to test it myself but I just want others opinion on it.

I have the same question.

FWIW, I run the OnDemand Governor and underclock at 883200 (245000 min) and don't notice a slowdown in any apps I run except angry birds (I ramp it up to 1.2 to play that). I haven't run any benchmarks or anything to see how it might improve the battery, since I really don't need to worry about it. It goes on the charger every night and I've never seen it below 50% when I plug it in.
I've been running a relatively stock DesireHD Gingerbread ROM based on the Asian WWE GB (2.37.707.3) but as of yesterday, I've been running one based on the telus GB released a few days ago (2.43.661.1). My kernel is custom based on stock HTC source for the 2.6.35.10 with OC/UV support added as hacked from the LeeDroid kernel tree. My source is here:
https://github.com/hoxsiew/ace-2.6.35-gb-mr

King Askaba said:
I want to know generally what is a good speed to underclock the inspire to achieve maximum batter and before you say every device is different I'm asking for a general idea not a specific one. Also do you think that overclocking has a big impact on batter I am overclocking right now at 1.3 ghz do you think that I'll notice a difference. And I know I have to test it myself but I just want others opinion on it.
Click to expand...
Click to collapse
I'm running at my rom's default (1017mhz). Instead of underclocking, I use the conservative governor. Battery life is good, but I also haven't noticed a battery drain when overclocking (I've been up to 1228mhz). I didn't test/run it for an extended period of time (1 day), but I only noticed a slight bump in performance.
I've heard of people on my rom (GingerBeast), clocking down to 768mhz without noticeable slowdown. As you stated, it just depends on the rom.

I have my phone set at:
Max: 768000
Min: 230000
This works for me in literally all the situations.

diablo009 said:
I have my phone set at:
Max: 768000
Min: 230000
This works for me in literally all the situations.
Click to expand...
Click to collapse
just about default GingerBeast.

But what cpu scaling is best for balance of battery life and performance
Sent from my Inspire "4G" using XDA Premium App

King Askaba said:
But what cpu scaling is best for balance of battery life and performance
Sent from my Inspire "4G" using XDA Premium App
Click to expand...
Click to collapse
No one but you can figure that out.

Yea I know but id like to know what works best fire others
Sent from my Inspire "4G" using XDA Premium App

Pretty sad uve gotta worry bout people jumping down ur throat when u ask a question. I see it on here alot, thats why i dont ask.
sent from my inspire 4g on xda premium

Thank you its like they either yell at you to search or they give you all devices are different you have to try it. I'm not looking for a definitive answer I just wanted an idea of what has worked for them. Seriously this forum has some rude people exspecially that Scott guy hasn't helped me once just tells me to search I said I searched and he says its on google but when I bring up the page nothing. This forum would be 1000x better if people didn't have a stick up their asses everytime someone asked a question.

King Askaba said:
This forum would be 1000x better if people didn't have a stick up their asses everytime someone asked a question.
Click to expand...
Click to collapse
+1
Sent from the most interesting device in the world.

I hope my response wasn't considered rude, but the question really is too vague to answer. If there were some magic combination of OC/UV that worked for everyone, everyone would be using it.
They say that if you ask five New Yorkers their stance on an issue, you'll get six different opinions. Similarly, five smart phone users probably have six different opinions about the best setup for their device and none will be applicable to your situation.

Yea but I wasn't asking for the perfect combination out just wanted to know what others use to get an idea of what I should set it at but clearly you don't get that
even though I've said it three times
Sent from my Inspire "4G" using XDA Premium App

Overclocking - pros & cons?

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