When I said it wouldn't start it is the application that would exit. So on starting the first activity a key about having checked the password would be looked for. If not found authenticate. On Jan 7, 2012 10:19 AM, "Kristopher Micinski" <[email protected]> wrote:
> On Fri, Jan 6, 2012 at 10:27 AM, James Black <[email protected]> > wrote: > > Since the user needs a password then create your own market and install > app > > so you can require a password. > > > > Or ask for the password when it starts and don't allow them to do > anything > > if it fails. > > No: this can't be done at the application level. To think it could > would be indicate that the framework is in some way broken, as one app > should not be able to hijack the experience of the rest of the phone. > There are certain apps which can provide something which slightly > emulates this functionality, though they are just rough hacks, they > can easily be removed by the user simply uninstalling your "protector > app." The fact that you want to write such an app indicates that it > is likely you do not fully understand the security goals within the > Android platform (to the OP). The modifications necessary would not > be quite at the kernel level, but would be at the system level, where > applications are installed. This would be at the package manager, as > well as perhaps a few other places... > > Kris > > -- > 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 -- 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
