This has been implemented by a free plug-in. Look for “Locale Autorotation” on the Android Market!

As I understand it, the only reason for this request is really for reusing a condition or setting across multiple situations. Given that most conditions or settings are very easy to set up individually, the value gained by re-use seems low unless the number of situations is on the order of 10 or more.

We experimented with reusable Locations in older versions of Locale, and found the UI to be exceedingly complex and the benefits of reuse didn’t offset the UI complexity required.

I believe this request is obviated by the latest updates to Google Maps on Android, which allows for automatic checkins.

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

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.

Actually, I think there’s a better way to organize this:

I’m marking this feature request as complete, as there are two ways currently to detect when the phone is in a car: a car dock condition or a Bluetooth condition, both of which are available now as plug-ins on the Android Market.

In order to have the votes correctly tallied, created a new request for a speed condition. If you want a speed condition, vote here:

http://feedback.twofortyfouram.com/forums/5655-locale-feedback/suggestions/884809-speed-condition

Locale 1.1 improves battery usage by up to 50%, depending on the device.

Apps cannot directly change call-forwarding settings on the phone, due to security restrictions in Android. Despite this, there are two workarounds to allow for a call forwarding setting:

1. The Locale Dial Plug-in setting can be set up to dial any number. Most cell phone carriers allow special dialing codes to enable/disable call forwarding. For example in the United States dialing *72 followed by a phone number will enable call forwarding to that number. Then dialing *73 later will disable call forwarding. Please consult with your carrier for its specific dialing codes. https://market.android.com/details?id=com.mariobialos.LocaleDialPlugIn

2. Use Google Voice. The Locale Google Voice plug-in can be used to change Google voice call forwarding settings, although your callers must be dialing the Google Voice number for this to work. https://market.android.com/details?id=com.steelgirder.LocaleGoogleVoicePlugin