In general, Locale is required to display an ongoing notification in order to run reliably. Background apps displaying a notification are given higher priority, such that they are killed last when Android runs low on memory. A notification has no impact on performance, only on reliability. If Locale is killed, it will no longer work. In fact, Android 2.3 is very aggressive about killing background apps running for more than a few minutes without displaying a notification. In order to ensure that Locale runs reliably, it must display an ongoing notification. Locale simply cannot offer an option that makes the app unreliable.

The underlying goal is to have multiple “At Home” situations with additional conditions. Even though you don’t want to do it, the right way to accomplish this is through the creation of multiple situations.

As requested, this feature will not be implemented because it will add significant complexity to the UI.

While an interesting idea that might save some time during data entry, this isn’t feasible. For consistency’s sake, it doesn’t make sense to only allow locations to be created this way. A web-based user interface would need to be created for every condition and setting type. With plug-in conditions and settings that would be very difficult to manage. Locale is a mobile app, and I think we should keep it that way :).

I believe the underlying issue here is that the Locale interface isn’t as efficient as you would like it to be? So if anyone has other ideas to improve the efficiency of the interface on the phone, please let us know.

From within Locale, you can also search for locations by name/address, which is likely what one would do from within a web browser anyway. So how much more efficient would a web-based interface really be?

This is implemented by the free Locale Pulse Trackball Plug-in available on the Android Market.. This plug-in is only for the Nexus One, as the notification light is not configurable for earlier devices.

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.

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

The Locale Media Volume Plug-in is available for free on the Android Market here https://market.android.com/details?id=com.twofortyfouram.locale.setting.media_volume

For those who are looking for Voice or Alarm volume settings, I’ve created two new requests. Please cast your votes there.

Voice Volume Setting http://locale.uservoice.com/forums/5655-locale-feedback/suggestions/450512-voice-volume-setting

Alarm Volume Setting http://locale.uservoice.com/forums/5655-locale-feedback/suggestions/450514-alarm-volume-setting

This has been implemented by the “Locale Call Detection Plug-in” plug-in condition for Locale 1.0. To find this plug-in on the Market, simply open Locale and choose Get Plug-ins from the menu.

This has been implemented by the “Inbound SMS Plug-in” plug-in condition for Locale 1.0. To find this plug-in on the Market, simply open Locale and choose Get Plug-ins from the menu.

This is now supported in Locale 1.0. To add multiple conditions of the same type, simply long-press on the Add Condition button.

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