Go to file
Marc Blank 81fbc1e1b9 Handle inactivity timeout > maximum allowed properly
* In a recent change, we mistakenly removed the logic for handling
  too-long inactivity timeouts; we should just fall back to the maximum
  since this is stricter than what we're being asked to enforce
* Restore this logic and update the unit test
* The regression was caused by change Ida5663a9, to wit:
  Backport: Handle "Allow non-provisionable devices" properly

Bug: 2886746
Change-Id: I99cf9a37441b80477cc1c2c7ec2a78f8a14a83da
2010-08-17 23:54:59 -07: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 DO NOT MERGE - Revert workaround for KeyguardLock problem 2010-06-11 11:21:41 -07:00
src Handle inactivity timeout > maximum allowed properly 2010-08-17 23:54:59 -07:00
tests Handle inactivity timeout > maximum allowed properly 2010-08-17 23:54:59 -07: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 Set proguard flags 2010-03-02 14:03:08 -08:00
AndroidManifest.xml DO NOT MERGE - Revert workaround for KeyguardLock problem 2010-06-11 11:21:41 -07:00
CleanSpec.mk Add an empty CleanSpec.mk 2010-03-08 18:05:00 -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
proguard.flags Added a test for IMAP APPEND 2010-04-06 14:33:43 -07:00
remove-exchange-support.sh Remove exchange readme and update script 2010-02-04 13:09:34 -08:00