Automate on/off for HD Voice (VoLTE)

[1slav]

Hello kindred spirits,

I would like to solicit your help in automating a task. I'm new to this app and have not been able to figure out how to solve this issue.

Here's what I'm trying to accomplish. 

I have an LG G3 and Verizon recently (in the last year) rolled out VoLTE, or HD Voice calling. I would like to use this feature at all times, other than when I'm home, because at home I have a network extender (femtocell) which doesn't work if I have the HD Voice feature enabled. Thus, I would like to automatically turn off HD Voice every time I connect to my home wifi (or by location when I'm near home) and then turn it back on when I disconnect from my home wifi (or leave the house). 

The HD Voice Setting is located in phone settings under Advanced Calling and does not appear under the Tasker phone settings list of actions. I'm not sure how best to approach this and would greatly appreciate any advice from you experts.

Thanks in advance,

1Slav

[Don D]

Check out Autoinput

https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput

You can have it turn on/off when you connect or disconnect from home wifi.  The screen does need to be on for it to run, so if you are rooted you can turn the screen on automatically, if not just turn it on manually when you get home.

[1slav]

Thank you Don! I've been playing around with AutoInput and here's how far I got. I created an event based on being connected to my home wifi SSID...and when that happens I used AutoInput's Easy Setup where it asks to me to go the screen of the app I want to act on and click "Add." 

So I go into my phone settings with a down-swipe, click on the gear in top right corner, click on Advanced Calling, then click on Turn on/off HD Voice/Video and then return to AutoInput to click "Add." I then click on the HD Voice on/off toggle switch...I save everything and return to Tasker. So everything seems right but it's not working. I'm wondering if Tasker or AutoInput is having problems getting to the proper settings screen to enable/disable HD Voice since it's not really an app. I don't know...

Any additional advice/help would be greatly appreciated. I feel like I'm pretty close to solving this.

Thanks again,

1slav

[Brad Minion]

So I go into my phone settings with a down-swipe, click on the gear in top right corner, click on Advanced Calling, then click on Turn on/off HD Voice/Video and then return to AutoInput to click "Add." I then click on the HD Voice on/off toggle switch...I save everything and return to Tasker. So everything seems right but it's not working. I'm wondering if Tasker or AutoInput is having problems getting to the proper settings screen to enable/disable HD Voice since it's not really an app. I don't know...

​I believe AutoInput needs to do each of those actions, not just the last one. So try coding an AutoInput action for each one. Also, be aware that in my experience for AutoInput to work properly, the screen must be on​ and unlocked.

[1slav]

Thanks Brad - i tried creating actions for each one of those steps, too but this is what I get:

14.56.48/ActionArgBundle key: NearbyText: replace <null> String value with null
14.56.48/ActionArgBundle key: TextToWrite: replace <null> String value with null
14.56.48/ActionArgBundle key: StoredAction: replace <null> String value with null
14.56.48/ActionArgBundle AutoInput Action: TextToWrite: ignored replacement specified for null value
14.56.48/ActionArgBundle AutoInput Action: StoredAction: ignored replacement specified for null value
14.56.48/ActionArgBundle AutoInput Action: extra key not found in bundle:RecentFieldIds
14.56.48/ActionArgBundle AutoInput Action: extra key not found in bundle:ActionTimeout
14.56.48/ActionArgBundle AutoInput Action: NearbyText: ignored replacement specified for null value
14.56.48/E FIRE PLUGIN: AutoInput Action /com.twofortyfouram.locale.intent.action.FIRE_SETTING: 12 bundle keys
14.56.48/E AutoInput Action: plugin comp:com.joaomgcd.autoinput/com.joaomgcd.autoinput.broadcastreceiver.BroadcastReceiverFire
14.56.48/E add wait type Plugin5 time 5
14.56.48/E add wait type Plugin5 done

Not sure what to do from this point....

[1slav]

Hello again Don - I've been playing around with AutoInput and can't seem to get it to toggle the on/off switch for HD Voice in my settings. On the plus side, I was able to get it to open my Calendar app, however, so I got that going for me...haha.

Any tips on how to get it to the correct settings screen so that it can toggle my HD Voice switch on and off? 

Brad (below) suggested creating an action for every step of getting to the correct settings screen but where do I start? at the home screen? from the app drawer? from the top slide-down menu (as you know there are multiple ways to access the settings)?

I appreciate your help with this. Perhaps you could also point me to a good AutoInput tutorial/instructions because for some reason they are not easy to locate.

Thanks,

iSlav

On Wednesday, February 17, 2016 at 10:49:45 AM UTC-5, Don D wrote:

[Brad Minion]

I created a basic task to toggle HD Voice. I couldn't figure out how to tell AutoInput to turn off (i.e. slide the on/off toggle to the left), so I ended up just choosing to click it. That makes it a toggle rather than turning it off specifically. Maybe you can figure that part out or live with it as a toggle. You can probably shorten the Waits as well but I think you need some kind of pause between actions. One last thing. When I first tried using AutoInput I couldn't get the free version to work. Once I purchased it, then it worked for me. I used Tasker's All Settings action to initially bring up settings. Then used AutoInput after that.

Profile: ATest (55)
State: Wifi Connected [ SSID:home MAC:* IP:* ]
Enter: Anon (69)
A1: All Settings
A2: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A3: AutoInput Action [ Configuration:Type: Text
Value: Advanced Calling
Action : Click
Is Tasker Action: false
Check Screen State: false Package:com.joaomgcd.autoinput Name:AutoInput Action Timeout (Seconds):20 ]
A4: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A5: AutoInput Action [ Configuration:Type: Text
Value: Turn on/off HD Voice and Video call.
Action : Click
Is Tasker Action: false
Check Screen State: false Package:com.joaomgcd.autoinput Name:AutoInput Action Timeout (Seconds):20 ]
A6: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A7: AutoInput Action [ Configuration:Type: Id
Value: com.android.phone:id/advanced_call_switch
Action : Click
Is Tasker Action: false
Check Screen State: false Package:com.joaomgcd.autoinput Name:AutoInput Action Timeout (Seconds):20 ]

 

--
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 https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[1slav]

Thanks again Brad. Your instructions worked for the most part. However, I'm running into a big of an issue still. 

When I "play" the task myself in Tasker it runs through the sequence flawlessly, going from screen to screen until it gets to last window and switches the toggle on or off. I set all my waits to 5 seconds between the steps and it works fine.

However, when I actually connect/disconnect from my wifi it sometimes takes very long pauses like 45sec after the first task (All Settings) and then it just sits at the second screen....not sure what's happening. Why would it work when I run in Tasker but not when it's in the "real world?" Not sure I understand what's changing with the tasks to cause it to hang up. 

Any thoughts on this?

Thanks again,

iSlav

[1slav]

Ok so I've been messing around with it and may have found a solution. I believe it was hanging up because I wasn't giving it enough of a pause at the start so when wifi was connecting/disconnecting it was eating up a lot of my phone's resources and without a longer wait (45secs) Tasker would just hang up on step 1 and get all messed up after that.

At least that's my best guess at what was going wrong and with the pause it seems to all work now.

Thanks,

Stan