Which of the current 2.3 ROMs is considered the fastest/most responsive? Or which ROM would be considered the fastest based on the mods & tweaks used by the developers? I'm not to versed in the technical side of things to discern which tweaks/mods/kernels/etc give way to the most stability, speed, and response and would like the community's opinions on the matter.
Probably CM7, I just started using it and there is never any lag. I haven't even OC'd it yet. This also comes with the price of having to live off a wall charger though.
Sent from my SGH-I897 using XDA App
If you mean fastest in clock speeds, then thats a balance betwen rawr clock and how much battery life you can get out of it. Keep in mind these phones clock easily 1.2ghz-1.3ghz no issues past that you need to increase the voltage. So you can in theory get 1.6ghz-1.8ghz but you will live next to a charger. If you mean fastest on how it feels Id have to say Continuum moved awesome few months back (haven't used it in a while) Atomic Fusion if the ext4 version comes out. But there you should just test them out.
On a side not if you want to OC your phone and not have to pay for the oc app, then Id suggest you stick to I9000 ports or AOSP's like CM7 or MIUI. Native roms like Cognition 5, Atomic Fusion and Nuclear Fusion need Tegrak for OC/UV.
Which of the I9000s seem to run the fastest/smoothest? I've been looking at Dlev and Darky but how does Apex/Symply GS II/Mosaic/Sensation compare?
prbassplayer said:
Keep in mind these phones clock easily 1.2ghz-1.3ghz no issues past that you need to increase the voltage. So you can in theory get 1.6ghz-1.8ghz but you will live next to a charger.
Click to expand...
Click to collapse
I actually read in the Glitch kernel thread that when overclocking, higher voltages doesn't always mean more stability. I'm OC'd at 1.5ghz right now really stable and I was UV'd at -50mv but I just dropped it to -75mv to see if its stable there. I'll keep dropping it till I have issues.
Oh yeah, and CM7's battery life has got WAY better over time, so I'm not having to worry about charging all the time either.
Sent from my Samsung Galaxy S Captivate
Reamer09 said:
I actually read in the Glitch kernel thread that when overclocking, higher voltages doesn't always mean more stability. I'm OC'd at 1.5ghz right now really stable and I was UV'd at -50mv but I just dropped it to -75mv to see if its stable there. I'll keep dropping it till I have issues.
Oh yeah, and CM7's battery life has got WAY better over time, so I'm not having to worry about charging all the time either.
Sent from my Samsung Galaxy S Captivate
Click to expand...
Click to collapse
From my experience to maintain a stable phone i over volt the "step" that's overclocked, and then undervolt the other "steps". Im by no means a expert nor is there a full proof way to do it. Each phone kinda reacts differently on the overclocking past 1.2-1.3ghz.
Which of the I9000 roms should theoretically run faster due to the tweaks/mods used by the developers without the need to overclock?
There if no need to overclock for daily use. Only if you are playing very demanding games. And only during those games.
As for fastest rom....have a search this question gets asked a lot with always the same answer and result:
There is no best rom, all phones are different as well as tastes, what's best for me on my device may not be on yours. Flash and try a few and make you own decision...
CM7 is fastest but Display and Sound quality is not as good as stock ROM .
Before school started for me and i couldnt access a charger when i wanted to, i used MIUI at a stable 1.6 GHz ALL of the time with odemand govenor and i got like 18 hours with moderate use, on Glitch V12! And you dont need to overvolt for higher speeds i have tested it and its better to undervolt higher clocks, i get better battery and performance!
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
For the 10th time Each phone reacts differently to Overclocking. There is no sure way to get it OC/Uv. On my phone past 1.2ghz i need to over volt.
prbassplayer said:
For the 10th time Each phone reacts differently to Overclocking. There is no sure way to get it OC/Uv. On my phone past 1.2ghz i need to over volt.
Click to expand...
Click to collapse
Well i ran 1.6 GHz undervolted at ever clock speed fine, had better performance than over volting, so its different
Sent from my Stock KH3/4 2.3.4 Captivate using the XDA Premium App!
Related
This is probably a stupid question but I'll ask it anyway. I've noticed my phone draining lately (or maybe it's not, I'm not quite sure what the battery life used to be xD), and I recently overclocked my phone to 1.25 GHz (my profile on SetCPU is ondemand), does overclocking affect the battery that much?
I run Froyo (rooted with wifi fix and the 1.25 GHz kernal)
I'm using an ultra low voltage kernal at 1ghz and haven't noticed a difference, if anything it seems like it's better.
I guess it probably largely depends on what kernal.
I've been overclocked for 4+ months. The first month before I rooted, I was getting around 16-18 hours on a full charge at the stock 550 speed. After I rooted, a lot depended on the rom (lesser so) and the kernel (more so). I think the best performance I got was on ChevyNo1's SS rom (2.1) with one of his kernels ... 40+ hours overclocked conservatively at 800. My first shot some time back with CyanogenMod got me 3 hours with the early Bekit kernels but the past several versions up through 5.0.8 I was getting about 30 hours clocked at 800 with a jdlfg kernel. Now on Froyo I'm getting close to 30 hours again conservatively at 800-1000 ... which on a 2.2. rom is more like 1200+ since its faster.
So, in short, my battery life has significantly improved while running faster than stock. But no 2 Droids are identical in terms of how a rom and/or kernel perform. With 2.1 roms my Droid seems to like jdlfg's kernels, while on 2.2 the P3droid kernels do good. But that's what I found out via a lot of trial and error, not anyone's post saying "You must try ______'s kernel (or rom) as its da bomb!"
I would like to include that the post above by "cvhovey" provides some valuable information that might interest you and suggest anyone untreated in this thread to read that post.
Using an application like SetCPU you can throttle down the processor speed when the screen is off, this reducing heat and gaining better battery life. This doesn't mean you will get better battery life if you use your phone all day and never turn the screen off. But is totally worth it because u feel like I'm getting awesome battery life, plus an amazingly fast phone because SetCPU will overall me to my personal preference of 1100mhz on demand.
The answer to your actual question depends on how well you set up your phone preferences according to what benefits you the most, and what method of adjusting processor speed. I only mentioned one here, there are mire ways than just an APK.
Sent from my Droid using XDA App
PetRiLJoe said:
Using an application like SetCPU ...
Click to expand...
Click to collapse
1+ on that. But how one uses SetCPU can also make big differences, such as which governor is selected. SetCPU at 400-1250 with the Performance governor will essentially run at its highest speed all of the time (if I'm correct), whereas with the Conservative governor will ramp up from 400 to 1250 at a slower pace, or at a faster face with Ondemand.
This thread can give you some helpful tips: Battery Saving Techniques - Theories in Test
Alright, thank you for your help ^^
i used SetCPU and my phone had continuously reboots...
I just had to uninstall it..
Were you using profiles in any way? A specific ROM? I've had similar a experience with certain ROMs (specifically UltimateDroid).
Best guess is that it just didn't play nice with the modded kernel.
Sent from my Droid using XDA App
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.
What are the benefits of OC/UV (particularly for CM7)?
I know of improved performance due to OC, but what does UV do in regards to performance. Also, how does an OC/UV kernel compare to one without the option?
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
xredjokerx said:
your processor doesn't need as much voltage as the stock settings--undervolting lets you save battery
personally i want to know.. do you have to UV to OC?
Click to expand...
Click to collapse
You can do either or both but don't have to do both. At some point UVing will cause a crash. Right before that point it can cause performance issues. See the link below for instructions on how to find an optimal UV level to maximize battery savings and performance.
http://forum.xda-developers.com/showpost.php?p=10936691&postcount=1102
OCing improves speed but can also cause stability issues. For a captivate this usually isn't a problem until you get past 1.2 ghz. After that, it depends on the kernel but I have yet to find a kernel that is completely stable past 1.2 ghz under stressful conditions. Samsung designed the processor to handle 1.2 ghz and in theory it can go up to at least 1.6.
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
venomio said:
Like everyone before me has said, OC will make your processor work more (which will eat up more battery, and send the temps a bit higher).
UV is a way to "fix" that problem by controlling the voltage used by each Mhz/Ghz range. The mini guide that QuarkGluonSoup posted is a great way to start off.
Most Captivates start have random errors past 1.2Ghz, but the highest I've seen (stable) are 1.4Ghz.
Click to expand...
Click to collapse
Odd as it sounds, my battery life on CM7 is close to 50% better when it is OC'ed to 1.2 ghz and UV'ed than it was on the froyo ROMs under the same conditions.
That really is odd :S I think I'll try it myself.
Cyanogen 8? Is this next? Or is this in the works? Also is 2.3.5 next and would it be numbered a different version when Ice Cream comes out? Also is anything coming from the devs to overclock to 800 yet?
cell2011 said:
Also is anything coming from the devs to overclock to 800 yet?
Click to expand...
Click to collapse
It's been done. So very very few phones are even stable at 800, and those that could generally performed worse in benches at 800 than at lower clocks. Many of these devices bootloop above 700.
Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.
Also, on a side note, this should not be in the Development section. This should be in general or Q&A
This belongs in Q&A for future reference.
CM8 will be next, obviously. It will be based on Ice Cream Sandwich, so no, it won't be in development until ICS is released to AOSP so that the CM team can start using that code. 2.3.5 is an update coming out soon for the Nexus S 4G that fixes wifi and network speed, as well as adding more secure NFC for Google Wallet. It won't really affect us when it is merged into CM7. ICS is expected to be Android 4.0, but it could be 3.5 if Google decides.
There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.
rizdog23 said:
Cyanogen 8 will not come out yet since will most likely be ice cream sandwich. I am not even sure is 2.3.5 will even come out and no the devs can not overclock this device to 800mhz because is 768 is the limit of the processor. Most people's phones do not even run that smoothly at 768 anyways. If somehow the dev found a way to overclock it to 800 (impossible btw but this is just a what if kind of statement) since the processor can not handle 800 it would just overheat the thing and cause crashes.
Click to expand...
Click to collapse
I lol'd at this statement. Did you not read any of the posts above you?
When i began to post there were no posts yet. They must have got posted while i was typing. So seeing as the only post at the time was the op, then yes i did read the post(s) above mine.....
There is a kernel that goes over 800Mhz, but anything over 768Mhz can be unstable on some phones. I tried it and there were no real performance gains, but battery life was a lot worse. Performance was actually worse at the highest CPU clock, in my experience. Just stick with 768Mhz. It's stable and chances are that you can get even better performance at a lower clock. I get better battery and performance at 633Mhz. It all depends on each unique phone.
Click to expand...
Click to collapse
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D
dastin1015 said:
I can confirm that the Godmode kernel was able to push some phones, such as mine, past 800Mhz. Although I had a faster processor speed, my battery would drain incredibly fast as well as overheat. Even though I never hit a bootloop with the kernel, the battery life, overheating, and loss of performance kept me away. Sacrificing too much for having a faster processor speed. Normally I overclock to about 729Mhz and have great battery life, speed and performance in conjunction with a min of 19Mhz and a smartass governor.
Sent from my Hero that never dies! ;D
Click to expand...
Click to collapse
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes
rizdog23 said:
Thanks. I am glad someone at least confirmed it. I never knew about the godmode kernel as ive only been here for a little bit. Sorry for misinformed post about their not being an 800mhz kernel. As I can see, i was wrong, but also I was correct in saying that the processor can not handle it....sometimes
Click to expand...
Click to collapse
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.
In before bierce gives birth over ANOTHER question being in the dev section
Sent from my Android using Tapatalk
rizdog23 said:
For some reason my phone never works well with higher clock speeds no matter what rom or kernel i use. I get my best results at 710-352 performance.
Click to expand...
Click to collapse
Correct me if I'm wrong, but from what I've noticed is that newer Hero's that were sold with Eclair as opposed to the original Donut, when I bought mine, are not able to reach those higher processor speeds past 691Mhz.
Sent from my Hero that never dies! ;D
i bought mine at radio shack back in september and it was still on 1.5 and ive never been able to get over 768mhz without it freezing and bootlooping its different with every hero.
i stay at 352-691 ondemand and thats plenty fast for me
Mine was running 1.5 also and it will run fine at 768 but battery life suffers so I usually run at 352/710 and battery and performance are good (depends on rom kernel)
Where can I get the godmode kernel ....
Sent from my HERO200 using XDA App
I actually got mine two weeks after it came out.....so i mean it could just be that this phone is dead now. I never had a refurb or anything. I got it wet once but it got repaired. I've only had this one the whole time. Do you think that is the issue?
rubyknight said:
Yup, I'm at 806 - 19 ondemand while posting this and I can already feel it slowing down a little. 729 - 19 on demand is my best setup. I've tested a lot with trying higher setups than that but so far 729 seems to be the best for battery life and performance on every rom I've ever tried
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks
chalan30 said:
Hey rubyknight,
just wondering why 19? Ive seen people do that but can the processor really ever do anything at 19? if so, doesnt it affect stuff like wake. Im trying it now just to see for myself. Ive been playing with a really high min value between 480 and 576 with the high at 748 and it actually doesnt only seems to affect battery life a little, both on the .29 and .35 kernels on jaybobs roms and on OMFGB.
Thanks
Click to expand...
Click to collapse
It depends on the cpu governor that you use.
nandroids are for
sissies
ch1naski said:
It depends on the cpu governor that you use.
nandroids are for
sissies
Click to expand...
Click to collapse
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.
chalan30 said:
so update, ive run it at 19/768 on demand all day and after 11hrs 13 min its at 60% thats not bad for my phone! and there was almost no performance difference. Just the slightest UI lag... this is on jaybobs 7/8 with the .29 kernel, with background data off. And my regular usage which is not a lot. but for me its good. i wish I had tried it ages ago.
Click to expand...
Click to collapse
I believe that you can set the ramp up frequency and that may help with the lag. Setcpu, advanced settings, I think?
nandroids are for
sissies
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