Hey, I was wondering if it were at any way possible to add a quit or kill button to the menu popup that will end the currently loaded app? Maybe the devs can come up with a way to implement a global method that will work with any currently open app when you press the menu button?
I know they have the task killers and all that.. but I just thought it would be a neat modification while I was in browser and came across a situation where I had to restart the browser and couldn't figure out a way to kill it without having to download a task killer....I just seldom need to kill all apps is why I don't have advanced task killer installed anymore. ...
Each application's menu is within that application itself. It would have to be something in the pull-down menu, and that would only be visible if the application allows it.
A nice alternative might be to add a "kill top" to the long-press-home.
Although it really isn't too hard to go to home, open a terminal, and kill the problem application.
bobbybooshay said:
Hey, I was wondering if it were at any way possible to add a quit or kill button to the menu popup that will end the currently loaded app? Maybe the devs can come up with a way to implement a global method that will work with any currently open app when you press the menu button?
I know they have the task killers and all that.. but I just thought it would be a neat modification while I was in browser and came across a situation where I had to restart the browser and couldn't figure out a way to kill it without having to download a task killer....I just seldom need to kill all apps is why I don't have advanced task killer installed anymore. ...
Click to expand...
Click to collapse
Although closing apps is actually against the ethos of Android I tend to agree that, whilst we still attach ourselves to old paradigms, a close function would be nice. Perhaps a little x on the right hand side of the app's entry in the navigation list would be good. It could be implemented universally (using the same Android close app mechanisms as are used for low memory conditions) and would not require modifications to any apps.
In the meantime, you do realise you can close a single app from Settings | Applications | Manage Applications right?
bobbybooshay said:
...while I was in browser and came across a situation where I had to restart the browser...
Click to expand...
Click to collapse
Were you looking at porn?!
^haha you know it! Nah but actually I enabled that browser download any file type setting In astro which required a restart of the browser and I was feeling lazy when I thought it would be nice to have a close button.
And ya.I am aware of the manage applications deal in the built-in settings. But I was jus thinking it would be nice to be able to close it while I'm still I'm the actual app itself.
Nice to know it could be possible tho
Related
I wonder if there is a better way to close a browser instantly rather than to pressing Back button several times until back to the homepage?
Thanks,
Elgs
Get a task manager like Advanced Task Manager
elgs said:
I wonder if there is a better way to close a browser instantly rather than to pressing Back button several times until back to the homepage?
Thanks,
Elgs
Click to expand...
Click to collapse
If you're talking about getting back to the homepage, you can always do that through bookmarks, or by creating a new window and then closing out the old one.
If you're talking about closing the browser completely so that it's no longer running, pressing the home icon and moving on to another task normally closes it out. Since the Browser is the largest application on the G1, it's a system resource hog, and as soon as Android sees that something else wants a chunk of that resource, it makes room for it by closing the biggest app open :].
For an insta-kill (not to be confused with Halo 3 ), use a task manager like TasKiller.
OK, this may be kind of a dumb question but...Why isn't there a quick way to quit browser? Menu--->Quit like with Pandora would be a useful addition IMO. Right now, there is no reliable way to quickly quit the browser other than hitting back however many times is needed until the browser quits. Or, menu--->windows--->X on the open windows--->once a new window opens up the hit the back button again. Seriously, it doesn't make sense.
ummm try the home button.
Sleeepy2 said:
ummm try the home button.
Click to expand...
Click to collapse
I don't want it to continue running in the background though.
staunty said:
I don't want it to continue running in the background though.
Click to expand...
Click to collapse
Use advance task manager or some kind of task killer to kill it.
staunty said:
I don't want it to continue running in the background though.
Click to expand...
Click to collapse
Android will kill/clean it up when the ram is needed.
Why not just let android do what it does and kill it when it's necessary?
Sleeepy2 said:
Android will kill/clean it up when the ram is needed.
Why not just let android do what it does and kill it when it's necessary?
Click to expand...
Click to collapse
While correct I find android deals with backing out of an app and pressing home differently.
Home says try to keep the apps state.
Backing out says I no longer need this app.
Neither kill the process but the second will be chosen first if more memory is needed. So by using back in general I find it more likely when I need multiple apps in ram they will both/all stay there.
The browser of course overrides the default back function to a web browser's back button unless you are on the first page of a window/tab.. so it can be harder to tell the OS you are done with it.
However even so don't use a task killer on the browser I find it causes some things to become out of place and make the memory issue worse as the day goes on.
If fact just don't use a task killer!! If things are going slow and you have swap. . Reduce or remove swap. If you have comp cache above the cm default same applies.. if you are tired of waiting on the home screen to reload, try keep home in ram.
Dolphin browser has exit with or without clearing cache on long press of back.. hopefully it 'backs' and nothing fancy. (Well unless you asked it to clean the cache)
ezterry said:
While correct I find android deals with backing out of an app and pressing home differently.
Home says try to keep the apps state.
Backing out says I no longer need this app.
Neither kill the process but the second will be chosen first if more memory is needed. So by using back in general I find it more likely when I need multiple apps in ram they will both/all stay there.
The browser of course overrides the default back function to a web browser's back button unless you are on the first page of a window/tab.. so it can be harder to tell the OS you are done with it.
However even so don't use a task killer on the browser I find it causes some things to become out of place and make the memory issue worse as the day goes on.
If fact just don't use a task killer!! If things are going slow and you have swap. . Reduce or remove swap. If you have comp cache above the cm default same applies.. if you are tired of waiting on the home screen to reload, try keep home in ram.
Dolphin browser has exit with or without clearing cache on long press of back.. hopefully it 'backs' and nothing fancy. (Well unless you asked it to clean the cache)
Click to expand...
Click to collapse
What he said. I don't use a task killer anymore. I could get the quit function on dolphin browser but I don't understand why it isn't a standard function on the stock browsers.
Hello Chefs (and all you microwave re-heaters..you know who you are..)
I have a request for a feature either as a standalone app, or implemented into a rom. Maybe, it's not possible. I don't know.
What I would love to see is a simple task killer (no gui) mapped to the 'hangup' button on android phones. When I'm running an app and I want to close it, I hit the hang up button, and it kills the currently running app. This seems to me to be intuitive, would streamline task management/eliminate unneeded apps running in the bg, and make Android much more user friendly.
Order of Operations would work something like this.
User starts an App (Browser)
If the user hits the hangup button, Browser would be killed and the screen would return to the home page. A second click on the hangup button would turn off the screen and lock the phone.
If the user hits the home button, the app stays running in the background, and when the user clicks Browser again, the app returns in it's current state with the last loaded page available.
Like I said, it seems pretty simple and straightforward. I know it would require a rooted phone, but it seems like it would give maximum flexibility to the user and allow them to kill the apps that they want when they want to. But maybe it's not possible. So please, let me know. Thanks for the great work guys.
And what would you do if you had a call running in the background?
WHY do you want to kill the running application? It won't do anything once you switch off of it except consume memory, and if more memory is needed, the task killer will take care of that for you.
If you need this you either:
* fail to understand how the user interface works in android (including reclaiming of processes)
Or
* are running applications by developers who didn't design the application to work correctly on android.
The button you are looking for is the back button. It will background the app immediately and allow it to be overwritten as soon as anything needs memory.
I'm using MileStone, but when I run apps, they always suspend, not exit => so mine works more and more slows when I run many apps
I check out in Settings, but I still dont know to exit apps then return home every time I click back
Please tell me how to do it
Thank you very much
anyone help me please
download advanced task manager or task killer
I recommend Auto Mem Manager on the Market, a freeware, just choose the "aggressive" profile.
AND, as for how to exit app, I suggest you try to press "back" button when you wanna exit this app, not directly press "home" button.
reply to the OP
Let me explain to you the logic behind this, simply your application is not closed but it enter what is called hibernate mode where it will not consume too much memory and at the same time when you will open the application again you can resume what you was doing.
I belive that this is a smart action form Android OS where you will not find in WM or Symbian (maybe Apple OS).
if you want to get rid of it, please install Advanced Task Manager and from the setting use what ever setting that might suite you.
For me i use the following setting:
Auto Kill Level --> Safe
Auto Kill Frequecny --> Every One Hour
Security Level --> Meduim
With the above setting, i didn't face any performance problem and reduced reboot frequency (General Problem in the Android).
Feel free to ask any question and I will be ready for you
Has anyone come accross a way to make for example a long press of the back button always close (exit) a program....and the Home button would leave it suspended or hibernated. I completely understand what they are trying to achieve by going the 'no exit/close' route, but it is really annoying that it isn't even an option for me. I think it totally defeats the idea of a homepage on your internet browser now. Every time I open the browser, I have to mess around with 10 back button presses or manually open a bookmark. Would be nice to be able to hit back or home if you plan on returning...or just long press back to fully exit whatever you are doing. I've installed a few task manager programs, but haven't found anything that is that easy, or that works on the Atrix.
I have been searching for exactly the same thing myself, mainly because I want to shutdown a crashed or frozen app in one foul swoop!
In the froyo days I used 'Quick Exit Froyo' by long pressing search. This would take me to Android Application Manager where you can hit 'Force Close'
2 presses wasn't good enough for me so I then found 'EXIT - task killer' which creates an 'x' at the top right corner of the screen. Just tap it and the current app shuts down. However, this doesn't work on Gingerbread 2.3.
I'm now searching for one that will work with 2.3, but I will probably have to root my Desire.
links Below:
EXIT - Task Killer - http://tinyurl.com/44gknpy
Quick Exit Froyo - http://tinyurl.com/3jgyd27
Warm regards.
I have cognition 2.2 beta7. I have made every attempt to remove that stupid task manager, but it's hijacked the long press home option even after I removed it. Anyone know what I would do to get back to the normal long press home thing?
xelaboy said:
I have cognition 2.2 beta7. I have made every attempt to remove that stupid task manager, but it's hijacked the long press home option even after I removed it. Anyone know what I would do to get back to the normal long press home thing?
Click to expand...
Click to collapse
The long press home has always brought up a dialog for selecting recently run apps as a sort of short cut to multitasking even in the stock eclair rom shipped by samsung. The only difference in the froyo leak is that dialog now contains a link to enter a new front end app to the task manager.
I don't know how to remove that link - I'm guessing you will have to edit something in the framework somewhere. And by the way - you may have or be able to remove the front end user interface app to the android task manager but you can't remove the actual android task manager and still have the phone be operational.
The long press home thing in android isn't exactly a "Task Manager" in stock android. It functions as a way of accessing apps.
The front end app, has hijacked that screen by adding it's button to it.
I was able to delete the app, but now I am stuck a task switcher screen that has a broken task manager link on it. (which if clicked happens to lock up the entire device.)
I'm sure I'd have to get down and dirty somewhere, but I just don't know where.
xelaboy said:
The long press home thing in android isn't exactly a "Task Manager" in stock android. It functions as a way of accessing apps.
The front end app, has hijacked that screen by adding it's button to it.
I was able to delete the app, but now I am stuck a task switcher screen that has a broken task manager link on it. (which if clicked happens to lock up the entire device.)
I'm sure I'd have to get down and dirty somewhere, but I just don't know where.
Click to expand...
Click to collapse
That dialogue was not hijacked by anything - the link was intentionally encoded by someone from samsung to be in the dialogue in froyo 2.2
Ugh. Why would they do that to us?
That link below is why I think it's stupid. (I'm not sure if I'm allowed to post links yet but I'll try anyway.)
http://androinica.com/2010/05/07/go...-imply-task-killermanager-apps-are-pointless/
xelaboy said:
Ugh. Why would they do that to us?
That link below is why I think it's stupid. (I'm not sure if I'm allowed to post links yet but I'll try anyway.)
http://androinica.com/2010/05/07/go...-imply-task-killermanager-apps-are-pointless/
Click to expand...
Click to collapse
Yes. While task managers have value in allowing someone to watch their phone learn what is going on with their and give them some knowledge and a tool for trouble shooting, far too many people are using them as a system resource management tool, killing processes and apps without really knowing what they are doing or that it is completely unnecessary. Often people are even doing more harm then good as they are going way too far in their zest to kill that they are keeping their phone from operating properly.
I think that is what samsung is probably attempting to accomplish with this limited front end app to the task manager that is being included in their froyo builds - trying to give people a tool to satisfy some of there (way over the top) task killing mania while keeping people safe from getting to deep in there task killing and causing problems.
Hopefully more and more people will start getting the message - quit all the arbitrary unneeded task killing - use your task manager keep tabs on your phone and to catch any problem apps that you may of installed - and leave the resource task managing to the actual built in OS task manager as it really does do a good job - so long as you don't have some poorly coded resource hog software installed.