automatic speakerphone -- is this the best way?

[Shane]

I got this idea from a comment posted at lifehacker. I created a task
that turns the speakerphone on when the orientation is face up. The
only potential downside that I see is that this task activates
whenever the phone is face up -- regardless of whether or not I am on
a call. Is that okay? If not, is there a way to make this task only
activate if the phone is face up AND I am on a call?

[Pent]

Event: Phone Ringing
Variable Set, %INCALL, 1

Event: Phone Offhook
Variable Set, %INCALL, 1

Event: Phone Idle
Variable Clear, %INCALL

State: Variable Value Is Set %INCALL
State: Orientation: Face Up:
Action: Speakerphone

That's a bit clumsy, it will get easier in the future.

Pent

[Shane]

Thanks for the quick reply. I'm still new to this so I need a little
more guidance. This solution would actually be 4 profiles correct?
With each of the Events being their own profile and the two states
being part of one profile?

[Pent]

> Thanks for the quick reply.  I'm still new to this so I need a little
> more guidance.  This solution would actually be 4 profiles correct?
> With each of the Events being their own profile and the two states
> being part of one profile?

Yes. To add the other state, click on the existing one and select Add.

Pent

[Shane]

What is the advantage of your way verses just doing one profile like
below?

Event: Phone Offhook

State: Orientation: Face Up:
Action: Speakerphone

[JJay]

Pent's example is using two starting events and one ending event to
create a certain state inbetween, for the full duration of the call.
My guess would be the event you use is not working for the full
duration of the call. Or is it?

If so: Hooray! I like the profile and add it to my phone as well.
I use the opposite (face down) for silent mode in meetings, they'll
combine perfectly together...

[JJay]

And maybe he added the ringing event for incoming calls, the offhook
event might handle outgoing calls only (?). I'm pretty sure he has
some good reason :)

[Pent]

> What is the advantage of your way verses just doing one profile like
> below?
>
> Event: Phone Offhook
> State: Orientation: Face Up:
> Action: Speakerphone

Events are a little bit special. They only last a millisecond, so they
don't do settings restoration.

That profile says 'if the phone is face up, then when the phone goes
offhook set the speakerphone on'. The speakerphone will
stay on.

If you don't care about speaker phone while the phone is ringing, you
can skip the Event: Phone Ringing profile I mentioned though.

In the future, I plan to make 'Incoming Call' 'Call In Progress' so
you won't need to use the messy events and variables.

Pent

[JJay]

Thanks for the explanation, the workaround works perfectly.

> In the future, I plan to make 'Incoming Call' 'Call In Progress' so
> you won't need to use the messy events and variables.

I kinda like creating these custom vars anyway (for using as a
condition in other tasks, contexts, etc.), so no complaints here :)

[Aaron]

I am attempting to use this in conjunction with a "Juice Defender"
type profile that turns on airplane mode when the screen is off. Even
though I added Wait Until %INCALL does not match 1 to that task, the
task continues no matter what.

Is there a better, more reliable way to indicate an "in call" state
currently (or planned)?

On Sep 5, 10:19 am, Pent <tas...@dinglisch.net> wrote:
> Event: Phone Ringing
> Variable Set, %INCALL, 1
>
> Event: Phone Offhook
> Variable Set, %INCALL, 1
>
> Event: Phone Idle
> Variable Clear, %INCALL
>
> State: Variable Value Is Set %INCALL
> State: Orientation: Face Up:
> Action: Speakerphone
>
> That's a bit clumsy, it will get easier in the future.
>
> Pent
>
> On Sep 5, 4:13 pm, Shane <seck...@gmail.com> wrote:
>
>
>
> > I got this idea from a comment posted at lifehacker. I created a task
> > that turns the speakerphone on when the orientation is face up. The
> > only potential downside that I see is that this task activates
> > whenever the phone is face up -- regardless of whether or not I am on

> > acall. Is that okay? If not, is there a way to make this task only

[Adrian Amoroso]

On Monday, 6 September 2010 18:27:06 UTC+10, Pent wrote:

<snip>

Events are a little bit special. They only last a millisecond, so they
don't do settings restoration.

I have the same profile as Shane suggested, except that I use the Phone Call state rather than an event.  Seems to work fine for me :)