[Q] Apps on their own screens - Vibrant Q&A, Help & Troubleshooting

would it be at all possible to make apps stay open on their own screens.. so maybe when i see the screen previews it would allow me to switch screens and apps... similar to webos?.. hmmm...

No, that's no possible because of the way Android handles switching applications. When you switch an application, it is paused and its state saved. This is done so if the system needs to free up memory, it can kill the process, and when you select the application again, it will resume from the saved state.
If I understand you correctly you are asking for something like workspaces or virtual desktops, which does not translate well into the mobile sphere. However, you can approximate what you want by using the "Recent Apps" functionality by long-pressing the home button to switch applications. But neither should be necessary, because a properly written application is supposed to note its state and resume where you left off when you select it again. If that is not happening, it is probably due to something in the way the application was coded.
Perhaps reading the documentation on Acitivitiesand Tasks will help you understand what is happening you run an application, and why sometimes the Back button does things you don't expect it to.

Related

How to END programs without an app...

I was wondering how to quit a program without using an app like taskiller. basically i'm using the Browser and pressed home screen to leave, but i want to quit the browser so it stops running...
Press the "Back" button. That is when you're inside an app and want to close it.
The behaviour of the "home" and "back" keys vary from application to application. Some quits, but the majority keeps running in the background. Some applications have an "exit" option from their menu, but that's just a few and most notably applications which normally are expected to do things in the background like maintaining connectivity to IM servers, checking for new mail etc. This is one of several inconsistencies which hopefully gets sorted in future android releases, accompanied by consistent recommendations in the dev-kit documentation.
From the Hero home screen, do this
Menu - settings - applications - manage applications - browser - force stop
Or you could stop treating your phone like a desktop computer and accept the fact that a) you can't run different apps in windows side-by-side and b) there is no point in closing windows. Android does the memory management for you.
Volker1 said:
Or you could stop treating your phone like a desktop computer and accept the fact that a) you can't run different apps in windows side-by-side and b) there is no point in closing windows. Android does the memory management for you.
Click to expand...
Click to collapse
I agree that android does the memory management very neatly, that's only when you are running very low on it... and what about the fact that the backgroung apps are draining the battery?? I think one really needs to get rid of unnecessary apps to improve battery life.
LooieENG said:
From the Hero home screen, do this
Menu - settings - applications - manage applications - browser - force stop
Click to expand...
Click to collapse
Hmm, yeah that's one way but it takes for ever!!
salmanbodla said:
I agree that android does the memory management very neatly, that's only when you are running very low on it... and what about the fact that the backgroung apps are draining the battery?? I think one really needs to get rid of unnecessary apps to improve battery life.
Click to expand...
Click to collapse
Background apps are SLEEPING, ie they ONLY take up memory, they hardly use any CPU time at all
Background apps can sleep and can also continue to work.
Just let the handset work its own management. Never had an issue with memory or slow downs but just leaving well alone.
If you want the browser to stop loading before you move to another app or go Home, just hit the stop loading icon in the address bar.

[Q] Question about keeping background apps off

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!

[Q] when minimize, app hibernating or running in background?

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.

My life is changed forever

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.

EASY way to instantly exit current app?

...and I don't mean 'minmize' like what pressing the home or back button does. (which merely puts it in the multitasker menu list, still open.)
I mean closing it like when you swipe it out of the menu list. (which are far as I can tell, seems to close it off enough to stop what it's doing and free up the memory it was using!)
Sometimes I want to just close an app since I know I won't be using it for a while and I want to conserve cpu/memory/battery - or merely manage the list of things in my multitask list. kinda like on Desktop. (you don't want every app on your pc open all at once, do you, do you?!) and I just want a simple way like on the desktop to close that app when I want to close it.
SO: Is there some app that can assign a custom screen gesture (like the lovely letter C for 'close') to perform 'fully exit current app' or some solution like that? I started to research, but couldn't seem to find one very quickly, so thought I'd ask here, at THE place to ask.
also I apologise for using things like Windows terms ('minimize'), i know that's not how it works in android. But you do know what I mean.
Thanks
This is a question that a lot of people ask when moving to Android and the answer simply is, forget about it.
Android handles processes and memory in a completely different way to Windows. When an app is "minimized" it obviously leaves a footprint in the memory, but it uses no CPU (unless it's a polling app or something that keeps alive for a specific purpose).
Just trust Android to handle memory management - it does a very good job of it.
If you really, really MUST do something about it then the best thing you can do is get something like Juice Defender (there's tons of similar apps) and make it kill apps periodically. Most apps that people use for this type of purpose are merely placebo, but if it makes you feel better then I guess it's serving a purpose.
Archer said:
This is a question that a lot of people ask when moving to Android and the answer simply is, forget about it.
Android handles processes and memory in a completely different way to Windows. When an app is "minimized" it obviously leaves a footprint in the memory, but it uses no CPU (unless it's a polling app or something that keeps alive for a specific purpose).
Just trust Android to handle memory management - it does a very good job of it.
If you really, really MUST do something about it then the best thing you can do is get something like Juice Defender (there's tons of similar apps) and make it kill apps periodically.
Click to expand...
Click to collapse
Thanks for your answer. I can sense you have wisdom and experience in your words there, but I want to probe a little further.
surely there can be an almost macro-like (again, windows terminology, sorry) functionality, that can be assigned to a gesture swipe that can emulate pressing home button, then swiping the bottom item away from the multitask menu? (which is always the one you just 'minimized')? Could an app like Tasker even do it?
i agree that good memory management is a beautiful thing, but there really should be manual control of closing apps, my reasons above are stated.
i wouldn't touch automatic time-based closing, i sometimes have saved states in apps and wouldn't want them closed when i don't want them closed.
Most apps that people use for this type of purpose are merely placebo, but if it makes you feel better then I guess it's serving a purpose.
Click to expand...
Click to collapse
you really think it's all placebo, and that say, running 50 apps in android with finite set amount of ram on the device is all fine simply due to memory management?
is me experiencing lag in some android apps (or battery draining faster than I'd like), then closing off several running apps in the multitask list, then noticing the problem go away, all placebo????? what about google maps, say?! I'd love a one-step swipe action to CLOSE google maps when I'm done with it, not having to press home button, then multitask button, then swipe away google maps. (I know when minimized it consumes nothing like it does when open, but I think still it consumes more than if it were fully closed...)
it's not just about memory. edit: and I already stated in addition, I often want to simply manage what I have open. this is a basic function in desktop OSes, I think it's time it came to mobile. if not officially, there surely must be some hack/tool to do it. :S
download a task killer app with a widget.
press home button and press the widget and you're done
If you're using AOKP based ROM then there is hold back to kill in Settings > ROM control > general UI
Sent from my GT-I9100 using 1st ROM
Hold homesçern key
Sent from my ST23i using xda app-developers app
jman2131 said:
download a task killer app with a widget.
press home button and press the widget and you're done
Click to expand...
Click to collapse
that's about 2/3 the way towards the current 3-step solution though :/.
Am I to be amazed that a function to put this simple task into a single gesture hasn't been done? or isn't possible? it HAS to be possible. Otherwise I'd be flabbergasted.
I have googled further and just can't seem to find something :|.
WAIT! I think I have! here. https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontroldemo&hl=en it has a "kill task" function that you can set up a custom gesture for. it's a start.
however I'm getting a "ERROR! No ROOT permissions?" error despite being rooted with supersu and successfully using other root apps etc, so I've emailed the dev and hope I can get it working :S.
But still, it seems a little clunky the offering of custom gesture types. I can't set a nice curvy gesture defined by tracing it on the screen. oh well - it's a start.....
jootanen said:
If you're using AOKP based ROM then there is hold back to kill in Settings > ROM control > general UI
Click to expand...
Click to collapse
That seems the holy grail! too bad I'm on stock jb with plans for upgrading to CM .....

Categories

Resources