Overview

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

Contact

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.

Troubleshooting Tips

  • Reboot: Like the good old Windows 95 days, rebooting keeps Android happy. If you haven't rebooted today, please try rebooting your Android.
  • Uninstall/reinstall: Due to bugs in Android and defective flash memory in various Android devices, uninstalling and reinstalling Locale will magically resolve a variety of otherwise inexplicable issues.
  • Don't use third party backup utilities: We recommend using Locale's built-in backup and restore facilities, which are described in detail below. Third party backup utilities tend to corrupt Locale's installation.
  • Battery savers: "Battery saver" apps and tools disrupt many features of Android and may prevent Locale from working properly. For example, battery savers may disrupt Locale's location algorithms. Even if you haven't installed a battery saver app, check your Android settings as many devices now come with "battery saver" or "Wi-Fi connection optimizer" features preinstalled.
  • Wi-Fi toggling: Some Android devices have buggy Wi-Fi drivers, and turning Wi-Fi on and off repeatedly can make these these devices unstable. Rather than have Locale turn Wi-Fi on and off automatically, consider leaving Wi-Fi on all the time. To optimize battery usage, change the Wi-Fi sleep policy by going to Android Settings -> Wi-Fi settings. From there, choose Menu -> Advanced and then set the "Keep Wi-Fi on during sleep" setting to "Only when plugged in." In our experience, this configuration does not drain the battery.
  • 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 a sophisticated app that 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 any other app.

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.

  • 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 always 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 artificial intelligence 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.
  • 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 multiple redundant backups of your situations.

    1. Cloud backup: Locale uses Android's built-in cloud backup and restore for supported devices. Please note that cloud backups are managed by Android, not Locale, and therefore we cannot guarantee them to be 100% reliable. Cloud backups generally do not work across different device models, because different devices may store backups on different incompatible cloud servers. In addition, many custom ROMs do not support cloud backups.
    2. External storage backup: Locale automatically places a backup on external storage under /Android/data/com.twofortyfouram.locale/files/backup.xml.gz. (Note: external storage varies from device to device and may or may not be the SD card). If this file exists when Locale is reinstalled, Locale will automatically ask to restore from it.
    3. Manual backup: For Android 4.0 and later, the Android developer tools can perform a backup to a desktop computer. First, install the Android developer tools on your computer. Second, enable USB debugging under the Android settings of your device. Third, run the command "adb backup -f locale.bak com.twofortyfouram.locale" from your computer's terminal to create a backup called locale.bak in the terminal's current working directory. To restore a backup, run "adb restore locale.bak".
  • 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 cannot be disabled.

    Under Android 4.1 and later, Locale's ongoing notification will only appear in the notification pulldown area. The notification icon will not appear at the top of the screen. Android 4.1 and later also allows 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."

Compatibility

Locale is compatible with Android devices running Android 1.5 through Android 4.4. 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 5,300 Android devices, there are a few known issues which are documented below. The issues described only occur on the specific devices listed. Although a manufacturer may have many similar devices, each model is slightly different and each device is affected differently. For example, an issue that occurs on the Samsung Galaxy S II does not occur on the Samsung Galaxy S III (and vice versa) unless explicitly indicated. Also many Android devices have similar names, please keep in mind that we will always be explicit when naming a specific device.

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

  • Due to an Android bug, Android will report a Force Close about 1% of the time when installing a Locale update from Google Play. Just ignore this error. The problem is that Android does not properly close the old version of Locale before installing the new version, resulting in an erroneous Force Close.
  • Locale does not currently support Android 4.2's multi-user feature. If multiple users have Locale configured, multiple copies of the app may run simultaneously and conflict.
  • Due to Android limitations, changes to Display Brightness and Display Sleep settings may not take effect while the device is in a car or desk dock accessory.
  • Due to an Android bug, Locale's ongoing notification cannot be hidden on Android 4.3.
  • 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.
  • On HTC Sense UI devices running Android 2.2, the Orientation condition is prevented from updating while the screen is off. HTC's Android 2.3 update resolves this issue. Non-Sense UI devices such as the Nexus One were never affected by this issue.
  • Samsung Galaxy S and Galaxy S II devices have a firmware flaw that causes Wi-Fi to get stuck after a few days when using the Location condition. We have reported this issue to Samsung and Google. Until Samsung fixes this bug, we recommend one of the following workarounds: 1. Leave Wi-Fi ON all the time on these devices. To optimize battery usage, change the Wi-Fi sleep policy by going to Android Settings -> Wireless and Networks -> Wi-Fi settings. From there, choose Menu -> Advanced and then set the Wi-Fi sleep policy to "Never when plugged in." 2. Make all locations 2,000 meters or later to implicitly disable Locale's Wi-Fi location feature.
  • 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.
  • Samsung Galaxy Note 3 devices have a firmware bug that prevents setting minutes in the Time condition UI.
  • Samsung Galaxy Note 3 devices have a firmware bug that prevents the Wallpaper setting from saving.
  • Sony Ericsson devices have a bug that prevents the Orientation condition from working reliably, therefore the Orientation condition is disabled on Sony Ericsson devices.
  • Due to Android bug #21635, when running Android 4.0 through Android 4.0.4 it will take about 20 seconds before Locale's ongoing notification appears after manually turning Locale's service off and then back on again. Google resolved this issue with Android 4.1.
  • 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).