I'm a a newer android user but quickly picking up on custom ROM's, etc. I'm currently running Alien #4 with the Alien theme and the kernel that comes with alien. I'm always trying to test out new combinations of things to see if I can get the most performance out of my phone while still maintaining a great battery life. So it's a constant trade-off. So my question is
Is there a difference between Faux's stock kernel for the atrix and the one that comes with alien or are the both stock in the sense of the same one as if I were running the Gingerbread release from AT&T?
If I were to install the Faux or kohlk OC kernls, but not install SetCPU would they still run at the higher clock speeds or would they run at 1GHZ until I used SetCPU to overclock? If they only run at 1Ghz, would there be benefit to using those kernels instead? I'm assuming they have more optimizations than just the overclocking. I'm quite happy with 1Ghz as my phone is plenty snappy so I'd rather keep the good battery life of 1Ghz but maybe get some better optimizations if possible.
I understand I can run SetCPU to have it clock down the CPU, but I've tried that on a number of occasions and even with it supposedly capped at 1Ghz, I still saw SetCPU saying my phone was in the 1.1Ghz state a fair bit.
I have faux's 1.3 ghz kernel and my battery life is comparable to the stock 1 ghz kernel.
Faux's stock kernel is a more optimized version of the stock kernel and is pretty good but his best work is put into his OC kernels. I suggest going with one of those...and yes you would need setCPU to get it to run above 1 ghz.
Have you ever run a "quadrant standard" test on your phone? I ran one when I was stock and scored below 1750. When I was on Alien v4 with faux's 1.3 ghz OC, I hit 2500. Now that I'm on CM7 with the same OC (and a little undervolting) I'm scoring above 4700.
Yea I use quandrant quite frequently but for me quandrant scores are good but I use my judgement on which feels the best. I know its now scientific but it works for me.
Sent from my MB860 using Tapatalk
so i have always run overclock kernels w/out any problems. bali at 1.2, bullet at 1.42, bullet at 1.48, and i cant remember the name, but another kernel at 1.5. all without any problems.
I want to try to clock higher. I have tried the app Tegrak, while using bullet 1.48, but it wont let me clock past 1.48.
Is the only solution to try to build a kernel myself, are there any Vibrant kernels that clock faster then 1.5, or is there an app that will let me set my clock speed above the preset?
thanks
Glitch kernel for MIUI and CM7 allows clocking up to 1.7ghz. It's rarely stable, but if your CPU is capable, use the ML or LL versions and see how far you can go.
You'll have to be using MIUI or CM7, obviously.
kaintfm said:
Glitch kernel for MIUI and CM7 allows clocking up to 1.7ghz. It's rarely stable, but if your CPU is capable, use the ML or LL versions and see how far you can go.
You'll have to be using MIUI or CM7, obviously.
Click to expand...
Click to collapse
the thing is that im on always on 2.2 or 2.2.1
Yeah was gonna suggest glitch+cm7or miui but if you are on 2.2...
I think cmenard might have made a 1.54ghz bullet(only worked on some vibrants,needed good cpu)
can't remember if it was GB bullet or 2.2 though. google it yourself....
If you're not willing to move to MIUI or CM7, there's not much you can do. Regardless, 1.5ghz and above is rarely stable anyways. Only thing that has gotten me past 1.3ghz stable is the Glitch kernel with the medium leak CPU tweaks.
It is possible to build 1.7ghz frequencies to a froyo kernel(the kernel dev just have to know where to add it), but chances are few phones would be able to handle it, and battery life would seriously decrease at those frequencies. My opinion is 1.7ghz on a vibrant isn't worth it.
Honestly, I'm down to 1512. A notch above that proved unstable as far as I can tell. I can run benchmarks fine upwards of ~1800, but I'll get random force closes and boot loops if left for any extended period of time. Also have issues with display not coming back on (menu lights and led backlight work, but no image). The stability test app is pretty much worthless too. Let it run for 6 hrs no errors. When I turned it off, BAM restart.
So what is your max, truly stable, OC?
Sent from my PG86100 using XDA App
edit: just for archival's sake, using Anthrax-CDMA-Sense (v1216) with Scott's 2.08.651.2 Stock Rooted ROM.
That's interesting...
I'm using the same Kernel with Scott's 'senseless' ROM and I have my clock set to 1.836 with no issues.
I'm no expert but have you tried using a super wipe (or just manually wiping everything including system) and reflashing?
Sent from my PG86100 using XDA App
My first 3D was pretty stable at 1.94 but when it started getting the black screen of death I got it replaced through sprint. The Refurbed one they gave me (the one I have now) freezes if I go to 1.6..
I used to do 1.94 but it gave me random reboots (nothing fatal)
I stick to 1.5 smartass when the battery is greater than 50%, then 1.2 smartass, and .8 conservative at 15%.
On charge it's 1.7GHz lagfree
Depends on your CPU, they all arn't created equal. I'm stable at 1.9 GHz with no reboots. I'd say that 1.5 is a good mark, seeing as the HTC Rezound has the exact same CPU as the Evo 3D, just clocked to 1.5 instead of 1.2.
Akasa Fox said:
Depends on your CPU, they all arn't created equal. I'm stable at 1.9 GHz with no reboots. I'd say that 1.5 is a good mark, seeing as the HTC Rezound has the exact same CPU as the Evo 3D, just clocked to 1.5 instead of 1.2.
Click to expand...
Click to collapse
This is interesting. I bet the CPUs, while manufacturing wise are identical, are chosen based on thier bin level for the different devices.
After writing this post I cleared Dalvik cache and switched my kernel to RCmix-evo3d-v7. I ran it at 1.62 or something like that while I was running around Christmas shopping, so it had heavy use. Google nav, lots of phone calls, texts, Pandora, etc with zero issues (especially that display issue I mentioned is gone, thank god). After getting home I was so impressed with it that i stepped it up to 1.782, and we'll see about that, although I'm not holding my breath.
Basically I learned that your overclocking potential (or maybe more accurately system stability regardless of overclocking) is greatly influenced by your kernel.
Akasa Fox, mind sharing your kernel version, ROM and version, and hboot and any other potentially relevant information I may be forgetting? I'm impressed with your performance.
Sent from my PG86100 using XDA App
zadias said:
I used to do 1.94 but it gave me random reboots (nothing fatal)
I stick to 1.5 smartass when the battery is greater than 50%, then 1.2 smartass, and .8 conservative at 15%.
On charge it's 1.7GHz lagfree
Click to expand...
Click to collapse
I like this approach of different clocks and governers based on bat level. Is this a pro feature of the Antutu app?
Sent from my PG86100 using XDA App
bleaktrotter said:
This is interesting. I bet the CPUs, while manufacturing wise are identical, are chosen based on thier bin level for the different devices.
After writing this post I cleared Dalvik cache and switched my kernel to RCmix-evo3d-v7. I ran it at 1.62 or something like that while I was running around Christmas shopping, so it had heavy use. Google nav, lots of phone calls, texts, Pandora, etc with zero issues (especially that display issue I mentioned is gone, thank god). After getting home I was so impressed with it that i stepped it up to 1.782, and we'll see about that, although I'm not holding my breath.
Basically I learned that your overclocking potential (or maybe more accurately system stability regardless of overclocking) is greatly influenced by your kernel.
Akasa Fox, mind sharing your kernel version, ROM and version, and hboot and any other potentially relevant information I may be forgetting? I'm impressed with your performance.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
The kernel does have a decent bit to do with your max OC, but it also has to do with the CPU you have and if it was made on a good day at the foundry or not and how good a section of the silicon it came from.
I used to run RC Mix kernels before Chad was around, but those kernels always ran MUCH hotter. When playing a game my phone would literally be almost too hot to touch. Chad's Anthrax kernels have always been cool and after playing a game for a while (same game, same amount of time) the phone is just a bit warm. So you may be able to go farther with an OC on RC Mix kernels, but your phone's lifetime for its processor is going to be a whole lot less. At the temp it was hitting id bet it is well above its max rated temperature level and degrading the processor substantially.
Some people may not be able to OC far, but how far can you undervolt? Many times those who cannot OC very high can undervolt like crazy (me included) and those who can OC much higher than most also cannot run really low voltage levels. My phone is 100% stable @ 192MHz on only 700mv. Thats the lowest Chad allows, Id love to see if I can be stable even lower. I am also 100% stable @ 1188MHz (HTC Stock) with only 987.5mv. But the most I have ever been able to overclock stably (even with RC Mix kernel) was 1.6GHz, with the max benchable being 1.72GHz. Any higher and the phone insta locks up and reboots. No matter what voltage.
Hm, that's a good point. I'd like to push the undervolt limits as well to see what its got. That anthrax kernel I mentioned in the first post was terribly unstable for me, but maybe I should give it another shot after researching the super wipe method mentioned a few posts up. Is there a version of his kernel that everyone is having good luck with? Or is the latest one the best?
Also, I don't see voltage options in the antutu program. What are you using for your oc/uv utility?
Thanks.
Sent from my PG86100 using XDA App
bleaktrotter said:
I like this approach of different clocks and governers based on bat level. Is this a pro feature of the Antutu app?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Just profile settings for SetCPU.
bleaktrotter said:
Hm, that's a good point. I'd like to push the undervolt limits as well to see what its got. That anthrax kernel I mentioned in the first post was terribly unstable for me, but maybe I should give it another shot after researching the super wipe method mentioned a few posts up. Is there a version of his kernel that everyone is having good luck with? Or is the latest one the best?
Also, I don't see voltage options in the antutu program. What are you using for your oc/uv utility?
Thanks.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
His latest 100% Qualcomm based kernel is incredibly smooth. 100% stable for me. I'm giving this kernel a lot of praise considering I used to have crazy reboots and lockups on the older anthrax kernels.
Sent from my PG86100 using Tapatalk
Weird. Well, I will give it another shot before writing him off. I'm a noob so its entirely possible and probable that I did something wrong.
I found setcpu last night, but I didn't see any uv options. Does rcmix not allow for it?
Thanks.
Sent from my PG86100 using XDA App
Just leave it at the default settings... It's fast enough as it is.
Sent from my PG86100 using xda premium
1782mhz. I stay at stock though.
My Blog: knowledgexswag.tumblr.com
Twitter: @knowledge561
Coriolis3ffect said:
Just leave it at the default settings... It's fast enough as it is.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Noted.
Sent from my PG86100 using XDA App
My phone won't overclock for ****. At first it would do good and I could get around 1.7-1.8, now when I try anything after superwipe and wiping through nand, I can't get the thing to post at 1.5 and remain stable without lockups/freezing and slowdowns. The phone even has trouble at stock now. I haven't traded it in for obvious no s off reason.
1.78 GHz. I can do 1.83 but not very stable.
1.782 runs all day locked at that speed but I usually run bcblend kernel @ 1.512 max 194 min. Ondemand.
Sent from my PG86100 using Tapatalk
bleaktrotter said:
Akasa Fox, mind sharing your kernel version, ROM and version, and hboot and any other potentially relevant information I may be forgetting? I'm impressed with your performance.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I know it was Virus' InfectedROM (Before the nightly), Software 2.08.651.2, HBoot 1.5 (HTC Unlock.) [Edit]: I'm almost certain the Kernel I used was Tiamat, hard to remember though, seeing as I traded out performance for battery life by switching to viper ages ago. (And that i'm a flashaholic )
im @ 49 hours uptime on RLS4 of my new kenel @ 1.94GHz IntelliAnthrax
..no RLS4 is not public yet -- testers will have it in 1-2 days
Hello! i am in the process of overclocking my thunderbolt in order to get better performance with the eternity rom, and i was wondering what you guys oc your phones to? and if you do, what program/setting do you use to do so? (i plan to use a script in init after have found suitable settings)
I, personally, find it pointless to OC the Thunderbolt. The phone is fast and smooth enough for me on the stock speed, plus the battery life is bad enough without adding more strain to it.
However, if you insist on OC'ing, 1.2GHz is a safe bet. Some people can get to 1.4GHz, but then you run into freezing and random reboots. Also remember that individual phones handle overclocking differently. Where one phone can run perfect at 1.4GHz, another might freeze instantly when going that high.
Good OC'ing programs include SetCPU, No Frills CPU, and ROM Toolbox.
I don't overclock. That being said i have OC'd my phone b4 i have had it up to 1.8 Ghz stable, but it doesnt seem to make anything run faster. I use the Thundershed version of CM7 and its super fast. I dont think it could get much faster. and without overclocking i get better battery life.
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
lacrosse1991 said:
thanks for the info actually ended up going with the lean kernel which is oc'd on the kernel level, works fairly well
Click to expand...
Click to collapse
Leankernel is tops. I use battsaver mode which is stock speed and undervolted. Smooth as butter on my phone.
Sent from my ADR6400L using xda premium
Just wondering what kernels people are running on NOS m7 v2.0.3 it comes with the stock kernel. From reading thread it seems like a lot of people are using Beastmode kernel and a few people are using crpalmer kernel. Any advantages of one over the other? Will one work better than the other?
pitchinnate said:
Just wondering what kernels people are running on NOS m7 v2.0.3 it comes with the stock kernel. From reading thread it seems like a lot of people are using Beastmode kernel and a few people are using crpalmer kernel. Any advantages of one over the other? Will one work better than the other?
Click to expand...
Click to collapse
Beastmode is faster IMO, benchmarks higher, overclocks to 1.9, has more options, it also has sweep2wake and the flashy button thingy, and USB drives mount automatically without a third party app. It doesn't have the best battery life but it's not bad either. It seems to get unstable for me when I put the lowest frequency at 192 mhz.
Crpalmers kernel is more of the opposite approach. Reliability, battery life, and improving upon all the faults of htc's stock kernel. The battery life is pretty unreal ppb this kernel. It's completely stable at any frequency with any governor. It doesn't have any extra frills though like sweep2wake or extreme overclocking.
Both of them are excellent kernels it's really just personal taste. I would recommend trying both for a few days and seeing which you prefer.
Sent from my DNA using Tapatalk 2
jamiethemorris said:
Both of them are excellent kernels it's really just personal taste. I would recommend trying both for a few days and seeing which you prefer.
Click to expand...
Click to collapse
Yeah I have been on crpalmer's for a couple days and so far have thought has done great. Not really into overclocking on my phone since I don't really using it for gaming or anything CPU intensive right now. Thanks for the input.