Open weller0 opened 10 months ago
Is there any way to test that in a linux machine?
The backtrace looks weird because it does correspond to the loading of the native code, i.e., Gecko engine in this case, but in your report you're already playing a video in Wolvic. Are you sure that's the right backtrace?
Just to confirm that is not a limitation in the underlying Android system, are you able to reproduce it on the Pico browser or the Meta browser?
quest browser.log wolvic.log Uploaded logs from Quest browser and Wolvic. Logged the black screen from opening the browser to entering VR. It may be that this process crashes causing no screen to appear 12-04 10:40:03.313 25082 25082 F DEBUG : Cmdline: com.igalia.wolvic:media
I don't have a Linux environment to test here(I only have WSL2). But it is stably reproducing. PICO optimizes many logs, so we use Quest to test and capture logs
Thanks for the information. We're superbusy now preparing a new release, but will take a quick look after that to check what's going on
Configuration
Wolvic version: v1.5.1 Wolvic build ID: 220
Hardware: PICO 4 Quest 2 also has this issue.
Steps to Reproduce
1.Use ue pixel-streaming(https://docs.unrealengine.com/5.2/en-US/experimental-pixel-streaming-features/). I have a packaged version(). 2.After decompressing Windows. rar, run the PC side service 3.Enter the Wolvic browser and enter the PC address, for example:https://192.268.1.10 4.Entering VR mode
Current Behavior
Currently in black screen state
Expected Behavior
It can display normally
Possible Solution
By checking the settings, it was found that the encoding option is empty, while there is an encoder in the PICO browser
Context
Error Logs and Stack Traces