A WindowContainer's children are sorted so the focused child is at the
end of the list, so RootWindowContainer needs to iterate from end to
start when looking for the focused window.
Bug: 36590788
Test: DisplayContentTests#testFocusedWindowMultipleDisplays
Change-Id: I56e6b7d2054bc1e74b54a4f99706a08d278fa2e1
If an app specifies SCREEN_ORIENTATION_BEHIND, then use the orientation
of the app behind it regardless of the visibility state of the app
behind.
Fixes: 35281868
Test: bit FrameworksServicesTests:com.android.server.wm.WindowContainerTests
Test: bit FrameworksServicesTests:com.android.server.wm.AppWindowTokenTests
Test: bit FrameworksServicesTests:com.android.server.wm.TaskStackTests
Change-Id: Ieba4e4bb1a7f47cd6f082491d37fcabcf5bd5199
It was commented earlier because of a crash. Since that issue has been
fixed, uncomment the test.
Bug: 27803922
Test: runtest -c com.android.server.am.ActivityManagerServiceTest frameworks-services
Change-Id: I5f2b1b0bffe032633f42c8c34ed8a7ae5a3dfc10
Ignore maxAspectRatio values less than 1.0 and set it to 0 which
means use device aspect ratio.
Change-Id: Ib2c76f6232e3f7521a1a4565d7c0c9e1de9c9eac
Fixes: 36606641
Test: cts/.../run-test CtsAppTestCases android.app.cts.AspectRatioTests
Adds two flags to watch for movement outside of the starting area of the
gesture, one for dismissing and one for minimizing.
Test: - Have PiP at bottom of screen, drag to top and fling down (does not
dismiss)
- Have PiP at left or right edge of screen, drag PiP to opposite
edge and fling to other side (no longer minimizes)
Bug: 35358628
Change-Id: I007e2c2c688254dbe1abaecdedc28e281278def8
- Increase the size of the text sent as context to the classifier
- Pass regex match hints to the classifer
Test: Build still works. Regex hints logged correctly. The hints won't
matter until we've actually passed in this values to native code. Native
library test will be written and I've got a tracker bug to write more robust Java tests.
Bug: 35416389
Bug: 36584397
Change-Id: I29e56189b388b36dc0cc7a8bb13ef237ff55be7b
It was checking if the weak reference pointee was null, but not for a null
weak reference per se.
Fixes: 36643768
Test: manual verification
Test: CtsAutoFillServiceTestCases pass
Change-Id: I106dfd4a91ff1d45f8cb3141a992b06cbe460367
Make sure it starts up to everything showing and that the StatusBar
calculates the bar mades after it is attached.
There is still a bug where the behind scrim is showing during SUW,
but this fixes many of the issues besides that case.
Test: visual
Change-Id: I93314c607e374c97d5c06f936ef8b7e07e057648
Bug: 36407135
to meet CDD requirement.
bug: 33423136
Test: manual - shared images in Camera. More CTS and GTS tests to be
added.
Change-Id: I0e0c759bec11137e2290f4a43a92be8e97eef022
Various zones in timezones.xml were being identified by old
IDs. The settings picker and setup wizard uses the exact
ID when pre-selecting the user's current zone. Since the
autodetection uses the new IDs in places like Buenos
Aires users would not have the correct zone pre-selected
during setup.
Thanks to Marcio Ikeda of LG for the report.
Other legacy IDs found with:
for TZ in `grep 'id=' timezones.xml \
| awk -F\" '{ print $2 }'`; do \
grep ${TZ} ~/Downloads/tzdata2016g/zone.tab > /dev/null; \
if (( $? != 0 )); then echo Bad: ${TZ}; fi; \
done
New IDs found using tzdata NEWS and "backward" file.
Test: Manual testing: selection of the zone in the settings
Bug: 36469833
(cherry picked from commit b4d003da66beb414e8e7fcec94a82a53027dbbfa)
Merged-In: I8c20494a48870cdc600854756061e86db730e14a
Change-Id: I829a70921eb13b763b5446820c87672615f2524d
On second thought, let's set accept_ra_rt_info_m**_plen in
Netd (InterfaceController::initializeAll())
This reverts commit 25870a2c9effd7a7d31c0678c34a6e952b2d56a1.
Change-Id: I22b000623bb852e375385d4aae789d007e84ba3d
