OK, yeah, I just checked that myself. Since there's no changes, it's still got the problem of being event-driven and killing your battery. This is why we want to deprecate it on Android, since it actually can kill your phone within an hour if used continuously.
Still, I think we should accept the changes. Anyone else have any thoughts on this? On Thu, Aug 6, 2015 at 8:39 AM Paul Contat <[email protected]> wrote: > Because this plugin is based on the old one and don't modify the native > side, I think it keeps the same power consumption on Android. Is there any > tools to check that? > > > Le jeu. 6 août 2015 à 16:57, Joe Bowser <[email protected]> a écrit : > > > I think we want alignment. However, is the Battery Status plugin still > > harmful, as in does it still kill the battery as you monitor its status > on > > Android? If so, it's probably better that Android not have a Battery > Status > > plugin. > > > > On Thu, Aug 6, 2015 at 7:54 AM Paul Contat <[email protected]> > wrote: > > > > > Hi everyone, > > > A few weeks ago I did modification about promise polyfill into this > > > battery-status plugin pull request [1]. I know it's not one of the main > > > plugin, but battery status was downloaded 1950 time since it's on npm: > > it's > > > more than device orientation and just less than media capture and > > > vibration. > > > > > > So my question is, are you interested with this alignment or is it > > > preferable to create a third party plugin for this? > > > > > > [1] https://github.com/apache/cordova-plugin-battery-status/pull/24 > > > > > > Thanks, > > > Paul Contat > > > > > >
