In landscape and largest density, the area that could show the heads
up notification is smaller than normal density. To handle the heads
up notification should be different with the normal notification in
both of targetScrollForView and getScrollRange because
StackScrollAlgorithm translation heads up notification as
mHeadsUpInset but neither targetScrollForView nor getScrollRange has
have the same consideration.
The solution make the StackScrollAlgorithm to considerate scroll
value to move up the heads up notification.
The getScrollRange need to consider more about the difference
between heads up showing and non-heads up showing. The top padding
and the total content height are the major considerations.
Test: manual test
Test: atest SystemUITests
Change-Id: I46bb960a81f6ab5be4d8e39738e8fb64245dd4eb
Merged-In: I46bb960a81f6ab5be4d8e39738e8fb64245dd4eb
Fixes: 110388615
(cherry picked from commit 529bfe6f0a)
In NotificationShelf, mShelfIcons.setActualLayoutWidth's parameter
comes from the return value of mCollapsedIcons.getFinalTranslationX.
both of mCollapsedIcons.getFinalTranslationX and 'start' has the
operator '+' and mCollapsedIcons.getFinalTranslationX should return
the value that doesn't translate to the xTranslation. The root cause
is that mCollapsedIcons.getFinalTranslationX should return the
'start tranlation' rather xTranslation.
The solution is to make the mixing usage between 'start tranlation'
and xTranslation to be seperated. And, 'start translation' is called
xAnchorStart. To get the 'start translation' by counting
(getWidth() - mLastVisibleIconState.xTranslation - iconWidth) to get
xAnchorStart.
Change-Id: Iec6893446ba161cce50e9b018e43f94782b91f11
Merged-In: Iec6893446ba161cce50e9b018e43f94782b91f11
Fixes: 111861498
Test: manual test
(cherry picked from commit b623343f13)
- Make ActivityMetricsLogger the single source of truth for activity metrics and
use it to provide data for Tron, logcat, event logs and {@link android.app.WaitResult}
- Remove LaunchTimeTracker
- Remove workaround added for b/80084651
- Remove thisTime from WaitResult and logs
- Remove am_activity_fully_drawn_time EventLog Tag
- Update WaitResult parsing logic in AppLaunch
- Discard metrics if a launching activity is already visible.
- original bug: 67683350
Compatibility Changes:
- thisTime removed from logcat and eventlog. Only totalTime will be displayed.
- Change in activity visiblity during launch will invalidate totalTime. am start -w
will only report WaitTime in this case.
- am_activity_fully_drawn_time is removed from event log.
Bug: 117235762
Test: atest google/perf/app-startup/third-party-apps/cold-dropcache-stable-test -v
Test: manual tests
Test: check applaunch.txt matches test run
Change-Id: Ib033594b961be9227256eba2a519dd6c2e3db573
(cherry picked from commit 132ee83808)
(cherry picked from commit 017cddcbcb)
(cherry picked from commit f8accc5b30)
(cherry picked from commit af0ea31549)
Test: manual (verified from logcat that intent is broadcast)
Bug: 115990430
Merged-in: I660cf2d04a1b57a58c8cefd212e5f8d73b329890
Change-Id: I660cf2d04a1b57a58c8cefd212e5f8d73b329890
(cherry picked from commit 8c1c45a710)
Draw TextureView with bilerp sampling, when the matrix is not
integer translate or identity. For example scaling matrix or
translation on X by 0.4f will draw with GL_LINEAR on OpenGL pipeline.
Translation on X by 3.0f will draw TextureView with GL_NEAREST.
Bug: 117890671
Test: Passed CtsViewTestCases and CtsUiRenderingTestCases
Change-Id: I72033410c8b0ab637c2e6b816ac9b04434286fbb
Merged-In: I3acd710ff2cb4ee7b14dd4b7d9227842187130c9
- http://ag/5163037
Fix a race in AMS.getContentProviderImpl().
If the provider process has just been killed by AM but appDiedLocked()
hasn't been called yet, this method would wait on the wrong
ContentProviderRecord.
- http://ag/5201125
Fix getContentProviderImpl() permission issue
- http://ag/5284403
Add timeout to AMS.getContentProviderImpl()
Bug: 116876013
Bug: 110030490
Test: manual test with the following debug code:
+ final String prop = "debug.am.provider.fake-kill." + cpr.proc.processName;
+ if (SystemProperties.getBoolean(prop, false)) {
+ cpr.proc.kill("fake-kill", true);
+ SystemProperties.set(prop, "0");
+ }
providerRunning = !cpr.proc.killed;
Then:
setprop debug.am.provider.fake-kill.android.process.acore 1
And launch the contacts app when acore is already running, and make sure
the timeout log shows up on logcat.
Test: Also do it with work profile contacts
Change-Id: I765d61a1b2719a92dff7db0162335f2c09c33421
Merged-in: I2c4ba1e87c2d47f2013befff10c49b3dc337a9a7
Merged-in: Ia35a9d36a34257873edbdcaefcf85d2373f3295e
Merged-in: Id5e7fff228d777eb0d1804654600d9ea156e36fd
- Break the power button alignment when power menu height larger then screen height,
remove power menu padding and set gravity to center vertical within the screen.
Test: Manually, set display size or font size to large, larger or largest & check
power menu should be center vertical/horizontal when power menu height
larger then screen height.
Bug: 110761858
Change-Id: Ice7f816a30fa0f565a9098b3d6d5989aca9a4e5b
Merged-In: Ice7f816a30fa0f565a9098b3d6d5989aca9a4e5b
By requiring an explicit default setting, it eliminates all ambiguous
states where a disambiguation would normally be shown. With this
change in place, at no point should a disambiguation be shown.
(Note: this is a fix to Change-Id: Ib32daf that clarifies
the logic if R.string.config_defaultAssistantComponentName
has not been set in a given build.)
Test: manual
Bug: 111603898
Change-Id: Id39fdf700ed4ef08ebbc333b5452223430ac2e48
Merged-In: Ib32dafbd3c6fcbe11186dc8ecab6b09c9b734067
