Related
The problem is, no matter what program I use, if I set the Tab to downclock at 100/200 or even 100/400 when the screen is off, the phone will freeze in sleep and force me to reset the tablet pressing the power buttornfor 7 seconds.
Anybody else have this issue?
Sent from my Milestone
do you use SerCPU?
I set is 100/400, it sometimes work but my phone was getting random reboot.
So I disabled it...
Sent from my GT-P1000 using XDA App
same issue with me , if I set the cpu to 100 to 300 it would hang or crash coming out of sleep mode . I ended up removing setcpu and going back to stock . i expect the Cooked roms will resolve this later on .
Probably kernel related. If i select the Set On Boot option, after a reboot both min/max freqs will change to a min of 19 and max of 500. Probably best to leave it until we have devs working on it.
Sent from my GT-P1000
there's really no need to underclock when the screens off, you know that right?
infamousjax said:
there's really no need to underclock when the screens off, you know that right?
Click to expand...
Click to collapse
Get an app to graph the cpu use, and you will see the cpu spike when sleeping.
So, in short, yes: downclocking with the screen off really help the battery life
Sent from my Milestone
It doesn't make much difference as the cpu scaling does a more than adequate job, but whatever wets your whistle
This is what I've done to help my battery life.
Firstly you'll have to root your device, then follow the steps below.
1. Install SetCPU(from Market or where ever you can find it)
2. Run it, allowing root access when asked by superuser.
3. On the Main tab, set Max and Min to 1200000(1.2Ghz), or whatever you want general usage to be. Most users probably want it like this so it will stay at best performance during using, and will not slow down. Also, whatever speed you're using set Scaling to Performance. Even if you are not running at top speed, it is still good to use Performance for the settings you want while using the device.
4. Go to Profiles tab. and check Enable, and click Add Profile. Set it to Screen Off, and you can change the settings to whatever you want. I had it at 100000(.1Ghz) for Min and Max, but when you go to unlock your screen, it lags a lot for a second. I currently have Max and Min set to 400000(.4GHz), and it made it so it does not lag when I go to unlock, but it is still low enough to be very conservative on battery. Set Scaling to Powersave, and Priority does not matter unless you have more than one profile, so don't worry about it.
5. (Optional) Install JuicePlotter from the Market, for free, and it has a nice widget that collects your phone data and after a few days will become very accurate on phone battery life remaining. It will show it after a day or so, but it will tell you how accurate it is, and it might not be very high until a few days later.
And that's it. Whenever your screen is off, it will underclock the processor so it's not using as much battery when not necessary. If you want, you can add other profiles, such as for when charging, and when the battery is low. I originally had it set to 1.2 GHz Max and Min while charging, and set the priority higher than the Screen Off, so it didn't clock down if I turned the screen off while charging, but there is no reason, I'm still not using it when I turn off the screen, so I deleted that profile.
So if your only profile is the Screen Off, then once you turn the screen on, it will change to whatever settings you have on the Main tab.
I unplugged my phone at 6:30 AM, and it is now 5:30 PM here, and I still have 32% battery, with JuicePlotter telling me I have 4 hours and 49 min left, but it only has a 72% accuracy since I just got the app yesterday. That's great since yesterday my phone would have been dead over 2 hours ago. When I woke up JuicePlotter said I had around 15 hours, but it wasn't as accurate as it is now, and it so far is expected to last longer than that..
I just use JuiceDefender free set to Agressive to obtain the best battery life. I got this little vendetta against SetCPU though.
I saw a button on there that said battery saver, what exactly does it do?
apwhitelaw said:
I saw a button on there that said battery saver, what exactly does it do?
Click to expand...
Click to collapse
Not sure. I'm learning JD myself here so .... yeah
apwhitelaw said:
I saw a button on there that said battery saver, what exactly does it do?
Click to expand...
Click to collapse
It takes you to a recommended battery saving app from the market. I haven't tried that app, but I imagine it is probably something similar to SetCPU.
I think this is wholly unnecessary, I'm sure samsung underclocks when not in use already, it's an obvious thing to do. I haven't done any of this and I can get ~40 hours of light-medium use
But try watching justin.tv streaming movie on hspa+ lets see if you even get 4hrs?
Sent from my SAMSUNG-SGH-I997 using XDA App
Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?
Yeah I used it since yesterday. I've frozen a ton of bloatware via TB and it went into deep sleep for 7.5hrs last night while I was asleep. I'm seeing a crazy amount of different CPU speeds in there too though. Very odd.
I actually removed all the damn bloatware instead of freezing them. But then I added my own apps that I normally use. But I think I have finally weed out the damn app that is causing my deep sleep issues. it's either FriendCaster Pro or Google Music Beta...
I gave it a try yesterday when I first picked it up. Seems to either idle really high, or low depending on what your doing. Hardly ever used the mid range cpu frequencies.
yes! Once the source code can be.... had.... Kernel development would begin. As anyone have seen using CPU Spy, the governor either MAX out the CPU or just lower it to the minimal, it "rarely" stays in the middle. With some "tweeking" how the CPUFreq works we can probably save battery
mbze430 said:
Has anyone else been using CPU Spy to monitor Deep Sleep? I haven't once seen my phone going in to Deep Sleep. Anyone else?
Click to expand...
Click to collapse
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.
RAVEN6 said:
I have been using it for a couple of weeks now along with Antutu CPU Master. After charging, I usually reboot my phone and deep sleep kicks in. I use Antutu to lower the CPU speed to 192 mhz.
Click to expand...
Click to collapse
Are you having any problems with Antutu keeping the setting at 192, after I reboot my phone Antutu keeps changing the low setting up to 384? Yes I have it set to apply on boot. I sent the Antutu devs an email a few days ago asking them about this, but no reply?
Sent from, The Eclectic Chair.
I thought this was the deep sleep issue that people have with certain chargers?? plug charger in and let screen turn off then turn screen on and unlock, then unplug charger. Check to see if it goes into deep sleep then or just reboot the phone after charging....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I am running cm9(beast mode wifi calling one ) atm but I have a heat issue with my phone around the camera and speaker area where the phone is really hot but by the battery n bottom half it is much cooler.
is this normal for you guys? N gals? And even if I turn of the phone n it cools to 91 is shoot back up again
Sent from my SGH-T959V using xda app-developers app
I'm running on demand btw and around of charge 98-113 charging 109-123
Sent from my SGH-T959V using xda app-developers app
idunno why but we have the same problem..
i think that the reason why it heat up is because you overclocking it?
when i set it max it really heat up quickly.
Install betterbatterystats and see how much CPU you are using and on what.
Sent from my SGH-T959V using xda premium
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
dgmoodey said:
Sometimes I have this problem while charging my phone, it actually will not charge at all through the night. I think this happens when it is warm, because in the summer, the phone overheats in my pocket and dies out
Click to expand...
Click to collapse
i do that but it goes to 200 mhz never 100
xtrem88 said:
i do that but it goes to 200 mhz never 100
Click to expand...
Click to collapse
That's a 'feature' of the ICS+ kernels. While 100MHZ is the minimum, if it's actually set to that, the kernel is set to go back to 200MHZ anytime it gets the chance. You can watch this happen if your scheduler/governor app actually updates on current min/max speeds. ROM Toolbox PRO, SetCPU, ROM Control, and CM's Performance controls all display this shifting, though with luck you can sometimes get it to stick at 100MHZ. It just takes some persistence.
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
airfluip1 said:
The modem on the phone isn't very good.
It even happens on stock where if you go in and out of dead zones, it will "SEARCH" for network and become burning hot, so it's a common problem that happens year round. It's a great way to kill battery. That's also why if you leave you phone in a sock drawer, it's going to last longer than if it's in your pocket walking around.
Click to expand...
Click to collapse
well i left i think it was kj2 and flashed lb6 and i started using greenify hasn't really happened now
No to open another thread I have a Android backup issue any suggestions?
And power managed is on even though wifi is off
Sent from my SGH-T959V using xda app-developers app
I never got my phone to go into deep sleep when I selected ondemand (or maybe it was ondemandx). I would try a couple of the other governors & see if that would help.
Sent from my SAMSUNG-SGH-I547 using xda app-developers app
OndemandX gives me good sleep, but forces the phone to minimum speeds when the screen is off. That tends to cause issues if I'm trying to use GPS or music without the screen burning.
As to what will work best... that depends on unique your phone, its apps, any tweaks that have been made, and your specific combination of scheduler/governor settings. I'm a fan of SIO, but sometimes the tweaks make that (and deadline) stick at max MHZ, in which case noop is great. At various times, I go with any of the SA2-based 'intelligent' options (SavagedZen, brazilianwax, SmoothAss, or SmartAssv2) or the OndemandX/Conservative basic sets. The others have gotten stuck more often and tended to allocate more processor than I think it needs.
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
FBis251 said:
I've always had the best luck with smartassv2. I think it's a good tradeoff between good battery life and quick processor speedups in order to prevent lag, plus I haven't had the issue of the processor locking up while the screen is off.
Click to expand...
Click to collapse
That's usually the one I always fall back on too despite new ones all the time and everything, it's my default now on any ROM.
I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
I have the same problem too. For awhile thought it was to an app I moved to sd card (walgreens). Wasn't as often moving app off sd card.
Sent from my MyTouch 4G Slide using Tapatalk
m3gz said:
I am having some screen issues with my doubleshot. Basically my screen would not turn on but I know everything still works. I am able to listen to music, pick up calls, unlock the phone, etc.
It seems to happen randomly. Pressing the middle button or the power button only makes the buttons glow but doesn't turn on the screen.
Pulling out the battery and forcing the phone to restart solves the problem. Is there a solution or a more graceful way of getting the screen to come back on?
Edit:
Forgot to mention that it happens to my on JellyBean DS and KitKat DS by Emmanuel U.
Was using CM 9.1 by scverhagen and the issue doesn't happen as often. Once a week where has the JB and KK happens atleast once a day.
Click to expand...
Click to collapse
I've seen this happen as well with various roms as well (including 9.1). I currently am using tbalden's 10.1, and haven't seen it in forever. I don't know if he fixed it, or I've just been lucky.
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
m3gz said:
I have a feeling that it might be the minimum frequency processor settings. The default settings that Emmanuel set seem pretty aggressive.
I am going to:
increase my minimum frequency to 540MHz (and incrementally lower it until it becomes unstable)
keep my maximum frequency at 1512 MHz
set CPU governor to ONDEMAND
Battery shouldn't be too much of a problem for me since I upgraded to 3500 mAh.
daswerk, have you tried playing around with your processor settings?
Click to expand...
Click to collapse
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
I keep mine at 1512 too. Low at 192, going to try 384 for a bit. I have not had the problem for awhile though.
Sent from my MyTouch 4G Slide using Tapatalk
Ziida said:
540 minimum sounds a bit high to me unless your phone wasn't stable on stock ROM either. Maybe try 192? You could also try lowering your max to the stock 1.2ghz
Click to expand...
Click to collapse
Thanks for the advice.
I remember having my max frequency at 1512 MHz before so I thought that wasn't a problem.
So far 540 MHz minimum has kept my phone from going blank. I'll try 192 Mhz next
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Saem persun said:
I've tried to set 192 Mhz as a minimum rate - and got black screen anyway.
Click to expand...
Click to collapse
192 MHz worked for me. You can try doing something extreme like what I did to see if it's the minimum frequency. It may decrease battery a bit but it's better than having the annoying black screen. I tried 540MHz as a test frequency.
Not all processors are the equal. So what may work for some may not work for others.
Same problem here. Black screen on Doubleshot with CM 10.1. Made me really concerned when it happened, as I was was reading the hardware maintenance thread earlier today (for fun) so I thought the LCD went.
This is the first time this has happened in the three weeks I had this phone, and I've been on 10.1 for almost a week now.
Because battery life[1] is an issue for me as well, I edged things up only slightly (from 96 MHz to 128), hopefully that will do to the trick. If not, I will try 192 MHz.
[1] Speaking of which, any tricks on keeping battery usage low? I use Deep Sleep Battery Saver which helps out a lot. And I'm selective about my apps (removed Songza because it was hanging around while closed, eating up battery life). GPS stays off, although I keep Wi-Fi and 3G on. It looks like the screen becomes the biggest draw at this point. Any advice would be appreciated.
Since the problem in March, I have upped the minimum frequency to 192mHz. For the longest while I haven't had any issues.
But since I installed my new Anker battery (was on a half-in-the-bag EZO Power 1900mAh), the problem came back, happened twice now, a week apart.
I'm trialing KitKatDS right now, but will probably go back in a week or less due to wakelock (Android OS) issues. Judging by above, when I do I will bump up the minimum even higher. Hard to see the correlation with how the battery will be causing it, but I see no other change.
Upping the lower end frequency seemed to work for a bit but i'm still getting the screen issues. I'm using a 3500mAh battery from China but I'm just doubting that the battery affects the screen.
The correlation of frequency to screen issues could also be coincidental.
m3gz said:
The correlation of frequency to screen issues could also be coincidental.
Click to expand...
Click to collapse
I wonder if the scheduler has anything to do with screen as well, that is, if CM uses a different one from stock?
Sent from my MyTouch 4G Slide using XDA Free mobile app