diff options
| author | Wale Ogunwale <ogunwale@google.com> | 2015-06-01 09:48:36 -0700 |
|---|---|---|
| committer | Wale Ogunwale <ogunwale@google.com> | 2015-06-01 11:37:57 -0700 |
| commit | 2c8c30ac3cbd899cefc9b963669f3a18df08b425 (patch) | |
| tree | 3703b2396672c9410940a117757d11ed871c9e73 /docs/html/sdk/api_diff/19/changes | |
| parent | 55b4b2d5a82ef7999a32b8163340a15085b2df38 (diff) | |
Allow app to stop lockTaskMode if started by manifest attribute
It is possible lockTaskMode was started by the system process
because android:lockTaskMode is set to a locking value in the
application's manifest instead of the app calling
startLockTaskMode. In this case TaskRecord.mLockTaskUid will
be 0, so we compare the callingUid to the
TaskRecord.effectiveUid instead so the app can exit lockTaskMode.
Bug: 21464182
Change-Id: Ibca6de8e4b17051d5fcbb05cde9c8aefed7216f2
Diffstat (limited to 'docs/html/sdk/api_diff/19/changes')
0 files changed, 0 insertions, 0 deletions