on casio commando, when i have my browser open and i am loading a page, if i need to leave the browser for any reason and i come back to it later, the page needs to reload. is there a way to keep the browser running so the page doesnt have to reload when i return to it? i am running the stock browser
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help browser
- Thread starter brianlh
- Start date
cbreze
Android Enthusiast
Wasn't sure if mine did that or not as I hardly use the stock, but I tested, got a page started loading and left it and went to another app, came back in 30 sec and the page was loaded and waiting for me. Is that what you meant?
john58ford
Well-Known Member
Using the stock browse myself, my page is up and waiting for me... What procedure do you use to close and open the browser? Depending on what I need to do, I suppose my most frequent method is (from browser with page loaded) press home button, find other program I need, open other program, then for switches between browser and other program(s) longpress on home... there are other ways to do it also, such as the drop out bar (I use this if I'm realy data hungry and running slacker also...) and I'm sure even a way or two I have never personaly used, gotta love android... Anyhow there are also ways that are wrong ways. For example, from browser page >double tapping back, then opening other program then going back to browser icon.
Now here comes the fun part, although you can usualy "close" a program in android by "backing out" as opose to letting it "idle" by pressing home, the way android uses your resources is different in nature than the way windows(or that other company...) uses your resources. Just because you "closed" a program in android doesn't mean it actualy cleared the program from the cache, it may even show it as open in the running programs menu, maybe even if the app had an actual close button you would still find it in the "cached" section. See the thing with android is this thought: If I don't have to wast power to write all 1s over that string of 1s and 0s why would I if this guy is just going to reopen that program in 10 minutes anyhow? but heres the catch, just as it doesn't close that program and clear it from cache just because you asked it to, it may also need to clear the cache for another program to have some headspace while you are "multi tasking", if you are using another program (unlike if you say close this and screen off in the pocket time) the android system thinks you have assigned a priority to this other program and will just short of kill itself to please you.
Any how, now you know; if you are using your home buttons and shortcut keys correctly and using modest processor/ram programs your page should be there ready to go when you get back to it, but if you are flogging that thing like its a new nexus, or any other name brand android phone made since 2009, it's probably going to run out of resources and shoot itself in the knee for you. At least this is a nice and only minor inconvenience issue if it's the later.
Good Luck,
John
Now here comes the fun part, although you can usualy "close" a program in android by "backing out" as opose to letting it "idle" by pressing home, the way android uses your resources is different in nature than the way windows(or that other company...) uses your resources. Just because you "closed" a program in android doesn't mean it actualy cleared the program from the cache, it may even show it as open in the running programs menu, maybe even if the app had an actual close button you would still find it in the "cached" section. See the thing with android is this thought: If I don't have to wast power to write all 1s over that string of 1s and 0s why would I if this guy is just going to reopen that program in 10 minutes anyhow? but heres the catch, just as it doesn't close that program and clear it from cache just because you asked it to, it may also need to clear the cache for another program to have some headspace while you are "multi tasking", if you are using another program (unlike if you say close this and screen off in the pocket time) the android system thinks you have assigned a priority to this other program and will just short of kill itself to please you.
Any how, now you know; if you are using your home buttons and shortcut keys correctly and using modest processor/ram programs your page should be there ready to go when you get back to it, but if you are flogging that thing like its a new nexus, or any other name brand android phone made since 2009, it's probably going to run out of resources and shoot itself in the knee for you. At least this is a nice and only minor inconvenience issue if it's the later.
Good Luck,
John
jova33
Android Expert
I run a s--t ton of apps that I don't need. I'll open the browser, then go SMS, check my email, use my banking app, then go to browser and it'll reload the page I was on. My guess is the Android system is killing processes you're not using, that's why the page reloads. I have no complaints about it. Yeah, my Wife's iPhone 4s works lightening fast, but can it go underwater?