/frameworks/base/docs/html/guide/topics/testing/ |
D | what_to_test.jd | 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 the 75 since WiFi transfers maximize battery usage compared to transfers over 3G or EDGE.
|
/frameworks/base/services/java/com/android/server/ |
D | SystemServer.java | 117 BatteryService battery = null; in run() local 173 battery = new BatteryService(context); in run() 174 ServiceManager.addService("battery", battery); in run() 184 power.init(context, lights, ActivityManagerService.getDefault(), battery); in run() 191 Watchdog.getInstance().init(context, battery, power, alarm, in run() 495 final BatteryService batteryF = battery; in run()
|
D | Watchdog.java | 183 public void init(Context context, BatteryService battery, in init() argument 187 mBattery = battery; in init()
|
D | EventLogTags.logtags | 10 # This is logged when battery goes from discharging to charging.
|
D | PowerManagerService.java | 496 BatteryService battery) { in init() argument 501 mBatteryService = battery; in init()
|
/frameworks/base/docs/html/guide/topics/location/ |
D | 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 …]
|
/frameworks/base/docs/html/sdk/ |
D | android-1.6-highlights.jd | 62 <img src="images/battery.png" class="screenshot" alt="" /><br/> 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
|
D | android-2.3-highlights.jd | 127 the system helps ensure best possible performance and maximum battery life.</p> 131 accurate overview of how the battery is being used, with details of the usage
|
D | RELEASENOTES.jd | 634 <li>The emulator's battery-control commands (<code>power <option></code>) 800 <li>The emulator's battery-control commands (<code>power <option></code>)
|
D | android-3.0-highlights.jd | 238 … application could receive broadcasts that indicate a connected device's battery level and could n…
|
D | android-2.3.jd | 577 battery usage reported in Manage Applications. </p></li>
|
/frameworks/base/docs/html/guide/practices/design/ |
D | seamlessness.jd | 18 <li><a href="#battery">Do Conserve the Device Battery</a></li> 229 <h2 id="battery">Do Conserve the Device Battery</h2> 232 wall. Mobile devices are battery-powered, and the longer we can make that 233 battery last on a charge, the happier everyone is — especially the user. 234 Two of the biggest consumers of battery power are the processor, and the 244 if you try right away; all you'll do is waste battery power.
|
D | performance.jd | 29 power and storage, and constrained battery life. Because of 32 Battery life is important to users, and Android's battery usage breakdown 33 means users will know if your app is responsible draining their battery.</p>
|
/frameworks/base/docs/html/resources/articles/ |
D | zipalign.jd | 40 and kill processes. The user ends up with a slow device with a poor battery
|
D | live-wallpapers.jd | 46 as much as possible to avoid using too much CPU, not only for battery life
|
/frameworks/base/docs/html/resources/faq/ |
D | security.jd | 108 <li>drains the device's battery very quickly;</li>
|
/frameworks/base/docs/html/guide/appendix/faq/ |
D | security.jd | 108 <li>drains the device's battery very quickly;</li>
|
/frameworks/base/docs/html/guide/developing/tools/ |
D | avd.jd | 213 <td>Whether the device can run on a battery. Default value is "yes".</td> 214 <td>hw.battery</td>
|
D | emulator.jd | 1354 <td>Display battery and charger state.</td> 1364 <td>Change battery status as specified.</td> 1370 <td>Set battery presence state.</td> 1375 <td>Set battery health state.</td> 1380 <td>Set remaining battery capacity state (0-100).</td> 1768 <li>No support for determining battery charge level and AC charging state</li>
|
/frameworks/base/docs/html/guide/topics/appwidgets/ |
D | index.jd | 167 conserve the battery. You might also allow the user to adjust the frequency in a 173 cause significant problems for the battery life. If, however, you need to update more
|
/frameworks/base/docs/html/guide/publishing/ |
D | preparing.jd | 69 touch-screen UI) and that your application's performance and battery efficiency
|
/frameworks/base/docs/html/guide/topics/intents/ |
D | intents-filters.jd | 151 <td>A warning that the battery is low.
|
/frameworks/base/docs/html/guide/topics/ |
D | fundamentals.jd | 201 that the battery is low, that a picture has been taken, or that the user
|