FAQ

[mysterion]

Q: Black screen after selecting video on Google Chrome

Chrome can play videos with resolution lower or equal to your mobile screen resolution.
Example: Playing 4k video(3840 x 2160) on a 2400x1080 device will show a black screen.
Make sure the video codec and resolution is supported by your phone/chrome, goto chrome://gpu -> Video Acceleration Information to be sure. thanks @shatsky

Q: Cant access the links on mobile

Fix 1: make sure the application executable is whitelisted in firewall

Q: Client sent an HTTP request to an HTTPS server on mobile device

Make sure you follow these steps:-

1. put https explicitly into the browser address bar
   
2. tap advanced
   
3. tap proceed to ...
   
4. tap VR button
   
5. allow site to access VR device
   
6. [CARDBOARD ONLY] make sure the white line should be in-between the left eye view and right eye view. If its not, put your phone into Landscape mode/orientation, then tap the VR button.
   

[shatsky]

I believe that "Chrome can play videos with resolution lower or equal to your mobile screen resolution" is incorrect. On Pixel 6 with 2400x1080 display aframe-vr-player on Chrome can certainly play 3840x2160 videos, but attempt to play higher resolution videos results in default background (not black screen). I found that "chrome://gpu" shows supported accelerated video decoding formats with resolution ranges under "Video Acceleration Information", and on Pixel 6 resolution limit is exactly 3840x2160 for most of them (though it can decode 8bit HEVC in 4096x2176). However if opening video file directly, Chrome is able to play even 8k (though not without freezes). I guess there is a bug or shortcoming in underlying pipeline which prevents using software-decoded video frame as texture.

Testing note: to open local file in Chrome on Android directly, copy local "file://" URL to clipboard, activate Chrome URL input and choose "Text you copied" action (if you enter such URL into the input, Chrome will only provide options to search for it via search engine, possibly another bug in current Chrome).

[mysterion]

tested it a few months ago on few 4k videos, must be an 'unsupported codec issue' and not resolution problem. i'll updated the faq, thanks.