Hello, I have an incredible 2 rooted with cm7 on it, and it works well but I would like to Overclock it. I have setcpu installed, but when I try to increase the Max speed or set the profile to performance or anything it force closes, so I am assuming I need a kernel that can be O
Overclocked.
This is the first time I have ever looked into getting a new kernel and it seems easy enough, I'm just having a difficult time finding the kind of kernel that I need.
Any help or information is greatly appreciated, and so is your patience.
I used the revolutionary program to gain s-off amd then root my phone, if that makes a difference.
Thanks everyone!
If you have cm7 installed, then you can already overclock without setcpu. There is a built in oc feature with cm7 in the settings. Menu-settings-cyanogen settings-performance- at the top will be the cpu settings for overclock.
Sent from my Incredible 2 using Tapatalk
Thanks so much for the reply, I actually found this last night when I was laying in bed playing with my phone. Everything is working just as it should now.
Thank you!
As far as kernels go, there are a few to choose from since you're running an aosp based rom. They offer slightly different advantages in overclocking by giving you an extra governor and different voltages. This is not something you necessarily have to flash, but its an option you have.
Sent from my Incredible 2 using Tapatalk
Related
Does anyone know how to over clock you're DI to say 1.2? Thanks for any help.
You first need to root your phone, then install a kernel that is compatible with whatever rom you are using, then you need to install an OCing app like SetCPU and adjust accordingly.
I'm rooted running the 2.2 RUU and I have set cpu. So do I just need a kernal? Which one?
i reccomend King Kernel bfs #4, best freaken kernel ever... its located... here
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
makos101 said:
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
Click to expand...
Click to collapse
A lot of factors come into play when you start overclocking, every rom will respond differently.
The first thing to do before anything is to do a complete nandroid back up.
When overclocking keep in mind that the more you overclock the more chances you have of making your system unstable.
I have experimented a quite a bit and I have found that the King Kernal #4 seems to work well for me and at 1.2 it seems to be pretty stable. Any higher than that and my phone will sometimes re-boot itself for no apparent reason.
Again, your rom may handle things different so experiment and see what works best for you.
And remember - Do a complete backup first!
I'm using the number 4 kernal and it only goes to 1.19 is this what you mean by 1.2? I have to keep mine at 1.1 ghz at 1.19 my di gets unstable
Ya that's as high as they can oc these chips. I can only get to 115 safely 119 just crashes. But the charging experience will be better than stock with the BFS #4.
Sent from my ADR6300 using XDA App
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
makos101 said:
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
Click to expand...
Click to collapse
If you are experiencing slow wake up, try increasing the min cpu speed to something around 460. Better batt life and increased speed takes a lot of experimenting. Your OC speed might differ from others due to differences in the phones cpu. For example, I have never been able to oc to 1.19 without the phone freezing or rebooting. My phone can handle 1152 but 1113 is perfect. In my opinion, ROMs have something to due with best batt-speed combo. I am running Ruby 1.1.1 with a setcpu profile of Screen off=245 without any wake lag. Other ROMs I have tried had wake up lag at that speed profile.
My set up:
(ROM-ASOP) Ruby 1.1.1
King's #1 ASOP "I told you so"- only works with ASOP
With the ROM's "Gem" performance scaling setting off, I use setcpu to OC to 1113, min is 245. I have a profile set to SCREEN OFF = 384 max/245 min.
I haven't worried about battery life since I started using King's kernals (I've tried them all with every compatible ROM on xda). I have several posts elsewhere on XDA showing 12 plus hours on a single bump charge and heavy phone use. Good enough for me. Stock cpu speed plus Sense ROM seems slow to me now.....to each his own though.
I hope to get some help because i value the opinions of those on this forum. Currently i am running virtuous 2.7 with virt. kernal v2. I am rooted, s-off, 2.15.xx radio. I want performance without draining my battery. What are the best settings to use in setcpu?
I did try king's kernal #4, but it was rebooting. switched kernals this morning.
One other app I use in conjunction with SetCPU is MinFreeManager. This will readjust your free ram to a higher standard. But with SetCPU I have it at 1113/Ondemand with no custom profiles. One other thing I really don't set is the Set on Boot option. I don't know why but I do. So with SkyRaider Vanilla 3.0 RC3/ KingX Kernel #4/ and MinFreeManager my phone fly's. I can't say for certain what settings you need for your phone but 1113-1115 is preferred by "most" phones and keep the set on boot option off. I keep a Galaxy S live wallpaper running and pandora while browsing the web and no lag what-so-ever.
CyanogenMod 6.0.2 and KingX kernel #1 with the same setup runs almost as smooth.
Hope this helps you out.
I have been bouncing back in and forth from rom to rom. Most are great. Warm 2.2, DamageControl, and Virus (currently running). The issue I'm having is no matter witch rom or kernal I run on my Evo froyo, every time I install Setcpu within a couple of hours my launcher (no matter witch one) stops working. I have gone into root to reinstall, install and uninstall and nothing works. All Rome are affected by what I can tell. I'm finding the problem to be with setcpu. I'm surprised if can't find much information on this. Does anyone have ideas?
Sent from my Evo using Tapatalk
Yea, setcpu can improve things but also causes issues elsewhere. I was using launcher pro for a while, and using that in conjunction with setcpu gave me nothing but poor battery life and terrible freezing. I have since then stopped using setcpu and my phone works fine. Besides the difference between 1ghz and 1.1-1.2 is negligible on the Evo unless your benchmarking imo
sent from my DAMN Evo!!
Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.
drmacinyasha said:
Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.
Click to expand...
Click to collapse
I did all that already. I had my screen off set to 384mhz, im no novice, setcpu has great benefits but has some negatives also.
OP, try ziggys 10/26 kernel. It has scripts that handle oc'ing up to 1.13ghz using interactive governer WITHOUT using setcpu
sent from my DAMN Evo!!
I use SetCPU and Launcher Pro Plus and have used these 2 on every ROM I have used...which is a LOT!! My screen off is set to 245 and I OC to around 1228. I have NEVER had any issues on amy ROM. I dont know what is causing your issue but it isnt SetCPU and Launcher Pro....
Can anyone tell me the best rom that comes with an overclocked kernal built in? Looking for a kernal that has killer battery life also. I've been looking but i'm new to the dinc and am not sure what the best one is. I tried to install a custom ziggy kernal with incredibly re-engineered installed but it started rebooting every time it started up... Any help is appreciated. Thanks.
Did you read everything before flashing ziggy's kernel? this is quoted from his site. did you have setcpu installed before you flashed?
NOTE1: If you’re having problems, please uninstall/disable SetCPU and any init scripts first. A lot of the issues are OC related. If everything works fine after doing that, slowly start over-clocking, if not, please post. Once the problem speed is found, report it, but most likely, it’s a voltage issue, not all phones/processors are equal. Since these kernels have snq-’s VDD sysfs interface, you can modify the VDD levels yourself. If there are any Java developers that would like to tackle the task of writing a program to assist, please do, I’ll help as much as I can
oh and make sure you dl the right kernel its the bottom 2 on his page. i made that mistake earlier today. tryed loading a bravo kernel and my phone got stuck in the splash screen
brandon2x said:
Can anyone tell me the best rom that comes with an overclocked kernal built in? Looking for a kernal that has killer battery life also. I've been looking but i'm new to the dinc and am not sure what the best one is. I tried to install a custom ziggy kernal with incredibly re-engineered installed but it started rebooting every time it started up... Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Incredibly re-engineered comes with Lou's #8 kernel, which is my understanding that it already has pre-configured screen off speeds, governor etc. It could be as simple as a wipe cache/dalvik that would solve your problem.
Other than that, i'm curious as to why you are looking into OC when you want killer battery? Those don't go together
Ok. I missed the setcpu statement. Ill try that... and I want to oc because this inc wont play the only game I play worth a crap compared to my old x... homerun battle 3d... im hoping that will help...
Sent from my ADR6300 using XDA App
brandon2x said:
Ok. I missed the setcpu statement. Ill try that... and I want to oc because this inc wont play the only game I play worth a crap compared to my old x... homerun battle 3d... im hoping that will help...
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
hmmm homerun battle 3d plays fine on my end. Check my sig for my rom and kernel, stock speeds.
chads incredikernel is probably the best for gaming, its oc-able..i actually run it some days on 1075 mhz performance, and get great batt life
Sent from my ADR6300 using XDA App
In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
scott7044 said:
In the past week have just rooted my inc2, flashed OMGB rom and Tiamat 1.1.0 kernel. I also loaded SetCPU from the market. I can't go over 1.036ghz without the phone locking up and having to do a battery pull. When the phone is back on I only have a few seconds to open SetCPU and lower the OC rate or the phone will lock again. I wiped cache/davlik cache before flashing kernel. What am I doing wrong? I have seen in the Tiamat thread in the development forum that people are going as high as 1.9ghz with out a problem. I would only like to get 1.2ghz to 1.3ghz because I read that this is a safe range. I do have have the governor set at Smartass. Thank you for your input.
Click to expand...
Click to collapse
Go back to the kernel thread look for the voltage table. The voltage levels are too low at the overclock levels, that what's causing your freeze ups. Use incredicontrol app from the market to adjust the voltage levels. You want to mirror the settings to match those of the previous version of the kernel
Sent from my Incredible 2 using Tapatalk
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
I'm fairly new myself but have been using SetCPU for a while. Make sure the "Set on Boot" option is unchecked until you find a setting that will work for your phone. As far as the nandroid, restore is your friend!! lol I've made many mistakes in the past that have totally locked up my phone and the restore option from recovery has saved me every time. There is always a chance that you can damage your phone but as time has gone by the devs have really made that possibility minimal
scott7044 said:
Thanks tnez, I found chads post about incredicontrol and sounded like it only worked on ver 1.0.4, will it work on ver 1.1.0 also.
How bad is this freezing for the phone? If I ever get really stuck will booting into recovery and reflashing omgb fix it or using the nandroid backup I created before flashing the kernel? Still new to all the rooting and custom roms and kernels, lots of fun but still have the fear of bricking the phone.
Click to expand...
Click to collapse
The app works on any kernel that supports adjustable voltages.
Both methods will work to undo things. Either restore or re flash the rom. But like stated above don't select the set on boot option until you find settings that work good on your phone.
Sent from my Incredible 2 using Tapatalk
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
scott7044 said:
Thanks again tnez, I installed incredicontrol and made the changes to the voltages so far so good. I have gone to 1.19ghz with no problems after the voltage changes. Is there app that can be used to test for stability or is just using the phone the way to test for stability.
Click to expand...
Click to collapse
You can do it by use....open up different apps very quick and switch between them...basically trying to over load the phone by making it multi task at a high level. set cpu also has a built in stress test under the info tab, run that for a few mins. I usually do the stress test for 3-5 mins followed by a quadrant test.
Sent from my Incredible 2 using Tapatalk
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
TheMavic said:
In regards to Tiamat, there have been a ton of people say that downgrading back to 1.0.4 Tiamat fixed the issue of the phone locking up when overclocked. If all else fails from what you have been recommended, try that!
Click to expand...
Click to collapse
voltages just need to be changed and made to match 1.0.4 for the kernel to run like a champ
Sent from my Incredible 2 using Tapatalk
Oky guys, so I'm somewhat of a noob and I was wondering how I overclock my Dinc running this ROM:
http://forum.xda-developers.com/showthread.php?t=1175842
I heard I have to change the Kernal or something (I have no idea what that means). Is there a step by step process somewhere or something? Also, what can I safely overclock to without damaging the CPU.
Thanks everyone!
Can't over clock the 3.0 kernels yet
Sent from my ADR6300 using XDA App
Our devs, Chad for one I'm sure of, is working on a new kernel for that. When it does drop, it's pretty easy to do with setCPU. In theory, you can cook your CPU overclocking, but devs seldom set voltage so hit you'll cook anything before the system goes unstable. Just don't check "apply at boot" until you're sure your setting will work.
thanks, looking forward to oc;ing my dinc soon
Well, I've been overclocking stuff since the days of the i486. Need some advice, hit me up.