So, on every TW ROM with whatever kernel combination no matter what I set my minimum frequency to, it always bumps it back up to 1020 whenever I go back into whatever app I used to set it with. Even if I just flash a kernel or a ROM and I don't mess with it, I look on CPU Spy and it says it's still set to 1020. Also on CPU Spy it says that it operates in frequencies lower than 1020, so it makes no sense. Anyone know anything about this?
Sent from my SCH-I535 using Tapatalk 4 Beta
jakereeves31 said:
So, on every TW ROM with whatever kernel combination no matter what I set my minimum frequency to, it always bumps it back up to 1020 whenever I go back into whatever app I used to set it with. Even if I just flash a kernel or a ROM and I don't mess with it, I look on CPU Spy and it says it's still set to 1020. Also on CPU Spy it says that it operates in frequencies lower than 1020, so it makes no sense. Anyone know anything about this?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Sounds like you have a benchmark apply or something that is over ridding your setting. I know kt has a lock frequency option, maybe look at others?
Sent from my Ktweaked PACmaned SGS3!
Go to the init.d folder and see whats in there and what the settings are. Also do you block mpdecision at boot? What kernel are you using? Try setting your cpu app to delay at boot
Surge1223
It's none of that because it still happens after wiping my phone and everything
Sent from my SCH-I535 using Tapatalk 4 Beta
Used to happen to me too, i solved it by setting system to mount r/w at boot and using only one app to lock my cpu setting and set that app to delay loading a couple seconds on boot. What app do you usually use to mod you min/max cpu settings?
Surge1223
Surge1223 said:
Used to happen to me too, i solved it by setting system to mount r/w at boot and using only one app to lock my cpu setting and set that app to delay loading a couple seconds on boot. What app do you usually use to mod you min/max cpu settings?
Surge1223
Click to expand...
Click to collapse
I usually use trickster mod! What do you mean by setting system to mount r/w at boot?
Sent from my SCH-I535 using Tapatalk 4 Beta
I remember reading a post In synergy rom about CPU revs. And that certain revs you can't mess with the CPU.its some where in the thread.
Sent from my SCH-I535 using xda premium
jakereeves31 said:
I usually use trickster mod! What do you mean by setting system to mount r/w at boot?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I mean I set a script to launch at boot. I used rom toolbox pros scripter.
Oooh, well I'm back on AOSP and the problem doesn't exist. It only happens on Suckwiz
Sent from my SCH-I535 using Tapatalk 4 Beta
Related
Would setcpu work in this case just to lower clock speed of the phone? I'd like to lower it when the screen is off.
Cheeze[iT] said:
Would setcpu work in this case just to lower clock speed of the phone? I'd like to lower it when the screen is off.
Click to expand...
Click to collapse
yea, if you're rooted, setcpu works without any problems. I have my at 1000 mhz min & max but you can set it however you like
jroid said:
yea, if you're rooted, setcpu works without any problems. I have my at 1000 mhz min & max but you can set it however you like
Click to expand...
Click to collapse
It works, but you have to re run it every boot up, because it gets confused (you'll see an error when you run it after a reboot)
Gotta wait for a real update to it to support the stock kernel correctly.
Setcpu
Anyone successfully using setcpu on the nexus s? Seeing any benefit in battery life?
Sent from my Nexus S using Tapatalk
hah2110 said:
Anyone successfully using setcpu on the nexus s? Seeing any benefit in battery life?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=880968
Mine doesn't wake up when in conservative...
Sent from my Nexus S using Tapatalk
What governor are you using? Per directions of app, I try conservative but the phone never wakes up when using a sleep/conservative profile. Same thing happens with the superpower app with or without OnDemand force.
hah2110 said:
What governor are you using? Per directions of app, I try conservative but the phone never wakes up when using a sleep/conservative profile. Same thing happens with the superpower app with or without OnDemand force.
Click to expand...
Click to collapse
I have the same problem, I've tried a few different setups/governor settings and I still get the same issue. I have to pull the battery to get the phone to turn back on. Also I think the phone actually shuts off, according to an app called System Panel after I rooted and set up setcpu the phone shutoff shortly after I went to bed for the night.
same problem. I set min 100 max 400 for screen off profile, never wakes up.
On the epic, 100mhz is too low for the phone to wake up so 200 is the min
Snce the ns uses a humingbird, that might be the problem too
Try conservative on 200min 1000max and see if it'll wake up
Sent from my SPH-D700 using XDA App
Is that nexus s auto step down the speed automatically?
Sent from my Nexus S using XDA App
jcsmart said:
Is that nexus s auto step down the speed automatically?
Click to expand...
Click to collapse
OS Monitor puts the cpu at 100,000khz - 1,000,000khz and shows it changing so yes stock will do it too. However, what they want to do is make sure that, at certain times, the cpu can't reach its full speed and that stock will not do
there is a new version of set cpu 2.10
did anyone try it?
on 2.04 it was still acting crazy
I was having the same issues with the phone never waking up -even with the most updated version of setCPU- and having to pull the battery to get it back on so I uninstalled. However, I flashed the Team Whiskey ROM with the 1.3Ghz kernel and it has been rock solid since. I've overclocked the processor to 1.3Ghz while awake and using on demand governor with 200mhz min/400mhz max when sleeping. No problems so far.
SetCPU 2.10 works properly on Nexus S
just confirmed, it doesn't show weird numbers anymore
Moved to Q&A
SetCPU help
Hey I just got set CPU and I'm not going to lie I don't understand hhow to use. I messed around without a bit but it would freeze after a while and the screen wouldn't turn on. I don't care about overclocking it all I really want to do is save battery power. Can someone share there setcpu profile Either the info or just the file.
Sent from my Nexus S using XDA App
[Q] SetCPU Instructions
Okay, can someone give me the low-down on how to use SetCPU to it's potential. I'm no noob, but I need someone to point me in the right direction.
I am very interested in a how to as well!
Sent from my Nexus S using XDA App
can someone help?
So I was able to successfully overclock my phone last night.
Today, after several black screen of deaths, it's no longer OC'd. Not sure if it's the black screens.
I flashed faux's DS kernel .044 on CM7 nightly 174
If you have setcpu make sure you check "set on boot"
fcisco13 said:
If you have setcpu make sure you check "set on boot"
Click to expand...
Click to collapse
It'd be best if the OP waits til they find a setcpu configuration that doesn't cause issues before they set it to set on boot. Until then I'd just start setcpu manually with each reboot.
Oops I forgot to include, I set it to 1.55ghz found stability issues with that, then set it to 1.4ghz. Checked it to "set on boot"
Now it's back to normal and it says the max is 1ghz.
So I can "no longer" overclock. Wow I can't believe I left that out.
Seems like u flashed a new kernel and setcpu doesnt read it. Go to device selection in setcpu choose auto detect and should be fine, I hope
Sent from my LG-P999 using xda premium
I actually didn't flash a new kernel. I didn't flash anything.
Have u tried device selection anyway?
Sent from my LG-P999 using xda premium
Thanks waldano. I restored a backup which changed it from auto detect to tegra. Now I set it back.
Thanks
What should I set my min to?
Sent from my LG-P999 using XDA App
I'm using matr1x's v22.5 jb kernel with slimbean. Whenever I try to change the CPU speeds my phone reboots and the settings are not saved. Does anyone know why this is? I've tried changing them with ROM toolbox pro and nstools but both did the same thing.
Sent from my Crespo using xda app-developers app
Yeah I don't have that here... try it with setcpu too though.
Sent from my Nexus S
Will do. Might I note everything becomes unresponsive before restarting.
Sent from my Crespo using xda app-developers app
Yeah no crap like that here... try setcpu or reflash kernel.
Sent from my Nexus S
Don't have any money for setcpu unfortunately, but I did manage to get my min CPU set to 200 but I can't change the max CPU. I felashed the kernel, too.
Sent from my Crespo using xda app-developers app
DefinitiveX said:
Don't have any money for setcpu unfortunately, but I did manage to get my min CPU set to 200 but I can't change the max CPU. I felashed the kernel, too.
Click to expand...
Click to collapse
Are you trying to underclock? Don't.
So setting my MX CPU to 800 would not be a good idea? I'm trying to do everything I can to preserve my battery life.
Sent from my Crespo using xda app-developers app
DefinitiveX said:
So setting my MX CPU to 800 would not be a good idea? I'm trying to do everything I can to preserve my battery life.
Sent from my Crespo using xda app-developers app
Click to expand...
Click to collapse
Actually you will be able to underclock in my next release without any problems because I've included the bug fix for that... for now you can run it at 1Ghz.
Sent from my Nexus S
i have encountered same problem several times due to NSTool did not automatically change the kernel's default settings.
but sometimes it works and sometimes it doesn't , how strange is it ... can't really figured it out...
however, it doesn't actually caused problem just little annoying
---------- Post added at 12:54 AM ---------- Previous post was at 12:53 AM ----------
setCPU , why don't you just use NSTool ? it's free and more usable...
Is there an app for turning on and off the second core besides the terminal?
Sent from my SAMSUNG-SGH-I727 using xda premium
I use system tuner and force my 2nd core on at startup.
Sent from my SAMSUNG-SGH-I727 using xda premium
Why would u want to turn it on and off manually? Something called mpdecision had been pre-baked into every rom (stock or not) since the phone was released. It controls whether or not the second cpu is active depending on load. As long as u are using a performance oriented governor setting, when u start a game it'll automatically switch it on.
I've had my Note 10.1 for 3 days now and when I first got it I flashed a JB rom on it but I noticed that whenever I press the power button it takes a few seconds to wake up. It's not consistent. It's the only glitch/bug/etc. I've come across. Everything else seems perfect. Maybe it's because I'm using JB on an 8013 version or is this something normal that affects everyone?
Yeah, it is from the sleeping stuff, like booting your other computer, it takes different amounts of time from different types of standby types. If you want to get rid of this issue, youll more than likely lose more batrery life on standby
What is it that is causing it? The kernel?
Sent from my GT-N8013 using XDA Premium HD app
That would be one reason. You can change some of your settings with your cpu, maybe a build.prop tweak or init.d script coild make it wake up faster. It hasnt bothered me to the point of fixing it yet, but that is also becuase it would cause the battery to drain faster
smaw51 said:
That would be one reason. You can change some of your settings with your cpu, maybe a build.prop tweak or init.d script coild make it wake up faster. It hasnt bothered me to the point of fixing it yet, but that is also becuase it would cause the battery to drain faster
Click to expand...
Click to collapse
Is it from being on this jellybean rom? I'm just wondering if it's from this or if it happened on ics also. I had the ics stock rom on for about 5 mins so I don't remember. None of my other devices have had this problem. Just curious.
Sent from my GT-N8013 using XDA Premium HD app
SkizzMcNizz said:
Is it from being on this jellybean rom? I'm just wondering if it's from this or if it happened on ics also. I had the ics stock rom on for about 5 mins so I don't remember. None of my other devices have had this problem. Just curious.
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
I dont remember about ics, but it would probably be a different way of handling some things. Look into build.prop tweaks for sleep and see what you find
smaw51 said:
I dont remember about ics, but it would probably be a different way of handling some things. Look into build.prop tweaks for sleep and see what you find
Click to expand...
Click to collapse
I wouldn't know what to look for lol.
Sent from my GT-N8013 using XDA Premium HD app
SkizzMcNizz said:
I wouldn't know what to look for lol.
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
I use rom tool box, but there are a lot of other apps that will let you get into the build.prop and make the edits
Open it up from /system/build.prop
add this to the end with a text editor:
Code:
# sleep modes
pm.sleep_mode=2
#usage:
#pm.sleep_mode=0 -> collapse suspend
#pm.sleep_mode=1 -> collapse (will totally power off the cpu)
#pm.sleep_mode=2 -> sleep (cpu is still on, but put into low power mode (registers are still saved)
#pm.sleep_mode=3 -> slow Clock and Wait for Interrupt (lowered frequency and voltage)
#pm.sleep_mode=4 -> wait for interrupt (no change in cpu clock or voltage)
The # represents a comment line, so the build.prop is not reading it, it is just to know what is going on an stuff.
try having it set to 2 or 3
you will need to reboot after making the changes and maybe even wipe the cache