Am I doing something wrong? No matter what I do. I cannot get setcpu to cap at 1200Ghz, it always resets to 1300Ghz. No matter what rom I use it wont stay set. It always resets
Sent from my MB860 using xda premium
Do you have the "set at boot" box checked off?
If so, under Settings > CyanogenMod Settings > Performance do you have the CPU set at 1200 and have set at boot checked off?
DK
I hope someone corrects me if I'm wrong, but I believe there may be a bug with SetCPU. You can try CPU Tuner or that other app which does the same thing to confirm.
In any event, you may be able to circumvent it by setting up a profile. Just an idea. Let us know how it goes!
Maybe a bad version of setcpu or oc kernel. I haven't had any issues but I'm on HomeBase and have setcpu limits on screen off 216/456 and battery <50 1000. Been working superb I must say.
I use CPU Master and haven't had any issues at all.
Sent from CM7 Pre-Beta 4 on Atrix 4G.
No problems with setCPU. Just check off "apply at boot"
Hmm,i have the same issue with stock 2.3.4, setCpu and both faux or kholks kernel,very weird, i will try profiles, later today.
Same here, I have mentioned it many times and actuallly thought I was the only one.
Sent from my Tab using a pigeon.
Ok, i just tried the profiles and still to no avail. Very weird and rather annoying
I've also mentioned this a few times and have since moved back to 0.1.7
Try wiping setCPU's data from the manage applications menu.
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
drdino said:
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Very odd. You could also try wiping cache and dalvik if you haven't already.
Have you had this issue with any other ROMs?
I am more or less having the same issue. The annoying thing is that sometimes it would work but sooner or later, after a reboot, or changing the settings, it would go off again.
One thing that seeme to help is to set both slides to the min setting then just move one slide at a time, one click at a time and wait a few seconds between changes, till you get the settings you want... did not always work but it did more often then not.
I am going to try cpu master see if that does work for me.
Yeah it's weird. Whether it sticks or not seems totally random.
Hi, I'm on stock 2.3.4 and tried using CPU Tuner, it seems the kernel still won't act accordingly to the max cap I set.
Just like when I use SetCPU, even with the slider set max to 1000 and "Set on boot" ticked, it still jumps to 1300 sometimes.
So the problem could be with kernel, but I don't really know
bapaogoreng said:
Hi, I'm on stock 2.3.4 and tried using CPU Tuner, it seems the kernel still won't act accordingly to the max cap I set.
Just like when I use SetCPU, even with the slider set max to 1000 and "Set on boot" ticked, it still jumps to 1300 sometimes.
So the problem could be with kernel, but I don't really know
Click to expand...
Click to collapse
That's what I figure. I've tried everything.
Sent from my Atrix using XDA Premium
amwbt said:
That's what I figure. I've tried everything.
Sent from my Atrix using XDA Premium
Click to expand...
Click to collapse
Here's the good news:
http://forum.xda-developers.com/showthread.php?p=17575166#post17575166
drdino said:
Nope, same thing happens. The interesting thing is that if I cap it at 800 MHz, it tops up at that. Any step higher and the cap doesn't work.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Had the same problem with my atrix when I had one, prevented me from using any oc kernel.
Sent from my GT-I9100 using xda premium
bapaogoreng said:
Here's the good news:
http://forum.xda-developers.com/showthread.php?p=17575166#post17575166
Click to expand...
Click to collapse
Very good info. Thanks for posting! Greatly appreciated.
Sent from my SGH-I897 using xda premium
Related
I have been using Ultimate Juice defender and it seems to be working well I guess. Is there a better option? If you use UJD what settings do you use?
Root and use "SetCPU".
1967ls2 said:
Root and use "SetCPU".
Click to expand...
Click to collapse
That's what I use, I have profiles set to underclock the CPU when the screen is off or when the battery life falls to a certain percent
What's a strait forward guide to using set CPU.
Sent from my ADR6300 using Tapatalk
Here is the official setCPU documentation: http://www.pokedev.com/setcpu/
I am using the Adrynalyne Custom Kernal (v2) which defaults the cpu governor to Conservative in setCPU. For my setCPU profile, I only have one entry that underclocks to the slowest speed when the screen is off.
I have it set to run at conservative from 600 so mhz at 50%, 300 at 25% and powersave and lowest clock setting when the screen is off on powersave.
I'm running the latest frankenrom and using adr's experimental battery kernel
Deltaechoe said:
That's what I use, I have profiles set to underclock the CPU when the screen is off or when the battery life falls to a certain percent
Click to expand...
Click to collapse
+1 couldn't be happier wirth the battery life. Get about 27 hours power charge
Sent from my ADR6300 using XDA App
1967ls2 said:
Root and use "SetCPU".
Click to expand...
Click to collapse
i'm trying to run setcpu on my phone but everytime i set a profile it never kicks in and i set a default of 384/786 but phone still clocks out at max use according to my system panel. i'm using stock kernal so i dunno if that has anything to do with it........
trembly01 said:
i'm trying to run setcpu on my phone but everytime i set a profile it never kicks in and i set a default of 384/786 but phone still clocks out at max use according to my system panel. i'm using stock kernal so i dunno if that has anything to do with it........
Click to expand...
Click to collapse
I would make sure you have preflock disabled in the menu.
Sent from my Incredible using XDA App
"Stumbled" across this article
In my opinion one of the most informative!
http://www.acsyndicate.net/which-cpu-governor-should-you-go-with/
good read. thanks.
Shameless.
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Lol. Troublemaker!
Sent from my SPH-D700 using xda premium
squshy 7 said:
Shameless.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
What does that mean? lol
qbking77 said:
What does that mean? lol
Click to expand...
Click to collapse
i think because it was a team page it links to. that was my impression.
Sent from my SPH-D700 using xda premium
I was gonna post about this actually very informative. Now I'm using voltage control. What should I set for the I/o scheduler? I tried interactive governor and my phone almost locked up lol. Was using conservative. Just started using ondemand.
Sent from my SPH-D700 using XDA Premium App
Bump
Sent from my SPH-D700 using XDA Premium App
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
nubecoder said:
For your reading enjoyment.
There are actually a few things Samsung have done that contrast these docs, the biggest of which is that Samsung's conservative governor is more like a transitional governor, in that it simply uses the "transition_states" array to do it's scaling (rather than the calculation conservative uses to determine the next frequency).
Click to expand...
Click to collapse
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Sent from my SPH-D700 using xda premium
JohnCorleone said:
So Nubecoder, is using "on demand" on our phones bad or not? I haven't had any problems running 1400/100 on demand with no,undervolting for months without issue but I still wanted to know. Thanks.
Click to expand...
Click to collapse
[The short answer]
If it's working for you, then it's not "bad". ;]
[The much longer than I had expected it to be, other info / opinions on Epic governor related issues, answer]
It's just that the Samsung phones don't have anywhere near the amount of steps as other devices do, and their handling of which step to jump to when asked for freq X is not that great (and becomes more of a problem when frequencies are disabled with tools like setCPU and Voltage Control).
The other big thing is that (in Samsung's code) there isn't any compliance to the cpufreq "scaling_min" setting, it simply uses a clip to make sure it's not below the lowest available freq (ie 100MHz) and doesn't care if it's below the scaling_min. Some phones handle the 100MHz better than others (and the original 100MHz is possibly "broken" when you look at it's divisors).
Note that some do kernels have some changes in place to force the compliance of the scaling_min setting. (I know Genocide does anyway.) (And mine does but it has yet to be released to the wild.)
There's some other things in play as well, like the DVFS lock that can be applied to force the frequency to be a "fixed" freq (as in won't change) or a "high_lock" which is basically "no lower than X".
For example, there is a DVFS lock used any time you touch the touch screen that will not allow the CPU to scale below 800MHz (lock token 6 IIRC). (The lock is lifted when you let go). And Samsung's conservative (IMO transitional) governor uses a fixed lock of 800MHz during sleep (suspend).
I've spent a lot of time trying to figure all of this out and to determine why Samsung's devices (specifically the Epic) simply don't play well with most governors.
I have worked out most of the bugs in my kernel (I wrote a function to handle getting the nearest requested frequency with disabled freqs in mind). But it's still not perfect.
I've considered going full force and adding tons of freqs to see how that works out, but that's a crap-ton of work, and my current goal is to release my kernel before official GB drops.
Hopefully will be over the next few days (but I've been saying that to myself for weeks now it seems).
=]
I am running faux's newest kernel on my att atrix, Allen build 4. I've noticed that upon cold reboot, the frequency scales correctly. after a while however, the phone stays at the max frequency. I've tried stopping running archives that I thought might be causing this, hit it doesn't help. Is it the kernel?
Sent from my MB860 using xda premium
You have a misbehaving process
turl1 said:
You have a misbehaving process
Click to expand...
Click to collapse
That's what I thought originally, but after killing all the apps that were running, it still stayed at the frequency.
I have a hypothesis, and i'm going to test it in a second. I think that when I plug my phone into my laptop dock, it for some reason locks the frequency at max.
EDIT: It's the webtop mode. If I plug the phone into my laptop dock, and open the laptop, the frequency is locked at maximum frequency. I'm going to flash the stock kernel again, and see what happens next.
EDIT2: So it's definitely faux's newest kernel. It might just be me, but it definitely is locking to max frequency. Stock does not have this problem.
Sent from my MB860 using xda premium
paravorheim said:
That's what I thought originally, but after killing all the apps that were running, it still stayed at the frequency.
I have a hypothesis, and i'm going to test it in a second. I think that when I plug my phone into my laptop dock, it for some reason locks the frequency at max.
EDIT: It's the webtop mode. If I plug the phone into my laptop dock, and open the laptop, the frequency is locked at maximum frequency. I'm going to flash the stock kernel again, and see what happens next.
EDIT2: So it's definitely faux's newest kernel. It might just be me, but it definitely is locking to max frequency. Stock does not have this problem.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I have seen the same behaviour. Just got my HD Dock yesterday. When I pulled it out it was warm/hot. I thought it was just the clock/screen using power or whatever. Then I opened SetCPU while in the dock and it showed a constant 1000Mhz. When I unplug it still shows that frequency. Too bad
use the auto detect button again#
Sent from my MB860 using xda premium
ltdanno360 said:
use the auto detect button again#
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks, I'll try it out in the morning, and report back.
Sent from my MB860 using xda premium
I think this is a known issue with faux's new kernel. When you place the phone into a laptop dock it clocks the CPU at max until a reset. I guess the same thing happens with any dock
Sent from my MB860 using xda premium
i have recently made a decision to delete the set cpu and install cpu masters from the market ,i think so for after 24 hours i think it does make a difference um
i notice lower temps even after an hour of useing the webtop or just an average temp overall i am useing the faux 2.0 kernal 1.3 oc but its set at 1.2
my profiles are screen off 456 max-216-min
the rest are 1200max 216-min
Sent from my MB860 using xda premium
I don't have a dock but I just installed _unknown's hdmi/webtop mod while running faux's enhanced stock 0.2.0. Noticed my phone was really hot after trying it out, even with the screen off and noticed a constant 1000 max. in setCPU.
Cleared my cache & dalvik, reinstalled kernel, jugg's battery fix, cleared my battery stats, rebooted into recovery (figured it wouldn't hurt since it defaulted to that option), then fixed permissions and restarted. Everything seems to be back to normal.
Will see what happens when I run the webtop again and report back later. Currently CPU is showing 36C and battery is at 32C. Are these acceptable temps?
Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.
I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium
I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium
Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.
If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064
100-800 mhz, 125% live oc.
So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though
Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize
I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?
Hi All,
Want to share with you, experimented the XXLT5 on GTN7000. Superb ROM....so far no issues....you name it, it works fine. Note the downloaded file is above 1GB...seems this has all the fixes required. You can root it as well....if any issues found on this stock rom do let me know....will be interested to catch the bug.
Link for download...http://www.hotfile.com/dl/213299077/83496c8/N7000XXLT5_N7000OXXLT2_XEH.zip.html
Link for root : http://d-h.st/GiO
Installation...as usual....Odin...so have a latest pack..open, select the PDA and good to go.
the hotspot works?
aftabbabar said:
the hotspot works?
Click to expand...
Click to collapse
Yes...works fine.
I'm running N7000XXLT4 as my build -- is this simply an improved update that just hasn't hit my German unit yet?
And what's better in this LT5 from LT5 posted on may 7th? http://forum.xda-developers.com/showthread.php?t=2267748 Why we need another thread?
...from SG NOTE N7000 with Tapatalk 2
Murshad007 said:
I upgraded ota from Gb to Ics. And i do a factory reset before. Then on ics i didnd factory due to brick bug. And ota update to JB UAE version. My cpu is always 15-35 % on idle and above 60% with any applictation like Google+ or Hangout..
I did wipe cache and factory reset in recovery.
Now i flashed LT5 And wipe and factory before and after. But still the same?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Do you have a cracked screen? My CPU idled quite high when my screen was cracked.... Did you also experience the above problems with CyanogenMod?
Screen not cracked, outer body have some cracks. Phone is running smooth in gb and Ics
Sent from my GT-N7000 using xda app-developers app
hotweiss said:
Do you have a cracked screen? My CPU idled quite high when my screen was cracked.... Did you also experience the above problems with CyanogenMod?
Click to expand...
Click to collapse
Cm10.1 nighties 29 06 2013 same issue.. Although phone not hanged up.. But CPU usage around 35-65% without any heavy usage
Sent from my GT-N7000 using xda app-developers app
Murshad007 said:
Cm10.1 nighties 29 06 2013 same issue.. Although phone not hanged up.. But CPU usage around 35-65% without any heavy usage
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Something must be wrong with the phone if you have such a high CPU usage after a fresh install. Send it in for servicing.
hotweiss said:
Something must be wrong with the phone if you have such a high CPU usage after a fresh install. Send it in for servicing.
Click to expand...
Click to collapse
first, whats your upgrade procedure, try without restoring stuff and let os settle in. restoring app+data usually causes this with me.
Also what app do you use for measuring cpu usage. That may be off for some reason. Also note cpu utilization v. s. governor. Example on demand scales up frequency when e. g. uses 80%, so it will seem high, but in regard to frequency it is not. Due to battery savings lower frequencies are used, until 80% frequency is reached before going to a higher frequency, thus for same task higher utilization of that frequency it may not be a bad indication is what I am saying.
Now a rom usually needs some time to synch, perform breakin tasks, scan all media etc, try to see through settings, development options then cpu utilization what is utilizing cpu. Maybe app has gone bad, rogue, or maybe its expected.
M using CPU Z, thanx for utilization info
Sent from my GT-N7000 using xda app-developers app
Murshad007 said:
M using CPU Z, thanx for utilization info
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
your welcome, you can check also cooltool, that has a nice overlay you can position anywhere. You can configure and show e.g. frequency, cpu utilization, temp(battery I think), pretty fun.
Sent from my GT-N7000 using Tapatalk 2