| /frameworks/base/docs/html/training/ |
| best-performance.jd | 8 and uses as little battery as possible.</p
|
| best-background.jd | 8 application's performance and minimize its drain on the battery.</p>
|
| /system/core/healthd/ |
| healthd.h | 28 // suspend, or in suspend and connected to a charger (to watch for battery
33 // not connected to a charger (to watch for a battery drained to zero
38 // to use for the associated battery parameters. healthd will search for
42 // batteryHealthPath: battery health (POWER_SUPPLY_PROP_HEALTH)
43 // batteryPresentPath: battery present (POWER_SUPPLY_PROP_PRESENT)
45 // batteryVoltagePath: battery voltage (POWER_SUPPLY_PROP_VOLTAGE_NOW)
46 // batteryTemperaturePath: battery temperature (POWER_SUPPLY_PROP_TEMP)
47 // batteryTechnologyPath: battery technology (POWER_SUPPLY_PROP_TECHNOLOGY)
48 // batteryCurrentNowPath: battery current (POWER_SUPPLY_PROP_CURRENT_NOW)
49 // batteryChargeCounterPath: battery accumulated charg
[all...] |
| /device/asus/flo/ |
| thermald-flo.conf | 63 actions cpu+battery cpu+battery cpu+battery cpu+battery cpu+battery cpu+battery cpu+battery shutdown
|
| /device/lge/mako/ |
| thermald-mako.conf | 84 actions cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery cpu+gpu+lcd+battery
|
| /external/chromium_org/chrome/browser/chromeos/power/ |
| peripheral_battery_observer.cc | 33 // When a peripheral device's battery level is <= kLowBatteryLevel, consider
34 // it to be in low battery condition.
37 // Don't show 2 low battery notification within |kNotificationIntervalSec|
41 const char kNotificationOriginUrl[] = "chrome://peripheral-battery";
43 // HID Bluetooth device's battery sysfs entry path looks like
44 // "/sys/class/power_supply/hid-AA:BB:CC:DD:EE:FF-battery".
48 const char kHIDBatteryPathSuffix[] = "-battery";
124 LOG(ERROR) << "Unsupported battery path " << path;
129 LOG(ERROR) << "No valid battery address at path " << path;
134 LOG(ERROR) << "Invalid battery level " << leve
157 BatteryInfo* battery = &batteries_[address]; local
[all...] |
| peripheral_battery_observer.h | 23 // This observer listens for peripheral device battery status and shows
24 // notifications for low battery conditions.
65 // Battery level within range [0, 100], and -1 for unknown level.
75 // Posts a low battery notification with unique id |address|. Returns true
77 bool PostNotification(const std::string& address, const BatteryInfo& battery);
81 // Record of existing battery infomation. For bluetooth HID device, the key
|
| /frameworks/base/docs/html/training/monitoring-device-state/ |
| battery-monitoring.jd | 1 page.title=Monitoring the Battery Level and Charging State
2 parent.title=Optimizing Battery Life
18 <li><a href="#CurrentLevel">Determine the Current Battery Level</a></li>
19 <li><a href="#MonitorLevel">Monitor Significant Changes in Battery Level</a></li>
31 updates on battery life, checking the current battery level and charging state is a good place to
34 <p>The battery-life impact of performing application updates depends on the battery level and
38 prolong the battery life.</p>
40 <p>Similarly, you can check the battery charge level, potentially reducing the frequency of—o
[all...] |
| index.jd | 1 page.title=Optimizing Battery Life
26 <p>For your app to be a good citizen, it should seek to limit its impact on the battery life of its
31 reducing the rate of such updates when the battery level is low, you can ensure that the impact of
32 your app on battery life is minimized, without compromising the user experience.</p>
41 <dt><b><a href="battery-monitoring.html">Monitoring the Battery Level and Charging State</a></b></dt>
42 <dd>Learn how to alter your app's update rate by determining, and monitoring, the current battery
|
| /external/chromium_org/chrome/test/functional/ |
| chromeos_battery.py | 14 """Tests ChromeOS Battery Status.
21 3) Battery is installed in the DUT, and battery is not fully
26 When AC power is turned off or on, the battery will take from 2
41 # Leave AC power ON so battery does not discharge between tests
58 'Battery charge/discharge time was not calculated.'
67 """Calculate battery time to full when AC is ON"""
68 # Apply AC power to chromebook with battery.
71 # Get info about charging battery
75 msg='Battery is not present.'
[all...] |
| /frameworks/base/docs/html-intl/ru/training/monitoring-device-state/ |
| index.jd | 1 page.title=Optimizing Battery Life
5 next.title=Monitoring the Battery Level and Charging State
6 next.link=battery-monitoring.html
38 <dt><b><a href="battery-monitoring.html">???????????? ?????? ?????? ??????? ? ????????? ???????</a></b></dt>
|
| docking-monitoring.jd | 2 parent.title=Optimizing Battery Life
6 previous.title= Monitoring the Battery Level and Charging State
7 previous.link=battery-monitoring.html
48 <pre>int dockState = battery.getIntExtra(EXTRA_DOCK_STATE, -1);
|
| /frameworks/base/docs/html/training/efficient-downloads/ |
| connectivity_patterns.jd | 2 parent.title=Transferring Data Without Draining the Battery
22 <li><a href="{@docRoot}training/monitoring-device-state/index.html">Optimizing Battery Life</a></li>
28 <p>When it comes to impact on battery life, not all connection types are created equal. Not only does the Wi-Fi radio use significantly less battery than its wireless radio counterparts, but the radios used in different wireless radio technologies have different battery implications.</p>
32 <p>In most cases a Wi-Fi radio will offer greater bandwidth at a significantly lower battery cost. As a result, you should endeavor to perform data transfers when connected over Wi-Fi whenever possible.</p>
34 <p>You can use a broadcast receiver to listen for connectivity changes that indicate when a Wi-Fi connection has been established to execute significant downloads, preempt scheduled updates, and potentially even temporarily increase the frequency of regular updates as described in <a href="{@docRoot}training/monitoring-device-state/index.html">Optimizing Battery Life</a> lesson <a href="{@docRoot}training/monitoring-device-state/connectivity-monitoring.html">Determining and Monitoring the Connectivity Status</a>.</p>
38 <p>When connected over a wireless radio, higher bandwidth generally comes at the price of higher battery cost. Meaning that LTE typically consumes more energy than 3G, which is in turn more expensive than 2G.</p>
40 <p>This means that while the underlying radio state machine varies based on the radio technology, generally speaking the relative battery impact of the state change tail-time is greater for higher bandwidth radios.</p>
42 <p>At the same time, the higher bandwidth means you can prefetch more aggressively, downloading more data over the same time. Perhaps less intuitively, because the tail-time battery cost is relatively higher, it's also more efficient to keep the radio active for longer periods du (…)
[all...] |
| index.jd | 1 page.title=Transferring Data Without Draining the Battery
2 page.tags="battery","network","wireless"
21 <li><a href="{@docRoot}training/monitoring-device-state/index.html">Optimizing Battery Life</a></li>
27 <p>In this class you will learn to minimize the battery life impact of downloads and network connections, particularly in relation to the wireless radio.</P
29 <p>This class demonstrates the best practices for scheduling and executing downloads using techniques such as caching, polling, and prefetching. You will learn how the power-use profile of the wireless radio can affect your choices on when, what, and how to transfer data in order to minimize impact on battery life.</p>
39 <dd>This lesson introduces the wireless radio state machine, explains how your app?s connectivity model interacts with it, and how you can minimize your data connection and use prefetching and bundling to minimize the battery drain associated with your data transfers.</dd>
48 <dd>When it comes to impact on battery life, not all connection types are created equal. Not only does the Wi-Fi radio use significantly less battery than its wireless radio counterparts, but the radios used in different wireless radio technologies have different battery implications.</dd>
|
| /external/chromium/chrome/browser/chromeos/cros/ |
| power_library.h | 32 // Whether or not the battery is fully charged..
35 // The percentage (0-100) of remaining battery.
38 // Whether there is a battery present.
41 // The amount of time until battery is empty.
44 // The amount of time until battery is full.
|
| /device/samsung/manta/health/ |
| healthd-manta.cpp | 63 "battery overheat (%d), charging unavailable\n",
72 "battery recovery (%d), charging available\n",
80 "battery cold (%d), charging unavailable\n",
116 KLOG_INFO(LOG_TAG, "battery charge enable=%d\n", enable);
134 KLOG_INFO(LOG_TAG, "battery full\n");
144 KLOG_WARNING("battery charging timer not started, starting\n");
153 KLOG_INFO(LOG_TAG, "battery charging timer expired\n");
185 * Don't re-enable charging if the battery is full and we
256 KLOG_INFO(LOG_TAG, "battery health recovered\n");
284 // return 0 to log periodic polled battery status to kernel lo
[all...] |
| /external/chromium_org/ash/system/chromeos/power/ |
| power_status.h | 25 // Different styles of battery icons.
42 // Maximum battery time-to-full or time-to-empty that should be displayed
43 // in the UI. If the current is close to zero, battery time estimates can
76 // Returns true if a battery is present.
79 // Returns true if the battery is full. This also implies that a charger
83 // Returns true if the battery is charging. Note that this implies that a
85 // battery may be discharging even while a (perhaps low-power) charger is
90 // Returns true if the battery is discharging (or neither charging nor
94 // Returns the battery's remaining charge as a value in the range [0.0,
98 // Returns the battery's remaining charge, rounded to an integer with
[all...] |
| /external/chromium/chrome/browser/chromeos/ |
| low_battery_observer.h | 18 // The low battery observer displays a system notification when the battery
|
| /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.
|
| /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 -->
|
| /external/bluetooth/bluedroid/stack/include/ |
| srvc_api.h | 87 ** Data structure used by Battery Service
182 ** BATTERY SERVICE API
188 ** Description Instantiate a Battery service
197 ** Description Respond to a battery service request
205 ** Description Send battery level notification
|
| /external/chromium_org/base/power_monitor/ |
| power_monitor_device_source.h | 18 // Windows HiRes timers drain the battery faster so we need to know the battery
84 // running on battery power. Returns true if running on batteries,
88 // Checks the battery status and notifies observers if the battery
|
| /external/chromium_org/base/timer/ |
| hi_res_timer_manager_unittest.cc | 28 // test is running on a laptop/battery, then the PowerMonitor would have
29 // already set the PowerState to battery power; but if we're running on a
30 // desktop, then the PowerState will be non-battery power). Simulate a power
45 // Simulate a on-battery power event.
50 // Simulate a off-battery power event.
|
| /frameworks/base/docs/html/tools/testing/ |
| what_to_test.jd | 52 <h4>Battery life</h4>
54 Mobile devices primarily run on battery power. A device has finite "battery budget", and when it
56 minimize battery usage, you need to test its battery performance, and you need to test the
57 methods that manage battery usage.
60 Techniques for minimizing battery usage were presented at the 2010 Google I/O conference in the
63 Coding for Life -- Battery Life, That Is</a>. This presentation describes the impact on battery
65 impacts. When you code your application to reduce battery usage, you also write th
[all...] |
| /external/bluetooth/bluedroid/stack/srvc/ |
| srvc_battery.c | 82 /* read battery level */
121 /* read battery level */
189 ** Description Instantiate a Battery service
202 GATT_TRACE_ERROR0("MAX battery service has been reached");
225 /* add battery level
237 GATT_TRACE_ERROR0("Can not add Battery Level, Battery_Instantiate() failed!");
250 GATT_TRACE_ERROR0("Add battery level client notification FAILED!");
262 GATT_TRACE_ERROR0("Add battery level presentation format descriptor FAILED!");
275 GATT_TRACE_ERROR0("Add battery level report reference descriptor FAILED!");
298 ** Description Respond to a battery service reques
[all...] |
