Tasker actually dialing a phone number?

[Soudane GMTA]

Is there any way to get Tasker to actually dial a phone number?  Or are we limited to Tasker only feeding the phone number to the dialer app, after which we have to use the dialer to call the number?

[Soudane GMTA]

PS: I know that I can get Tasker to feed the phone number to the dialer and then use AutoInput to click on the appropriate place in the dialer in order to initiate the call. However, I'm wondering if there is a more direct way from Tasker to simply directly dial a phone number?

[Matevz Leskovsek]

action -> call (on my phones it creates a phone call reliably)

> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/e67e75e4-641b-4821-b69a-9c48f2b69faen%40googlegroups.com.

[Soudane GMTA]

On my phone (Android 11), "Action Call" only opens the dialer sends the phone # to the dialer, and then I have to click the "Call" button on the dialer to actually make the call.

I'm hoping there is an alternative way to do this which makes the call immediately.

[Soudane GMTA]

PS: setting "Auto Dial" in "Action Call" works for actual outgoing calls. But I neglected to mention in my original message that I'm doing this with USSD codes, not an actual phone call.

The LSPosed package can be invoked via a USSD sequence. I want to control that via Tasker. But if I send the USSD sequence via "Action Call" with "Auto Dial" set, the dialer just tries to make that into a real phone call instead of treating it as USSD. So it fails.

I guess maybe my only alternative is to do what I mentioned in my original message: to send the USSD sequence to the dialer, and then control the Dialer via AutoInput in order to click the dialer's "Call" button. In that case, the USSD sequence gets properly recognized.

[Matevz Leskovsek]

seems it is possible with securetask plugin
https://www.reddit.com/r/tasker/comments/dc44iv/help_with_ussd/

> To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/33a98ba0-c2b1-40f5-8371-45617d71ba42n%40googlegroups.com.

[Soudane GMTA]

Thank you very much.

I discovered that I have to set SecureTask to be a device owner on my Android-11 phone before it can send USSD. And I now realize that this is a headache to get correct under A11, and if I make certain errors, I could end up in a boot loop and have to re-flash my OS.

So, unless there is another way for Tasker to cause USSD codes to be invoked, I'm going to give up on direct USSD and go back to simply invoking "Action Call" without "Auto Dial" and then using AutoInput to click on the dialer's "Call" button.

But I'll check back here periodically, in case someone might offer a non-SecureTask way to invoke USSD codes.

[aa6vh]

This may be phone dependent. On my Samsung S22 Ultra, the Tasker action "CALL" will sent the number to the dialer, and initiate the call, with doing any of that complicated stuff.

[Soudane GMTA]

But when initiating the call, does it honor the USSD command, or does it try to actually dial the USSD code as an outgoing phone call?

The problem I have is that the USSD command is dialed as an outgoing phone call when "Auto Dial" is set, and it's not honored as a USSD command to be executed.

[aa6vh]

Sorry, I was answering the OPs question, of not passing on the initiate call function. I would not expect USSD codes to necessarily work, especially the ones that are handled by the phone app itself. CALL sends the digits to the dialer, not the app. Codes that are passed on to the phone company, such as *67 to  block the caller id, should work though. And I verified it does on my phone.

[Soudane GMTA]

On Monday, January 23, 2023 at 3:41:11 PM UTC-5 aa6vh wrote:

Sorry, I was answering the OPs question, of not passing on the initiate call function. I would not expect USSD codes to necessarily work, especially the ones that are handled by the phone app itself. CALL sends the digits to the dialer, not the app. Codes that are passed on to the phone company, such as *67 to  block the caller id, should work though. And I verified it does on my phone.

Thank you, and I understand.  Actually, maybe the codes I'm trying to send are actually "MMI" codes and not "USSD" codes.

In any case, as I mentioned, I can do this by doing "Action Call" without "Auto Dial", and then just use AutoInput to click the "Call" button. So far, that's working fine.