Do we only want to do this on our FYI bot?

Running on everything will be easier/cleaner (just need to remove some @Restriction annotations). FYI-only isn't exactly difficult, either, but will require a little more work than that.

I think we only want to run it on FYI bot, since we don't officially support it, we don't want to block others if it is failed. FYI bot is better for this use case.

My Nexus 5X doesn't seem to be able to enter the VR browser. The call to forceEnterVr() isn't doing anything, which seems to stem from this check https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/vr_shell/VrShellDelegate.java?q=vrshelldelegate&dr=CSs&l=455.

Are we sure that the VR browser works on KLM devices at all?

That is what I heard from David in our last sync up meeting, you can confirm with David.

I would be surprised if it was.

In practice no non-dev user (without root on their phone) will be able to use VR browser without an actual daydream headset (and of course a daydream ready device).  The flag required to turn on VR entry from the menu (and do pretty much what the tests would do by calling forceEnterVr) can only be set from the command line (which requires root).

I think it would be useful to enable the browser on all platforms (the gaze cursor works fine for me), but until we have a firm commitment to support it on all those platforms it probably doesn't make sense to try and test it when it won't work for any actual user.

FWIW I still think a cardboard VR browser test (using daydream ready devices and OS to get past the check mentioned in comment #3, but setting the device to cardboard) would still be worthwhile (as developers probably are using it instead of always going through the daydream don flow and pairing controllers), but that's slightly different from what this issue proposes.

I'm going to go ahead and close this as a wontfix since the VR browser is NOT supported on KLM. I think we got this confused with VR browser support for Cardboard on Daydream-ready devices, which is covered in  Issue 734757 .