This reverts commit c50f47d970.
Fixes: 79465234
Reason for revert: Google still does it using private APIs and apps were relying on this behavior, not good for the ecosystem.
Change-Id: I62e2b4cd1e6e562fcdd89c97e599bcdade83381a
In TextClassificationManager, we use the application context to reduce
the likelihood of leaking the underlying Activity. Unfortunately, some
places (e.g. auto, system_server) don't actually provide us an
application context, so we need to fall back to whatever context was
passed in to TCM in the first place.
Bug: 80188317
Test: none
Change-Id: Ib4b2e6ed543d3ed56cefd8f56717855158cdc0fe
- The ordering was such that the disabled state was updated before
onPanelExpandedChange which was masking the issue by updating the
slippery flag, but when unlocking from the screen off state, we get
onPanelExpandedChange first, and disabled state after (which doesn't
update the slippery state).
Bug: 80204751
Test: Turn screen off, unlock with fingerprint, swipe up
Change-Id: I88f1bc6a983ec0d693844724d8b9d4bf11a0fd31
...as opposed to after the async channel finished disconnecting.
Bug: 78308259
Test: runtest frameworks-net
also used a device with this patch over the weekend and
tried all I could think of
Change-Id: I77ad6d97abb20815b801a794eaa9685acf2d1173
Different navbar layouts are loaded via config.xml depending
on if Quickstep is enabled. A contextual button frame is added
to replace the right nav buttons so different styling can be
applied. New back, rotate and keyboard icons are added.
Maintains support for custom navbar layouts. Adds support for
nested reversable elements, needed for contextual button frame.
Fixes navbar gravity support by using RelativeLayout's gravity
and top/bottom switching.
Change-Id: I5e24b2392c377313d421c0f95c3a7a0b99f32590
Fixes: 79930722
Fixes: 79930974
Fixes: 80164476
Test: manual, crash sysui, test against a11y, gb menu, rotate
Recently cellular radio related values {"radio.active", "radio.scanning",
"radio.on"} are removed from power_profile.xml, which causes inaccurate
radio power usage. We use following formula to calculate radio
values from modem.controller values.
radio.active = average of modem.controller.rx and modem.controller.tx values
radio.scanning = 0 (since this is already included in radio.on bin 0)
<array name="radio.on"> <!-- Strength 0 to BINS-1 -->
<value>modem.controller.idle * 25 / 180 </value> <!-- none -->
<value>max(1, modem.controller.idle/256) </value> <!-- poor -->
<value>max(1, modem.controller.idle/256) </value> <!-- moderate -->
<value>max(1, modem.controller.idle/256) </value> <!-- good -->
<value>max(1, modem.controller.idle/256) </value> <!-- great -->
</array>
Bug: 79379255
Test: use debugger to observe correct mPowerRadioOn, mPowerBins,
mPowerScan are calculated. "adb shell dumpsys batterystats", looking for
"radio=" in "Estimated power use" section.
Change-Id: Ic65a5c8a35a5b1f4ba05ddc150e29b00bc62689f
We are not removing transient views for the 'swiped out' animation.
Utilizing the transient view cleanup in onAnimationFinished to handle
this better.
Test: Manually
Bug: 79896012
Change-Id: I3c169815433e34795472264de30ff23b3d744269
Applying this mechanism for system carrier apps to make visibility
reasonable from the user's perspective. In other words, before
hidden system apps have been installed, they wouldn't be listed
via APIs in PackageManager which are used at all apps list and
search in Settings and so on.
Test: manual
Test: atest CarrierAppUtilsTest
Test: atest PackageManagerTest
Bug: 74068582
Change-Id: Id3ff138ad529b909d9bbf6719af3a553b909ccbb
These don't get access to this internal parameter of native window,
yet require it for each buffer.
Bug: 79493409
Change-Id: Ib16e9af58b26c7b66a7e4bb466433fcee7b7d080
If a profile or device owner is present, package manager does not
support calls to PM#setPackagesSuspended. So if there were already
suspended packages, they need to be unsuspended when a PO or DO is
added.
Test: atest com.android.server.pm.SuspendPackagesTest
Bug: 79980390
Change-Id: Ib79d95ccc25eef534fdcd540d3d6ea75c31982a7
