Ever since I have my HTC Magic on Vodafone UK, I have that utterly annoying issue of Magic's internal browser reloading webpages that were previously loaded and switched into background. Simple example: I load a webpage, making sure it's fully loaded. Then I go back to home screen, play around with icons or other apps etc., or open new browser window and load another page. After short while, when I go back to that first loaded page (already fully loaded and sitting in the background) - I get blank browser window, and page gets reloaded from the scratch. Uber-annoying, especially when I try to get few pages pre-loaded for later reading while in the Tube.
There is a bug floating around Android's bugtrack: http://code.google.com/p/android/issues/detail?id=2171 - however I was wondering whether other Magic users are experiencing same thing and if there's any workaround for this?
eva_d said:
Ever since I have my HTC Magic on Vodafone UK, I have that utterly annoying issue of Magic's internal browser reloading webpages that were previously loaded and switched into background. Simple example: I load a webpage, making sure it's fully loaded. Then I go back to home screen, play around with icons or other apps etc., or open new browser window and load another page. After short while, when I go back to that first loaded page (already fully loaded and sitting in the background) - I get blank browser window, and page gets reloaded from the scratch. Uber-annoying, especially when I try to get few pages pre-loaded for later reading while in the Tube.
There is a bug floating around Android's bugtrack: http://code.google.com/p/android/issues/detail?id=2171 - however I was wondering whether other Magic users are experiencing same thing and if there's any workaround for this?
Click to expand...
Click to collapse
Is it a bug or is it just that the web browser has been moved off RAM to make space for another application so that when its re-opened, it has to reload everything again.
If you load a website that is just text only without any graphics or javascript and then go to another application and come back, it will not be reloaded, because the footprint is small.
dwang said:
Is it a bug or is it just that the web browser has been moved off RAM to make space for another application so that when its re-opened, it has to reload everything again.
If you load a website that is just text only without any graphics or javascript and then go to another application and come back, it will not be reloaded, because the footprint is small.
Click to expand...
Click to collapse
Yes, I can understand this point of view, however I'd still regard this as a bug, or at least as a feature that massively undermines user experience as for internet-centric mobile device...
In fact, this is the very first device I've had in my hand that has such 'feature', in every other phone or internet tablet (like Nokia N810) that has multi-window browser, I am able to load many webpages simultaneously and keep them persistent in the background. The new and shiny, internet-centric HTC Magic suddenly offers that 'magic' feature of saving RAM at a cost of utterly horrendous user experience...
dwang said:
Is it a bug or is it just that the web browser has been moved off RAM to make space for another application so that when its re-opened, it has to reload everything again.
Click to expand...
Click to collapse
Anyway, content should then have been cached on sdcard (or internal memory).
have you tried swapper?
http://forum.xda-developers.com/showthread.php?t=483110
that extends the internal ram out to flash so maybe that will help.
Seems to work fairly well. I can have imeem streaming and other stuff and the browser pages still stay in "memory" and aren't reloaded.
dwang said:
have you tried swapper?
http://forum.xda-developers.com/showthread.php?t=483110
that extends the internal ram out to flash so maybe that will help.
Seems to work fairly well. I can have imeem streaming and other stuff and the browser pages still stay in "memory" and aren't reloaded.
Click to expand...
Click to collapse
Good idea, but I'd need to root my phone first, which is actually quite good excuse to do it.
Thanks for a tip!
eva_d said:
Good idea, but I'd need to root my phone first, which is actually quite good excuse to do it.
Thanks for a tip!
Click to expand...
Click to collapse
yeah, i've been using it for a few hours and once everything is loaded into memory and swap, and its not bad and I haven't encoutered a browser page reload yet.
Of course when a swap from flash to memory occurs, there's a pretty significant pause, but thats to be expected.
Just a quick update, I've finally managed to install swapper and set the swap space to 32MB. It helps to the issue, however when many other windows are opened, there is still that reloading issue...
I guess it's not a bug, but just a feature of Android and its 'clever' memory management. Fingers crossed that they would improve it in future versions...
The web browser should be Google's most stable and capable app, that's where google should shine. I wont rehash all of my browser problems (yes I've tried 3rd party browser apps) because I trust google and ill be patient for software updates to make the browser more functional. But sometimes from the browser I press home, send a text and when I go back to browser I'm at my homepage but other times same sequence and I'm at the same page that I was on before I pressed home and sent the text. I know its not my task manager. I thought maybe it was a setting but sometimes it doesn't take me to my homepage and sometimes it does. Does anyone know how I can consistently go to browser and be at the page I was on when I last left the browser? I want it to restart via my task manager at the times I have it set to but I need to be able to press home, carry out various functions and still have the same website up. I'm almost positive its user error but I don't know what to do. And yes I used the goddammed stupid search function. Thanks for any help...
Android has a built in task manager itself, as well, that closes apps as need be to free up RAM for current processing. As well, if you have a 3rd party task killer, it can get pretty dicey, even if you have browser "excluded". Also, keep in mind that your task manager uses up RAM itself, and in all honesty is not needed unless you really want to close tasks, and in that case just use Astro.
Anyways, 99.9% of the time the browser is where I left it at. I would say 100%, but I can't be 1000% certain the browser has never been closed by the built in task manager.
I remember having that problem constantly with my G1 but haven't run into it yet with my N1. As the guy before said, its likely that the memory manager is killing the browser app. Here are a few questions I would look into:
1. Are you using an advanced launcher? This can open a NEW window, but won't close an old one
2. How many apps do you have installed? The more apps you have the more that will boot on startup, eating away at memory
3. How many messages do you have? Maybe there are so many that the messaging app is logging all the memory.
4. Are you running CM5 with the highmem hack? If not, this sounds like a good excuse for you to root.
I've noticed that if you launch the Browser by using Home <Long Press> it often tries to reload some previous page that you were at. If you launch the browser directly from the home screen / app tray, it doesn't do this.
Very weird.
I've noticed a serious problem with the way android handles multitasking, at least for me. if I am using opera mini browsing, and I switch to the built in browser and go to a bookmark and load a page, now when I'm done and I go back to opera mini it starts a brand new session of opera. I've lost my page that I had open.
my free RAM during this is around 35 mb. this is why I think we should have control over what runs in the background rather than the OS just loading up everything and deciding for us. I don't have any services or anything running during this time, and I'm on the stock ROM. anyone else experienced this? anyone think this is a serious usability issue?
I've been testing this every which way, using either the home button to switch or long pressing home button to switch, and every single time opera closes.
my current free
No, that is just the way opera was made.
Why blame the os its the app...
Yep, its only Opera. I don't use it anyways, but when I did - I do remember this issue, well I guess its an issue..
its not opera because this issue doesn't happen if you do not go to the bookmarks of the default browser. go ahead and try it out. I can go open 10 other apps and multi task, and I can still return to opera mini on the same page I left it at. its most certainly not a problem with opera mini. It's a problem with the way the OS handles certain events giving them priorities over others, I.e. default browser bookmarks gets some higher priority. so again if we had the ability to actually control what we want to run, it would be better.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Wait a second, my Opera stays on the same page I left off on, even if I plenty of other applications open. A lot.. Maybe cause I'm rooted, and I have more RAM at the time? I am also using Dolphin, and the default.. and it still is leaving off at the same page.
RogerPodacter said:
my free RAM during this is around 35 mb.
Click to expand...
Click to collapse
This sounds fairly low.
How many apps do you have?
Are you rooted / using a custom rom?
Paul22000 said:
This sounds fairly low.
How many apps do you have?
Are you rooted / using a custom rom?
Click to expand...
Click to collapse
He said he is using the stock ROM in the first post. :/
Eclair~ said:
He said he is using the stock ROM in the first post. :/
Click to expand...
Click to collapse
Woops, missed that somehow.
Well... There's the problem haha!
ok maybe I jumped the gun, because I closed all my apps in one swoop and still only had 30 mb free RAM. so I did a reboot and now my opera mini does not close no matter what I do.
that's strange though, I guess its good to reboot once in a while as something ate up all my RAM. it was at the point where I closed every service and every app with a task manager, and still had barely any ram. my bad guys.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
RogerPodacter said:
that's strange though, I guess its good to reboot once in a while as something ate up all my RAM. it was at the point where I closed every service and every app with a task manager, and still had barely any ram. my bad guys.
Click to expand...
Click to collapse
Not your bad, Opera's bad. They should do a better job of saving application state so that when the OS shuts it down it doesn't cause you to lose the page you were on.
OK i'm having this same exact problem again. All day yesterday i was browsing with opera mini, press home button to perform other tasks, and come back and it is still showing the same web page i was reading.
but then last night all i had to do was check my email real quick, i switch away from opera with the home button press, and go back to opera and it now has to re-load the entire app, taking me to the start page again. surely this is some problem with the way android OS handles multitasking, no? i mean the app obviously was saving my page all day yesterday, just like its supposed to. but then it suddenly STOPS doing this.
my free RAM was again down near 30MB because the OS has loaded a million apps that i dont need. yet the OS then will close the one app i DO need, opera mini, while leaving all these useless apps running, which i didnt even ever need or open in the first place!!
am i the only one who has a problem with this method of OS task management?
i'm sure a reboot will free up all the RAM and things will work normally again. but isnt android a linux based OS? shouldnt linux be able to run for days or even weeks without the need to reboot the phone just to set the RAM back on track?
very frustrated!
If you have a mirror handy, kindly gaze into it and you will find your problem.
http://www.youtube.com/watch?v=BFytHoXdG3E
lol
RogerPodacter said:
surely this is some problem with the way android OS handles multitasking, no?
Click to expand...
Click to collapse
No.
Again, this isn't a problem with Androids method of multitasking, it's a problem with the way Opera was written. It's not saving it's state properly. It should, but they haven't written it properly.
Opera obviously doesn't behave the way you expect, so my suggestion is to use something else until they have fixed it.
I just can't get on board with that argument. so the OS is giving priority to apps like tuneWiki, which I haven't opened in 3 weeks, over an app that I just switched away from 10 seconds ago is the best way for the OS to operate?
I would agree if my issue happened every single time. but 95% of the time opera stays open like its supposed to. so that tells me it IS doing what its supposed to. but in certain situations it just magically disappears even though it was just in use a few moments before.
I agree that opera is not saving state properly when the OS decides to close it. but why can't the OS leave it open with all the RAM and CPU power this phone has? this situation shouldn't even be happening whether opera is coded right or not.
I made a post on the opera forums to see if maybe they know about it and have a solution.
RogerPodacter said:
I just can't get on board with that argument. so the OS is giving priority to apps like tuneWiki, which I haven't opened in 3 weeks, over an app that I just switched away from 10 seconds ago is the best way for the OS to operate?
I would agree if my issue happened every single time. but 95% of the time opera stays open like its supposed to. so that tells me it IS doing what its supposed to. but in certain situations it just magically disappears even though it was just in use a few moments before.
I agree that opera is not saving state properly when the OS decides to close it. but why can't the OS leave it open with all the RAM and CPU power this phone has? this situation shouldn't even be happening whether opera is coded right or not.
I made a post on the opera forums to see if maybe they know about it and have a solution.
Click to expand...
Click to collapse
I'm not sure you're understanding what everyone else in this thread is saying, so here's another way to think about it:
Can you name another big-name app that behaves in the same constant state-losing behavior as Opera?
RogerPodacter said:
so the OS is giving priority to apps like tuneWiki, which I haven't opened in 3 weeks, over an app that I just switched away from 10 seconds ago is the best way for the OS to operate?
Click to expand...
Click to collapse
The fact that it feels like tuneWiki hasn't been closed even though you haven't used it in 3 weeks lead me to believe that the tuneWiki guys have done it correctly and as a result the user can't tell if the app has been running the whole time or if it is actually loading up a fresh copy of it (loading speed might be the only way to tell). Opera with tabs open probably uses a lot more memory than most programs, so it's a good candidate to close down when memory is needed which is probably why it keeps happening to you.
What Opera should be doing is taking a snapshot of the tabs you have open when you switch to a different applications and writing it to permanent storage so that if it does happen that it get's closed down by the system, when it starts up again later it can reload all of the tabs. It doesn't need to store the page data, just the URLs. I don't know why they don't do that for Opera Mini as their desktop browser does it perfectly.
If you are interested, this developer video on Android application lifecyle might clear things up a bit:
http://developer.android.com/videos/index.html#v=fL6gSd4ugSI
Send Opera an email and tell them to use meta data to remember where you were.
RogerPodacter said:
I just can't get on board with that argument. so the OS is giving priority to apps like tuneWiki, which I haven't opened in 3 weeks, over an app that I just switched away from 10 seconds ago is the best way for the OS to operate?
I would agree if my issue happened every single time. but 95% of the time opera stays open like its supposed to. so that tells me it IS doing what its supposed to. but in certain situations it just magically disappears even though it was just in use a few moments before.
I agree that opera is not saving state properly when the OS decides to close it. but why can't the OS leave it open with all the RAM and CPU power this phone has? this situation shouldn't even be happening whether opera is coded right or not.
I made a post on the opera forums to see if maybe they know about it and have a solution.
Click to expand...
Click to collapse
Each properly coded app speaks up and says "I Have _____displaying on screen, I have ____data on hand and I'm doing______".
If the OS says "sorry bud, you gotta go away cause the guy that's always fondling me(you the user) needs to do something else, go away" then that program is killed and that information saved.
Next time you open up your app, the OS asks "alright, I just got finished showing this guy settings, now he needs you again, do you remember where you were when I sent you away?"
If yes, then boom, you are back to where you were. If not then, your app goes back to square one.
Seems opera mini isn't properly implementing their save states. It's an issue with the application not the OS.
RogerPodacter said:
I just can't get on board with that argument.
Click to expand...
Click to collapse
YOU MUST UNDERSTAND THAT THIS IS OPERA'S FAULT. THE DEVELOPERS DID NOT PROPERLY WRITE THE PROGRAM TO SAVE CURRENT STATE. IT HAS NOTHING TO DO WITH ANDROID OS
RogerPodacter said:
I've noticed a serious problem with the way android handles multitasking, at least for me. if I am using opera mini browsing, and I switch to the built in browser and go to a bookmark and load a page, now when I'm done and I go back to opera mini it starts a brand new session of opera. I've lost my page that I had open.
my free RAM during this is around 35 mb. this is why I think we should have control over what runs in the background rather than the OS just loading up everything and deciding for us. I don't have any services or anything running during this time, and I'm on the stock ROM. anyone else experienced this? anyone think this is a serious usability issue?
I've been testing this every which way, using either the home button to switch or long pressing home button to switch, and every single time opera closes.
my current free
Click to expand...
Click to collapse
This is already an issue that has been brought up in a previous post. They came to the conclusion that it was the app, and in all common sense, it is the app. There is no reason to blame the OS, that is Android. Might i recommend rooting your phone and uploading a fine ROM like CyanogenMOD? I think it would be on your best interest to do so.
so the OS is giving priority to apps like tuneWiki, which I haven't opened in 3 weeks, over an app that I just switched away from 10 seconds ago is th
Click to expand...
Click to collapse
The fact that it feels like tuneWiki hasn't been closed even though you haven't used it in 3 weeks lead me to believe that the tuneWiki guys have done it correctly and as a result the user can't tell if the app has been running the whole time or if it is actually loading up a fresh copy of it (loading speed might be the only way to tell). Opera with tabs open probably uses a lot more memory than most programs, so it's a good candidate to close down when memory is needed which is probably why it keeps happening to you.
What Opera should be doing is taking a snapshot of the tabs you have open when you switch to a different applications and writing it to permanent storage so that if it does happen that it get's closed down by the system, when it starts up again later it can reload all of the tabs. It doesn't need to store the page data, just the URLs. I don't know why they don't do that for Opera Mini as their desktop browser does it perfectly.
If you are interested, this developer video on Android application lifecyle might clear things up a bit:
http://developer.android.com/videos/index.html#v=fL6gSd4ugSI
Click to expand...
Click to collapse
just to be clear I literally haven't opened tuneWiki in 3 weeks, and have done many reboots since then. it was just an example of one of the many apps I see running in the background, which I've never opened in weeks, yet the one I just used is the first to close.
to the other replies, I'm not confused and understand what's going on. I just think its a major flaw whether opera is saving state correctly or not.
9 out of 10 times I can switch away, do my tasks, come back and opera is still there where I was browsing. I just don't like the inconsistency. I feel like I have nocontrol over what and how I want my apps to run.
also if opera mini DID have to save my tabs and reload them, then that would be horrible as it takes certain time to get the proxy server going and then reload the pages. the current method where It's just instantly there, still in memory, is the best way for it to happen. and it DOES work this way majority of the time.
I've noticed in the default browser (when the user agent is set to tablet mode) that when I go to Flickr and look at photos using their Lightbox it will sometimes cause FC's. I even had it cause a sudden reboot yesterday but that might be because I was using an overclocked kernal at the time. I switched back to Prime 1.6 kernel but it still FC'd on me when performing the same operation.
If I use Opera in tablet user agent mode Lightbox appears but no photos show.
The only app that seems to work is the new Dolphin Pad beta. I like the tablet mode Lightbox because instead of clicking on next/back you just swipe the screen to move to the next photo. In Dolphin Pad you have to disable side swiping though for this to work otherwise you get the Dolphin sidebar settings instead.
Not sure if this is a problem with the browsers or Flash or Flickr's Lightbox to be honest.
EDIT: Nevermind it crashes Dolphin Pad too. No FC warning either. A straight crash out to desktop. Anyhow else have this issue (in any browser)?
Late post to this thread... I have been trying to figure out causes of rebooting (ramdump.log present), and have narrowed it down (painful process) to an application that doesn't play nice with my TF. I am pretty sure it's the lightbox application as my tablet is rock solid for days on end, going into deep sleep and no random rebooting when lightbox is uninstalled..... But frequent, random rebooting when installed. Shame, as it's a really promising camera/photo management app.
I'm currently running ARHD 2.0.1 with Prime 1.9.1 stock kernel (pretty sure the same kernel for 3.2.1 current asus 3.2.1 stock ROM).
Actually this is not a question, just a statement in case any people from Samsung are reading, they should get their stuff right.
What I like about Chrome browser was the way it "fits" the text of web pages in comparison with the stock browser which makes everything look so small. (Text, not photos)
So after some searching with the settings (accessibility) on the stock browser, I managed to get the same exactly text fitting on the screen, as Chrome.
The bug is this:
Every time I close the browser and re-open it, it doesnt perform the settings I've made.
If I go to the settings menu, the settings are there but not applied on the web page.
If I make a minor change and go back, they are applied.
But again, if I close the browser and re-open it, the page appears with stock settings although if I check the settings, my settings are there.
Only by making another change, it applies the rest of the settings I made.
And again the same thing... Close the browser, re-open it... Page opens with stock settings.
Get your stuff right Samsung guys.... This is your flagship mobile at the moment.
(ofcourse if anyone has a solution to this, although I've tried everything, it is VERY welcome)
A lot of people are quite unhappy with that. If I'm not wrong, it's called text reflow. Just use other browser apps. I prefer firefox. It's less buggy than chrome.