Le 06/08/2013 10:47, Jonas Sicking a écrit : > On Aug 6, 2013 12:54 AM, "Jordano Francisco (UK)" < > francisco.jord...@telefonica.com> wrote: >> Hi all, >> >> >> On 06/08/2013 07:43, "Jonas Sicking" <jo...@sicking.cc> wrote: >> >>> On Aug 5, 2013 11:07 PM, "Karim Geiger" <gei...@b1-systems.de> wrote: >>>> On 08/05/2013 07:26 PM, Jonas Sicking wrote: >>>>> No. Do we need any? >>>> I think that's an important point. There are some cases you want to >>>> control the LED separately. >>> I think we need a bit more detail than that in order to spend time on > this >>> :-) >>> >>> / Jonas >> Typical use case for this api could be notifications, like FB >> notifications in android, >> use this API to setup the led blue. >> >> Other use cases (in samsung android phones): >> >> Red when plugged in - Charging >> Green when plugged in - Charging complete. >> Red when not plugged in - Low battery warning >> Blue - Audio is recording or you have a notification waiting. > Is the LED usually in control of system level logic, or is it more commonly > handled by drivers? > > I.e. would we be able to implement a LED API on most platforms? > > Either way, implementing an API which is exposed to only the system app > sounds like it would make sense. Though we would likely need the API to > expose which colors the hardware is able to support.
The K9-mail mail application is using led colors as well. I have a color wheel to choose the color of, but I don't know if the actual color is used or if only some colors are used. There may be several leds also, right ?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
