Fix imcompatible app warning when insert to DayDream headset

chrome/android/chrome_public_apk_tmpl.gni

Index: chrome/android/chrome_public_apk_tmpl.gni
diff --git a/chrome/android/chrome_public_apk_tmpl.gni b/chrome/android/chrome_public_apk_tmpl.gni
index c6f48fc4af73c02c014fbfbb16ae358af5cfca41..57492b242385fabd8aaf16eddffeccfb3a181a5a 100644
--- a/chrome/android/chrome_public_apk_tmpl.gni
+++ b/chrome/android/chrome_public_apk_tmpl.gni
@@ -31,6 +31,7 @@ default_chrome_public_jinja_variables = [
   "channel=$android_channel",
   "enable_leakcanary=$enable_leakcanary",
   "enable_vr_shell=$enable_vr_shell",
+  "enable_webvr=$enable_webvr",

[Maria, 2016/10/26 20:10:27]

What's the difference between enable_vr_shell and enable_webvr?

[bshe, 2016/10/26 20:51:46]

enable_webvr will enable WebVR related web API and code.
enable_vr_shell will enable VrShell system UI and functionality. We also calL
VrShell ChromeVR. Mostly, we refer to our VR browser system UI controls(such as
navigation button)  and pages(such as bookmark).
Hope I explained them clearly, if not, feel free to ping me directly. And we are
probably going to ship WebVR first and then ChromeVR.

They share a lot of VR related code (such as code under vr_shell folder), which
makes them confusing. But we are hoping to remove these flags soon.

 ]
 
 template("chrome_public_apk_tmpl") {