help with a profile for a semi noob.

[gkf9]

Would any one be kind enough to help me achieve a Profile, I'm a noob but have managed to do some of the simpler stuff in tasker.

I have the app "Carhome Ultra" and so far I've set it up as: State - Orientation -Left side down then opens the Carhome app. Now after this what I want to achieve is for it to auto answer any incoming calls from callers I know, and for it to read out any texts I receive and then an auto reply to tell the person "I'm driving etc"

I got it half set up, but didn't work right. Would really appricate someones help thankyou ..

 

[SUroot]

You might need to explain more about the "Carhome ultra" app. Does this offer the reading of SMS and auto-answer of calls or are you expecting tasker / Android to handle that?

 

[gkf9]

You might need to explain more about the "Carhome ultra" app. Does this offer the reading of SMS and auto-answer of calls or are you expecting tasker / Android to handle that?

No the app doesn't answer calls or read notifications etc, basically just gives you short cuts to maps, contacts etc. I want tasker to handle it all, but whilst I was in the app kind of thing, if that makes sense?

 

[gkf9]

No the app doesn't answer calls or read notifications etc, basically just gives you short cuts to maps, contacts etc. I want tasker to handle it all, but whilst I was in the app kind of thing, if that makes sense?

Ps, I want tasker to know I'm in the car, so thought the various tasks would only trigger whilst in the app.

 

[SUroot]

I would probably have when that app opens, another part of the task that sets a variable called %CarMode to "on" or "1" or something...

So edit your existing carmode task (from profile screen press the task in question and "edit")

That task would be Variable > Variable Set then name it CarMode (Leaving the % in place so its %CarMode) and set To "on" or "1".

Then you need to add an exit task to it so again press the task from the profile screen and "add exit task". This then wants to be the opposite of what you did. So when the state is no longer true (orientation is back to normal) the exit task will variable set %CarMode to "Off" or "0"


THEN... hahaha...

Then you need a new profile (this will do the auto answer)

context 1 > state > Variable > Variable Value
Find the variable %CarMode in the name section using the tag icon...
The Value you want is "On" or "1" (whatever you chose earlier...)

Context 2 > event > Phone > Ringing (set caller to "any contact")

Task > Phone > Take call

 

[SUroot]

Ok and for the SMS I tested this and it seems ok...

context 1 > state > Variable > Variable Value
Find the variable %CarMode in the name section using the tag icon...
The Value you want is "On" or "1" (whatever you chose earlier...)

Context 2 > event > Phone > received text, Type "SMS", Sender "Any contact"

Task > Misc > Say

The text could be

"%SMSRF, sent %SMSRB" But you can pick from variables Such as "Text from", "Text Body" etc etc (tahst the two i used here)...

 

[gkf9]

Just working my way through it, but in the last but "variable Value" its asking for an "OP" what do i put in? thanks .

 

[gkf9]

SUroot

Your a star! Thank you very much, all works a treat.
I don't suppose you can do me another favor? Can you explain in simple terms what the variables with values do in the profiles you wrote for me. I've read and read till I'm blue in the face trying to understand variables?!
It's really frustrating not knowing what's doing what, I've got a fairly basic idea and for anyone who's not programmed before it's a learning curve.

Thanks again for taking things out.

 

[SUroot]

No worries.

Imagine a variable is actually a text file. This text file can contain text. So what you are doing when orientating the phone to the left, is putting something in a text file. We are putting "on" or "1" in the text file.

With it so far?

Lets just say we used "on"

OK so the other 2 profiles need to be triggered to react when an SMS comes in or when a call comes in. However, with just these contexts, it would happen all the time, regardless of what orientation the phone is in. So what we did here is added a second context which is based on the text file saying "on" in it.

So basically...

Phone Call + Text file says "on" > Auto answer. If the text file doesn't say "on" it wont auto answer.

So its just a way of controlling the profiles for phone and sms so they only do it when we want, which is when the text file says "on". To make sure the text file doesn't always say "on", we set it to say "Off" when we flip the orientation back. So when a call comes in, the text file says off and is NOT auto answered.


Hope this helps.

Its also worth noting, variables all in CAPS are built in variables. You can create your own just like we did, naming it anything. Just be aware that if you want to access it from other tasks, it must contain at least 1 capital letter (but cant ALL be capital letters)

 

[bberryhill0]

Actually user created global variables can be all caps if they don't conflict with system variables. But don't do it. It makes things very confusing.

 

[gkf9]

No worries.

Imagine a variable is actually a text file. This text file can contain text. So what you are doing when orientating the phone to the left, is putting something in a text file. We are putting "on" or "1" in the text file.

With it so far?

Lets just say we used "on"

OK so the other 2 profiles need to be triggered to react when an SMS comes in or when a call comes in. However, with just these contexts, it would happen all the time, regardless of what orientation the phone is in. So what we did here is added a second context which is based on the text file saying "on" in it.

So basically...

Phone Call + Text file says "on" > Auto answer. If the text file doesn't say "on" it wont auto answer.

So its just a way of controlling the profiles for phone and sms so they only do it when we want, which is when the text file says "on". To make sure the text file doesn't always say "on", we set it to say "Off" when we flip the orientation back. So when a call comes in, the text file says off and is NOT auto answered.


Hope this helps.

Its also worth noting, variables all in CAPS are built in variables. You can create your own just like we did, naming it anything. Just be aware that if you want to access it from other tasks, it must contain at least 1 capital letter (but cant ALL be capital letters)

Yes it helps a lot thanks.
Think I've got the basic idea, so numbers "1" and "0" are language for "On"and"Off "?

I've downloaded a few samples off the wiki page, I'm going to have a lot through them and try to understand how they work.

Once again thankyou for taking the time to help me.
Love this phone, (coming from Apple) and love the forum for its help.

 

[SUroot]

Yes and no.

"1" and "0" are universal language for on and off and that is also how computers process. It's called Binary. Bursts of electricty (1's) and spaces between the bursts (0's)

If you look at Kettles and Guitar amps, often they have a switch with a 1 for on at one side and a 0 at the other for off. Even the universal icon for standby on TV remotes, computers etc is made up of a 1 and a 0

However, I used "On" and "Off" or "1" and "0" simply because of the above logic, so we can see at a glance what the variable says (what state it is in). The text within the variable could have been anything.

For example, when we orientate the phone left, the variable could be called %YGutfyfya and we could set it to "HaricotVert" Then we set the context to look for "HaricotVert". It could literally be anything, but logic tells me "on" and "off" makes more sense or "1" and "0" if you can't be bothered typing 2 or 3 characters in the task