LocaleĀ® is available as a paid app on Google Play. The latest version of Locale is 6.2.4 (release notes).


With LocaleĀ®, you get what you pay for: Locale is fast, accurate, reliable, secure, and battle tested. We stand behind our app 100%.

For help with downloads, installs, refunds, payments, account transfers, or store access, please contact the Google Play team through the Google Play Help Center. We do not have the ability to administer your Google Play account.

For help with third party Locale plug-ins, please contact the plug-in developer directly.

For technical questions regarding Locale we recommend using Locale's in-app priority support feature: open Locale and choose "Contact support" from the menu or Action Bar. This will attach information about your setup to your inquiry so that we can help more quickly. You can also email us anytime at up@244.am, however you will receive a significantly faster resolution to your inquiry by using Locale's in-app priority support feature.

Disable Battery Savers

"Battery saver" apps and tools disrupt many features of Android and may prevent Locale from working properly. Be sure to whitelist Locale from these battery savers, so that the app can run reliably. With thousands of different Android devices, these instructions may vary slightly depending on the exact Android device model.

  • Samsung

    Open the Smart Manager app > Battery. Under the App Optimization section, tap Detail. Tap on Locale in the list of apps. Select "Turned off for" to disable. Repeat this for any plug-ins for Locale.

  • OnePlus

    Lock Locale in Task Switcher: Open Locale. Tap the task switcher button, to the right of the Android Home button/fingerprint reader. Tap the Lock icon in the top right corner so that it is locked.

    Disable aggressive doze: Go to Android Settings > Battery. Tap on the overflow menu and choose "Aggressive doze & app hibernation." Either turn off Aggressive doze & app hibernation for all apps, or check the box next to Locale to move it to the Not optimized category. Repeat this for any plug-ins for Locale.

    Disable auto close high power usage apps: Go to Android Settings > Battery. Tap on the overflow menu and choose "High power usage apps." Turn off "Auto close high power usage apps."

    Allow auto-launch: Go to Android Settings > Apps. Tap on the gear icon in the Action Bar. Scroll to the bottom and go to Apps auto-launch. Either disable Apps auto-launch or check the box next to Locale to move it to the Allow auto-launch category. Repeat this for any plug-ins for Locale.

    Enable normal recent app management: Go to Android Settings > Advanced. Tap on "Recent app management." Choose "Normal clear."

  • Huawai

    Add Locale to Protected Apps: Go to Android Settings > Advanced Settings > Battery Manager. Add Locale to the list of "protected" apps, so that it can run when the screen is turned off. Repeat this for any plug-ins for Locale.

    Prevent Locale from being closed: Go to Android Settings > Advanced Settings > Battery Manager. Tap the Gear icon in the top right corner of the screen. Check "History of closed apps" to see if Locale is shown in the list. If yes, then disable the option for "Close excessively power-intensive apps."

  • Sony

    Go to Android Settings and disable Stamina Mode.

  • ASUS

    Allow auto-start: Open the Auto-start manager app. Set the box next to Locale to "allow". For further instructions, see ASUS documentation

Frequently Asked Questions

  • Why does it sometimes take a while to update my situation?

    Locale's built-in conditions--Battery, Calendar (Android 4.0+), Caller, Charger, Movement, Orientation, Location, and Time--will update almost immediately. Some third party plug-ins may take a few minutes to detect a change. If you have questions about the performance of a third party plug-in, please contact the plug-in developer directly. Opening Locale forces refresh of all conditions including plug-ins, which is why opening Locale sometimes seems to "make it work."

    If Locale frequently seems to not detect changes, make sure that Locale is running by pulling down the Android notification area and confirming that Locale's ongoing notification is displayed. If Locale's notification is not displayed, a "battery saver" may be preventing Locale from running. Please see the "Disable Battery Savers" section.

  • Why won't my situation change? IT'S NOT WORKING >:(

    Usually this is just a minor misconfiguration of the situations. Let's narrow the problem down:

    1. Is the problem with the conditions or the settings? Look to see if the situation is becoming active. Active situations are indicated by a colored dot in the situation list. In addition, active situations are listed in Locale's ongoing notification in the pull-down notification area. If the situation is not becoming active, the problem is with the conditions. If the situation is becoming active, but not behaving as expected, then likely the problem is with the settings.
    2. Can you try something simpler? Try replacing all of the Conditions with something like the Charger condition and replacing all of the Settings with a Volume setting. This should work reliably, and provides a good baseline to start with.
    3. If you're using a third party plug-in, try seeing if a situation using only Locale's built-in conditions and settings works. Some third party plug-ins are buggy and do not work correctly. If you have questions about the performance of a third party plug-in, please contact the plug-in developer directly.
  • Why won't Locale detect my location?

    Locale uses patented artificial intelligence algorithms in combination with cell towers, Wi-Fi, GPS, accelerometer and other data to instantly determine your location, while using practically zero battery power. Arriving at a location should be detected almost instantly. Leaving a location may take a few minutes to detect, in order to conserve battery power. If Locale does not update your location, there could be bad location data in your area which can be corrected with Calibration, described below:

    1. Every once in a while, stale or bad data needs to be corrected through calibration. Calibration will not only correct bad location data, but it can also reduce battery usage by helping Locale avoid using GPS. To perform calibration, choose "Calibrate" under the menu or Action Bar of the Location condition. Pick a nearby Wi-Fi access point, and then drag-and-drop the pin to the right spot. If the pin is way off (e.g. hundreds or thousands of kilometers off), zoom out to move the pin long distances. Then, zoom back in to position it precisely. It does not matter if the access point is secured. It does not matter if the access point has Internet access. Locale merely uses the presence of the access point as a reference point; Locale does not connect to it. After calibration, you do not need to leave Wi-Fi enabled. Calibration will not increase Locale battery usage, and in fact it will reduce battery usage.
  • How do I make my Locations smaller than 500 meters?

    Location accuracy varies from place to place, so Locale adjusts Location condition size based on sensor readings. For remote locations where Locale may not know the accuracy, the minimum size is 500 meters. To create smaller locations, physically move yourself to the place you want, and then try creating a new Location condition. For example, create your Work location while you're already at work.

  • Why does Wi-Fi keep turning on and off?

    Locale will sometimes perform brief Wi-Fi scans (even if Wi-Fi is turned off) to determine your location accurately. Although it seems counterintuitive, these Wi-Fi scans significantly improve location accuracy and battery life. Without Wi-Fi scans, location accuracy is typically within 2,000 meters. With Wi-Fi scans, location accuracy is typically within 100 meters.

  • How do I backup Locale?

    Locale automatically makes backups of your situations.

    1. Whenever a situation is modified, Locale automatically places a backup on every external storage volume. For Android 4.4 and later, this also means the SD Card if present. The path is /Android/data/com.twofortyfouram.locale/files/backup.xml.gz. If this file exists when Locale is installed, Locale will automatically ask to restore from it. This file will be deleted automatically if Locale is uninstalled, so consider copying it to a safe place before uninstalling Locale. To move Locale's configuration to a new device, either transfer the SD card or manually copy the file from the old phone to the same location on the new phone and create the folders if they do not exist. Mac users may need Android File Transfer. Note: For devices without an SD card, external storage is technically internal memory built-in to the device but Android confusingly calls it "external storage."
  • I see the Shortcut setting opens apps... how do I kill apps?

    Android treats memory differently than a desktop computer. When leaving an app, it is paused rather than killed, so that returning to it later is faster. If Android needs more memory, it will automatically close apps that have been paused but have not been used recently. Because Android manages memory automatically, "task killer" apps are not necessary. Google has blocked "task killer" apps for Android 2.2 and later.

    While it is not possible to "kill" apps on Android, the Shortcut setting can be used to simulate this behavior by bringing the Home screen to the foreground. To do this, create a new Shortcut setting that opens the "Launcher" or "Home" app (on HTC devices, the Launcher might be called "HTC Sense"). When the setting is fired, it will bring the Home screen to the foreground, pausing whatever application was previously on the screen.

  • Why can't I install Locale to external storage or the SD card?

    Locale is a background application and therefore needs to be installed to internal storage to work properly. This is consistent with Android's guidelines for app install locations. Locale will however store location cache data on external storage in order to minimize usage of internal storage.

  • How do I disable Locale's ongoing notification icon?

    Locale displays an ongoing notification in order to reliably monitor conditions. Android aggressively kills background apps, except for apps displaying an ongoing notification. For this reason, Locale's ongoing notification is necessary.

    Android 4.1 and later allow Locale's ongoing notification to be entirely disabled, without impacting reliability. To completely disable Locale's ongoing notification, go to Android Settings -> Apps -> Locale and uncheck "Show notifications."

    We do not recommend disabling the notification, as it provides best status of Locale's state. If troubleshooting, please turn the notification back on. This is useful to 1. see if Locale is still running and 2. see status of situations. Although situation status can be seen by opening Locale, tapping on Locale's icon also causes a implicit refresh of all conditions which may make troubleshooting more difficult.


Locale is compatible with Android devices running Android 2.3 through Android 7.1. Locale supports all screen resolutions and screen sizes. Locale supports phones, tablets, media players, and even TVs. Locale is tested extensively on a wide variety of Android devices in our lab from nearly every manufacturer. Although Locale is compatible with over 14,000 Android devices, there are a few known issues which are documented below.

We test new devices as soon as they are available, and this list is continuously updated.

  • Samsung, Huawei, OnePlus, and Sony devices have "battery saver" features that block Locale from running in the background. See the "Battery Savers" section at the top of this page to see how to disable these features.
  • Locale does not currently support Android's multi-user feature. If multiple users have Locale configured, multiple copies of the app may run simultaneously and conflict.
  • Due to an HTC bug, some HTC devices running Android 4.0 or later will return to the Android Home screen, rather than Locale's Edit Situation screen, after selecting a wallpaper in Locale's Wallpaper setting. To complete setting up the Wallpaper setting, re-open Locale and then the Wallpaper setting will finish saving.
  • Locale is fully compatible with Android's built-in Wi-Fi tethering feature, however location accuracy will be reduced while Wi-Fi tethering is active. For this reason, we recommend USB tethering instead.
  • While Locale is fully compatible with Android's built-in Wi-Fi tethering feature, third party tethering apps that require root may conflict with the Location condition. To use root tethering apps, we recommend one of the following workarounds: 1. While root tethering is enabled, temporarily turn Locale off from the menu or Action Bar of Locale's main screen. 2. Make all locations 2,000 meters or larger to implicitly disable Locale's Wi-Fi location feature. 3. Don't use the Location condition.
  • Sony Ericsson devices have a bug that prevents the Orientation condition from working reliably, therefore the Orientation condition is disabled on Sony Ericsson devices.
  • The custom ROM MIUI prevents apps like Locale from changing the volume. To fix this issue, 1. Open the Superuser app. 2. In the list of apps, tap on Locale. 3. Under the Manage Permissions section, set "Monitor calls" to allow. (This name is misleading, but this setting is what allows Locale to change the ringer volume).
  • Don't use custom ROMs or root your device: Locale is designed from the ground up to be reliable and portable across different versions of Android and different devices. We test Locale on dozens of different devices, versions of Android, and even on several custom ROMs before release. Locale is sophisticated and interacts with many parts of the Android hardware and software. Although a custom ROM may appear to work most of the time, Locale is more likely to uncover bugs in a custom ROM because Locale does a lot more than other apps.