From cb316b52d2abd26acf827317924d58b1c9bcec84 Mon Sep 17 00:00:00 2001
From: Mathias Agopian <mathias@google.com>
Date: Mon, 22 Aug 2011 18:40:10 -0700
Subject: Pull some configurations over from Crespo.

Most important is of course config_animateScreenLights.

Change-Id: I3cf053443c71af7ef74484d0a86f30703448c45e
---
 overlay/frameworks/base/core/res/res/values/config.xml | 12 ++++++++++++
 1 file changed, 12 insertions(+)

(limited to 'overlay/frameworks')

diff --git a/overlay/frameworks/base/core/res/res/values/config.xml b/overlay/frameworks/base/core/res/res/values/config.xml
index abdf914..c00f1e2 100644
--- a/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/overlay/frameworks/base/core/res/res/values/config.xml
@@ -21,6 +21,18 @@
      for different hardware and product builds. -->
 <resources>
 
+    <!-- Our amoled doesn't animate well. -->
+    <bool name="config_animateScreenLights">false</bool>
+
+    <integer name="config_deskDockKeepsScreenOn">0</integer>
+    <integer name="config_carDockKeepsScreenOn">1</integer>
+
+    <!-- Component name of the service providing network location support. -->
+    <string name="config_networkLocationProvider">com.google.android.location.NetworkLocationProvider</string>
+
+    <!-- Component name of the service providing geocoder API support. -->
+    <string name="config_geocodeProvider">com.google.android.location.GeocodeProvider</string>
+
     <!-- Flag indicating whether we should enable the automatic brightness in Settings.
          config_hardware_automatic_brightness_available is not set, so we will use software implementation -->
     <bool name="config_automatic_brightness_available">true</bool>
-- 
cgit v1.1