OSDN Git Service
Jing Ji [Tue, 5 Nov 2019 21:55:26 +0000 (13:55 -0800)]
Prevent system uid component from running in an isolated app process
am:
84f2b227b0
Change-Id: Iba55ca710d5ee6e443520ceb899980c792fe5b2a
Jing Ji [Mon, 4 Nov 2019 19:35:49 +0000 (11:35 -0800)]
Prevent system uid component from running in an isolated app process
Bug:
140055304
Test: Manual
Change-Id: I5a1618fab529cb0300d4a8e9c7762ee218ca09eb
Merged-In: I5a1618fab529cb0300d4a8e9c7762ee218ca09eb
Torne (Richard Coles) [Wed, 30 Oct 2019 16:51:40 +0000 (09:51 -0700)]
Merge "Clarify CookieManager RFC reference." into qt-dev
am:
7186df9e6f
Change-Id: I91a6a53d029b8ec2567eaac93056c91642b5177e
TreeHugger Robot [Wed, 30 Oct 2019 16:31:03 +0000 (16:31 +0000)]
Merge "Clarify CookieManager RFC reference." into qt-dev
Nate Fischer [Tue, 29 Oct 2019 07:26:23 +0000 (00:26 -0700)]
WebView: clarify docs for onShowCustomView
am:
aaaa660a44
Change-Id: Idaa495f908c914057ac785bfeca1f2f15a0a5fd8
Nate Fischer [Fri, 25 Oct 2019 03:35:54 +0000 (20:35 -0700)]
WebView: clarify docs for onShowCustomView
No change to logic, only docs.
This clarifies the docs for onShowCustomView. This @links to
FLAG_FULLSCREEN, reminds the developer they must override both
onShowCustomView and onHideCustomView, and provides guidance for
CustomViewCallback.
Bug:
143247282
Test: make -j4 docs
Change-Id: I64de3723674da5c138438921cc8232c4bf2a3d98
Bill Yi [Sun, 27 Oct 2019 00:38:28 +0000 (17:38 -0700)]
Import translations. DO NOT MERGE
Change-Id: I2407d77349f697484f62cf943f5960381ffc76ae
Auto-generated-cl: translation import
Philip P. Moltmann [Fri, 25 Oct 2019 18:22:34 +0000 (11:22 -0700)]
Merge "[DO NOT MERGE] Split access-media-storage from read-external-storage" into qt-dev
am:
3b050525e4
Change-Id: Ie40f68f660e579cf9c2b1cbd446a4e3996bfa34d
Philip P. Moltmann [Fri, 25 Oct 2019 18:22:30 +0000 (11:22 -0700)]
[DO NOT MERGE] Split access-media-storage from read-external-storage
am:
f3ff750f29
Change-Id: I0f37950a78df7d503a830ec5eff77acad7382fb8
TreeHugger Robot [Fri, 25 Oct 2019 18:08:22 +0000 (18:08 +0000)]
Merge "[DO NOT MERGE] Split access-media-storage from read-external-storage" into qt-dev
Beverly [Thu, 24 Oct 2019 20:28:26 +0000 (13:28 -0700)]
Fix zen alarms only mode check
am:
51563b5ffe
Change-Id: I577da2d70a3ca8a9f2af0d574cb4406db25439f2
Philip P. Moltmann [Fri, 13 Sep 2019 22:12:34 +0000 (15:12 -0700)]
[DO NOT MERGE] Split access-media-storage from read-external-storage
And also pre-grant it to all apps that currently get any storage
permission pre-granted
Test: atest SplitPermissionTest
m -j gts && gts-tradefed run commandAndExit gts-dev -m GtsPermissionTestCases --test=com.google.android.permission.gts.DefaultPermissionGrantPolicyTest#testDefaultGrantsWithRemoteExceptions
Manual testing:
All combinations of
- App targetSdk = 28 and 29 (and 22 for extra credit)
- App having the <uses-permission> tag for
ACCESS_MEDIA_LOCATION or not
- Upgrade from P->Q-QPR and from vanilla Q->Q-QPR
Further upgrade of targetSdk from 28->29 while on Q-QPR
==> All permission behavior should make sense. Sometimes there
are weird, but expected behaviors. Hence we need to
collect the results and then look at the unexpected ones.
See SplitPermissionTest for some tests I added for the
location-background permission which was split from
the fine/coarse-location permissions
Fixes:
141048840,
140961754
Change-Id: Ib9f50d25c002036f13cf2d42fc4d1b214f20920c
(cherry picked from commit
ac7b10c135bb148edcad1aad8e19c733d333f769)
Beverly [Tue, 3 Sep 2019 21:00:51 +0000 (17:00 -0400)]
Fix zen alarms only mode check
Also fixes setting the consolidated zen policy logging.
Fixes:
140329813
Test: android.app.cts.NotificationManagerTest#testTotalSilenceOnlyMuteStreams
Test: android.app.cts.NotificationManagerTest#testAlarmsOnlyMuteStreams
Change-Id: I43d503ac23d7b0b141930d77cb76f1f589b22525
(cherry picked from commit
dcc5cfc56111676d687c8c29d1ceb6914dc1d8ce)
Kevin Hufnagle [Mon, 21 Oct 2019 22:44:08 +0000 (15:44 -0700)]
Merge "docs: App doesn't receive "first launch" broadcast" into qt-dev
am:
0823f1b508
Change-Id: I1e775265df7964f4eb5a41d5e228308aad29ee22
Kevin Hufnagle [Mon, 21 Oct 2019 22:33:05 +0000 (22:33 +0000)]
Merge "docs: App doesn't receive "first launch" broadcast" into qt-dev
Kevin Hufnagle [Mon, 21 Oct 2019 22:32:07 +0000 (15:32 -0700)]
Merge "docs: Added consent notice re. getAccounts()" into qt-dev
am:
3b6bbed3af
Change-Id: I0a32519c272af7fc21b1544a77b6bde86843d1e7
Kevin Hufnagle [Mon, 21 Oct 2019 22:14:54 +0000 (22:14 +0000)]
Merge "docs: Added consent notice re. getAccounts()" into qt-dev
Torne (Richard Coles) [Mon, 21 Oct 2019 18:34:03 +0000 (14:34 -0400)]
Clarify CookieManager RFC reference.
RFC2109 has been obsolete for a long time, and the docs aren't very
clear what exactly the RFC has to do with CookieManager; the RFC is
about HTTP and it's not immediately clear how this would apply to a Java
API.
Update the reference to the current cookie spec (and hyperlink it), and
clarify the text to explain that the HTTP header formats from the RFC
are the formats used to get/set set cookies.
Fixes:
143086151
Test: make ds-docs
Change-Id: I5e5838d3435b74516847b63e485fdd93810284aa
Kevin Hufnagle [Mon, 30 Sep 2019 17:59:49 +0000 (17:59 +0000)]
docs: Added consent notice re. getAccounts()
Test: make ds-docs -j32
Bug:
32704758
Change-Id: Id5e5c00840f2bde6c31a4f95f365b8bc8857884d
Bill Yi [Fri, 18 Oct 2019 14:41:12 +0000 (07:41 -0700)]
Import translations. DO NOT MERGE
Change-Id: I2206c0e454eb10858fa687a469d06c61230539b2
Auto-generated-cl: translation import
Seigo Nonaka [Thu, 17 Oct 2019 04:44:24 +0000 (21:44 -0700)]
[automerger skipped] Merge "RESTRICT AUTOMERGE Revive runLimit check logic" into oc-mr1-dev am:
9f7fb87dc4 -s ours am:
aa76cf3da5 -s ours
am:
9c6d7fe4bb
Change-Id: I1e21b2703948ee70d1f678680dd6daaa58905512
Seigo Nonaka [Thu, 17 Oct 2019 04:37:26 +0000 (21:37 -0700)]
[automerger skipped] Merge "RESTRICT AUTOMERGE Revive runLimit check logic" into oc-mr1-dev am:
9f7fb87dc4 -s ours
am:
aa76cf3da5 -s ours
am skip reason: subject contains skip directive
Change-Id: I1681d85652afe4fb20fa3d76f2f9483303e3d429
Seigo Nonaka [Thu, 17 Oct 2019 04:34:17 +0000 (21:34 -0700)]
[automerger skipped] Merge "RESTRICT AUTOMERGE Revive runLimit check logic" into pi-dev am:
d7f6ede261 -s ours
am:
8d016ab4ff
Change-Id: I32ea97ed0a26a07a741c61ddb40a0a4292a3320a
Seigo Nonaka [Thu, 17 Oct 2019 04:31:25 +0000 (21:31 -0700)]
[automerger skipped] RESTRICT AUTOMERGE Revive runLimit check logic am:
b730f1984f am:
2af4f537ff am:
709e9e6855 -s ours am:
37c65a3e5c -s ours
am:
ac663b4595
Change-Id: I8f11c57d4706f03291099be5d9d2d244ed354b78
Seigo Nonaka [Thu, 17 Oct 2019 04:11:44 +0000 (21:11 -0700)]
[automerger skipped] Merge "RESTRICT AUTOMERGE Revive runLimit check logic" into pi-dev
am:
d7f6ede261 -s ours
am skip reason: subject contains skip directive
Change-Id: I1f761fe6c5336996407892ebae25eb34a8d83538
Seigo Nonaka [Thu, 17 Oct 2019 04:08:47 +0000 (21:08 -0700)]
[automerger skipped] RESTRICT AUTOMERGE Revive runLimit check logic am:
b730f1984f am:
2af4f537ff am:
709e9e6855 -s ours
am:
37c65a3e5c -s ours
am skip reason: subject contains skip directive
Change-Id: Id5cce5424c5e712de76143a301e26e823d3df249
Seigo Nonaka [Thu, 17 Oct 2019 04:07:12 +0000 (21:07 -0700)]
[automerger skipped] Merge "RESTRICT AUTOMERGE Revive runLimit check logic" into oc-mr1-dev
am:
9f7fb87dc4 -s ours
am skip reason: subject contains skip directive
Change-Id: If95365aeca3f84f75f571dcf705f477b01425a0c
TreeHugger Robot [Thu, 17 Oct 2019 02:33:30 +0000 (02:33 +0000)]
Merge "RESTRICT AUTOMERGE Revive runLimit check logic" into pi-dev
TreeHugger Robot [Thu, 17 Oct 2019 01:46:22 +0000 (01:46 +0000)]
Merge "RESTRICT AUTOMERGE Revive runLimit check logic" into oc-mr1-dev
Seigo Nonaka [Thu, 17 Oct 2019 00:38:11 +0000 (17:38 -0700)]
[automerger skipped] RESTRICT AUTOMERGE Revive runLimit check logic am:
b730f1984f am:
2af4f537ff
am:
709e9e6855 -s ours
am skip reason: subject contains skip directive
Change-Id: Ib2c5674e2cf4442fe10d3dd5eb7ae7906e432254
Seigo Nonaka [Thu, 17 Oct 2019 00:26:09 +0000 (17:26 -0700)]
RESTRICT AUTOMERGE Revive runLimit check logic am:
b730f1984f
am:
2af4f537ff
Change-Id: Ia671d3f5a7fa62c80dd3c2468d199ce66fe734f1
Seigo Nonaka [Thu, 17 Oct 2019 00:14:15 +0000 (17:14 -0700)]
RESTRICT AUTOMERGE Revive runLimit check logic
am:
b730f1984f
Change-Id: I329515d36c12ee5e12a63262ff7db8daff350832
Seigo Nonaka [Wed, 16 Oct 2019 21:48:30 +0000 (14:48 -0700)]
RESTRICT AUTOMERGE
Revive runLimit check logic
The runLimit check logic was accidentally removed by
I7089ed9b711dddd7de2b27c9c2fa0fb4cb53a735
Bug:
142134328
Bug:
140632678
Test: Manually done with reported step
Test: StaticLayoutTest passes
Change-Id: Ib1d5efdcb9adcc18a6a43370dc016ea464f48148
Seigo Nonaka [Wed, 16 Oct 2019 21:48:30 +0000 (14:48 -0700)]
RESTRICT AUTOMERGE
Revive runLimit check logic
The runLimit check logic was accidentally removed by
I7089ed9b711dddd7de2b27c9c2fa0fb4cb53a735
Bug:
142134328
Bug:
140632678
Test: Manually done with reported step
Test: StaticLayoutTest passes
Change-Id: Ib1d5efdcb9adcc18a6a43370dc016ea464f48148
Seigo Nonaka [Wed, 16 Oct 2019 21:48:30 +0000 (14:48 -0700)]
RESTRICT AUTOMERGE
Revive runLimit check logic
The runLimit check logic was accidentally removed by
I7089ed9b711dddd7de2b27c9c2fa0fb4cb53a735
Bug:
142134328
Bug:
140632678
Test: Manually done with reported step
Test: StaticLayoutTest passes
Change-Id: Ib1d5efdcb9adcc18a6a43370dc016ea464f48148
Kevin Hufnagle [Tue, 15 Oct 2019 19:47:35 +0000 (19:47 +0000)]
docs: App doesn't receive "first launch" broadcast
Test: make ds-docs -j32
Bug:
116543817
Change-Id: I9aa1f1851ce236397ad2e1a36ea487b96daa55c5
Kevin Hufnagle [Tue, 8 Oct 2019 19:00:20 +0000 (12:00 -0700)]
Merge "docs: Updated SECURITY_PATCH field description" into qt-dev
am:
3c92f24adb
Change-Id: Ieb7549bb38439ad297bba0f5a4b64870919651a7
Kevin Hufnagle [Tue, 8 Oct 2019 18:36:19 +0000 (18:36 +0000)]
Merge "docs: Updated SECURITY_PATCH field description" into qt-dev
Evan Laird [Mon, 7 Oct 2019 23:40:18 +0000 (16:40 -0700)]
[automerger skipped] Force FGS notifications to show for a minimum time am:
3b8c4743f6 -s ours
am:
d3618f8275 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1
5136eefeb3 is in history
Change-Id: I84e294f2e9e192cfaf1c62cab4b05a1e8b5df7db
Evan Laird [Mon, 7 Oct 2019 23:30:51 +0000 (16:30 -0700)]
[automerger skipped] Force FGS notifications to show for a minimum time
am:
3b8c4743f6 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1
5136eefeb3 is in history
Change-Id: I5ad32c66fa4502e232b802241789977252ddec8e
Evan Laird [Mon, 7 Oct 2019 23:30:31 +0000 (16:30 -0700)]
Merge "Force FGS notifications to show for a minimum time" into qt-dev
am:
e590a7d0b5
Change-Id: Ia160497ca078e4d7c2ed99b28d41713cc17f5c90
TreeHugger Robot [Mon, 7 Oct 2019 23:04:14 +0000 (23:04 +0000)]
Merge "Force FGS notifications to show for a minimum time" into qt-dev
Kun Niu [Mon, 7 Oct 2019 20:22:55 +0000 (13:22 -0700)]
Merge "add java_api_finder plugin to mainline module Media to generate java APIs used by Media." into qt-dev
am:
01dfc10948
Change-Id: I0c7f975dfd910d7c8773bbf3a46086bbca82c7a4
TreeHugger Robot [Mon, 7 Oct 2019 20:14:31 +0000 (20:14 +0000)]
Merge "add java_api_finder plugin to mainline module Media to generate java APIs used by Media." into qt-dev
Kevin Hufnagle [Mon, 7 Oct 2019 19:53:36 +0000 (12:53 -0700)]
Merge "docs: Edited sharedUserId deprecation message" into qt-dev
am:
35b69e2ca3
Change-Id: I5f1fbce04b8e7f70d623e15dce2c13d122cba95c
Kevin Hufnagle [Mon, 7 Oct 2019 19:35:38 +0000 (19:35 +0000)]
Merge "docs: Edited sharedUserId deprecation message" into qt-dev
Evan Laird [Mon, 5 Aug 2019 21:11:54 +0000 (17:11 -0400)]
Force FGS notifications to show for a minimum time
It's possible for a service to do a start/stop foreground and cause a
couple of things to happen:
NotificationManagerService will enqueue a EnqueueNotificationRunnable,
post a PostNotificationRunnable (for the startForeground), and then also
enqueue a CancelNotificationRunnable. There is some racy behavior here
in that the cancel runnable can get triggered in between enqueue and
post runnables. If the cancel happens first, then
NotificationListenerServices will never get the message.
This behavior is technically allowed, however for foreground services we
want to ensure that there is a minmum amount of time that notification
listeners are aware of the foreground service so that (for instance) the
FGS notification can be shown.
This CL does two things to mitigate this problem:
1. Introduce checking in the CancelNotificationRunnable such that it
will not cancel until after PostNotificationRunnable has finished
executing.
2. Introduce a NotificationLifetimeExtender method that will allow a
lifetime extender to manage the lifetime of a notification that has been
enqueued but not inflated yet.
Bug:
119041698
Test: atest NotificationManagerServiceTest
Test: atest ForegroundServiceNotificationListenerTest
Change-Id: I0680034ed9315aa2c05282524d48faaed066ebd0
Merged-In: I0680034ed9315aa2c05282524d48faaed066ebd0
Alan Stokes [Mon, 7 Oct 2019 15:18:41 +0000 (08:18 -0700)]
Merge "Revert new app installed notification doc" into qt-dev
am:
98540e2a16
Change-Id: I12b1bf9c6c078ee1629e2135140ccd59b8f9da81
Alan Stokes [Mon, 7 Oct 2019 14:41:57 +0000 (14:41 +0000)]
Merge "Revert new app installed notification doc" into qt-dev
Bill Yi [Sun, 6 Oct 2019 00:17:00 +0000 (17:17 -0700)]
Import translations. DO NOT MERGE
Change-Id: Iae1b021de5e543f5b157cde38e1f693a104f1fbe
Auto-generated-cl: translation import
Evan Laird [Fri, 4 Oct 2019 18:18:59 +0000 (14:18 -0400)]
Force FGS notifications to show for a minimum time
It's possible for a service to do a start/stop foreground and cause a
couple of things to happen:
NotificationManagerService will enqueue a EnqueueNotificationRunnable,
post a PostNotificationRunnable (for the startForeground), and then also
enqueue a CancelNotificationRunnable. There is some racy behavior here
in that the cancel runnable can get triggered in between enqueue and
post runnables. If the cancel happens first, then
NotificationListenerServices will never get the message.
This behavior is technically allowed, however for foreground services we
want to ensure that there is a minmum amount of time that notification
listeners are aware of the foreground service so that (for instance) the
FGS notification can be shown.
This CL does two things to mitigate this problem:
1. Introduce checking in the CancelNotificationRunnable such that it
will not cancel until after PostNotificationRunnable has finished
executing.
2. Introduce a NotificationLifetimeExtender method that will allow a
lifetime extender to manage the lifetime of a notification that has been
enqueued but not inflated yet.
Bug:
119041698
Test: atest NotificationManagerServiceTest
Test: atest ForegroundServiceLifetimeExtenderTest
Change-Id: I0680034ed9315aa2c05282524d48faaed066ebd0
Merged-In: I0680034ed9315aa2c05282524d48faaed066ebd0
Kevin Hufnagle [Fri, 4 Oct 2019 19:49:00 +0000 (19:49 +0000)]
docs: Edited sharedUserId deprecation message
Test: make ds-docs -j32
Bug:
142139123
Change-Id: I3485785126f268c76f81f760fc19e0506929b272
Philip P. Moltmann [Fri, 4 Oct 2019 18:43:06 +0000 (11:43 -0700)]
Merge "Update PermissionChecker usages to avoid unnecessary attribution." into qt-dev
am:
0a71df1f7e
Change-Id: I658626de14fa325e08db3aead53707d8d3e00d3b
Philip P. Moltmann [Fri, 4 Oct 2019 18:23:30 +0000 (18:23 +0000)]
Merge "Update PermissionChecker usages to avoid unnecessary attribution." into qt-dev
Bryan Ferris [Fri, 4 Oct 2019 17:57:23 +0000 (10:57 -0700)]
Merge "Only allow INSTALL_ALLOW_TEST from shell or root" into qt-dev
am:
06684aed55
Change-Id: I166f54becf2d4fa99939c1d9b5e9c335f70e8a69
Bryan Ferris [Fri, 4 Oct 2019 17:42:36 +0000 (17:42 +0000)]
Merge "Only allow INSTALL_ALLOW_TEST from shell or root" into qt-dev
Ricky Wai [Fri, 4 Oct 2019 15:10:17 +0000 (16:10 +0100)]
Revert new app installed notification doc
Bug:
111214100
Test: Able to compile
Change-Id: Id4fdabf0e8c69074eb8cb5838ab11d9d5f030093
Kun Niu [Tue, 2 Jul 2019 00:59:25 +0000 (17:59 -0700)]
add java_api_finder plugin to mainline module Media to generate java APIs used by Media.
Bug:
129294170
Test: m updatable-media RUN_ERROR_PRONE=true |& tee media_error_prone.out
Change-Id: I3cdfe5e00394c6ff7b9c857f63a5e45ac79f8d24
(cherry picked from commit
6eff1d439b472b6114bc11f3a50c70ca7c68add7)
Merged-In: I3cdfe5e00394c6ff7b9c857f63a5e45ac79f8d24
Svet Ganov [Tue, 24 Sep 2019 04:32:08 +0000 (21:32 -0700)]
Update PermissionChecker usages to avoid unnecessary attribution.
We had accidental usages of the PermissionChecker for cases where no
private data was provided to the app but the checkPermission API on
the latter also did blame data access on the app. The PermissionChecker
was designed to handle IPC calls and not for generic API checks.
To avoid future accidental incorrect PermissionChecker usages this
change renames the existing APIs of the latter to clearly indicate
that they should be used for data delivery and also adds sibling
methods for doing the same permission checks for preflight purposes.
Also the documentation is improved to furhter assist developers.
In addition, this change fixes accidental permission checker usages
that blame when they should not by using the new preflight flavor
of the permission check APIs.
Test:
atest com.android.settingslib.location.RecentLocationAppsTest
atest CtsPermissionTestCases
added: LocationAccessCheckTest#notificationOnlyForAccessesSinceFeatureWasEnabled
added: LocationAccessCheckTest#noNotificationIfFeatureDisabled
added: LocationAccessCheckTest#noNotificationIfBlamerNotSystemOrLocationProvider
added: LocationAccessCheckTest#testOpeningLocationSettingsDoesNotTriggerAccess
bug:
141028068
Merged-In: I65c71569d0dd8a40bc6fecabb22c5373dd6e806e
Change-Id: I65c71569d0dd8a40bc6fecabb22c5373dd6e806e
Seigo Nonaka [Wed, 2 Oct 2019 17:38:35 +0000 (10:38 -0700)]
[automerger skipped] RESTRICT AUTOMERGE Do not compute outside given range in TextLine am:
4ce901e405 am:
b51c7bb175 am:
af62f3a7b3 -s ours am:
86ddd9eb6a -s ours
am:
eab868fa63
Change-Id: I2f88eecd916f2642cc3cb0c8ba91ed6348247900
Seigo Nonaka [Wed, 2 Oct 2019 17:30:08 +0000 (10:30 -0700)]
[automerger skipped] RESTRICT AUTOMERGE Do not compute outside given range in TextLine am:
4ce901e405 am:
b51c7bb175 am:
af62f3a7b3 -s ours
am:
86ddd9eb6a -s ours
am skip reason: subject contains skip directive
Change-Id: Ie6db3a3499cb02ef1bd34232a4ca8fb362b18e7d
Seigo Nonaka [Wed, 2 Oct 2019 17:10:34 +0000 (10:10 -0700)]
[automerger skipped] RESTRICT AUTOMERGE Do not compute outside given range in TextLine am:
4ce901e405 am:
b51c7bb175
am:
af62f3a7b3 -s ours
am skip reason: subject contains skip directive
Change-Id: Ifb67887f4b1a5860dca2569e57a74911efde801d
Seigo Nonaka [Wed, 2 Oct 2019 16:59:45 +0000 (09:59 -0700)]
RESTRICT AUTOMERGE Do not compute outside given range in TextLine am:
4ce901e405
am:
b51c7bb175
Change-Id: I6770f4b1a884020c374a75f67eb762b2c2bfd538
Sterling Huber [Wed, 2 Oct 2019 16:59:45 +0000 (09:59 -0700)]
[automerger skipped] Merge "RESTRICT AUTOMERGE Do not compute outside given range in TextLine" into pi-dev am:
e352c1f2bc -s ours
am:
66e93df90a
Change-Id: I1c8d52d8db52e53f15095d43e9744ece11f9c900
Sterling Huber [Wed, 2 Oct 2019 16:33:57 +0000 (09:33 -0700)]
[automerger skipped] Merge "RESTRICT AUTOMERGE Do not compute outside given range in TextLine" into pi-dev
am:
e352c1f2bc -s ours
am skip reason: subject contains skip directive
Change-Id: Id51032f27a8325444290483a9a30da49da8ac2e2
Seigo Nonaka [Wed, 2 Oct 2019 16:33:53 +0000 (09:33 -0700)]
RESTRICT AUTOMERGE Do not compute outside given range in TextLine
am:
4ce901e405
Change-Id: I739746d80a8dd29998a67c1d9aaa2d3f804ac57c
Sterling Huber [Wed, 2 Oct 2019 15:51:19 +0000 (15:51 +0000)]
Merge "RESTRICT AUTOMERGE Do not compute outside given range in TextLine" into pi-dev
Bill Yi [Tue, 1 Oct 2019 18:19:50 +0000 (11:19 -0700)]
Import translations. DO NOT MERGE
BUG:
138175268
Change-Id: I4e6ca4ed7c7ba4a39a15988100fad60dafd79c02
Auto-generated-cl: translation import
Seigo Nonaka [Mon, 16 Sep 2019 21:49:49 +0000 (14:49 -0700)]
RESTRICT AUTOMERGE
Do not compute outside given range in TextLine
This is second attempt of I646851973b3816bf9ba32dfe26748c0345a5a081
which breaks various layout test on application.
The empty string must be also handled by the TextLine since it
retrieves the default line height from the empty string.
Bug:
140632678
Test: StaticLayoutTest
Test: Manually done
Change-Id: I7089ed9b711dddd7de2b27c9c2fa0fb4cb53a735
Seigo Nonaka [Mon, 16 Sep 2019 21:49:49 +0000 (14:49 -0700)]
RESTRICT AUTOMERGE
Do not compute outside given range in TextLine
This is second attempt of I646851973b3816bf9ba32dfe26748c0345a5a081
which breaks various layout test on application.
The empty string must be also handled by the TextLine since it
retrieves the default line height from the empty string.
Bug:
140632678
Test: StaticLayoutTest
Test: Manually done
Change-Id: I7089ed9b711dddd7de2b27c9c2fa0fb4cb53a735
Jungshik Shin [Mon, 30 Sep 2019 17:27:18 +0000 (10:27 -0700)]
Merge "Use NotoSansMyanmar (pure Unicode) fonts" into qt-dev
am:
e31854028e
Change-Id: I5337ac53b41fc00b87e6c74604900764d28359fa
TreeHugger Robot [Mon, 30 Sep 2019 17:09:15 +0000 (17:09 +0000)]
Merge "Use NotoSansMyanmar (pure Unicode) fonts" into qt-dev
Kevin Hufnagle [Mon, 30 Sep 2019 16:23:00 +0000 (09:23 -0700)]
Merge "docs: Added link to multi-window drag how-to guide" into qt-dev
am:
667b944522
Change-Id: Ic5039fb781c73c2e1691c4c32afc7e35a9713683
Kevin Hufnagle [Mon, 30 Sep 2019 16:10:39 +0000 (16:10 +0000)]
Merge "docs: Added link to multi-window drag how-to guide" into qt-dev
Bernardo Rufino [Mon, 30 Sep 2019 11:12:52 +0000 (04:12 -0700)]
Merge "Don't consider tasks with INITIALIZING top activity as visible" into qt-dev
am:
0a252361dd
Change-Id: I077cf0c3e82ddcec213b50b5efdba97699a7ed0d
Anna Malova [Mon, 30 Sep 2019 11:08:44 +0000 (04:08 -0700)]
Merge "[WebView] Minor javadoc fix for WebSettings." into qt-dev
am:
63c65616ae
Change-Id: I3ee0487212dfb139da111e9a7314dc781db66b63
Bernardo Rufino [Mon, 30 Sep 2019 11:00:13 +0000 (11:00 +0000)]
Merge "Don't consider tasks with INITIALIZING top activity as visible" into qt-dev
Anna Malova [Mon, 30 Sep 2019 10:54:16 +0000 (10:54 +0000)]
Merge "[WebView] Minor javadoc fix for WebSettings." into qt-dev
Suprabh Shukla [Sat, 28 Sep 2019 02:38:34 +0000 (19:38 -0700)]
[automerger skipped] Merge "DO NOT MERGE revoke certain app-ops on suspend" into pi-dev am:
0e8f1fa5e9 -s ours
am:
c6a2982b86 -s ours
am skip reason: change_id Ie95555856afdd56728125f7e60b6a78cf9fc0e58 with SHA1
873e19f63f is in history
Change-Id: I8c9e309eae92633cb6193f147f81d109cc812d7c
Suprabh Shukla [Sat, 28 Sep 2019 02:31:55 +0000 (19:31 -0700)]
Merge "DO NOT MERGE revoke certain app-ops on suspend" into qt-dev
am:
b036952896
Change-Id: Ieb5d9cc6e8aee976069c7ebd0b8d01db9982d886
Suprabh Shukla [Sat, 28 Sep 2019 02:31:51 +0000 (19:31 -0700)]
DO NOT MERGE revoke certain app-ops on suspend
am:
873e19f63f
Change-Id: I2447a90e4935e53fc0d55510bb50938fdaea23fa
Suprabh Shukla [Sat, 28 Sep 2019 02:31:47 +0000 (19:31 -0700)]
[automerger skipped] Merge "DO NOT MERGE revoke certain app-ops on suspend" into pi-dev
am:
0e8f1fa5e9 -s ours
am skip reason: subject contains skip directive
Change-Id: I53678027aa329651d6d6c9652aee847ee36b9b30
TreeHugger Robot [Sat, 28 Sep 2019 02:15:10 +0000 (02:15 +0000)]
Merge "DO NOT MERGE revoke certain app-ops on suspend" into pi-dev
TreeHugger Robot [Sat, 28 Sep 2019 02:08:05 +0000 (02:08 +0000)]
Merge "DO NOT MERGE revoke certain app-ops on suspend" into qt-dev
Kevin Hufnagle [Fri, 27 Sep 2019 23:51:27 +0000 (23:51 +0000)]
docs: Added link to multi-window drag how-to guide
Test: make ds-docs -j32
Bug:
71008103
Change-Id: Ifcc50920cf3828697add018d1d3a6a827c7c9f98
Anna Malova [Wed, 25 Sep 2019 11:19:27 +0000 (12:19 +0100)]
[WebView] Minor javadoc fix for WebSettings.
No change to logic.
Test: N/A
Bug:
132394762
Change-Id: I957b0d8a03cd937b38611e32f6c012b01a6ad7da
Evan Laird [Tue, 24 Sep 2019 23:14:05 +0000 (19:14 -0400)]
DO NOT MERGE Allow for HTML styling in mobile data type content descriptions
This CL implements a (somewhat hacky) way to enable HTML attributes in
the mobile data type content description strings. This way we can use
some basic styling in the Quick Settings cellular data tile which uses
it in a TextView.
We do this by assuming that the content description is valid, escaped
HTML, and send two separate CharSequences to all of the listeners, all
of which can then decide if they need the regular content description or
the prettified version.
Test: atest SystemUITests; system ui demo mode
Bug:
141177147
Change-Id: Idf387111b0cdc34ad3762eac0ec6c2b484b393e3
Merged-In: Idf387111b0cdc34ad3762eac0ec6c2b484b393e3
Kevin Hufnagle [Tue, 24 Sep 2019 22:06:18 +0000 (15:06 -0700)]
Merge "docs: Modernized AccessibilityNodeProvider example" into qt-dev
am:
e49cbb3a5d
Change-Id: I24a281dd7194ea5c731ecc02371734fe1fa315f8
Todd Kennedy [Fri, 20 Sep 2019 20:45:15 +0000 (13:45 -0700)]
Only allow INSTALL_ALLOW_TEST from shell or root
Bug:
141169173
Test: Manual. App can't be installed as test-only
Change-Id: Ib6dcca7901aa549d620448c0165c22270a3042be
Kevin Hufnagle [Tue, 24 Sep 2019 21:18:39 +0000 (21:18 +0000)]
Merge "docs: Modernized AccessibilityNodeProvider example" into qt-dev
Kevin Hufnagle [Mon, 23 Sep 2019 23:08:03 +0000 (16:08 -0700)]
Merge "docs: List BIOMETRIC_WEAK in setPasswordQuality()" into qt-dev
am:
2a082b1e9e
Change-Id: I74d42b68ebed97c2db3a179e92ba3196ffc7a04f
Kevin Hufnagle [Mon, 23 Sep 2019 22:45:45 +0000 (22:45 +0000)]
Merge "docs: List BIOMETRIC_WEAK in setPasswordQuality()" into qt-dev
Kevin Hufnagle [Fri, 20 Sep 2019 22:39:50 +0000 (15:39 -0700)]
Merge "docs: Fixed link to material design for ScrollView" into qt-dev
am:
80b543b45a
Change-Id: Ic7cc4494a88e6feaedf85626270ed1e8057189f5
Kevin Hufnagle [Fri, 20 Sep 2019 22:14:46 +0000 (22:14 +0000)]
Merge "docs: Fixed link to material design for ScrollView" into qt-dev
Kevin Hufnagle [Fri, 20 Sep 2019 00:58:45 +0000 (00:58 +0000)]
docs: Updated SECURITY_PATCH field description
Test: make ds-docs -j32
Bug:
127625306
Change-Id: I052bb647ebb36ea3c9a788be592e7de9cd969e10
Kevin Hufnagle [Wed, 18 Sep 2019 01:52:45 +0000 (01:52 +0000)]
docs: Fixed link to material design for ScrollView
Test: make ds-docs -j32
Bug:
141024886
Change-Id: I69d05cdf99d91f74143454c78c000128d1da42ce
Santos Cordon [Thu, 19 Sep 2019 15:08:30 +0000 (08:08 -0700)]
Merge "Acquire display suspend blocker for DozeService" into qt-dev
am:
576a6f4ac5
Change-Id: I75471698513cfc72c87f0149d4da891d7156fa3b
TreeHugger Robot [Thu, 19 Sep 2019 14:50:10 +0000 (14:50 +0000)]
Merge "Acquire display suspend blocker for DozeService" into qt-dev
Bernardo Rufino [Thu, 29 Aug 2019 18:12:28 +0000 (19:12 +0100)]
Don't consider tasks with INITIALIZING top activity as visible
To fix b/
130645908, tasks with top activities in INITIALIZING state were
considered visible. This allowed apps to circumvent background activity
launch restriction by starting 2 activities when in a background stack.
The first activity will remain in INITIALIZING state (since it's in the
bg), so the second launch is permitted since top activity is
INITIALIZING.
Removing '|| topActivity.isState(INITIALIZING)' removes the
vulnerability and curiously still allow the legitimate use case of the
bug linked above to work, i.e. the test in ag/
7088262 still passes. This
is because of 2 reasons:
1) Grace period introduced in ag/
7638265.
2) Allow bg activity starts to put activity on top of bg task (instead of
fg’ing it) in ag/
7190176.
I verified (2) by removing the grace period check, reverting the linked
CL and verifying that the test failed.
This essentially reverts ag/
7090415.
Test: atest BackgroundActivityLaunchTest \
RootWindowContainerTests \
WmTests:ActivityStarterTests \
CtsWindowManagerDeviceTestCases:ActivityStarterTests
Bug:
138583650
Bug:
130645908
Change-Id: Iee4ba841c6c83888b55c5cb55fffc949048d2030
Kevin Hufnagle [Thu, 19 Sep 2019 00:32:55 +0000 (17:32 -0700)]
Merge "docs: Add condition for hiding synth. activities" into qt-dev
am:
00537efd07
Change-Id: I1ec3fb8fea7f6b5fe292807b3951fb265a9cbb94