We just noticed that our Vimeo videos do not open in full screen anymore when the play button is tapped on Android devices and there is no way to make the video full screen either. Full screen does still work in iOS though. We even went back and tested an older version of the Cordova based app and those no longer opened in full screen so it seems to be an issue with Vimeo.
I've tried doing some searching via StackOverflow and Google but have not been able to find anything that has helped. Has anyone else had this issue? None of our code has changed when it comes to videos and this used to work. Like I said previously, it still works on iOS. I would say it's an Android issue however, it doesn't work on an older Android OS anymore either with an older version of our app so it seems that it's a Vimeo issue.
Thank you!
Related
I've built an html5-video webpage that uses video-js and its chromecast-plugin. When I use the resulting cast button on video-js player's control-bar, when running on Chrome-browser on Android, it fails to completely transfer over to the TV's screen. The failing symptom is that only a large blue cast-icon is visible in the center of the TV screen. It fails on Android, each and every time I try it. (My Android is version 7.1.1, on a Google Nexus-9 tablet.)
And when it fails to completely cast over to the TV, the cast-icon-button on the video-js control-bar turns red, which I assume means that the chromecast-plugin 'knows' that it failed. (The videojs-chromecast-plugin is version 2.0.8)
My chromecast device is a 2nd-generation chromecast-dongle from Google.
[ From a PC-platform, the video-js chromecast-plugin's cast-button works perfectly every time. That PC-platform is Windows-10, using the newest version of Chrome browser (Version 63.0.3239.132 (Official Build) (64-bit)) ]
So, could someone with Android and a chromecast device please test my
webpage and report whether it works or whether they too fail with a large
blue cast-icon image in center of their TV-screen.
(Note: I've googled for symptom of the blue cast-icon in center of TV, and
find various reports of this exact symptom, on various platforms. But
none of those problem posts ever end with a solution, so I've concluded
that this is a known open issue.)
My webpage that is failing is located here:
https://weasel.firmfriends.us/HTMLVideoFromCloud/
[ You can see the page's html and javascript via "view page source"
in the browser (right-click anywhere on the page, outside of the
video-js viewer) ]
(EDIT#1) Ok, some extra clarification: The problem casting from Android happens ONLY when I use the cast-button at right-end of videojs-viewer's control bar.
But, I have found an alternative cast-button on Android, that CAN successfully cast my page to the TV. I don't recall exactly what I did to get this extra button to start appearing, but it will appear for a few seconds in the upper-left client-area of the video-js player window rendering my webpage. This 'workaround' doesn't completely solve my issue, because the goal is to get videojs-chromecast-plugin's cast-button to work. Also, other people viewing the page from Android may not know how to get that alternate cast-button.
(EDIT#2) I've tested now from two different tablets...both fail.
(1) Android version 7.1.1, on a Google Nexus-9 tablet
(2) Android version 5.1.1, on a Google Nexus-10 tablet
TIA...
I have built hybrid app with Sencha touch 2.3 and till recent it was working fine but i recently updated the Android System Webview via Play Store (i have moto g running android 5.0.1) and now i am encountering various bugs in UI as follows :
The selectfield picker does not work correctly now. It behaves randomly. The store bound to it has data but no items are displayed in the picker when it opens. At times items do get displayed but you cannot select the items at bottom because picker always resets the selection to the item at top.
Few screens show up blank initially when rendered for the first time. As soon as user touches the screen and moves a little bit the whole screen/view becomes visible.
Also there might be other things that might have broken after updating the webview which i might not have discovered but this a big issue as far as developing for android is concerned with sencha touch. The webview updates are now pushed Over the Air and hence many things may break in future.
I also confirmed the above bugs in older versions of android wherein the webview has not been updated and the above bugs do not show up in.
I am thinking of using crosswalk as the solution to the issues with the webview. Anyone with the same issues or any tips regarding a fix ?
I ran into a similar issue with my Sencha Touch app (almost nothing rendered). Here is the workaround I used which seems to work great:
http://trevorbrindle.com/chrome-43-broke-sencha/
Thanks #Ian. The link was tremendously helpful and it solved the issue for now. Sencha has not officially released a build with these fixes so the overrides are the only solution right now.
For anyone facing same issues here is one more link from the Sencha Forums where all the issues sencha frameworks are facing with Chrome 43 are stated and solved.
https://www.sencha.com/forum/announcement.php?f=92&a=58
I am also stuck with same issue and i found solution we should not update the chrome. Better download 42.0.2311.152_chrome64_installer which is offline exe for chrome.
I'm using the ImpactJS framework for work and I've tried what most of people did to get their games to work but with no luck, most recently I tried following the instructions from this thread: http://impactjs.com/forums/help/cocoonjs/page/1.
It seems whatever I do CocoonJS refuses to launch the Impact framework (I've tried with both a game and with just the framework alone but nothing happens), whenever I launch the game I get a black screen running at about 60 fps.
Again I'm just trying to get the framework itself working but even that seems impossible. Does anyone have any suggestions?
I'm pretty sure you have a javascript error (see console log), or maybe you have debug enabled on ImpactJS (debug requires DOM, not supported by CocoonJS)
I cannot add a web app to the home screen on the nexus 5, android 4.4
I've followed the instructions found at this link
https://developers.google.com/chrome/mobile/docs/installtohomescreen
You can test the problem with this app for example:
http://weight.aerotwist.com
After following the instructions, I get an homescreen icon, but tapping on it brings up a menu with the various browsers available instead of just opening the web app.
I've tested the same problem with a locally installed app and it gives the message "App isn't installed".
It looks like a bug. Can anyone confirm this? Does anyone know a workaround?
Thanks!
The cause of this problem is that in Android 4.4, WebView was changed as in previously it was based on Webkit browser, and now its based on Chromium browser.
You can follow this guide to help migrating your app to Android 4.4
I'm using an iframe to embed a youtube video in an app for android/iOS developed using jQuery mobile and phonegap build.
Testing it on my browser works fine.
On my device (android) I see the video thumbnail, but when I click on it the screen goes black, I see the controls (play, forward and backward) and the video doesn't start.
On some other video I see the loading "circle" and after that the YT related videos.
I'm checking that the video is avaible for mobile
http://gdata.youtube.com/feeds/videos?alt=json&format=1,6&fields=entry[link/#rel='http://gdata.youtube.com/schemas/2007%23mobile']&max-result=10&category=Music&q="+mySong
Any help would be really appreciated.
This tutorial seems to work :
http://eisabainyo.net/weblog/2012/01/24/embed-a-youtube-video-iframe-in-phonegap-app/
Pay attention to this step:
Change/add the following values in PhoneGap.plist file of your app.
MediaPlaybackRequiresUserAction: NO
AllowInlineMediaPlayback: YES
OpenAllWhitelistURLsInWebView: YES
ExternalHosts
*.youtube.com
*.ytimg.com
The problem seemed to be related with the android version: on 4.0 the iframe/html5 version worked fine. The problem was on android 2.3.
I used a jqm plugin as a workaround in 2.3