summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorAlan Stokes <alanstokes@google.com>2021-01-20 17:56:33 +0000
committerAlan Stokes <alanstokes@google.com>2021-01-27 11:29:32 +0000
commitdfebe6bd9b47708597b9922f2dffc739bb084155 (patch)
tree42721385d9aa0ce19950bf0f2340860743ab8cd7 /tools/aapt2/java/JavaClassGenerator.cpp
parent7e56827d84f49f7141c0b907bb3aebe554113c7b (diff)
Clean up BLOCK_ACTIVITY_STARTS_AFTER_HOME_FLAG.
This flag was only introduced to allow teamfood testing of the change to use background activity launch blocking instead of delaying app launches after app switching protection is engaged. The flag has been on everywhere for 2 weeks (ag/176961146) without problems and is no longer needed. This CL went in three stages: - Change getBalAppSwitchesProtectionEnabled() in ActivityTaskManagerService to always return true. - Inline the function (and selected others) into call sites and then eliminate the resulting dead code - done as a serious of automatic refactorings to minimise the risk of human error. - Delete unit tests for code that no longer exists. Apart from deleting the use of the flag I believe this CL is a pure refactoring with no new behavior changes. The end result is we eliminate quite a lot of code - especially PendingActivityLaunch and all uses of it. Test: atest BackgroundActivityLauncherTest Test: atest ActivityStarterTests (both of them) Test: manual Bug: 176961146 Bug: 159433730 Change-Id: I01625843f67b00e5901833cff99aec16c1287a0c Merged-In: I01625843f67b00e5901833cff99aec16c1287a0c Exempt-From-Owner-Approval: proto change approved on main branch (cherry picked from commit 5897ecc699c9dde4c1e616393b324b67a012c1d5)
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions