HonYa_fd

Figured it out.... adb shell am start -a android.intent.action.VIEW -t video/mp4 -d content://com.android.externalstorage.documents/document/primary%3AMovies%2Fxxxxx.mp4 takes couple of seconds after the app is started to start the video (my video has 4 and 8gb).... @chengnay

yes it the same response...which is weird, becaue it starts the player, but it does not load the file (nor it says, that the file does not exits)... the problem is, why in the response is empty path to the file the proper response should look like this: Starting: Intent { act=android.intent.action.VIEW dat=file:///storage/emulated/0/Movies/WORLD.mp4 typ=video/mp4 }

did not run the Focus ROM on emulator (will try) i am trying to start the video on Focus what is the reason, when i sent over command line adb shell am start -a android.intent.action.VIEW -t video/mp4 -d file:///storage/emulated/0/Movies/WORLD.mp4 i get response: Starting: Intent { act=android.intent.action.VIEW dat=file: typ=video/mp4 } what should i do differently....the file is there

the file path itself does not matter - if will fail with the program loading the movie.... i have like 5 android emulators, it works in all of them (mainly using the Android Studio) apparently the Focus does not translate the path in the sent adb command to Starting intent...the file there is missing.....what is the correct way than, how to set the file path, so Focus takes it over and works with it?... how can the adb command look like, if it needs to look different?

The warning is because the player is already started - that is ok my question is.... why is dat=file: empty....if i try that command on an android emulator it adds the file path in that.... dat=file:///storage/emulated/0/Movie/WORLD.mp4 and than it says in the emulator after it launches the video player, that such file is not existing

the file path was taken from Focus "viveport video player" where it is shown as /storage/emulated/0/Movies/ through adb command "ls" it as well listed in /sdcard/Movies/ (tryed this path as well) the files are called ALBA.mp4 and WORLD.mp4 those are 360 videos files are stored directly in the Focus (no ext sdcard), if you try to play them through the Focus via FileBrowser or the VIVEPort video - it works the pc app generates exactly the same command as i try through the command line "adb shell am start -a android.intent.action.VIEW -t video/mp4 -d file:///storage/emulated/0/Movies/WORLD.mp4" when i send this command through the command line, next line i get is: Starting: Intent { act=android.intent.action.VIEW dat=file: typ=video/mp4 } and in Focus, the video player starts, with no menu - looks like it is waiting for the file

i have the device fully connected, i can ping it, it is listed in "adb devices" without unathorised.....over cable or over wi-fi, the same connection to device

Hi. i am trying to run a server app over wifi to start video on couple of Focuses at the same time. i have adb connection with no problem. when sending this, i get empty response with "dat=file"" [192.168.99.145:5555] sending command: shell am start -a android.intent.action.VIEW -t video/mp4 -d file:///storage/emulated/0/Movies/WORLD.mp4 [192.168.99.145:5555] Starting: Intent { act=android.intent.action.VIEW dat=file: typ=video/mp4 } tryed content, " , ' ,....did not help tryed it over USB cable as well. Focus reacts to any adb command properly and the connection is working. In fact, it starts the vive video player, as it should...but the enviroment is just empty....only the background is shown....looks like the path is totaly wrong...tryed different variants, no success.... thanks for any help