W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2011

RE: Review of the Battery Status Event specification

From: 鼻扁全 <kihong.kwon@samsung.com>
Date: Tue, 31 May 2011 17:59:40 +0900
To: 'Anssi Kostiainen' <anssi.kostiainen@nokia.com>
Cc: public-device-apis@w3.org
Message-id: <001001cc1f71$13bde7c0$3b39b740$%kwon@samsung.com>
Hi Anssi.

I have thought about your mention, you are right.
I can get same information what I want by monitoring the level and the
isPlugged.

As your mention, using the battery level and the isPlugged for checking
charging status is common way.

Thank you for the response.

Best regars.
Kihong.



> -----Original Message-----
> From: public-device-apis-request@w3.org [mailto:public-device-apis-
> request@w3.org] On Behalf Of Anssi Kostiainen
> Sent: Monday, May 30, 2011 10:32 PM
> To: kihong.kwon@samsung.com
> Cc: public-device-apis@w3.org
> Subject: Re: Review of the Battery Status Event specification
> 
> Hi Kihong,
> 
> On 30.5.2011, at 15.28, ext 鼻扁全 wrote:
> 
> > I'm Kihong Kwon and works for Samsung Electronics.
> > Concerning to revised draft of Battery Status Spec, I have a comment
> > related with dropped attribute, isCharging.
> >
> > In the perspective of handset manufacturer, I think additional attribute
> > might be required to indicate whether a device is strongly charged or
> not
> > on the isPluged state.
> > Because some applications would like to do certain heavy works as a
> > background jobs in only strongly charged state due to battery
> consumption
> > issue.
> > In case that device is connected to USB port, the amount of power is a
> > little. So it's not appropriate time to do heavy works in background.
> >
> > What do you think?
> 
> Thank you for your feedback.
> 
> I tried to simplify the prose around isPlugged to better address your
> concerns, but I see we may still need to clarify it. Feel free to propose
> better wording.
> 
> Would your use case be addressed by monitoring the level while isPlugged
> is true?
> 
> -Anssi
Received on Tuesday, 31 May 2011 09:00:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:20 GMT