Again I disagree. We've made clear that we do plan on adding priority support at some point. I'm simply pointing out that just because you did something one way on Tasker or some other app doesn't mean thats how this app is supposed to work. Our goal was never to be a Tasker or any other app clone. If another app has everything you are looking for then why are you trying other apps out? Clearly something was missing or you won't be looking into other solutions. We've only been available for 3 weeks. So we would hope we would be granted a little leeway before being compared to app that has years of development under their belts. So before you go saying this is how so and so did it, so you are wrong for not doing it that way. Maybe give us a chance to figure out how we want to handle these type of issues.
In your replies to me (on G+, I think) on the subject of priorities, it sure sounded like you had decided it was too difficult, and weren't going to be implementing them. If you've changed your mind, I'm sorry I didn't know that.
But there's another problem I've reported a couple of times, with Bluetooth, and haven't seen answered. My work profile has an action to turn BT
off. But it doesn't consistently work. Here's what I've noticed trying to figure this out:
My workplace has multiple WiFi APs. I have an app that will reconnect me to a strong AP as I move about the building and the AP I'm connected to gets too weak. When that handoff happens, the work profile re-fires (I have notifications turned on, so I can see it), but BT ends up turned on, instead of off. This is consistent, reproducible behavior.
Here's what seems to be happening: In order to connect to the new AP, the app has to disconnect from the prior AP. This should fire the trigger (Disconnect from any network) for the default profile, which turns BT on. But I don't get a notification for default profile, only the work profile. I wonder if the triggers (disconnect from any network, Connect to [specific network]) are happening so close together that the actions for the work and default profiles are somehow interfering with each other.
Occasionally, when moving between APs the default (not-work, not-home, not-car) profile does produce the notification when switching APs. This profile turns WiFi off, which prevents my phone from reconnecting to another AP. I have a location-based trigger for the work profile, but it doesn't seem to fire if I'm already inside that location.
