Go to file
Andrew Stadler d71d0b223a Force security activation after new account create
On new accounts, we can accelerate the process of setting up security
by explicitly checking (at the end of the security process).  The user
is not required to "answer" the asynchronous notification.

This is an imperfect solution, as a slow initial sync could leave the
user in a non-synced Inbox (with a notification waiting for them), but
we can come back to this after we evaluate real-world performance.

Bug: 2387961
2010-02-09 17:24:55 -08:00
assets auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
docs auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
images auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
res Logic to move phone into security-admin mode 2010-02-05 11:10:39 -08:00
src Force security activation after new account create 2010-02-09 17:24:55 -08:00
tests Adding security hold flag to accounts 2010-02-08 17:42:42 -08:00
.classpath Initial Contribution 2008-10-21 07:00:00 -07:00
.project Initial Contribution 2008-10-21 07:00:00 -07:00
Android.mk replace Email's private base64 class with one from android-common 2010-02-08 20:26:02 -08:00
AndroidManifest.xml Logic to move phone into security-admin mode 2010-02-05 11:10:39 -08:00
MODULE_LICENSE_APACHE2 auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
NOTICE auto import from //depot/cupcake/@135843 2009-03-03 19:32:22 -08:00
remove-exchange-support.sh Remove exchange readme and update script 2010-02-04 13:09:34 -08:00