Age | Commit message (Collapse) | Author |
|
Change-Id: I598e03c717e351c29d31f413e3f3132ecd3c4d09
|
|
Bug:111603898
(cherry picked from commit 974a86e201e2fa17bad58d1fb2f83b7d21ed1580)
Change-Id: Ica3e8254b90ce5a5ce697d7f5dd683fdd148492e
|
|
5318499, 5317874, 5317875, 5317876, 5318243, 5318244, 5318537, 5318538, 5318539, 5318540, 5318541, 5318542, 5318543, 5318544, 5318545, 5318546, 5315210, 5317756, 5318557, 5318558, 5318559, 5318560, 5318561, 5318339, 5318547, 5318548, 5318549, 5318562, 5318563, 5318564, 5318565, 5318566, 5318172, 5318173, 5318174, 5318550, 5318401, 5318196, 5317889, 5318175, 5318176, 5318577, 5318578, 5318579, 5318580, 5318581, 5318503, 5318390, 5318505, 5318341, 5318551] into pi-qpr1-release
Change-Id: Iccfb3610e4261a2edd86e5abfba682248992fb9a
|
|
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
(cherry picked from commit c6ed3a29f0e2f0f1ceb727c5ece07702987e4ba5)
|
|
Bitmap created in TaskSnapshotPersister are very short lived and
shouldn't be left around in the Java heap.
Test: boot, switch apps, works
bug 117795621
Merged-in: I4b5e0db50c2b7adaa71cb0d22535c1b37c7523e8
Change-Id: I4b5e0db50c2b7adaa71cb0d22535c1b37c7523e8
(cherry picked from commit 9b4eaf740957663b01d4bf056df250dd028e0cb0)
|
|
Immediately purge malloc pages on bitmap destruction. Bitmaps are often
big and can cause memory to stay high for much longer than it should.
Test: boots and works
bug 117795621
Merged-in: If2e8c5f1fc07039cf3dc3edcd3dc06861dbce1a1
Change-Id: If2e8c5f1fc07039cf3dc3edcd3dc06861dbce1a1
(cherry picked from commit 535fae32e597445a480896ea8e01662ada444c0c)
|
|
The path-permission element offers prefix or regex style matching of
paths, but most providers internally use UriMatcher to decide what
to do with an incoming Uri.
This causes trouble because UriMatcher uses Uri.getPathSegments(),
which quietly ignores "empty" paths. Consider this example:
<path-permission android:pathPrefix="/private" ... />
uriMatcher.addURI("com.example", "/private", CODE_PRIVATE);
content://com.example//private
The Uri above will pass the security check, since it's not
technically a prefix match. But the UriMatcher will then match it
as CODE_PRIVATE, since it ignores the "//" zero-length path.
Since we can't safely change the behavior of either path-permission
or UriMatcher, we're left with recovering these shady paths by
trimming away zero-length paths.
Bug: 112555574
Test: atest android.appsecurity.cts.AppSecurityTests
Test: atest FrameworksCoreTests:android.content.ContentProviderTest
Merged-In: Ibadbfa4fc904ec54780c8102958735b03293fb9a
Change-Id: Ibadbfa4fc904ec54780c8102958735b03293fb9a
(cherry picked from commit c084ddbf826b25808c4553e4b5992c6723eac4ea)
|
|
If an app was in the TOP state and immediately moved
to a foreground service state, then try harder to keep it
in memory for another 20 seconds before releasing the
memory to bound foreground services. Using an oom_adj value
of 50 which is between "fore" and "vis". So BFGS apps might
get killed ("vis") before this recently FGS'ed app. That
way any app that has a lot of state in memory that it needs
to persist before getting killed has a chance to do so.
Also bind NotificationListeners with a special bind flag
to rank them below FGS (perceptible adj) so that they
can be killed before any other foreground services or
bound services get killed.
Bug: 110969183
Test: Manual for now. Take a bunch of portrait
pictures and hit home, while being under memory
pressure with a bunch of notification listeners.
Change-Id: Ie8934c2331afe6450c582b209869aeca7272f58a
Merged-In: Ie8934c2331afe6450c582b209869aeca7272f58a
(cherry picked from commit b735830a1e71e72c4e72260d7eab0382b4ee19df)
|
|
When removing an exiting process that is running foreground activities, clear the launch times for
the current windowing mode. When an app process is removed, activities from the process may be
relaunched. In the case of forceStopPackageLocked the activities are finished before any window
is drawn, and the launch time is not cleared. This will be incorrectly used to calculate launch time
for the next launched activity launched in the same windowing mode.
Bug: 80084651
Test: adb shell am start -W com.amazon.mShop.android.shopping/com.amazon.mShop.home.HomeActivity && sleep 1 && adb shell am force-stop com.amazon.mShop.android.shopping
Change-Id: I2c4f0716c922baa1ad209b4ea1fa7ce366e0e108
(cherry picked from commit 9372683dd2b6ceafee4714770b51e67066e3d8bc)
|
|
Change-Id: I06f63095c26ffb6cb482ea66b4f2663296c968ba
|
|
requested permissions."
This reverts commit 5e37e9d962c476202590bef32b87c2eb794d61a1.
Reason for revert: Not a security fix and the security fix needs this cl is reverted.
Bug: 114365189
Change-Id: Ia12ce2692b47a1d59be0b199b1fbfa415767e145
(cherry picked from commit 0b103c697331a5bcae2f65de4a3864bca0b592ff)
|
|
package."
This reverts commit fde947837c848b51a830b74b28f96f9808405492.
Reason for revert: triggers other issue.
Bug: 114365189
Change-Id: I37523a1778d55153253cf10df1ede68c5acb8178
(cherry picked from commit 06cc74977fcebe8a270e6bcd812dcfb31c32492c)
|
|
4986378, 4986889, 4986745, 4986746, 4986747, 4986748, 4986749, 4986750, 4986773, 4987169, 4987170, 4987611, 4987631, 4987632, 4987633, 4987634, 4986890, 4987612, 4987651, 4987598, 4987613, 4987614, 4987615, 4987599, 4986379, 4986380, 4987652, 4987653, 4987691, 4986774] into pi-qpr1-release
Change-Id: Idfec2f26918d14afde9ef01367ffb1ecd1dde548
|
|
Make sure the number of entries written by Parcel#writeMapInternal
matches the size written. If a mismatch were allowed, an exploitable
scenario could occur where the data read from the Parcel would not
match the data written.
Fixes: 112859604
Test: cts-tradefed run cts -m CtsOsTestCases -t android.os.cts.ParcelTest
Change-Id: I325d08a8b66b6e80fe76501359c41b6656848607
Merged-In: I325d08a8b66b6e80fe76501359c41b6656848607
(cherry picked from commit 057a01d1f38e9b46d3faa4059fdd7c8717681ea0)
|
|
SUPL_ES=1 ensures the GnssLocationProvider and related framework code
accepts incoming SMS SUPL_INIT messages with ES-bit=1
(which allow redirection of the ESLP
end-point e.g. to the current local emergency services provider when
you are travelling) only during an emergency call
Bug: 111899241
Bug: 112159033
Test: Build pass
Change-Id: I7dcd9c173a1d56fcf0da15257db5b8d1322b39d6
(cherry picked from commit 5b63dcc6a617cbab74dbda1f4cd759c75efa3aa5)
|
|
permissions.
Bug: 111752150
Test: Manual local test
Change-Id: I80383300cd5d2455d08a0ad91000efa85404903b
(cherry picked from commit 5e37e9d962c476202590bef32b87c2eb794d61a1)
|
|
Leaving a no-op CREATOR can lead to issues. We throw a run-time
exception to prevent anyone from using this. The StatsLogEventWrapper is
meant to be write-only since it's only used to send data to statsd.
Bug: 112550251
Test: Tested with provided POC app by external researcher.
Change-Id: I001d84e2a61a1cd8a4f59aa156ca52f73ad0f6e1
(cherry picked from commit 78622d57ad102c054306b01321b6b2dbec3f9d1d)
|
|
4948531, 4946116, 4948532] into pi-qpr1-release
Change-Id: I9938da9c9b2a3e53b6987d0d1e5d61a9177485f1
|
|
Checks for equality between two PhoneAccounts, not taking into account
the icon, which cannot be compared with equality.
Test: Manual as part of telephony account registry updates.
Test: Added new unit tests to test equality.
Bug: 112884689
Merged-In: Change-Id: Ibd0c69425bf185dc6b79db4ca4e9ca4a770320a3
Change-Id: Ibd0c69425bf185dc6b79db4ca4e9ca4a770320a3
(cherry picked from commit a04bd3d292ce29ad6f8c94348ea1c8ce80d29e8e)
(cherry picked from commit 5df50b83bcc22a3d23de6f48d5d93418bfb63f1d)
|
|
Change-Id: Ida0d6a734faa333574d13d4319bf149ad9bfa1d7
|
|
The NearestTouchFrame spanned the entire nav bar that took any tap to
hit the nearest button such as the back button. Reducing it prevents
taps from the edge of the nav bar. Related: ag/4179853
Change-Id: I25a73cc995ed8d479ca9d5da85ec8a7cb629769d
Fixes: 112298917
Test: tap the left side of the nav bar
(cherry picked from commit 9e90f24dc5dc2574700c46288617bea18b28bf29)
(cherry picked from commit 7daaaad74a29eca0e2a56b29fe55e2f615b05415)
|
|
Change-Id: I94a38b8375529c17492adf346429a48d5969c733
|
|
Test: Switch display cutout
Bug: 113093654
Change-Id: I2ca076a214da86656b6c71ebe1f63eb92e340ac0
(cherry picked from commit 1fd30aa5581dec8cfa5113fe436bcd963d0a35f9)
|
|
Change-Id: I4f32356294ed679fa8f6374099f471de85486a36
|
|
Some Pixel devices had a wrong brand value provisioned into keymaster.
Due to this misprovisioning those devices fail device ID attestation because it includes a check for the correct brand value.
This is now solved by re-trying Device ID attestation if we are running on a potentially misprovisioned device, allowing for the known incorrect brand value.
Bug: 69471841
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement
Change-Id: If715ebdd4ab6d7fcfffab60b40fd2dc8fa1fda44
Merged-In: Ia0da5478d6092c1927d26600a6893ae8ce53da51
(cherry picked from commit 3f821a8e17f97a6f0b3ae408b2e7f2bfde666df4)
|
|
pi-qpr1-release
Change-Id: Ie4bd913ccb175f035e4d284226db33be943a1ecf
|
|
Test: javadoc fix.
Bug: 112882126
Change-Id: I69f55aaa49103690a796ff394fcd1934891a52f2
|
|
pi-qpr1-release
Change-Id: Ib9fe15999e374e3fc58127b6415e8b019a5b960c
|
|
|
|
|
|
Causes too much of a process restart storm.
Test: Switch cutout option
Bug: 112876936
Change-Id: I76909bd292c7d6b28c673f068c408885da0d92c1
|
|
We do this by storing the masking inset in a persistent property.
The boot animation then animates itself to where it would be if that
masking inset were applied, then changes the viewport.
For this to work, we also need to make sure the DisplayManagerService
has the right overlay right at the start.
Bug: 112876936
Test: Hide cutout, then reboot. Verify boot animation is smooth.
Change-Id: I3e988b2340b2e0d2be3939bdc6878704c234ccc8
|
|
pi-dev
|
|
If we have a display size change, make sure to set different
scaling mode such that we can show the buffer even if there is
a size mismatch.
Test: Rotate screen
Test: Change cutout type
Bug: 112876936
Change-Id: Iedc7774d69730a95b98ba46d4f274bc3b7e66bd1
|
|
pi-dev
|
|
Now that battery saver is sticky this notification never shows
and we are getting reports from people that the notification
they were expecting never showed up. It turns out that a lot
of these were due to people not realizing battery saver was on.
To remedy the worst case situation (your phone is about to die
soon but no 15%/3 hour notification came up) we should always
show the severe warning even if battery saver is on. This only
affects the hybrid warning, not the legacy percentage based
version.
Test: unit tests
Bug: 111596093
Change-Id: I92453b68b6ee8aad8f862147c877f4e789afc55c
Merged-In: I92453b68b6ee8aad8f862147c877f4e789afc55c
|
|
This isn't something apps generally can handle, so we kill all of
them for now.
Test: Change cutout overlay that changes display size
Test: Rotate screen
Bug: 112876936
Change-Id: Ic3b0f1b3ae1e9bd93ac8f2c6952aa093878602b8
|
|
pi-qpr1-release
Change-Id: I348dc5200bd75dc04d6af22983e9c0bf2643dcd6
|
|
into pi-dev
|
|
|
|
Bug: 112876936
Test: atest ScreenDecorationsTest
Change-Id: I4359b3da4a47dcf434f018fe3e62e18354d1be47
|
|
|
|
Adds an option to mask the cutout by effectively shrinking the logical display
such that developers can test apps as if the device did not have a notch.
Bug: 112876936
Test: Go to Settings > Developer Options > Simulate display with cutout > "No cutout". Cutout should be hidden. Rotate screen, take screenshots, screenrecord, screen off animation should all work as expected.
Change-Id: I5cdb201734d238bf3785ab55843114e4b5b4ee41
|
|
Bug: 112876936
Test: Open developer options, go to "display cutout", verify strings.
Change-Id: I1d22f56ca7fa8c817da2407f36613e4fc132a3a9
|
|
pi-qpr1-release
Change-Id: I729e9afd508d1ce9d778f365b017024bda3d7afc
|
|
|
|
|
|
|
|
|
|
QSTile#clearState puts QS tiles in an invalid state that may not be
immediately rectified through QSTile#refreshState. In the case of
configuration changes, if a subclass implementation of
QSTile#handleSetListening does not trigger a refresh state, the
invalid state causes incorrect click handling.
Change-Id: I17eba133cf08c45a768e9e0ed8fda623e85b4370
Fixes: 69738120
Fixes: 110480955
Test: manual
(cherry picked from commit 299c45c85d41975514022263fa6a29329eb5a0bc)
|