Troubleshooting

Follow these steps in order to help debug your situations.

1. Is the background service running?

If Locale’s background service isn’t running, then none of your situations will run.

Open Locale and check the Overview screen. There is a card which shows the status of the background service including when it started and why.

If Locale’s service isn’t running, the app will appear to “wake up” when you open it and you’ll see a message that Locale started when you opened the app. If this happens, most likely a “battery saver” or “memory cleaner” is stopping the app. These usually kill apps if you haven’t opened them for a few days, which can make the issue seem inconsistent.

Please visit our Battery Savers page for instructions on how to disable these on various Android devices.

2. Is the situation enabled?

Situations can be turned off by unchecking the “Monitor conditions and apply settings” in the Edit Situation screen. Please double check that your situation is enabled.

Disabled situations also have a gray dot in the situation list. You can tap on the dot to access another view to update the situation’s enabled state.

3. Are the conditions being detected?

If Locale’s background service is running, look to see if the situation is becoming active. A situation becomes active when at least one condition of each type in the situation is true.

Example: A situation has a Location condition and a Time condition, then it will only become active when BOTH conditions are met. If the situation is not becoming active, the problem is with the conditions. Some questions to ask:

4. Are the settings being fired?

If the Situations are listed as active, then the settings will be fired when the situation becomes active.

You can see which settings were fired (and when) from the overview screen in Locale.

If you don’t see the correct setting listed:

If you do see the setting listed, but the actual settings aren’t correct: