Define a new change id and use it for gating the change.
Test: atest -p cts/tests/signature, atest AndroidTestBaseUpdaterTest
Bug: 30188076
Change-Id: Ic8c85eae0c490a7eca117b74c4326dd50df2b352
Sometimes, we have seen cases that 'set as default' feature does not work properly in ResolverActivity.
This issue occurs when an activity, with 'exported=false' attribute, is included in the list returned by PackageManager.queryIntentActivities().
By the logics in ResolverListController.java#getResolversForIntent(), the activity is removed from the list.
This creates a difference between the list that ResolverActivity sends to PackageManager when calling addPreferredActivity() and
the list PackageManager maintains. Due to the difference, PackageManager does not set preferredActivity requested from ResolverActivity,
which results the showing of ResolverActivity the next time with same action(even though user has set preferred activity).
To handle this issue, we recommend that the removal logic should be removed from getResolversForIntent() method
because it is already handled in ResolverListController.java#filterIneligibleActivities() through ActivityManager.checkComponentPermission() api.
As the result of that, the list which will be delivered to PackageManager is not changed.
Bug: b/135738126
Test: 1. Install 'JustDial' application via Play store
2. Try below command to launch ResolverActivity
adb shell am start –a android.intent.action.VOICE_COMMAND
3. Pick an item on ResolverActivity, then press 'Always' button
4. Repeat the second step again.
(you will see ResolverActivity comes again)
(cherry picked from commit 5cdfeeaca5516a6d64fa259f9a4ffd2955f8d2ab)
When an automatically generated notification group has 4+ persistent
notifications, hitting "clear all" will cause the group to lose its
automatically generated group summary notification. The solution is to
count the number of notifications belonging to a specific group as well
as the number of ongoing notifications. if the number of grouped
notifications > min before grouping limit & the group has at least one
ongoing notification, then the group summary notification will be marked
as ongoing with the flag FLAG_ONGOING_EVENT. otherwise the flag will
be removed.
Bug: 129562864
Change-Id: I65412935fbb4a74de6ac4cf159d4fd2ebe96dae8
Fix: 129562864
Test: atest NotificationManagerServiceTest
- AWT#inSizeCompatMode is overridden by ActivityRecord but they
were used for different purposes.
- Add missing ConfigurationContainerListener of display level.
So the configuration got from ActivityRecord#getParent (Task)
is synced with TaskRecord.
- Initial Task with TaskRecord's resolved configuration instead.
That avoids the orientation being locked.
Bug: 80414790
Test: atest AppWindowTokenTests#testSizeCompatBounds
Test: Launch an unresizable portrait activity, after calling
setRequestedOrientation to rotate, the restart button
won't appear.
Test: 1. Enter split-screen in portrait.
2. Finish the activity in secondary.
3. Launch the same activity from recents.
4. Drag divider to top.
5. Check the orientation is still portrait.
Change-Id: Ib3b54a74e98d1e85ea4f7707f17bac51d6dbe21b
am: ce374538d5 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 5136eefeb3 is in history
Change-Id: I3c2c15efb6d0ede52dc5be3c0797076209b55add
am: b2cbf7c207 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 5136eefeb3 is in history
Change-Id: I91eed42c62ecc338e7e819032ad430d957d18273
am: e121d6d10a -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 5136eefeb3 is in history
Change-Id: Ic61150f73972e2ce9e06900d94ac61755bd351c6
am: 4821ae7fc6 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 5136eefeb3 is in history
Change-Id: Iab7ace52b4add9e7c3f63f439fd4ead520e9c8d4
am: 833d336899 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 3ceaa9b957 is in history
Change-Id: I222a55c751ed1d4eda8aad2e99f508063143def2
am: a2ba1ccfdc -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 5136eefeb3 is in history
Change-Id: Ibdd94e1e6425403022f04f2a7b91c6f1dba2b74e
am: ff059037d5 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 5136eefeb3 is in history
Change-Id: Id39ca9f51d9b61a43ad13c7bdb724e046b8e637b
am: 67e7268757 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 5136eefeb3 is in history
Change-Id: If638f3a41362dbbc07b101df3ddd9d51c2dfb103
am: cbab929395 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 09843a687b is in history
Change-Id: I91f64c2252e7ac3c09bea87c276d2fb5391e7e84
am: 9ec959b8f3 -s ours
am skip reason: change_id I0680034ed9315aa2c05282524d48faaed066ebd0 with SHA1 09843a687b is in history
Change-Id: I8cb6a74fb003c359cf81f5dbf84d77f675dd5b5c
Phone system ui made some changes recently which require
super_status_bar to be updated.
Bug: 142274450
Test: manual (build, flash, no crashing)
Change-Id: Icf1049d0264da57d435600d607c26a612fcaeb3b
