Re: Tasker not performing all of the action [for real] but records the action in the Log as OK
79 views
Skip to first unread message
Pent
Jul 29, 2012, 3:46:37 AM7/29/12
to Tasker
> Tasker appears to perform the 'Take call' tasks, and records them in the
> log with status 'OK', but the 2 tasks of answering the call and then
If the action shows as exiting OK, Tasker has asked Android to do the
relevant action. In some situations, some ROMs etc, Android will still
not do the thing e.g. some versions of the phone app ignore audio
related changes once a call has started. In some cases, a Task / Wait
action will help because you're trying to do the thing while Android
is busy with something else.
> turning on the speaker are not performed. I've test the proximity sensor
> both inside and outside Tasker and it works fine. However, I managed to get
> it to answer automatically without checking the proximity sensor in the
> context. As soon as I added the proximity sensor check, it stopped working.
Phone Ringing is an event. It happens once when the phone starts
ringing. If the proximity sensor was not covered at that time, then
the profile will not activiate.
I wouuld change Phone Ringing to the state Call, Incoming, which will
be active still when you cover the prox sensor.
Pent
> log with status 'OK', but the 2 tasks of answering the call and then
If the action shows as exiting OK, Tasker has asked Android to do the
relevant action. In some situations, some ROMs etc, Android will still
not do the thing e.g. some versions of the phone app ignore audio
related changes once a call has started. In some cases, a Task / Wait
action will help because you're trying to do the thing while Android
is busy with something else.
> turning on the speaker are not performed. I've test the proximity sensor
> both inside and outside Tasker and it works fine. However, I managed to get
> it to answer automatically without checking the proximity sensor in the
> context. As soon as I added the proximity sensor check, it stopped working.
Phone Ringing is an event. It happens once when the phone starts
ringing. If the proximity sensor was not covered at that time, then
the profile will not activiate.
I wouuld change Phone Ringing to the state Call, Incoming, which will
be active still when you cover the prox sensor.
Pent
Ishaan Agrawal
Jul 29, 2012, 3:56:29 AM7/29/12
to tas...@googlegroups.com
Will D
Jul 29, 2012, 4:13:15 AM7/29/12
to tas...@googlegroups.com
Hi Pent,
Thanks for the reply. I'm puzzled because its obvious that the profile was always activating even though I was checking the prox sensor as an event. I've changed the prox sensor to a state, as you suggested, and it has worked 2 out of 3 times. I will have to do some more testing, and will let you know what happens.
What does the status 'ExitOK' mean? I'm getting that along with seeing the profile as 'Inactive' sometimes, too.
Thanks.
Pent
Jul 29, 2012, 5:24:11 AM7/29/12
to Tasker
> Thanks for the reply. I'm puzzled because its obvious that the profile was
> always activating even though I was checking the prox sensor as an event.
Didn't understand that last bit. And earlier you said 'As soon as I
> always activating even though I was checking the prox sensor as an event.
added the proximity sensor check, it stopped working', which doesn't
sound like 'always activating'.
> I've changed the prox sensor to a state,
> as you suggested, and it has
> worked 2 out of 3 times. I will have to do some more testing, and will let
> you know what happens.
>
> What does the status 'ExitOK' mean?
> I'm getting that along with seeing the
> profile as 'Inactive' sometimes, too.
Pent
Reply all
Reply to author
Forward
0 new messages