'Quiet mode' on MyTouch Slide - auto canceling?!

[Dave]

Like everyone else, I tried the example quiet mode from the review. I
thought it wasn't working, but it seems it is...

I struggled with it, then finally added a notification to see if it
was firing. It was. So then why was the volume always up? I tried
different paths do quiet the phone, and finally did Silent Mode = ON.
After a couple tests, I finally caught a brief glimpse of the silent
mode icon in my notification area, just as it disappeared.

Getting smart, I held the phone above my head so I could see what it
was doing when face down. Silent Mode = ON comes on, as does Silent
Mode = VIBRATE. However, when you flip it off of the face down
orientation, the Silent Modes are automatically cancelled.

It is actually doing exactly what I would like, but I don't understand
why. I don't have an exit task, nor a Not Face Down task. What is
cancelling the Quiet Mode?

Later that same day...

Did some further testing after reading notes regarding the orientation
setting not working with the screen off. I turned off the screen, and
face-down is not detected, or whatever the problem is. Next, I
decided to let the screen time out. So, Tasker entered Quiet Mode and
the screen turned off. I tested it with text messages.

Face down, already in Quiet Mode, it will exit Quiet Mode after about
3 minutes. I suppose that is about 2 minutes after the screen goes
off. This pretty much negates the usefulness of Quiet Mode.

Odd behavior, at least non-intuitive.

Dave

[BossMan]

What contexts does your profile use?

Also, there will be some changes related to orientation monitoring in
the next version - see this thread
http://groups.google.com/group/tasker/browse_frm/thread/6db3cc02e1e92121/5badcdefe4a9c7d4?#5badcdefe4a9c7d4
and http://tasker.dinglisch.net/nextversion.html

BR,
A.

[Dave]

This profile uses the Orientation -> Is Face Down context.

I saw the discussion about the next version, but this seemed bullet
most applicable:

http://tasker.dinglisch.net/nextversion.html
* orientation/gestures contexts monitor immediately after screen on
(don't wait for unlock)


It's interesting, in that this seems to pertain to the detection of
orientation while the screen is alive but locked. My situation is
happening whether or not the screen is locked or the phone is dormant.

On Jul 30, 8:44 am, BossMan <adam.marynow...@gmail.com> wrote:
> What contexts does your profile use?
>
> Also, there will be some changes related to orientation monitoring in

> the next version - see this threadhttp://groups.google.com/group/tasker/browse_frm/thread/6db3cc02e1e92...
> andhttp://tasker.dinglisch.net/nextversion.html

[Marcus]

As far as I know those actions with that small gear symbol
automatically turn back to their original setting when the context is
over.
Events should be the only exception to it.

So this should be right behaviour.

[Marcus]

Found the part of the userguide:
http://tasker.dinglisch.net/userguide/userguide_settings.html

When a setting is applied by the Enter Task, it's value is restored
when the profile becomes inactive. For example, if the ringer volume
is at 7 and is set to 0 in the Enter Task, when the profile becomes
inactive it is automatically set back to 7.

[Pete Scott]

That's exactly correct. If for some reason you need to bypass this
behavior: create a named task that performs the action (ie: set ringer
volume to 0). Then in your enter task have tasker execute that named
task. This will prevent Tasker from restoring the setting upon
exiting.

Unless, of course, I'm wrong. In which case one of those erudite
fellows (Pent, UncleMike, Stefan, et cetera) will surely come in here
and correct me.

[Marcus]

Try this (haven't tested this):
use your face down context to set a custom %FACEDOWN variable to 1.
Then add an event and select variable set. Use your %FACEDOWN
variable.
In the action you can change silent mode to on when %FACEDOWN is 1 and
perhaps also add silent mode again and set it to off when %FACEDOWN is
0
This way you can use this one event (that's why I didn't use the value
for the event itself) to turn it on and off (using another context,
e.g. certain caller id).

face down -> variable set to 1 -> fire variable set event -> silent
mode on when variable = 1 (-> continue to 2nd action -> don't turn
silent mode off cause variable != 0)
important caller id -> variable set to 0 -> fire same variable set
event -> do not turn silent mode on cause variable != 1 -> continue to
2nd action -> turn silent mode off when variable = 0


Perhaps this will work.
Hope you can understand it. :D

[Marcus]

ok tested it and it does work.
you also don't have to worry about setting the variable back to
something else again.
it will fire again when you set it to 1 again.


Here is what it would look like:

Context: State: Face Down
Variable Set: %FACEDOWN = 1

Context: Event: Variable Set %FACEDOWN
Silent mode: on if %FACEDOWN = 1
silent mode: off if %FACEDOWN = 0 (<- if you want some special
context to turn it off automatically, put it on its face again and it
is silent again)

[Calvin]

Nice to have these workaround.
But it still leaves the question: why does it leave quiet mode after 3
minutes?
Sounds like a bug to me.
Or am I missing something here?

On Jul 30, 3:17 pm, Dave <hathaway.d...@gmail.com> wrote:
>

> Facedown, already in Quiet Mode, it will exit Quiet Mode after about

> 3 minutes.  I suppose that is about 2 minutes after the screen goes
> off.  This pretty much negates the usefulness of Quiet Mode.
>

> Dave

[Dave]

That was my thought as well. It is NOT leaving facedown orientation.
It is entering a sleep mode while still facedown. Thus, it may not
detect that it is faceup if that happens while it is asleep, but
surely it should still be in facedown mode until it wakes up.

Dave