Proper way to close an application? - Nexus 4 Q&A, Help & Troubleshooting

Is it the back button all the way out of the application or pressing the Home button? I can't seem to find a concrete answer!

ojai00 said:
Is it the back button all the way out of the application or pressing the Home button?
Click to expand...
Click to collapse
Those do the same thing, which is either leave the app running or leave it in a nearly running state. To actually close an app, you press the multitasking button (the button to the right of home) and swipe the app off the screen.
BUT, you generally don't need to do that in Android -- The OS manages most well behaving apps fine.

jaybeeunix said:
Those do the same thing, which is either leave the app running or leave it in a nearly running state. To actually close an app, you press the multitasking button (the button to the right of home) and swipe the app off the screen.
BUT, you generally don't need to do that in Android -- The OS manages most well behaving apps fine.
Click to expand...
Click to collapse
Swiping an app out of recents does the same thing as pressing the back button actually. To answer the first question, the back button exits an app properly, the home button just suspends the app

jaybeeunix said:
Those do the same thing, which is either leave the app running or leave it in a nearly running state. To actually close an app, you press the multitasking button (the button to the right of home) and swipe the app off the screen.
BUT, you generally don't need to do that in Android -- The OS manages most well behaving apps fine.
Click to expand...
Click to collapse
The back button actually does a better job closing the app, and usually the app has a close button when after jamming the back button. This is how you close (not force close/stop) the app.
If you are using an app and tap the home button, do other stuff and go back, you will be exactly where you were before. This is how you multitask (with the home button).
The multitask menu is like the one on iOS 4 and above. It is a menu of RECENTLY USED APPLICATIONS and is there just for quick switching. Swiping will not close the app, it will delete it off your "history."
Sent from my DROID2 using xda premium

jacklebott said:
Swiping an app out of recents does the same thing as pressing the back button actually. To answer the first question, the back button exits an app properly, the home button just suspends the app
Click to expand...
Click to collapse
http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle
Swiping gets you to the "activity shut down" phase (onStop and onDestroy are called, assuming your app is nice, it'll shut down).
Home-ing gets you to the onPause phase (from the things I tested, they usually then go to onStop (cached phase)).
Backing out gets you to the onStop (cached) phase.
(You can verify this by looking at Settings>Apps>Running. When I back or home out of an app, the app is shown with the same state (cached). When I swipe an app away, it's gone from both of those task lists.)

jaybeeunix said:
http://developer.android.com/reference/android/app/Activity.html#ActivityLifecycle
Home-ing gets you to the onPause phase (from the things I tested, they usually then go to onStop (cached phase)).
Backing out gets you to the onStop (cached) phase.
Click to expand...
Click to collapse
Although that is native Android behavior, developers almost always make it so the app will nicely shut itself off when pushing the back button.
For example, when I open Root Explorer, it starts of with a black screen, and only after Root Access is granted my files show up. If I tap back and open it again, bam! Same process.
If I tap home after opening and open it again, bam! Takes me right to the / file directory, no inital "startup" of app
Sent from my DROID2 using xda premium

Why can't developers just put an exit button in the app menu?

donec said:
Why can't developers just put an exit button in the app menu?
Click to expand...
Click to collapse
They can, some do, some don't *shrugs*
Sent from my DROID2 using xda premium

donec said:
Why can't developers just put an exit button in the app menu?
Click to expand...
Click to collapse
Generally speaking, there isn't a need for it -- The OS closes and restarts apps as needed to manage resources optimally. Additionally, as gagdude said, most apps save and restore their state beyond the OS cached state, so it isn't always obvious that an app was ever "gone".

Related

AnyUnlock: An app to treat N1's power button problem (no root required)

Before developoing this app, I am using
1. Nolock
2. Flyscreen
3. lock widget
in order to
1. use any key to turn the phone on
2. use widget to turn off the phone
3. Use flyscreen to prevent the accident tap
However this combination is huge and invenient. So I deciced to develop a very small app (40k in size) it can
1. Use any key to turn on the phone
2. A widget turn phone off
3. A very simple lock screen to prevent accident tap.
Search AnyUnlock in Android Market and enjoy it. If there are any porblems, please report.
i like it!
perhaps you should include an option to enable or disable the 'lock screen to prevent the accidental tap.'
deenn said:
i like it!
perhaps you should include an option to enable or disable the 'lock screen to prevent the accidental tap.'
Click to expand...
Click to collapse
Yes, I will do that in next version.
It didn't work for my N1. I enabled the app, brought me to the 2nd window where I also enabled it and let the phone shut down and nothing, I had to use the power button to turn the screen back on. Back to nolock.
It was the way I installed it, working now but after installing gingerbread the trackball wake no longer wakes the screen, have to use the volume key. Still very effective but like the trackball wake.
vinnyjr said:
It didn't work for my N1. I enabled the app, brought me to the 2nd window where I also enabled it and let the phone shut down and nothing, I had to use the power button to turn the screen back on. Back to nolock.
Click to expand...
Click to collapse
Yes, there is a bug. If you don't allow the admin permission in the first time. The program will fail. You can disable it, uninstall it and reinstall to take effect.
I also couldn't pick up on an incoming call... it just went to the screen which shows the enable/disable anylock buttons. I couldn't press home or back. Uninstalled it for now.
Sent from my Nexus One using XDA App
deenn said:
I also couldn't pick up on an incoming call... it just went to the screen which shows the enable/disable anylock buttons. I couldn't press home or back. Uninstalled it for now.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have updated to 1.2 with the option to disable simple lock screen. Also I tried to fix your phone call issue. Hopefully it is working.
OK 1.3 released with fixes to some non-n1 devices.
Works fantastic. After enabling the app I went back into settings and unchecked the lock screen. Now it works just the way I wanted. Thanks for the great app.
Vinny
Interesting app since my power button is acting up, Thanks.
cesar67 said:
Interesting app since my power button is acting up, Thanks.
Click to expand...
Click to collapse
You can have a try. The power button is quite vunerable for HTC devices. I hope Android would make an official option to power on the device using any keys.
works brilliantly now! thanks.
maybe you should put in the description in the market that no root is required.
and an option to still use the slider when unlocking? that would be my favorite option.
just pressing the track ball brings you to the unlocking screen with the slider.
This is super awesome, thanks for making this!
Curious, what specific activity does the widget call? I would like to be able to shut the screen off using other things (dock swipe up, tasker, custom widget) etc. is it an android acitivity or one that is specific to AnyUnlock?
I tried each of the 4 or 5 activities in AnyUnlock but they didn't work.
Thanks for making this!
Sent from my Nexus One using XDA App
Just updated to Gingerbread on N1 and the trackball doesn't wake anymore, but volume button still works.
I can also confirm the trackball doesn't work to wake the screen up, but the volume buttons still do.
Hopefully the trackball wake issue will be resolved for gingerbread.
Sent from my Nexus One using XDA App
colins said:
Just updated to Gingerbread on N1 and the trackball doesn't wake anymore, but volume button still works.
Click to expand...
Click to collapse
Yup, I noticed this also with other apps that disable the lockscreen (like Switchpro)
That's too bad.
No Lock too from what another user has stated. There's no way i'm changing from CM7 if there's no possibility of trackball wake!
Does this app just Wake the N1 or does it power ON a device which is powered off ?
I can already wake via the trackball using CM6 , but I need something which will Power it ON as my power button is broken.
OJ in Compton said:
I can also confirm the trackball doesn't work to wake the screen up, but the volume buttons still do.
Click to expand...
Click to collapse
I can also confirm trackball doesn't wake screen but the volume key will. Hopefully the dev. can fix this issue.
Thanks for a great app.
PS Will donate when trackball is fixed.

How to: remove Voice Command without root or any tech know-how

Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Or just don't double tap the Home button
In a year of owning a Galaxy SII I can't say I've every double tapped the Home button by mistake
PFC Hudson said:
Or just don't double tap the Home button
In a year of owning a Galaxy SII I can't say I've every double tapped the Home button by mistake
Click to expand...
Click to collapse
It's weird, but lately, occasionally when I hit the home button the app would just launch. It's like the device was registering a double-tap. Not sure if it was me, or a hardware issue. Either way, it was annoying and I've seen a few others complain about the same issue.
If you're not affected, then you're set. But if you are, this seems to work wonders.
PFC Hudson said:
Or just don't double tap the Home button
In a year of owning a Galaxy SII I can't say I've every double tapped the Home button by mistake
Click to expand...
Click to collapse
I agree, I never experienced the issue and laugh when I see people complain.
I know multiple people with the S2 and none of them experience.
I admit, maybe it may be hardware; but I would think if it was hardware it would be on a larger scale. I personally think people don't realise they double tapped it.
T__ said:
laugh when I see people complain.
Click to expand...
Click to collapse
And I laugh when I see someone who assumes that because their phone works perfectly, everyone else must have a perfect phone too.
Does this remove the double tap delay though? Always drove me mad about gs2, and I've always got rid of it as soon as I can
Sent from my GT-I9100 using xda premium
jaykresge said:
Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Click to expand...
Click to collapse
I agree....it is annoying. It comes up all the time when I don't want to. Anyone know the name that is appears in Titanium Backup so I can remove it?
Voice command. Just filter for "vlingo"
i have a hardware problem, when i press home button, like 30% of time the voice command will appear, but i dont want to uninstall the app, there is any other way for disabling it?
jaykresge said:
Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Click to expand...
Click to collapse
Boys install system app remover, no need for root, and uninst apps u don't need. Quicker, safer, legal ,
i had the same issue (about 30% of erroneous voice command starts). i had frozen
the app with Titanium Backup and since then had about 30% of keypress failures.
Is there a program that shows if there was a keypress or not?
Thanks for a nice tip, that voice is useless in Russia anyway.
BTW, I also can unistall readers hub in that way, why it allows me to unistall it, but I cant unistall music hub, they're seems to be both system apps.
ES File Explorer can also uninstall it.
Select the App Manager then long press on the app you want to remove, eg Voice Commamd, choose uninstall, and its gone.
Help
I've tried go launcher and it doesnt have a red x by it when i press and hold.... i tried apex launcher and the same thing. Anyone else have this problem.... please help. i'm using the SGH-i777 with stock ICS
is this the solution
utahst8 said:
I've tried go launcher and it doesnt have a red x by it when i press and hold.... i tried apex launcher and the same thing. Anyone else have this problem.... please help. i'm using the SGH-i777 with stock ICS
Click to expand...
Click to collapse
I don't have the problem because I fixed it.
Search for root app uninstaller, install it, and find voice talk, or viingo as it is called, and uninstall the app, so uninstall root app installer so you can't launch it by a mistake and double tap and see what's happening, now nothing happens when I double tap home button, so it's fixed.
I hope I can help other people.
Its the most frustrating app ever even more frustrating than Touchwiz. Its like whenever I press the home button around 80% of chances are that it would pop up with that annoying voice,"What would you like to do ?"
And I'm like GTFO off my device. Finally removed it using Root Explorer forever after...
Sent From My Pencil
Finally, after 2 years ...
jaykresge said:
Can't stand that annoying Voice Command app that pops up whenever you accidently double-tap the home button? Well, apparently it can be removed if you have ICS, though not the typical way.
Thanks goes out to Marrr over at AF for pointing this out.
Step 1: Install Go Launcher
Step 2: Long-press voice command in the app drawer, and when the red "x" comes up, hit it. Follow the prompt and the app will be completely uninstalled.
Step 3: Uninstall Go Launcher if you want (and delete the Go Launcher/Store folders it created in your USB storage).
It really is THAT simple!
Click to expand...
Click to collapse
Thank you very much. Just to say so I went through that buttcracking process of making like my millionth forum account, but that one was worth it. Thx a bunch, I really have a device where pressing home leads you to the voice crap in 99,456%. Now its finally fallen off board. Thx again.
removing voice command easier
you don't have to change a theme or anything like that. you should download "Smart App Protector Free" and and in the apps section inside the app scroll down until you get to "voice command". click on it and choose uninstall. that easy
You can also use system app uninstaller from the market, just go into regular apps and remove voice command.
tiggerlator said:
You can also use system app uninstaller from the market, just go into regular apps and remove voice command.
Click to expand...
Click to collapse
This is an outdated thread. You can now disable the app.

How do you kill a running app

On my Samsung Gingerbread /Touchwiz Galaxy Phone long touch of the home button brings up recent applications with a task killer button that lists running apps with an exit button each.
The recent apps button on the Nexus doesn't seem to lead to a kill option.
I guess I could go to settings/apps/running and select an app and pick the stop from its page, but thats a lot more complicated.
Is there an easier way?
Press the right button (looks like two windows) then swipe to kill
Sent from my Nexus 7 using xda premium
rowanparker said:
Press the right button (looks like two windows) then swipe to kill
Click to expand...
Click to collapse
Thanks, I had the right button, but I was trying to kill with a long press instead of a swipe. I thought kill/delete with Swipes was an Apple thing, while Android used long press.
Maybe Apple will sue
Nah, in the iPod touch and iPad it's long press which brings up close buttons
According to the manual the only way to kill a task is in the settings / apps section. "Force Stop"
Swiping away the "recent apps" simply removes it from "recent apps"
Jellybean manages apps / memory automatically. You should never be short on memory.
Hemidroids said:
According to the manual the only way to kill a task is in the settings / apps section. "Force Stop"
Swiping away the "recent apps" simply removes it from "recent apps"
Jellybean manages apps / memory automatically. You should never be short on memory.
Click to expand...
Click to collapse
Yea, that isn't killing an app.
You don't need to kill apps as a matter of routine although people always seem to think so. Sometimes it is necessary if the app is behaving badly and there a lots of task-killers available that will do that.
I like "system panel" as it has other uses too.
The "recent apps" button is supposed to be there for your convenience so you can easily go from one app to another, if you are swiping them away you are just nullifying the point of the button.
Actually swiping away from the recent apps does indeed kill the app. You can verify the behavior on apps by swiping them away and opening them again. They will load from the beginning instead of where you left off.
Sent from my Nexus 7 using xda app-developers app
ok thanks, didn't know that. I think some of the other stuff I said is still kinda valid tho. There is no real need to kill apps.
Sent from my LG-P990 using Tapatalk
kangxi said:
Actually swiping away from the recent apps does indeed kill the app. You can verify the behavior on apps by swiping them away and opening them again. They will load from the beginning instead of where you left off.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would hardly call that proof. It could simply be a signal to refresh instead of "pick up where you left off". After all, if you swipe it away you dont really have an urgent need to go right "back where you left off".
Hemidroids said:
I would hardly call that proof. It could simply be a signal to refresh instead of "pick up where you left off". After all, if you swipe it away you dont really have an urgent need to go right "back where you left off".
Click to expand...
Click to collapse
The proof is already out there. I just simplified it. There was a huge debate about it when the Gnex came out and I believe a Googler posted about it on Google+ as well.
Sent from my Nexus 7 using xda app-developers app
Don't most people put a task manager widget (Application Manager) on their home screens anyway for this so you can quit all active apps and clear your RAM? It was a standard app on my Samsung Captivate Glide, and I keep it next to my battery widget so maybe between the two I can make the battery last more than 8 hours.
-Ara
is there a way to delete all the runnings apps at once? It's tiring to swipe them out one by one..
sometimes after a long use you have more than 10 apps running, it would be easier if i can simply swipe them all out with one button
thunder9111 said:
is there a way to delete all the runnings apps at once? It's tiring to swipe them out one by one..
sometimes after a long use you have more than 10 apps running, it would be easier if i can simply swipe them all out with one button
Click to expand...
Click to collapse
Again, that's why I like my App Manager widget, you have the option to kill everything in one click (at least until I get the ics update, then it's two clicks for that damn confirmation screen).
-Ara
I've always heard it likened to the backing out of an app with the back button. If I go into G+, go into a room in messenger and skip to home, I can resume the app right where I left off (provided it's soon, hasn't been killed). But if I exit home, swipe the app out, it acts as if I've closed it but it's kept in memory. If I do the same but long press the app in the recent apps list, go to app info and kill the app, then it is forced out of memory. It's essentially killing the app. A good example is a music app; the app continues to play when you've backed out of the app via the back button, even when you swipe the app away as it is still in use. Force stopping the app has a definite result.
Guess it is time for the obligatory "why you shouldn't don't need to use a task killer" with Android. This is an old article, but this was true then and is even more so now. Killing all apps isn't necessary and can have negative effects.
-edit-
Probably should have linked the mentioned article;
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
AraDreamer said:
Again, that's why I like my App Manager widget, you have the option to kill everything in one click (at least until I get the ics update, then it's two clicks for that damn confirmation screen).
-Ara
Click to expand...
Click to collapse
There's no need for task killers. This has been confirmed over and over, even by Google. That's why they made them stop working in Froyo I believe'
Sent from my Nexus 7 using xda app-developers app
Hemidroids said:
According to the manual the only way to kill a task is in the settings / apps section. "Force Stop"
Swiping away the "recent apps" simply removes it from "recent apps"
Jellybean manages apps / memory automatically. You should never be short on memory.
Click to expand...
Click to collapse
Well, actually i use Cool Tool to monitor my available ram, and when I swipe away apps from the recent apps view, i free up lots of ram.
AraDreamer said:
Again, that's why I like my App Manager widget, you have the option to kill everything in one click (at least until I get the ics update, then it's two clicks for that damn confirmation screen).
-Ara
Click to expand...
Click to collapse
It works, but it ruins the the running tasks page. After you killed everything, bring up the running apps, and they are all still there. It doesn't get rid of the apps there, so that's still annoying

[Q] delete/before key

In the LG-E960 service manual there is a question about battery consumption is too fast and one of the answers is.
After turning on the application and turning it off using the home key, invisible applications are still being used on the background, so battery consumption becomes faster. It is recommended that delete/before key is always used to end applications or programs.
Does anyone know what is meant by "delete/before key"?
The back button.
Sent from my Nexus 4 using xda app-developers app
I think the service manual is wrong. Back key doesn't close apps (at least, most of them). You need to use app key and swipe it from there to really close it.
VivaErBetis said:
I think the service manual is wrong. Back key doesn't close apps (at least, most of them). You need to use app key and swipe it from there to really close it.
Click to expand...
Click to collapse
Actually that doesn't do anything on stock android, cyanogen and other custom ROMs have it though
Sent from my Nexus 4 using Tapatalk 2
sy224048 said:
Actually that doesn't do anything on stock android, cyanogen and other custom ROMs have it though
Click to expand...
Click to collapse
It works on stock. I just tested swiping tapatalk and it dissapers from background cached processes.
VivaErBetis said:
I think the service manual is wrong. Back key doesn't close apps (at least, most of them). You need to use app key and swipe it from there to really close it.
Click to expand...
Click to collapse
It depends on how the developer coded the app to handle the function. It doesn't close everything.
AFAIK apps are closed, services don't.
They probably mean the " long press back button to kill apps" function.
Check the developer options. It should be the last option.
Nuu~ said:
They probably mean the " long press back button to kill apps" function.
Check the developer options. It should be the last option.
Click to expand...
Click to collapse
That is not a option on stock android

Navigation Buttons Mod?

Call me a bit old fashioned, but I have a specific set of "keybinds" that I always work to achieve one way or another on my android devices.
The "Menu" button of old is more important to me than a "Recents" button - really just hoping to achieve inverted behavior of the square button: short press for menu, long press for recents.
Long pressing the "Back" button should kill the foreground app.
Any other bind to quickly toggle the torch light.
Using the menus in OxygenOS, I can't seem to achieve this. Any suggestions or secrets I've yet to find out about?
In Oxygen os you can set LONG PRESS RECENT BUTTON to perform MENU Action. I use it all the time.
About long press back button to kill app, I think this feature was removed in PIE.
Me too was looking for it but didn't find a solution.
Anyway I quickly realized that I don't need it. Op6t can keep a lot of app in memory so there's no need to kill.
When i want to kill one or all i use Recents.
Not a big deal for me.
Yep that's how I'm using everything now. It gets the job done, though I find myself reverting to old habits absent-mindedly. I'm sure I'll be perfectly adapted in a matter of days.
bigcc32 said:
Call me a bit old fashioned, but I have a specific set of "keybinds" that I always work to achieve one way or another on my android devices.
The "Menu" button of old is more important to me than a "Recents" button - really just hoping to achieve inverted behavior of the square button: short press for menu, long press for recents.
Long pressing the "Back" button should kill the foreground app.
Any other bind to quickly toggle the torch light.
Using the menus in OxygenOS, I can't seem to achieve this. Any suggestions or secrets I've yet to find out about?
Click to expand...
Click to collapse
Try this app: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
dannejanne said:
Try this app: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Click to expand...
Click to collapse
Permissions granted using root. It won't get past the compatibility check (The screen says "If you don't see anything your device is incompatible," and I certainly dont see anything). Thanks for the suggestion, though.
bigcc32 said:
Permissions granted using root. It won't get past the compatibility check (The screen says "If you don't see anything your device is incompatible," and I certainly dont see anything). Thanks for the suggestion, though.
Click to expand...
Click to collapse
It can be granted access with ADB (PC). It should work I've had it work even on LG phones and such.
dannejanne said:
It can be granted access with ADB (PC). It should work I've had it work even on LG phones and such.
Click to expand...
Click to collapse
I don't think the permissions are the problem. The app doesn't complain about that, it just doesn't do anything to the nav bar during setup, and according to the app that's indicative of incompatibility.

Categories

Resources