Forum Replies Created
-
-
Hi Martin,
Yes, it seems that it was because of another issue, though I have no idea what.
It may have been because of an html5.js file in the WP theme that needed updating or even just the phone itself needed re-booting, which doesn’t make any sense to me at all, but now the videos are playing again in the Android stock browser, and Google Chrome, although still with the original glitch.I look forward to any Flowplayer Core update to resolve the original problem, if they do make one. This version of Samsung Android is still quite widely used by a lot of people!
Thanks,
Nathan.
It’s a pleasure. But is there going to be any fix for the problem? It has got worse now since the latest updates, on Android phone AWS hosted videos no longer play at all. After a few taps it just skips to the end of the video and stays stuck if you replay it. Self-hosted videos still play, but the same problem as before. I haven’t checked it on other mobiles or iphone yet. Is this a new bug or glitch?
Nathan.
Hello,
No, I’m afraid it took 3 taps to play the video (In the Stock Browser) !
Thanks,
Nathan.
Hi,
In the Stock Samsung browser this URL has the same original problem, blank grey screen, which you have to tap 2 or 3 times to get to play.
Thanks,
Nathan.
Yes, 2 and 3 both work in the Google Chrome browser on my Samsung phone.
Except No.3 still has the blank white background when it first loads up with just a play button, other than that they both work in the google chrome browser.Thanks,
Nathan.
Also, I forget to say that I did originally try playing my site’s videos on both cellular network and Wifi connection and they were the same with the same problem.
As said, the video on the latest URL you sent me seems to work perfectly!
Thanks,
Nathan.
Hi Martin,
On this URL (Flowplayer 5?), it works fine! One tap, fully responsive, play button, everything.
Just so you know, yes, I have been using the stock browser on all the tests, and have been using cellular network, not Wifi connection.
Thanks again,
Nathan.
Hi,
Well, they all behave completely differently.
No.1 seems to work the best, though there is no play button in the centre of the screen, just in the player controls below, and it does not appear to be fully mobile responsive.
No.2 is basically the same problem as before, you have to tap twice to get it to play. it does however seem to be responsive,
No.3 is exactly the same as No.2, except that when you first load the page there is no video player, just a single play button against a blank white background.
So of the three I’d say No.1 is almost there.
Thanks,
Nathan.
Hi,
Exactly the same I’m afraid. I put in the url on my android mobile and it was the same problem as before.
I should ask at this point whether this is something that only happens on my Android Version (Samsung I9300 Galaxy S III, Android OS, v 4.3) or has it happened on any other too?
It is unfortunately a phone that many people use.Thanks,
Nathan.
Hello,
Just touching base, did you have any chance to check it out on your device yet?
Thanks,
Nathan.
Hello,
it is a Samsung I9300 Galaxy S III, Android OS, v 4.3, Jelly Bean
Kernel Version 3.0.31-2168382
Older, I guess.
Thanks,
Nathan.
Hi,
I am using Mp4. I noticed the problem does not happen on Apple devices like iphone, but only on Android phone, don’t know about Android tablets.I visited http://whatsmyuseragent.com/ on my Android phone and could not get the entire string because, guess what, their site is not mobile responsive. At least not on my android device. The best I could make out, with some characters missing, was:
Mozilla/5.0(Linux;U;Android 4.3;en-gb;GT-i9300Build/Jss15J)App53430(KHTML.LikeGecko) Version/4.0Mobilesafari/53430
That is all I could make out.
An URL you could check on my site is: http://www.reviews4u.com/is-there-a-need-for-family-tree-software/
As said, i am using MP4’s , incliuding on the above URL.
Thanks,
Nathan.
Hi Martin,
I did get it working in the end. It was just the bucket name in the settings, which had a prefix that was not part of the name, that stopped it from connecting.
Thanks for getting back,
Nate.
