Distinguishing between actually being in a phone call and the phone simply ringing.

[Soudane GMTA]

I'd like to use Tasker's facilities to distinguish between the following cases:

Case 1: The phone is ringing and hasn't been answered yet.

Case 2: The phone call has now been answered, and I'm within the connected phone call.

Oh, and I'd also like to detect when an answered phone call gets hung up.

There probably is some bug in my event management, because I haven't been able to properly tell these cases apart.

Thanks in advance for any ideas or suggestions.

[Brenden M]

For Case 1: Using the context of Event > Phone > Phone Ringing

Any call, or those from a specific number, can activate it.

For Case 2: Using the context of State > Phone > Call

If you leave the "Type" as Any," then an active call occurring with the number specified, or any number if blank, will make the Call State context active.

You might use "Incoming" if you do not want the state to activate when you call out.

When the call disconnects, use an exit task.

With state contexts, since you require at least one enter or exit task but do not need to have both, you can separate things into two Profiles or keep them in one as your workflow benefits.

Something here might work for you.

[Brenden M]

For example,

If Phone Ringing is "active" it is ringing.

If Phone Ringing stops being active, and Call is "active" it has been answered.

Then if Call stops being active, it has been hung up.

In other words there isn't one state or one event context....But combining in the right way might get something going.

Off topic: I have my partner able to send an SMS, which writes a variable, and AutoInput answers my buzzer call and buzzes my partner in, when I don't have my phone in hand or certain times. Tasker's call facilities and overall workflows are interesting and uncanny!!!

[Soudane GMTA]

Thank you very much!

At what point does "Call" become active? Is "Call" also active when "Phone Ringing" start being active, or does "Call" only go to active state when the call is answered?

[Brenden MacDonald]

The userguide says Call is a "call in progress" and is a state as in, has a duration and is present. I think any time the min:sec is ticking in a call this state should be active.

The Phone Ringing is a more transitory thing, even though there is a short duration, so it's an event not a state. At least I understand it this way now.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/mqABXRr3fy4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/3830c308-37a7-4680-b916-a009099d3d45n%40googlegroups.com.

[Soudane GMTA]

Oh, yes ... I overlooked that text in the user guide.

I think that you've given me more than enough useful information for me to accomplishe what I want now.

Thank you very much!

[Soudane GMTA]

Follow-up: How can I tell whether "Phone Ringing" is "active" or "inactive", given that it's an event?

In other words, how can I determine the following, which was stated above? ...

"If Phone Ringing stops being active ... "

???

[Brenden MacDonald]

Hi there!

Take a look at the Phone >events "Missed Call" and "Phone Offhook"

They might be of relevance. Check their documentation in the userguide.

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/0ff05da1-9a44-411d-bf77-7752cfcd9c54n%40googlegroups.com.

[Soudane GMTA]

From the docs ...

Phone Offhook
The phone has just gone off the hook (at least one call exists that is dialling, active or on hold).

Missed Call (Event)

A call has been missed.

This event activates every time there is a new missed call. If you want something to happen until a call has been notified, it's better to use the state Missed Call.

Missed Call (State)

The Android call log has one or missed calls.

If a Caller is specified, only missed calls from that number are relevant (see Pattern Matching in the Userguide).

If you want something to happen every time there is a *new* missed call, use the event Missed Call instead.

None of these seem to be able to give me what I want.

I think that this is another case where I will have to use Logcat Entry to solve my problem.

I'll post my findings after I have time to experiment with this.