> Hi hmin, I'm currently in the process of moving over from CJS to Crosswalk, and I came across this issue. What is the resolution process for this bug? Is this something that you guys deal with on your side, or is WebGL just never going to work with Crosswalk on a Galaxy S3 due to a driver bug that's beyond your control?
> I understand that blacklist ignoring is something that's coming up soon in Intel XDK. Will it be safe to simply ignore blacklistsed GPUs to ensure WebGL works? I've been testing on my GS3 using Cocoon for some time now (with WebGL enabled), and it's always behaved itself fine.
GeometriX, currently Crosswalk disables WebGL internally by default for a buggy driver , which means WebGL would never works unless gpu blacklist is ignored .
If you want to ignore gpu blacklist by manual, from Crosswalk 6, it allows to add app-specific command line options by adding a new asset file to your apk. You can add <APP_DIR>/assets/xwalk-command-line into your apk with the following content:
and then rebuild your apk.
I would like to try this out but I don't know how. Where exactly in the process of exporting with Construct, importing into Intel XDK, building and installing the build do I do this? Do I have to modify the built APK file (because then I would have to resign it, right?) or can I do this BEFORE building with Intel XDK?
EDIT: I read the Crosswalk Documentation and tried out making a blank file named 'xwalk-command-line' containing the single line: 'xwalk --ignore-gpu-blacklist'. I copied this file to the root directory of the App (before compiling, the one containing index.html). I then built the App with Intel XDK and Crosswalk 6 (beta) enabled. This didn't work.
P.S.: I am doing all this because on my test device, a Galaxy S2, the GPU seems to be blacklisted and WebGL is disabled by default.