Carter

@spookymonster: We usually give developers a chance to investigate issues before we re-evaluate. Often such bug reports are specific to a particular version of Android, a particular device, etc.

Although I haven't had any issues with this specific plug-in, I'd recommend following up with the plug-in developer first because I'm sure he'll be glad to help.

@spookymonster: This is a third party plug-in, which means we didn't develop it. For support with third party plug-ins, we recommend contacting the plug-in developer directly. Contact information can be found on the Android Market screen for that plug-in.

While technically possible, I'm wary of implementing a true "screen off" setting. I could imagine the combination of some sort of third party plug-in condition and a screen off setting causing the screen to turn off once per second, effectively locking a user out of their phone.

What is the underlying goal with this request? Could you simply set the screen timeout to 15 seconds when the phone is face up or face down, and a longer timeout in the defaults? I believe that might effectively accomplish the same end result of turning the screen off very quickly when the phone is lying flat.

I understand how accidentally answering the phone when pulling it out of your pocket can be annoying!

Android uses a "slide to answer" screen when the phone is ringing, and this gesture should make it difficult to accidentally answer the phone. Can you be more specific as to what you're experiencing?

I don't follow your comment. It is absolutely impossible to toggle data roaming on or off via Locale. It is possible to disable all data via APNDroid.

Taking a guess as to what you might be thinking: data roaming would have to be always turned on. Then rather than toggling data roaming, you could toggle all data access via APNDroid based on the carrier. This would have the same effect as a data roaming setting, although it seems far riskier to your cell phone bill if you happen to disable Locale and forget about it. Or if APNDroid has a bug that causes it to fail, etc. Is that what you are thinking?

@Kosi2801 K.:
I understand that you're trying to optimize your battery usage. The Android battery statistics are buggy and not correct, so please ignore them.

We've found the only way to accurately gauge battery usage is to perform multiple trials using a stopwatch and measure how long it takes for the battery to drain completely. This is how we perform our own battery usage testing.

Locale is extremely efficient and is working as expected. While we are always improving Locale's efficiency, no changes are planned or necessary in this area as such changes would counter-intuitively increase Locale's CPU and battery usage.