Foliovision › Forums › FV Player › Bug Reports › Video does not run on Samsung default mobile browser
-
-
Hello Davide,
please post your mobile browser user agent, you can find it here: https://www.whatsmyua.info/
We mainly need the “Chrome/70.0.3538.110” part of it and the Android version. But is that GT-I9060i which uses Android 4.4.4?
Please also let us know what video hosting are you using and if the situation improves if you disable the video ads.
Thanks,
MartinHello Martin,
the device in which we test our pages (with Chrome it runs, with default browser not) uses Android 4.4.4
I needed to use another service for retrieve the user agent, due the fact SSL/TLS version is outdated:
Mozilla/5.0 (Linux; U; Android 4.4.4; en-us; GT-I9060I Build/KTU84P) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Mobile Safari/534.30
We are using VIMEO as video hosting.
Samsung GT-I9060I (Galaxy Grand Neo)I did disable pre-roll and post-roll ADS on this video: (if possible please don’t publish this URL for SEO reasons)
My very best
Hello Davide,
so there is no information about SafariBrowser nor Chrome in the user agent string? Here’s what I have on my Samsung X-Cover 3, which was upgraded from Android 4.4.4 to 5.1.1:
Mozilla/5.0 (Linux; Android 5.1.1; SAMSUNG SM-G388F Build/LMY48B) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/3.3 Chrome/38.0.2125.102 Mobile Safari/537.36
And it plays, it uses the HLS stream.
Thanks,
MartinHello Davide,
I found an issue when using the built-in browser on my Samsung with Android 5.1.1 on https://foliovision.com/player/demos/roll-custom-video -> scroll down to the “VIMEO VIDEO WITH ANOTHER VIMEO VIDEO IN PRE-ROLL” video. I see that the video doesn’t play after the ad. I will check it out in depth.
Thanks,
MartinHello Davide,
I’m having no issues with Samsung J5 (2017) which is Android 7.0. The user agent also says SamsungBrowser/6.2 and Chrome/56.
But I’ll fix it for my older Samsung phone and I bet that will help with Samsung S7. I tried S7 now using an online phone testing player where it reports Android 6.0.1, SamsungBrowser/6.4 and Chrome/56 in user agent string and it worked fine though.
Thanks,
MartinHello Davide,
seems like the only safe option is to let these old Samsung browsers use MP4 files. My Android 5.1.1 which is SamsungBrowser/3.3 Chrome/38 just won’t let me initialize MPEG-DASH nor HLS.js properly.
Practically speaking using MP4 means that there are less CDN servers with the video, so in some part of the world it might be slower to load. We had reports of such issues in Asia when using MP4.
Thanks,
MartinHello Davide,
the MP4 solution is not perfect (sometimes a bit less reliable in Asia), but it works as only a fraction of viewers will get these MP4 files.
So let me release a new FV Player Pro version which will address this.
FV Player also includes a warning which popups up above the video if there are playback issues. It suggests the users to use a modern browser on their phone like Chrome or Firefox. This was not appearing on your mobile and now I see why, I prepared a fix for that too.
Thanks,
MartinHello Davide,
FV Player Pro 7.3.2.727.beta is out and it fixes these issues – it uses MP4 for these old Samsung Android phones which use the built-in browser. To get the bet updates, you need to first switch to beta like this: https://foliovision.com/player/basic-setup/switching-fv-player-pro-to-beta
The fix for the Samsung browser deprecation messages will be in the next FV Player release.
Thanks,
MartinHello Martin,
we did upgrade and use the Beta branch, through the select input field.https://…/wp-admin/admin.php?page=fv_player (please hide the URL) returns a not complete page, with no PHP errors (not founds in any log).
May you help us please? I could give you our credentials, if needed to whatch yourselves.
Regards
Hello Davide,
I’m sorry to hear about such issue. Do you mean that the settings boxes didn’t properly show up, or was it just plain white? We haven’t found any issue with this new version and there were barely any PHP changes since the last version.
Could you please try again and double check you are looking at the right place for the error logs? Perhaps using WP_DEBUG or WP_DEBUG_LOG in your wp-config.php would help? Here’s how if you have some PHP experience: https://codex.wordpress.org/WP_DEBUG
Thanks,
Martin