> Unifying multiple binder tracing implementations
> Removing wallpaper customization check as it has been rolled out
few years ago, this avoids additional RPC to check for wallpaper
> Removing RaceConditionReproducer as it is not used anywhere and
is not integrated with this tracing anymore
Bug: 273718665
Test: Presubmit
Flag: N/A
Change-Id: I801af5d039a9d38d5d39e803723ec6da50a9d59f
Since we enable generate_traces by default for the system and
signature apps, we can remove this special case
Test: Manual
Bug: 161393989
Change-Id: Iff92c0a729a9b9b038fb6310c7509925c59547b6
Instead of having only one switch to enable all binder tracing,
we seperate between stack tracking and tracing. Stack tracking
still works as before. However, the more lightweight option,
tracing using android.os.Trace, is toggleable separately and will
work on the receiver side without dumping the entire stack trace.
We also make the tracing more efficient by caching
getTransactionName and concatting the class name.
Also, enable this selectively for SysUI+Launcher, which is
currently the focus of always-on-tracing effort to figure out
what kind of binder calls these processes are calling which seems
to contribute a huge amount of jank (long binder calls are in
>= 50% of janky traces).
Test: external/perfetto/tools/record_android_trace gfx view freq sched wm am aidl
Test: atest aidl_unittest
Bug: 202278427
Change-Id: Ia555740400808e0a467d00e305b6743931d3af0a
* Whenever launcher setting is changed, only log the changed setting instead of all
Bug: 181703659
Test: wwdebug && wwlogcat AND statsd_testdrive 10108
Change-Id: I9c6b7a17d653038a91f885df455e5ebbb401b49a
- Previously we rely on whether launcher is resumed as a signal to see what "toggle" means. This no longer works since launcher is not resumed in Overview. Instead, we need to check the live tile signals.
- Use screenshot doesn't propagate after setting a new current task. So followed the logic around mRunningTaskIconScaledDown to work it out.
- Get rid of NavigationModeFeatureFlag, pending on 3rd party launcher change ag/14409355
Fixes: 185934639
Test: (1) Toggle overview from home screen and toggle back to fullscreen. (2) Toggle overview from app and keep toggling.
Change-Id: Iffaea18afb2179b5bb7dadda49e56efefa5658bc
3 Button mode doesn't use recents animation so live tile would not work on 3 button mode before migration to recents animation happens.
Bug: 169694902
Test: manual
Change-Id: I9574c624f3d220834fa18e910637cd64460adb0c
This will skip generating metrics for fallback recents,
which is not a big loss
Test: manual
Bug: 177472265
Change-Id: I0e167ddc3276246510ea5a22ba04dfd53a8d4eac
> Workspace snapshot is logged when the workspace loads (at most once a day)
> Removing unnecessary thread jumping when logging folders
> Preference snapshot is logged on process start and whenever something changes
Change-Id: I93767de89b11522d843c0e8300d1f108c78f6d90
This will allow us to cleanly remove ENABLE_OVERVIEW_ACTIONS while still
keeping the shelf instead of actions in 2-button mode.
Bug: 143361609
Change-Id: I5cd43b6d3daeb527c7787b1cb81fae9179d8911c
When ENABLE_OVERVIEW_ACTIONS flag is enabled, swiping up from the nav
bar goes to overview if you hold, or the first home screen if you don't.
- Added NoButtonNavBarToOverviewTouchController, which extends
FlingAndHoldTouchController but only works if you start from the nav
bar. Otherwise it falls back to PortraitStatesTouchController to
handle normal state transition to all apps.
- Added HintState. This is where the workspace/hotseat/qsb scale down
when you swipe up from the nav bar, to hint that you're about to
either go to overview or the first home screen.
- Added getQsbScaleAndTranslation() to allow Overview and Hint states
to treat it as part of the hotseat.
- Since Overview needs to show above the QSB as it's animating, bring
Overview to the front and update OverviewScrim to handle the case
where there's no view above Overview to draw the scrim beneath.
- ENABLE_OVERVIEW_ACTIONS is always false in 2-button mode, since the
shelf is crucial to that mode.
Bug: 143361609
Change-Id: I743481bb239dc77f7024dc98ba68a43534da2637
While removing unused files in Go version of quickstep, I removed
QuickstepProcessInitializer which seemed unused but is actually
initialized as a resource based ovverride. This CL puts it back as
common src so that both Launcher3GoIconRecents and the rest of the
variants all use this class.
Bug: 135472635
Test: Run Launcher3GoIconRecents => no exception
Test: Run Launcher3 => no exception
Change-Id: I56f319bac536ec4da96285fab932fe574afa4520
As Go will not be using RecentsView, there are several files that are
unneeded in the recents Go source. This moves these files to
recents_ui_overrides where they will be used for non-Go builds.
Bug: 114136250
Test: Build NexusLauncher, aospWithQuickstep, l3GoWithQuickstep
Change-Id: I9d0154a75f4f2c71b865d414448e262b3019b2b9
- The launcher package is automatically enabled for work profiles due to
DPM interpreting it as a critical component since it does not have any
launchable activities. Once enabled, it is possible for an explicit
broadcast to update smartspace or assistant state to trigger the process
to be created for the work profile user, which ends up initializing logic
which may call into LauncherApps (which is not allowed from the work
profile).
As a workaround, we disable the launcher application immediately upon
detecting that it is running in a work profile.
Bug: 120550382
Change-Id: I72c52fe598d41440a1fb59304b494a000277384b
Andy Wickham