Related
I've noticed that when I close an app (exit it) it usually stays open in the background. An example for this would be Facebook or Google Goggles.
I don't want to have those apps drain my battery when I don't use them and I don't want to have to close them manually every time I exit them. What can I do?
Please help
Im doing the same thing too i would like to know if possible. I tried a taskmanager program but that just halts an app from coming back up again.
Sent from my Arc using XDA premium App
When any Activity is no longer the frontmost Activity (on screen), it's shut down by the OS. Any "background" Activities are simply stored in memory in case you want to go back to them. What you're seeing is essentially the history of the app; when you "open" it again it'll just reload the last saved state. At that point, the application is allowed to execute again.
The only applications that should continue running in the background are services.
The only drain you'll see are, as above, services running and the power necessary to keep the background Activities in memory; they're not actually executing.
Of course, there are ways to get around that, but most good citizens will respect Android's wishes when it comes to saving state and exiting when they're no longer frontmost.
NickWarner said:
When any Activity is no longer the frontmost Activity (on screen), it's shut down by the OS. Any "background" Activities are simply stored in memory in case you want to go back to them. What you're seeing is essentially the history of the app; when you "open" it again it'll just reload the last saved state. At that point, the application is allowed to execute again.
The only applications that should continue running in the background are services.
The only drain you'll see are, as above, services running and the power necessary to keep the background Activities in memory; they're not actually executing.
Of course, there are ways to get around that, but most good citizens will respect Android's wishes when it comes to saving state and exiting when they're no longer frontmost.
Click to expand...
Click to collapse
So when I click the "Force Stop" in the task manager on one of those applications that I've closed, what does it do? I don't think it erases them from the memory.
For instance, Facebook, when I click "Force Close" I'll still get notifications.
I'm seeing some of these applications in the Battery Usage.
Furthermore, Android will completely shut down apps in the background in order to recover the memory they're using, if it's needed elsewhere. That's really the only time that app management is necessary.
If you're simply seeing a lot of "background apps", rest assured they're not draining your battery.
If you are seeing an inordinate battery drain while you're on the home screen, you might have a service running behind the scenes that's consuming your CPU cycles.
Look for System Panel Lite in the Market; it will let you see the amount of CPU being devoted to each process. I'd bet that most of your background stuff is only eating RAM and not CPU. If there is something eating up a lot of CPU, you can investigate that particular app instead of simply force-killing everything in the background.
matanc1 said:
So when I click the "Force Stop" in the task manager on one of those applications that I've closed, what does it do? I don't think it erases them from the memory.
For instance, Facebook, when I click "Force Close" I'll still get notifications.
I'm seeing some of these applications in the Battery Usage.
Click to expand...
Click to collapse
There are two components to the Facebook app: the application itself and a service. When you "Force Close" the application, you're just stopping what you see onscreen. The service is still running, and a totally different animal than the application stuff we were discussing.
Edit: To clarify: You're seeing the package under Battery Usage, which combines the application ("Activity") and service usage to form an aggregate for "Facebook", not just one component.
Edit: (again) You're right above when you say that it removes them from memory. That, in fact, is ALL it's doing. It's removing the history/background Activities from memory. Unless that Activity is actually the frontmost Activity at that time you click "Force Close", it's not saving you any CPU time/battery usage.
Okay.
So you're saying there is no reason for me to "Force Close" every app after I've closed it?
And btw, when you say that they are in the background what does that mean?
I mean, the Active Applications widget is supposed to show me those that are running in the background right? So how come when I go to the home screen (using the back button) from an app like Facebook it won't show in the Active Applications widget but it will show Google Goggles?
matanc1 said:
Okay.
So you're saying there is no reason for me to "Force Close" every app after I've closed it?
And btw, when you say that they are in the background what does that mean?
I mean, the Active Applications widget is supposed to show me those that are running in the background right? So how come when I go to the home screen (using the back button) from an app like Facebook it won't show in the Active Applications widget but it will show Google Goggles?
Click to expand...
Click to collapse
To your first point, yes, that's exactly it. Android does this for you if it needs the memory. Otherwise, it leaves the history hanging around to make it appear the app is loading quickly the next time you open it (and it puts you right back where you left off). Note that we're ONLY talking about the user interface you see onscreen here, not any services.
Your second point requires a bit more explanation. My apologies if this gets either too basic or too in-depth; I'm not sure what your skill level is with Android. Each "window" or "screen" you see is actually a separate Activity, and is essentially self-contained. As you navigate through screens, the previous one saves what you were doing in memory and then exits. When you hit the Back button, Android simply grabs the last screen in memory and loads it back up. At that point, the application is running again. My references to "background" applications above is exactly this: screens you've left behind that are waiting for you to hit Back.
It's ultimately more complicated than that, but I think this will work for our needs.
matanc1 said:
Okay.
So you're saying there is no reason for me to "Force Close" every app after I've closed it?
And btw, when you say that they are in the background what does that mean?
I mean, the Active Applications widget is supposed to show me those that are running in the background right? So how come when I go to the home screen (using the back button) from an app like Facebook it won't show in the Active Applications widget but it will show Google Goggles?
Click to expand...
Click to collapse
To continue: Services are the real sticking point here. A service is an application that doesn't have a user interface (or screen). It's running all the time and not subject to the history/back button behavior we've been discussing. These guys are the ones you really need to be worried about, if anything. These are the ones that will run behind the scenes, consuming CPU and data (and, by extension, battery). Facebook is an excellent example: It's always checking to see if you have new messages, posts, etc. so that it can pop them up on the screen. GMail and SMS (and phone calls, even) all do the same thing using services. If the service is badly-written, it can be a real drain even when you're not using it.
You mentioned Google Goggles specifically above, and unfortunately, I'm not very familiar with how that particular app works. I suspect it's not subscribing to the good citizen philosophy and shutting down when you're done with it. It imagine it has to do with needing to perform searches or image comparisons in the background while you're off doing something else. This is technically allowed by Android, but it's frowned upon and suggested that you only do it when absolutely necessary.
Whew. All of that to say this:
Apps, as a general rule, don't consume resources when they're not on screen. They'll consume RAM, which does consume battery power, but it's really insignificant in the grand scheme of things.
Some apps will continue running after you "exit" to the home screen, but they should only do that as long as they have actual work to do. Once they're done, they should also shut down as above.
Services will consume resources all the time; they're constantly used for things like checking Facebook, Twitter, email, voicemail, etc.
okay, so again, just to summarize:
Force Closing an app just removes it from the System Memory (which makes them load faster when I open them). These apps use no additional battery life?
So I can feel free to not Force Close apps such as Camera (which I can do that to for some reason which I can't think of)?
Edit: And thank you very much Nick for the help and great responses.
matanc1 said:
okay, so again, just to summarize:
Force Closing an app just removes it from the System Memory (which makes them load faster when I open them). These apps use no additional battery life?
So I can feel free to not Force Close apps such as Camera (which I can do that to for some reason which I can't think of)?
Click to expand...
Click to collapse
You're correct. As a general rule, you don't have to force close any applications in Android. They will use some RAM and zero CPU and data, which equates to effectively zero battery.
Leaving the app in the background (in memory) loads the app faster the next time you open it, assuming Android hasn't closed it to reclaim that memory on its own. I've found that within a few minutes of heavy use (browsing the Internet, etc.), Android has shut down several of the apps in the background for me; it needed that memory to let me continue doing what I was doing.
You don't need to force close apps in the normal course of business. The only time you should force close an application is if it's behaving badly while on the screen (it's not responding to button presses or it's stuck in a tight loop or somesuch). Force closing it while it's in the background doesn't really gain you anything.
Okay, so just one last thing:
Do you have any suggestion to try and improve the battery life?
matanc1 said:
Okay, so just one last thing:
Do you have any suggestion to try and improve the battery life?
Click to expand...
Click to collapse
I have some general suggestions:
Don't sync accounts that you don't use. For example, if you don't use Facebook very often, don't have it set to sync up every hour.
Turn off WiFi, Bluetooth, and GPS unless you're actively using them. (A caveat: Google Maps uses WiFi in conjunction with GPS, so turn them both on while using Maps, even if you're not connected to WiFi.) Personally, I don't do this. I leave WiFi, Bluetooth, and GPS on all the time, but I know people who swear by this.
Keep your screen brightness as low as you can stand it. Again, I don't do this. I generally leave it on Auto-brightness.
Ultimately, though, you need to find that balance between usability and battery life. If you're always on Facebook and Twitter, sending SMS and surfing, well, there's not much you can do but keep an extra battery or charger nearby. If you're an office-worker that only uses their phone on break and at night, some of the above will probably help.
If you can give me an idea of a normal day's usage of your phone (and make/model/ROM version), I might be able to be a little more specific, or at least point you in the direction of your device's Q&A forum.
Well, I'm new to android and I've got a Samsung Galaxy S 2.
I don't really use the data connection (which is why it's always disabled unless I decide otherwise) and I turn on the Wifi only when I need it (which is often relative to 3G).
Normally I just use my phone for calls, SMSing and a bit of surfing.
About the google maps, I've noticed that it uses A LOT of battery and that it starts itself after I force close it, so I've closed the Maps service which seemed to fix the problem.
That's more or less it.
Not much syncing as well, I usually sync only when I need it.
Edit: I must say that I don't really understand what Backround Data is.
Is it that the Background Data lets the apps use data (like use facebook via wifi?) while the Auto Sync syncs automatically when I get a new email / notification? Does the background data have to do only with the my monthly data package and not with wifi ( i think that is the case ).
First off, you'll probably be better served to ask the guys in the Samsung Galaxy S2 Q&A Forum. They'll have a better idea of what the device's baseline is and what specific features you can turn off. Sometimes, as with the Samsung Fascinate, there are specific features that cause problems on the stock ROM, like Maps issuing bad WakeLocks. I know on my Fascinate before the first update, I had to toggle airplane mode every time I booted or Maps would eat the battery up in hours. Those guys in the device-specific forums will have a better handle on it, if there's anything of concern.
In general, though, it sounds like you're doing a pretty good job of keeping the device doing just what you want it to do. Android's sync framework is going to try to sync up all of your accounts essentially simultaneously whenever you turn on data, since it's probably been turned off for longer than their individual refresh intervals. You might want to turn off automatic sync on the service that you do use, so you can control those a little better when you turn on data to do something else.
Maps is a heavy data user and it makes use of GPS, which is going to consume quite a bit of power. The startup cost you're noticing is it trying to get a fix via the cell tower, GPS, and WiFi all at the same time, since the services have been off. If you use Maps often, you might be better served to leave data on (but, say, Edge only if you're GSM or 3G only if you're LTE/WiMax). This way, Maps can get a rough fix on your location at all times and not have to beat up the hardware to get a fix from scratch when you turn all the services on.
The Maps service is probably, to be anthropomorphic, freaking out all the time because it's trying to get some sort of fix while all the data services are off. Truth be told, I don't believe it was designed for that. Shutting down the service is a good way to go if you don't use it often.
You could try an application like Autorun Manager to control which services start up on boot. To make the most use of it, you need to be rooted, but in non-rooted form it will give you more control over what starts up automatically.
matanc1 said:
I must say that I don't really understand what Backround Data is.
Is it that the Background Data lets the apps use data (like use facebook via wifi?) while the Auto Sync syncs automatically when I get a new email / notification? Does the background data have to do only with the my monthly data package and not with wifi ( i think that is the case ).
Click to expand...
Click to collapse
Background Data is what services use behind the scenes (like syncing and such), but I believe it's an aggregate of all data, not just data on the cellular network. I'm looking through the docs right now to see if I can find a definite answer.
Edit: According to the docs, Background Data is data that is sent or retrieved when the application is not onscreen. This can be either in a service (as is usually the case) or when the app has to do some cleanup after you've moved to a different screen.
Thank you very much
I've noticed that I've got a few widgets that are using memory etc, ones that I don't use and never intend to.
They were preinstalled with the phone and I can't seem to uninstall them. Is there a way that I could without rooting my phone?
And on another subject, if I root my phone, is there a way to "unroot" it in case I'll need to send it to Samsung if there is a problem with it (since i've got a warranty and rooting voids it?)
matanc1 said:
Thank you very much
I've noticed that I've got a few widgets that are using memory etc, ones that I don't use and never intend to.
They were preinstalled with the phone and I can't seem to uninstall them. Is there a way that I could without rooting my phone?
And on another subject, if I root my phone, is there a way to "unroot" it in case I'll need to send it to Samsung if there is a problem with it (since i've got a warranty and rooting voids it?)
Click to expand...
Click to collapse
In theory, widgets don't consume resources unless they're on your home page. If they have services that collect their data, that's a different story. If you don't want them, you can just long-press on them and drag them to the trash can.
In conjunction with Autorun Manager above, you can remove the widget from your home page and stop the service from starting at boot. For example, I don't use Facebook (I know, lame), so I removed the widget and stopped the service. True, it's burning up a couple of megabytes of disk space, but that's insignificant next to the power of the Force, as it were.
Regarding uinstalling them, generally the answer is no. If you root your phone, you can manually remove them from the device, but that's sometimes overkill. Generally, they take up little enough room on disk that you won't be hurting for space.
In most cases, "unrooting" is as simple as flashing the stock ROM (usually available at the top of your device's development forum). Rooting your device generally doesn't make any changes to the device itself that can't be undone by flashing a stock ROM.
I've heard that rooting still leaves traces on the device though and that if they catch that it's been rooted I'm screwed. So you're saying that's not true?
Hi guys,
I have a USCC Mesmerize with EC10 PNP w/ none of the pack addons.
I would consider my phone to be very slim. I pretty much only use the camera, sms, mms, internet, & phone.
But still after my phone has been on for a while my process is up to 295/349 MB
I constantly use the stock task manager with Level 2 clear memory option to kill the active process.
When I do this I normally close anywhere from 5-12 process's. Sometimes I will get a drop to around 245MB and other times it will stick around 282MB
On a fresh restart my phone boots up with 164MB
I immediately goto task manager and do a level 2 clearing of the memory and end up closing 10 programs with a RAM use of 131MB
Is there anything out there app or otherwise I can use to stop and prevent all non-critical process's?
uselessmidget said:
Hi guys,
I have a USCC Mesmerize with EC10 PNP w/ none of the pack addons.
I would consider my phone to be very slim. I pretty much only use the camera, sms, mms, internet, & phone.
But still after my phone has been on for a while my process is up to 295/349 MB
I constantly use the stock task manager with Level 2 clear memory option to kill the active process.
When I do this I normally close anywhere from 5-12 process's. Sometimes I will get a drop to around 245MB and other times it will stick around 282MB
On a fresh restart my phone boots up with 164MB
I immediately goto task manager and do a level 2 clearing of the memory and end up closing 10 programs with a RAM use of 131MB
Is there anything out there app or otherwise I can use to stop and prevent all non-critical process's?
Click to expand...
Click to collapse
That sounds pretty normal from what I have seen. Are you having any issues or just like to see the Rom lower?
Actually android by design is supposed to run almost always at full ram/memory compacity. Using a task killer other than stock can give unwanted results. My phone runs the same as yours does. When you kill off task the systen will automaticly reload common and system apps. Its the nature of android. Unless your having really bad performance. I wouldn't worry about it.
Edit: Ninja'd.
Tap-a-Talked from my Mesmerize
I agree with akellar, that sounds pretty normal. I mean, are you actually suffering any performance issues? If you're not, then you're just worrying about nothing.
Similar stuff here. I use the level 2 clear as well, but mainly to save battery. I run the clear,just before I set it down for a no use period or prior to bedtime and it saves battery big time.
Sent from my SCH-I500 using Tapatalk
No not really any performance issues. Sometimes but its infrequent enough that I couldn't describe it.
That was mainly my thought was saving on battery.
Why have all this crap running if you aren't using it?
Technicly its not running. It is suspended. While it is in ram it isn't using any processing power until the app is brought to the foreground meaning you are using it. Android does this so these apps are ready to go when you need them. I quit using task killers other than the stock one a while back and noticed a big jump in battery and performance. I though they were helping me when in reality it was hurting me. Take a read on android and how it handles multi tasking. It explains it really well. I wish I had a link handy hut if you google it you will find several articles on it.
Tap-a-Talked from my Mesmerize
Yeah, you are actually wasting battery by having the screen on in order to end tasks that aren't actually running.
Either way, my battery lasts longer. I understand the logic, but in reality - my battery lasts longer.
Sent from my SCH-I500 using Tapatalk
I've read probably 20 or 30 articles on this explaining bboth sides and hundreds of user opinions who say to use them, don't use them, use them once a day, etc and why they think that. I really think it depends on what you do with your phone, because in my personal experience I am a heavy user of my phone, constantly switching applications and loading browsers and whatnot. If I don't use a taskkiller then my phone becomes unresponsive and almost unusable at times. I know you're supposed to stay away from them and I have tried that but it is really obvious that it is useful when I can press a button and have my phone actually work again.
For somebody like the OP that just uses it like a normal phone and not a computer like I do, you probably shouldn't use one unless you are really getting slowdowns. It all depends on what exactly is using the memory and not getting killed by the system.
Sent from my CM7 SCH-i500
I agree to an extent. I use the paid version of system panel to monitor apps like that from time to time. I use the stock task killer and do a level two kill after I have been on my phone switching between programs and such. And it does make a difference is performance. Depending on what you are dping depends on whether you should use one or not. I thinl the big depate is whether you should use an auto kill function. Its one thing to kill all task here and there to improve performance but another to have an app doing it every five or ten minutes. I think that's were the big battery drains happen. Anyway. To each there own and if they see it helps them in how there phone performs and are happy with the results, then maybe a task killer ia for them. For me. I just use the stock task manager and it works fine.
Tap-a-Talked from my Mesmerize
*Disclaimer* This is all from a personal experience and testing/research from a long time android user, what I have discovered over time and has helped me and some friends. This will work whether your rooted OR not. I kept it as basic as I can so everyone can benefit. If you dont like what you read and disagree, or want to add something PM me, Ill change/add and give credit to you. Hopefully, this can grow with the community.
*Rooted Section Will be Added*
*When I charge my battery I usually drain it all the way down or as much as i can (around 20% left) then charge plugged in till green, then power down and charge for another hour or so. Not sure if this matters or not but seems to help me out try it!*
This guide will help you if your rooted or non-rooted, all the apps I talk about I honestly have no ties to the devs. I don't use any SUPER AWESOME AMAZING BATTERY SAVER 5000 apps or anything like that. Those mostly just turn ur radios off and on and kill apps in the background. In my experience a lot of them cause syncing issues with my e-mail and other notifications. I like to receive my information instantly not have an app waiting for me to turn my screen on to check for updates.
About my personal setup: Basically, I want my phone to last me all day but still perform well with a heavy use, WITHOUT needing to constantly change settings to save battery. With what I have here Im able to keep my Sensation running for a full day of moderate-heavy use (7:30am to around 10pm) with its STOCK battery (Did damn well on my Evo 4G too). Days of very minor use Ive gone into the second day with 60% + battery. Yes, I use all my home screens and have a good amount of widgets, I love sense and its widgets. I play games, surf the web, do a lot of texting, listen to a lot of music, decent amount of fbing and email, usually take a few pictures a day. Half my day is wifi/other is mobile data.
Here goes the real basics, mostly common sense here not trying to insult anyone. Feel free to browse thru it quick (green text) if your not totally new to the android scene, whats after it will be a good read for noobs and vets.
*I use the power control widget, make getting to a lot of settings quicker. Why waste battery digging thru menus?*
Basics:
-Screen brightness: (duh ) these pretty screens eat battery brighter=quicker drain naturally and from my experience leaving it on Auto Brightness kills more battery too. Each time your phone pulls information from the sensor to decide on how bright it should adjust itself too.
-GPS: If GPS is on it should not effect battery unless an app is using it and you see the GPS icon on your notification bar. I noticed a very slight increase in mA discharge when i had it enabled, to be safe leave it off if you dont use it extremely frequently.
Location thru mobile networks: Not to hard on battery. I leave mine on it does add drain but it takes away from my weather widgets updating when Im traveling.
-Bluetooth: Moderate battery drain. I honestly don't use it at all myself but if you do try your best to keep it off when not in use.
-Wifi: Android has gotten a lot better at managing wifi over the past few years. It doesn't drain that bad on battery and it shuts off/on periodically on its own when screen is off depending on whats using it.
Google Back-Up: Takes a little juice here and there no biggie. I dont use it just because I like to fresh install my apps when I try a new rom, run into less problems that way.
2G/3G/4G: This varies phone to phone, the slower speed the better battery life. If you know your not going to be using 4G for a while turn it off. I leave mine on 4G or wifi all day with my sensation. When I had Sprint and my Evo I would leave it off most of the time. Depending on your carrier and how their data works this is a big one. T-Mobile seems to handle well, Sprint and Verizon's 4G Ive seen eat an insane amount of battery.
Sync/Background Data: I lumped them together because sync is pretty much reliant on background data. These kill a lot of your battery in general. It syncs your apps (email, facebook, google data, contacts, etc.), the periodic checks your apps do to check for and download new emails and notifications, using background data (data still transmits when screens off). I always leave these on and still manage great battery life, I like things instant if I wanted to wait Id just wait till i got in front of a PC. Sync and Background data are the settings most battery saving apps control because they really can help your battery if you turn it off. You can control what core apps sync in settings>accounts and sync. Or the power widget that 95% of android phones have has it on there. I recommend minimizing the amount of apps you allow background data with, example: WeatherBug first launch it asks if it can automatically update itself in the background for apps were thats not necessary hit no.
Radio/Airplane Mode: Pretty self explanatory, turns off your connection to your wireless provider. No point in ever turning it off in my eyes, your phones no longer a phone.
What has really helped me with my battery life (non-basics):
There is a lot to be said when it comes down to 2.2+ android phones and whether they need a task killer anymore or not. Since Ive had a lot of android phones and a few now that are 2.2+ Ive done a lot of testing. I usually go about a 2 weeks on one idea or new task killer and keep a close eye on battery drainage using Battery Monitor Widget, free app in the market. It tells you exactly how much of your battery is being drained without killing battery itself. Each phone/rom settles at a different average mA lower the better. In my experience if I can keep my phone anywhere under 100mA when idle im doing good. This held true on both the Evo 4G and my Sensation. Some ASOP roms i could get down to the 30's but for sense under 100mA is good. Keep in mind you will get the occasionally spike here and there its just android and/or apps in the background. You can view the a chart of the battery data in Battery Monitor.
Instead of boring you guys with each task killer Ive used and its results, Ill just get down to what I found out in the end.
Basically, the way android 2.2+ works it really isn't necessary to run a task killer it does a decent job removing apps from memory when you need more memory. But at the same time I found running a task killer periodically (BUT not killing frequently used apps) results in a lower average mA drain leading to overall better battery life.
The best application I have used has to go Automatic Task Killer , trust me Ive used a lot from the top free ones to a few of the more popular paid ones. What this task killer does is kill a selection of apps you allow it too every time your phones screen shuts off and goes idle. On Automatic Task Killer's first boot your shown a screen of every application that could at some point run in the background on your phone. This part sucks a little bit but it is worth it, you need to select which of the apps you want to allow it to kill automatically. It does not kill foreground apps the ones you currently have open on the screen aka a browser or a game. Example your playing NFS: Shift and your boss walks by so you quickly pause and hit the power button turning off the screen, next time you turn the screen on it will kill all other allowed background apps but your game will still be up front and center.
Now the trick is to go thru and set it to kill apps you know your phone won't automatically just restart or you don't use 90% of the time. So don't select things like Dialer, Contacts, Clock, Calendar, Messages or apps you constantly use/check such as a third party SMS app or your main E-Mail Client or third party keyboards (various by person and what you use most). Letting the app automatically kill those is just going to lead to worse battery life because your phone will just restart it each time leading to more CPU cycles (not what you want and part of the reason some consider task killers bad things).
Also, when using any task killer and killing the proper apps sense runs smoother, a big deal with sense 3.0.
So hopefully with a little messing around you can get a good setup where your phone lasts you all day without having to constantly keep changing settings and watching your battery life. All while everything stays syncing and instant. Hope this helps!
*ROOT Section (now that we have s-off )
Everything posted above can be done on any rom, rooted or none. There has been a lot of posts on "freezing apps" that you dont need or typically use, which does in fact really help battery life. Since, we (by we i mean sensation users) now have a permanent root this is my tiny second part of the guide for rooted devices.
I dont freeze my apps I prefer them to be gone for good if its something I dont see myself using or its bloat that came with my phone/rom. Since 98% of us will be using custom roms now this usually isnt an issue since most dev's r good at what they do and remove all the bs we dont need or normally use. Still there is some apps we may not want on our phones so for that I use SystemApp Remover . Its a great App for people who dont want to have to worry about going in manually and getting rid of system apps.
Its just basically an Uninstaller that allows you to access any and every app on the phone for you to uninstall (thats y roots needed). For me I just go in an drop the apps I know i wont use. A lot of roms come with carrier add-ons and such, those I normally delete as well as a few HTC sense widgets and apps I see no need for. It will free up space and increase your phones battery life with most things you delete.
Now, be careful. You are prompted upon opening SystemApp Remover that messing in system apps is dangerous and it is. If your not sure what something is DONT touch it, simply do a google search or ask around to see if its safe to remove first.
Re-calibrate Battery: After you flash a new rom or start using a new battery, you should use your recovery (CWM or other) to Wipe Battery Stats. Before you do this make sure your battery is at 100% and has been on the charger for over an hour with the fully charged green led on. This will allow your device to better drain your battery and can really help battery life.
So hopefully with a little messing around you can get a good setup where your phone lasts you all day without having to constantly keep changing settings and watching your battery life. All while everything stays syncing and instant. Hope this helps!
Thanks to people who have contributed:
-JadeSoturi
thanks for sharing the experience
i'm trying Automatic Task Killer
devine might said:
thanks for sharing the experience
i'm trying Automatic Task Killer
Click to expand...
Click to collapse
no problem. let me kno how it goes for you
very good info! would also help if you specify which versions of android.....
Thanks for the info, hope it will increase my battery life to last a day
Airfaire said:
very good info! would also help if you specify which versions of android.....
Click to expand...
Click to collapse
im on my sensation so 2.3.3. Been getting a lot of hate on the sensation forums since task killers are officially deemed no longer needed, but this method really helps me with battery life hoping itd help some of u too
Watchdog> then any task killer
ADR6300
Hmm, ill try auto task killer as well, tried a few others.
I use JuiceDefender, I like it. It manages my connectivity pretty well and it does help.
This is excellent, many thanks. As a converted WM 6.5 user I have to say, I am enjoying android considerably more and I prefer it to the Metro interface of WP7. It's nice to know the little tricks to get the most out of it. Thanks again. ^_^
DarkSwanKnight said:
I use JuiceDefender, I like it. It manages my connectivity pretty well and it does help.
Click to expand...
Click to collapse
same here, JD works pretty good
TastyTorge said:
same here, JD works pretty good
Click to expand...
Click to collapse
Worth getting the full one or will the free version do?
Sent from my HTC HD2 running TyphooN CyanogenMod 7 via XDA Premium App
Thanks
Thanks for the info, and for sharing, i will try the different methods
i havent really bothered with task killers but ive found reducing the brightness and disabling data and sync makes my battery last alot longer. i just re enable when i need them.
also, i downloaded setcpu and added a profile for while the screen is off. that helps alot. the drain is about 5% with the screen off after every 3 or 4 hours.
Very good info thanks
You had me impressed until you mentioned task killers. Absolutely horrible...
Sent from my HTC Sensation 4G
Martin_Toy said:
Worth getting the full one or will the free version do?
Click to expand...
Click to collapse
Full version is much better.
It's killer app indeed. I think many of it's features should be natively included in android.
Options like "Turn off 3G/EDGE when connected to Wi-Fi", "Turn off all radios when screen is off", "Turn off Wi-Fi after x minutes if it doesn't connect to a network", "Set screen brightess to minimal when battery is low", etc....it wouldn't be that hard to implement and battery life, perhaps most criticized aspect of Android, would improve immensely.
fpu
floating_point_unit said:
Full version is much better.
It's killer app indeed. I think many of it's features should be natively included in android.
Options like "Turn off 3G/EDGE when connected to Wi-Fi", "Turn off all radios when screen is off", "Turn off Wi-Fi after x minutes if it doesn't connect to a network", "Set screen brightess to minimal when battery is low", etc....it wouldn't be that hard to implement and battery life, perhaps most criticized aspect of Android, would improve immensely.
fpu
Click to expand...
Click to collapse
Your mobile network DOES turn off when connected to wifi, and if all radios turned off when the screen went off, how would you ever get calls or emails with the phone in your pocket? The wifi after x minutes would be a nice feature, but I don't like things touching my screen brightness.
Thank you for your information.
So, Sense has always been this way for a while (the HTC EVO 4G LTE was the worst of them all), and I see that the U11 with *almost stock* software and 4GB of RAM is not enough for it to keep a few more apps in the background.
This is bothersome when trying to play games that start over every time that I switch to another app! Even XDA just restarted and I lost half of this post that I was writing. I don't actually see it as a bug or faulty software...just very aggressive RAM management.
Is there any solution to this? Do custom ROMS even solve this issue?
+1, I'd also like to see how to make the RAM management less aggressive. Right now when I play a game, then switch to Chrome, Facebook, or even just public transport timetables app and then go back, game usually starts over. I thought 4 GB of RAM would be enough to have two games loaded, apparently not
LuH said:
+1, I'd also like to see how to make the RAM management less aggressive. Right now when I play a game, then switch to Chrome, Facebook, or even just public transport timetables app and then go back, game usually starts over. I thought 4 GB of RAM would be enough to have two games loaded, apparently not
Click to expand...
Click to collapse
I don't think that the 4GB of RAM is to blame. There is no justification for closing a game to send a TEXT! I think that they just try to keep as much RAM available at all times, at the cost of convenience.
Boost+ enabled,?
Yeah I think it's the boost+ app. Uninstall it and check. I don't use it and I just launched 25apps and none of them reloads.
Update: hmmm actually they started reloading after 3 mins. Not all of them but half. Wierd. I don't mind though as long as the battery stays like this.
In boost+ I don't allow the background optimizer to kick in in less than 3 days on apps I want to run in background, so that's probably not it.
LuH said:
In boost+ I don't allow the background optimizer to kick in in less than 3 days on apps I want to run in background, so that's probably not it.
Click to expand...
Click to collapse
Neither do I. Even coming from a fresh install and rejecting Boost+, the Task Killer is still aggressive.
I think that it depends on the OOM settings (I think that is the correct acronym...haven't dealt with those for a WHILE....).
I was getting frustrated with a lot of my apps pretty much closing every time I backed out of them causing me to have a huge delay in getting notifications as a best case scenario, and sometimes not getting any at all unless I actually opened the app again, Facebook/Messenger being the biggest culprits, but many others too.
Looking in Settings/Power/Battery Optimization I found that nearly all my apps say they are being optimized. I've never used Boost+ so it seems they have defaulted to this. After toggling a few apps to Not Optimized I've found that these apps no longer close and need to reload when I back out, and notifications come through in a timely manner. Battery life seems unaffected, I still easily get through a day and have at least 50% remaining at bed time. Might be worth looking at
liberator72 said:
I was getting frustrated with a lot of my apps pretty much closing every time I backed out of them causing me to have a huge delay in getting notifications as a best case scenario, and sometimes not getting any at all unless I actually opened the app again, Facebook/Messenger being the biggest culprits, but many others too.
Looking in Settings/Power/Battery Optimization I found that nearly all my apps say they are being optimized. I've never used Boost+ so it seems they have defaulted to this. After toggling a few apps to Not Optimized I've found that these apps no longer close and need to reload when I back out, and notifications come through in a timely manner. Battery life seems unaffected, I still easily get through a day and have at least 50% remaining at bed time. Might be worth looking at
Click to expand...
Click to collapse
Bro....thank...you! This definitely made a difference so far.... I'll pay attention to see if it makes a big difference in the long run...
Testing as well, thanks! It doesn't seem connected to Boost+ and appears all my apps are optimized by default - even those I never ran on this phone.
Yeah it had me stumped at first but I noticed it last week and changed it then and have had no problems since. Hopefully it sorts it for you too
liberator72 said:
Yeah it had me stumped at first but I noticed it last week and changed it then and have had no problems since. Hopefully it sorts it for you too
Click to expand...
Click to collapse
Still restarting apps quicker than I prefer, but much better. Thanks!
The problem is android and how it handles apps. If you want to switch apps then use the recents list to use the multi app function (splitscreen).
Beamed in by telepathy.
Hey all, I've had my G7 Power for about 2 years and in the last year or so I have been super frustrated with the handling of background processes, etc.
It can hardly hold a background process. The two worst offenders for me are:
It will kill my music app almost instantly after pausing. This is exceedingly frustrating when an app mutes all other audio and it instantly kills my music.
It will kill my browser when I go to search for a file to upload (for example if I go to upload a PDF to a website I can't because the website has to reload when I come back from finding the file).
In an attempt to solve this I moved from stock to LOS 18.1 and rooted. This was perhaps marginally better, but still overall terrible.
The other day I used this Magisk module to enable the low_ram flag, as well as disabled the Google app (which despite always always hogging RAM also loved to close in the background), which actually kinda solved my problem. It is still not perfect, and I had to find a new weather app, but it's acceptable. HOWEVER, I learned that I cannot use messages for web with this flag on (really Google????), which is kind of a dealbreaker for me.
I happily used stock ROMs on my phones for the last few years and would rather not spend my time making my phone with 3GB of RAM work worse than my older phones that ran MM on 1GB just fine. Any suggestions? Should I go back to Android 9 and never update? I can't even remember if it was better but it seems like it might be.