The file is empty and not used, and its presence confuses people.
Remove it.
Bug: 64382372
Test: make
Change-Id: I8646a78b96d81dd38e5c58460d354430babd9d53
Previous CL Ide42eacc8db4e403432ddd9d952495dda85db0ac left it
unsorted which makes it difficult to programatically add new APIs.
Bug: 64382372
Test: make
Change-Id: Iff35925d9ad64d8a98e59c1b8c4094d59a1c3a3c
Added an annotation necessary to allow the power manager CTS test to
access the non-public method nap.
Test: adb install -r \
out/host/linux-x86/cts/android-cts/testcases/CtsOsTestCases.apk
adb shell am instrument -e class android.os.cts.PowerManagerTest \
-w android.os.cts/android.support.test.runner.AndroidJUnitRunner
Change-Id: Ida939f074654bef351e2b8fd563c8463431ce9c6
Fixes: 77907164
This is from CtsOsTestCases which we cannot exempt because it also
tests StrictMode.
Test: cd cts/tests/tests/os && atest .
Bug: 77909325
Change-Id: Id0fee2c48612d69c5cf4f31bd32e29a19ffd8f0e
When entering split screen, the secondary window changes position so
it's below the primary split screen when minimized. The WSA at the same
time is also changing size to fit the area. However, the size doesn't
change until the client requests a new size and a frame with the correct
size comes in. This causes the stack to update position before the
resize which causes content to get cut off and then a jump when the resize
completes.
This change updates the WSA position as soon as it recognizes that the
stack changed position due to entering split screen secondary. The WSA
sets its position as the negative of the stack position, making the
calculated window position at (0,0). When a relayout is requested, the
WSA's position is requested back to (0,0), deferring until the new frame.
This will put the WSA position at (0,0) when a frame with the correct size
is drawn. This places the window position at the stack's new position in
the same transaction that a WSA frame with the new size is drawn.
Change-Id: I8c88d7784f827d66926fb5c382af2346028dc48f
Fixes: 74354855
Test: Entering split screen with quick step is smooth
Test: Entering split screen with old launcher still works
This applies to SpannableString methods:
- charAt(I)C
- getChars(II[CI)V
- getSpanEnd(Ljava/lang/Object;)I
- getSpanFlags(Ljava/lang/Object;)I
- getSpanStart(Ljava/lang/Object;)I
- getSpans(IILjava/lang/Class;)[Ljava/lang/Object;
- length()I
- nextSpanTransition(IILjava/lang/Class;)I
(these are all already in the greylist)
and one method from android.app.backup.FileBackupHelperBase:
- writeNewStateDescription(Landroid/os/ParcelFileDescriptor;)V
(added in this CL).
We won't fix this properly in P, so greylist the uses for now.
Bug: 64382372
Bug: 76424618
Test: make
Change-Id: I4c4ef13338b1fa2f7f21c07c63d88d3559d10341
Migrate DefaultLogger implementation to SelectionSessionLogger.
This cleans up after the API refactor and fixes two bugs:
- All events are currently logged twice.
- Interfaces accept a null signature, but it currently crashes the legacy logger.
Bug: 73392698
Bug: 77659305
Test: atest FrameworksCoreTests:TextClassificationManagerTest
Test: atest FrameworksCoreTests:TextClassificationTest
Test: atest CtsViewTestCases:TextClassificationManagerTest
Test: atest CtsViewTestCases:TextClassifierValueObjectsTest
Test: atest CtsWidgetTestCases:TextViewTest
Test: atest CtsWidgetTestCases:EditTextTest
Test: Manually examined logs
Change-Id: I0d2b925abf5cab12d71fc2cc0fa527530c86ab10
