Re: Sending MMI codes with Tasker's Phone > Call action

[Joe Irvine]

I use this to check my data usage daily and it works flawlessly for me.

Thanks,

Joe

On Mon, Jul 2, 2012 at 12:30 PM, James Valentine <jdval...@gmail.com> wrote:

Until recently, call diverts that I had working on a schedule would happen in the background. The only indication that they had run would be a message from Android.

So: sending ##004# would result in: "Call fordwarding - Erasure was successful" which I could dismiss by clicking ok.

Something must have changed. Now, instead of running the function in the background, the dialler is displayed. I don't believe the feature is working any more because I do not get the confirmation.

I can't use the divert action in Tasker, because I need to set up the divert using an MMI code as I specify a number of rings before the divert, and I can't do that with the standard divert feature of either Tasker or the phone.

Is anyone aware of any changes to the behaviour of the Phone > Call action?

Thanks.

[James Valentine]

Thanks Joe,

I've just double-checked with the code that disables call diverts.

I entered ##004# into the dialer, pressed call, and was greeted with the correct "MMI Code Started' flash, followed by the alert box, "Call forwarding // Erasure was successful".

Using a task shortcut to run the task (which does exactly the same thing) at will rather than on a schedule opened the dialer but never gives those messages.

There seems to be a difference in what Tasker does when dialing and what happens when a user actually presses the keypad buttons.

I'm on an HTC Desire HD with an OTA upgrade to Android 2.3.5 and HTC Sense 3.0. It has worked for months since my last software upgrade, though.

Many thanks.
J.

[Joe Irvine]

Can you post the settings you are using?  Maybe it;s something simple you're missing.

Thanks,

Joe

[easiuser]

Not sure if this just changed recently but you need to check the "Auto Dial" checkbox if you want the action to complete the call.  Otherwiase it just brings up the dialer screen and prefills the number.

[James Valentine]

Thanks easiuser,

yes, I've got auto dial on, and in fact, it does dial but also leaves a line in the call log, which it never used to do. It's although the code is being treated like a MSISDN/number. Here's what I have in that task:

Action: Call
Number: ##004#
Auto Dial: true
If:
Label:

Note that call works fine if I actually want to call somewhere. It just doesn't want to send MMI code.

Thanks,
J.

[James Valentine]

Hi Joe,

A development: something (Android itself) is prepending #31# in front of numbers dialled by third-party apps. How can I stop that happening? Hard to search Google for that problem, as the hashes are ignored.

Thanks,
J.

On Thursday, 5 July 2012 19:00:30 UTC+1, Joe Irvine wrote:

Can you post the settings you are using?  Maybe it;s something simple you're missing.

Thanks,

Joe

[James Valentine]

Apologies to the list. Sanity (another 3rd party app) was unhelpfully hiding my number. What confused me is that it was only for calls placed by 3rd party apps. I've turned that feature off, and now my MMI codes are going out fine.

Best regards to all.
J.