!C:ANY matches a number not belonging to a contact - NOT WORKING

[Shane Rock]

Not sure if I have something setup wrong or what, this seemed to work fine for me in v4.1, but it is not being detected now.

My overall goal is to setup ringtones for specific contacts - "Known Contact Ringtone" profile

If I don't have a ringtone for a specific person but they are still in my contacts then ring a different ringtone - "Known Contact Other" profile

and lastly if they are not in my contact list ring a default ringtone - "Unknown Contact" profile

That last one "Unknown Contact" I cannot get to run.

Any ideas attached is a picture of the profile is there anything else I could post that might help?

[Mark G.]

What I do is
1) create the profile "state" from "phone" and select "call" and use incoming calls.

2) I enter 0/!C:ANY the 0 blocks restricted and unavailable calls. but you can just use !C:ANY

3)then run a task from "phone" and selec "end call" and the message goes to my voice mail.

If you wanna completely hang up on those rat basards!! Do this..

from the task "Phone"
1) Take call

From the task "Task"
2) use "wait" (I set it to 1 sec)

From the task "Phones" again.
3) end call.

You can also run a sms task after telling the person why you've hung up. Hope this helped

[Shane Rock]

my problem is the !C:ANY condition isn't being met

[Mark G.]

Oh my bad, didn't have my glasses on and only looked at your screenshot.

You can try using Events and select "ringer" if you didn't already.

[Matt R]

Start with the run log (menu > more > run log).  It should help determine if the profile is not activating or if the task is failing.

Matt

[SunKol]

Please try changing your profile with "Phone Ringing" Event Rather "Call Incoming" State.

[Shane Rock]

I was able to get get it to work, but I first had to uninstall tasker and delete its folder and reinstall it, I ended up getting to work with the events - phone ringing profile.

don't know what was wrong before, it was like tasker was running old profiles i had already deleted?? oh well its working now

thanks!

--
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/WujCWI001Lw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Carlos Federico WOLFF]

Is "!CG" working for you? "!C:ANY" works, but i think there is a problem when trying to check a contact NOT belonging to a specified group. Thank you very much.

[Shane Rock]

yes !CG is working for me.

On Fri, Dec 5, 2014 at 8:00 AM, Carlos Federico WOLFF <wfc...@gmail.com> wrote:

Is "!CG" working for you? "!C:ANY" works, but i think there is a problem when trying to check a contact NOT belonging to a specified group. Thank you very much.

--

[SC]

I hope I am not highjacking this thread, but just want to add that I am having a similar issue.

Both !CG and CG work for me, and so as C:ANY, but somehow !C:ANY didn't work consistently.

By that I meant some contacts will match both C:ANY (correct behavior) and !C:ANY (incorrect behavior).

I tried the same profile on 3 different phones on 3 different version of Android and they all gave me the same wrong results so I am pretty sure it is not a phone/OS specific issue.

Anyway my profile is very simple, basically just a trigger on 'Phone Ringing' event' with a pattern of '!C:ANY' and a task to display a notification. Tasker would constantly trigger the task despite calling from a phone that matches one of the contacts. Also tried changing the trigger to 'Call Incoming' but then the task would not get triggered at all, even when calling from a number that is not a contact (i.e. wrong behavior).

When I changed the pattern from '!C:ANY' to 'C:ANY' using 'Phone Ringing' event, calling from the same number would trigger the task correctly, so tasker seemed to know that the number is from one of the contacts.

Basically looked like there is a bug when the not condition (!) is applied to the pattern 'C:ANY'.

[Marta Hintz]

Are you sure you backed out of tasker when you made those changes?

[Marta Hintz]

Also check the log file to see if something is wonky there.

[SC]

On Tuesday, December 9, 2014 10:08:01 AM UTC-5, Marta Hintz wrote:

Are you sure you backed out of tasker when you made those changes?

I wish it is that simple :-(

Like I said I tested the issue on 3 different phones with various stock and custom roms. None of them works consistently.

I am wondering how Tasker perform the comparison. Does it require all digits/space/symbol to match? All my contacts are in the standard international format (i.e. +1 xxx-xxx-xxxx). Is Tasker smart enough to know how to deal with them if the number in the caller id is not exactly the same? For example will it be smart enough to know a calling number '123-1111-2222' is the same as '+1 123-1111-2222' in the contact?

[Carlos Federico WOLFF]

Finally, I can see that "!" with a group works with Samsung Groups (my phone maker), but not with Googles Group. Google groups seems not being corectly evaluated when using "!", otherwise they work ok.

Thx.

[SC]

I think you maybe on to something. I found like if I edit the number (add a dash and then remove it) in my contacts locally on the phone, then Tasker will evaluate the number correctly. However after a few syncs then the problem will be back again.

[mkraft]

I am experiencing the same problem as in the OP. A Call Incoming context for !CANY fails to trigger for callers who are not in my contact list - but does trigger a Phone Ringing context:

//This one does not work

Profile: Test (114)
	State: Call [ Type:Incoming Number:!C:ANY ]
Enter: test (100)

//This one does
Profile: Test2 (115)
	Event: Phone Ringing [ Caller:!C:ANY ]
Enter: test2 (121)

I first noticed the issue in mid October last year - it worked properly prior to that time. I have tried a complete uninstall/delete the Tasker folder/reinstall, with no success.

Unlike the original poster, having to use Phone Ringing is not very convenient for me - I need a state with both entrance and exit tasks, not an event.

Has anyone seen this or have a solution?

Phone: Nexus 5 w. stock Android 4.4.4
Carrier: Rogers Canada
Tasker: 4.6u2

Thanks.

[mkraft]

To be more clear, the following profile also fails if the caller is not in my contacts list:

//This also does not work

Profile: Test3 (154)
	State: Call [ Type:Incoming Number:* ]
Enter: test (100)

I.e., if the caller is not a contact, as far as Tasker and Call Incoming are concerned, the call never happened.

[Darren Becker]

I have the Nexus 5 running stock OS and for some reason Take Call option is Red and doesn't allow me to select it. Is there any way to fix this?

[Pent]

I am experiencing the same problem as in the OP. A Call Incoming context for !CANY fails to trigger for callers who are not in my contact list - but does trigger a Phone Ringing context:

I first noticed the issue in mid October last year - it worked properly prior to that time. I have tried a complete uninstall/delete the Tasker folder/reinstall, with no success.

I havn't been able to reproduce this at all. I suspect something changed on your phone or with your carrier. Could you send me a log when it fails ?

http://tasker.dinglisch.net/userguide/en/faqs/faq-how.html#x2

Thanks,

Pent

[mkraft]

It happened at about 10:24 this morning. Before and after log files and the crash report are attached.

[mkraft]

Hi Pent,

Any updates?

Thanks

[Luis Gómez Guzmán]

If i want to exclude one specific contact, should i use: !contactname ?