Just out of curiosity, does anyone know why our browsers have to reload the page even though you are just going "back" one page. For example, if I visit Gizmodo, then go to engadget, then back to Gizmodo, my browser has to reload the page instead of using the cache. It seems as if the cache is barely used (granted the reload is a little quicker, but not much).
Is there a tweak or program that can make this better? It is really frustrating, especially if you are trying to browse a page and accidentally hit the wrong link, which requires you to fumble for stop and oft times requires a reload (this is one reason I miss the Hero browser, because it had a stop button in the address bar).
Hmm, I've noticed this as well. Perhaps Android thinks you need to refresh the page? I know with apps like Opera Mini, pages back (somewhere around 10) are completely stored which is a very nice feature, but as to why Android doesn't do this, is a mystery .
I know the larger files, like images and chunks of text, are saved to the cache, but not whole pages. That would get pretty big after a while, and would slow down the browser because of access times. It's the time the Browser takes to draw the page is what's creating the lag. Look at Opera Mini again, the page loads instantly because it's zoomed out first, then you zoom in.
try "steel" browser.
@ phuthanvinh: I have tried "Steel", but it really isn't any better.
@lukekirstein, yeah, that is one nice thing about Opera. It loads cached pages almost instantly in most instances. When I need quick information, I always turn to Opera. If I want to browse for pleasure, then I use the Android browser.
It would be awesome if a Developer could implement some type of Webkit add-on that forces cache of the whole page.
I just wonder if the "lag" is not caused by redownloading, but rather stems from Android using software-based graphics decoding instead of using the onboard graphics chip. At least that is what I have heard.
I have the same issue and it's very annoying when I'm using google reader!
Have you find a solution?
Does anyone have a solution to prevent android browser to reload pages already load in a tab after I come back from another tab?
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 just updated to the latest version of Google Maps, 5.5.0
It now seems to take forever for the app to load new "areas," and navigating the app itself is significantly more sluggish than normal. Is anyone else experiencing this?? As of now the app seems close to useless. Vector mapping is enabled, as was made default in an earlier update.
Edit: I think I fixed it by going to Cache settings > Clear map tile cache
I notice that the maps load differently, the image tiles in the background load first then the street names, which is how it worked before but it looks and renders differently. It's probably doing it asynchronously.
It is much slower now, but I'm thinking it could be server side.
It's reasons like this I don't let ANY apps auto-update. Thanks for the heads up. Please keep us posted on whether it's fixed or not
It does look a little different, but it could be all in my head. It seems sharper, almost. After clearing my cache as stated in the 1st post, the app is bearable again. However, panning and loading new content still seems slower than 5.4.0.
BTW, I don't let any of my apps auto-update either, but that's just because I like reading the changelog. But I might as well have it checked since I'm not cautious like you, and just want the newest version ASAP
Hi,
I have been using the default browser, and also Chrome on my Xoom. Initially, they both seemed pretty fast, but after several days of using them, they both get pretty slow. I usually have multiple tabs open (3 or 4), and loading up a typical page takes quite a bit of time. For example, loading engadget takes about 25secs. Clearing the browser cache, and history helps a little bit - down to about 20secs.
Comapre that to my ipad, which loads up much faster.
But, either way scrolling up on down just a little fast brings white screen - while it takes time to refresh the content on the page.
What kind of performance are you seeing?
I am on a 12Mbps connection, so that shouldn't be an issue.
ive noticed this too. clearing the cache seems to help
hkk said:
Hi,
I have been using the default browser, and also Chrome on my Xoom. Initially, they both seemed pretty fast, but after several days of using them, they both get pretty slow. I usually have multiple tabs open (3 or 4), and loading up a typical page takes quite a bit of time. For example, loading engadget takes about 25secs. Clearing the browser cache, and history helps a little bit - down to about 20secs.
Comapre that to my ipad, which loads up much faster.
But, either way scrolling up on down just a little fast brings white screen - while it takes time to refresh the content on the page.
What kind of performance are you seeing?
I am on a 12Mbps connection, so that shouldn't be an issue.
Click to expand...
Click to collapse
Experiment with different browsers. I used dolphin hd for a long time, but it got a bit laggy after updates a couple months ago (haven't tried it in a while, might be better). Boat browser is currently my primary... just tried endgadget, and while it certainly isn't scientific, my results were less than 10 seconds in 3 tries, the fastest being 5-6. I also use maxthon and firefox periodically, and keep at least 1 "lite" browser loaded (boat mini at the moment) for use when in a low bandwidth cellular area.
im using chrome as default and have no issues whatsoever - pages load 5-6 seconds on wifi speeds upto 12mbs - only issue with chrome for me is no flash support yet
From what I understand there will not be any flash supports for chrome beta on android.
Sent from my Xoom using XDA Premium HD app
Thanks for the responses guys, will try the other browsers mentioned.
So I added this in another thread but I feel it might be a slightly different problem... A lot of my data transactions have this "hesitation" before the requested info loads. Instagram, Facebook, web pages, etc all continuously have the loading spinning circle and will sometimes even time out. I have to refresh to get it to load again, sometimes multiple times. I've tried using DNS switching using apps that make a VPN for that purpose but still have the issue. Any ideas? I am on QK3. Thanks!