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.
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?
I usually keep my N1 at around 30-50 MB free of internal storage, which is enough to have everything I want loaded on, but it's tough to free up much more space than that without uninstalling apps or moving to SD the apps that shouldn't be moved.
So anyway, today my phone suddenly dropped down to 13 MB left and the culprit appeared to be Browser data - suddenly over 46 MB! The cache was already cleared. I went through with Root Explorer and found that the largest file was located in:
/data/data/com.android.browser/app_thumbnails
For some reason a 31.5 MB file had made it into this directory, and Android clearly is not smart enough to clean it up. Anyway I deleted the offending file via Root Explorer and now it's happy.
Any thoughts on how to keep the browser from ballooning like this? I didn't want to delete all browser data because of bookmarks, cookies etc.
because in 2.2 froyo google updated the browser to temporarily store the entire contents of the page you are browsing into memory such that if you lost data connection, the page could be reloaded without the data connection. so when you have a few tabs open in the browser, or a very large site open, all contents are temporarily being stored for just in case.
if you were to close out all the tabs, kill the browser, all would return to normal. often times my browser hits up over 80MB because i have tons of pages open. i just kill all my tabs and the low space warnings go right away.
its a trade off, i dont mind it cause its better than the old way, but the trade off is we suffer with low storage.
I'll try closing tabs next time, but I swear I'd already closed all the tabs and still the bloat persisted across reboots...
Sent from my Nexus One using XDA App
also delete the browser cache if you want to clear the pron vid, that stuff can take up quite a bit of space
cmstlist said:
I'll try closing tabs next time, but I swear I'd already closed all the tabs and still the bloat persisted across reboots...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
when this happens to me, occasionally i kill all the tabs and it takes a small bit of time for it to appear back to normal, but never more than a minute or so. but if i close the tabs, then force close the browser, it for sure instantly clears the used space back.
if its happening to you across reboots, then might be something completely different.
FYI i havent cleared my browser cache since July last year hehh, and i use the browser like a madman. i wonder how much space i'd get back if i did?
I find that when space is low, it automatically empties the browser cache to zero. In the scenario I described above, the cache was already empty.
Sent from my Nexus One using XDA App
Hello everyone.
My Bionic is my first android device and I'm having an issue with the web browser automatically refreshing the page when I leave the browser and then come back.
It will still be open to the page I was one but refreshed and back at the top.
I'm assuming this is a memory savings item so it doesn't have to hold the entire page in memory while the browser isn't active but it's very annoying when I'm partly through a page and having scroll back down and figure out where I was.
Is there a way to stop this behavior? I've seen the ability to add tasks to an "autokill" list that drops them within a few seconds of going inactive but nothing to make something permanent.
Thanks.
This is something I've had to deal with since Android, but it doesn't really bug me, because I can understand why. With my Bionic, this definitely doesn't happen as much as when I had my Droid X, since it has more RAM, but there very well could be some sort of way to get this to work. I know there are some task killer apps (but that makes it completely useless if our on an OS past 2.2+) that will allow you to keep apps in memory at all times, but other than that, I believe it does it just so your phone doesn't get bogged down with trying to keep a whole web page in memory.
That's what I figured.
I was reading a game walk through and then switching back to the game and I had to keep scrolling back down through the massive page to find where I left off.
I wonder if an alternative browser would be any better? I'll have to search the market.