Le 08/09/2014 10:05, Jonas Sicking a écrit : > I think we should do a few things here: > > 1. Introduce a privileged API for controlling the LED. > 2. Let the system app use that API in order to blink the LED whenever > a notification is rendered. > 3. Use the API to indicate battery status (low battery, very low > battery, charging) > 4. Possibly enable apps to specify an LED pattern when creating notifications. >
Yep, however, the Flame currently does not have a LED that we could use that easily. There is the charger led, but it's not really intended for this, mostly because as far as I could test hacking in sysfs, any change would work but get overwritten after a couple of seconds. > > I'm honestly not fully understanding the use case of using the LED > when a notification is rendered. At least given that we currently > always turn on the screen whenever a notification is created. Is using > the LED useful even when we display the notification on screen? Having a LED could help us notifying more efficiently the user in several ways: blinking, changing colors, etc. > > However, Robert is working on the ability for apps to opt out having > the screen come on. Then I can more see the use for blinking the LED > to indicate a notification. > > Or is the idea to turn on the LED to indicate pending notifications? > And leave it on (or leave it blinking) until the user interacts with > the device? So that if you come back to a device that you were away > from you can see if you missed any notifications when you were away? > > / Jonas > > > On Sat, Sep 6, 2014 at 7:23 PM, Michael Henretty <[email protected]> > wrote: >> For the Notification API part, there has been a bunch of recent discussion >> about being able to specify device level behaviors using the API. If you are >> interesting in seeing the LED part standardized, now would be a great time >> to raise your voice: >> >> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2014-August/297421.html >> >> Also, we are currently working on version 1 of this which includes being >> able to specify things like waking the screen, sound, and vibration pattern >> using the API: >> https://bugzilla.mozilla.org/show_bug.cgi?id=912645 >> >> >> >> >> >> ----- Original Message ----- >> From: "Alexandre Lissy" <[email protected]> >> To: [email protected] >> Sent: Saturday, September 6, 2014 7:33:03 AM >> Subject: Re: [b2g] LED API? >> >> Le 06/09/2014 16:16, Jan Jongboom a écrit : >>> I wanted this badly yesterday tbh. I think a proper way to do this is to >>> combine it with notification API. System would be responsible for LED >>> handling, but apps can specify their wanted behavior through notification. >> >> That could be a good idea, but this needs: >> - API so that Gecko can drive the LEDs >> - extension to the notification API >> >>> _______________________________________________ >>> dev-b2g mailing list >>> [email protected] >>> https://lists.mozilla.org/listinfo/dev-b2g >>> >> >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
