summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramFragmentFixedFunction.java
diff options
context:
space:
mode:
authorCharles He <qiurui@google.com>2017-04-12 16:22:35 +0100
committerCharles He <qiurui@google.com>2017-04-12 17:35:07 +0100
commite7c5ced2119f89b8e8b722b9010e685db8168b69 (patch)
tree2a8f4f0d6e3002013bf59a146acb2cca9e6d35c9 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java
parenta9a2bbc64744e33cdd555a843b3ea352ddd70a11 (diff)
Disallow direct-boot aware activities to bypass work lock
Effectively reverting 89927b3cd96472c478a988d6c731cd09d412a043, which allowed direct-boot aware activities in the work profile to show before the profile was unlocked. This causes problems with key eviction introduced in O. Specifically, many system activities (e.g. ChooserActivity, activities in Settings, etc.) are marked direct-boot aware, and therefore can be started while the work profile is locked with key evicted. Currently they either bypass the keyguard when they should not, or simply crash due to profile still being locked. In the future, we need to create a new mechanism to allow activities such as video calls, alarm clocks, etc. to bypass the work keyguard. It probably involves checking for something like FLAG_SHOW_WHEN_LOCKED. Bug: 36961785 Bug: 35708183 Bug: 30296144 Test: manual, by following the steps in the bugs quoted Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services Change-Id: I5ccaaf963f3dd96e4abb785a10aa258b15363178
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions