XR Targets on Pixel 2017: Do not boot into VR directly

The flag will be set to false by default for test automation. As we
don’t have VR power manager ported to Android mainline yet, XR targets
with “ro.boot.vr=1” drains the battery fairly quickly. As a
workaround, we will use “ro.boot.vr=0” as the default value configure
and then manually override it during manual QA or development.

Bug: 129712284
Test: Build system
Change-Id: I2a4b8fdeb8a38a17f6b172c51fe2b29af5f5c8cc
This commit is contained in:
Jiwen 'Steve' Cai
2019-04-24 18:21:58 -07:00
parent 9bb671b847
commit f3066e68b7

View File

@@ -21,8 +21,10 @@
import /vendor/etc/init/hw/init.${ro.hardware}.common.rc
on init
# Boot into VR.
setprop ro.boot.vr 1
# Temporarily stop booting into VR directly due to battery drain.
# TODO(b/131327495): Re-enable this once VrHeadsetPowerPolicyService or its
# equivalent lands in Android master.
setprop ro.boot.vr 0
# Setup cpusets used by the VR services.
mkdir /dev/cpuset/kernel 0750 root system