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?
Related
It worked fine on infused now that I'm running infused 2.0.0 ill set my 2 profiles (screen off and while charging) if my screen is off my phone wont wake up, nothing happens even if I hook my charger up to it. I have to pull battery in order for my phone to wake up. I've disabled my profiles and phone works fine, its just a little odd. Any ideas?
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
I'm currently running v2.0 and I have a screen off setCPU profile and am experiencing no problems. However, I am not necessarily experiencing better battery life or performance. I think I'm going to run juice defender for a while and see if I can find anything different. For now, I don't even know if I would use setCPU is the best advice I can give.
I'm currently running v2.0 and I have a screen off setCPU profile and am experiencing no problems. However, I am not necessarily experiencing better battery life or performance. I think I'm going to run juice defender for a while and see if I can find anything different. For now, I don't even know if I would use setCPU is the best advice I can give.
Don't set any profiles with frequencies below 800, will cause an SoD. Netarchy has a fix for this, and the fix is in the reference kernel git repo, but I don't think anyone has released a compiled kernel with the fix yet.
Sent from my GT-P7510 using Tapatalk
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 running cm7 with Trinity kernel Oc at 1400 when I plug into the wall sometimes the battery gets hot also when playing VIP poker .all other apps run great. Any suggestions?
Sent from my LG-P999 using XDA App
timothy7732 said:
I'm running cm7 with Trinity kernel Oc at 1400 when I plug into the wall sometimes the battery gets hot also when playing VIP poker .all other apps run great. Any suggestions?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
That's gonna happen while using the phone non stop, as for charging make a profile for when screen off/ while charging I do that and never have over heating issues... I also reboot the phone after I plug it in.
Sent from my LG-P999 using xda premium
Thanks
Sent from my LG-P999 using XDA App
timothy7732 said:
Thanks
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It seems like an error in the graphic drivers. I could come from a cold boot play a game til my phone gets warm then exit the game. After that the phone never cools down until after reboot. This has less to do about a charging profile and deals more with rouge code
Sent from my LG-P999 using xda premium
I'm assuming that's the performance kernel, and of course it'll overheat (to about 108-115 for normal highs). You're overclocked and charging the battery will be more hot than usual, you don't need to have it clocked so high for something like that, try it at lower frequencies if you're charging.
Why dont you just drop your clock speeds down to 1200. It should still perform like a champ. Expect heat while charging, I am running the ICS Eagles Blood ROM. It happens to mine too, without O.C.
It still has major bugs but it is far smoother than the stock 2.3 lg release that sucks to date.
Really you don't need to OC that high though, and if you do you should consider doing some undervolting.
If you are over clocking to 1.4gz your phone WILL get much hotter.
This us because your CPU is running faster, and generates more heat.
Sent from my LG-P999 using xda premium
Obviously, lower the CPU speed. This shouldn't have to be said.
Sent from my amazing G2X running Bionic Reloaded v1.2.1
Thanks still learning just drooped to 1200 Max and 430 min so ill se what happens thanks again
Sent from my LG-P999 using XDA App
Serotheo said:
I'm assuming that's the performance kernel, and of course it'll overheat (to about 108-115 for normal highs). You're overclocked and charging the battery will be more hot than usual, you don't need to have it clocked so high for something like that, try it at lower frequencies if you're charging.
Click to expand...
Click to collapse
It's not an overcloking issue. I had the same problem at 1.2ghz and my phone was set to drop to 800mhz max when the screen was off. If it was an overclocking it wouldn't happen only when the phone is asleep because most phones are setup to use very little of the cpu when they are inactive.
Sent from my LG-P999 using xda premium
psychoace said:
It's not an overcloking issue. I had the same problem at 1.2ghz and my phone was set to drop to 800mhz max when the screen was off. If it was an overclocking it wouldn't happen only when the phone is asleep because most phones are setup to use very little of the cpu when they are inactive.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Or, you had an app/s that kept running in the background, thus keeping the CPU awake. No G2X kernels currently support deep sleep (which would basically shut down almost everything when the screen is off), so that's another possibility. I'm on stock and don't need more than 760mHz per core most of the time.
Sent from my amazing G2X running Bionic Reloaded v1.2.1
my g2x running cm7 and the stock kernel will overheat when plugged into the wall. this alone caused many screens of death and constant reboots for me. i tend to just pop off the battery door before plugging it in and no more issues.
qpinto said:
my g2x running cm7 and the stock kernel will overheat when plugged into the wall. this alone caused many screens of death and constant reboots for me. i tend to just pop off the battery door before plugging it in and no more issues.
Click to expand...
Click to collapse
Yeah last night my phone froze and I'm running eagleblood's rom with stock kernel. I didn't reboot my phone before I went to sleep so that probably killed it
Sent from my LG-P999 using xda premium
Yeah switch miui havent had that problem on this one
Sent from my LG-P999 using XDA
psychoace said:
It's not an overcloking issue. I had the same problem at 1.2ghz and my phone was set to drop to 800mhz max when the screen was off. If it was an overclocking it wouldn't happen only when the phone is asleep because most phones are setup to use very little of the cpu when they are inactive.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
it really is not but it helps overheating a bit.its not like We OC to 1.8 but 1.4 still unnecessary.
This a dual core even at stock voltage still overheats.I seen single core devices really overheat.Plus Our experiences with overclocking,overheating would be different because each hardware make act different even though it's same phone.Also different locations,humidity temperature that affects phone too.You try to oc to 1.8 in the UK and it won't overheat lol COLD.
Sent from my LG-P999 using XDA
theking_13 said:
Obviously, lower the CPU speed. This shouldn't have to be said.
Click to expand...
Click to collapse
+1 zillion
So I've had a bit of a heating issue with my g2x as of late. Currently running the Hellfire sandwich (witch by the way is beast). Even before that it for pretty warm. Anyone else have this problem?
Sent from my LG-P999 using XDA
fatchuckyd said:
So I've had a bit of a heating issue with my g2x as of late. Currently running the Hellfire sandwich (witch by the way is beast). Even before that it for pretty warm. Anyone else have this problem?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
mine has been getting a little warm since i flashed Hellfire... but that is mainly due to always being on it lol... it cools down when idle. Still not as warm as some of my old phones... but didn't have any temp issues before hellfire if that helps at all
meh8036 said:
mine has been getting a little warm since i flashed Hellfire... but that is mainly due to always being on it lol... it cools down when idle. Still not as warm as some of my old phones... but didn't have any temp issues before hellfire if that helps at all
Click to expand...
Click to collapse
The problem I'm having is at idle its warming up, its only clocked to 1260 but I tried it at 870 and it got really hot
Sent from my LG-P999 using XDA
I'm at the default 1015 and it seems to be fine... Are you running the newest rom (1.4)?
meh8036 said:
I'm at the default 1015 and it seems to be fine... Are you running the newest rom (1.4)?
Click to expand...
Click to collapse
Yes, flashed it last night. I've had this issue for some time now. Started with GB
Sent from my LG-P999 using XDA
hellfire does get pretty warm but use a CPU manager to put a profile for temperature. fyi the AOKP rom doesn't cause the g2x to heat up as much. it could be a kernal problem?
All ics roms have my phone running warm. Sort of to be expected with the way it has to be built
Sent from my LG-P999 using Tapatalk
it happened twice but my phone while on the charger over night got extremely hot. The phone wouldn't come on and I had to remove the battery and let it cool off.
theicebergx said:
it happened twice but my phone while on the charger over night got extremely hot. The phone wouldn't come on and I had to remove the battery and let it cool off.
Click to expand...
Click to collapse
I've had to do that to. I don't think the ics did it cuz it did it with gb
Sent from my LG-P999 using XDA
I rock out at 1.2 and 1.4 ghz quite alot and I always have a failsafe at 44.9c (which is what the stock battery is rated for) clocking the CPU to 594 @ 750mv then it will cool down and clock back up when its safe with setcpu profiles.
Note: I run an aftermarket battery which is rated for 50 degrees c so if you have a stock battery you may want to set it below the Max temp rating on your battery cause the hotter it gets more often the quicker it loses charge.
Pin it to Win it.
I.R.Chevy said:
I rock out at 1.2 and 1.4 ghz quite alot and I always have a failsafe at 44.9c (which is what the stock battery is rated for) clocking the CPU to 594 @ 750mv then it will cool down and clock back up when its safe with setcpu profiles.
Note: I run an aftermarket battery which is rated for 50 degrees c so if you have a stock battery you may want to set it below the Max temp rating on your battery cause the hotter it gets more often the quicker it loses charge.
Pin it to Win it.
Click to expand...
Click to collapse
Is an aftermarket the way to go with this?
Sent from my LG-P999 using XDA
fatchuckyd said:
Is an aftermarket the way to go with this?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
I would never go back to a stock battery after having this but your issue sounds like the classic set the phone to not sleep during charging problem.
Try going into settings>applications>development>stay awake
Make sure that its checked and you shouldn't have overheating issues
Pin it to Win it.
Try putting it to the lowest CPU. If not try a new battery.
Sent from my LG-P999 using xda premium
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