End tasks when closing apps - Android Software/Hacking General [Developers Only]

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?

Related

<Q> How apps run in background?

On a unit like this HD2, how do apps run in background? Do all apps use power just being there? Like Album app. Does it use up more power? Or like Google map. Does it use power? Or does it keep my GPS on if I have that feature enabled in it, while in background?
I'm trying to figure out how much apps I should be really closing to save battery.
more processing power used, more battery used
Ok, that I knew. What I'm wondering is if a app is in background, does that automaticly mean it's running? Example: Google Map. If it's in bacgound, is it still tracking where I am? Or will it only update when I have it on my main screen? Or lets say it uses my GPS. When in bacgound, is my GPS on or does it turn it off, and only turn it back on once I move it to my main screen?
kivine said:
more processing power used, more battery used
Click to expand...
Click to collapse
All apps, whether in the background or not, only use power when they "do" something. This is normally in the event of user interaction. Obviously, if you're watching a video or listening to music then the app is doing stuff without you interacting, but most apps have buttons and textboxes and lists etc. that require you to touch the screen in order to interact with them. In the case of applications like that, they literally sit there and do nearly nothing. They only react.
Of course an application in memory causes the device to utilise more memory and therefore more battery, but it's such an insignificant amount that you may as well say it's not using any. Try running 10 different apps that require input - notes, the remote desktop login screen, internet explorer on the blank page etc. - and see how much battery gets used. I doubt you'll see a significant increase.
Also bear in mind that there are apps that poll for information. There are apps that sit in memory and keep checking on the state of various things so that they can react to them. (Apps that do stuff when you rotate the phone - that kind of thing.) These are obviously active when they check things, so they can use more battery.
In your particular examples, it would be down to the software. Does the google maps app recognise that it's not in the foreground and stop polling gps information? That's purely down to the application and only Google (or the developers) could answer that specific question.
I think that's about it. Hope this helps

Sure fire way to stop background programs from running?

I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background. However there seems to be a number that like to restart even after I think I've disabled their startup, widgets, notifications, etc.
Is there a way to make sure programs that you install don't run? Or at least don't launch during start up? Perhaps something like msconfig in windows?
Thanks.
Raleran said:
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background. However there seems to be a number that like to restart even after I think I've disabled their startup, widgets, notifications, etc.
Is there a way to make sure programs that you install don't run? Or at least don't launch during start up? Perhaps something like msconfig in windows?
Thanks.
Click to expand...
Click to collapse
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
asrrin29 said:
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
Click to expand...
Click to collapse
Eh, this is the first I've heard this. I don't remember reading this in the various battery optimization guides.
Still is there a was to stop things short of uninstalling? For example, I want to stop using the Yahoo Mail app but don't want to install yet. I went through all the options I could to disable checking/notifications, etc but it still pops back into memory constantly.
I assume youve tried the obvious, turn off WiFi (3G) and screen when not actively using it?! Those are the big batt.-eaters
Sent from my HTC Magic using XDA App
asrrin29 said:
Killing background tasks will only decrease your battery life. When an application goes to the background, it sits in memory but does NOT consume any CPU power. since the memory is in solid state, it requires no power to stay in that state. By constantly killing background applications, it will need to start up, reinitialize, and consume more power then if you had just left it alone. Also, long term performance will be negatively affected, even if you do expereince a small short term performance gain. the Android OS is designed at the core level to have applications behave this way, and modifying that behavior will make for a worse experience.
Click to expand...
Click to collapse
Documentation? As far as I have read an application does not go into any type of dehydrated state when running in the background / minimized. It can do anything it wants including using CPU cycles.
I do agree that most applications do not need to be killed with a task killer but leaving 3D games (for example) running in the background could hurt your battery. Also not all applications are progammed with ther same fore thought and skill level.
I get about 33% more runtime out of my battery using a task killer to kill specific applications that I know I do not want running in the background.
Streaker said:
I assume youve tried the obvious, turn off WiFi (3G) and screen when not actively using it?! Those are the big batt.-eaters
Click to expand...
Click to collapse
I leave wifi on since I'm usually in range. It's more efficient than 3g right? I alway sleep the device when I'm done. I still have huge percentages on the screen when looking at the battery usage. I'm trying a completely black screen now.
Mainly your widgets and icons and stuff still cover large portions of it, so: a black screen will help, not but alot.
Also, to keep items in RAM, to the second poster... What do you think is keeping those items in RAM?
Ummm... It's the CPU.
Task Killers won't help you on RAM usage at all (Because Android will automatically shuffle them out if it has to, or so I've read... I've yet to hit max memory). Task Killers DO help you as far as battery use goes, though... Keeping the browser killed if you aren't using it, etc.
Bjd223 said:
Documentation? As far as I have read an application does not go into any type of dehydrated state when running in the background / minimized. It can do anything it wants including using CPU cycles.
I do agree that most applications do not need to be killed with a task killer but leaving 3D games (for example) running in the background could hurt your battery. Also not all applications are progammed with ther same fore thought and skill level.
I get about 33% more runtime out of my battery using a task killer to kill specific applications that I know I do not want running in the background.
Click to expand...
Click to collapse
I should clarify. I guess the term I meant to use is "suspended." If a program is actively "running" in the background, it will use CPU cycles. But if you simply stopped using a program, say for example the xda app, and returned to your homescreen, the application stays "suspended" in the background and consumes no CPU cycles until you go back to it. Now services that are updating, such as email or SMS, will use CPU cycles in the background because they are still actively running. But if you want to conserve battery life you can simply disable the notifications from most of these programs.
asrrin29 said:
I should clarify. I guess the term I meant to use is "suspended." If a program is actively "running" in the background, it will use CPU cycles. But if you simply stopped using a program, say for example the xda app, and returned to your homescreen, the application stays "suspended" in the background and consumes no CPU cycles until you go back to it. Now services that are updating, such as email or SMS, will use CPU cycles in the background because they are still actively running. But if you want to conserve battery life you can simply disable the notifications from most of these programs.
Click to expand...
Click to collapse
The app itself at that point may not be but the Android OS still does to maintain that suspended state.
I have some applications I rarely use or even some that I've never used but may want to in the future. I see absolutely no benefit in keeping these applications in the background. Further more, I've noticed a signficant drain on the battery when extra applications are running in the background. I'm sure it's not all of them, but I've yet to discover who exactly the culpit is. Right now I suspect it's the NPR app, perhaps due to data use?
The point is, there are perfectly good reasons to keep some apps in the background, and perfectly good reasons to kill others - or perferrably not have them start up at all unless I do it myself. Could be due to data usage (especially if you do not have unlimited data), could be due to concerns about excessive cpu usage. There really should be a clear method in which you can stop applications from opening on their own.
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Sent from my SAMSUNG-SGH-I897 using XDA App
Shuggins said:
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Wouldn't tasker also help?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sent from my AOSP on XDANDROID MSM using XDA App
To me, it's not a matter of "task killer or not", but rather when and where to use one. And I think it's simple: Don't bother, unless you suspect a specific app is doing something you don't want it to do in the background. Then, just kill that specific app and leave everything else alone. A Task manager that shows CPU% for each process can be handy for this as well.
I generally try to avoid killing tasks, but one night I had 50% battery on my phone and after about 2 hours or so I took it out of my pocket to make a phone call, and it was very hot and had about 12% of batter left -- something was running wild that shouldn't have been (I think it was Pandora, even though it was not currently playing any music!) So, background apps do occasionally run out of control, and you do need to occasionally kill them, but do it on an "as needed" basis.
Raleran said:
I'm attempting to try to increase my battery life so it lasts longer than 12 hours (~13 seems to be my limit). (I'll admit I'm a bit jealous of those who can run the phone 24+ hours) Though it's somewhat painful, I'm shutting down most the programs I have running in the background.
Click to expand...
Click to collapse
Unless the background process is syncing data, it won't eat your battery. So instead of wasting your time, you should focus on other energy hogs. Things like screen brightness, bluetooth, wifi, and gps.
Shuggins said:
You can use the program "Autostarts" to keep applications from starting at startup. With it you can also prevent things from launching under a number of other situations. That might be what you are looking for. Just do a google search for the APK as I don't think it is in the market.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I installed Advanced Task Killer from the Market. It lets you kill all running applications including itself.
durrence
jsmith8858 said:
To me, it's not a matter of "task killer or not", but rather when and where to use one. And I think it's simple: Don't bother, unless you suspect a specific app is doing something you don't want it to do in the background. Then, just kill that specific app and leave everything else alone. A Task manager that shows CPU% for each process can be handy for this as well.
I generally try to avoid killing tasks, but one night I had 50% battery on my phone and after about 2 hours or so I took it out of my pocket to make a phone call, and it was very hot and had about 12% of batter left -- something was running wild that shouldn't have been (I think it was Pandora, even though it was not currently playing any music!) So, background apps do occasionally run out of control, and you do need to occasionally kill them, but do it on an "as needed" basis.
Click to expand...
Click to collapse
Or an auto-killer would've killed it before it killed your battery by 38% lol
Task Killings are bad, mmmkay...
Slightly off topic:
To help conserve battery power,
Use an all black desktop background since the black areas dont use battery power.
Hmm, people in this thread have said a few things that I haven't heard or seen much before. Specifically that killing apps could decrease battery life. When I first downloaded advanced task killer I tended to kill most things. I slowly backed off and now I've been watching what launches and what tends to come back and not kill those (mail apps, widgets, performance watchers, etc). The second is that not having a black background doesn't necessarily improve battery life. Makes sense considering I have icons everywhere on my screen.
@Shuggins - Thank you! That's exactly what I was looking for. I've downloaded it but now I have to, er charge my battery a bit before I can take a close look at it.
@jsmith8858 - Are you running setCPU? A couple days ago I noticed my battery running pretty hot. I stopped using setCPU and the battery cooled down a lot. I've used setCPU since them without the heat issue so I'm not sure what was going on.
Well during todays iteration I ran for about 12 hours (typical). I had a couple short phone calls, 2 email accounts syncing as well as other bg syncing processes. I did eat up 30% in an hour messing with a game. I'd probably have 13-14 hours if I didn't play anything (but if I didn't what's the point of the phone . Still, as much as I love it the screen is killing me. Guess there's nothing to do about it though (usually brightness is all the way down, turn it off when I'm not using it, using a darker background). I didn't kill any of my background processes today. I'm going to set up that Autostarts program and start auto-killing various programs tomorrow.
You can try using autokiller and art it to extreme, but I don't recommend this
Sent from my HTC Dream using XDA App

Maps App Always Running

Did a search but found nothing substantial on this:
Does anyone notice their Google Maps is constantly running? And I don't mean in the cached menu. It's running in the "used" column (left column of the "Running" apps screen.
I'm certain Latitude is off, in fact, I unchecked all the location update options and then signed out of Latitude.
What's causing Maps to constantly stay open? Even after I close it and Stop it from the Running apps menu, it reappears moments later by itself.
Anyone know a definitive answer as to why?
onthecouchagain said:
Did a search but found nothing substantial on this:
Does anyone notice their Google Maps is constantly running? And I don't mean in the cached menu. It's running in the "used" column (left column of the "Running" apps screen.
I'm certain Latitude is off, in fact, I unchecked all the location update options and then signed out of Latitude.
What's causing Maps to constantly stay open? Even after I close it and Stop it from the Running apps menu, it reappears moments later by itself.
Anyone know a definitive answer as to why?
Click to expand...
Click to collapse
The answer I gave to someone asking about Task Killers earlier today in another thread pretty much answers your concerns here. I'll quote it below.
In addition to the explanation of why you shouldn't worry about killing apps I'll add that on my phone Maps is also always running, but it's not sucking up any resources I need (like juice or cpu) so I don't care that it's "running"...and neither should you unless you see it misbehaving.
Android's memory manager has decided that Maps is one you'll need or want running, so it's going to keep re-loading it until something else with a higher priority takes its place.
If you really just can't stand that it's running or it's affecting performance of the phone, there's a root-required app in the Market called AutoStarts, which let's you mark apps as not being allowed to start automatically under a particular situation. You could use that to mark Maps as not able to start on bootup or whatever, but be aware, Android will just load up a different app to fill up that unused memory space...
distortedloop said:
In Android, free memory is wasted memory. People not knowledgable in how Android manages memory think that they're accomplishing something by killing tasks in the hopes of freeing up memory. It doesn't work that way.
Android has a threshold of what amount of free RAM should be maintained, and then does its best to fill up the remaining RAM with apps and stuff you might want to use later; it's like pre-loading your stuff so it loads faster.
The irony of people using task killers to free memory up to "improve performance" and "save battery" is that in most situations they're doing just the opposite. If you kill an app with a task killer, Android will frequently just re-open it in the background to frill up that empty memory space back to its thresholds, thus using up more cpu and juice to reload it.
There are apps or even terminal commands (for root) that let you change that threshold number, and on other devices (2.2 and lower) for me, tweaking that number did sometimes make the phone feel snappier, but it was real trial and error to get it right. I haven't felt the need for it on the Gingerbread Nexus S.
If you're interested in trying something like that, check out AutoKiller Memory Optimizer. Don't let that name fool you, it's a poorly named app, this is NOT a task killer app, it's just a GUI interface to the minfree settings that tell Android's own memory manager what thresholds to use.
There's another one I used to use MinFreeMgr or something like that, but I can't find a link.
And finally, there are limited times that killing tasks is beneficial, one would be if you have an app that's run amok and won't exit on its own. I'm sure there are others, but it's usually a good idea to avoid that practice.
Click to expand...
Click to collapse
Sometimes it happens to me, but a reboot solves this issue.
Thanks Distorted for the explanation. A few more questions:
How come if Google feels it's necessary to keep it open, it's not in the Cache menu? They feel they have to keep it up and running? It can't be cached? Why? I'm mostly just curious about this.
Secondly, also for curiosity's sake, how much percentage does Maps show in your Battery Usage menu? It shows about 2% for me, and that's without actually using it. I'm guessing the 2% is just from running by itself.
It's not detrimental to my performance or my battery (2% is small), but I'm justu wondering why it needs to stay open, and what others' readings are in terms of batt. usage.
I've never noticed Map in my battery statistics as something listed. It's been running all day since I responded earlier, and not there.
2% may or may not be an issue, it depends on what else is used up. And remember, that 2% doesn't mean it used 2% of your total battery charge, it means it's used 2% of what's been used so far.
You lost me with cache menu; not sure what you mean there.
I just peeked at Maps in the Applications/Running apps again. If you click on it in there, it shows 1 process and 1 service. It looks like the service is the "network location services". I'm just wild guessing now, but perhaps it's related to having "use wirelss networks" or use "GPS satellites" enabled in Location & Security menu of Settings. Try turning those off and seeing what happens.
Also, you know that in the battery history screen, you can tap on anything that's listed there and it will give you more details on a new screen? Could you tap that on yours for Maps and see what it actually says? Maybe show a screen shot if you can capture one.
Sign out of latitude that's what is using it.
Sent from my Nexus S using XDA App
leerobson99 said:
Sign out of latitude that's what is using it.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
He said in his first post that "I'm certain Latitude is off, in fact, I unchecked all the location update options and then signed out of Latitude."
I'm curious what other locations aware apps or activities he might have enabled.
When you go to the Running Applications screen, if you click on the lower right of the screen (somewhere near the "Ram" or "200 MB free" indicator) it'll switch to the cache screen.
Anyway, after a night's full battery charge, Maps no longer shows in the Battery Usage screen, but if it shows up there again, I'll click on it and share more info. I do have "Use Wireless Networks" checked, so perhaps that's the culprit? GPS is unchecked. I only check it when I need to use Maps or Navigation. But I'm not running any location update apps.
But again, it seems it's not doing anything detrimental to my CPU or battery, so this is more of a curiosity's sake. Will report if I find anything new.
onthecouchagain said:
Thanks Distorted for the explanation. A few more questions:
How come if Google feels it's necessary to keep it open, it's not in the Cache menu? They feel they have to keep it up and running? It can't be cached? Why? I'm mostly just curious about this.
Secondly, also for curiosity's sake, how much percentage does Maps show in your Battery Usage menu? It shows about 2% for me, and that's without actually using it. I'm guessing the 2% is just from running by itself.
It's not detrimental to my performance or my battery (2% is small), but I'm justu wondering why it needs to stay open, and what others' readings are in terms of batt. usage.
Click to expand...
Click to collapse
I have noticed it running also after I do a reboot but usually after a few hours the system usually moves it to the cache menu. I have tried to force stop the process but it will usually come back a little later. I noticed the same thing with the android market.

TaskPanel, Autostarts, and when to use a task killer

Please dont 'quote' this as it VERY lengthy, just copy and paste the this first sentence.
I wanted to write up a definitive posting on task killers as I think they are way to often misused and misunderstood and I am getting quite tired of reposting this same information.
I use a task killer called TaskPanel XTRA (its free). BUT, I ONLY use it for killing tasks that are misbehaving (an app that has slowed down or nearly hung your phone or an app that is CLEARLY causing battery drain or sending copious data via your cellular connection). If an app continues to misbehave, switch to a different app that offers the same functionality, do NOT continue to use a task manager / task killer to kill an app continuously.
Task killers should NEVER be configured to automatically kill an app (as I will explain later in the post) and should NEVER be used to manually kill apps UNLESS it is a small emergency (as in major battery drain, copious cellular data, massive processor usage/memory usage preventing the user from using the phone normally).
Android is a VERY powerful operating system which gives YOU THE USER the control to manage your phone (hence the major reason I dont like the IPhone or Windows Phone), but with that control comes responsibility. As I will explain shortly, Android has many built-in features in place to help you manage your phone's precious memory. While there has been much nonsense one way or the other as to whether task killers should be used for anything other than a misbehaving app, I tend to listen to the creators of a product before I listen to some jackass who bases a decision on pure speculation or a 'feeling' he has. I can tell you that I have not used Task Panel in the last 4 months (with the exception of I believe Pandora which I used about a month ago and could not find a way to actually exit the app - guess what...this app is no longer on my phone - both because of privacy concerns that recently came up about Pandora AND I dont keep apps around that I cant manually exit the app cleanly).
For a VERY good write up (with a brief 'readers digest' summary at the bottom with plain English bullet points, since most of the article is taken directly from the Android developer FAQ and is very techy for non-programmers), have a gander thru this.
http://geekfor.me/faq/you-shouldnt-b...-with-android/
And for the FAQ they quote most of the above article from (but I do recommend you read the above FIRST as it will give you some context - much of the reasons are 'cherry picked' from different areas of the FAQ to help you understand why this is important and give you the information that is relevant to the discussion as to why task killers are not a good thing). All of the relevant information is in the page that will load up (in the rightmost panel / frame) so you dont need to click any links to read the relevant article. I am only providing this link as a reference to the original source material so you dont think I am just making this up - this is straight from the horses mouth so to speak (again, for most people, dont read this FAQ, read the one above first to get context and then if you feel you want to know more, read this link below).
http://developer.android.com/guide/t...damentals.html
Alright, enough about task killers, now to deal with how to manage those pesky apps that seem to always be running (even if you never started them) and how to keep them from starting up using a method that will NOT affect Android and how it manages your memory but will keep your phone in peek performance.
For managing the conditions when an app starts up, use an app called Autostarts, do NOT use a task killer to 'auto kill' tasks. Autostarts literally allows you to control the conditions of when an app starts.
Android has built in functionality for managing the memory footprint of various apps and will manage your phones memory quite nicely. Much of the functionality of the built in memory management came in Android 2.2 (also sometimes referred to as Froyo) and is really quite good 'if' you allow the phone to manage processes rather than just quickly killing everything.
There is a reason you can no longer just 'kill' system level processes, Google wants you to allow Android to 'learn' how to manage itself.
Android has a very powerful feature, the ability for app writers to start their app when certain conditions occur. The problem with this powerful feature is, often times, apps are bloated or poorly written, many times being started for any little thing your phone does (wifi on or off, Bluetooth on or off, location changes, screen on or off, USB connected, cellular connection, headphones connected, a cow fart, a bird poops, etc.). Even Google itself has been guilty of this, Google Maps (until recently) would be started in nearly 20 different conditions as a background process for very trivial things and was a major source of battery drain (it still is to some extent). This is where Autostarts comes in. Use Autostarts to control the conditions of when/if an app will start up automatically based on a certain condition.
Most ancillary apps (apps that are not integral to the core functioning of the phone - although it is probably more appropriate to refer to these as 'user apps', it isnt quite accurate because many 'system apps' (which in the technical description are apps that are installed with the rom) are not core apps either. For example, many roms come with Youtube pre-installed (meaning you do not manually have to go to the market and install them) which is not integral to the core functioning of the phone), these apps do NOT need to ever start under ANY condition for that app to function normally. The only considerations for an app starting itself would be the widget updating, the app has a scheduled event (for example, an alarm, a podcast client downloading podcasts at a certain time of day, Titanium backup performing a scheduled backup, etc.), or an app that has to be running in the background to perform a task when certain conditions arrive (for example, an app called Sanity needs to be available to run and monitor for incoming/outgoing phone calls so that it can start itself and perform its function during a phone call).
Using Autostarts, I have disabled nearly 80% of EVERY condition that all NON-system apps start under (I havent counted but for 70 apps, this is probably 55 apps or so that I disabled EVERYTHING these apps would start under). This includes Google Maps (yep, even Google is guilty of having an app needlessly running when it doesnt need to).
By taking control of your apps (in essence, disabling as many apps from 'auto starting' until YOU the user launch the app manually) and properly quitting an app when you can (within the app, find a way to click a 'quit' or 'exit' button to allow the app to remove itself from memory) rather than just allowing apps you launch to run in the background, you can save yourself massive amounts of battery life, limit cellular data usage, AND allow Android to properly manage itself.
Think of it like this, if I were trying to learn something but you (the user) kept doing it for me, Id never learn. And if you read the above linked article, you will begin to understand why there is more to this than just allowing Android to learn.
To give you an idea, using Autostarts to disable any non-system app that does not need to be running, if I am using the stock battery, I can run my phone for 2 days pretty easily if I simply turn off cellular data, Wifi and Bluetooth when I dont need it, maybe even stretch it to 3 days.
My ram usage is almost always around 50% (150 MB free) on a fresh reboot (around 2 minutes to allow the phone to stabilize) and it remains this way during the day because I exit apps when I am done using them, even tho I have around 80 apps installed, and I dont allow apps to just start themselves because they sensed a fart in my general direction.
For those of you that use a Windows PC, you can think of Autostarts as a proper 'msconfig'. Keeping your PC clean of apps when windows starts keeps your PC running much more smoothly. Autostarts takes this to the next level and keeps apps from ever starting in the first place rather than a task killer 'auto killing' a task, the app restarting, the app getting 'auto killed' again by the task killer, the app again restarting, etc. (a vicious cycle that both kills your battery because the phone has to crank up the cycles on the processor to both start and stop the app, the power used to write and clear the data written to both ram and 'perma' storage (if an app needs to store any data), and cellular data (if an app 'phones home' so to speak when it initially launches (which is both a cause for additional battery usage to send data and also adds to the amount of data your phone transmits over the cellular network, which is a problem given most cell plans have a monthly data cap).
Autostarts is fairly easy to use but does require root.
The app is $2 and here is a brief synopsis of how to use it:
When you initially launch the app, read any dialog messages that appear and click ok thru them. Then, wait for the app to finish loading (there is a progress bar at the top that will fill with yellow - on my phone it takes about 45 seconds to a minute to finish loading in).
Once it is loaded, you need to configure a few things BUT, you might want to just scroll thru the list of things currently on the screen. These are the 150+ conditions that apps currently installed on your phone are starting up under (dont click anything just yet, just browse the list if you are curious).
Right now, the app is configured to show a list categorized by conditions. This unfortunately is not very helpful. We need to change it to sort this list by apps rather than by conditions (so that we can literally disable EVERYTHING an app will automatically start under rather than scrolling thru every condition).
So, hit your menu button and the top left most icon in the menu that appears is an icon 'Group by application'. Hit that icon and magically, you are now seeing every app. You can now click an app and see all the conditions every app starts under. Neat.
But there is one more setting to change first in order to help keep you from doing something you should not.
(Optional but HIGHLY recommended!) Hit your menu button again (if you exited out of the menu already) and hit the upper right most icon, the 'View' button. Tick the topmost checkbox, 'Hide system apps' and hit the 'Ok' button. This will keep you from disabling anything that 'may' be critical to your phone operating.
Now, exit the menu (the 'back' button on the phone itself).
If you decided not to hide system apps, these will appear in YELLOW. It is probably not a good idea to mess with these unless you know what you are doing. Messing with these can cause a soft brick or make your phone unusable in certain conditions (for example, if you prevent the phone.apk app from ever starting, you will never be able to take phone calls).
Now, start scrolling thru the list (start at the top). If it is an app that does NOT need to run in the background, expand the app by selecting it and starting with the topmost condition that app starts under, tap each condition and in the menu that appears, select 'Disable'. Do this for ALL conditions for each app you want to manage. When you are done disabling the conditions, go to the next app and decide again whether that app needs to run in the background or not.
As a brief summary, to consider whether an app should be allowed to run in the background, ask yourself the following:
Does the app:
a. ...have a widget that you are actually using on your home screen that needs to update? For example, a media player or weather widget should NOT be disabled...
b. ...have a scheduled event such as checking the weather, downloading new podcasts, checking email, etc?
c. ...need to perform a certain task or provide some extra function(s) when a specific event happens (such as recording a phone call when it comes in, an eq when audio is playing, etc.)?
My recommendation is, if you answered YES to any of the above questions, leave all the conditions that app starts under alone (unless you know what you are doing, its best not to mess with it as I will explain in a moment).
If you answered NO to all the above, DISABLE ALL of the conditions that app starts under (again, DONT mess with system (yellow) apps and certainly dont disable every condition for these).
I recommend an all or nothing approach for each app is because if an app doesnt behave properly, it can become a major pain to continue to open Autostarts and try to track down a specific condition you disabled that is stopping / preventing that app from functioning the way you want it to.
Every time you update or install an app, if you remember, try to open autostarts and review the conditions the app starts under. Updated apps often times will add something new and if you have this app completely disabled, it may find a way to start itself again.
And, dont worry, you cant permanently screw anything up (unless you are messing with system apps - get the reason why I recommend not playing with system apps?). If an app stops functioning correctly, just re-enable the conditions that app starts under. Pretty easy.
Hopefully, this is complete enough, I will now just link to this post everytime I need to mention autostarts. I am getting quite tired of posting this same information .
Good information for people. Well done.
Sent from me to you using stuff

Battery

I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Dr_Nacho said:
I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
A bit more information is needed before a specific course of action can be recommended. How much battery life are you using in an average 24 hour period? Also, what version of Juice Defender(beta, free, plus, ultimate) are you using, and what specific settings are you utilizing. It is a very customizable program after all. You might look into Battery Indicator Pro, which estimates your total remaining battery life based on your level of usage. I would also recommend CPU spy, which, if your device is rooted, will show the percentages that your device is running at various CPU levels.
If you turn off all the locational stuff, turn off 'update my current location' in Navigator, and set your CPU gov to conservative, you might get better battery life. I've not had any lasting luck with any of the battery saving apps. In the end, I decided to buy a couple of Anker batteries from Amazon just in case I have a bad battery day... Also some of the battery saving mods work, but I'm not sure about applying them to ICS and JB ROMS. I haven't tried!
Battery life is what you make of it..
Anything running in the background will drain the battery.. email constantly checking for new messages, twitter, Facebook, GPS, WiFi if no connection is found, etc..
Anything that makes the phone process even while the screen is off is going to kill a battery..
What ROM are you using? Some ROMs have better life than others..
How much are you actually using the phone?
What's the brightness set at?
Have you tried changing the processor and slowed it down?
Lots of information that is missing is helpful..
Its powered by Jellybeaned AOKP!
I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery
Click to expand...
Click to collapse
Some have good luck with these, others don’t. I prefer to try to adjust settings myself.
I believe it primarily happens because my data (mobile network) consumes it.
Click to expand...
Click to collapse
How about putting a widget on your homescreen to toggle data on/off. Keep it on only when you need it. I go a step further, I use Tasker to automatically turn my data off every time my screen times out (because that means I’m not using it... I can restart my data later with my widget when I need it). Maybe that’s extreme, but I’m not just watching my battery.. I’m managing my limited data plan.
My phone is drained throughout my day, even without use.
Click to expand...
Click to collapse
It may be that you have wakelocks keeping your phone awake when it’s supposed to sleep. One way to see this is (in GB or above) Settings / About-Phone / Battery Use...then click on the small graph at the top... should expand it to a large graph with traces along the bottom including Awake and Screen On. If you have long periods of time where phone is awake while screen is off, that’s a wakelock problem. A good program to troubleshoot that is Better Battery Stats. If nothing else, follow the instructions in the first post in the BBS thread linked below, and then post a dump to the end of that BBS thread (the developer and a lot of other knowledgeable people follow that thread and will help you interpret results):
http://forum.xda-developers.com/showthread.php?t=1179809
Thru use of BBS, I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
electricpete1 said:
I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
Click to expand...
Click to collapse
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
atrix4nag said:
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
Click to expand...
Click to collapse
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
electricpete1 said:
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
Click to expand...
Click to collapse
Thanks for your detail explanation. My main question was how can close the app without restarting? i feel my major battery drain is from dolphin browser, befor dolphin i used opera, even that has the same problem. Most of the time, if I dont open dolphin, my phone battery is good, but once I open it, it drains battery. So i am looking for soemthing simple which does, without rebooting the device.
Any way thanks for your help.

Categories

Resources