Airplane mode not detected when set by tasker

[psiho]

Hi,

I'm using trial period of this great software and trying to write my
first task/profile on my HTC Desire.

First scenario I want to cover is bringing phone out of airplane mode
in the morning when I get up in the morning. So i created context with
state "Airplane mode" and I do some stuff there. Basically, as soon as
I enter airplane mode by HTC power button, this profile becomes active
so it works fine.

However, after that, I wanted to avoid using power button on HTC to go
to Airplane mode as this is slow. I wanted to use widget instead, to
do it faster. So i made another task, as a menu, and one of those menu
items is a simple task: Airplane Mode set to "on". I created a widget
from this and it works like a charm, click widget, menu pops up, click
"go to sleep" and hone enters airplane mode.

Everything seems to work except one thing... if I go to airplane mode
through widget then profile mentioned above is not activated! If I go
through HTC power button then it gets activated! I cannot figure out
why.

[BossMan]

There are couple of things you can do:
- try replacing the "Airplane mode" context with the state->variable
value context and check if %AIR matches 'on' (http://
tasker.dinglisch.net/userguide/userguide_variables.html) - maybe this
will work,
- you can also modify the idea a bit: instead of turning airplane mode
by a widget, set a variable from there. Then again: a variable-based
context that sets "airplane mode" in its entry task. However, this way
you will have to enter/leave airplane mode always through the widget
to make the profile works.

BR,
A.

[psiho]

Thank you for your answer... your second suggestion is what I was
planning to try. However, my moto is to first try to understand WHY
something is not working before I implement workarround or different
solution. It helps in learning process.

Your first suggestion also seems great alternative, although one
should thing it would behave exactly the same as my method.

Still curious.

[BossMan]

>my moto is to first try to understand WHY
> something is not working

> Your first suggestion also seems great alternative, although one
> should thing it would behave exactly the same as my method.

Exactly - so it's rather to check whether there's an issue with the
airplane mode detection or not.

BR,
A.

[psiho]

Ok, here are the results.

First, I created another menu item that pops %AIR value. Both, after
starting airplane mode by HTC power button and by tasker task, popup
displays same result, %AIR = on

Then, in my profile, I replaced State>Airplane mode context with
state>variable value (%AIR) as you suggested. Now, my profile is
activated no matter what method I use for going to airplane mode!

So, I'm a noob, but this seems like a bug of Airplane mode detection
in State>Airplane mode context?

[Pent]

Thanks very much for narrowing down this problem both of you.

Pent