Good news!

Android 4.0 finally grants apps official access the built-in calendar, so we’re planning to support this with a new Calendar condition. This new Calendar condition will be Android 4.0+ only.

As a general design principle, Locale only has features that Android officially supports (for the developers out there, we only use public APIs). This ensures that Locale works reliably across different versions of Android and different Android devices. For those without Android 4.0 (or those looking to live on the edge), there are some third-party plug-ins that implement Calendar condition functionality. These plug-ins are using undocumented Android APIs, and may therefore not work on all devices or may break when new versions of Android are released. Anyway, here are links to these plug-ins on the Android Market:

https://market.android.com/details?id=org.acm.steidinger.calendar.localePlugin

https://market.android.com/details?id=com.DroidMunkey.LocaleCalendarConditions

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

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!

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.