Does root call manager show notifications in the notification bar?
Inbox doesn't provide an api like Gmail does to get at this information.
You may be able to use the Gmail labels for inbox notifications but I've not tried that as lightflow doesn't rely on the actual notification from Gmail for new labels like it does for some apps.
Can you send me a link to the app in the play store as I couldn’t find it?
Do you know the package name of the app?
I totally agree with what’s been said. My plan is for version 4 of the app to have full profile support (or at least the basics to get things started). I’d like to add a manual widget plus events to automatically switch profiles (such as llama has). There’s already hooks between light flow and llama that will be possible (once I’ve added profiles) to allow profile changes in Llama to hook up to automatically changing lightflow profiles as well.
It does need thorough thought though to make sure it works in a sensible way.
I'm still working towards this, a big part of this was done as part of the user interface rework recently and also the last releases llama and tasker integration.
With tasker or llama you can now switch most lightflow settings via their events. This will also be used by lightflow directly in the future once I've added in the user interface and events model
These are all things I'm thinking of too
Yes that make sense. I am planning on adding wear support to hopefully allow more control regarding granularity by using lightflow instead of the native apps.
Determining when to send notifications, if they vibrate and only for specific contacts is certainly something I'm wanting to add.
If you have a pebble could you email me as I’m looking for somebody to test it (I’ve written some code, but don’t have the watch)
@Todd, is that a specific app?
Could you explain a little more, I don’t understand quite what you mean
So adding a "vibrate mode" notification, separating it from the silent mode option?
I’ll get in touch with their dev and see if there’s anything I can do
Thanks Francois. I've been in touch with Jake and I've got myself a reminder set to chat about this soon. I've just ended up very busy since pushing out a recent update in the app. Once that's calmed down I'll be in touch
It's a feature I'd love to add and technically it's possible, but there's a big side effect - battery drain.
With the current on/off timings the processed is controlled via android and passed through to the hardware drivers and is fairly battery efficient. To keep changing the pattern more frequently (either more color changes, or keeping changing the pattern) would mean that we'd have to keep issuing on/off timings or color change timings potentially several times a second. Every change like this means code needs to run. Running code means the phone has to be in a "partial wake" state which brings the CPU out of "deep sleep" and hits the battery quite hard. On testing this in the past (I had it working in an older development build) it would make the app use 25%+ of the battery.
Do you have a link to the app as I can’t find it in the play store?
Thanks, I'll add it in
It may be a little easier, but there are still many apps where this just wouldn't work. It's more complicated than just monitoring for the package name. Some apps need to include/exclude persistent notifications. Some need to react differently depending on circumstance and often require decompiling of other apps to figure things out. Some need text filtering out.
As one example (I could have many apps, so this is just an example). Kaiten mail on every sync will popup a notification into the notification bar for a really small period of time when checking mail.If just based on notifications this would either switch the notifications on or would clear existing "new mail" notifications when the sync check finished.
Another example is n4'get which has a concept of sticky messages, you wouldn't normally want a persistent notification to raise notifications, but in this situation you would.
Other apps such as twitter, facebook, mail, whatsapp and many more all use custom code to be able to identify notifications.
I need to balance this with increased support for application 'x' getting added by the user and getting false/no notifications.
I may add a "labs" section for doing this though. I'll have a think about it.
This one is actually very difficult to add. I know some other similar apps add options for this, but the issue is that there's so many different ways to monitor correctly for notifications. I've over a dozen standard routines used, plus lots of custom ones also where I need to decompile the app I'm trying to support or even get in touch with developers of the 3rd party app. Adding all these settings for the dozen standard methods would really confuse the standard user and also probably add to support time. Everything not notified would end up with constant false notifications I think as apps often raise notifications for tiny amounts of time then clear them and you'll probably never really see them.
At the moment samsung devices will work with root mode with the daydream on and I've made some progress with the nexus 4 on controlling in root mode, but I'm struggling to work out how to control the flash rate (I can get solid, or one flash speed)
I'm aware of this, Google have prevented any third party access at the moment to the information required to switch this off. I'm hoping that if they announce a new version of android they they also announce some API access for developers like they have added for gmail to be able to do this.
It's certainly something they have tightened up since gtalk. It's now not possible to query the message database or pick up on the broadcasts they use to clear the notification.
I'll look into adding all of those (vibrate may come a little later as it's a bit more complicated)
Which amazon app do you mean? Could you send me a link to it? (ie is the amazon app store)?
There's the option to have the sleep mode enable when the charger is plugged in. Would this help? With that you can suppress the led when charging (or can at least on most phones)
It really needs to be done via the led drivers. If I try and control it directly via android I'd keep needing to adjust the brightness level of the led. As it would need to be running code to always do this, it'd stop the CPU going into a sleep state and would therefore kill the battery. Technically it's possible, but the side effect wouldn't be worth it. Modified kernels should with different led drivers would be the only practical way to do this.
It's coming in the next release. That's one that I've got working.
This would technically be possible, but would kill the battery as the phone would never manage to go into a sleep state. I may add something like this for incoming call type notifications where it'll only be happening for a few seconds.
The talkback bug has been confirmed by samsung as a bug in their accessibility service which they have a fix for that they plan to release in their “next release”
The folder open / folder closed looks like it'll be fixed by samsung in 4.2.1 of android. It certainly seems fixed in the leaked rom on the internet that I've tried.