Related
Is there a negative effect of setting the clock speed lower while screen off? Aside from running really labor intensive tasks?
It just seems like a great way to save battery to me. Right?
The only negative is getting the phone to wake up fast enough when you get an inbound call.
The CFS kernel (which is widely used now) seems to be less able to come out of a deep sleep rapidly than the older "zanfur" OC kernel did.
IIRC, on the older "zanfur" OC kernel, you could set the minimum scaling frequency to 19 Mhz - but with with the CFS kernel, you may need to use a minimum value of 122 Mhz or 245 Mhz.
Set the max scaling speed to 480 or 528 when sleeping. (The max frequency is only rarely used when the phone is sleeping - but you want the phone to pop out of it's low speed state quickly when you power up the screen, or experience an inbound call).
Thanks, Yeah I usually set the max to 480 while sleeping and 480 as min while awake. Battery seems good there.
Originally I was using SetCPU but I have switched to CPUBoost. Most all the kernels in the past few roms I have used are made by conap and he is also the creator of CPUBoost, so I figured they would integrate really well.
Also if I enter anything above the 800 range the phone will have random reboots throughout a few different roms I've tried.
As a note, if I remember correctly, if you have a kernel/ROM that supports the smartass governor, you should be able to use it and not need to have a profile set to underclock while the screen is off, or really need to underclock at all, as I believe it determines for you how much CPU is needed and sets the clock speed accordingly, simply abiding by your max and min speeds you set. Since less CPU is needed when the screen is off, it will automatically adjust accordingly. However, this is just something I've read around the forums, so don't take my word for it
Pokelover980 said:
As a note, if I remember correctly, if you have a kernel/ROM that supports the smartass governor, you should be able to use it and not need to have a profile set to underclock while the screen is off, or really need to underclock at all, as I believe it determines for you how much CPU is needed and sets the clock speed accordingly, simply abiding by your max and min speeds you set. Since less CPU is needed when the screen is off, it will automatically adjust accordingly. However, this is just something I've read around the forums, so don't take my word for it
Click to expand...
Click to collapse
Thanks for the info, I didn't know that. I will assume that's more or less accurate unless Conap or bftb0 chime in.
Pokelover980 said:
As a note, if I remember correctly, if you have a kernel/ROM that supports the smartass governor, you should be able to use it and not need to have a profile set to underclock while the screen is off, or really need to underclock at all, as I believe it determines for you how much CPU is needed and sets the clock speed accordingly, simply abiding by your max and min speeds you set. Since less CPU is needed when the screen is off, it will automatically adjust accordingly. However, this is just something I've read around the forums, so don't take my word for it
Click to expand...
Click to collapse
roirraW "edor" ehT said:
Thanks for the info, I didn't know that. I will assume that's more or less accurate unless Conap or bftb0 chime in.
Click to expand...
Click to collapse
Well, I suppose it could be said that the whole point of any rate governor is to reduce overall power consumption without markedly affecting the user's perception of "responsiveness" or "speed" - however they go about defining those metrics.
OTOH, because there are - what - five different scaling governors available, it is apparent that people have found their own reasons to create new scaling governors; presumably that arose from a dissatisfaction with the behavior of the available scaling governor - or, that different users have differing application workloads, and so they prefer one governor over another.
As Pokelover980 suggests, you could just hand a given rate governor a fixed set of limits (min/max), and be done with it.** For folks that have the time and desire to experiment, I would suggest that: pick a governor and a min/max clock rate and run that way for 2-3 days - no profiles at all. Then pick a different governor with the same min/max clock rate and run that way for another 2-3 days, and see how it goes - maybe not in battery life, because that's hard to measure in a repeatable way, but at least to see if any problems occur coming out of sleep.
Is the "smartass" governor better than all the rest of them? I don't really know. I used it for a little while, but found something I didn't like about it. (But don't take that as conclusive about anything; I doubt that I was doing disciplined testing when that happened). I tend to use either "interactive" or "ondemand", and don't have a strong preference for one over the other.
There probably is some value in keeping things simple. I think that I mentioned before that at one point (back when the CFS kernels were still in a state of flux) I was convinced that using setCPU was exacerbating problems with lock-ups I observed (once every couple of days). Again, though - that was really only my suspicion; I can't really prove it.
bftb0
** I suppose that folks that insist on extreme levels of overclocking ought to use either an overtemp profile or some other means to monitor temperature so that they don't cook their phone.
I Installed SetCPU on the wifes Eris. The smartass governor on CM7 will max out the cpu (to your preset max) if needed. I dont think the smartest thing to do is max out the cpu at 15% batt life. I have 5 different profiles set. One for screen off, charging, < 50%, < 30%, <10%. I use interactive governor vs smartass. Her phone is pretty responsive and I dont hear about issues with it not waking up. Battery life has also increased quite a bit.
Ok - someone help me understand how this thing works. Can I only have three steps? What is the VSel1/2/3? Can I change the governor?
it's here :
http://forum.xda-developers.com/showthread.php?t=898036
That is the app thread but I don't see instructions.
Yes, there are three steps and for each one you can choose the CPU voltage (vsel) and frequency.
You can choose between two governors: performance (always at max freq and voltage) and on demand (freq and voltage scaling).
Sent from my MB525
Ok but how do I know what voltage is best? What frequency is best? I read the item about phone ringing:
________________
update7:
when i set my defy to 300mhz while screen is off then when a phonecall is incoming the defy is so slow that it takes ages for the screen to go on....
sometime it takes 2-3 ring befor i can answer the call
so setvsel set it to maximum speed on phoneringing befor the screen is on!!
________________
Is he saying he did that in code or an action is needed by the user to handle this? Mine still takes 3 seconds for the screen to turn on.
its preety much the same as overclocking cpu on pc ..but easier
just try ...each chip is different ..and it depends on the rom aswell
phone will reboot if ull set it 2low ...or ull get some app closing errors or stuff like that
safe voltages to start would be 300/20 600/40 1000/56 ...then go lower
So if I set it too low then phone will reboot?
What is the safest settings if I am still using stock rom?
Sent from my MB525 using Tapatalk
e-prast said:
So if I set it too low then phone will reboot?
What is the safest settings if I am still using stock rom?
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
Yes if you go too low on the vsel for that frequency then the phone will reboot - just make sure at first you don't have setvsel configured to "apply at boot" until you have discovered your stable settings.
As for stable settings then maybe start with the first vsel & lower it until it reboots then you know it's too low & you need to go up higher by 2 vsel or so.
It would be easier to do each vsel at different times so you know which one causes the reboot.
Just for info my settings are:
300/18
700/32
1100/56
Up_threshold 75%.
I could possibly go lower on the 300 & 700 but I'm happy as they are. The 1100 on mine is set at the lowest stable vsel I could get.
As mentioned all cpu are different & what settings that work for one person may not be any good for another.
Ok thanks
I am still using the default clock but i'm lowering the vsel a bit. I'll start tweaking untill get the best result. I hope I can reach 1000 max. BTW what is the threshold for? Mine still in default.
Sent from my MB525 using Tapatalk
Threshold is the % load that the cpu reaches before it switches to the next higher frequency.
Just for example sake here are my settings. Actually the only one I changed was #3. [email protected] All the rest is left at default. I just wanted a bit of a quicker device, and changing just this one setting gave me what I wanted. Very stable and snappy now. My Quadrant scores are in the low 1700s. (oh and I'm on the official 2.2.1, but nothing else is changed)
How is your battery? Do you use the stability test to determine your lowest values?
sp8y said:
Yes if you go too low on the vsel for that frequency then the phone will reboot - just make sure at first you don't have setvsel configured to "apply at boot" until you have discovered your stable settings.
As for stable settings then maybe start with the first vsel & lower it until it reboots then you know it's too low & you need to go up higher by 2 vsel or so.
It would be easier to do each vsel at different times so you know which one causes the reboot.
Just for info my settings are:
300/18
700/32
1100/56
Up_threshold 75%.
I could possibly go lower on the 300 & 700 but I'm happy as they are. The 1100 on mine is set at the lowest stable vsel I could get.
As mentioned all cpu are different & what settings that work for one person may not be any good for another.
Click to expand...
Click to collapse
Battery lasts a long time for me could get between 2-3 days on a full charge but i normally top up the battery every day and don't let it run out.
As for the stability test i did use it when there was a one built into the setvsel app but not for long. I just adjusted my settings then used the phone for a while to make sure it was ok.
How do I know how high I can go on over clock?
Sent from my MB525 using Tapatalk
Bump
Sent from my MB525 using Tapatalk
Just try it; but generally top frequency is 1200 otherwise you have to set too high vsel with consequences on temperature and stability.
Sent from my MB525
Just working fine, thanks
Hello guys, i have overclocked the cpu at 1100Mhz with 58v and is perfect but i want understand what is the maximum v for stay secure.
I have 1200 at 62
Sent from my MB525 using XDA App
I use
19/300
38/600
50/800
only for the reason - to to keep my Defy, without charging as lons as it possible. now my record is 4,5 day for normal everyday using (30 minuts of wi-fi, 45 minutes of conversations, a little bit games some times, 1-2 hour of reading e-books)
I'm currently debating buying WidgetLocker, but I'm a bit skeptical since I'm not sure how bad it will lag with my current sleep profile. Can any WidgetLocker users possibly shed some light if they think it will lag on my phone? I'll put my profiles below.
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Charging/Full, Priority: 75, 710 max 245 min, ondemand
Battery < 25%, Priority: 50 ,480 max 245 min, ondemand
Screen Off, Priority: 25, 245 max 160 min, ondemand
If my sleep profile would make it lag, would bumping it up to 245 max 245 min help any?
Profile recommendations are welcome as well if theres anything that could be done to improve performance without sapping an excessive amount of battery. I have noticed my phone lags waking up sometimes and occasionally just when it's being used.
I would put your sleep profile at either the 2nd or 3rd highest priority - either right after the overtemp profile, or after the "on charger/full" profile.
my profiles usually look something like this (ordered from highest to lowest priority) :
- temperature (can have more than one; highest (over-)temp has highest priority)
- charging/full
- screen off
- battery (can have more than one; lowest battery % has highest priority)
- battery < 101% (this is the sort of like the "off charger, not overtemp, screen on state)
If the "screen off" profile has a higher priority than all the battery conditions, then all the "battery" conditions certainly can only be effective when the screen is on. (Note that the way you have it now, your < 25% battery condition always "wins" over the screen-off profile)
Also, note that your profiles don't contain anything matching the "off charger, 25% < battery < 101%" condition as they stand - what is controlling that, the default profile?
I'm not sure that there are big gains to be had by ratcheting down the min/max cpu frequency for low battery conditions: when you have the display on, it could well be drawing more power than the CPU - so, if your goal is to save battery, it would make sense to have whatever it is you want "computed" to show up on the screen as quickly as possible - so that you can shut the screen off that much quicker.
For the same reason, if most of the time the phone is on you are just "staring at the screen", and nothing is going on in the background, allowing the rate governor to drop to a low frequency saves you only a little bit (if the screen is really the dominant juice-user in that scenario.)
My GSB v1.6 Eris reports using only 2-3 % overnight - it's screen off profile is set to 160/245 - and I seem to be using the "interactive" governor on all profiles ... but I also use Toggle2G with a 10-minute sleep onset delay.
( Probably that means that I don't get email notifications as soon as I could, but that doesn't bother me much - I get them as soon as I unsleep the phone. If you are the type of person that needs to look at their phone every time your facebook updates, then Toggle2G perhaps isn't for you.)
I can't prove it, but so long as you don't peg your CPU minimum frequency too high, and rely on the rate governor to do it's job, most power savings are likely to come from managing the radio state and the screen brightness.
bftb0
What percentages do u recommend bftb0
Sent from my Ginger Tazz using Tapatalk
bftb0 said:
I would put your sleep profile at either the 2nd or 3rd highest priority - either right after the overtemp profile, or after the "on charger/full" profile.
my profiles usually look something like this (ordered from highest to lowest priority) :
- temperature (can have more than one; highest (over-)temp has highest priority)
- charging/full
- screen off
- battery (can have more than one; lowest battery % has highest priority)
- battery < 101% (this is the sort of like the "off charger, not overtemp, screen on state)
If the "screen off" profile has a higher priority than all the battery conditions, then all the "battery" conditions certainly can only be effective when the screen is on. (Note that the way you have it now, your < 25% battery condition always "wins" over the screen-off profile)
Also, note that your profiles don't contain anything matching the "off charger, 25% < battery < 101%" condition as they stand - what is controlling that, the default profile?
I'm not sure that there are big gains to be had by ratcheting down the min/max cpu frequency for low battery conditions: when you have the display on, it could well be drawing more power than the CPU - so, if your goal is to save battery, it would make sense to have whatever it is you want "computed" to show up on the screen as quickly as possible - so that you can shut the screen off that much quicker.
For the same reason, if most of the time the phone is on you are just "staring at the screen", and nothing is going on in the background, allowing the rate governor to drop to a low frequency saves you only a little bit (if the screen is really the dominant juice-user in that scenario.)
My GSB v1.6 Eris reports using only 2-3 % overnight - it's screen off profile is set to 160/245 - and I seem to be using the "interactive" governor on all profiles ... but I also use Toggle2G with a 10-minute sleep onset delay.
( Probably that means that I don't get email notifications as soon as I could, but that doesn't bother me much - I get them as soon as I unsleep the phone. If you are the type of person that needs to look at their phone every time your facebook updates, then Toggle2G perhaps isn't for you.)
I can't prove it, but so long as you don't peg your CPU minimum frequency too high, and rely on the rate governor to do it's job, most power savings are likely to come from managing the radio state and the screen brightness.
bftb0
Click to expand...
Click to collapse
Never a post that isn't enlightening from you.
Yes my default clock profile (710 max 160 min, might bump it up to 245 min) is the one managing the clock rate when the phone is off the charger. As for Toggle2G that might not be a bad idea, I keep my phone on Airplane Mode most of the time I'm at school (horrible signal = battery draining out the wazoo) but it might not be a bad idea to have for when I'm not at school. Of course I'm not sure I would need it though since I have an extended battery, maybe something to experiment with.
As for profiles, something like this?
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Screen Off, Priority: 75, 245 max 160 min, ondemand
Charging/Full, Priority: 50 ,710 max 245 min, ondemand
Battery < 25%, Priority: 25, 480 max 245 min, ondemand
If you are already using Airplane Mode because of poor signal conditions, Toggle2G won't help much - the battery will drain just looking for voice/1xRTT service (not to mention 3G). I have a pretty good signal where my phone spends most of it's time, including overnight ( -70 dBm to -80 dBm )
ToastPwnz said:
As for profiles, something like this?
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Screen Off, Priority: 75, 245 max 160 min, ondemand
Charging/Full, Priority: 50 ,710 max 245 min, ondemand
Battery < 25%, Priority: 25, 480 max 245 min, ondemand
Click to expand...
Click to collapse
Seems OK. I have a couple of battery profiles where I slowly drop the max frequency, and make the default condition explicit by using a "battery < 101%" profile, as in:
Pr Min/Max Governor Condition
90 245/480 interactive Temp > 50.0 C *audible alarm
80 245/604 interactive Temp > 45.2 C
70 528/710 interactive Charging
60 160/245 interactive Screen Off
50 160/480 interactive Battery < 15%
40 160/528 interactive Battery < 25%
30 245/604 interactive Battery < 40%
20 480/710 interactive Battery < 67%
10 480/729 interactive Battery < 101%
I'm not sure this really produces much effect in terms of battery savings, though - for instance, it runs counter to my suggestion (above) that it might actually hurt to slow things down with reduced battery reserve because you just end up with the screen on longer.
I'll also mention that for a period of time I was actually convinced that using setCPU was causing random freeze-ups when used with certain combinations of the CFS kernel, governor choice, and min frequency - and so I didn't even have it installed on my phone. I only recently put setCPU back on my phone because I was noticing that CPUboost settings did not seem to be sticking even within the same session (perhaps I was misinterpreting something, I'm not sure). No random freeze-ups lately.
Because some of the things which actually drain the battery - cell radio, screen time on & brightness, 3G activity level, etc., are so highly variable, I'm not sure that any of the reports on this forum (including mine) can be regarded as particularly meaningful. It takes real dedication to the task (creating reproducible signal conditions and compute/activity workloads) to be able to produce quality data about battery usage. Most folks need to use their phones throughout the day (moving continuously from place to place with widely varying signal levels), so they can't set their phones aside to do such things; their usage is not repeatable, so it is hard to believe them, whether they are saying "great battery life", or "battery life sucks!".
Heck, even at night, when my phone isn't "doing anything", (which you would think would be sort of "reproducible") if I move it 8 inches one way or another on the nightstand, my signal level can change by 10 dBm. That means that if I don't use Airplane Mode overnight, it is really not too meaningful to compare "configuration X" to "configuration Y" on successive nights - because the battery usage by the radio is not reproducible.
I guess the bottom line is - if you can get a full day out of the phone, be happy with that; it's just about what the phone was designed to do.
bftb0
bftb0 said:
If you are already using Airplane Mode because of poor signal conditions, Toggle2G won't help much - the battery will drain just looking for voice/1xRTT service (not to mention 3G). I have a pretty good signal where my phone spends most of it's time, including overnight ( -70 dBm to -80 dBm )
Seems OK. I have a couple of battery profiles where I slowly drop the max frequency, and make the default condition explicit by using a "battery < 101%" profile, as in:
Pr Min/Max Governor Condition
90 245/480 interactive Temp > 50.0 C *audible alarm
80 245/604 interactive Temp > 45.2 C
70 528/710 interactive Charging
60 160/245 interactive Screen Off
50 160/480 interactive Battery < 15%
40 160/528 interactive Battery < 25%
30 245/604 interactive Battery < 40%
20 480/710 interactive Battery < 67%
10 480/729 interactive Battery < 101%
I'm not sure this really produces much effect in terms of battery savings, though - for instance, it runs counter to my suggestion (above) that it might actually hurt to slow things down with reduced battery reserve because you just end up with the screen on longer.
I'll also mention that for a period of time I was actually convinced that using setCPU was causing random freeze-ups when used with certain combinations of the CFS kernel, governor choice, and min frequency - and so I didn't even have it installed on my phone. I only recently put setCPU back on my phone because I was noticing that CPUboost settings did not seem to be sticking even within the same session (perhaps I was misinterpreting something, I'm not sure). No random freeze-ups lately.
Because some of the things which actually drain the battery - cell radio, screen time on & brightness, 3G activity level, etc., are so highly variable, I'm not sure that any of the reports on this forum (including mine) can be regarded as particularly meaningful. It takes real dedication to the task (creating reproducible signal conditions and compute/activity workloads) to be able to produce quality data about battery usage. Most folks need to use their phones throughout the day (moving continuously from place to place with widely varying signal levels), so they can't set their phones aside to do such things; their usage is not repeatable, so it is hard to believe them, whether they are saying "great battery life", or "battery life sucks!".
Heck, even at night, when my phone isn't "doing anything", (which you would think would be sort of "reproducible") if I move it 8 inches one way or another on the nightstand, my signal level can change by 10 dBm. That means that if I don't use Airplane Mode overnight, it is really not too meaningful to compare "configuration X" to "configuration Y" on successive nights - because the battery usage by the radio is not reproducible.
I guess the bottom line is - if you can get a full day out of the phone, be happy with that; it's just about what the phone was designed to do.
bftb0
Click to expand...
Click to collapse
Hm, I might try those profiles with a few tweaks, or I might just end up bumping up my screen off profile in terms of priority, not sure yet.
Another question, what do you suggest as far as governors go? I seem to have the most success with ondemand, but I've never tried interactive. I learned the hard way that smartass lags my phone horribly, not sure why.
With my extended battery, I've gone roughly 65 hours total uptime with about 45% battery left with moderate use. I guess I should be proud of that.
ToastPwnz said:
I'm currently debating buying WidgetLocker, but I'm a bit skeptical since I'm not sure how bad it will lag with my current sleep profile. Can any WidgetLocker users possibly shed some light if they think it will lag on my phone? I'll put my profiles below.
Code:
Temp > 38.6C, Priority: 100, 480 max 160 min, ondemand
Charging/Full, Priority: 75, 710 max 245 min, ondemand
Battery < 25%, Priority: 50 ,480 max 245 min, ondemand
Screen Off, Priority: 25, 245 max 160 min, ondemand
If my sleep profile would make it lag, would bumping it up to 245 max 245 min help any?
Profile recommendations are welcome as well if theres anything that could be done to improve performance without sapping an excessive amount of battery. I have noticed my phone lags waking up sometimes and occasionally just when it's being used.
Click to expand...
Click to collapse
Wow you actually set a max of 480 for merely being over 38.6C??? I think that's a bit extreme. Other than that your profiles aren't that different than what I use (using Conap's CPUBoost tool, what are you using?).
I love WidgetLocker, and yes it's one of the only two apps I've actually purchased. Lag or not I wouldn't trade it.
The only "issue" (not necessarily WL's fault) is that using the Theme Chooser under GB ROMs, at least with the Speedometer Battery theme, definitely causes WL to lose what widgets are on it between reboots, although not always every reboot, but most of them.
It's confirmed that the solution is to not use Theme Chooser, at least with the Speedometer Battery theme. I don't know for sure if other themes cause it as well, but it's easily reversed (go back to the stock theme) if it does.
roirraW "edor" ehT said:
Wow you actually set a max of 480 for merely being over 38.6C??? I think that's a bit extreme. Other than that your profiles aren't that different than what I use (using Conap's CPUBoost tool, what are you using?).
I love WidgetLocker, and yes it's one of the only two apps I've actually purchased. Lag or not I wouldn't trade it.
The only "issue" (not necessarily WL's fault) is that using the Theme Chooser under GB ROMs, at least with the Speedometer Battery theme, definitely causes WL to lose what widgets are on it between reboots, although not always every reboot, but most of them.
It's confirmed that the solution is to not use Theme Chooser, at least with the Speedometer Battery theme. I don't know for sure if other themes cause it as well, but it's easily reversed (go back to the stock theme) if it does.
Click to expand...
Click to collapse
I'm still using SetCPU.
Yes I do knock it down that far, my phone heats up like crazy while I'm at school (terrible signal) and once it reaches 100F I could use the phone as a hand warmer and if I take off the back I can smell burning plastic. Maybe thats normal for the Eris, but I use it just as a precautionary measure.
ToastPwnz said:
Another question, what do you suggest as far as governors go? I seem to have the most success with ondemand, but I've never tried interactive. I learned the hard way that smartass lags my phone horribly, not sure why.
Click to expand...
Click to collapse
I haven't spent much time trying to figure out the "best" governor - I tend to use either "ondemand" or "interactive" without giving it too much thought. I tried smartass for a while, and remember being not happy with it for some reason or another; but I don't remember what those reasons were. ( It might have been nothing more than "choppiness" of scrolling behaviors. )
bftb0 said:
I haven't spent much time trying to figure out the "best" governor - I tend to use either "ondemand" or "interactive" without giving it too much thought. I tried smartass for a while, and remember being not happy with it for some reason or another; but I don't remember what those reasons were. ( It might have been nothing more than "choppiness" of scrolling behaviors. )
Click to expand...
Click to collapse
Now my curiosity is getting the best of me. Whats the difference between ondemand and interactive? (Sorry for all my questions <.<)
ToastPwnz said:
Now my curiosity is getting the best of me. Whats the difference between ondemand and interactive? (Sorry for all my questions <.<)
Click to expand...
Click to collapse
I don't know for sure...
... but I can tell you that the exact answer to your question is right here.
bftb0 said:
I don't know for sure...
... but I can tell you that the exact answer to your question is right here.
Click to expand...
Click to collapse
Hidden within that garbled mess.
I kid, I think I found the explanation you had in mind, and from what I can find the only major difference is that interactive is more aggressive then ondemand. I'm not sure if I should take that governor for a test run or not, I do notice that my phone lags when waking up occasionally. It kind of sounds like switching to interactive might help that.
ToastPwnz said:
I'm still using SetCPU.
Yes I do knock it down that far, my phone heats up like crazy while I'm at school (terrible signal) and once it reaches 100F I could use the phone as a hand warmer and if I take off the back I can smell burning plastic. Maybe thats normal for the Eris, but I use it just as a precautionary measure.
Click to expand...
Click to collapse
You probably have your reasons, but when you're at school, why don't you put it in Airplane mode and just take it off it between classes to check emails and such? Save your battery and the heat of your Eris a bunch.
Or do you and you just use the temperature profile as a fallback in case you forget to put it back in Airplane mode?
roirraW "edor" ehT said:
You probably have your reasons, but when you're at school, why don't you put it in Airplane mode and just take it off it between classes to check emails and such? Save your battery and the heat of your Eris a bunch.
Or do you and you just use the temperature profile as a fallback in case you forget to put it back in Airplane mode?
Click to expand...
Click to collapse
You are quite correct sir. That and my I bump my phone occasionally, and I think two days ago it turned on and I didn't notice, and when I checked it I noticed over the course of about 2-3 hours it lost 14% and was at around 95ish F.
I do keep it in Airplane Mode when I'm not using it (and it's off as well), but the profile is pretty much just a precautionary measure.
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
I'm using the Oxygen ROM on an HTC Desire HD. When I leave my phone alone for a while and come back to unlock it, performance is often slow for 20 seconds to the point where swiping between launcher screens is sluggish. After this time it goes right back up to normal speeds.
Is this possibly related to the CPU settings in my ROM? The settings are available governors - interactive, min CPU - 245MHz, max CPU 1024 MHz. My guess is that when the phone's idle it goes down to 245MHz and takes a while to get back up to regular speeds. Am I looking in the right place and how much would increasing min CPU frequency affect my battery life?
Thanks
It relly shouldn't affect battery life that much. You could try raising the Min speed to the 300's.