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 7A6BC1048F for ; Tue, 8 Mar 2016 06:15:58 +0000 (UTC) Received: (qmail 85779 invoked by uid 500); 8 Mar 2016 06:15:58 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 85734 invoked by uid 500); 8 Mar 2016 06:15:58 -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 85716 invoked by uid 99); 8 Mar 2016 06:15:57 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2016 06:15:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6E1731806C7 for ; Tue, 8 Mar 2016 06:15:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id vMpWjRdFbeeT for ; Tue, 8 Mar 2016 06:15:55 +0000 (UTC) Received: from mail-vk0-f52.google.com (mail-vk0-f52.google.com [209.85.213.52]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id A03745F393 for ; Tue, 8 Mar 2016 06:15:54 +0000 (UTC) Received: by mail-vk0-f52.google.com with SMTP id k1so6029157vkb.0 for ; Mon, 07 Mar 2016 22:15:54 -0800 (PST) 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; bh=dH0FtXHpxbYxAxr9k8gO14pKxjxDq1nDTGdWBtfzHOQ=; b=v8kgxFF+1xAsCygxEIX0fRzh2vZ5at0T/2XJXec2AOG/l+wS2D1+K5tLf4nU2J+AoA lQ3uRR2pd/sY4r5GfaYK/rkhuCkp9tx9H1BzytklCuwrxnFISUpBuiqaWN6mEO/hGlZO BEsma4OAbW/U+vt6ROhrE2S7kALDCcNpwPSkJjyZLf+rMrqsmr5NH3PKbVTMOH6ER+8I coVvdUJnoycTyVYz1MdHuNXlc79TdY379iF1eTWxjop5PU6Qj/xCIxpmyue0RQRc9R7q RsLiSu9YcCwpszV2Kuevd8i0dhwQNLKSSQMxm6Amw3h/U5yORqfZr+HsRPKaBUZ47o3j 7nIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=dH0FtXHpxbYxAxr9k8gO14pKxjxDq1nDTGdWBtfzHOQ=; b=XNkMl42Tlf+lMa2ZeBg3UfEbb1O6qTYapvPBAW+49J0f6wZfbUn1PZyeWrSQPEL0y6 1nQzbl7K+T+HzsfehYGWEFL2IgZiRM8vHzAHVQUq5ylSHsP4zCZ1CfRmsn0GnxT0JdUY 6kmNo6W5VLtryNJxjmknWNEA9tv6KFzxhu7y/1e6s/Q8Qrm1dHjcl2zEo30a2p7tufUh d5nPnMmqsujIFKMGnSCiPYttpVXk7BOJFjvV6L8GfRdQbKiVi8bXUjYnfZhTdEreaNqg d0Gqdals7+TyRfuY+tv9rsQ/LDjAyfdX7W8yeZTL9iqcCOVdZwkpTM1gUcaqTGEd1wiA 75qQ== X-Gm-Message-State: AD7BkJJVlFpco3AwIQm1bqjdbJl12L2ck0ZHjXS3RbpXcu3fggpTyknA9lrsSdhFEfjQDKNTX0R6wL4k3y2qng== MIME-Version: 1.0 X-Received: by 10.31.169.87 with SMTP id s84mr24151954vke.55.1457417495887; Mon, 07 Mar 2016 22:11:35 -0800 (PST) Received: by 10.159.38.66 with HTTP; Mon, 7 Mar 2016 22:11:35 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Mar 2016 22:11:35 -0800 Message-ID: Subject: Re: Can we please kill the Battery Plugin on Android From: Joe Bowser To: dev Content-Type: multipart/alternative; boundary=001a1141636e21c612052d8374c5 --001a1141636e21c612052d8374c5 Content-Type: text/plain; charset=UTF-8 Actually, we already document this as clear as possible in the README.md for the plugin. I think this is a very serious understatement. https://github.com/apache/cordova-plugin-battery-status On Mon, Mar 7, 2016 at 10:09 PM, Joe Bowser wrote: > > > On Mon, Mar 7, 2016 at 10:00 PM, Nikhil Khandelwal > wrote: > >> What's our deprecation policy? Should we log a deprecation message before >> remove this support. What alternatives do Cordova developers have - are >> there other plugins which provide the equivalent functionality - perhaps >> with a better API - as opposed to polling events every 1% battery drop. >> > > Our regular deprecation policy is six months, but I think we should bypass > that because our Battery Plugin on Android is harmful and will kill the > battery in two hours if left running. > > Chrome 38 has support for the W3C Battery API, but there's still not an > option for people stuck on 4.4 or below other than to use Crosswalk. The > thing is that a size penalty is still better than a battery that actually > drains the battery of the phone. > > You could do a scaled-down API where it only sends an event when the > battery is at 15% and has no meta information, but it wouldn't be > compatible with the W3C and I remember criticizing the W3C spec as being > unable to be implemented in Cordova by itself, since the Android SDK > requires us to subscribe to an event manually that is never meant to be > subscribed to. AFAIK, the community hasn't created a third party battery > plugin that works. I don't want us to keep distributing a plugin that is > so completely broken that it's harmful for users. I don't care how many > developers use it, since they're obviously not testing their applications. > > > >> >> -Nikhil >> >> -----Original Message----- >> From: Shazron [mailto:shazron@gmail.com] >> Sent: Monday, March 7, 2016 5:27 PM >> To: dev@cordova.apache.org >> Subject: Re: Can we please kill the Battery Plugin on Android >> >> +1 >> If no one has concerns by the end of the week, I'd say we would have lazy >> consensus and you can delete the Android part of the plugin (maybe prep the >> PR now) >> >> On Mon, Mar 7, 2016 at 12:12 PM, Joe Bowser wrote: >> > Hey >> > >> > Once again, I ran into someone using the Battery Plugin that actively >> > kills the Battery on Android, and can we please discourage people from >> > using this very broken plugin that we have no ability or intention of >> fixing? >> > >> > The reason I don't want to fix it because the browser already supports >> > it on the latest versions of Chromium, and because it's impossible to >> > fix without changing the API entirely. We really need to kick this >> > harmful plugin to the curb so that people stop making applications >> > that drain the battery of their devices. >> > >> > I know that we've talked about it at length, but I don't ever remember >> > us coming to a conclusion regarding killing the battery plugin on >> Android. >> > >> > Any thoughts? >> > >> > Joe >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org >> For additional commands, e-mail: dev-help@cordova.apache.org >> >> > --001a1141636e21c612052d8374c5--