ACTION-699: Review battery and how low battery threshold is handled

Review battery and how low battery threshold is handled

State:
closed
Person:
Giridhar Mandyam
Due on:
June 19, 2014
Created on:
June 12, 2014
Related emails:
  1. [minutes] Draft minutes 2014-06-26 Teleconference (from w3c@fjhirsch.com on 2014-06-26)
  2. Re: [battery] Moving Battery API forward, next steps? (from frederick.hirsch@nokia.com on 2014-06-26)
  3. Re: [battery] Moving Battery API forward, next steps? (from timvolodine@google.com on 2014-06-26)
  4. [admin] Agenda - DAP Distributed Meeting 26 June 2014 (from w3c@fjhirsch.com on 2014-06-23)
  5. [battery] Moving Battery API forward, next steps? (from frederick.hirsch@nokia.com on 2014-06-23)
  6. [admin] Corrected Draft Minutes 12 June 2014 teleconference (from w3c@fjhirsch.com on 2014-06-13)
  7. [battery] CfC for Battery API Last Call - decision is not to publish right now (from w3c@fjhirsch.com on 2014-06-13)
  8. [admin] Draft Minutes 12 June 2014 teleconference (from frederick.hirsch@nokia.com on 2014-06-12)

Related notes:

Any low power event would have to be created by the high level OS. The drivers do not provide this. In Android, the threshold for a low power event is fixed and determined at compile time. Any implementation of battery API would require an implementer (i.e. browser vendor) to create this event based on a threshold. It may not be that useful to developers, as they have no control over the threshold.

Giridhar Mandyam, 26 Jun 2014, 14:37:52

Display change log.


Anssi Kostiainen <anssi.kostiainen@intel.com>, Reilly Grant <reillyg@google.com>, Chairs, Fuqiao Xue <xfq@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $