Outgoing call variables not being set.

[Kevin Taylor]

Using Tasker 1.1b5m on an HTC Desire S, Release:2.3.3

The outgoing call variables %CONUM and %CONAME are not being set.
I have tried making calls via Tasker (Action Intent android.intent.action.CALL), by selecting fron Contacts, and by manually dialling, all with the same result.
I have tried switching the phone off and on again. (fast boot disabled)

From a search of this group I understand this used to work - but maybe not on this phone model / OS version.

Incoming call variables %CNUM and %CNAME are set correctly.

Kevin

[Pent]

> The outgoing call variables %CONUM and %CONAME are not being set.

How are you using them ?

Pent

[Kevin Taylor]

>> The outgoing call variables %CONUM and %CONAME are not being set.

> How are you using them ?

In a Tasker task called from a Zoom element.
I've tried a couple of ways:
As part of the text argument to a Say; ( Say says "percent-conum" )
As the RHS of a Variable Set with condition: Set %myvar to %CONUM If %CONUM IsSet (%myvar remains unchanged)

Kevin

[Matt]

Hi Kevin,

I had a similar problem (see:
http://groups.google.com/group/tasker/browse_thread/thread/430c9c9e8232526f/e98a8cfaa1885847#e98a8cfaa1885847)
The way I got round it was to set up a profile Event> call in > Caller
%CNUM the task for this set zoom element text.

I would be interested to know if there is a better way of getting the
variables to be monitored though...

Matt

[Pent]

> >> The outgoing call variables %CONUM and %CONAME are not being set.
> > How are you using them ?
>
> In a Tasker task called from a Zoom element.

Ah, right.

Tasker doesn't know you're using that task for anything so it doesn't
bother monitoring the variables (it would notice if you called it from
a Tasker widget).

It would be the same with any external app calling a Tasker task.

Didn't think of that, but I don't want to monitor any variable
mentioned in any task.

Will think about a solution, in the meantime you can work around it by
e.g. making a profile with a variable value state %CONUM with just a
Stop action for the task.

Pent

[Kevin Taylor]

> Will think about a solution,

Maybe a list of extra variables to monitor in Preferences/Monitor?

> in the meantime you can work around it by
> e.g. making a profile with a variable value state %CONUM with just a
> Stop action for the task.

OK, that works perfectly, Thanks!

Kevin

[S Mackin]

Would you be able to detail making the workaround profile?

I have created a profile triggered by event -> %CONUM *

and placed it top of the list, linked to a task of tasker action -> stop with all fields empty.

Can you spot where I have gone wrong?

Thanks in advance