summaryrefslogtreecommitdiffstats
path: root/overlay/frameworks
diff options
context:
space:
mode:
authorJustArchi <JustArchi@JustArchi.net>2015-05-30 15:17:36 +0200
committerforkbomb <keepcalm444@gmail.com>2015-11-25 08:07:32 +1100
commit90b505f2d785665ead0b4d5df1a0e1761ab7eae1 (patch)
tree457047af201e34b079f43da68e36992428a8511e /overlay/frameworks
parent549a1c6690b905748645107c1a1099761849c8e9 (diff)
downloaddevice_samsung_i9300-90b505f2d785665ead0b4d5df1a0e1761ab7eae1.zip
device_samsung_i9300-90b505f2d785665ead0b4d5df1a0e1761ab7eae1.tar.gz
device_samsung_i9300-90b505f2d785665ead0b4d5df1a0e1761ab7eae1.tar.bz2
i9300: Overlay bringup
Change-Id: Ica5b5c3035c6e5ff2756564fa3d894ba8a6d24bd
Diffstat (limited to 'overlay/frameworks')
-rw-r--r--overlay/frameworks/base/core/res/res/values/config.xml91
-rw-r--r--overlay/frameworks/base/packages/SystemUI/res/values/config.xml6
2 files changed, 93 insertions, 4 deletions
diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index e0fabe0..7d7cfc7 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -134,6 +134,48 @@
<item>0</item>
</integer-array>
+ <!-- Screen brightness when dozing. -->
+ <integer name="config_screenBrightnessDoze">20</integer>
+
+ <!-- Dream of notifications -->
+ <string name="config_dozeComponent">com.android.systemui/com.android.systemui.doze.DozeService</string>
+
+ <!-- If true, the doze component is not started until after the screen has been
+ turned off and the screen off animation has been performed. -->
+ <bool name="config_dozeAfterScreenOff">true</bool>
+
+ <!-- Power Management: Specifies whether to decouple the interactive state of the
+ device from the display on/off state.
+
+ When false, setInteractive(..., true) will be called before the display is turned on
+ and setInteractive(..., false) will be called after the display is turned off.
+ This mode provides best compatibility for devices that expect the interactive
+ state to be tied to the display state.
+
+ When true, setInteractive(...) will be called independently of whether the display
+ is being turned on or off. This mode enables the power manager to reduce
+ clocks and disable the touch controller while the display is on.
+
+ This resource should be set to "true" when a doze component has been specified
+ to maximize power savings but not all devices support it.
+
+ Refer to power.h for details.
+ -->
+ <bool name="config_powerDecoupleInteractiveModeFromDisplay">true</bool>
+
+ <!-- Specifies whether the dreams feature should be supported.
+ When true, the system will allow the user to configure dreams (screensavers)
+ to launch when a user activity timeout occurs or the system is told to nap.
+ When false, the dreams feature will be disabled (this does not affect dozing).
+
+ Consider setting this resource to false or disabling dreams by default when a
+ doze component is specified below since dreaming will supercede dozing and
+ will prevent the system from entering a low power state until the dream ends. -->
+ <bool name="config_dreamsSupported">true</bool>
+
+ <!-- If supported, are dreams enabled? (by default) -->
+ <bool name="config_dreamsEnabledByDefault">false</bool>
+
<!-- An Array of "[Connection name],[ConnectivityManager.TYPE_xxxx],
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
@@ -185,10 +227,15 @@
<!-- Is the notification LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveNotificationLed">true</bool>
+ <!-- Does the notification LED support multiple colors?
+ Used to decide if the user can change the colors -->
+ <bool name="config_multiColorNotificationLed">true</bool>
+
<!-- Is the battery LED intrusive? Used to decide if there should be a disable option -->
<bool name="config_intrusiveBatteryLed">true</bool>
- <!-- Does the battery LED support multiple colors? Used to decide if the user can change the colors -->
+ <!-- Does the battery LED support multiple colors?
+ Used to decide if the user can change the colors -->
<bool name="config_multiColorBatteryLed">true</bool>
<!-- Default color for notification LED is white. -->
@@ -207,9 +254,9 @@
<!--bool name="config_disableHomeUnlockSetting">false</bool-->
<!-- Workaround for devices with broken keyboards -->
- <bool name="config_forceDisableHardwareKeyboard">true</bool>
+ <!--bool name="config_forceDisableHardwareKeyboard">true</bool-->
- <!-- Hardware 'face' keys present on the device, stored as a bit field.
+ <!-- Hardware keys present on the device, stored as a bit field.
This integer should equal the sum of the corresponding value for each
of the following keys present:
1 - Home
@@ -217,11 +264,47 @@
4 - Menu
8 - Assistant (search)
16 - App switch
+ 32 - Camera
+ 64 - Volume rocker
For example, a device with Home, Back and Menu keys would set this
config to 7. -->
- <integer name="config_deviceHardwareKeys">7</integer>
+ <integer name="config_deviceHardwareKeys">71</integer>
+
+ <!-- Hardware keys present on the device with the ability to wake, stored as a bit field.
+ This integer should equal the sum of the corresponding value for each
+ of the following keys present:
+ 1 - Home
+ 2 - Back
+ 4 - Menu
+ 8 - Assistant (search)
+ 16 - App switch
+ 32 - Camera
+ 64 - Volume rocker
+ For example, a device with Home, Back and Menu keys would set this
+ config to 7. -->
+ <integer name="config_deviceHardwareWakeKeys">65</integer>
<!-- Boolean to enable stk functionality on Samsung phones -->
<bool name="config_samsung_stk">true</bool>
+ <!-- Maximum number of supported users -->
+ <integer name="config_multiuserMaximumUsers">4</integer>
+
+ <!-- Whether UI for multi user should be shown -->
+ <bool name="config_enableMultiUserUI">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>
+
</resources>
diff --git a/overlay/frameworks/base/packages/SystemUI/res/values/config.xml b/overlay/frameworks/base/packages/SystemUI/res/values/config.xml
index 88851f7..717384b 100644
--- a/overlay/frameworks/base/packages/SystemUI/res/values/config.xml
+++ b/overlay/frameworks/base/packages/SystemUI/res/values/config.xml
@@ -22,5 +22,11 @@
<resources>
<!-- Control whether status bar should distinguish HSPA data icon form UMTS data icon on devices -->
<bool name="config_hspa_data_distinguishable">true</bool>
+
+ <!-- Doze: does this device support STATE_DOZE and STATE_DOZE_SUSPEND? -->
+ <bool name="doze_display_state_supported">true</bool>
+
+ <!-- Doze: should the pickup sensor be used as a pulse signal? -->
+ <bool name="doze_pulse_on_pick_up">false</bool>
</resources>