Requires Rooted Device, Xposed framework installed, latest version of GravityBox Xposed module and an automation app - I use Macrodroid
Create a macro in Macrodroid
Application Launched → select from the drop down list, all apps you want to use on SIM card linked to banking, WhatsApp, Uber etc (5 apps in example below )
Use the trigger Regular interval only. Do not use with any other Trigger. Setup your action, the media tone that is, and use the constraint battery level. You may have to use a logic constraint here, such as AND constraint in MacroDroid specific category.
It had nothing to do with the device settings (but OS bug )
It was a macro misbehaving and reading out for any contact rather than chosen contacts (since the device is always on vibrate wanted audio alert for text messages from chosen few).I never suspected this since a similar macro for incoming calls was working fine
Edit: Shared logs with the developer ...
Tasker can do Airplane mode only in Android 2.2 - 4.0. The application recommends to use Secure Settings plugin and rooted device to get the feature. It would be great to understand why Tasker fails with such a feature in later versions of Android.
The biggest reason why some Tasker tasks are broken on different Android versions is, because it doesn't ...
It appears that MacroDroid now (I've v3.10.1) doesn't go with the approach of installing helper file inside /system as default option. Instead, it now uses it as a backup approach and only when you're having an issue with GPS/NFC. If you've that file inside /system then either it was installed when you were using a version older than v3.10.1 or you ...
I am not sure what went wrong at your end, it could be wrong configuration, misuse of global variables or a silly mistake. In the absence of trouble shooting information, it's a guessing game.
Your approach of changing 63 to 0 as in the title is totally unnecessary.
Outgoing call number is assigned to local variable A as a string (don't use ...
If you want to turn on the Out Loud using automation app, do this:
Leave the rest entries untouched.
If you want to turn off the Out Loud, do this:
If you want to ...
Some phones have a drive mode where the notifications are spoken. You might have a shortcut button from the pull down settings or go into the talkback settings and it should be near the bottom.
If not a drive mode then go into talk back settings , tap verbosity, then unselect speak when screen is off.
See if that is the answer.
I am an avid user of MacroDroid and noticed this issue with two devices and raised this issue on app forums (accessible from within the device and my post dated 24 December 17- unable to link)
This is what the developer said
It's not a MacroDroid issue but a system issue that can happen with any app.
If you Google the issue you will find stuff like this: ...
I recommend using Macrodroid. This has the same functionality as Automate but is much easier to use.
To set up this feature:
Click "Add Macro"
For the trigger, choose Battery/Power. If device is rooted, you can pick the option for when device turns on. Otherwise, you can set another trigger such as "Power button toggle" to do close to the same thing.
Macrodroid has three powerful conditional statements
WHILE / DO , which you tried is not suitable. It doesn't work with OR ( background or foreground ) . That leaves us with
IF <conditions> ELSE which is also not appropriate . Reason you have 4 states , app in Foreground, Not in foreground , Alive in background , Not running - if you choose one state ...
My solution requires sending the intents with superuser (root) privilege and unfortunately, the Send Intent action in MacroDroid does not permit that. So I've used the Script action of MacroDroid as a workaround.
Sending a broadcast (it is universal, not Tasker specific) alone would not do anything here. Using the logcat, I noticed that the app starts the ...
Here is a workaround you could use.
Create a Task to toggle torch ( alternatively get a TeslaLED plugin -it supports a lot of devices).
I am not sure if this is my device limitation but the Hardware state is only limited to media button and not power button but nevertheless I believe the outcome will be the same.
State >> Hardware >> Media button ...