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?
Related
I have tried to ignore this issue but it's gotten to be such a huge pain in the ass that I have to ask. Every time I open a new browser window (tabbed browsing) or use another app even for a split second and switch back to the browser, the whole page reloads -- wtf?? Pisses the hell out of me.
Does that happen to everyone else too?
I'm running Cyanogen 4.2.5, with an 8 GB fat/ext3/linux-swap partitioned SD card. I have very few apps, and am always running 30+ MB free according to TasKiller. The browser reloads even happen when I kill all other tasks except for the browser.
Is there a way to minimize or stop the browser reloads from happening altogether?
Always Happens for me too.
This is pretty ridiculous. I can be on a single webpage, press home for literally 1 second, then go back to browser and it'll reload. (With no other apps open). Grrr
The worst part is the page is 90% visible, so why does it need to fully reload?? (You can press Stop, but then it continues reloading and leaves you with a white screen.)
There has to be a way to stop this?
This is ridiculous
Paul22000 said:
This is ridiculous
Click to expand...
Click to collapse
so is this
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?
Anyone try the new opera mobile 11. it now supports flash.
If so does it work on stock rooted?
Sent from my GT-I9000M using XDA App
Stock rom doesn't support flash so no. It will now show you the preview image, and if you click through to youtube and press play there it'll play the video in your youtube app.
It also recognizes it's on a tablet, and shows a different interface than the one for the phone.
Personally I love the new opera, I'm using it as my daily web browser. That's saying alot considering how good dolphin HD is.
I've tried Opera Mobile 11, Firefox 4 RC, and various reskinnings of the default browser (Miren, Dolphin, and stock). Opera Mobile 11 seems by far the smoothest, apparently due to hardware acceleration. Scrolling/panning, pinch zooming, etc., are smooth as silk, similar to what you'd see on an iPad. None of the WebKit-based browsers are that smooth, presumably because they don't yet feature hardware acceleration (at least on the NC?). Firefox 4 RC looks okay but doesn't yet have Flash. I think I may make Opera may daily driver for a bit and see how it does with the various sites I visit.
UPDATE: After playing with Opera 11 for a while, I'll go so far as to say that everyone should try the New York Times Web site with Opera 11 in landscape orientation. That, to me, is what tablet browsing is all about! VERY impressive!
Sorry for asking this. Which fingerprint do you use? I can only find Opera mini, but not opera mobile in the market. any pointers would be great.
cheezer38 said:
Sorry for asking this. Which fingerprint do you use? I can only find Opera mini, but not opera mobile in the market. any pointers would be great.
Click to expand...
Click to collapse
Even I didn't find opera mobile in market....So i went to opera website thru nook browser (I am using cm7 sd card bootable), went to download page, selected android devices. Here you get option to download opera mini or mobile....
Download mobile and enjoy
I am loving it......
Opera = no Javascript = pass!
akarol said:
Opera = no Javascript = pass!
Click to expand...
Click to collapse
Where did you hear that? Opera Mobile has a very good JavaScript engine.
I've been testing Opera and a few things bug me:
A) Panning up and down the page doesn't "lock" the motion to that axis so that it only moves up/down like every other Android browser does. So the page moves around on BOTH axes (up/down/left/right) and even looks weird as it jitters (or "vibrates") left/right when you only mean to move up/down. In every other browser, when you start panning in one motion, it locks the movement to that axis, which makes for a smoother motion (and rarely do you need to move on both axes, which is why this is implemented).
B) Long pressing on a link doesn't show the URL. Sometimes I'm reading an article and want to see what a link goes to without opening a page. In Opera Mobile, there's no way to do that.
C) I find tab switching to be slower and more tedious than in Dolphin, where the only action needed is a single tap on a tab. Whereas in Opera, you need to tap the (frustratingly small) tabs button, tap the tab you want, and then tap out of it to get rid of the pop-out.
That being said, the re-flow option is much better in Opera than Dolphin. It re-flows the text immediately after zooming, every time. Very helpful.
opera:config, uncheck "Scoll is Pan" in User Prefs, helps a little bit with the vertical scroll lock problem.
The only real issue I've found so far is that it's kind of hard to close a tab. I tap the "X" on the tab but most of the time nothing happens, or if something does happen, there's a LONG delay. Any idea if I'm doing something wrong? I have my LCD density set to 200 so perhaps the UI isn't properly adjusting for that (even though everything looks right cosmetically)?
SCWells72 said:
The only real issue I've found so far is that it's kind of hard to close a tab. I tap the "X" on the tab but most of the time nothing happens, or if something does happen, there's a LONG delay. Any idea if I'm doing something wrong? I have my LCD density set to 200 so perhaps the UI isn't properly adjusting for that (even though everything looks right cosmetically)?
Click to expand...
Click to collapse
I had the same issue. Found out tapping the X button twice did the trick. Best browser I've tried.
victle said:
I had the same issue. Found out tapping the X button twice did the trick. Best browser I've tried.
Click to expand...
Click to collapse
Just tried that and it works perfectly! Thanks!
Thanks for the tip. This is the best browser yet for the Nook in my view. Quick, accurate (pinching, dragging) and no fuss. I'm running it on a CM7 SD card build and it's fast. Flash works. A question, however: I know Flash works because I use Flash for our site and checked it there. However, going to HBO.com (wanted to grab some Flash video to see what happened) it tells me that my device is not Flash enabled -- so won't let me connect with Flash. ????????????????????
Regarding panning, zooming, etc., I found version 11 to be far worse than 10.1 Beta. Whereas it was iPhone/iPad-like buttery smooth with 10.1 Beta, it's now become choppy with 11 like every other Android browser. I can really tell the difference on graphics-heavy pages like espn or engadget. With 10.1 Beta, panning/zooming on images was silk smooth even while the cpu was busy loading the rest of the page; now with 11, that's not the case.
Ironically though, Web pages load much, much faster (in their entirety) with 11 compared to 10.1 Beta.
OMG, I just installed this a few moments ago... can't believe how fast this thing is! It's as fast as the iPad browser on a rooted. stock Nook. running stock clock speed. Gentlemen, I have found my new browser. End of story.
I don't find it to be as tablet-friendly as the stock HC browser, but it does seem to be very good in terms of performance
Most importantly I can now watch youtube videos on my nook even with HC. Wowza thanks for the tip!
rabid_droid said:
Regarding panning, zooming, etc., I found version 11 to be far worse than 10.1 Beta. Whereas it was iPhone/iPad-like buttery smooth with 10.1 Beta, it's now become choppy with 11 like every other Android browser. I can really tell the difference on graphics-heavy pages like espn or engadget. With 10.1 Beta, panning/zooming on images was silk smooth even while the cpu was busy loading the rest of the page; now with 11, that's not the case.
Ironically though, Web pages load much, much faster (in their entirety) with 11 compared to 10.1 Beta.
Click to expand...
Click to collapse
Funny, i am the opposite. For me, this is the first browser in CM7 that lets me view pages like Engadget with good fluidity....
It's also the first I've found that handles xda with any level of fluidity
Animec said:
It's also the first I've found that handles xda with any level of fluidity
Click to expand...
Click to collapse
Same here, I thought I was the only one that noticed. Switched to Opera Mini 10, then back to Dolphin Mini 2 because page rendering more livable, now back to Opera Mobile 11 because of speed, although I still hate how vertical scrolling a pain on long pages.
When browsing the web if I press the home button or go into another app and immediately back into the browser all of the tabs want to refresh, even if there is only one tiny html file open. I have read about many people having this problem on different android devices but it never gets much attention. I am not clear what the issue is, can anyone give me a little bit more info?
I currently run an up to date Serendipity 7 on my Captivate and use Dolphin HD although this happens in the stock browser. Never tried any others. I have run many roms on this device and all of them have had this problem, although some more sporadically than others. With the latest Serendipity it happens like clockwork. I don't use a task killer, the browser doesn't close.
Sounds like a ram priority issue, cache not being written to disk or something. Is this general to the kernel? Is there a browser available that saves pages to disk until you've navigated away for a while? Why do most people not have this problem? Where should I post this so it gets the proper attention?
First post, longtime lurker, this issue is making me mad.
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.