Theory Less RAM, longer battery life? - Desire General

This is just an idea, but the android phones that seem to have longer battery lives all have low RAM compared to the higher end devices.
Are we needlessly draining power by loading more apps into our larger RAM? Since it isn't a persistent memory form it will always pull a current when in use.
Therefore the larger the memory, the more current would be drained. I don't know how much of an effect this would have but is there anyway we can control how much RAM the desire has access to in order to test?

Well I think its probably more to do with high end phones loading more apps at startup, having bigger brighter screens and having bigger power hungry processors. The power for ram would be very small.

Not necessarily, phones like the Samsung Spica have good battery life & comes with a 800Mhz processor.
I just want to know if there is a way of fashioning a kernel at 256-384MB. People have played around for a long time with undervolting with little luck so why not this?

always worth a try. Any saving on the desire battery is a bonus I am nearly always on 30% after a day of light use.

Dynamic memory modules (ram) use full power regardless of load or current free/used space.
Sent from my HTC Hero using XDA App

Related

used RAM and battery life

Is there a relationship between the amount of used RAM and battery life? My TP2 boots up with 41% of used RAM and increases to about 55% in the course of the day, without using either cleanRam or RAM Sweeper. Using either of these two keeps the used RAM below 46%.
hi, im not too technically experienced but yeah id say there is link between battery power consumption and ram used. I too experience the ram increase but like you am not too sure as to the cause of this. I have the habbit of running CleanRam every now and then to free up some ram but often wonder whether that ram being used would consume less battey than having it being cleared up by a program!

[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.

[Q] Paradox with underclock & battery savings, does it actually hurt? SetCPU, etc.
In theory, using SetCPU or other underclocking app to reduce CPU clock should reduce the power draw from the CPU, therefore reducing battery consumption.
However, underclocking does not reduce the amount of work that needs to be done. That is to say, whatever app or kernel processing that needs to be done will still be done. When UC'ed, they will be done at a slower pace, therefore taking longer time. In some cases, the UI becomes sluggish, requiring more user interaction time as well.
If, at 1Ghz, a process takes 10 seconds to complete and requires 10mA per second. This task should consume 100mA. By underclocking to 500mHz, perhaps the CPU takes only 6mA, but the task will require 20 seconds to complete. Now the task actually takes 120mA (plus the longer screen on time).
Is my theory sound?
Also, does the constant scaling itself consume power?
As far as I know, Froyo is supposed to scale the CPU anyway. So why underclock? Does it actually work or does it hurt the battery life?
Input please!
Thanks.
Edit: I know the function of CPU speed vs. efficiency vs. battery drain is never linear, and each situation has a different break-even point, but I'm curious the general application of underclocking within the Android environement and its effect on battery life, and more specifically, the Evo.
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNFlNlZCm-gnvD1PzEsDezCIPeA8jQ
Sent from my PC36100 using Tapatalk
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
snovvman said:
Interesting stuff... Take a look at this thread:
[ROOT] Using SetCPU + Perflock Disabler to Save Battery, Underclock
The data seem to suggest that underclocking an Evo at idle yields real results. I would think that this can only work if there is not a lot of background/idle tasks going on?
Click to expand...
Click to collapse
both pics depicts very different device usages. not a fair comparison imo.
quocamole said:
both pics depicts very different device usages. not a fair comparison imo.
Click to expand...
Click to collapse
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
snovvman said:
Yea I went through and read the whole thread. I'm now even less convinced that SetCPU provides any tangible battery benefits at all.
Click to expand...
Click to collapse
Do you think i am right on any part of which i said or am i talking out of my arse lol
A microprocessor does not live by its clock alone. lol
It can cycle through a huge math operation, which is loaded into its registers lickity split with a fast clock. It will have to wait while the memory/code of the programs it runs are loaded either into its cache memory or into execution space. So in calculating theoretical energy use, you got to figure the bus speed, as well as the type of operations the processor is doing.
Golly, ( pronounced like a resident of Mayberry) the bus is key on loading programs to be run. What's the bus clock triggered off? That's the key. You don't want the bus to slow while slowing the cpu. If you can cycle the processor while it prefetches then you've got optimal use, providing it isn't thrashing.
Google cpu wait states for bus synchronization
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
In practice, I haven't seen all that much of a difference.
iitreatedii said:
i'm a regular dude with a phone, but im educated...that being said im sure your aware of the diminishing marginal utitlity law. For example if me and you can mow a lawn in 2 hours, and we got one more guy, we can do it in in less than two...Bu you eventually reach a breakoff point where it is hurting you and those extra guy(s) are not needed and acutally slow down the process or are just a waste. Same thing here, although i am not sure of the numbers, im positive there is a sweet spot for underclock and if you go too low it actually is a waste or hurts battery life. It also could be in the middle meaning, im going to make up numbers. 1ghz uses 100 Mah in 10 seconds. 800 mhz used 50 mah. 900 uses 60 mah. Now, the difference ratio of battery usuage and spees would lean you towards using 900 because if you relate this to sales on products or even anything, for lack of better words this setting is the best abng for your buck...my 2 cents
Click to expand...
Click to collapse
iitreatedii said:
Do you think i am right on any part of which i said or am i talking out of my arse lol
Click to expand...
Click to collapse
What you wrote makes sense and the concept is sound. I just wish we knew what that sweet spot is, although I think it changes constantly based on load, code, and operational requirements.
With the two posts above, it would seem like phone manufactures would do everything they can to optimize efficiency. Having SetCPU loaded for 24 hours, I too, can say that I have not seen a huge difference...
Noxious Ninja said:
This is basically the reason HAVS is supposed to be better than static scaling and underclocking. With HAVS, voltage is based on workload as well as clock speed, so you should get the benefits of running fast/idling more often combined with the benefits of using as low of a voltage as possible. As long as you don't have something pegging the CPU at 100% all the time in the background, it should, in theory, work better.
Click to expand...
Click to collapse
Does the stock HTC kernel, 2.6.32 "#11" have/use HAVS?

[Q] overclock dameges hardware but does it damage device or just battery

overclock dameges hardware but does it damage device or just battery
The Hardware is the Device or the battery....
every thing you can touch is hardware :3
I've never overclocked a phone from myself... Unfortunately previous experiences with PC overclocking have ended badly with a lot of components breaking, if you know what your doing, I've found the results can be more than worth the risk!
Overclocking your phone will put more stress on your hardware, CPU will attempt to run more bits of information than it's designed for, battery will be pushing out more power to keep up with hardware demand, etc...etc...
Computers are easier to handle in terms of overclocking because you can modify hardware such as liquid cooling or bigger fans to support the extra heat generated from your adjustments. The strain on the hardware will always be there but it's easier to manage than portable devices. Phones on the other hand are restricted in terms of cooling; you may notice a larger amount of heat generated when you're playing games or running Google Maps. In most cases, always remember that heat = bad in terms of most things technology related... Unless it's a toaster oven.
I had a Motorola Droid for over 2 years (before my SE switch) and I had overclocked it to around the 1GHz marker (550MHz stock), the only thing that kept my Droid from blowing up was using a Ultra Low Voltage Kernel and Memory Management. While that may seem reassuring I know in the back of my head that I'm still cutting away at the overall life cycle of my hardware. My phone would heat up anytime I had to travel with GPS and that only reminded me that my phone would explode at any moment... Well, not really explode but that would've been a cool experience.
It's your choice to overclock your phone or not, just keep in mind that even while using a LV Kernel and managing your memory the stress on the CPU, Battery, and RAM is there. (I personally believe) Hardware now-a-days can handle the stress and most likely you'll be getting a new phone in 2-3 years time anyway.
n0_face said:
Overclocking your phone will put more stress on your hardware, CPU will attempt to run more bits of information than it's designed for, battery will be pushing out more power to keep up with hardware demand, etc...etc...
Computers are easier to handle in terms of overclocking because you can modify hardware such as liquid cooling or bigger fans to support the extra heat generated from your adjustments. The strain on the hardware will always be there but it's easier to manage than portable devices. Phones on the other hand are restricted in terms of cooling; you may notice a larger amount of heat generated when you're playing games or running Google Maps. In most cases, always remember that heat = bad in terms of most things technology related... Unless it's a toaster oven.
I had a Motorola Droid for over 2 years (before my SE switch) and I had overclocked it to around the 1GHz marker (550MHz stock), the only thing that kept my Droid from blowing up was using a Ultra Low Voltage Kernel and Memory Management. While that may seem reassuring I know in the back of my head that I'm still cutting away at the overall life cycle of my hardware. My phone would heat up anytime I had to travel with GPS and that only reminded me that my phone would explode at any moment... Well, not really explode but that would've been a cool experience.
It's your choice to overclock your phone or not, just keep in mind that even while using a LV Kernel and managing your memory the stress on the CPU, Battery, and RAM is there. (I personally believe) Hardware now-a-days can handle the stress and most likely you'll be getting a new phone in 2-3 years time anyway.
Click to expand...
Click to collapse
The life cycle on phones today is far longer then you would expect. Every processor can handle more speed then the manufacturer clocked it at but they will never release a device with a processor at its full potential. Unless your taking your xperia play and o/c to constant 2ghz you really will never see a degrade in its life. Even o/c'ed the phone will outlast a 2 yr contract.
I recently went back to my OG Droid because my Xplay is torn apart. My droid is 125 min - 1300 max and had the device for 3 years. It have always used the 125 -1300 max with regular voltage with no profiles, yes if your o/c and using navigation its gonna heat up, the droid heats up at 550mhz on navigation with stock kernel , but then again when navigating I would always underclock to keep the heat down. It was never gonna blow up and it will run another few years im sure, its a trustworthy backup !
With all the phones I've had , never had a problem with overclocking , no damage to device or battery, except reboots if clocked to high or reboots if not enough voltage (every device and processor are different though, even the ones with same make and model) which is why you should still be careful, you could get a device that just won't like anything you do to it, but I've never had that problem
it really depends how much you overclock it. most cpus are underclocked especially in phones for battery life reasons. ive been running by pc at about 130% for two years with no issues. now if you double the speed 2ghz (1.9Ghz doomlord kernel) that would mess up you device super fast lol

[Q] My HTC One V drains battery fast and lag

HELP EVERYONE
MY HTC ONE V drains faster even in normal use.
I just use the phone for texting
Wifi OFF
Data OFF
GPS and Location OFF
Bluetooth OFF
from 77% after five hours it became 39%
and also is the HTC One V lag? is it normal? how to run the device so smooth?
THANK YOU IN ADVANCE EVERYONE FOR HELPING ME. GRATEFUL :")
Def not normal. My battery with everything on WiFi, sync etc. And playing music for 4 hours my battery is at 72 after 10 hours
Sent from my HTC One V using xda premium
You have an app that uses the cpu too much = it eats a lot of battery.
Yea true! Some app is sucking the juice off your battery! See if you have some background app running which is trying to connect to the Internet (Since you have both data n WIfi off). Usually these apps eats up a lot of CPU speed. Could explain the lag issue too
Also does you phone heat up?
Great battery life on this phone. Better than most I've tried. Watch what apps you have installed as well. They might be tapping the juice in the background.
Sent from my HTC One V using XDA
yep something is draining ur battery and eating lot of ram
wt free ram ua having?
and if u use swift key x thn think twice it uses more thn 3mb ram when u nt using 50+ whn ua using
soo think ovr it
dnt keep screen brightness to max
it will drain juice twice faster whn ua at home keep it low and when out 25% is enough to make u see the screen in bright daylight
Sent from my HTC One V using xda premium
paarthdesai said:
yep something is draining ur battery and eating lot of ram
wt free ram ua having?
and if u use swift key x thn think twice it uses more thn 3mb ram when u nt using 50+ whn ua using
soo think ovr it
dnt keep screen brightness to max
it will drain juice twice faster whn ua at home keep it low and when out 25% is enough to make u see the screen in bright daylight
Sent from my HTC One V using xda premium
Click to expand...
Click to collapse
Just keep it at auto-brightness...
Sent from my HTC One V using XDA
Yes I must point out that the battery life on this phone as I have observed is quite above average.
RaceAce said:
Yes I must point out that the battery life on this phone as I have observed is quite above average.
Click to expand...
Click to collapse
I definitely agree on that. At this day and age of smartphones and their battery lives, this phone is rather exceptional.
Use apps like Watchdog and Wheres is my droid power to check what is using more cpu/battery! And remove it or find a alternative
Sent from my HTC Desire using XDA
Its always better to install apps which are without ads (mostly freewares are like that only). Keep the brightness at optimum coz its the screen which uses most of the battery.
The more the softwares are running at a moment, the more the RAM is used and hence the battery runs out qiuckly.
Dont keep wi-fi or internet connectivity open always.
Or else u can install third party softwares like Juicedefender or Easy Battery Saver.
Oh and most importantly NO TASK KILLERS!
Sent from my HTC Desire using XDA
iamsonal said:
Its always better to install apps which are without ads (mostly freewares are like that only). Keep the brightness at optimum coz its the screen which uses most of the battery.
The more the softwares are running at a moment, the more the RAM is used and hence the battery runs out qiuckly.
Dont keep wi-fi or internet connectivity open always.
Or else u can install third party softwares like Juicedefender or Easy Battery Saver.
Click to expand...
Click to collapse
Or you can install the program AdFree, set the adress ip for ads to be ignored and you will have your phone ad free .
And those softwares "juicedefenders" are good on a short term but on the long run it causes problems.
Use it as stock without any programs that help you to have more battery or **** like this..
Check the battery usage through Settings > Power > Battery use.
No need to use a third party app for this (unless you've removed this by any means).
Sometimes software issues cause these problems on the phone (even on the stock ROM). Common culprits are "Phone is idle", "Inactive" and "Android system". If these are reporting battery use above ~10% (and you haven't actually had the phone inactive for most of the time), the problem should be resolved with a factory reset.
Otherwise, unless you've tampered with the bootloader this would be covered under the 24 month manufacturer's warranty (12 outside EU) and the device should be sent in for a battery swap / given back to retailer as DOA.
Also, the device isn't the fastest one. The processor is running at 1Ghz with 512Mb of RAM to go along with it. The solution is to load a kernel with overclocking capabilities (Titanium for example) and crank up the CPU to 1,5 or 1,7 GHz. I would assume all of them can run 1,5 GHz as I suspect the processors are actually underclocked to keep battery life long.
Obviously this would reduce your battery life, but having less than 24 hours of battery life on an unmodified One V is what I would call poor unless you are a heavy user.
I hope this helps.
mysdavey said:
Check the battery usage through Settings > Power > Battery use.
No need to use a third party app for this (unless you've removed this by any means).
Sometimes software issues cause these problems on the phone (even on the stock ROM). Common culprits are "Phone is idle", "Inactive" and "Android system". If these are reporting battery use above ~10% (and you haven't actually had the phone inactive for most of the time), the problem should be resolved with a factory reset.
Otherwise, unless you've tampered with the bootloader this would be covered under the 24 month manufacturer's warranty (12 outside EU) and the device should be sent in for a battery swap / given back to retailer as DOA.
Also, the device isn't the fastest one. The processor is running at 1Ghz with 512Mb of RAM to go along with it. The solution is to load a kernel with overclocking capabilities (Titanium for example) and crank up the CPU to 1,5 or 1,7 GHz. I would assume all of them can run 1,5 GHz as I suspect the processors are actually underclocked to keep battery life long.
Obviously this would reduce your battery life, but having less than 24 hours of battery life on an unmodified One V is what I would call poor unless you are a heavy user.
I hope this helps.
Click to expand...
Click to collapse
Actually, a good kernel can improve battery life even if you overclock your cpu. HTC's kernel doesn't come with all the tweaks available for volting and battery life. So if a good dev makes a good kernel, the battery should be the same as running on stock, but with faster performances. Adi_Pat has done a great job with his kernel. I was running it for 2 days until I needed to get a replacement for my phone and now I am waiting to get a new one so I can run it again. I even overclock it at 1.9 ghz and run it for 1 full day and after almost 8h of wifi on, the battery still had 50%. So if you don't have an app that kills your juice, you have definitely a poor battery built in.
does it lag
it was going to buy this phone but saw this vid /watch?v=JptIYZl8qmE that said it was very lag. do you think i should buy this or the sony arc s. plz help
I had some similar issues until I did the following:
Run the battery completely dead until the phone shuts itself off, then put it on the charger with the phone off. Charge it until it is at 100%. Take it off the charger and turn it on. Turn it off again, put it back on the charger until the LED is green, then turn it on again. This helps Android to calibrate the battery.
Install Quick System Info and see what apps are running and how much resources they are using. Also, close all apps, then go into Settings>Apps>Running and see what is running. Look for any apps that shouldn't be running and uninstall them. You have something running in the background and need to get rid of it, this will help you do that.
Uninstall Swiftkey X or Thumbs Keyboard or any other keyboard apps you put on there. Uninstall any weather/clock widgets like HD Widgets or Animated Weather. Use the stock keyboard and stock weather widget (they both work pretty well).
After doing all of this I consistently get home after 10 hours from work with about 60% after moderate usage. I also have almost no lag unless I am playing a more graphically intensive game. Couldn't be happier.

[Q] First timer - Pl suggest ROM upgrade to improve battery

Hello Champs.. I am first time user to this forum so pls excuse any idiot questions if it may seem.
I tried to go through threads to find answers but got completely confused, so though to put my question in simple words here.
I have Desire HD running task killer and Juice defender ultimate with extreme power saving option set and also optimized settings but still my phone don't last more than a day of normal usage. I just check emails, read news and call.. I do not play games and use any CPU intensive app. Phone is not rooted and running 2.3.5v of android
One of my friends told me after flashing ROM, battery power is improved by 40% in case of his tablet, so I am wondering if there is any suggestion for me to use for my Desire HD mobile. I have tried all options at application and settings level to improve the battery life.
As I am not too techincal in this field, if someone could write me few high level steps from start to end to get better battery life ROM and / or jellybean on Desire HD, I'll try to find out low level details of those steps in this forum and root (and flash) my mobile.
My sole requirement is to get as much battery as possible and if possible, some latest android version (4.1 or 4.2) to avail the new features.
Also, would there be an option to take the snapshot of current mobile setup in case if rooting / flashing goes wrong, I could revert back to the current version without loosing settings / data.
Thanks for your help.
two things, go to settings>about phone> battery
Or something like that. Take screenshots of your battery consumption, and the amount of time for each. Without that we can't know what's really causing your battery drain.
That said, a day of use will pretty much wind down your phone, the DHD has a very poor battery, decent sized screen, and most modern smartphones don't last terribly long anyways. However, you said you weren't using it too hard, so I'm not sure what it could be
As for juice defender, make sure that the intervals are set to no less than 15 minutes. 10 minutes pushing it. if you set it to 5 minutes, your phone will constantly be waking up from sleep (ultra battery saving mode), and constantly enabling and re-enabling radio. That'll cause more drain than it will save. At 15 you'll notice definitive increases, and at greater your battery will only get better.
Get rid of the task killer, or disable autotask killer and keep task killing to an absolute minimum. Never kill all your user apps at once. Kill only very large resource hogs (e.g. after playing a game, kill it). An autotask killer is very bad for your phone, and for your battery. Linux naturally tries to keep as many processes 'running' or cached in the background, using up a lot of your ram- it makes multitasking better, so in linux this is a good thing. With windows, it does the opposite, and if you run out of RAM you're screwed. A task killer will try to ruin that behavior, and in the end both performance and battery life will suck. It hurts battery life because after you kill that app, it'll just restart itself in the background- using more CPU therefore battery. Plus it also wakes your phone up from sleep when it needs it. I would only recommend a task killer for a phone with 512mb of RAM.
If it's an older battery, you could also have lost a lot of it's charge. I recommend installing battery monitor widget, and letting it run in the background. It'll estimate your mAH (battery capacity). If it's over 1,000, you're fine. If it's around 800, not bad, still doable. If it's at around 600, I would recommend going in for a replacement battery. I'm using an Anker 1500 (amazon), and I highly recommend it. Mugen 1600 is very good one, but it'll cost you a lot more money. I would not recommend an original HTC one.
finally, installing a custom ROM may or may not help battery life. With HTC Sense based ROMs, I've noticed a battery increase. In AOSP (unmodded, as google intended) gingerbread ROMs, you'll also notice a battery increase. With AOSP ICS, JB4.1.2 and 4.2.1 battery life is hit and miss, some ROMs will get you better battery, some will get you worse. You'll need to experiment around with it.
Also, yes you can backup everything after you install a custom recovery. I recommend looking up AAHK (advanced ace hack kit) on google and youtube, as well as rooting and S-OFF in general on youtube.
Thanks for your reply... Really appreciated. I'll look at the suggestions and see if it is unnecessary to root if 1 day battery is expected.
Do you think recommended high power battery actually improves usage time or people just compare their used up battery with new high capacity ones and think they hv got more juice in it. If high capacity ones really give another 2-3 hours of browsing as compared to OEM 1230 mah battery, I would rather buy it instead of flashing Rom.
Sent from my HTC Desire HD A9191 using xda app-developers app

Categories

Resources