| /system/core/rootdir/etc/ |
| init.goldfish.rc | 9 # fake some battery state
10 setprop status.battery.state Slow
11 setprop status.battery.level 5
12 setprop status.battery.level_raw 50
13 setprop status.battery.level_scale 9
|
| /development/simulator/wrapsim/ |
| DevPower.c | 29 { "battery/batt_temp",
31 { "battery/batt_vol",
33 { "battery/capacity",
35 { "battery/health",
37 { "battery/present",
39 { "battery/status",
41 { "battery/technology",
129 * battery power manager is blowing up if we get an error other than
|
| /frameworks/base/core/java/android/os/ |
| BatteryManager.java | 38 * boolean indicating whether a battery is present.
44 * integer field containing the current battery level, from 0 to
51 * integer containing the maximum battery level.
58 * indicating the current battery state.
65 * source; 0 means it is on battery, other constants are different
72 * integer containing the current battery voltage level.
78 * integer containing the current battery temperature.
84 * String describing the technology of the current battery.
|
| Power.java | 64 * Brightness value to use when battery is low
70 * Screen will stay dim if battery level is <= LOW_BATTERY_THRESHOLD
|
| /packages/apps/Settings/res/layout/ |
| battery_info.xml | 23 <!-- Battery Status -->
29 <!-- Battery Status -->
35 <!-- Battery Level -->
41 <!-- Battery Scale -->
47 <!-- Battery Health -->
53 <!-- Battery Voltage -->
59 <!-- Battery Temperature -->
65 <!-- Battery Technology -->
|
| /frameworks/base/docs/html/guide/topics/testing/ |
| what_to_test.jd | 50 <h4>Battery life</h4>
52 Mobile devices primarily run on battery power. A device has finite "battery budget", and when it
54 minimize battery usage, you need to test its battery performance, and you need to test the
55 methods that manage battery usage.
58 Techniques for minimizing battery usage were presented at the 2010 Google I/O conference in the
61 Coding for Life -- Battery Life, That Is</a>. This presentation describes the impact on battery
63 impacts. When you code your application to reduce battery usage, you also write th
[all...] |
| /frameworks/base/packages/SystemUI/res/values/ |
| strings.xml | 40 <!-- When the battery is low, this is displayed to the user in a dialog. The title of the low battery alert. -->
43 <!-- When the battery is low, this is displayed to the user in a dialog. The subtitle of the low battery alert. -->
44 <string name="battery_low_subtitle">The battery is getting low:</string>
46 <!-- A message that appears when the battery level is getting low in a dialog. This is appened to the subtitle of the low battery alert. -->
50 <!-- When the battery is low, this is the label of the button to go to the
51 power usage activity to find out what drained the battery. -->
52 <string name="battery_low_why">Battery use</string
[all...] |
| /development/apps/SpareParts/res/values/ |
| strings.xml | 25 <string name="title_battery_history">Battery history</string>
26 <string name="summary_battery_history">Summary of how battery has been used</string>
28 <string name="title_battery_information">Battery information</string>
29 <string name="summary_battery_information">Current battery status information</string>
|
| /frameworks/base/tests/BatteryWaster/ |
| AndroidManifest.xml | 7 <activity android:name="BatteryWaster" android:label="Battery Waster">
|
| /packages/apps/DeskClock/res/layout/ |
| desk_clock_battery.xml | 17 <!-- battery/charge status -->
18 <TextView android:id="@+id/battery" xmlns:android="http://schemas.android.com/apk/res/android"
|
| /device/samsung/crespo/ |
| init.herring.rc | 9 # fake some battery state
10 setprop status.battery.state Slow
11 setprop status.battery.level 5
12 setprop status.battery.level_raw 50
13 setprop status.battery.level_scale 9
|
| /device/samsung/crespo4g/ |
| init.herring.rc | 9 # fake some battery state
10 setprop status.battery.state Slow
11 setprop status.battery.level 5
12 setprop status.battery.level_raw 50
13 setprop status.battery.level_scale 9
|
| /frameworks/base/services/java/com/android/server/ |
| BatteryService.java | 50 * battery. When these values change this service broadcasts the new values
60 * <p>"health" - String, the current battery health.<br />
61 * <p>"present" - boolean, true if the battery is present<br />
65 * <p>"voltage" - int, current battery voltage in millivolts</p>
66 * <p>"temperature" - int, current battery temperature in tenths of
68 * <p>"technology" - String, the type of battery installed, e.g. "Li-ion"</p>
75 static final int BATTERY_SCALE = 100; // battery capacity is a percentage
139 // assume we are powered if battery state is unknown so the "stay on while plugged in" option will work.
144 // assume we are powered if battery state is unknown so
173 // returns battery level as a percentag
[all...] |
| /external/qemu/android/avd/ |
| hw-config-defs.h | 92 "hw.battery",
94 "Battery support",
95 "Whether the device can run on a battery.")
|
| hardware-properties.ini | 92 # Battery
93 name = hw.battery
96 abstract = Battery support
97 description = Whether the device can run on a battery.
|
| /frameworks/base/tests/BatteryWaster/res/values/ |
| strings.xml | 19 <string name="waste_away">Discharge my battery!</string>
|
| /prebuilt/linux-x86/toolchain/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/ |
| pmu.h | 3 * which controls battery charging and system power on PowerBook 3400
27 #define PMU_BATTERY_STATE 0x6b /* report battery state etc. */
28 #define PMU_SMART_BATTERY_STATE 0x6f /* report battery state (new way) */
51 #define PMU_POW_CHARGER 0x02 /* battery charger power */
59 #define PMU_INT_BATTERY 0x20 /* Battery state change */
|
| /frameworks/base/core/res/res/xml/ |
| power_profile.xml | 52 <!-- This is the battery capacity in mAh -->
53 <item name="battery.capacity">1000</item>
|
| /frameworks/base/packages/SystemUI/res/values-en-rGB/ |
| strings.xml | 28 <string name="battery_low_subtitle" msgid="7388781709819722764">"The battery is getting low:"</string>
30 <string name="battery_low_why" msgid="7279169609518386372">"Battery use"</string>
|
| /external/bluetooth/bluez/audio/ |
| telephony-ofono.c | 71 /* HAL battery namespace key values */
72 static int battchg_cur = -1; /* "battery.charge_level.current" */
73 static int battchg_last = -1; /* "battery.charge_level.last_full" */
74 static int battchg_design = -1; /* "battery.charge_level.design" */
922 DBG("telephony-ofono: battery.charge_level.last_full"
925 DBG("telephony-ofono: battery.charge_level.design"
928 DBG("telephony-ofono: battery.charge_level.current"
999 if (g_str_equal(name, "battery.charge_level.last_full"))
1001 else if (g_str_equal(name, "battery.charge_level.current"))
1003 else if (g_str_equal(name, "battery.charge_level.design")
[all...] |
| /external/qemu/hw/ |
| power_supply.h | 24 * For systems where the charger determines the maximum battery capacity
|
| /system/vold/ |
| NetlinkHandler.cpp | 59 } else if (!strcmp(subsys, "battery")) {
|
| /frameworks/base/docs/html/sdk/ |
| android-1.6-highlights.jd | 62 <img src="images/battery.png" class="screenshot" alt="" /><br/>
63 Battery Usage Indicator
105 <h3 id="Battery">Battery usage indicator</h3>
107 <p>A new battery usage screen lets users see which apps and services are consuming
108 battery power. If the user determines that a particular service or application is
109 using too much power, they can take action to save the battery by
|
| /frameworks/base/services/java/com/android/server/am/ |
| BatteryStatsService.java | 42 * battery life.
64 Slog.w("BatteryStats", "Writing battery stats before shutdown...");
81 * to reflect events that affect battery usage. You must lock the
91 //Slog.i("foo", "SENDING BATTERY INFO:");
428 pw.println("Battery stats reset.");
|
| /frameworks/base/docs/html/guide/topics/location/ |
| obtaining-user-location.jd | 12 <li>Obtaining user location can consume a lot of battery, so be careful how
30 <li><a href="#Adjusting">Adjusting the model to save battery and data exchange</a></li>
46 GPS is most accurate, it only works outdoors, it quickly consumes battery power, and doesn't return
49 works indoors and outdoors, responds faster, and uses less battery power. To obtain the user
63 and trust is a matter of trade-offs in accuracy, speed, and battery-efficiency.</p>
164 battery, getting user location is complicated. To overcome the obstacles of obtaining a good user
165 location while preserving battery power, you must define a consistent model that specifies how your
198 fixes can consume a lot of battery power, but short periods might not allow for sufficient
232 long time consumes a lot of battery power, so as soon as you have the information you need, you
317 <h3 id="Adjusting">Adjusting the model to save battery and data exchange</h3
[all...] |
