yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] matanc1:
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.
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] matanc1:
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?
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] matanc1:
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.
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] matanc1:
Okay, so just one last thing:

Do you have any suggestion to try and improve the battery life?
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] matanc1:
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 ).
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] matanc1:
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?)
[Android Software/Hacking General [Developers Only]] NickWarner:
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.
[Android Software/Hacking General [Developers Only]] matanc1:
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?
[Android Software/Hacking General [Developers Only]] NickWarner:
I won't say with absolute certainty that it can't ever happen, but it's unlikely. It might take a few extra steps to ensure it, though. For example, when you root, you also put a new recovery in place (CWM, usually). This recovery survives flashing, so if/when you went back to a stock ROM, you'd also have to revert to a stock recovery.

Usually, you can ask one of the ROM devs for your device for a procedure that will completely undo the changes they're making. In some cases (the Thunderbolt, specifically), there's a stickied thread in the dev forum that explains how to go about unrooting your phone.

Concerning warranties: It all depends on what's wrong with the phone and who's looking at it when you take it in. If, say, the screen falls off or a button gets stuck, that's a hardware issue and in no way caused by rooting. Generally, they won't even look at the software before sending it back. Once it's at the factory, it gets wiped regardless. Granted, you're still liable if they do find out (and care), but the chances are much less.

If it's a software issue, the first thing anyone recommends is going to be to go back to completely stock (unrooted) to make sure it's not a device issue. At that point, if it is a device issue, you're all set for a warranty return.
[Android Software/Hacking General [Developers Only]] scottspa74:
Nick seems to have covered all bases here, and his answers should probably answer my question about maps, too. But still, I will say about google maps, if I don't force stop it thru settings>manage applications, I get poorer battery life. It even shows up in my battery log as 8-15%.

I also keep gps and wifi and BT off,unless I need it. But 3g is always on. I always kill maps after boot now.

Also, running a more aggressive havs kernel with bfs seems to help android kill unnecessary activities more promptly.

Evo. Virus rom (usually). Netarchy kernel.

Thanks for all the clarifications nick
[Android Software/Hacking General [Developers Only]] scottspa74:
And as to the root/warranty question, nick also nailed it. I've taken my quite-obviously rooted evo in to a sprint repair center for screen replacement, camera replacement, etc. many times.

As ling as it's hardware related, you're fine. If it's software related, more often than not you can fix it yourself with root access.
[Android Software/Hacking General [Developers Only]] NickWarner:
On my Fascinate, there was a particular version of Maps that would hold a WakeLock on GPS upon startup unless you toggled data and GPS off/on before you opened Maps the first time each boot. It was incredibly frustrating.

Granted, Maps is very data-hungry and GPS/cell triangulation/WiFi triangulation uses quite a bit of power in and of themselves, but other than that one particular bug, I've never had any trouble on my Fascinate or Thunderbolt with Maps. Or, I should say, unexpected resource drain.
[Android Software/Hacking General [Developers Only]] matanc1:
Thank you very much, you've certainly clarified many issues for me :)
[Android Software/Hacking General [Developers Only]] matanc1:
Just one more question: does enabling the data connection without using it waste battery?
[Android Software/Hacking General [Developers Only]] NickWarner:
Yes, you'll see more power consumption when leaving data turned on, since the phone's maintaining connectivity to the data network. Also, your LTE/WiMax radios consume quite a bit more power than your CDMA/GSM radios as well, even when idle, so keeping data on at 3G instead of 4G will have a marked difference in usage.

This is the point where your Allow Background Data setting will have the most effect.

If you allow background data, you're saying that services and background apps are allowed to use whatever means available (cell, WiFi, etc.) to access the Internet even when they're (or their controlling app's) not on screen. In this scenario, you'll see additional data use and power consumption while the phone's idle.

If you turn off background data, you explicitly tell apps that you don't want them to connect to the Internet unless they're actually on the screen. In this scenario, you'll see much less data use and power consumption while the phone's idle. Bear in mind, though, that it's possible for an application to ignore this setting (and I assume that some of the core processes will ignore this setting in order to do their jobs).
[XPERIA X10 General] gAracUh:
guys i really need help about my phone

Mobile number: SO-10B

Baseband 2.0.52 (i forgot sorry) im currently stock in se logo

everytime i root using flashtool 0.2.0.8 and install bussybox and xrecovery then flash JIT i always stock on SE logo even i try many times. im so sad this phone if i didn't install JIT. what wrong my device? it will need a right tool for rooting? everytime i root always they have a red message like didn't expect need to ro.build.prop ect. guys anyone here using my same device NTT docomo S0-10B from japan please tell me the right the right step:(
[XPERIA X10 General] aR_ChRiS:
Maybe try flashing to a global generic firmware then install JIT? I'm not sure whether the JIT mod would work on the Japanese firmware.
[XPERIA X10 General] gAracUh:
i dont want to flash im afraid what causing my phone aside in stock in SE LOGO:( any suggestion?

EDIT: if i flash this using other firwmware what firmware should i choose? and even im on other firmware im able to updgrade to 2.3 this coming update form sony?
[XPERIA X10 General] gAracUh:
please anyone? or some help from pinoy, pilipino here.
[XPERIA X10 General] Horayken:
When you install or add new tweaks to the phone.. first you should make a nand backup of the Rom. did you install the Xrecovery? because there are 2 .ZIP which allows you to install or remove the JIT. try to find thoose zip and remove to see if it works. and remember to always make a backup to prevent to flash the device again and loose everything ;)
[XPERIA X10 General] gAracUh:
yes i install xrecovery the latest one. i do some search but i dont if this true JIT is not compatible with mobile number SO-10B is this true?
[XPERIA X10 General] CMoney87:
DO NOT install JiT if its already installed, it will break your FW and you will need to reflash. Flash global generic and try again. Only try and install one time, the only way you'll know its installed is by benchmark score improvements.

Sent From My *Super Fly X10*

If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
[XPERIA X10 General] OmegaRED^:
"wipe dalvik cache" after installing jit.
[XPERIA X10 General] gAracUh:
thank you for reply sir CMoney87 and OmegaRED^ @OmegaRED but i did "wipe dalvik cache" right after i flash JIT.

@CMoney87 that my problem sir after i flash JIT im stock in SE logo and about flash i dont know what the right firmware for my device to flash without bricking or stock in SE LOGO again can you choose firmware for me in this thread? http://xdaforums.com/showpost.php?p=10879519&postcount=2

sorry for my super newbie im new in xperia x10 i came from wildfire.

EDIT: X10i_2.1.A.435_GLOBAL-GGL GENERIC this one can flash in my device? or this? Generic version 2.1update1 build 2.0.2.A.0.24 please tell me if choose is wrong.
[XPERIA X10 General] acmode:
well honestly i would choose this "2.1_2.0.2.A.0.24 with DualTouch already in HERE just need to flash once" and then install a custom firmware because i believe they already have jit installed (but please correct me if im wrong)..

http://xdaforums.com/showthread.php?t=1085918

this is my personal favorite but look around see what u like.
[XPERIA X10 General] agentJBM:
Definitely global generic 2.1.A.0.435. It is newer and has dualtouch, and you will be certain to get the official 2.3.3 Gingerbread update directly from PC Companion or SEUS when available.
[XPERIA X10 General] tsuyo.kou:
On Japanese fw jit cant work correctly.

If you wanna use jit on Japanese fw,you must use goro's.

Search with google in Japanese.

Then you'll find it soon
[XPERIA X10 General] Slothagus:
no jit in japan?? bruutal
[XPERIA X10 General] gAracUh:
thank you all for reply and information this will help me a lot thanks again.
[XPERIA X10 General] CMoney87:
If your gonna flash new FW and root you might as well install a custom ROM. All custom ROMs have JiT enabled so if you go custom DO NOT, under any circumstance, try and install JiT.

Sent From My *Super Fly X10*

If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
[XPERIA X10 General] gAracUh:
One more question about before flashing. my device is came form japan S0-10B and now im going to shop to unlock this to use my simcard because im here in philippines. after the unlocking this phone and flash the unlock will gone? or not?
[XPERIA X10 General] aR_ChRiS:
I think they are separate. You won't lost your sim-unlock once you have flashed your phone.
[XPERIA X10 General] gAracUh:
that's i think too thanks for info. thanks again.
[Galaxy S II General] matanc1:
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
[Galaxy S II General] RogerPodacter:
you dont close them because they dont drain battery. that is the way android OS and its apps are written. when they lose foreground focus, they do into paused state.

there is no way for you to exit them.

now that said, there are some apps that are buggy. the facebook app for example eats my CPU when i am not using it, because they did not code it properly.

best thing you can do is use the paid version of system panel to use monitoring to see what actually is using your CPU when in the background. this will prove to you what is and is not using resources.
[Galaxy S II General] cmd512:
I started a thread on this as this was my exact issue: My "Awake" bar would be solid for over 8 hours when I had absolutely nothing 3rd party running... but there are buggy apps that still stay awake as a cached process.

More of my issue and fix here:

http://xdaforums.com/showthread.php?t=1094666