Silence mode by putting phone upside down

[Lesept]

Hello

I tried to make a new profile for putting the phone in silence mode
(for meetings) when it's upside down. It's quite simple but I think
the accelerometer gets lost when I have the phoen in my pocket, and
then I miss some incoming calls.
Would there be any possibility to add a condition such as "if the
phone didn't move in the last second" and "if it's upside down" then
"silence mode" ?

Can anyone help me ?
Thanks

Lesept

[Pent]

> I tried to make a new profile for putting the phone in silence mode
> (for meetings) when it's upside down. It's quite simple but I think
> the accelerometer gets lost when I have the phoen in my pocket, and
> then I miss some incoming calls.

I think it's more likely that the phone was face down, it went off
(display timeout), (so the accelerometer was turned off to save
power), then you put it in your pocket ?

Pent

[Fabrice Auzanneau]

Yes this is possible. Then I should turn the sound on again when the phone is moving? How can I do this?

[Chris Cowles]

Do I understand your explanation correctly? If the phone is already silent from bring face down, does it not exit that context when I pick it up to put it in my pocket? Do I have to turn on the screen to make that happen?

__
Chris Cowles
Gainesville, FL

-----Original message-----

[Fabrice Auzanneau]

Actually I added an exit task to put the sound back on and vibrate a little so I can check it is done. But I still miss some calls.
I don't think the phone was still silent when I take it and put it in my pocket. I really think that the accelerometer believes the phone is upside down. It would be interesting to know what "upside down" means for the accelerometer by the way...

[Lesept]

Hello

Could anyone send me a working profile for that, as it seems that mine
is not working ?

My profile is (sorry I translate from French) :

Condition : Orientation - Face down
Task : Silent mode, vibrate
Exit task : Silent mode - Off / Vibration 44 (to tell me it did it) /
Vibrate on call : On

As is, when the phone is upside down, when someone calls me, sometimes
I get the first notes of the ring (mp3 file) sometimes nothing even no
vibration. And when I have the phone in my pocket, it often doesn't
ring when someone calls.

[Randy Cohen]

I just bought Tasker. This was the first task(er) I tried...

New Profile | State | Sensor | Orientation | Is Face Down

New Entry Task name "Going Face Down"
If %FACEDOWN = 0
Vibrate 250ms
Silent Mode On
Popup | No Title | Center Text | "Silent Mode" %SILENT
Display Timeout 10 Seconds
Variable Set %FACEDOWN 1
endif

New Exit Task name "Going Face Up"
if %FACEDOWN = 1
Silent Mode Off
Play Ringtone | Type Notification | Sound Charming Bell
Popup | No Title | Center Text | "Silent Mode" %SILENT
Display Timeout 10 Minutes
Variable Set %FACEDOWN 0
endif

It's not clear to me if the Face Down context is a one-time event that
occurs only on the state transitioning to "Face Down" or if the system
periodically issues the same event as long as the physical condition
is Face Down. It looked like, with my first attempt, the event
repeated so long as the phone was face down. If I held the phone in
the air and watched, the Ringer Volume would appear about 1/second. I
added the %FACEDOWN variable to act as a semaphore so I only get one
execution at a time.

I've noticed the Display Timeout doesn't appear to work as I
expected. The value is being set correctly, but it doesn't take
effect until you go to Settings | Sounds once. Maybe there's some
other command I'm supposed to throw to make a settings change take
effect?

I've looked at when the phone "thinks" it's face down or up, and it's
a pretty narrow range of positions. But in my pocket or belt holster,
sitting in my car, it might easily think it was upside down enough. I
need to make sure I put my phone in the holster face-out to prevent it
from thinking it should go silent.

[Lesept]

I added some short vibration patterns to see how it is working, and I
saw what is going wrong.
If the phone is on, when I turn it upside down, it actually goes to
silent mode, and if I turn it up it comes back to normal mode.
BUT : if I shut the phone off (simply pushing the on/off button, not
turning it off completely), and after that if I turn it upside down,
nothing happens. The profile is not triggered. If someone calls, the
phone wakes up, the profile is triggered but it takes a fraction of a
second to go to silent mode, which is why I ear the first few notes of
the ring.

I don't understand why Tasker behaves like this in this case, because
another profile I have (wifi on when at home) works perfectly even if
the phone is off when I get home.

My objective for this profile is to prevent the phone from ringing
when someone calls if I'm in a meeting (it can vibrate but not ring),
I can tell him to behave so by turning it upside down. But I usually
turn it off (simply pushing the on/off button, not turning it off
completely) before putting it on the desk upside down. So it doesn't
trigger the profile and doesn't work as expected.

What is wrong with my profile ?

[BossMan]

From the userguide: http://tasker.dinglisch.net/userguide/en/help/sh_index.html

Orientation

The device is in the specified orientation. 

Orientation is not checked while the device display is off in order to conserve power.

BR,

A.

[Steven Porteous]

I've got a similar profile working but I need to have accelerometer alway on on my Galaxy Nexus (Screen Off) but it works "only on power" on my dad's Nexus 4,Any advice to how better configure the accelerometer on my Galaxy Nexus, as it should be active when the screen is on (phone ringing) anyway?  

[Brandon Horwath]

This is WAY off topic... but, congratulations on applying the word 'semaphore' in a technologically modern context. That was good... didn't know it was possible but well done.

[Ivelin Ivanov]

http://en.wikipedia.org/wiki/Semaphore_%28programming%29 :)

On Tuesday, July 16, 2013 5:34:05 AM UTC+2, Brandon Horwath wrote:

This is WAY off topic... but, congratulations on applying the word 'semaphore' in a technologically modern context. That was good... didn't know it was possible but well done.

To the previous poster(s) - in the Tasker's Preferences, Monitor tab, when you scroll way down there is the setting for the accelerometer - by default it's set to only work when the phone is charging. Try to set it to yes, though according to the help popup next to it, that still might not work for some devices. Also be aware that if you set it to yes and it works, you might get a significantly higher battery drain.


@Pent - if you could, maybe add the accelerometer setting to Action -> Tasker -> Set Tasker Pref. so we can automate when to activate it and when not, in order to save some battery?

[Steven Porteous]

Thanks Ivelin I know that, I was asking how to better calibrate it with my Galaxy Nexus, as the same profile works fine on a Nexus 4(not on all the time) also why do I need to set the accelerometer to on all the time ? When the phone rings the screen is on (Incoming call) so why should I need it set to always on?

I like your suggestion for the accelerometer

[Steven Porteous]

Have reduced Orientation State Accuracy and is working ok.

[Sam]

while this may come from the userguide i can personally verify that this is not actually the case...

 

i have a profile that pauses my xbmc player when the phone is oriented face down...

 

while the display is active this is nearly instantaneous...

 

however, with the orientation facedown and the display off i can wait up to the minute (that i have set in the prefences) between checks that  tasker performs after display is set to off...

 

it always works...  but it may take upto one minute if the display is off...

[Sam]

i retract that...  upon a short check...  tasker will perform the check while the screeen is off upto the the specified time...  so it is possible that the check is performed twice if orientation changes while the screen is off... 

 

however, checks are performed after the screen is off...

On Monday, November 7, 2011 6:22:34 AM UTC+9, BossMan wrote:

[Sam]

will gladly post a video demonstrating the point if you would like...

On Monday, November 7, 2011 6:22:34 AM UTC+9, BossMan wrote:

[Sam]

confirmed:  if orientation changes between to checks while the screen is off the task will trigger...  leading to his problem

On Monday, November 7, 2011 6:22:34 AM UTC+9, BossMan wrote:

[Sam]

further confirmed continuous orientation between off screen check will not lead to triggering of the task...

 

so basically the problem is he is moving his phone aroung setting different orientations between screen off checks and as a result setting the task to fire again...

 

and again despite the userguide i would be glad to provide a nice video demonstration....

 

On Monday, November 7, 2011 6:22:34 AM UTC+9, BossMan wrote: