Due to changes in Android Lollipop, In order for AutomateIt to monitor active apps it requires an explicit permission from the user. You can do that by going to your device Settings→Security and click on the “Apps with usage access option” (This should be the last item on the settings screen). On some devices, that option is not present (such as LG G3) and on those devices, the “Application State Trigger” cannot be supported.
On that screen, you need to authorize AutomateIt to access the device usage info so it can monitor active apps.
See this link to bug report filed to Google on that matter, that was closed as “Working as intended” by the Android team.
From Lollipop onward, this action will only be supported on rooted devices.
The main change from previous Android versions is that lowering the volume all the way down does not go to silent mode and only affect the ringer volume (meaning, notifications are still playing sounds).
To support this newly introduced feature several adjustments were made and might require additional configuration to be performed by the user.
On rooted devices – we have taken care of that for you and no additional configuration is required.
On non-rooted devices – you’ll need to grant access to your device notification to AutomateIt in order for it to be able to silence them, and switch the sound mode to “None”.
To do that you need to go to your device` settings, Select the “Sound & Notification” option, scroll down to “Notification Access”, click that option to see a list of apps that require access to your notifications, and grant access to AutomateIt.
We recently received several reports that AutomateIt is being falsely identified by several anti-virus apps as malware or as a potential threat.
Needless to say, this is not true.
We have contacted AVG support to verify that the app does not contain any virus or threat, and they have confirmed that AutomateIt should not be recognized as a threat and this will be fixed on AVG next update. See below the full response from AVG customer support:
On some ROMs you might need to install BusyBox for AutomateIt to properly use the “Enable/Disable GPS Action” or “Set Airplane Mode State Action”.
You can easily install BusyBox using apps from the Play Store (such as BusyBox by Stephen (Stericson)).
Once you have BusyBox installed, you need to reboot your device and the issue should be resolved.
Root is used solely for several actions such as “Kill Application”, “Shutdown Device” or on some devices (Android 2.3+) it might be required to turn on/off GPS and Airplane Mode.
It is used since the application does not run in a privileged context and cannot kill other applications or shutdown the device.
If this is something that is of no interest to you, you can just deny root access to the application and all other functionalities will work exactly the same, except you will not see the “Kill Application Action” in the action selection dropdown, and if you already defined a rule that uses this action, it will not show on the application main screen, and of course, will not execute.
You can also check out this post for the source code used for executing root commands in the application.
Enabling or disabling GPS is officially not supported by Google. Up until Android 2.2 (Froyo) this was done in an unofficial way that is no longer available on Android 2.3 (Gingerbread) and above. If you have a device that runs Android 2.3 or above and you don’t have root privileges, this action will not be available. On rooted devices this action will be available.
As for “Set Airplane Mode State Action” – This is not supported by Google since Android 4.2 (Jelly Bean) and will only be available for rooted devices running Android 4.2 or later.
Please visit this post for a more detailed description on how to use the location trigger. most of the times, it’s a matter of using the correct proximity radius for your area, available location providers and location fix accuracy.
The application is not supposed to consume battery since it literally sits and waits for events doing nothing. The only thing that might consume battery in the application is the location triggers, but its battery consumption can be controlled as described in this post.
In most cases where this happens, It’s probably caused by a blank character in the text you’ve defined for the “SMS with Text” trigger. make sure you don’t have any blank space or new line in your SMS text.
The most common cause to of that issue is using 3rd party SMS apps (such as GO SMS, Handcent SMS or Contacts+) that block SMS messages from other apps. To allow AutomateIt to receive the SMS notification, you need to disable this feature from the 3rd party SMS app settings.
To configure Handcent SMS make sure that the “Default messaging application” is set to “Disable”:
To configure GO SMS Pro make sure the “Disable other message notification” setting is unchecked:
To configure Contacts+ make sure the “Default notification” setting is unchecked:
Unfortunately, The short answer is “No”. There are several types of applications that Android requires to run from internal storage due to technical limitations and AutomateIt is one of those apps. For a more technical explanation, see the “Applications That Should NOT Install on External Storage” section on this link.
Since AutomateIt runs a a background process the only way to ensure that the delayed execution countdown will not be terminated is to show a notification on the notification bar. Also, If this notification is removed, you won’t have any way to cancel the delayed execution.
AutomateIt Pro uses the licensing mechanism provided by Google which requires Internet connection once in a few days to validate the license. There are several things you can do to resolve this issue: Make sure your device has Internet connection and reboot your device. In most cases this should resolve the issue. If this does not resolve the issue you can uninstall the app (after making a backup of your rules before they are removed, immediately after reboot) and re-installing the app and restore your rules. If that also doesn’t work, please contact the developer using the “Bug Report” button on the “Support” option of the “More…” menu on the app’s main screen.
When you are using a pattern/password lockscreen this requires confirmation when selecting a notification from the notification bar, due to security limitations by Android.
This does not happen when using a “slide” lockscreen.
There are two ways for reporting an issue with the application and such reports are very much appreciated as it helps me keep improving the application.
One way to report in case of a “Force Close” message is simply by pressing the “Report” button on the popup message. this will submit most of the data that is required to try and resolve the issue.
The other way (Which is more preferable as it delivers more relevant data) is sending us a “Bug report” using the “support” option on the “more..” menu of the main screen as soon as possible after you experience the error or unexpected behavior. This will create an email with a more detailed report and some additional files that will help us trying to resolve your issue.
Please be as descriptive as possible in describing the scenario that lead to having your problem.
|Permission||What is it used for?|
|READ_CALENDAR||Read calendar events for the Calendar Trigger|
|WRITE_EXTERNAL_STORAGE||Read/Write backup files|
|RECEIVE_SMS||Monitor incoming SMS messages for SMS triggers|
|VIBRATE||Required for Vibrate Action|
|BLUETOOTH||Monitor Bluetooth state and connecting devices for Bluetooth triggers|
|BLUETOOTH_ADMIN||Required for Enable/Disable Bluetooth Action|
|CHANGE_WIFI_STATE||Required for Enable/Disable Wifi Action|
|RECEIVE_BOOT_COMPLETED||Start AutomateIt service on device startup|
|ACCESS_WIFI_STATE||Monitor Wifi state for Wifi State Trigger|
|INTERNET||Required to access the rules market|
|ACCESS_COARSE_LOCATION||Required for Location Trigger|
|ACCESS_FINE_LOCATION||Required for Location Trigger|
|READ_PHONE_STATE||Required for Call State Trigger|
|READ_CONTACTS||Required for selecting contacts in various triggers and actions (Call State Trigger, Dial Number Action, Send SMS Action etc.)|
|ACCESS_NETWORK_STATE||Monitor Wifi connection state to wireless networks|
|WRITE_SETTINGS||Change (unsecured) settings such as screen brightness and timeout|
|READ_SYNC_SETTINGS||Required for Enable/Disable Sync Action|
|READ_LOGS||Required for generating an informative bug report sent by the user through the “Bug Report” button on the “Support” screen of the app|
|GET_TASKS||Monitors activated apps for the Application State Trigger|
|CHANGE_NETWORK_STATE||Required for Enable/Disable Wifi Action|
|CALL_PHONE||Required for Dial Phone Number Action|
|SEND_SMS||Required for Send SMS Action|
|PROCESS_OUTGOING_CALLS||Required for Outgoing Call Trigger|
|BROADCAST_STICKY||Required for internal usage (system permission)|
|MODIFY_AUDIO_SETTINGS||Required for Set Speakerphone State Action|
|WAKE_LOCK||Required for internal usage (system permission)|
|NFC||Required for NFC Trigger|
|GET_ACCOUNTS||Required for registering to the Rules Market|
|SET_WALLPAPER||Required for Set Wallpaper Action|
|READ_SMS||Required for SMS With Text Trigger and for using the Last SMS Text keyword|
|READ_CALL_LOG||Required for Last Caller keyword|
|WRITE_SYNC_SETTINGS||Required for Enable/Disable Sync Action|
|DISABLE_KEYGUARD||Required for Enable/Disable Screen Lock Action|
|USE_CREDENTIALS||Required for Send Gmail Action (used for authenticating the Gmail account)|