Android 2.0 finally adds APIs that would allow apps like Locale to implement a “Bluetooth Condition.” If this were implemented, it would only be available on Android 2.0 phones.

Update: There are some Android bugs that will prevent this from being implemented for the time being. Specifically, we’ve found that Bluetooth will periodically crap out until the phone is rebooted.

Android treats memory differently than a desktop computer. When leaving an app, it is paused rather than killed, so that 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 plug-in can be used to simulate this behavior by bringing the Android Home screen to the foreground. To do this, simply create a new Shortcut setting, choose Menu → Filter → All. Pick the “Launcher” app. When the setting is fired, it will bring the Home screen to the foreground, pausing whatever application was previously on the screen.

This has been implemented by the third party SMS Auto Respond Plug-in, which is available on the Android Market. https://market.android.com/details?id=com.suttco.locale.telephony.sms

There is a third party plug-in that accomplishes this. The “Locale Plug-in Appli Detection” is available on the Android Market in all countries that support paid apps.

Wi-Fi location training is now available as a feature in Locale 1.2. It can be found under the Menu of the Location condition.

We strongly discourage the use of third party location conditions or Wi-Fi conditions. These are less accurate and require more battery power. Instead, users should use the built-in Location condition and use Wi-Fi training if necessary.