-
Notifications
You must be signed in to change notification settings - Fork 30
intent request (led) #63
Comments
What would this do? I'm technical enough to tailor MWM to do odd things extra that I might My point is that I'm probably not alone there, and I and others could lend Kind Regards
|
we have "auto light when notify" but this is enabled for every notification/call; possible uses;
etc :) |
I would find that useful too. Good feature :-) Kind Regards
|
So do you want the ability to enable and disable the notification light for all notifications, based on a sent intent, or do you want to be able to choose whether specific notifications sent through the api have the light enabled? |
the latter. |
I don't think my watch has a notification LED. It has a little hole on the top right but I think that's the light sensor. |
What is meant by a notification light is that the backlight on the watch On 8 October 2012 20:16, foxmajik [email protected] wrote:
|
That does make sense. We have a configuration option that lets us specify whether or not to turn the light on when a notification arrives, as mentioned in an earlier comment, which is very useful. Some additional modifier options might be:
|
Light per-notification type is doable, all the others would require modifications to the firmware, which I'm currently trying to avoid, as there's no way for the app to recognise custom fw functionality - that's something I've talked to the MW guys about adding (so we can have a standard way of supporting fw mods), but that would be something for further in the future. |
hello,
can you add Protocol.ledChange
"led" - int (optional // 0 = off, 1 = on, default from options unless forced by this command)
to ApiIntentReceiver.java
org.metawatch.manager.NOTIFICATION and org.metawatch.manager.VIBRATE
cheers,
The text was updated successfully, but these errors were encountered: