Just a word to the wise: if you're having any Launcher crashes and screen brightness changes, it might be due to having the ASUS Task Manager widget running. I noticed that whenever I switched to the screen containing that widget, the screen dimmed, then returned to normal when I switched to another screen. Also, my Launcher was crashing, and I just today noticed it was only crashing when I switched to that screen.
I've since removed the widget, and those problems went away.
Sent from my Transformer Prime TF201 using Tapatalk
I haven't had any of this, but I have noticed that at low brightness settings just about any ASUS widget causes an annoying sputter of the brightness.
I also have the ASUS Task Manager fc all the time, so I just don't use it. Android isn't supposed to need such things anyway and I have faith lol
Task manager does fc pretty often. Thing is I find it so useful. Ill see things running and be like wtf is that doing running. I have no plans on using that app or process n has no business being in active tasks. Lol. I might go a similar route and get rid of it for a while. But its really the only way tl truly close an app out. You can back out of browser n think its closed but its still actually running in background burning up ram unless you manually close it through task manager or system panel.
Ill see how long I can go without needing to use it or look at it and see how things go. Still been getting annoying android.androidprocess.media has stopped message. Need to figure out what is constantly causing that. Hopefully getting rid of Asus task manager will solve that.
demandarin said:
Task manager does fc pretty often. Thing is I find it so useful. Ill see things running and be like wtf is that doing running. I have no plans on using that app or process n has no business being in active tasks. Lol. I might go a similar route and get rid of it for a while. But its really the only way tl truly close an app out. You can back out of browser n think its closed but its still actually running in background burning up ram unless you manually close it through task manager or system panel.
Ill see how long I can go without needing to use it or look at it and see how things go. Still been getting annoying android.androidprocess.media has stopped message. Need to figure out what is constantly causing that. Hopefully getting rid of Asus task manager will solve that.
Click to expand...
Click to collapse
As for the browser, don't back out. Just close all the tabs, and it'll close the tab and the browser absolutely.
As for all the other processes, I know what you mean, but my battery is much less affected ignoring them than killing them (using the screen and sensors) and just having them return with time.
The task manager is about junk.
FC often.
Stops keeping up to date often.
Sizing makes it contract to center versus close up from bottom.
Wont accept interactions.
There's no need to kill the Internet browser task. RAM uses the same amount of battery all the time as it requires a constant charge to prevent it losing its data. If you fill RAM up, the power usage stays constant. Android will close background tasks if a foreground task requires more memory.
Only ever kill tasks if they're inexplicably using CPU.
I dont think the merits of task killers is at question. The lame task killer is.
Lock-N-Load said:
I dont think the merits of task killers is at question. The lame task killer is.
Click to expand...
Click to collapse
Both really.
I mean, this is certainly the more useless of the ones I've tried. But even the best of them are generally useless considering the platform we're on. The only decent ones are those that watch your CPU usage per app (like watchdog or whatever).
I guess it gives people peace of mind, but the only time it is actually good to use one is like danieldeanhodge said, when there are run-away processes sucking CPU usage. That's what gives you battery drain as the RAM stays pretty consistent on its consumption: that's why the TF700t is going to have worse battery life under all circumstances, it has more hungry RAM.
Crashes for me all the time too. I removed it.
Do note that I'm not specifically talking about the Task Manager widget itself crashing. I actually didn't get that very often. What was happening to me is that the Launcher was crashing--it would throw up the "Wait or Close" dialog and then all icons and widgets would disappear from the home screens. I'd have to go into Settings and force close Launcher to get them to come back. After too many times of that, I'd have to reboot to resolve.
Getting rid of the Task Manager not only solved that problem, but it also resolved the issue of the screen brightness being inconsistent as I changed home screens, and also my UI is much smoother as well.
Bottom line is: I think the ASUS Task Manager is just really badly done and turning it off made a world of difference in how my Prime is performing.
wynand32 said:
Do note that I'm not specifically talking about the Task Manager widget itself crashing. I actually didn't get that very often. What was happening to me is that the Launcher was crashing--it would throw up the "Wait or Close" dialog and then all icons and widgets would disappear from the home screens. I'd have to go into Settings and force close Launcher to get them to come back. After too many times of that, I'd have to reboot to resolve.
Getting rid of the Task Manager not only solved that problem, but it also resolved the issue of the screen brightness being inconsistent as I changed home screens, and also my UI is much smoother as well.
Bottom line is: I think the ASUS Task Manager is just really badly done and turning it off made a world of difference in how my Prime is performing.
Click to expand...
Click to collapse
That's nuts, the launcher crashing...
I think all the ASUS widgets are this way with regards to the changing brightness (only happens to me on lower settings). I've noticed it with the Task Manager and the Weather anyway.
I appreciate their work, but ASUS is a h/w manufacturer: I don't understand why they're trying to be another closed system or why they're trying to push themselves as a major developing team or whatever, but they don't seem to be doing well with it.
Related
Ok I have looked around and have not found the answer. SO here Goes
In windows if you want to keep the memory that you have clear of background applications, you can run system configuration and just remove the check-mark for those items you dont want to auto start.
I have Advanced Task Killer installed and will set it up to auto kill and will manual kill apps as well. Instead of consistently looking at ATK to shut down apps, is there a way to just keep all the apps you not using nor have ever started from suddenly being there and sucking the life out of your battery?
Having applications "running" in the background (i.e., still in memory but in a suspended state) does NOT negatively affect your battery life. These applications are actually just remaining in memory because that memory does not need to be used by anything else at the moment. If an active application gets to a point where it needs more memory, Android will automatically close applications that are in a suspended state (i.e., not actively being used) to make room.
In other words, using an app killer is NOT necessary and I definitely recommend NOT using one. By closing the application repeatedly, you are just causing the application to take a longer amount of time to start up next time you use it. You're making your Android experience worse by using one, not better.
There is one caveat to this, and that is when you have an application installed that doesn't play nicely -- i.e., even when you stop using that application, it will continue to use up CPU cycles (never go into a suspended state). This is actually pretty rare unless you are installing really poorly written programs, but it can happen to some popular apps too (usually the result of a bug). In this case, you should either uninstall that application or use an app killer to only kill that one app.
I've heard both sides of this argument, and don't know who to believe. I didn't think I needed a Task Killer, but then I saw it repeatedly on "top 10 apps for Android" and "must have Android apps" lists from respected sites like cnet... who to believe?!
Cnet ≠ respected
Sent from my Liberty using XDA App
drumist said:
Having applications "running" in the background (i.e., still in memory but in a suspended state) does NOT negatively affect your battery life.
Click to expand...
Click to collapse
I need to confirm this. Anyone? I dont care about memory because I bet Android excels at that, and at any rate, memory is there to be used, not to keep it empty.
But I come from a Symbian smartphone and "minimized" applications DO uses battery. Maybe little, but noticeable.
Anyone can confirm that background apps consume negligible battery juice?
Additionally, is there a nice task changer? Like windows Alt+Tab. I feel my Android like an iPhone, that I need to press the home button to move to another already opened app and that's just plain stupid. So far I'm using Multitasking Lite, but it can get sluggish once there are too many apps opened. Any suggestion would be warmly welcomed.
"Running" background apps DO NOT consume battery life unless they're actively syncing. If it's just in the memory saving the state of the app then that is fine.
As far as using a task killer, if you are manually killing apps and they keep starting back up then that is a bad thing for your battery. The app uses cpu cycles everytime it starts up again and syncs data. You can use a task killer to close apps that opened on startup or when you're done with them. If they stay closed until you choose to open them again then you're saving memory, but nothing to do with battery life.
ocswing said:
"Running" background apps DO NOT consume battery life unless they're actively syncing. If it's just in the memory saving the state of the app then that is fine
Click to expand...
Click to collapse
Thanks for confirming ;]
Darius_bd said:
Additionally, is there a nice task changer? Like windows Alt+Tab. I feel my Android like an iPhone, that I need to press the home button to move to another already opened app and that's just plain stupid. So far I'm using Multitasking Lite, but it can get sluggish once there are too many apps opened. Any suggestion would be warmly welcomed.
Click to expand...
Click to collapse
Obviously you can switch over to some apps by pulling down the notification menu and selecting the appropriate app. That only works on apps that put themselves in the notification menu though (multimedia apps and things like Google Nav usually do this).
Otherwise, you can press and hold the home button to bring up the list of 8 most recently opened apps without exiting the active app. This works but like I said, it's the 8 most recent apps, so it will list apps that aren't necessarily still running anymore. It's more of a shortcut to having to go search in your apps menu or home screens to find a recent app than a way to see what is currently running.
drumist said:
Otherwise, you can press and hold the home button to bring up the list of 8 most recently opened apps without exiting the active app. This works but like I said, it's the 8 most recent apps, so it will list apps that aren't necessarily still running anymore. It's more of a shortcut to having to go search in your apps menu or home screens to find a recent app than a way to see what is currently running.
Click to expand...
Click to collapse
What can I say, I hate pressing the home key to hunt for the icon that opens the app I already opened more than 6 other apps ago ;] Guess I'll stick to Multitasking Lite for the time being. Thanks!
My biggest quirk with hc is the deplorable implementation of a task manager. It actually slows me down while multitasking because it makes it hard to tell what I am and am not doing. Is there any way to implement the ics task manager?
I can handle the bar at the bottom and lack of buttons... But, at least gb only kept a few task that weren't up...when I see the last 11 things i was doing even if it isn't open..it just gets annoying.
Anyone know how to fix it?
To me I find the task mgr harder to process than the simple version
In the gm notifications menu. The previews are just clutter and having to scroll through the list just seems unnecessary.
If I could hit the button on the taskbar and just get the old popup that you used to get from holding the home button then it would be an improvement. It's harder to get simpler or more efficient than that.
Sent from my HTC_Flyer_P512_NA using XDA App
No you can't have it that way. Google obviously thought the new way was an improvement or more gee-whiz. One thing for sure in tech, things will always change.
well, on the ipad, or any ios device, when apps are minimize, they "freeze" or hibernate, using minimal resources. (correct me if i'm wrong)
android is good at multi tasking, but i hope there's more control over this.
running in the background is not always a good thing.
example, while browsing, the page is loading a youtube video, i minimize and go have use another app, the browser video will continue to load while i'm in the other app. even if i lock my device, the browser video continue to load.
thats good if i want to multi task.
but sometimes, if i'm playing a game, i just want "freeze" it and continue later, maybe few hours later. so i minimize it and lock screen. but this may cause the device to not enter "sleep mode" and draining power as if it was running.
not all apps behave this way, i'm confuse as well. this is not a tab specific problem, my sgs2 as well, maybe all android device too.
my friend can calmly press the home button and lock screen on her ipad and never worry about power.
but i have to worry constantly whether or not the minimized app is draining power.
is there a way to know the minimized app is still running at back ground or able to "freeze"?
or better yet, is there a way to choose how we want it?, free or running at background after minimize.
PS: please dont recomend me to buy the ipad, i'm more of a android person.
Ray1 said:
well, on the ipad, or any ios device, when apps are minimize, they "freeze" or hibernate, using minimal resources. (correct me if i'm wrong)
android is good at multi tasking, but i hope there's more control over this.
running in the background is not always a good thing.
example, while browsing, the page is loading a youtube video, i minimize and go have use another app, the browser video will continue to load while i'm in the other app. even if i lock my device, the browser video continue to load.
thats good if i want to multi task.
but sometimes, if i'm playing a game, i just want "freeze" it and continue later, maybe few hours later. so i minimize it and lock screen. but this may cause the device to not enter "sleep mode" and draining power as if it was running.
not all apps behave this way, i'm confuse as well. this is not a tab specific problem, my sgs2 as well, maybe all android device too.
my friend can calmly press the home button and lock screen on her ipad and never worry about power.
but i have to worry constantly whether or not the minimized app is draining power.
is there a way to know the minimized app is still running at back ground or able to "freeze"?
or better yet, is there a way to choose how we want it?, free or running at background after minimize.
PS: please dont recomend me to buy the ipad, i'm more of a android person.
Click to expand...
Click to collapse
Run an app called os monitor or watch dog and you can see what app is using up resources.
Sent from my GT-P7510 using Tapatalk
If an App is running in the background (not to be mistaken with Services or System Apps like the browser) you usually should have a notification in the system bar;
If it doesnt show, then the app is hibernating.
For the majority of apps it's just to switch the home button and don't worry, this is how it should be. However, a few games that I've tried are still using CPU resources if I don't select quit from within the game. You can use the in built Task manager to check this.
I don't worry for anything but games - and I just check the behavior once after install.
When you have a program open, example is a video player. When I hit the home button does that program really fully close? Why I ask this is because I'll open up a web browser and input a web page. Before the web page even fully loads I'll hit the home button. Then even after a few minutes I'll load up that same browser and that page that didn't fully load will be there loaded up. I just want to make sure that when I close a program, it really is closed. That's all.
Hitting home does not "Close" or quit the program it rather puts it in the back round to fully quit it you must hit the recent apps button (Third on the left) and swipe the app away or get a task manager for those pesky back round apps.
Tech Faded said:
Hitting home does not "Close" or quit the program it rather puts it in the back round to fully quit it you must hit the recent apps button (Third on the left) and swipe the app away or get a task manager for those pesky back round apps.
Click to expand...
Click to collapse
Actually swiping apps away from recent list doesn't really close the apps. It just removes them off the recent list. Only a task manager can do that or going into settings, then apps, then force stopping it. But really,Android manages the memory very well itself. Alot of times, the way Android works, manually stopping a program will be more harm than good. Most of the time Android will just pull it back up itself therefore causing more CPU usage for that task tl bring it back. ANDROID keeps some apps semi-loaded. Ones it feels with load faster once you launch it since its already partially loaded. ANDROID is not like a PC where the processes in background will automatically slowbthings down or drain battery faster. Only certain apps that truly run in background can have that effect if too many loaded up. Whatever you do, don't use any auto memory killers or auto task managers or battery saver apps like juice defender, etc... those do more harm than good.
Unless your tablet is running with alot of lag, just try to ignore or resist the urge to keep constantly killing apps or whatever. You will see Android itself does a great job at managing it and will free up memory when actually needed. I'm still trying to do the same also resisting the urge. I just use Asus built in Task manger widget to see what's running in the background. If something clearly not needed then ill kill it. Beware though not to kill system apps or you might cause them to crash or be unstable.
A good app I came across is called BetterBatteryStats. Made by an xda member. Just type name of app in search box here in forum. That app will let you see what's truly running in the background and using up most battery or CPU processes. Has some great tips in there also in help section. IT LET me see how the Google currents app, although I wasn't using it, kept running in the background and using up processes and adding to battery drain. I would always see it pop up in my task manager although I never opened it and I have the refresh data set to long intervals. So it's basically a rouge app..lol. I uninstalled that mofo. Its a great app but runs to much in background regardless of data refresh settings and sometimes doesn't allow prime to stay in deep sleep when screen is off. Partial wakelocks, kernel wakelocks, etc...are all things you have to look over when determining what apps are causing most battery drainage or not allowing prime tl stay in deep sleep. Because they will partial wakelock n get data or whatever. It gets technical..lol learned alot from that one app. Free here in xda forums .
demandarin said:
Actually swiping apps away from recent list doesn't really close the apps. It just removes them off the recent list. Only a task manager can do that or going into settings, then apps, then force stopping it. But really,Android manages the memory very well itself. Alot of times, the way Android works, manually stopping a program will be more harm than good. Most of the time Android will just pull it back up itself therefore causing more CPU usage for that task tl bring it back. ANDROID keeps some apps semi-loaded. Ones it feels with load faster once you launch it since its already partially loaded. ANDROID is not like a PC where the processes in background will automatically slowbthings down or drain battery faster. Only certain apps that truly run in background can have that effect if too many loaded up. Whatever you do, don't use any auto memory killers or auto task managers or battery saver apps like juice defender, etc... those do more harm than good.
Unless your tablet is running with alot of lag, just try to ignore or resist the urge to keep constantly killing apps or whatever. You will see Android itself does a great job at managing it and will free up memory when actually needed. I'm still trying to do the same also resisting the urge. I just use Asus built in Task manger widget to see what's running in the background. If something clearly not needed then ill kill it. Beware though not to kill system apps or you might cause them to crash or be unstable.
A good app I came across is called BetterBatteryStats. Made by an xda member. Just type name of app in search box here in forum. That app will let you see what's truly running in the background and using up most battery or CPU processes. Has some great tips in there also in help section. IT LET me see how the Google currents app, although I wasn't using it, kept running in the background and using up processes and adding to battery drain. I would always see it pop up in my task manager although I never opened it and I have the refresh data set to long intervals. So it's basically a rouge app..lol. I uninstalled that mofo. Its a great app but runs to much in background regardless of data refresh settings and sometimes doesn't allow prime to stay in deep sleep when screen is off. Partial wakelocks, kernel wakelocks, etc...are all things you have to look over when determining what apps are causing most battery drainage or not allowing prime tl stay in deep sleep. Because they will partial wakelock n get data or whatever. It gets technical..lol learned alot from that one app. Free here in xda forums .
Click to expand...
Click to collapse
I was under the assumption that ICS fixed that? I suppose I was mistaken I apologize for my misunderstanding.
Demandarin, what makes you think swiping doesn't close a program? It does and its very obvious it works, just swipe then open the same program and you will see it starts over and will not be where you left off.
Try Settings > Developer Options > Don't Keep Activities. Sounds like it will fully close tasks once they are closed.
atgmartin said:
Try Settings > Developer Options > Don't Keep Activities. Sounds like it will fully close tasks once they are closed.
Click to expand...
Click to collapse
This is a very bad setting to enable if you ever have to switch back and forth between two different activities (for example email & web browsing). In general you should just leave the developer options alone.
As for closing apps.. why does it matter?
Apps that are not actively running don't use CPU and therefore don't use battery. Some apps sync information in the background, such as weather apps and email and while they do this battery is being used, however you can optimize the frequency of the updating to preserve as much battery life as possible.
In general unless you have experiencing performance issues, let Android manage itself.
If you absolutely need to turn off running apps, use the Asus Task Manager widget that comes pre-loaded on your tablet. You can use the Asus Task Manager to kill individual apps or all apps with a single click.
ON ICS, the swipe does stop the task running in the background, but I've seen where it the app may begin again, but as a background activity as almightywhacko describes.
People don't understand. Apps DON'T "run" in the background. They only run when you interact with them.
Buff McBigstuff said:
People don't understand. Apps DON'T "run" in the background. They only run when you interact with them.
Click to expand...
Click to collapse
Well, it depends. Apps don't run in the background like they do in windows, but some apps do continue to run processes in the background like data syncing and what not. However, it the app doesn't do this stuff then it only holds its state.
Also, I have not seen swiping recent apps closing apps. I think it is just happenstance if an app is closed by swiping it off the recent apps. Looking at the logging and monitoring the app state I have seen no correlation between running/not running apps and the recent app list.
However, as other people said, manually closing apps in Android will most likely reduce your performance rather than do anything beneficial.
I always get mad at those stupid apps that pretend to be providing a service. They won't go away. even if kill them they just come back(like Kenny). The app that likes to bother me the most is Zen pinball. I really like the game but it is always popping up prompting me to enable openfeint which I had already signed up for. I press enable but it still does not go away.
UmbraeSoulsbane said:
Well, it depends. Apps don't run in the background like they do in windows, but some apps do continue to run processes in the background like data syncing and what not. However, it the app doesn't do this stuff then it only holds its state.
Also, I have not seen swiping recent apps closing apps. I think it is just happenstance if an app is closed by swiping it off the recent apps. Looking at the logging and monitoring the app state I have seen no correlation between running/not running apps and the recent app list.
However, as other people said, manually closing apps in Android will most likely reduce your performance rather than do anything beneficial.
Click to expand...
Click to collapse
Only if they spawn a service. As far as activities, which most people would consider to be the "app" part, those do not run in the background. It just sits until it gets killed or used.
I just discovered that you can get rid of apps from the recent apps menu (the square button next to the home button) by swiping them to the side. I don't know why this makes me so retardedly happy, but I am sure that SOMEONE else out there will also appreciate this tidbit of information.
Anyone else have any nuggets of joy to share?
I liked that trick also when I first found out. Another thing too is that you can hold down the app in recent menu and a quicksetting will come up to let you remove it from list or look at app info.
Remember though, this only removes it from recent apps list. It doesn't close down the app itself.
Does it really matter though performance wise? I Always thought Android puts background apps into an "idle" state where they dont take up any resources until used? Although it is cool for people with OCD like me
demandarin said:
I liked that trick also when I first found out. Another thing too is that you can hold down the app in recent menu and a quicksetting will come up to let you remove it from list or look at app info.
Remember though, this only removes it from recent apps list. It doesn't close down the app itself.
Click to expand...
Click to collapse
Yes it does close the app. It just doesn't close background processes of the app.
Swiping an app from recent apps menu removes the app from cached memory, but keeps the background sync's (if it has any) still running. So you can kill off Facebook, but it's background sync (that would be started during system boot up anyway) remains.
You can test it, if you swipe browser from recent app's memory, it has to reload the page it was on. Same with Facebook app. But Facebook app's background process keeps running until you 'force stop' it.
Android application architecture runs in two layers, foreground and background processes. UI and the things you can use are written to memory when focus is lost from those apps, clearing them from recent apps also clears the memory those apps take at the time.
Is it useful? Yeah, for some things. But it won't improve your performance in any real noticeable way. Best you can do is swipe away apps that you don't need, keeping only apps that you want to keep in memory should you re-open them again. But that's usually too much micro-management to be worth it.
kristovaher said:
Yes it does close the app. It just doesn't close background processes of the app.
Click to expand...
Click to collapse
Perhaps, BUT, not every app in the recent apps list is actually running. That's why many times (most of the time?) the screenshot isn't what you actually see when you select an app from the list--you're really restarting it.
I think it's safest and easiest to just assume that you're really only removing apps from the recent apps list, not actually managing what's running in any way.
DroidHam said:
Does it really matter though performance wise? I Always thought Android puts background apps into an "idle" state where they dont take up any resources until used? Although it is cool for people with OCD like me
Click to expand...
Click to collapse
Yeah it doesn't make any difference performance wise, but it makes the menu much more useable for me =D
Thanks for this message, this is my first android device and I've been trying to figure out how to "close" applications. Did a search in here (I think), prime manual search and googled it. I am slightly OCD and like to "close" thinks that I'm not using. Harkens back to my early Windows days when you closed apps to conserve memory.
In the manual it says to close application by clicking on an X in the recent apps menu. Though unless it is super tiny, there isn't one.
redandblack1287 said:
I just discovered that you can get rid of apps from the recent apps menu (the square button next to the home button) by swiping them to the side. I don't know why this makes me so retardedly happy, but I am sure that SOMEONE else out there will also appreciate this tidbit of information.
Anyone else have any nuggets of joy to share?
Click to expand...
Click to collapse
if you have the dock, 2 finger gestures on the touchpad act as screen swipes. i.e. swipe two fingers across the tab, the tab changes screens. Also, if you want to actually kill the apps, add teh asus task manager widget to a screen. works great!
elybug said:
In the manual it says to close application by clicking on an X in the recent apps menu. Though unless it is super tiny, there isn't one.
Click to expand...
Click to collapse
That was an ASUS Honeycomb customization. It went away in ICS...
redandblack1287 said:
I just discovered that you can get rid of apps from the recent apps menu (the square button next to the home button) by swiping them to the side. I don't know why this makes me so retardedly happy, but I am sure that SOMEONE else out there will also appreciate this tidbit of information.
Anyone else have any nuggets of joy to share?
Click to expand...
Click to collapse
if you have the dock, 2 finger gestures on the touchpad act as screen swipes. i.e. swipe two fingers across the tab, the tab changes screens. Also, if you want to actually kill the apps, add the asus task manager widget to a screen. works great!
kristovaher said:
Yes it does close the app. It just doesn't close background processes of the app.
Swiping an app from recent apps menu removes the app from cached memory, but keeps the background sync's (if it has any) still running. So you can kill off Facebook, but it's background sync (that would be started during system boot up anyway) remains.
You can test it, if you swipe browser from recent app's memory, it has to reload the page it was on. Same with Facebook app. But Facebook app's background process keeps running until you 'force stop' it.
Android application architecture runs in two layers, foreground and background processes. UI and the things you can use are written to memory when focus is lost from those apps, clearing them from recent apps also clears the memory those apps take at the time.
Is it useful? Yeah, for some things. But it won't improve your performance in any real noticeable way. Best you can do is swipe away apps that you don't need, keeping only apps that you want to keep in memory should you re-open them again. But that's usually too much micro-management to be worth it.
Click to expand...
Click to collapse
that's what I meant. I should of been more clear then. just swiping it doesn't close down app "Completely", meaning no background process either. you have to use a task manager or Force stop in order to "Truly" close n stop an app from running.
elybug said:
In the manual it says to close application by clicking on an X in the recent apps menu. Though unless it is super tiny, there isn't one.
Click to expand...
Click to collapse
There isn't any in ICS, only in HC.
i didn't know that either until last week! ice cream is awesome :]
Conduitz said:
if you have the dock, 2 finger gestures on the touchpad act as screen swipes. i.e. swipe two fingers across the tab, the tab changes screens. Also, if you want to actually kill the apps, add teh asus task manager widget to a screen. works great!
Click to expand...
Click to collapse
You know.....that Asus task manager widget does not work on mine. It doesn't matter if I press x next to one app or select kill all - nothing happpens. I think mine is broken
I removed it from one of my home screens, no need to have it if it doesn't work
demandarin said:
that's what I meant. I should of been more clear then. just swiping it doesn't close down app "Completely", meaning no background process either. you have to use a task manager or Force stop in order to "Truly" close n stop an app from running.
Click to expand...
Click to collapse
It's a bit different though, because those background processes will (likely) already be running even if you don't start the app. Most of those background processes are started by boot activity in Android and others are started by scheduling activities (such as alarms or certain notifications and sync). These will be usually restarted once app is started again too (after Force Close) and if they are not already running (and they usually are).
Force Close is unnecessary unless you know that a certain app is bad for the system and was run accidentally, etc.