Problem with the Call State not activating when in a call

[S. H.]

I have an "automatic speakerphone" profile set up as per the instruction found here: https://android.gadgethacks.com/how-to/automatically-turn-speakerphone-when-you-arent-holding-your-android-device-your-ear-0159325/

But Tasker isn't picking up the Call state when I'm in a phone call. The profile doesn't activate, and the Call state isn't highlighted when I check Tasker while a phone call is active.

Tasker version is 5.0u6 on Android 7.1.2, OnePlus 3T custom rom. Using the stock dialer app.

Also, I don't want this profile to run when the phone is connected to my car's Bluetooth (so a state, not an event). How would I do that? The help file for State - BT Connected has a warning that "Tasker can't directly detect when a BT device is connected, only when a connection or disconnection is made." This is confusing...

Any help/pointer is appreciated!

[Rich B]

I am having the same trouble. It only started recently. Tasker is not recognizing that there is a call going on. The Call Any State doesn't turn green during the call. I tried creating different versions of the profile to see if that would help, but it doesn't.

PENT: Is there an issue with Call Any not recognizing when the phone is in a call? I'm using Nexus 6P rooted and Android 7.1.2.

Thanks.

[Rich B]

As a follow-up to my prior message, I checked the run log and the profile is not triggered at all. However, I have another profile that uses Call State and it IS triggered. That one uses the C:ANY parameter (any contact) to send an SMS when I'm on a call. For the other profile, I left Number blank and then tried *, neither of work. So, I think there's something up with Call Any without any contact parameters to match. Just in case anyone asks, here is my profile/tasks:

Profile: Speaker Test (114)
State: Call [ Type:Any Number:* ]
State: Orientation [ Is:Face Up ]
Enter: Test1 (115)
A1: Speakerphone [ Set:On ]

Exit: Test3 (116)
A1: Speakerphone [ Set:Off ]

Anybody have an idea about this? Any known problems with Call type any number? Thanks!

On Friday, September 29, 2017 at 4:32:20 PM UTC-4, S. H. wrote:

[S. H.]

I solved my problem by activating Tasker in the accessibility setting. Check if yours is on. This did the trick for me. The profile has been running fine since.

Go to the menu -> More -> Android Settings -> Accessibility Settings.

[S. H.]

Mine is Call Any + Not Proximity Sensor. (instead of Face Up Orientation).

[Rich B]

Interesting. My accessibility setting for Tasker got turned off somehow. Of course, Google is forcing the removal of the accessibility setting from Tasker so if it's needed for the speakerphone profiles then I'm not sure how we're going to get that to work in the near future.

[Rich B]

One of my routines uses the proximity sensor and the other used orientation. I was just trying he the one to see if they would work. I'll see if they work now that I turned accessibility back on. I had a profile that used to run daily to turn on accessibility for a bunch of apps. I might have to turn that profile back on, at least until accessibility is removed from all those apps because of Google policy.