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?
Related
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!
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.
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.
Hi
Sorry cant post in the development thread since i just joined.
Using TS1700-GPUOC-4.1.2-mr1-fr-ALPHA12 with CM10 causes Nexus 7 to Freeze/crash and reboot when you remove a USB pen drive or 2.5 harddrive that is connected with a OTG cable. It happens if you do a dismount from settings/storage or just pull the cable OTG cable out.
Otherwise its a very good kernel for Nexus 7.
/cazrack
cazrack said:
Hi
Sorry cant post in the development thread since i just joined.
Using TS1700-GPUOC-4.1.2-mr1-fr-ALPHA12 with CM10 causes Nexus 7 to Freeze/crash and reboot when you remove a USB pen drive or 2.5 harddrive that is connected with a OTG cable. It happens if you do a dismount from settings/storage or just pull the cable OTG cable out.
Otherwise its a very good kernel for Nexus 7.
/cazrack
Click to expand...
Click to collapse
Finally! I could Kiss you!! I wont don't worry.... at least however a manly high five will do. I am having this issue since using the Trinity Kernel and like an idiot never once though it was the Kernel. Strange how the units will still turn off even if you just plug and unplug in the OTG cable with nothing plugged into the cable itself. So we think it is the Kernel then?
Casanub said:
Finally! I could Kiss you!! I wont don't worry.... at least however a manly high five will do. I am having this issue since using the Trinity Kernel and like an idiot never once though it was the Kernel. Strange how the units will still turn off even if you just plug and unplug in the OTG cable with nothing plugged into the cable itself. So we think it is the Kernel then?
Click to expand...
Click to collapse
Yes, 100% certain its kernel related.
When you run CM10 updater from inside CM10 and a new nightly build gets installed it removes Trinity kernel and install the default CM10 kernel and that makes the problem go away.
After you flash Trinity kernel back you get the freeze and crash/reboot issue again.
If you use this Kernel, please contact morfic. check his site below for email and other contact information.
derkernel.com
(sorry no real link, just joined.)
/cazrack
cazrack said:
Yes, 100% certain its kernel related.
When you run CM10 updater from inside CM10 and a new nightly build gets installed it removes Trinity kernel and install the default CM10 kernel and that makes the problem go away.
After you flash Trinity kernel back you get the freeze and crash/reboot issue again.
If you use this Kernel, please contact morfic. check his site below for email and other contact information.
derkernel.com
(sorry no real link, just joined.)
/cazrack
Click to expand...
Click to collapse
Thank you Cazrack. I will email him now, I can imagine he will be inundated with emails
Another two quick questions "sorry" with Trinity, do you use setcpu to overclock or do you find the kernel gives you all the speed you need? secondly have you had the issue of the unit turning off on an overnight charge? I do not do this normally but I fell asleep with it plugged in and found in the morning it was turned off, when I turned it on it was at 100% so thought is might have turned off as a safety feature but just wondering if you experienced this or heard of it happening?
Thank you again for you help.
The same thing happens to me with the Trinity kernel but it also happens with LeanKernel for 4.2. It did not happen with LeanKernel for 4.1.2, so I don't think it is just a kernel only issue. It doesn't happen on the stock kernel, M-Kernel+, or Franco r30.
O2Blevel said:
The same thing happens to me with the Trinity kernel but it also happens with LeanKernel for 4.2. It did not happen with LeanKernel for 4.1.2, so I don't think it is just a kernel only issue. It doesn't happen on the stock kernel, M-Kernel+, or Franco r30.
Click to expand...
Click to collapse
Cheers for the response, always good to know its not the hardware . Defo a Kernel issue, I have emailed derkernel.com, I am sure we should have a fix soon, otherwise it aint that much of a big issue.
Casanub said:
Thank you Cazrack. I will email him now, I can imagine he will be inundated with emails
Another two quick questions "sorry" with Trinity, do you use setcpu to overclock or do you find the kernel gives you all the speed you need? secondly have you had the issue of the unit turning off on an overnight charge? I do not do this normally but I fell asleep with it plugged in and found in the morning it was turned off, when I turned it on it was at 100% so thought is might have turned off as a safety feature but just wondering if you experienced this or heard of it happening?
Thank you again for you help.
Click to expand...
Click to collapse
I keep the stock clock speed 1.3 ghz but I use setcpu to set certain programs to scale to 1.7 ghz.
For example webbrowsers benefit from 1.7 ghz in faster loading and smoothness.
overclocking for games i prefer to run cpu stock and have my gpu overclocked to 600 mhz.
stock gpu is 416 or 418 mhz.
cant overc to much during long gaming sessions since it get to hot and gpu oc give more than cpu.
when i used franco kernel r25 the power off thing happend to me too.
only 1 night during charging but i flashed a new kernel after that.
/cazrack
cazrack said:
I keep the stock clock speed 1.3 ghz but I use setcpu to set certain programs to scale to 1.7 ghz.
For example webbrowsers benefit from 1.7 ghz in faster loading and smoothness.
overclocking for games i prefer to run cpu stock and have my gpu overclocked to 600 mhz.
stock gpu is 416 or 418 mhz.
cant overc to much during long gaming sessions since it get to hot and gpu oc give more than cpu.
when i used franco kernel r25 the power off thing happend to me too.
only 1 night during charging but i flashed a new kernel after that.
/cazrack
Click to expand...
Click to collapse
Ah I see I have done the same it works very well. However you mentioned overclocking the gpu to 600mhz how is this achieved? its not an option in setcpu, suppose the programe is called setgpu
I think I will stick with the the Trinity as the OTG restart is not that much of a issue really. I am sure derkernel will have an update soon.
Casanub said:
Ah I see I have done the same it works very well. However you mentioned overclocking the gpu to 600mhz how is this achieved? its not an option in setcpu, suppose the programe is called setgpu
I think I will stick with the the Trinity as the OTG restart is not that much of a issue really. I am sure derkernel will have an update soon.
Click to expand...
Click to collapse
yes you can OC the gpu for better gaming fps on some kernels.
for example Trinity kernel and Franco kernel allow this if you use franco.kernel.updater from google play store.
i have tested 700 mhz but but during long gaming sessions with games pushing the gpu hardware like spiderman it just get to hot.
484 and 520 mhz is considerd very safe from the information i gatherd.
600 should work even for longer gaming sessions but the device will be warmer.
650 i will test this but im sceptical about long gaming sessions.
750 some crazy people run this....
at the moment im using cpu gov ondemand in setcpu with value 50 in cpu scaling.
have you tried the elite kernel? 1.8 ghz cpu 650 mhz gpu..
/cazrack
cazrack said:
yes you can OC the gpu for better gaming fps on some kernels.
for example Trinity kernel and Franco kernel allow this if you use franco.kernel.updater from google play store.
i have tested 700 mhz but but during long gaming sessions with games pushing the gpu hardware like spiderman it just get to hot.
484 and 520 mhz is considerd very safe from the information i gatherd.
600 should work even for longer gaming sessions but the device will be warmer.
650 i will test this but im sceptical about long gaming sessions.
750 some crazy people run this....
at the moment im using cpu gov ondemand in setcpu with value 50 in cpu scaling.
have you tried the elite kernel? 1.8 ghz cpu 650 mhz gpu..
/cazrack
Click to expand...
Click to collapse
Okay I see it comes full circle, I will give it a bash.
The elite was going to be my next kernel... only reason for using Trinity was, I was advised to do so as a first try. It might be the next step to get rid of the OTG restart and of course the 650 mhz gpu stock oc. Have you tried it or going to try it?
Casanub said:
Okay I see it comes full circle, I will give it a bash.
The elite was going to be my next kernel... only reason for using Trinity was, I was advised to do so as a first try. It might be the next step to get rid of the OTG restart and of course the 650 mhz gpu stock oc. Have you tried it or going to try it?
Click to expand...
Click to collapse
is it supposed to work with cm10? ive tried to flash it but it didnt seem to flash in good
because trinity animation still showing after flash... but nexus isnt booting up.
no problem just boot into recovery and reflash trinity kernel or a cm10 rom.
any clue?
prehaps reflash elite when you have updated to a 100% cm10 nightly installed.
/cazrack
cazrack said:
is it supposed to work with cm10? ive tried to flash it but it didnt seem to flash in good
because trinity animation still showing after flash... but nexus isnt booting up.
no problem just boot into recovery and reflash trinity kernel or a cm10 rom.
any clue?
prehaps reflash elite when you have updated to a 100% cm10 nightly installed.
/cazrack
Click to expand...
Click to collapse
Sounds strange did you delete the cache? As I had that issue originally? I am just using stock ROM tbh as it seems to be the most responsive at the moment but I have not tried them all obviously
Suppose we best keep on keeping and seeing if the smart devas can release a fix.
Casanub said:
Sounds strange did you delete the cache? As I had that issue originally? I am just using stock ROM tbh as it seems to be the most responsive at the moment but I have not tried them all obviously
Suppose we best keep on keeping and seeing if the smart devas can release a fix.
Click to expand...
Click to collapse
I think i did, but i will try again. Could be that extreme kernel is not compatible with cm10?
I would like to try to OC cpu even more up to 2 ghz would be intresting but i dont think there is such a kernel to download.
Once i reach 10 posts ill post in XDA Trinity developer thread
/cazrack.