Topic: Auto play not working on some mobile devices

I have 2 websites that run an auto play slideshow embedded in their home pages. They work fine on a computer and on an iPhone3, but won't auto play/play on my Android device at all.

I don't get what the problem is. What do I need to do to get them to work on all mobile devices?

Here's the code in my widget:
<!--START JUICEBOX EMBED-->
<script src="http://mywebsites.com/folderinfo/slideshowfile/jbcore/juicebox.js"></script>
<script>
  new juicebox({
      containerId : 'juicebox-container',
      baseUrl : 'http://mywebsites.com/folderinfo/slideshowfile',
  });
  </script>
<div id="juicebox-container"></div>
<!--END JUICEBOX EMBED-->

Here are my splash settings for both pages:
Show Splash page: AUTO
Splash page button text: View Gallery
Splash Title: (blank)
Splash image Url: (blank)
Splash Show Image Count: (unchecked)

Here are the web pages with auto play slideshows:
http://centerlinegraphicdesign.com/Home.html
http://arabian-training.com/Home.html

Re: Auto play not working on some mobile devices

I notice that your galleries do not display at all on IE10 (though they do display in Firefox, Chrome, Safari and Mobile Safari).
Try viewing the galleries on their own pages (rather than embedded in your main pages) to see if this makes a difference:
http://centerlinegraphicdesign.com/Home … arkup.html
http://arabian-training.com/Home_files/ … arkup.html

The galleries themselves do display OK in IE10 when I view them on their own so they may also display OK on your Android device.
This suggests that there is something that both IE10 and your Android browser do not like about the way the galleries are being embedded using the iWeb widget.
It may have something to do with the fact that your main pages use the XHTML 1.0 Transitional Doctype Declaration (with a missing xmlns attribute for the 'html' element) whereas your gallery pages (used by the iWeb widget within your main page) use the HTML 4.01 Transitional Doctype Declaration.
Try matching the Doctype Declarations for all your pages to see if this helps (and, if using the XHTML 1.0 Transitional Doctype Declaration, fix the missing missing xmlns attribute for the 'html' element on your main pages).