Auto Call Speakerphone

[Desmanto]

This set of flow is created based on this thread : AutoSpeakerphone during Call with Proximity & Control UI
This require accessibility (Control UI), so make sure you have turn it on for automagic.
Auto Speakerphone

The usage of these 2 flows is to automatically turn on/off speakerphone when proximity is detected near or far during call. To preserve battery life, proximity detection will only be enabled during call, thus requires another separate flow to enable/disable it.

Proximity Auto Speakerphone
This flow consist of two triggers, Proximity near and Proximity far (you maybe need to adjust the value for your phone).

The next expression after the trigger is to split the trigger event, so that we can put 2 triggers into single flow. We use condition expression because it is faster and accurate. At some phone condition Proximity sensor sometimes takes 100-300 ms to complete the checking. While we need our flow to execute as fast as possible. (we are racing with the default built-in screen off)

If proximity is near, for example we put the phone near to our ear; Control UI will turn off the Speakerphone. If proximity is far, for example we put on the table or hold it on our hand; Control UI will turn on the Speakerphone. You must change the Control UI script to match the one in your phone. You phone maybe use another dialer, with another elementId for the SpeakerPhone.

Pro Tips : For those phones with the Action Speakerphone can work properly (as at mine), you can replace the Control UI with Set Speakerphone State On and Off. It works more reliable and don't require accessibility.

Call Auto Speakerphone
This flow consist of 4 triggers (yes, four). They are
1. Incoming Call. State: Off-hook, Numbers: All
2. Outgoing Call: all, Off-hook
3. Incoming Call. State: Ended, Numbers: All
4. Outgoing Call: all, Ended

1 & 2 are used to detect any off-hook (active call), whether it is incoming or outgoing. 3 & 4 to detect ended call. So it covers all scenario. You can delete some of the triggers if you need it only at certain event (example only for incoming).

Next check is expression. Since we have 4 triggers in two pairs, we have to use two expressions. First expression is to check if it is triggered from Off-hook pair, another expression for ended-pair. If it is off-hook, enable the Proximity flow; if ended, disable proximity flow. This way, proximity flow will never consume any battery outside of a call. (where it also serve no use outside of call). You only need to enable this flow to use this 2 flows. Since Proximity flow will be enabled/disabled from this flow.

Testing
You can try it by making a phone call to free of charge number, or just call your nearby person and tell them not to answer the phone. Cover the proximity, you should have nothing (since it is the first trigger after enabled). Uncover it, your speakerphone should be on. Cover it again and speakerphone should be off. This flow won't impact the battery life much, since the proximity is only enabled during call.

Further Modification
Remember this only works on regular phone call. For other VoIP/messenger call, you have to checked on how they give the status of calling. For example, whatsapp will have ongoing notification with text "Ongoing Voice Call", which can be detected using Notification on Status bar trigger. The speakerphone button also must be adjusted to match the app's element.

[Bluscre]

why not use a exception line to use control ui when toggle speakerphone isn't available?

[Desmanto]

For example?

Maybe need to add some if() to check the state. Actually it only need one control Ui. But i make it using expression because someone can use set speakerphone state.

[Bluscre]

http://automagic4android.com/flow.php?i ... 02cd57c0dd

[Desmanto]

Yeah. That will work too if the action set speakerphone gives error. My phone speakerphone action works, so I can't check what happen if the action fail. Thanks for the addition.

[Bluscre]

No problemo ^^ i use the same thing in my API for the screenshot stuff