On Aug 6, 2013 12:54 AM, "Jordano Francisco (UK)" < [email protected]> wrote: > > Hi all, > > > On 06/08/2013 07:43, "Jonas Sicking" <[email protected]> wrote: > > >On Aug 5, 2013 11:07 PM, "Karim Geiger" <[email protected]> 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. / Jonas _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
