summaryrefslogtreecommitdiff
path: root/overlay-lineage
diff options
context:
space:
mode:
Diffstat (limited to 'overlay-lineage')
-rw-r--r--overlay-lineage/frameworks/base/core/res/res/values/config.xml48
1 files changed, 0 insertions, 48 deletions
diff --git a/overlay-lineage/frameworks/base/core/res/res/values/config.xml b/overlay-lineage/frameworks/base/core/res/res/values/config.xml
index 19a82eb..f2f6393 100644
--- a/overlay-lineage/frameworks/base/core/res/res/values/config.xml
+++ b/overlay-lineage/frameworks/base/core/res/res/values/config.xml
@@ -19,52 +19,4 @@
<resources xmlns:xliff="urn:oasis:names:tc:xliff:document:1.2">
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveNotificationLed">true</bool>
-
- <!-- Whether WiFi display is supported by this device.
- There are many prerequisites for this feature to work correctly.
- Here are a few of them:
- * The WiFi radio must support WiFi P2P.
- * The WiFi radio must support concurrent connections to the WiFi display and
- to an access point.
- * The Audio Flinger audio_policy.conf file must specify a rule for the "r_submix"
- remote submix module. This module is used to record and stream system
- audio output to the WiFi display encoder in the media server.
- * The remote submix module "audio.r_submix.default" must be installed on the device.
- * The device must be provisioned with HDCP keys (for protected content).
- -->
- <bool name="config_enableWifiDisplay">true</bool>
-
- <!-- Indicate whether closing the lid causes the device to go to sleep and opening
- it causes the device to wake up.
- The default is false. -->
- <bool name="config_lidControlsSleep">true</bool>
-
- <!-- Whether device supports double tap to wake -->
- <bool name="config_supportDoubleTapWake">true</bool>
-
- <!-- If true, the screen can be rotated via the accelerometer in all 4
- rotations as the default behavior. -->
- <bool name="config_allowAllRotations">true</bool>
-
- <!-- Default list of files pinned by the Pinner Service -->
- <string-array translatable="false" name="config_defaultPinnerServiceFiles">
- <item>"/system/framework/arm64/boot-framework.oat"</item>
- <item>"/system/framework/framework.jar"</item>
- <item>"/system/framework/oat/arm64/services.odex"</item>
- <item>"/system/framework/services.jar"</item>
- <item>"/system/framework/arm64/boot.oat"</item>
- <item>"/system/framework/arm64/boot-core-libart.oat"</item>
- <item>"/apex/com.android.runtime/javalib/core-oj.jar"</item>
- <item>"/apex/com.android.runtime/javalib/core-libart.jar"</item>
- <item>"/apex/com.android.media/javalib/updatable-media.jar"</item>
- <item>"/product/priv-app/SystemUI/SystemUI.apk"</item>
- <item>"/product/priv-app/SystemUI/oat/arm64/SystemUI.odex"</item>
- <item>"/system/lib64/libsurfaceflinger.so"</item>
- </string-array>
-
- <!-- True if camera app should be pinned via Pinner Service -->
- <bool name="config_pinnerCameraApp">true</bool>
-
- <!-- Should the pinner service pin the Home application? -->
- <bool name="config_pinnerHomeApp">true</bool>
</resources>