EpicSki › The Barking Bear Forums › EpicSki Feedback/Tech Talk › The Bug Report ›  Android - threads with lots of photos essentially unusable
New Posts  All Forums:Forum Nav:

Android - threads with lots of photos essentially unusable

post #1 of 21
Thread Starter 
I've posted about this before, but it deserves a bump. Threads such as the Utah gathering trip report thread, which have many embedded images, are nearly impossible to deal with on Android. It's particularly bad if you need to compose or edit a post. The screen is constantly reloading all the images and auto-scrolling in inscrutable and super-annoying ways.
post #2 of 21
I reset the maximum posts on a page to 10 to reduce that problem, but lately Chrome for Android is crashing on pages with lots of pictures.

I'd reduce it to five if the option were available.
post #3 of 21
FWIW, I'm not having any trouble with images using Firefox for Android (free download on Google Play). Dolphin is another lightweight Android browser that works well. These might be options until the Android mobile site is better.
post #4 of 21
Thread Starter 
Quote:
Originally Posted by sibhusky View Post

I reset the maximum posts on a page to 10 to reduce that problem, but lately Chrome for Android is crashing on pages with lots of pictures.

I'd reduce it to five if the option were available.

 

I'll look into that. But the biggest problem is with composing a reply. I think it has partly to do with the "auto save drafts" feature. It seems to auto save about every 10 seconds. And each auto save seems to take about 8 seconds. So basically you have 2 seconds of responsiveness and then 8 of freeze time, etc. 

 

Quote:
Originally Posted by litterbug View Post

FWIW, I'm not having any trouble with images using Firefox for Android (free download on Google Play). Dolphin is another lightweight Android browser that works well. These might be options until the Android mobile site is better.

 

Okay, I'll look at that too. Thanks.

post #5 of 21
Thread Starter 
Firefox test: utter fail. Browser crashes before it will even load the Utah trip report thread.
post #6 of 21

That Utah thread is also crashing FF 27 on my Win 7 notebook.  That said, it loads amazingly well on my Nokia 928 Windows Phone with IE whatever came with it..  So, go figure!  Guess it helps that I'm not using 4g at the moment and have a decent speed router rocking the place..  Didn't help FF 27 though so again, go figure!

post #7 of 21
I have tried this with three Android browsers. Loading the Big Sky picture thread is impossible. However, the Puffin browser at least gave me a clue. It told me it had insufficient memory before it crashed. I suspect there are only so many pictures that can be served to a mobile device. In spite of the fact that I have set the mobile preferences to only have ten posts per page, if someone is putting ten pictures in a post, you end up with 100 pictures coming down. There needs to be a limit on the number of pictures allowed in one post and the ability to ask for fewer posts per page, maybe even down to 3 if that's what it takes.
post #8 of 21

Probably in part due to the fact that we decided to not cap the size of images to allow high-res uploads, might overload the browser. FWIW I've never had issues with crashing on iOS, but I do know how frustrating the constant scrolling can be as a result of images loading. Nothing to do about it really other than have a really really fast internet connections. 

post #9 of 21
It's a memory issue causing the crashes, not a speed issue. The scrolling issue is reduced by having fewer posts per page. The crashing could be reduced by allowing an even lower number of posts to be set for a page.
post #10 of 21
Right but the scrolling is a speed issue.
post #11 of 21
Quote:
Originally Posted by tylrwnzl View Post

Right but the scrolling is a speed issue.


Or a poor resource management strategy.  Allowing unlimited numbers of unlimited sized items in a post sounds like a formula for disaster to me.  Not many other forums allow super high resolution uploads.  IIRC this one used to have a much smaller limit as well.  What was the rationale for dropping the size limit?

post #12 of 21
Quote:
Originally Posted by crgildart View Post
 
Quote:
Originally Posted by tylrwnzl View Post

Right but the scrolling is a speed issue.


Or a poor resource management strategy.  Allowing unlimited numbers of unlimited sized items in a post sounds like a formula for disaster to me.  Not many other forums allow super high resolution uploads.  IIRC this one used to have a much smaller limit as well.  What was the rationale for dropping the size limit?

 

We had some users request it for uploading high quality images to the Picture of the Day thread, although that was pre-mobile so perhaps we should re-evaluate. 

post #13 of 21
Quote:
Originally Posted by qcanoe View Post

Firefox test: utter fail. Browser crashes before it will even load the Utah trip report thread.
My apologies. Maybe there's something about our phones' hardware that makes it easier for mine to deal with the memory problem. Your right that unlimited sizes of graphics might be a mistake, even though I do love high rez photos.

I'm still doing okay reading forums with Firefox, but drafting posts is so bad that I have to take breaks to avoid hysteria. I can't get the cursor to stay somewhere unless I select some text, at which point I can retype the selected text and continue with whatever I wanted to insert. I can draft posts elsewhere to paste into the editor, but it takes several tours before the editor stops pasting an old post in and recognizes that the clipboard has new text in it. And the fact that the editor is five lines high doesn't make things any easier.

Now I'm giving Chrome a shot. So far this post is going well, but what do you want to bet that I won't be able to view photos? Good thing I don't get any emoticons...
post #14 of 21
The hardware definitely matters. My cheap acer tablet has trouble, but my fancy samsung phone does fine. Stock browser and similar pretty- current version of android on both.
post #15 of 21
Quote:
Originally Posted by mdf View Post

The hardware definitely matters. My cheap acer tablet has trouble, but my fancy samsung phone does fine. Stock browser and similar pretty- current version of android on both.

   

Hardware almost for sure.
Crashing due to insufficient memory is a client side problem, ie you don't have enough ram. 
The scrolling is a load time issue. 
 
Regardless, some of the images uploaded here are of insane size. They need to be capped. That big sky photo thread was pulling some serious memory. It would be some work but it would be sweet to upload high res images to the album, with a medium quality thumb as a link to the high res version in the post itself.    
post #16 of 21
My Nexus has a Gig of RAM. But I don't know how much is usually available with other things running.
post #17 of 21
Quote:
Originally Posted by sibhusky View Post

My Nexus has a Gig of RAM. But I don't know how much is usually available with other things running.

Something else could be eating it up. Some of the threads on here are pretty ridiculous though. My Linux chrome was eating 2+ gigs with a couple of tabs and the big sky thread open. It likes to eat though. I have so much ram it doesn't matter much to me. Internet is slow though. 

post #18 of 21

FYI I am in discussions with Huddler about our image sizing/page loading issues. 

post #19 of 21
Quote:
Originally Posted by sibhusky View Post

My Nexus has a Gig of RAM. But I don't know how much is usually available with other things running.
Here are two apps that tell you how much memory is free, and include app killers and app moving functions (you want all your apps on your SD card; otherwise they eat up, yes, memory), and they also find APK files, whatever they are. I was told app killers aren't necessary, but I'm amazed at how many apps that I haven't even used recently turn out to be eating RAM, and my phone gets much more perky when I frequently take that half a minute to run the the memory manager apps. I've got them set to put an alert in the toolbar when I go above 80% memory usage. You could do most of this within Android, but you'd have to know how to do it, and it would take much more time.

The first app is MobileCare, by IObit. That's the one that was recommended by a new IT guy who's the geekiest geek I've ever known. It's got virus scan, game speeder, and an anti-theft function (I use another program for that), but I mostly use the app killer and app manager. The app killer is very conservative; it lists the apps but won't automatically kill anything you've used relatively recently, including system functions; it tells you what they are, and takes you to the app, where you kill it, and then go back to work on the next one.

The other one is Clean Master; Steve mentioned it, but said he preferred IObit. It's much less conservative; if it finds anything running that I haven't just recently used, it comes up with the 'kill' checkbox checked, so I click one button and Clean Master kills them all. Which is kind of fun.

I run both of them just to make sure things are as clean as possible. It really does help.
post #20 of 21
By the way, Chrome is only a very tiny bit better than Firefox, the native browser, or Dolphin. I must really love to post to go through all that in order to write something. It makes me appreciate my desktop very, very much.
post #21 of 21
Iobit self installed when I connected it to my PC, but apparently didn't get as far as giving me an icon to run it, it's just one of these background things. But I have Norton and it seems to clean things up a bit if I do a scan. I normally force close things if the memory gets down in the 100s. Force closing things doesn't significantly improve my Epic success with the Big Sky, or now my own Whitefish, pages.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: The Bug Report
EpicSki › The Barking Bear Forums › EpicSki Feedback/Tech Talk › The Bug Report ›  Android - threads with lots of photos essentially unusable