Easy way to quit browser? Am I missing something? - G1 Q&A, Help & Troubleshooting

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.

Related

How to close the browser

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.

[mod-idea] adding a kill/quit button on the menu

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

Browser hogging internal phone storage?

Ever since I updated my nexus to Froyo, when I'm using the browser itll start to take up all of my available memory causing me to get the low storage warning and sometimes stop me from getting text messages. The only way to free back up the memory is to go force close the browser, which is sometimes using up to 80 mb of data. Ive already tried a factory data reset and also went into the recovery and wiped and clear the cache. I never had this problem in 2.1 and its really annoying. anyone got any ideas? thanks.
forceclosing the browser wont clear up cache.... scroll down instead of forceclosing, and hit clear cache. dont do it through recovery
I am having this problem too D:
Yeah, the browser doesn't seem to limit cache, although I've never seen it use 80M. Most I've seen is 7M. I just clear cache through the Applications list, although in Froyo you can do it directly in the browser now.
if you visit the google forums, the android team has changed the browser in 2.2 to cache the pages you have open in your browser much more aggressively, so that when you go back to the browser the phone doesnt need to refresh the network and reload the page. i posted a link to the google topic before. but what this means is that the browser now takes up huge amounts of space as time goes on. killing it does bring back the space. personally i like this change, but i can see why it might suck for some people.
here's the link
http://code.google.com/p/android/issues/detail?id=2171
Anyone who is having this issue, go here and click the star to vote for this issue: http://code.google.com/p/android/issues/detail?id=1068
i posted against this issue, because i happen to like what they did to the new browser. god forbid they go back to the old way, it was not good.
I agree, the browser is better this way in some regards, but it needs to LIMIT what it does... If you don't manually clear cache it'll easily take 8+ megs of storage!
khaytsus said:
I agree, the browser is better this way in some regards, but it needs to LIMIT what it does... If you don't manually clear cache it'll easily take 8+ megs of storage!
Click to expand...
Click to collapse
but its not the cache, its just a temporary storage usage. if you force close the browser, it regains back that storage. at least for me it does. my actual cache in the browser never changes, and hovers around 7mb.
Aaaand we're not using A2SD why???
RogerPodacter said:
but its not the cache, its just a temporary storage usage. if you force close the browser, it regains back that storage. at least for me it does. my actual cache in the browser never changes, and hovers around 7mb.
Click to expand...
Click to collapse
Ah, sorry, I got off topic then.. I was talking specifically about the browser cache, which for me varies between 4-8.5M it seems.. and I clear it because otherwise I'm <20M
Christopher3712 said:
Aaaand we're not using A2SD why???
Click to expand...
Click to collapse
Because not everyone is rooted running non-stock roms?
Simple solution
Friend was having the same issue but this was pre-froyo.
Found out that after viewing articles on the news and weather app and also viewing webpages she was just hitting the home softkey to return to the main page. This was causing new window after new window of fully loaded websites to be cached out of memory and into storage.
Although i agree there should be a caching limit on the browser there should also be an effort from the end user to close the unused windows when done (easily done through the windows menu). Also after using the news and weather app and any other app that uses the browser to display pages, it should be good practice to use the back button and not the home key.
I've always done that and now my girlfriend does it and guess what... its not an issue anymore.
Cabarnacus said:
Friend was having the same issue but this was pre-froyo.
Found out that after viewing articles on the news and weather app and also viewing webpages she was just hitting the home softkey to return to the main page. This was causing new window after new window of fully loaded websites to be cached out of memory and into storage.
Although i agree there should be a caching limit on the browser there should also be an effort from the end user to close the unused windows when done (easily done through the windows menu). Also after using the news and weather app and any other app that uses the browser to display pages, it should be good practice to use the back button and not the home key.
I've always done that and now my girlfriend does it and guess what... its not an issue anymore.
Click to expand...
Click to collapse
Except that you can't use the back button in the browser if you've been browsing a lot, you'll be going backwards through a bunch of pages. And if you've logged in, you can't go past that at all as it'll want to repost data etc...
One could close the window I suppose, which would load a default homepage, then go back, but that's tedious.
khaytsus said:
Except that you can't use the back button in the browser if you've been browsing a lot, you'll be going backwards through a bunch of pages. And if you've logged in, you can't go past that at all as it'll want to repost data etc...
One could close the window I suppose, which would load a default homepage, then go back, but that's tedious.
Click to expand...
Click to collapse
Tedious? Thats almost as bad as that YouTube review of the Nexus where one guy said he had to move his hand "All the way up to the top of the phone" just to switch it on. (Surely we've all seen it?)
I wouldn't say tedious, just something to get used to. Sadly Google aren't quite there with their Google MindReader beta for Android but until then menus and manually closing windows work just fine ;-)
Cabarnacus said:
Tedious? Thats almost as bad as that YouTube review of the Nexus where one guy said he had to move his hand "All the way up to the top of the phone" just to switch it on. (Surely we've all seen it?)
I wouldn't say tedious, just something to get used to. Sadly Google aren't quite there with their Google MindReader beta for Android but until then menus and manually closing windows work just fine ;-)
Click to expand...
Click to collapse
Steps to properly exit browser
Menu button
Select Windows option
X on all open Windows
Back Button
Not exactly "move hand to top of phone".
And again, my major complaint is about the lack of a limited browser cache, ie: html, css, images, cached for later reload. It grows over 8M, that's really too much IMO. Should be able to limit it, in which case I'd likely limit it to 2-3M myself and see how it worked out.
khaytsus said:
Except that you can't use the back button in the browser if you've been browsing a lot, you'll be going backwards through a bunch of pages. And if you've logged in, you can't go past that at all as it'll want to repost data etc...
One could close the window I suppose, which would load a default homepage, then go back, but that's tedious.
Click to expand...
Click to collapse
Actually I do that quite a bit. But you don't even have to. After you close all windows, it defaults to open a last page (Google home in my case), then just hit home cause there's nothing left to cache anyway, so back button or home button does the same thing, makes no difference.
hmm in my case it's also not the cache which makes the problems, but the "Data" of the browser app.
It easily exceeds 28MB!
And cache is only at 600kb, so clearing cache doesn't help.
Clearing the data helps. but it will delete all your bookmarks and other settings which is bull****.
Force closing the browser didn't help too (it helped in the past but interestingly not today).
Browser can not be installed on sd card. System updates can not be installed on external memory.
Sent from my Nexus One using XDA App
Shahpur.Azizpour said:
hmm in my case it's also not the cache which makes the problems, but the "Data" of the browser app.
It easily exceeds 28MB!
And cache is only at 600kb, so clearing cache doesn't help.
Clearing the data helps. but it will delete all your bookmarks and other settings which is bull****.
Force closing the browser didn't help too (it helped in the past but interestingly not today).
Click to expand...
Click to collapse
What? From apps, manage, all, find browser. Clear cache there. That does not clear up your 28M in ram?

why are apps running when i dont open them? memory leak also..

could be a noob question
every once in a while i will go into my advance task killer and see a bunch of apps running that i didnt manually open. i just checked my phone to see sprint nav, mp3 store, droid locator, internet, ringdroid, etc.. it also takes my phone from 71m free to about 35-40m. ill kill the apps, and they will be open again without me touching the phone. am i stupid, or is there actually a problem?
Okay bc those stock apps are coded to run at startup, and open themselfs for ease-of-access, this is normal. If you want to stop that, add them to autokill, and use a startup manager (market) to remove them from the start up screen.
For the mem issues, try disabling the GPS lovation services, that eats up battery life AND mem, same with internet.
If you really want your phone to fly, don't use a task killer.
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
abcdfv said:
If you really want your phone to fly, don't use a task killer.
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Click to expand...
Click to collapse
In theory this is true but in reality it couldn't be more misleading. Yes a task killer, especially one that is always running and using up resources itself is probably less than optimal in an Android environment, however they are sometimes necessary because things do not always work as they are supposed to. If you have root it is better to just use AutoKiller as it doesn't just kill programs but helps the OS by allowing you to set the limits for when the OS should start closing things. It also allows you to manually kill anything not working right.
Of course this is just my opinion, but I have tried it both ways on 3 different Android phones and my results were the same on all.
jlem26 said:
however they are sometimes necessary because things do not always work as they are supposed to.
Click to expand...
Click to collapse
There's a section at the bottom that goes over this.
It's really more of an explanation that "Having free RAM will make my phone faster" will not make your phone faster.

[Q] Is advanced task killer bad?

im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
EverythingNook said:
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
Click to expand...
Click to collapse
Everything I've read says you don't need it with Android 2.2 and above.
I use it, nice quick and easy way to close things (like emulators that normally won't shut themselves off.)
dsf3g said:
Everything I've read says you don't need it with Android 2.2 and above.
Click to expand...
Click to collapse
me too but my friends have 2.3 and they use it.
I use it if videos start to stutter (ie youtube etc). It seems to help.
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
alright ill stay away from it thanks!
That about sums it up. The only time an app should be killed is if a bug causes it to hang or slow down severely. Otherwise, let the Android system handle things itself.
In my experience it's nice to have for when you need to kill off a specific game or resource intensive app that seems to be slowing things down.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
so would you recommended going into the app itself and picking the apps i want to be closed? or could i also use the widget to close all of them?
I would only recommend going into the app itself, long-pressing on the app you want to kill, and then pressing kill. Closing all of them just forces a large number of apps to restart. I really only use it to kill certain apps that are more difficult to close.

Categories

Resources