Is it me or do Slayher's kernels seem to be head and shoulders above any other dev's in terms of speed? I'm running Pete's BB V0.5 and with Slayher's 900mhz kernel I'm getting about 1300 on Quadrant benchmarks. On Chevy's I was hitting about 1200 with his 1ghz lv kernel, and about the same with P3droid's. Chevy's ran a little cooler than P3droid's and Slayher's, though.
Anyway, what are you guys getting in terms of battery life from these? Any voltage, speed or ROM.
Please no flaming if this is a noob-ish question.
Sent from Droid
Just ran quadrant with Chevy's 1.2 and got 1726.
Using UD 2.0 right now but I had a similar score on BB 0.5. Batter lasts a full day of continuous use, using the ulv kernel. Phone never gets more than a little warm.
Related
Ive gone through just about every Froyo ROM, and the best results that Ive come across has been with Rodriguez 1.8 and pershoot's 1.113 OC kernel.
I was getting over 45 mflops on linpack
and over 1600 on quadrant standard
Then I tried moving around alot and ive been playing with Evil's 1.228 OC kernel, which for some reason is showing less performance benchmarking wise
im getting about 42 mplofs on linpack
and a little over 1500 on quadrant standard
So what has everyone else found as a fast setup? (again, benchmark wise)
With "stock" Froyo (first version released by Paul) I could get 40.7Mflops with Lin and 1425 with Quad. Im happy with the original combo of stock kernel and stock ROM for now.
I am using Setcpu on my motorola droid with rooted FRG22. Why wont it let me overclock it higher than 800mhz??? I'm kinda new to doing this and wondering if I'm doing anything wrong. Thank you
[A] Overclock answer
Yes you have SetCPU and your phone is rooted. However, you're missing one more piece to the puzzle. In order for you to clock over 800Hz you have to install a kernal cooresponding to the voltage and what you want to overclock it to. I recommend you googling(haha) p3designs and choose a kernal you want to try. Instructions are on the site as to how to install. I currently have a low voltage of 125Mhz overclocked at 1Ghz. Hope that helps
Question for you Stephen, with you running 1.2Ghz on your droid, has there been any istances of freezing thus far? I was tempted to go higher, though I stuck with 1Ghz to be safe.
M4r34d0 said:
Question for you Stephen, with you running 1.2Ghz on your droid, has there been any istances of freezing thus far? I was tempted to go higher, though I stuck with 1Ghz to be safe.
Click to expand...
Click to collapse
The right approach to overclocking is not how fast can you go, but how low can you tolerate? Most Droids are stable to 1.2 ghz. Some can go higher, some can't. I'm running the "stock" 1ghz kernel that comes with Sapphire rom. However, I have it choked back to 800mhz. This gives me 36 hours of battery life on light-moderate use, (3G off, wifi on) but also lag-free performance.
This is chevys 1.25 medium voltage, only reboots were with watching movies online.
Sent from my DROIDX using XDA App
That was droid 1, lol barely get 1300 with my droid x
Sent from my DROIDX using XDA App
The links for the kernals over at p3designs don't seem to be working for me. Does anyone have some overclocking kernels they could post?
Barkleyfan said:
The right approach to overclocking is not how fast can you go, but how low can you tolerate? Most Droids are stable to 1.2 ghz. Some can go higher, some can't. I'm running the "stock" 1ghz kernel that comes with Sapphire rom. However, I have it choked back to 800mhz. This gives me 36 hours of battery life on light-moderate use, (3G off, wifi on) but also lag-free performance.
Click to expand...
Click to collapse
I understand what you mean. I've done the trial between 800Mhz and 1Ghz. I have emulators now and I liked the performance on the 1Ghz more because of the speed, so I kept it on 1Ghz. I haven't had any battery drainage issue and all. I liked my low voltage 1Ghz kernal.
kclive said:
The links for the kernals over at p3designs don't seem to be working for me. Does anyone have some overclocking kernels they could post?
Click to expand...
Click to collapse
http://p3designs.info/kernels/
Is this the site you tried accessing the kernals? I did a test and downloaded the kernal zip fine.
That does sound impressive. I'm curious to try that out even more so now.
I'm just surprised when running cm7 on my nexus one. It felt snappy. But when I put in quadrant, it actually came out in 3rd place when running 998 Max and 245 min. So I overclocked both to 1113 mhz, and the score wasnt impresive either: 1424...which is only a tad bit better than n1 on 2.2. Now does this have to do with the app itself or the device?
Sent from my Xoom using XDA App
Thread moved to Q&A, since this is a question.
FWIW, on my Nexus S, my score (and overall 3d performance) went down considerably between 2.3.2 and 2.3.3 ROMs (e.g. CyanogenMod 7 RC1 and RC2). I used to get ~4000 in Quadrant at 1.4 GHz, whereas now I only get around 3300. The part most telling for me was that in the first 3D test, I used to be locked at 65 fps for the majority of the test. Now I get around 2/3 that. Similarly Smartbench 2010 and 2011 show major declines as well. Not quite as pronounced, but noticeable nonetheless. My previous recorded score was 1635/3669 at 1.4 GHz, and now I get 1551/3251.
On the Nexus S, I know that this decrease in performance is due to the different framebuffer driver in 2.3.3, which now supposedly calibrates the screen to not be as over-saturated and raises the gamma to 2.2 from 1.8. I don't know if this is applicable to the Nexus One.
There is definitely a decrease because I used to have up to 1800 in quadrant when running at 1.113 ghz. But the weird thing is the phone still felt really snappy when I set it to 998 mhz. In contrast, I experienced random lags on cm6 at 1032 mhz. Weird!
Sent from my Xoom using XDA App
Thinking if overclocking my captivate to 1.6 but will it shorten the like time significantly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
UV
Jusrertiner said:
Thinking if overclocking my captivate to 1.6 but will it shorten the like time significantly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
UV
Click to expand...
Click to collapse
What is your desire to oc?
Sent from my Captivate using XDA Premium
Very risky
Very.
Yes it will shorten the life on your phone no way to know how much though. unless you are into it and read a fair amount about it i would not oc. The benefits just are not that significant
Sent from my GT-I9000 using XDA App
start at 1.2 if your scared
It will not shorten the life to the extent that it will not last the update period
Miui Captivate
Oh well how long do u think it will last. N I want it for the extra speed in games mostly.
Samsung captivate
glitch kernel
cyanogenmod 7 #57
OC and UV
If you want some extra speed, still to 1.2 and below and try using Pimp My CPU to drop the voltage -50mV across the board (try messing around with it more to get more drops without charge deaths and etc). By doing this, I am running mine currently at 1.2 ghz with a -100mV voltage drop, which is the same as stock 1.0 ghz voltage level.
It's overvolting that kills a processor, not overclocking. More voltage means more power for the processor to dissipate as heat and some components are not spec'd to take more voltage than stock.
I hope this helps.
I have read that you should be safe up to 1300mv(not mhz). Usually 1200 mhz will run that. After 1300mv, you risk damage. It also can cause charging issues (phone uses more battery than it is charging).
Don't get me wrong, at one point I had my phone up to 1500 mhz, just to check kernel stability. Didn't stay there. Also remember that each phone is different when it comes to this. Some phones tolerate it better than others. That is why entered no definitive guide to it, only recommendations.
You shouldn't be scared to OC. but its your phones processor because everyones is different. My captivate can only get up to. 1.5. Then it freezes up. My inspire 4g can get up to 1.9 without a problem while others can only get to 1.6 or so. So try it out
Sent from my Inspire 4G using XDA Premium App
I overclocked to ,1.3 and my while screen turn purple and green n I had to pull battery. Is that a crash?
Samsung captivate
glitch kernel
cyanogenmod 7 #57
OC and UV
Hello
I recently acquired a nook color and i am going to install cynogen mod 7.1 and google apps from clock work recovery method, but i want to overclcok to 1.2 or 1.3 ghz, i understand that cynogen mod has an overclock facility built in, the part i am not sure about is to reach 1.2 ghz or 1.3 ghz do i have to use dalingrin overclock kernel to achieve these speeds, or is it possible in cynogen mod 7.1 without the kernel.
Any info would be appreciated.
Regards
Mark
Dal's kernel has been included in there for a while now. If you use 7.1 stable to later nighlies you are definitely safe.
ok, thats great, thanks for the reply, appreciated.
Regards
Mark
It appears the GPU may run best at 1200, even thou the CPU can do up to 1300.
It certainly seems to be true that going past 1200 can slow down graphic intensive operations. I am guessing that's probably because the graphics processor has to run at a ratio of the CPU and going past 1200 ends up with a lower graphics frequency.
But depending on the type of applications used there can be benefit in going higher and most Nooks seem to be capable of 1350. This can be seen in two different benchmarks. Quadrant gives significantly higher scores at 1350 than 1200 whilst the graphically more intensive Nenamark is slower at 1350 then 1200.
I ended up using 1200 anyway as it feels fast and probably also helps with battery life.
Check the voltage settings as well as these can normally be lowered a bit to help again with battery life. I use the one's originally quoted by Dal and don't have any stability issues. ( 09.25 / 1.05 / 1.2 / 1.275 / 1.325)
I did a comparison of 1200 and 1350 MHz with the Sunspider JavaScript bench. 1350 is faster but frankly I have a hard time telling the difference between even stock clock and 1350 in actual practical usage.
The most obvious speed boost I've found is running 16bit color. Big difference in browser scrolling performance.
Is overclocking it fully safe?
GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
From the standpoint that breathing in a metropolitan area is not fully safe, no it is not.
I use the stepper built-in to 7.1 stable and have never given it a second thought.
Try nook color tweaks.
Sent from my [R3] BLURR3D DROID BIONIC using XDA App.
GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
I have run at 1200 / 1350 for the last 4 months and it has been stable and I have not seen any real detectable difference in battery performance or in how warm the device gets. The governor means that a lot of the time the Nook is running at lower clock speed anyway.
I don't recollect seeing any reports of damage on this forum to the Nook through over-clocking. Increasing voltages from the stock values on the other hand is probably not a good idea. There may possibly be longer term effects from overclocking but I'd guess the effect on lifetime is small enough that most people will have changed their device before it is significant.
GuTsaV said:
Is overclocking it fully safe?
Click to expand...
Click to collapse
Being that Nooks CPU is underclocked by default. It is very safe.
---------------------------------
Sent from my LG Optimus V using Tapatalk