my infuse 4g always uses a lot of resources and always slows down my phone. when i go to free up the memory it only closes like 2-3 apps and only frees up a couple of megs. besides rebooting is there any other way that i can free up more memory on my phone so that it doesn't slow down? also is there any way to clear start up programs from starting when i boot my phone. kind of like "msconfig" on a windows machine? any help would be awesome. i just cleared my RAM and it was at 287MB and it only took it to 286MB. earlier it was over 300MB and did hardly anything. and yes i do stop all apps before i do anything like clearing memory. please help.
try NetQin app from market
thats a nice app and all but doesnt seem to do much. do you think that it is my widgets that are running and sucking up a lot or resources? also what about removing applications from startup?
Thanks
I'd recommend not closing anything unless it's giving you trouble. The OS will typically work out its kinks in memory usage if allowed to. Running apps alone shouldn't really bog down your device. I have 3 recommendations.
1. Wipe cache/dalvik cache in recovery
2. Get Watchdog (it'll tell you if an app is using more resources than it should - I have my cpu threshold set to 30%).
3. Purchase Autostarts (an excellent app that allows you to control what apps start up. I use it and it works really well.).
Also consider checking your sync settings (for apps that allow it). If some refresh intervals are too frequent, it could force an app to stay active and take up resources.
Simba501 said:
Also consider checking your sync settings (for apps that allow it). If some refresh intervals are set high enough, it could force an app to stay active and take up resources.
Click to expand...
Click to collapse
Can you explain it in more details... i didn't understand it correctly..
if we keep the refresh interval high.. it will eat more resourcess?
if I keep face book refresh interval as 4hr it tokes more resourcess (more battery drain), when compared to face book refresh interval of 15 mins?
I thought its other way..
or am I misunderstanding some thing.. Thanks in advacne..
atrix4nag said:
Can you explain it in more details... i didn't understand it correctly..
if we keep the refresh interval high.. it will eat more resourcess?
if I keep face book refresh interval as 4hr it tokes more resourcess (more battery drain), when compared to face book refresh interval of 15 mins?
I thought its other way..
or am I misunderstanding some thing.. Thanks in advacne..
Click to expand...
Click to collapse
That's what I meant. Shorter intervals (like 15 mins), are worse than longer intervals (like 4 hours).
More refreshes = more resources
Sent from my Galaxy SII
Simba501 said:
That's what I meant. Shorter intervals (like 15 mins), are worse than longer intervals (like 4 hours).
More refreshes = more resources
Sent from my Galaxy SII
Click to expand...
Click to collapse
but you said in the opposite way in your earlier post.. your earlier post says "If some refresh intervals are set high enough, it could force an app to stay active and take up resources."
high refresh intervals.. (4 hrs) take more resources...
atrix4nag said:
but you said in the opposite way in your earlier post.. your earlier post says "If some refresh intervals are set high enough, it could force an app to stay active and take up resources."
high refresh intervals.. (4 hrs) take more resources...
Click to expand...
Click to collapse
By high refresh, I think he meant if the number of refreshes was high. So 4 hrs would be low number.
Mushroom. said:
By high refresh, I think he meant if the number of refreshes was high. So 4 hrs would be low number.
Click to expand...
Click to collapse
Correct. Thank you.
Sent from my Galaxy SII
Mushroom. said:
By high refresh, I think he meant if the number of refreshes was high. So 4 hrs would be low number.
Click to expand...
Click to collapse
ok.. now i got it correctly.. got the concept correclty, but misinterpretted the words..
To help you out a little, here are few tips:
1. Weather widgets can be set to update every 4-12 hours range, unless you are in a place with too frequently changing weather patterns.
2. Take out feeds from your desktop, unless it is something you can't live without.
3. Avoid using live wallpaper. Same goes for widgets on home screen too. Keep only those necessary.
4. Use a launcher with low memory print, say like zeam.
5. Instead of using poll for emails, try using push option wherever possible.
Really basic question! Is the HTC email app or the standard yellow AOSP one better for battery life?
HTC mail in my opinion bcos it had peak and non peak period mail checking preferences which you can set how many days in a week and plus define your own timing of peak period. It also let you select minutes and hourly intervals.
The yellow one that you refers to I believe allows only hourly intervals without options to set peak periods preference. Currently I'm on ics senseless 2.10 and the yellow mail have maximum of 1hour intervals,that's it. So to summarise and answer your question, in my opinion is htc mail.
suhaimidee said:
HTC mail in my opinion bcos it had peak and non peak period mail checking preferences which you can set how many days in a week and plus define your own timing of peak period. It also let you select minutes and hourly intervals.
The yellow one that you refers to I believe allows only hourly intervals without options to set peak periods preference. Currently I'm on ics senseless 2.10 and the yellow mail have maximum of 1hour intervals,that's it. So to summarise and answer your question, in my opinion is htc mail.
Click to expand...
Click to collapse
Thanks for your thoughts. Do you happen to have any specific/detailed information about how much drain each app uses? I am just curious which app is more efficient before using the filters you just mentioned.
Cant be that quite detail as from my setup with htc mail would be like peak hour: set from 8am-5pm @30mins interval. So after the peak hour i set it to 3hrs interval. if using the yellow mail, just imagine at every 1hr intervals of checks being performed. Hope you get the idea.
Edit: If email within the office hours is important then yes, you can double the frequency or else you can set at 2hrs or more intervals.
suhaimidee said:
Cant be that quite detail as from my setup with htc mail would be like peak hour: set from 8am-5pm @30mins interval. So after the peak hour i set it to 3hrs interval. if using the yellow mail, just imagine at every 1hr intervals of checks being performed. Hope you get the idea.
Edit: If email within the office hours is important then yes, you can double the frequency or else you can set at 2hrs or more intervals.
Click to expand...
Click to collapse
Makes sense.
Hi all,
First time poster here, so hello! I've searched the forums and google but could not find an answer to this question.
Is anyone running a Nexus S on 4.0.4 ICS seeing lots of CPU usage at the 1000MHz frequency?
My phone is a Nexus S (i9020)
Operator: 02 UK
OS: Ice Cream Sandwich 4.0.4
Not rooted.
My phone goes into a deep sleep fine and battery usage seems to be little in this state. However, the moment I turn on the screen and start 'using' the phone, I see a battery drop of at least 1% every 5 mins or so. I'm not doing anything taxing, either scrolling through the home screens, or opening browser to read a web page for a few mins.
Higest three battery users are reported as:
Screen 37%
Android System 15%
Browser 7%
CPU Spy reports the following:
1000 MHz - 25.11 (30%)
800 MHz - 7.35 (9%)
400 MHz -3.34 (4%)
200 MHz - 6.26 (7%)
100 MHz - 6.56 (8%)
Deep Sleep - 33.29 (40%)
Total time: 1h23m13s
From what I've read cpu usage shouldn't max out unless you're running something intensive i.e. it shouldn't be at the 1000MHz frequency, when just reading an already loaded page.
I'm able to go from 100% to 50% in about 2 hours, just using the browser (on wifi) to read webpages and nothing more.
When I first got the phone, a year ago, on Gingerbread, I'd be able to watch 1 hour of video, send calls and texts and make it from 8.30am to 5pm using around 40% battery. These days, I don't get close to that at all.
Noted to moderators: if this is posted in the wrong place or would be better suited in an existing thread, I'm sorry please let me know and I'll edit as required!
Thanks in advance for your time and assistance!
Screen drains most the battery. If there is drain while it's off there would be some kind of wake lock preventing sleep. You likely don't have this since it seems your phone sleeps nicely, assuming you had the screen on for moat the time in that screenshot.
The frequencies you show seem a little skewed to 1000mhz for web browsing. What cpu governor are you using, and what settings? I usually get around 40-40 between highest and lowest frequency with ondemand, 20% or less for the intermediate frequencies. This is while web browsing most of the time.
Harbb said:
Screen drains most the battery. If there is drain while it's off there would be some kind of wake lock preventing sleep. You likely don't have this since it seems your phone sleeps nicely, assuming you had the screen on for moat the time in that screenshot.
The frequencies you show seem a little skewed to 1000mhz for web browsing. What cpu governor are you using, and what settings? I usually get around 40-40 between highest and lowest frequency with ondemand, 20% or less for the intermediate frequencies. This is while web browsing most of the time.
Click to expand...
Click to collapse
I understand the screen drains the most battery, but I feel there is an underlying issue since light usage (like reading) can drain 50% in 2 hours, whereas before I could watch 1 hour video and lose about 10%.
I'm not sure what you mean by CPU governor and settings. I'm running the stock ICS 4.0.4 (got the OTA only a few days ago). I agree it seems skewed. It seems to use the 1000MHz frequency pretty much all the time the screen is on.
chillerz said:
I understand the screen drains the most battery, but I feel there is an underlying issue since light usage (like reading) can drain 50% in 2 hours, whereas before I could watch 1 hour video and lose about 10%.
I'm not sure what you mean by CPU governor and settings. I'm running the stock ICS 4.0.4 (got the OTA only a few days ago). I agree it seems skewed. It seems to use the 1000MHz frequency pretty much all the time the screen is on.
Click to expand...
Click to collapse
First off, welcome to XDA!
The fact that you're not rooted + stock could only mean that there is probably a background app running while your actively using your phone. Have you checked into Settings > Apps > Running and noticed anything peculiar? For a fact, based on everything I'm reading here there is no way your phone should be at 1000 MHz for 30% of the time. At most for my usage, my phone is in the 1000 MHz state < 10% of the time.
If all else fails, you could always try doing a factory reset and seeing if the problem persists. If not then you can install your important apps one by one to find a culprit.
You could also try out this nify tool: BetterBatteryStats to give you more statistics as to what is eating your battery.
http://forum.xda-developers.com/showthread.php?t=1179809
10 percent drain while watching a video is hard to believe.
That would equal 10hrs to drain the battery with screen on watching a video. Which is not happening.
Your battery drain now sounds normal. Maybe in the past it was not reporting it correctly or you're simply mistaken somehow.
The average battery should last along the lines of 4 - 5 hours worth of screen on time. Whether this is playing a game or browsing around hasn't made more than that much difference for me. 1% every 5 minutes would give you ~8 hours of screen on time, a feat very few (aLNG, looking at you) have been able to do without an extended battery. Anything more than this is not going to happen while maintaining a cell signal and watching videos. You may have been exaggerating the time on battery in the past.
Go to Settings --> Developer options --> Show CPU usage and tick it. Leave the phone sitting there with the screen on for a bit and let me know what the top CPU users are.
Which settings are the best for battery lfe? I have stock everything.
Harbb said:
The average battery should last along the lines of 4 - 5 hours worth of screen on time. Whether this is playing a game or browsing around hasn't made more than that much difference for me. 1% every 5 minutes would give you ~8 hours of screen on time, a feat very few (aLNG, looking at you) have been able to do without an extended battery. Anything more than this is not going to happen while maintaining a cell signal and watching videos. You may have been exaggerating the time on battery in the past.
Go to Settings --> Developer options --> Show CPU usage and tick it. Leave the phone sitting there with the screen on for a bit and let me know what the top CPU users are.
Click to expand...
Click to collapse
The list of things using the CPU changes quite often, here's the list of the ones that are at the top of the list for a while (I've also attached a screenshot):
system_server
com.android.systemui
surfaceflinger
com.jim2
kworker/u:1
kworker/0:0
dhd_dpc
wpa_supplicant
UPDATE:
7h 48m 34s on battery
Voice calls: 1h 39m (screen is off for most of the call duration)
Screen on: 1h 23m
Used browser and xda app for less than 5 mins each.
Haven't done much else with the phone and I'm on 44% battery (from full charge).
CPU Spy (measuring whilst phone was charging overnight, so deep sleep is high):
Total CPU time = 13h26m
1000 MHz = 40 mins (5%)
800 MHz = 17 mins (2%)
400 MHz = 12 mins (1%)
200 MHz = 26 mins (3%)
100 MHz = 56 mins (7%)
Deep Sleep = 10h52m (80%)
hi,
I can confirm chillerz's notice. My experience's similar. Last week I upgraded my (non routed) i9023 from GB via OTA (before the update I did a hardreset). My phone became a cityphone I always have to keep a charger in my pocket and looking for power connectors.. with GB I could use my phone at least 2 days but now I'm happy if I can survive my workday.. my best was 13h - in that case Android OS battery usage was 61%.. I still haven't try to use the music player.. but I don't see any sense to it.. I'm also interested in a thread which could help me out and I've found my self here.. what do you recommend? what to do? replacing my 7 months old phone?? I've jus loved my nexus and here I'm.. It won't be a good business strategy in long term..
I know about the issues of released ICS in December.. I was hopping the 4.0.4 will solve them.. now it's April.. I don't want to wait 4 more months again..
thanks in advanced for your helping!
I had horrible battery life after the 4.0.4 update, but it's been much improved after fully discharging the battery and then charging it to 100% with the phone powered off.
great news, I will try tonight and share the result!
thx
The latest usage results seem good and processes also seem standard. Phone calls tend to use a fair bit of battery, keeping and transmitting a constant signal, powering speakers, keeping the entire phone awake and so on. I wouldn't put it above the screen being on, so you should be able to squeeze another ~30 minutes before 44% in normal use but this depends on too many factors to list anyway and bad reception can make it all the more difficult to figure out.
Also, while making calls don't be surprised if the CPU does decide it needs to ramp up to a higher frequency (ondemand likes 1000mhz) but i havn't put this to the test. This could skew the results as in the OP.
hello futangclan,
since your solution the battery usage "normalized" 26h/17%. This workaround would be a great tip on a welcome srceen at the first boot of ICS
before the fully discharging battery I noticed the battery usage of Android OS decreased from 60 to 19%.. I'm thinking about whether the ICS does something "maintenance" in the background after the OTA upgrade the first days or not..
Once upon a time, I too was one of the sullied - one those unfortunates souls, plagued with poor battery life on a Nexus S (stock FTW), brought on by an innocent (and joyful) upgrade to ICS 4.0.4 from 2.3.6.
When I first discovered the trouble, with great gusto, I ran to the interwebs and dutifully followed suggestions of restarting the phone or draining the battery, but alas - it was all to no avail. There is, however, a happy ending to this story. With effort and perseverance, I've since significantly improved performance. Here is my brief tale of success.
After the upgrade, Android (praise be its name!) decided to start, in the background, every single application on the phone. Verily Snake '97 was indeed running all the time. The horror!!! The game is entertaining certainly, but hardly worth keeping alive at the cost of other, more critical apps.
I was not deterred and took matters into my own hands. Using Manage Apps -> All (not Manage Apps -> Running, mind you), I went about Force Stopping each application (including some Android core apps). It was tedious and frightening. I was very careful and hesitant, as you should be if you are affected by a similar malady.
By the next day, I saw much improved battery life (hooray!), yet I wasn't free and clear. The hold of evil had not been loosened completely.
I found within, a strange and dangerous lock (wakelock - was that its name?) keeping the Gallery in the list of active applications, even when I had not used it for some time. It refused to move to the cached apps list. Puzzled, I scratched my empty head. The interwebs were of no use this time - I was on my own.
(cue ominous music)
Peering within, in the Sync section I found the system was trying to sync photos on an account where the checkbox for syncing was not selected.
A quick off-on-off stopped the syncing. The app slinked off the Running apps list. Soon, I was overjoyed, for I was experiencing improved battery life!
I've now returned to performance much closer to that from days of 2.3.6. My Nexus S' battery now reaches 40%-30% in ~16 hours, with always-on 3G, Wifi and GPS, oft use of phone, contacts, messaging, whatsapp, twitter, foursquare and browser, and infrequent use of music, market, maps, camera and rarer usage of games like Angry Birds (which consumes vast amounts of battery) and gallery.
All is well with the universe.
Certainly, this tale may or may not be a mirror to your own. Should you be experiencing similar problems, I hope my tale brings you solace, and provides a means to the end of your troubles.
demarcolister said:
Once upon a time, I too was one of the sullied - one those unfortunates souls, plagued with poor battery life on a Nexus S (stock FTW), brought on by an innocent (and joyful) upgrade to ICS 4.0.4 from 2.3.6.
When I first discovered the trouble, with great gusto, I ran to the interwebs and dutifully followed suggestions of restarting the phone or draining the battery, but alas - it was all to no avail. There is, however, a happy ending to this story. With effort and perseverance, I've since significantly improved performance. Here is my brief tale of success.
After the upgrade, Android (praise be its name!) decided to start, in the background, every single application on the phone. Verily Snake '97 was indeed running all the time. The horror!!! The game is entertaining certainly, but hardly worth keeping alive at the cost of other, more critical apps.
I was not deterred and took matters into my own hands. Using Manage Apps -> All (not Manage Apps -> Running, mind you), I went about Force Stopping each application (including some Android core apps). It was tedious and frightening. I was very careful and hesitant, as you should be if you are affected by a similar malady.
By the next day, I saw much improved battery life (hooray!), yet I wasn't free and clear. The hold of evil had not been loosened completely.
I found within, a strange and dangerous lock (wakelock - was that its name?) keeping the Gallery in the list of active applications, even when I had not used it for some time. It refused to move to the cached apps list. Puzzled, I scratched my empty head. The interwebs were of no use this time - I was on my own.
(cue ominous music)
Peering within, in the Sync section I found the system was trying to sync photos on an account where the checkbox for syncing was not selected.
A quick off-on-off stopped the syncing. The app slinked off the Running apps list. Soon, I was overjoyed, for I was experiencing improved battery life!
I've now returned to performance much closer to that from days of 2.3.6. My Nexus S' battery now reaches 40%-30% in ~16 hours, with always-on 3G, Wifi and GPS, oft use of phone, contacts, messaging, whatsapp, twitter, foursquare and browser, and infrequent use of music, market, maps, camera and rarer usage of games like Angry Birds (which consumes vast amounts of battery) and gallery.
All is well with the universe.
Certainly, this tale may or may not be a mirror to your own. Should you be experiencing similar problems, I hope my tale brings you solace, and provides a means to the end of your troubles.
Click to expand...
Click to collapse
You, my friend, deserve a cookie for such good writing.
@demarcolister Awesome first post here on XDA.
Great story too. Most will blame battery drain on the custom ROM/kernel they flash and fail to realize their battery drain is usually caused by a rogue app running in the background ...
I've never had good luck with the stock gallery app. I always freeze it via adb when I flash a new ROM. It seems much worse in ICS. It would always start back up.
Stock GB gallery was an absolute joke. Slow, missing thumbnails, weird background and hard to see what you're scrolling through. The stock ICS gallery i actually prefer over alternatives. Though i don't use picasa so that is disabled. Never an issue with it (besides always showing my damned album covers).
Harbb said:
You, my friend, deserve a cookie for such good writing.
Click to expand...
Click to collapse
nom nom nom!!
AeroEchelon said:
@demarcolister Awesome first post here on XDA.
Great story too. Most will blame battery drain on the custom ROM/kernel they flash and fail to realize their battery drain is usually caused by a rogue app running in the background ...
Click to expand...
Click to collapse
I was quick to (negative) judgement too, but I figured that Google would not (certainly!) release an update that completely cripples a modern and high-selling device.
Harbb said:
Stock GB gallery was an absolute joke. Slow, missing thumbnails, weird background and hard to see what you're scrolling through. The stock ICS gallery i actually prefer over alternatives. Though i don't use picasa so that is disabled. Never an issue with it (besides always showing my damned album covers).
Click to expand...
Click to collapse
Agreed! In fact, I'd accept, grudgingly, if album covers show up in the gallery (although, truly they should not), but I do not, under any circumstance, want to see the icons (tick for yes, cross for no, i for icons, etc.) used by an application in my Gallery. Idiocy!
What is the solution? I wish to remain Stock, so rooting and editing the equivalent of plist or config files is not an option. At least 'Camera' is the first option, always! That makes it usable, but as soon as I use picplz or camera360 or instagram their folders get shuffled in position. Is Google hinting at something!? *sigh*
Hey guys...
Sent from my Nexus S
Which kind of notification consumes less battery ? Logic tells me that push notifications should consume more battery since it's almost instantaneous but I've read it doesn't exactly work like that , I'm quite confused now
Sent from my Nexus 5 using Tapatalk
Push uses less battery.
Sent from my SPH-L900 using xda premium
Push can use less battery but it depends on lots of stuff, including the server on the other end.
Push has the nice feature of instantaneous notifications because it's semi constantly connected to the server. It polls the server every X seconds and gets long each time there's no new message to keep connectivity alive. When the server gets a message it initiates the connection to the phone telling it to download new messages and then it pulls them down.
Pull on the other hand just checks at a set interval of every X minutes. You can do 15, 30, etc... If you have pull set to a fast check time say 5 mins, it will needlessly waste battery every 5 mins going into full active mode to check the server often times for no reason. If you however have your pull set to check ever 4hrs that may be less power than push but if you need email all during your day you'll obviously be checking in more often.
shotta35 said:
Push can use less battery but it depends on lots of stuff, including the server on the other end.
Push has the nice feature of instantaneous notifications because it's semi constantly connected to the server. It polls the server every X seconds and gets long each time there's no new message to keep connectivity alive. When the server gets a message it initiates the connection to the phone telling it to download new messages and then it pulls them down.
Pull on the other hand just checks at a set interval of every X minutes. You can do 15, 30, etc... If you have pull set to a fast check time say 5 mins, it will needlessly waste battery every 5 mins going into full active mode to check the server often times for no reason. If you however have your pull set to check ever 4hrs that may be less power than push but if you need email all during your day you'll obviously be checking in more often.
Click to expand...
Click to collapse
Thank you for the explanation, I have a better Idea now what push does , I'll make sure to use it, I still can't believe there are some apps that come with a 5 minute refresh selected by default! aka tweedle, ATE may battery the first two days I was using it , until I noticed the outrageous refresh rate