This is implemented by the Locale Button Plug-in, which can be found on the Android Market by choosing “Get Plug-ins” from the menu of the Locale home screen.

At long last Locale 3.0 introduces the Calendar condition to detect events on your Google Calendar, Exchange Calendar, or any other calendar supported by Android.

While Locale 3.0 is available for Android 2.2 or later, the Calendar condition requires Android 4.0 or later. To learn more about Locale 3.0, please see our release notes here http://blog.twofortyfouram.com/post/19303488607/locale-3-0

Locale 1.0 adds a new condition: the Orientation condition. The orientation condition supports detecting when the phone is lying face up or face down.

Locale 1.0 is available on the Android Market today in countries that support paid apps. Full release notes are here: http://www.twofortyfouram.com/notes.html

As Chris said, this can be accomplished using the “Locale Power Power Source Plugin.” Simply add a Battery condition to detect the battery level, and a Power Source condition to detect being unplugged. Please note that this plug-in requires Android 2.0 or later.

This has been implemented by a third party developer. The Locale Inbound SMS Plug-in is available as a paid app on the Android Market!

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

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.

While an interesting idea, this isn’t possible because the actively displayed contact list is a private setting of the Contacts app. Third party apps like Locale cannot modify settings within the contacts app for security reasons.