Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Jeff5886 said:
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Click to expand...
Click to collapse
Well the 3rd I/O test does take the longest to complete. If you are having I/O issues this certainly would give you a fluctuating Quadrant score since so much is I/O affected especially on a voodoo'd SF. Have your other benchmarks taken a dip as well? Does the phone lag in regular use? If its just a Quadrant issue I would not overly panic. Cross check with other benches
My phone did that with voodoo too, I installed dirrks lv 1200, and when I upgraded it started acting up. I did remove the fix before I updated, did everything right, but it still lagged so I just glassed back to stock and did all the steps for remove lagfix. Still on stock kernel now but will install birdman optimized tonight.
Adrynalyne is the man BTW. Ok, as to the OP, have you reset the CPU in SetCPU after you restart your phone? If I don't, I get a score of 1400 ish too.
that would make sense as I believe it resets to 800 instead of 1200
thestigwins said:
that would make sense as I believe it resets to 800 instead of 1200
Click to expand...
Click to collapse
Yes, it resets to 800. 1.2 ghz is nice, I would like to see 1.6. G2 OC'ed at 1450 I believe... Ugh, one day, one day.
No luck with OC kernels
I have tried a few, everytime I get issues. Seems like setcpu just does not play well with this phone. I get 1800 on stock voodoo .2. Don't see a need for the extra conservative 200mhz that an OC can provide. Good luck with the kernels though.
Anyways, as stated, make sure set CPU is set to 1.2 GHz and not 800 MHz which is where it defaults. I use the widgit and crank up the speed any time I'm using the phone, else, I leave it at 800 when charging / idle etc.
Also, go into System Panel (best app killer around) and do an END ALL - it will kill everything... THAN run quadrant. If your scores skyrocket, don't be alarmed. Quadrant likes to have a very clean system to run on, if you have a lot of cached or running applications, Quadrant seems to suffer, I'm assuming due to the delay between it requesting more RAM from Android and the time it takes for it to release it. Seems to make sense as to why it would slow down to me at least based on what I know about how Android handles RAM.
Just make sure to reboot your phone after to restore your normal app library of running apps.
With a 1.2 GHz overclock on jt's voodoo kernel most of us are/were getting about 1925 . I've not ran dirrk's LV kernel, the undervolting is very minimal and I'd rather error on the side of stability, YMMV.
Accused: Everyone flaming & veering off-topic (You know who you are)
Charge: Violation of XDA Anti Spamming, Trolling & Flaming Rules
Verdict: GUILTY
Resolution: All violating posts have been deleted
Warning: Further transgressions might result in a BAN!
COURT'S ADJOURNED!
Related
After trying out all the 1200 and the 1250 kernels, my phone just doesnt like them while using setcpu. With Setcpu set at performance and maxed out at 1200 my phone will run for a little bit and then lock up. If I try to run a quadrant it will freeze up when the immage starts to walk up the steps to the blue room requiring a battery pull. I am currently running an 1100 kernel that is stable on my phone but would like to run 1200 or even higher as 2.2 comes out and newer kernels are released. Is anyone else having a problem running above 1100? I'm still within my 30 day window and could easly take it back and get another phone, but in reality there is nothing wrong with the one I have, I just want it to run faster (than intended) so would I be wrong in taking it back to get a new one that will run at 1200 or higher? Thanks.
You should be running in conservative mode in setcpu regardless of the kernel...should fix your problem...
Sent from my rooted 1.2 voodoo Fascinate
vecchioni27 said:
You should be running in conservative mode in setcpu regardless of the kernel...should fix your problem...
Sent from my rooted 1.2 voodoo Fascinate
Click to expand...
Click to collapse
Why is that? I always ran performance on my Incredible without a problem. Granted, I realize that this is a different phone/processor. Wouldn't Conservitive keep the processor from max performance?
No, it will rev up the processor when you need it. I don't know if this will stop your phone from freezing while it's being taxed hard @ 1200 though ie Quadrant
Some people can run 1250, some have to stick to stock speed. I think it's mostly luck.
I think its because of all the different hardware they put into this phone to pump it out. Ontop of that the kernel code was not complete that samsung released.
Sent from my SCH-I500 using XDA App
I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2
gkallivrousis said:
I just downloaded Jrummy's Overclocker and i was wondering what are some settings for a safe overclock. im shooting for 1.2
Click to expand...
Click to collapse
1.2 should be no problem although all phones are different. start with the low voltage at 1.1 make sure the phone is stable. a quick test is to open the browser and load a few pages. a GOOD test is to run quadrant. then just increase the speed until it locks up. pull the battery and set it down 1 or 2 speeds and thats your max stable overclock at that voltage. most people are able to run 1.2 or 1.3 with no issues. i can run at 1.3 with no issues. any higher and after a few days (or less respectively) my phone hangs. Also increasing voltage will yield higher clocks but will drain the battery faster. just play around if the phone locks up just pull the battery. also i would not play with the manual settings until you are familiar with the basic ones first.
I am most stable at 1.25ghz LV. Currently running GummyJAR2.5 with Blueberry Theme.
No issues. I would recomend installing AutoKiller. This is not same as Task Killer. It frees up memory. Same function as the one that comes with Jrummy Overclock but you can customize it more.
auto killer waste battery we have plenty of memory on our phones
so what do you recommend for a jrummy oc? i was thinkin 1.2 on lv
I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.
friguy3 said:
I can only get up to Low volt 1.15 otherwise. Once I click on anything higher i get a MAJOR hanging as soon as its done overclocking. pissed but guess thats just the point that all phones are different.
Click to expand...
Click to collapse
yup...some people can run 1.4 with no problems...try upping the voltage a little
1loudsvt said:
auto killer waste battery we have plenty of memory on our phones
Click to expand...
Click to collapse
I wasn't a believer until I installed it. My ram use to run low and some times made my DX run slow. Since installing the autokiller, my DX runs smoother, zippier and consistant. I have mine pre-set at extream. As for the battery, I don't notice any difference and I am semi heavy user. I been running Autokiller for a while.
Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel
I could never get over 1.1 using jrummy untill I changed the gov, use anything but "on demand" and I can get 1.4 all day. The stock settings work well using the "performance" gov but battery life can suffer if you get crazy. Performance keeps it running at top speed all the time. Hope this helps.
Sent from my DROIDX using XDA App
Droid-Xer said:
Hey guys, I recommend using QuickClock Advanced for some real battery savings. It calculates the lowest stable vsel your cpu can handle and then you can overclock from there.
my settings
300mhz 15vsel
600mhz 30vsel
900mhz 45vsel
1200mhz 61vsel
Click to expand...
Click to collapse
Ive used similar settings and worked fine on my phone running Rubix.
Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??
mike21pr said:
Im getting kinda fustrated here... i tried CM7 and currently on Ice Glacier and im having a problem where when i try to overclock my phone (even if its not so high) it gets frozen and needs a battery pull... i know that some cpu's cant handle frequencies like 1.8ghz, but even at 1.2 / 1.3 / 1.4 etc. i still get it. I switched from smartass, ondemand, and other governers and still freezes... any advice? Or am i stuck with the weakest link??
Click to expand...
Click to collapse
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel
Freek91 said:
have you tried flashing another kernel?...maybe another Faux kernel on low voltage or maybe try Grankin v.05 kernel
Click to expand...
Click to collapse
im using faux right now. ill see if i can find another one thats good to try out
thnx
i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board
mike21pr said:
i always thought that stock voltage was the more stable of the two since thats why i flashed it first when i had this issue... Anyways, tried faux low voltage and cranked it up to 1.8ghz to see how it goes. PLayed around with it so see no freezing yet. but performance was pretty much the same so i tried quadrant and see... i get an average of 1600 so thats pretty low IMO. As soon as i change to ondemand governor... it froze
back to the drawing board
Click to expand...
Click to collapse
well like im sure you've seen or heard...all hardware is different
so while 1.8ghz maybe slow...going down to 1.5 maybe quick and the opposite maybe true for someone elses phone...they may just totally fly at 1.8 while they grind to a halt at 1.5
so keep messing with it and see what happens...change clock speeds...change up the governors...just dont OC it to 1.8 and think the phone will magicly hit a 4100 quadrant and not have any issues
worse case...flash a different kernel and see how it acts
also on that topic...you said you were running IG...did you run the stock kernel for any length of time? did you try and OC that one?
Is it just my phone that seems to run as smooth or smoother in real world use at the undervolted 1ghz setting? I haven't seen any difference in opening apps and when playing Mega Jump it stutters at 1.2ghz just as much if not more than 1.0ghz. I'm not complaining in the least as my e-peen has no relation to the speed of my phone. The undervolting is also an added bonus of running the 1ghz setting. Coupled with Juice Defender and a few battery concious settings my phone is lasting crazy long. I'm running Bonsai's stock Genocide kernel at 1ghz conservative. When I was on ACS I think 1.2ghz my have been a bit smoother.
Yes i believe its just the kernels that are out right now...
i think they recommend 1000-1200 IF you want to OC but im not sure
As Randy pointed out in one of the Bonsai threads, much more battery is saved by lower operating freqs than by undervolting... 1000-1200 will drain the battery faster than 200-1200, even with the undervolt at 1000.
Sent from my mind using telepathitalk
I swear no one ever takes the time to fully read my posts on this forum :facepalm
stir fry a lot said:
I swear no one ever takes the time to fully read my posts on this forum :facepalm
Click to expand...
Click to collapse
I have noticed just the opposite of your OP. Running at 1000 I find that some of my games are a tad choppy at times. Going up to 1200 and they are smooth.
To be completely honest, I run at 100-800MHz on the SFR rom, no hiccups or lag differences between 800MHz and 1000MHz that I can tell, so why not run it at 800MHz.
what are your OC scaling?
Ondemand or Conservative?
100-1ghz Conservative (as recommended in the Genocide thread)
100-1.2ghz On Demand when I was running ACS.
I have personally found that setcpu is my phones nemesis. I get waaaaay better battery life and crazy better performance running genocide 0.2a 100-1200 "stock" than running any combination of settings / parameters, other versons of same kernel, or even another kernel for that matter.
Seven Sisters EPIC using XDA App
Bonsai rom uses genocide kernel? I thought it was it's own custom kernel, I'm on bonsai 3.0.1 with the bonsai 3.0.0 kernel and gpu performance is much improved over stock, running @ 1.2Ghz and much improved battery life over stock eb13.
Its an optimized version of Genocide from my understanding
I have personally found that setcpu is my phones nemesis. I get waaaaay better battery life and crazy better performance running genocide 0.2a 100-1200 "stock" than running any combination of settings / parameters, other versons of same kernel, or even another kernel for that matter.
Click to expand...
Click to collapse
I set it to 1.2ghz and deleted SetCPU. My phone is flying now. Thanks for the advice.
stir fry a lot said:
Its an optimized version of Genocide from my understanding
Click to expand...
Click to collapse
Ok, I've never read that anywhere before and my first thought was.....you switched out the kernel for genocide and thus caused your own performance issues.
No bonsai is not the same as the genocide kernel at all. Its their own kernel that they made.
Sent From My Evo Killer!
Well in that case I'm running the Bonsai kernel.
I am running the Twilight Zone kernel, and have it set at 200-1000 with ondemand
My battery life has been AWESOME, and the I have noticed no lack of response in anything I have run
stir fry a lot said:
I set it to 1.2ghz and deleted SetCPU. My phone is flying now. Thanks for the advice.
Click to expand...
Click to collapse
Apologies in advance if I misinterpreted your statement (it's a bit ambiguous).
If you set it in SetCPU, then got rid of SetCPU, the change will not stick. Any settings done through SetCPU do not make permanent changes to startup scripts, but are instead applied by the SetCPU application. To make them persist, the "Set on boot" checkbox must be checked, and when this is the case, SetCPU simply does its thing quietly in the background as a service.
If, instead, you modified startup scripts to set CPU speed and governor, well, then, never mind
dwallersv said:
Apologies in advance if I misinterpreted your statement (it's a bit ambiguous).
If you set it in SetCPU, then got rid of SetCPU, the change will not stick. Any settings done through SetCPU do not make permanent changes to startup scripts, but are instead applied by the SetCPU application. To make them persist, the "Set on boot" checkbox must be checked, and when this is the case, SetCPU simply does its thing quietly in the background as a service.
If, instead, you modified startup scripts to set CPU speed and governor, well, then, never mind
Click to expand...
Click to collapse
No, I got you. I've heard of people changing scripts in lieu of SetCPU. I just had read somewhere by one of the devs that if you set it to the 1ghz setting and remove SetCPU that the undervolting would stick. I though it would be the same for clocking. Either way my phone seems t be running very smooth without it so I'm ok with that.
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
GSF1200S said:
I dont have enough posts, and im not going to post a bunch of useless replies to threads im not interested in to inflate my post count to 10 posts. However, since ive encountered a fairly bad bug with this kernel, I figured id mention it here and see if an "expert" user might be able to guide/teach me what im missing, OR post in the Samurai kernel thread so the devs know its a problem.
Running the samurai kernel included with ACS ICS 5.5 (Samurai 3.0.1), i setup Voltage Control to use the Noop scheduler and Conservative governor. I disabled everything beyond 1000Mhz (for max battery life), and it worked as expected (100-1000mhz depending on what im doing). After flashing 3.0.4, it would no longer go above 800mhz. I ensured the max frequency was set to 1000mhz, applied changes, saved as boot settings, etc, and upon reboot the phone INITIALLY goes up to 1000mhz, but then stops at 800mhz. I noticed in voltage control I couldnt undervolt anything above 800 (all other frequencies disabled). Flashing back to 3.0.1, everything worked as advertised with all frequencies working well. BTW, to test, I changed schedulers and even set the governor to Performance, which maxed the frequency at 800mhz still.
Just thought id let some people in here know- I LOVED how well the ram optimization worked in 3.0.4- it reliably kept my RAM at about 170mb, whereas my RAM would eventually end up in the 70s with other choices.
Love the ROMS, kernels, and all the hacks you guys do; just wanted to let everyone know I noticed this.
Click to expand...
Click to collapse
Did you try reflashing fresh? I'm currently runnin CK23's Urban Precision 1.1 with Samurai 3.0.4 and I'm OC'd to 1400/200. I honestly don't kno why its not working for you, I'll be sure ta mention it in the thread tho.
Sent from a Epic like no other usin XDA Premium....
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
kennyglass123 said:
Did you reflash your ROM fresh and put on the kernel immediately like Earthbound recommended?
Click to expand...
Click to collapse
Yes, Ive done it a third time just to make sure; 100% reproducible with 3.0.4. The first 2 times I booted ACS ICS 5.5 FIRST, then booted back into CWM to flash the kernel. This last time, I flashed the ROM, then flashed the kernel immediately after. Same result. I guess its just my device? Ive never had issues with this before, so..
Did you clear data in Voltage Control? Perhaps it's your governor.