Is there a way to get a Volume Changed Event?

[Wes Stacey]

We have the variable %VOLM (and all the other volume variables) but there is no context to trigger whent eh volume changes. I have a Zoom widget that i want to update whenever there is a change in the volume. 

The Variable Set Event doesn't seem to trigger when i change the volume. 

and the Variable Value State doesn't work for Built in variables. 

I looked and haven't found any context that will work for this, right now i have it update when i hit any of the buttons on the widget but it'd be nice not to have to do this. 

[Brad Minion]

I have a profile that senses a media volume change. I did Event/Variables/Variable Set/Volume Media. I left the value blank because I don't care what the value is, I just care that it changed.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/groups/opt_out.

[Brad Minion]

Sorry, I selected "Volume Media" from the list and that translates to the variable %VOLM.

[Wes Stacey]

OK so that's weird, i had tried this before and i thought that it didn't work. It works but only partially, it works if the volume rocker changes the media volume, however it does not get triggered if Tasker changes the media volume. 

S i guess that is something we need to bring up to Pent. 

[Brad Minion]

>OK so that's weird, i had tried this before and i thought that it didn't work. It >works but only partially, it works if the volume rocker changes the media >volume, however it does not get triggered if Tasker changes the media >volume. 

I'm not noticing that behavior. The reason I created that profile is because I would be listening to an audio book through a stereo patch cable connected to my car's sound system with the volume on max so the sound can be controlled by the radio and for no apparent reason the volume gets lowered. I didn't know if it's another Tasker profile or something on my phone doing that. I turned on Tasker logging and that implied that it was my phone doing it. The last log I ran shows my AtHome profiles ending at 6:06. The very next thing that happens in the log is the Instant activation of my MediaVolume profile. I was driving and not touching the phone at that time so that means that it wasn't a result of me touching the volume rocker. I've also tested it using the volume rocker and that activates it as well.

[Wes Stacey]

I'm not saying that there aren't OTHER ways of changing the phone volume, such as the phone OS changing it and i assume that the OS will trigger the same way as if the volume rocker were hit. 

What i'm saying is that changes that TASKER makes to the volume (through the Media Volume Action) aren't getting recognized by the Variables Set Context. 

From what you're saying you aren't even having Tasker change the volume, so how can you say that you aren't seeing this behavior.. 

[Brad Minion]

I agree you're right. I just created a Tasker task to adjust the volume and turned on logging. I made sure volume was at max and then ran the task to adjust the volume down. My instant volume changed profile did not trigger.

At first I thought it might be Tasker trying to change the volume level to itself and that's why it wasn't activating. In other words, if I run my volume adjust task twice, it doesn't do anything the second time because the volume is already at that setting so no change to detect. Even if that's the case, it should have triggered in my test above.

This definitely seems like a bug.

--

[Matt R]

I think it might be intentional: https://groups.google.com/d/msg/tasker/phM9KrasECo/k6Yd6qksR0gJ

Matt

[Wes Stacey]

Ok so with that being the case i added Brad's suggestion to catch the changes made by the volume rocker and pressing any button on the widget will also update the widget. This combination should catch most of the changes, only ones that won't be caught are the changes made by a couple of other Tasker profiles. But i think i can live with that.