Ok, so i was super excited to hear that we are finally able to overclock, been waiting to do this since i picked up this phone and put down my OG Evo.. anyways, i tried Dread 7us's app Overclock v1.0, and installed it, pulled up Setcpu and i can see but it doesnt stick.. i pull up quadrant and look at system information. the max freq is set at my desired freq (1809MHz) but the actual never goes above 1512MHz. i go back into Setcpu and it says the same thing, max is 1809 but it doesnt go over 1512.
so i thought it could be the rom, i was on Rejuv 1.5, so i switched to OMJ 1.1 and same thing. Then Overclock v1.1 came out and i tried that with no luck, doesnt stick.
Then MeanRom 1.0 came out, and my phone hasnt really liked this rom but i wanted to see how it would do with the OC built into the rom at 1.72GHz. I get it all set up and go into quadrant and check my settings and the same thing, it shows max at 1.7GHz but my actual never goes higher than 1.5, even my quadrant scores do not change
i dont think im the only one having issues, i have heard of a few others having issues with it sticking, and the ones who think it is and post up quadrant scores of 5000-5200, my phone is doing that without being OC'd..
i have rooted many phones and flashed 100's of times, but havent ran into this before. Anybody got any idea's as to why this may be happening or any ideas i can try to see if it will stick
thanks for the help guys
Just wondering where your checking the frequencies.
Sent from my EVO using xda app-developers app
Like I stated in the OP, I used Setcpu and quadrant
Sent from my Supercharged ELiTE
harvickgm said:
Ok, so i was super excited to hear that we are finally able to overclock, been waiting to do this since i picked up this phone and put down my OG Evo.. anyways, i tried Dread 7us's app Overclock v1.0, and installed it, pulled up Setcpu and i can see but it doesnt stick.. i pull up quadrant and look at system information. the max freq is set at my desired freq (1809MHz) but the actual never goes above 1512MHz. i go back into Setcpu and it says the same thing, max is 1809 but it doesnt go over 1512.
so i thought it could be the rom, i was on Rejuv 1.5, so i switched to OMJ 1.1 and same thing. Then Overclock v1.1 came out and i tried that with no luck, doesnt stick.
Then MeanRom 1.0 came out, and my phone hasnt really liked this rom but i wanted to see how it would do with the OC built into the rom at 1.72GHz. I get it all set up and go into quadrant and check my settings and the same thing, it shows max at 1.7GHz but my actual never goes higher than 1.5, even my quadrant scores do not change
i dont think im the only one having issues, i have heard of a few others having issues with it sticking, and the ones who think it is and post up quadrant scores of 5000-5200, my phone is doing that without being OC'd..
i have rooted many phones and flashed 100's of times, but havent ran into this before. Anybody got any idea's as to why this may be happening or any ideas i can try to see if it will stick
thanks for the help guys
Click to expand...
Click to collapse
You stated that setcpu was used for verification. You have to use setcpu to set clock speed also. Dread7us' apk is kind of like setting the threshold max, so you can use a 3rd party app (setcpu) to OC. Hth.
Yes I know that.. and that's what I have done, but it does not stay. The max freq will say 1809 but the ACTUAL FREQ will never go above 1512 which is stock. This is what I'm trying to figure out and why
Sent from my Supercharged ELiTE
Here is a screenshot of what I saw when I opened Setcpu back up.
Sent from my Supercharged ELiTE
I had the same issue when I tried the OC... I checked in SetCPU, Quadrant, and System Monitor with the governor set to performance. Clock speed stayed at 1500MHz no matter what.
I uninstalled the OC APK and am just sticking with stock until we can get some proper kernels out. The stock speed is fast enough for everything I want to do realistically.
I had the same exact problem and run fresh rom. It would stick for normal use but as soon as I ran a benchmark it dropped to 1.5 again.
i had to install mine to internal memory. by default it went to phone. set it to internal you should be fine.
kaos420 said:
i had to install mine to internal memory. by default it went to phone. set it to internal you should be fine.
Click to expand...
Click to collapse
What did you install in internal memory?? Please explain what exactly it is what you did.
Maybe u can help us all figure this out
Thanks a lot man
Sent from my Supercharged ELiTE
harvickgm said:
What did you install in internal memory?? Please explain what exactly it is what you did.
Maybe u can help us all figure this out
Thanks a lot man
Sent from my Supercharged ELiTE
Click to expand...
Click to collapse
The oc program script. Wouldnt work till i installed to internal. Same for. Setcpu
Sent from my ice cream powered Evo Lte!
kaos420 said:
The oc program script. Wouldnt work till i installed to internal. Same for. Setcpu
Sent from my ice cream powered Evo Lte!
Click to expand...
Click to collapse
you mean installing the apps themselves on the internal memory and not the SD card. right? well i never install my apps on my SD card, so thats not the issue
It is when . They auto default to phone storage. Move them to internal like i said.
Sent from my ice cream powered Evo Lte!
I used the OC app in the original overclock mod post, installed setcpu, and then turned it up from there. I am using MeanRom. Not sure if anyone else has stated but you have to remember to set up in the OC app
Sent from my EVO 4G LTE using XDA-Developer App
Sent from my EVO 4G LTE using XDA-Developer App
EVOMIKE025 said:
Sent from my EVO 4G LTE using XDA-Developer App
Click to expand...
Click to collapse
ok, open quadrant and look at ur freq under system information. and look and see what ur actual freq stays at?
Related
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
xsalientx said:
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
Click to expand...
Click to collapse
setcpu is the only and the best overclocking app. If u want to be able to overclock ur phone us have to flash jt1134s 1.2ghz voodoo kernel then use can use setcpu to overclock to 1.2ghz!
sent from my fascinate rooted and ocl'd to 1.2ghz with voodoo
xsalientx said:
Hello everyone, I just had one quick question (I'm also very new to Android in general so I don't want to do anything to make my phone un-useable). Does Setcpu work with samsung fascinate root and clockwork mod? I heard some people say theres a seperate application to underclock and overclock the fascinate, but then again i do not think they knew what they were talking about. Is there a better program than setcpu?
Sorry if this has already been posted. I know its been posted in other forums for different phones, but didn't find one for the fascinate.
Click to expand...
Click to collapse
SetCPU is the most popular one. You'll need root to even use SetCPU. And you'll need CWM to flash the OC Kernels. If you dont OC SetCPU is pointless
On that note.
SetCPU must be ran on conservative and with no profiles and no load on boot.
If you do reboot your phone, mine reverts back to 800, so I need to manually change it to 1200.
Do u have to set both min & Max to 1200???
no just the max
Sent from my LV-Voodoo Fascinate using XDA App
saps said:
SetCPU is the most popular one. You'll need root to even use SetCPU. And you'll need CWM to flash the OC Kernels. If you dont OC SetCPU is pointless
Click to expand...
Click to collapse
Not pointless. You can always underclock to spare your battery life
Sent from my SCH-I500 using XDA App
jt1134 said:
Not pointless. You can always underclock to spare your battery life
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Yes, of course you are right. Actually the other day I forgot to slide sliders up from 800 to 1200 and I was getting really good battery life for like 2 hours my % only dropped 1% and I was like wow.
Im just pleased as punch that there are OC/UV kernels out, its the best of both worlds.
Actually my battery life is above average it seems; either that or my usage is below average so Im not draining it as much. I'd gladly mildly overvolt to something like 1350mV if it meant I'd be rock solid stable at say 1.4Ghz
BTW, jt I heard you might be getting out the kernel speed chase after these 1.2Ghz's? Just don't feel like chasing 1.3 or 1.4?
I am running Dirrk's D012 LV 1200 Kernel with SetCPU
Luckily, the LV runs EXTREMELY smooth on my phone..
So smooth, that for the past day now I have been able to run with "set on boot" and constant restarts on my phone..and with Profiles for Screen Off, Temp (probably wont get there), and Charging. I can say that I have had no problems with my profiles and set on boot. Then again, I don't want to contribute to hurting anyone's phone
Just thought I'd let everyone know how my phone (and potentially others) can seem to handle profiles and set on boot.
johnz1 said:
I am running Dirrk's D012 LV 1200 Kernel with SetCPU
Luckily, the LV runs EXTREMELY smooth on my phone..
So smooth, that for the past day now I have been able to run with "set on boot" and constant restarts on my phone..and with Profiles for Screen Off, Temp (probably wont get there), and Charging. I can say that I have had no problems with my profiles and set on boot. Then again, I don't want to contribute to hurting anyone's phone
Just thought I'd let everyone know how my phone (and potentially others) can seem to handle profiles and set on boot.
Click to expand...
Click to collapse
No problems with set on boot here either. I keep it on.
so how do i use setcpu/what are the steps i need to take?
xsalientx said:
so how do i use setcpu/what are the steps i need to take?
Click to expand...
Click to collapse
Install it, tell it to auto detect, set the max where you want, leave the min at 100, and then leave it alone.
Sent from my SCH-I500 using XDA App
I was hoping to get some help. I have installed jt's 1200 voodoo kernal, and I can't seem to get Setcpu to clock at 1200. It still says that the max is 800, however, on the slide it is only giving me the option to goto 528. Bellow are my facts, any help would be great!
Facts:
1. flashed jt's overclocked voodoo use clockwork, but did it through "install ROM from sd card". I am not sure if this is correct, but it seems to be running voodoo.
2. I have no idea how I need to have Setcpu set up.
I feel like I am blindfolded and I am trying to wack at a pinata.
thanks.
Edit: never mind...even a blind folded monkey hits the pinata every now and then
I tested it once and I'm losing 4% per hour. Its 800-200 on demand as main, screen off at 500-200 and less than 50% battery also at 500-200.
I haven't toyed around with different kernels, I'm using the kernal that came with Zedomax's root instructions. Also, 200, 500, 800, 1000 and 1200 are my only options, this is because of the kernel that I'm using correct?
In your experience is -4%/hour average or does it seem like SetCPU is working? 500-200 is the lowest I can go otherwise it would be 200-200.
Thanks
Sent from my SAMSUNG-SGH-I777 using xda premium
Sounds like you have some apps or widgets draining your battery. I've overclocked mine to 1.6 and get less than 1%/hr drain on idle.
First off, what rom are you running. Try unnamed or serendipity. Don't do the 50% or less at 500-200 its gonna slow you down. Also switching to entropys daily driver should net you an improvement. Also try out the conservative governor. Its just as good as ondemand but with better battery.
Sent from my SAMSUNG-SGH-I777 using XDA App
I am running stock ROM. Should I bump the 50% up to 800-200? I don't have many options with this kernel/rom.
Im still new to this process as well
CollegeProfesor said:
I am running stock ROM. Should I bump the 50% up to 800-200? I don't have many options with this kernel/rom.
Im still new to this process as well
Click to expand...
Click to collapse
800 should be fine for most things, only adds a tiny bit of lag to paging around the apps and home screens. I just benchmarked mine at 800 and got a 2721 on Quadrant, which is only ~500 less than what I got at 1200mhz on stock.
Also, I was wondering, is the issue with screen-off speeds below 500mhz still around? I have mine at 200-1600 conservative and I haven't had any issues yet.
Thanks. I flashed UnNamed and now I can finally overclock, but SetCPU won't allow me to set my main to conservative. Ive tried it multiple times and re-booted as well.
I also want to undervolt, I've reduced each one by 50, thoughts? Is this too little?
Thanks again, im trying to get the hang of this
CollegeProfesor said:
Thanks. I flashed UnNamed and now I can finally overclock, but SetCPU won't allow me to set my main to conservative. Ive tried it multiple times and re-booted as well.
I also want to undervolt, I've reduced each one by 50, thoughts?
Click to expand...
Click to collapse
Is it giving a error could be the new kernel didn't flash. Go to entropy's thread download the newest version and flash via CWM. See what it does then.
nh5 said:
Is it giving a error could be the new kernel didn't flash. Go to entropy's thread download the newest version and flash via CWM. See what it does then.
Click to expand...
Click to collapse
Nevermind, it worked. SetCPU was just using a different governor for a profile that I set.
Im running liquid gingerbread v3.0 and no matter what I do if I change the processed speed while it boots up over 1.42 it locks completely up and I have to do a battery pull and sometimes if I boot up above 1.42 it locks up randomly anyways I've tried a wipe and I tried a different kernal imoseyen 6.2.1 I believe im gonna try one more kernal and will update the results but I don't have much hope
Sent from my HTC ThunderBolt using XDA App
hunterjackson92 said:
Im running liquid gingerbread v3.0 and no matter what I do if I change the processed speed while it boots up over 1.42 it locks completely up and I have to do a battery pull and sometimes if I boot up above 1.42 it locks up randomly anyways I've tried a wipe and I tried a different kernal imoseyen 6.2.1 I believe im gonna try one more kernal and will update the results but I don't have much hope
Sent from my HTC ThunderBolt using XDA App
Click to expand...
Click to collapse
Some phones can't handle OC'ing. Yours may be one of those.
madzozs said:
Some phones can't handle OC'ing. Yours may be one of those.
Click to expand...
Click to collapse
this is correct... i can clock mine up to ~1700 no problems, untill the screen goes to sleep and then all goes south if i keep it under 1400 its all good. but honestly there is no point to going over 12-1300 benchmark results are neglegably improved and you are killing your battery and running the risk of burning up your equipment.
Each ThunderBolt handles overclocking differently as mentioned above. The expansion and contraction of the metal and other materials when heating and cooling vary from device to device, so one thunderbolt might be able to get up to 1.7GHz, and another might not be able to handle 1.2GHz.
Also, as mentioned above, clocking over 1.2GHz is really pointless. I honestly never overclock my phone. No need in my opinion.
Like mentioned above I really see no need to go above 1.4, but if you wanted you could always raise the voltage on those higher frequencies so it wouldnt lock up.
Thank you guys it isn't really that I want or need to go over 1.4 and I rarely ever do it is more me being a perfectionist. But its strange Ive had liquid before on here and it always ran five and I usually left it at 1.5 and it never really started acting weird till about 1.8 and it was the same version v3.0.
*Edit* just out of curiousity I booted up and older recovery of liquid 3.0 with the stock kernal and it ran up 1.8 fine?
Sent from my HTC ThunderBolt using XDA App
Different roms run different kernels/versions of kernels, which in turn use different voltages. If a kernel was undervolted, its less likely to handle higher speeds.
Sent from my HTC Thunderbolt powered by KillaSense 3.5.0
Are you clocking that high just to do it?? In reality I just use smartass v2 and clock at 1222 and it stays snappy and doesn't demolish my battery...
Sent from Shift Ao5p ic3 overclocked unlocked and ready to rock.
I must be a lucky one. I overclock to 1.7 and my phone runs super stable.
Sent from my ADR6400L using XDA App
That's the thing though it's the exact same rom liquid gingerbread v3.0 with the stock kernal I can go up to 1.8 before it gives me any problems and even then it just acts weird
Sent from my HTC ThunderBolt using XDA App
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Actually when I was on the second ics leak, and setcpu worked fine. I know this because I benchmarked before and after setting frequencies
Sent from my ADR6425LVW using XDA
benchmarking doesn't mean it wasn't running at full tilt when you didn't need it to. unless your kernel magically doesn't include perflock, it was.
also, there are some combinations of setcpu and monitoring that will work. at one point if i used setcpu, cpu monitor, and one other which i forget now, it would work, kind of. definitely not recommended.
Thats why I deaded mine. Phone was constantly overheating
Sent from my ADR6425LVW using xda premium
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
tspderek said:
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
Click to expand...
Click to collapse
Agreed. I had set CPU try to disable perflock and limit to 1200mhz on conservative and it ended up being worse battery and slower overall.
You're exactly right I advise everyone I discuss the topic with to make sure and avoid trying to over ride perflock with a CPU management app. It causes a conflict in my opinion which is a huge battery drain and also causes excessive heat due to the process of fighting for its life.
Sent from my ADR6425LVW using xda premium
I've been saying this I even started a thread to smash this rumor of ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels.
THERE WAS NEVER ANYTHING WRONG WITH ANY ICS LEAKS. JUST USER FAULT
Sent from my ADR6425LVW using XDA
richii0207 said:
I've been saying this I even started a thread to smash this rumor if ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
con247 said:
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
Click to expand...
Click to collapse
My favorite part is when they try to sound like a dev, I guess everyone's a dev on here ;-P. At least I only say something I know from EXPERIENCE and not what I read ;-)
Sent from my ADR6425LVW using XDA
jayochs said:
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
Click to expand...
Click to collapse
the widget i posted is what you want. it should be scaling up and down, and settling eventually when nothing is really going on. the system panel that you tried clearly affected the perflock in some way. from what i understand, some apps/widgets look at the cpu itself, while others hit up the kernel for status. the ones that hit up the kernel are the issue. i'm not 100% on this, that's just what i've been told. all i know is my experience seems to match this.
tspderek said:
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Click to expand...
Click to collapse
Hmm, that's weird, cause I've been using setCPU with ICS on the Rezound for months and it works great! My CPU scales fine and hits all the frequencies its supposed to. The min and max frequencies do change around seemingly randomly, but anyone can see by watching the current frequency display that it is always somewhere in between the range I selected, and always appropriate for the system load.
I've always had CPU Master installed. I just removed it, we'll see how it goes.
I Have the MeanBean and when I overclock and undervolt it works ok for a wile but after about 2 or 3 hours it will reboot untill I have rebooted it myself then its ok for a wile. I have tried to run as normal volt with overclock and same thing happens but if I overvolt and overclock to the 1.7 it runs ok. When I was on meanbean 2.8 the overclock was built into the rom. can someone tell me why this is and what I can do to get it stable and how far I can go with the overclock and voltage.
It's actually varies, some phones can't oc at all, some can only to 1.8 and some can go all the way to 2.1. Same goes for voltage. It's best to see how your phone reacts to each. So if 1.7 works for you then that might be your phones limit.
Sent from my EVO using Tapatalk 2
jdmohn12 said:
I Have the MeanBean and when I overclock and undervolt it works ok for a wile but after about 2 or 3 hours it will reboot untill I have rebooted it myself then its ok for a wile. I have tried to run as normal volt with overclock and same thing happens but if I overvolt and overclock to the 1.7 it runs ok. When I was on meanbean 2.8 the overclock was built into the rom. can someone tell me why this is and what I can do to get it stable and how far I can go with the overclock and voltage.
Click to expand...
Click to collapse
Each phone is different. Some phones handle overclocking/underclocking and over/undervolting better than others. What works for one may not work for the other. Find the setup that best suits your needs and stick with it.
The advice is free....the bandwidth, not so much
will this all change with the rom that I am using or is this all just in the phone? when I was on meanROM it was overclocked to 1.890 and it ran great, now I am not sure if I can get back to that or not. not tried it yet, going to see what happens after a day or two then try going up from there.
jdmohn12 said:
will this all change with the rom that I am using or is this all just in the phone? when I was on meanROM it was overclocked to 1.890 and it ran great, now I am not sure if I can get back to that or not. not tried it yet, going to see what happens after a day or two then try going up from there.
Click to expand...
Click to collapse
Well it could be the kernel used for now. Since htc has not released source, mean bean is using a hacked stock kernel. When you were on mean rom the oc and and voltage tables where written into the actual kernel source. Until htc releases the source that can not be done.
Sent from my EVO using Tapatalk 2
I think some of the variables affecting how the phone runs has to do not only with the phone itself but the ROM, also. When I was on ICS I ran Viper4G with a custom kernel OC'd to 1.9 and my phone ran without a hitch. I haven't been able to do the same since I've been on JB. Having said that, keep in mind that the kernel source for JB hasn't been released yet (as stated above). Once the source drops you'll see improvements in the kernels and how the phone runs overall
The advice is free....the bandwidth, not so much
and as we all know there is no telling when they will release that code. Thank you for the quick answers. I will see what happens in the next day or two.