am skip reason: Change-Id I2d2173a692ec95a7a35b5a24ca466917e59c1da3 with SHA-1 91baff9782 is in history
Change-Id: Ie51107fb80d858bcaa026be2e113438150db8156
am skip reason: Change-Id Iacf1bfe68fa86194e8b75cbfce9aa37c0abfbca3 with SHA-1 18d70ab7b0 is in history
Change-Id: I1730cf15c61939dc88f92862ba1a39974833dd5a
(partial cherry-pick of internal change:
I4457ff2bd466a4c56fed2570e110f251031c2385)
With b/150232615, we will need an explicit value set for the exported
flag when intent filters are present, as the default behavior is
changing for S+. This change adds the value reflecting the previous
default to the manifest.
These changes were made using an automated tool, the xml file may be
reformatted slightly creating a larger diff. The only "real" change is
the addition of "android:exported" to activities, services, and
receivers that have one or more intent-filters.
Bug: 150232615
Test: TH
Merged-In: I4457ff2bd466a4c56fed2570e110f251031c2385
Change-Id: I65a1ca1678048bbf09edc9a0485b673644c8109d
am skip reason: Change-Id I39de5a766b2438b73cbdd8207d8879ee78ebc7e4 with SHA-1 c1a87ae3bc is in history
Change-Id: I1b561e7eb05b454efd9e7f35f1edc19ac01df884
WindowContainer#getActivity() was returning null if there was no
matching activity or hit the boundary. Since we were unable to
tell the difference between the two cases, we would continue looking
for a matching activity from higher level window containers.
Take below hierarchy for example, #getActivity() returns null if
the boundary was TopActivity. So, we were kept looking for the matching
activity from Task#2 and returns BottomActivity.
RootTask
- Task#1
- TopActivity
- Task#2
- BottomActivity
Bug: 156014697
Test: start activity from recents in split-secondary
Change-Id: Ic344e8c1c47e9fa05c4de60be8c6b30f75cdb0bc
This bug occured when offset during pip window expanding animation.
curBounds value is still not expand bounds values, fix it by reset
curBounds if it should be expanded status.
Fix: 154647477
Test: Move pip widnow near and above IME then touch it.
Change-Id: I3d0215b96643c7d33d8d922d41ac12cd6291270e
This CL logs provider info and session info of the system route provider
for debugging purpose.
Set DEBUG = true to gather logs for a while.
Bug: 156723680
Test: manually checking log
Change-Id: I4b020e951ff3b5bd7350cc733c822c702526e260
am skip reason: Change-Id I6f190ae33fc9e724adc0e53d07107e9a1ae0291f with SHA-1 c8607a3a5b is in history
Change-Id: I7c1c8e592f24565bd8246ef1107790f7de57426f
am skip reason: Change-Id I927b7dae779da25589f2198e0480c0f2a788a7e4 with SHA-1 539298c1b9 is in history
Change-Id: I0dd072967f37835146a9e4199837946a36cb60b1
Framework's SystemUserHome and Shell's NullHome activities have no real
Home function and should only be used in bootable CSI products. They
should not exist or be enabled on normal products.
This test can help to find if they exist in the system without needing
to find them via Settings manually.
Bug: 149307007
Bug: 149780604
Bug: 154723738
Test: # On aosp_crosshatch with Shell's NullHome activity
$ atest NullHomeTest
...
arm64-v8a NullHomeTest
----------------------
com.android.test.nullhome (1 Test)
[1/1] com.android.test.nullhome.NullHomeTest#checkNullHome: FAILED (127ms)
# On aosp_crosshatch without Shell's NullHome activity
$ atest NullHomeTest
...
arm64-v8a NullHomeTest
----------------------
com.android.test.nullhome (1 Test)
[1/1] com.android.test.nullhome.NullHomeTest#checkNullHome: PASSED (2ms)
Change-Id: I6f190ae33fc9e724adc0e53d07107e9a1ae0291f
Merged-In: I6f190ae33fc9e724adc0e53d07107e9a1ae0291f
(cherry picked from commit c8607a3a5b)
