Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AF81B11FF2 for ; Wed, 11 Jun 2014 15:44:48 +0000 (UTC) Received: (qmail 48997 invoked by uid 500); 11 Jun 2014 15:44:43 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 48955 invoked by uid 500); 11 Jun 2014 15:44:43 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 48925 invoked by uid 99); 11 Jun 2014 15:44:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jun 2014 15:44:43 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bowserj@gmail.com designates 209.85.128.180 as permitted sender) Received: from [209.85.128.180] (HELO mail-ve0-f180.google.com) (209.85.128.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jun 2014 15:44:40 +0000 Received: by mail-ve0-f180.google.com with SMTP id jw12so8254718veb.25 for ; Wed, 11 Jun 2014 08:44:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=24fNnhhdhs8phjOvU1Yar6yYmJH7dTBpQIsWx+08dfo=; b=QYcWgycReyRjTvblwOexPjgUL6J6hDBT2arEHJkoeHXWzxU/DjJPFKOqck8Bvpao5Q GE68T1goicuBErSbrka9DfnnbjWcC00MoOWtyNTk26BcVq0XZT4VqnVqv3EtHp0X8mfp vUHmXNAitReOvBktGgm9uVSV5DCjqKTEoCJ5K8mTJkY84LqwdoITKRhXNt1vj6pxZHvm Zq8gzcTQwWv6INMnlYk0BSRY2SSIDKnrJijFDXgd2d6PFaMVSESl/U9W3z47S72YCiRp BIOgUtiXS6qdYxC2ZulMxe15k9yjvmkbKeioYV2lP1cPZc9zWmmNI+HpIL+cSrU3a03D uTkg== MIME-Version: 1.0 X-Received: by 10.220.89.4 with SMTP id c4mr1259826vcm.53.1402501456714; Wed, 11 Jun 2014 08:44:16 -0700 (PDT) Received: by 10.220.241.208 with HTTP; Wed, 11 Jun 2014 08:44:16 -0700 (PDT) In-Reply-To: References: <957F1ECDA90E004B8DBDE23CFC94E3A33B4E48EF@XMB111CNC.rim.net> Date: Wed, 11 Jun 2014 08:44:16 -0700 Message-ID: Subject: Re: [Android] Battery Plugin API drains battery..What now??? From: Joe Bowser To: dev Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org So, here's a couple of questions. 1. Do other platforms have battery problems when they're constantly monitoring the level of the battery? Or is this just something the Android implementation has problems with? 2. If it's just Android, does it make sense for Android to just not implement this spec and not have a battery plugin? I could test out iOS to see if this is also a problem, but I'm thinking other people already ran into this by now, right? On Wed, Jun 11, 2014 at 8:30 AM, Josh Soref wrote: > Joe Bowser wrote: >> So, last call for this is on Friday! > >> Josh, can anyone directly involved send in the -1 to this spec, >> or do you have to be involved somehow. > > It should be an implementer, but Cordova is more or less an implementer. > > It's better for someone who actually works on Cordova (e.g. You) than for > someone who is just a user of Cordova. > >> Otherwise, there's no way that Cordova can implement this on >> Android, and we'll be stuck with a plugin that has to be divergent. > > http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0049.html > > > Is the current thread, but you can start your own. If you want more > information about how to do this, you can contact Frederick Hirsch (the > chair of DAP) directly. >