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.
Related
http://forum.xda-developers.com/showthread.php?t=1020637
DON'T USE THE ROM, IT IS OUTDATED AND HAS BEEN DISCONTINUED!
DO NOT USE THE "PUV" (Pinky UnderVolt) VERSION, IT WILL CAUSE YOUR DEVICE TO GET STUCK AT THE SPLASHSCREEN! (POSSIBLY)
I DID NOT MAKE THIS KERNEL, I'M JUST POSTING IT HERE FOR YOU ALL.
THIS IS NOT FOR ANY OTHER ROMS BESIDES CM7 (AND CM7-BASED ROMS) AND MIUI, SO DON'T ASK!
I'm using the UUV CFS version. It is very fast and smooth, I urge you not to have an OC past 1.3GHz as a daily driver, unless you want horrible battery life.
Any option below PUV is safe (UUV, -50mV, and -25mV all work, but every device varies).
i didnt think my phone could ever sh*t itself until i flashed this kernal.
dethpikil said:
i didnt think my phone could ever sh*t itself until i flashed this kernal.
Click to expand...
Click to collapse
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?
vln004 said:
i logged in just to ask you to decrypt that message. what does that mean? bad kernal?
Click to expand...
Click to collapse
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.
Been running his kernels for a couple of weeks, no issues. It is nice to be able to choose from different undervolt versions. Helps battery life a little, around 5%-10% in my experience.
NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.
henrybravo said:
NikolaiT, just FYI this kernel works with Ultimate Droid, which is based on CM7. In case you want to update the OP.
Click to expand...
Click to collapse
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk
dethpikil said:
lol, iffy kernal. especially with two versions available, its kinda strange testing them and seeing whats best for your phone. flashed the cfs version, and as expected, things seemed evenly smother throughout the phone, yet even at 1.99, there was nothing special or over the top about performance. also, i had a very strange, completely indescribable hiccup after booting.
EDIT
tried the bfs version, and still nothing special. maybe its just me and my miui rom. the 1.99 is cool, but i think im just gunna stay away from this.
Click to expand...
Click to collapse
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.
rasroygbiv said:
+1. Running 4.2 cfs -25 version on UD now. 4.0 was the best battery life ever on any cm7 based roms. Haven't tried the puv version yet, but rest assured I will try and report results..
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Careful, the PUV version softbricked my device. Easily fixable through reflashing your ROM or just a new kernel.
It may not brick yours because some devices can handle it, some can't.
helushune said:
Hardly "iffy", the differences are stated in the thread or here.
I've been using this kernel with CM7 Final for quite some time now and it's been quite solid.
Click to expand...
Click to collapse
+1. Not "iffy" at all.
I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App
TheBassman369 said:
I've been using it for a while now. At the moment I'm using the latest CFS -25 UV version @ 1305 with the scaling set to Intelligent Donkey (lol) and I actually made it an entire day without charging. That's saying a lot for someone that gets about 12 hours max on a charge.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'm currently pulling two days at 64% with the same kernel but my CPU settings are 122 min - 1075 max.
So what's everyone recommendations for the best version of this Kernel in terms of both optimum battery and performance?
Additionally... what kinds of CPU governors and max-min frequencies are you using? I've seen a few post what their using in this thread, but I'd like to get some more opinions.
I've been using this Kernel for a few weeks now with no issues. The UUV had some slight hesitation when scrolling so now I'm running 4.3 CFS with the -50 UV and it's absolutely perfect. Fantastic battery life running at 122/1305 MHz with the -50 UV.
i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.
substance12 said:
i'm using 4.2 and I didn't flash any scripts... is the default -25UV? I'm gonna try 4.3 and -50 script later tonight.
quick question to the group: what is eating up your battery? mine, oddly enough is cell standby and phone idle. i'm using stock radio. in the past (on froyo builds), it's always been screen time.
Click to expand...
Click to collapse
Default is no undervoltage.
Cell Standby and Phone Idle are my two biggest "battery killers" but that's normal operation.
henrybravo said:
+1. Not "iffy" at all.
Click to expand...
Click to collapse
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.
Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?
dethpikil said:
maybe all of you missed the whole miui thing. it says it works great with miui, but my phone seemed very buggy after switching from cattleprods kernel, but you tested it on very different roms than me. it addition, my quadrant score were crap on both types, cfs and bfs, which is completely contrary to the description of one over the other. so yes iffy.
Click to expand...
Click to collapse
I sure did. Pardon.
sugardaddy1979 said:
Can anyone explain the difference between the scheduler flavors? I use cfs, but bfq or io?
Click to expand...
Click to collapse
Check these two posts: Post 1, Post 2. Looks like BFQ is the standard scheduler and VIO is quicker on paper (kind of like BFS vs CFS).
Thanks for the explanation. The bfqhs seems much smoother than the io. I am running it with the uuv.
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
Hi I am flashing this phone for a friend and I come from the Samsung Captivate so its fairly similar. Only question I have and I hope someone can help without flaming me is which Kernel would you suggest? Im going with Infused 1.5.2 as the rom and I am just curious what pairs with that best? Thanks in advance.
jivy26 said:
Hi I am flashing this phone for a friend and I come from the Samsung Captivate so its fairly similar. Only question I have and I hope someone can help without flaming me is which Kernel would you suggest? Im going with Infused 1.5.2 as the rom and I am just curious what pairs with that best? Thanks in advance.
Click to expand...
Click to collapse
if you're one of those "set it and forget it" types... i was incredibly pleased with the latest release of gtg's infusion 1.5.2 rom/kernel combo. very responsive, smooth and snappy. by far my favorite of all his releases to date for this phone.
if you're the type that likes to do a bit of fiddling for an ultimately rewarding end result, i recommend installing the above mentioned rom with bedwa's OC/UV kernel. i've had nothing but a smooth and stable experience with the two paired together. nothing but good things to say about both of these. having voodoo lagfix alone makes a huge difference. when you combine that with overclocking you get a device that feels much more awake and ready to perform. undervoltage allows you to use less battery power, even though the cpu is running at a higher frequency. really, makes a HUGE difference. cannot express how pleased i am with these two running together.
*i might also add that i've never installed any of the other roms. i have tried the defuse kernel with BLN was introduced(it has since been removed due to buggy issues).
bradbusa said:
if you're one of those "set it and forget it" types... i was incredibly pleased with the latest release of gtg's infusion 1.5.2 rom/kernel combo. very responsive, smooth and snappy. by far my favorite of all his releases to date for this phone.
if you're the type that likes to do a bit of fiddling for an ultimately rewarding end result, i recommend installing the above mentioned rom with bedwa's OC/UV kernel. i've had nothing but a smooth and stable experience with the two paired together. nothing but good things to say about both of these. having voodoo lagfix alone makes a huge difference. when you combine that with overclocking you get a device that feels much more awake and ready to perform. undervoltage allows you to use less battery power, even though the cpu is running at a higher frequency. really, makes a HUGE difference. cannot express how pleased i am with these two running together.
*i might also add that i've never installed any of the other roms. i have tried the defuse kernel with BLN was introduced(it has since been removed due to buggy issues).
Click to expand...
Click to collapse
It was for a friend.so set it and forget it was my best option. He instantly noticed a speed improvement in the responsiveness using infusion. Thanks for the help.
Sent from my I897 using XDA Premium App
jivy26 said:
It was for a friend.so set it and forget it was my best option. He instantly noticed a speed improvement in the responsiveness using infusion. Thanks for the help.
Sent from my I897 using XDA Premium App
Click to expand...
Click to collapse
cool man. no problem. infused rom makes a world of difference in itself.
I've had the best battery life and stability on Infusion 1.5.0
Overclocked to 1.6, with the right undervolting i lost 3% battery over night (9+ hours)
I tried the 1.8 infusion but "OnDemand" stops working and thats my favorite setting so I went back to 1.5.0
I never had good luck with ondemand, along with most other users. Ondemand always FC'd on me
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.
If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..
AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.
bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.
Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.
hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2
bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
yellowfuse said:
Why is the overclocking area on my Captivate greyed out after installing cm9 latest nightly???
I honestly do not have the time to read hundreds of pages of forums to see if someone has allready had this issue.
Of course i tried searches.
It happens on any cm9 nightly, not just the latest one.
I want to be back at 1.2ghz. being stuck at 1ghz. is rediculous to me after being so spoiled. (lots of google earth, gaming and other stuff that a higher clock speed helps with)
If I have to I will just go back to 2.3.7 and a swift 1.3ghz. MAX
BUT it seems like I should be able to overclock using CM9 on my captivate.
Please do not explain the system settings and performance yadda yadda yadda, anymore, i am obviously familiar enough with an android device to know how to use system settings etc. if i can root and install custom roms i can read and point and click as well.
Sorry for the frustruation but i seriously can not deal with anymore nonsense and 80 diff. pieces of broken info from people that only "heard from some guy" about how to do all this.
Thank you in advance... forever learning"!"
Click to expand...
Click to collapse
Were you using Glitch before, or some other custom kernel? I didn't think cyanogen's stock kernel supported overclock. If you install a new nightly you have to reinstall your overclocking kernel.
I have been using cyanogenmod only. I never purposefully installed a custom kernel then the rom. Just used Odin to root/clockwork and so forth. Never heard of Glitch. Through out all of my custom rom experiences with the captivate I have been able to use the sys. settings or osmonitor to overclock to a max of 1.3ghz. I have tried miui or whatever its called for about five minutes. other than that just cm6/7, then updated to cm9. in the past whatever kernel i had, stayed in effect, i guess.
I will do a search for custom kernels for cm9 on captivate.
I havent seen any yet, but who knows. I am used to simply stunning roms and the moto droid one. That was great! SS/chevy~ would always have links to the latest kernels avail. for the current builds etc. Good job too.
SO... the search continues.
*Mystery: If I cant even change cpu settings in osmonitor (up or down), yet it lets me enable root mode, what does that mean? The greyed out overclocking area in perfomance settings (up or down)???
I need to learn more"!"
As mentioned, glitch kernel b6 is a great ics kernel. Flash over CM9 and install nstools from the market to control all the kernel settings such as oc/uv, voltages etc etc.
Sent from my glitched ICS Captivate using XDA App
The options are greyed out because the stock kernel currently doesn't support overclocking. Glitch is awesome, and Semaphore kernel is pretty nice too.
Sent from my CM9 ICS i897 Captivate
IcyGlitch for OC, and Semaphore for 400MB mem.
Well Glitch has 387 MB of free RAM
both kernels are good
I want my 13 MB! They are unused so occupying them is unforgivable. IcyGlitch is solid kernel, and I hope 400MB will be added.
b-eock said:
Well Glitch has 387 MB of free RAM
Click to expand...
Click to collapse