Sorry we currently don't support this. On Tue, Jun 29, 2010 at 11:37 PM, LeveloKment <[email protected]>wrote:
> Hi again Dianne. ;) > > Ok, lets keep the DeviceAdmin out off the topic for now. From what you > have described it seems to be for corporate use mainly. > > The "problem" I've tried to fix with my app "PatternControl" was the > following: > People (private Android users) are aware that they have stored a lot > of sensible data on the smartphones, because of this some of them > would like to protect this information a little bit better... this is > where the Lock Pattern of Android (or with Froyo also the Pin or > Password) comes into the game. > > All the basic lock features that Android provides to the users have > one disadvantage... Ones enabled, they always on. Each time you want > to use your phone you have to deal with the lock (pattern, pin or > password). > For private users this is often a bit to much and in the end they > deactivate the security pattern again. > > What is missing from my point of view (and most likely the point of > view from thousands of users of apps like PatternControl, AutoLock > etc.), is an option like "Enable the lock only if I didn't used the > phone for xxx minutes". > > Best regards > Lars > > > > > > > On 29 Jun., 19:15, Dianne Hackborn <[email protected]> wrote: > > On Tue, Jun 29, 2010 at 4:53 AM, LeveloKment <[email protected] > >wrote: > > > > > If I understand you right, than the only "option" to provide more > > > flexibility to the users is still an option in Android itself. > > > The DeviceManager can then disallow such temporary lowering of the > > > lock level. > > > > Sorry I am not understanding that paragraph. > > > > > From my point of view an always on security feature will often be > > > disabled (at least by private users). This lowers the security even if > > > the origin intention was the other way around. > > > > Not sure I see the connection here... the API to disable the lock screen > is > > not supported when a device admin is requiring a lock screen, in which > case > > there is no way for the user to go around this except to disable that > device > > admin, and thus lose all access to whatever corp server the admin is > > associated with. And if their preference is to be able to not have a > lock > > screen at the expense of not having their corp server access... well, > that > > is fine for all. > > > > -- > > Dianne Hackborn > > Android framework engineer > > [email protected] > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
