- hashString API moved to utils to be used by Histogram metric APIs
Bug: 262791652
Test: m
Change-Id: Ic049083c6e19c045e6f743e3bc96e1fc15ed4533
Merged-In: Ic049083c6e19c045e6f743e3bc96e1fc15ed4533
In headless system user mode, USER_STARTING, USER_STARTED, and
USER_SWITCHED broadcasts were not sent for the system user.
It had caused issues for other parts of the system which are expecting
such broadcast messages. For example, VpnManagerService expects
USER_STARTED event for system user but was not receiving it.
This change will only affect headless system user mode. No behavior
changes for phones.
Bug: 263439429
Bug: 242195409
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest
Change-Id: I4a101418c10a2c959c2bfae01b95863aebd521e8
(cherry picked from commit ba0f9f3ad2)
Merged-In: I4a101418c10a2c959c2bfae01b95863aebd521e8
is lack of space.
Previously:
There was a chain [date]-[space]-[status icons]-[battery]. That's why we should add bias and space to make it working.
But there're several problems with this:
1) app:layout_width="WRAP_CONTENT" + app:layout_constrainedWidth=”true" != app:layout_width="0dp" + app:layout_constraintWidth_default="wrap". The first one gets view expanded like it's MATCH_PARENT.
2) I've found out that wrapping views in constraint layout 2.0.0 may not always work as expected with app:layout_constrainedWidth=”true" (the view get's stretched as it's match_parent). layout_constraintWidth_max="wrap" should've help with this, but motion layout can't parse this attribute in constraint set. That's why my solution is to reimplement the layout a little bit
This behavior is reported here: https://github.com/androidx/constraintlayout/issues/713
Now:
[date] and [battery] are constrained to the sides and [status icons] occupy the whole space between them.
[date] is always WRAP_CONTENT because there's always some space and we want to show it.
[battery] and [status icons] are wrap content with constraints restrictions to make them fill all the space left
Test: manual: phone + tablet
Fixes: 260364389
Change-Id: I4d54b795cc4e96f6c204f2f00aff7607572d9aa3
(cherry picked from commit 675ff0fe37)
Merged-In: I4d54b795cc4e96f6c204f2f00aff7607572d9aa3
Test: Auto + manual
- Add work profile -> QS tile is added
- Remove work profile -> QS tile is removed
- Reboot the device -> QS tile is in place
- Reorder tiles, reboot the device -> order is persisted
Fixes: 234639083
Change-Id: I4481a3f28f9d1f0c30618afaf78179e0033f50fb
(cherry picked from commit a240e7eebe)
Merged-In: I4481a3f28f9d1f0c30618afaf78179e0033f50fb
As part of renderscript deprecation/removal, of the two pieces of
renderscript in this app, one already had a Java alternative but the
heatmap code didn't. Rather than reimplement that, though, it appears
that this project has been obsoleted by CtsUiRenderingTestCases. So
let's remove it instead. (Even if we're wrong, this still gives us more
time to work out what, if anything, is actually needed.)
Bug: http://b/255624710
Test: treehugger
Change-Id: I7cf64a28bd3c7edea061fafc5e06d4134cc79b05
Upon suspending the app, we don't set mWaiting like we do in
waitingForDebugger. This is an error because this state is checked
upon handling HELO in DdmHandleHello chunk handler.
Mimicking what is done in waitingForDebugger ensure that WAIT is
sent and DDM client receive the event.
Bug: 266232837
Test: Manual
Change-Id: I3b8bc9af6f017f3a16c33ac38df7a9248c939a1a
After system boots,the UserDisabledHdrTypes also needs to be updated
in the display information.
Bug:265724287
Test: Prepare a HDR/DolbyVision TV which supports DolbyVision/HDR10/HLG.
1.Connect the STB to the TV.
2.On UI Settings -> Device Preferences -> Display & Sound -> Advanced
Display settings -> Format Selection,choose manual,disable DolbyVision
format and keep HDR10/HLG formats enabled.
3.Reboot STB ,Check 2) , it is same as previous saved result.
4.Open Netflix, search DolbyVision contents movie and check the format.
It should only list HDR contents, no DolbyVision contents.
Change-Id: I4c38532ad973a85c289796a9372413bd5491ca26
Signed-off-by: wangn <nan.wang@vantiva.net>
This CL refactors the way the ActivityLaunchAnimator and
DialogLaunchAnimator handle the visibility of the animated View when
that View implements LaunchableView.
Before this CL, a View that is animated would always end up being
VISIBLE, even if something made that View INVISIBLE or GONE before or
during the animation. That is because our animation code would sometimes
change the visibility of the View, using View.setVisibility.
After this CL, when animating a LaunchableView, all the visibility
changes made to the animated View are done using
View.setTransitionVisibility instead. That way, a LaunchableView can
track all calls to View.setVisibility only and restore the last
visibility that was set on the View at the end of the animation. Doing
so ensures that all calls made to View.setVisibility have the expected
result once the animation is done.
Bug: 264728445
Test: DialogLaunchAnimatorTest
Change-Id: I5848d42ef94952ecf058d4e895164389e37e0311
(cherry picked from commit 9ecb3db788)
Merged-In: I5848d42ef94952ecf058d4e895164389e37e0311
This CL fixes the View that is used when showing the Foreground Services
dialog.
Test: Click the FGS button when the Security button is also shown.
Bug: 264728445
Change-Id: Id686279bbfc1e47e28da894342688d44183ebf42
(cherry picked from commit 0e7b6e534c)
Merged-In: Id686279bbfc1e47e28da894342688d44183ebf42
Before the code compare the dev of the source, and target file.
However, since the target file hasn't been created at this time, the
code will always copy the source file instead of hard linkking.
Test: sideload train, and check whether the apex in rollback folder is a
hardlink. Run presubmit
Bug: 168562373
Change-Id: I6e5c6e0d35e4fa44d41d3d2d6fc564e5213e0092
The intended use is
- #apex is APEX-visible symbols provided by apex libraries
- #systemapi is APEX-visible symbols provided by platform libraries
Since libandroid is a platform library, update the annotation to
sytemapi.
Bug: 239274367
Bug: 265485106
Test: TH
Change-Id: I28db5cd0d3a76afa1a7ecac042ee02dd74faa2f1
And the presence tuple of the standalone is added.
Bug: b/262614903
Test: atest PublishServiceDescTrackerTest
Test: In the live network, if there is the feature tag related to the standalone in the registered feature tags, the service id of standalone is included in the PIDF
Change-Id: I2057c1a74e3db12d34b726c0cba7dfc26601bee5
Merged-In: I2057c1a74e3db12d34b726c0cba7dfc26601bee5
