- Per comments from ogunwale,jjaggi on ag/2016938, static imports
are preferred when possible, and are part of Android's tacit style guide.
Bug: 36662390
Test: Covered by existing unit tests.
Change-Id: Ic3897dd7a4a9cb665fc3d8c7a171f74494f02a2e
- Do not ever do onDestroy/onCreate cycle for VR activities when
configuration is changed due to VR mode UI change.
- Do not gate on global configuration change check, as updates
to the global UI mode configuration can race with activity
lifecycle changes.
Bug: 36491752
Bug: 36515684
Test: Manually checked activity lifecycle for pre-O, O VR apks.
Change-Id: Ic2739c6e78c1bdfe876bf1302cd0adeaadece15c
This reverts commit 58fc95dc578244b7beb687a48184045dcce788b8.
Bug 36186790
Test: cts-tradefed run cts-dev --skip-device-info --skip-preconditions --skip-system-status-check com.android.compatibility.common.tradefed.targetprep.NetworkConnectivityChecker -a armeabi-v7a -l INFO -m CtsShortcutHostTestCases
Test: cts-tradefed run cts-dev --skip-device-info --skip-preconditions --skip-system-status-check com.android.compatibility.common.tradefed.targetprep.NetworkConnectivityChecker -a armeabi-v7a -l INFO -m CtsShortcutManagerTestCases
Also all unit tests, except for the known failrues.
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest1 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest2 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest3 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest4 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest5 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest6 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest7 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest8 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest9 -w com.android.frameworks.servicestests
Test: adb shell am instrument -e class com.android.server.pm.ShortcutManagerTest10 -w com.android.frameworks.servicestests
Change-Id: I733ee7e12a419ee7ea17ca67c56afe7b039d189a
CALL_PRIVILEGED and CALL_EMERGENCY APIs are used
by vendors and Android Wear and should be moved
to @SystemApi to pass CTS tests.
Bug: 36566521
Test: CTS tests
Change-Id: I73a0b2c4e551b4738c4c322d9822a85ee19d269b
Instant apps can no longer see services that haven't been
exposed to them via the visibleToInstantApps attribute.
Change-Id: I6fd78067d1253825668d67b9e17dd3a0703f5d57
Fixes: 35871716
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.EphemeralTest
- Ensuring that we can update the stack bounds of non-docked stacks upon
rotation while split screen is enabled (previously disabled)
- Fix issue where subsequent bounds calculations were using the animation
target bounds from the prior orientation
Bug: 36657966
Test: android.server.cts.ActivityManagerPinnedStackTests
Change-Id: I810e35f907721ef5c781b914adac3273ea8da5c8
- Give the app 5 more seconds to restart following a crash
- Presume that system-default wallpapers are robust, and don't fall back
to showing nothing at all if timing or update problems arise
- Improve logging about static imagery handling during boot
- For now, turn on a bit more logging about wallpaper activity
Bug 36573894
Bug 34979999
Test: manual
Change-Id: I787a351f1251b83451d55bb98a4e0de9ce17836a
Since ICS MR-1 [1], InputMethodManagerService (IMMS) establishes two
connections to an IME: one is for general connection and the other to
allow the system to adjust the IME's performance characteristics much
more like a foreground activity. The tricky point is that the former
connection can be re-connected not only IMMS#startInputInnerLocked() in
but also in IMMS#showCurrentInputLocked().
It turns out that some previous attempts to adjust BIND_ flags for the
former connection [2][3] were not applied to
IMMS#showCurrentInputLocked(). This CL addresses that inconsistency by
make it clear that IMMS establishes up to connections to the IME.
[1]: Id1f73de66dc93d63212183958a72119ad174318b
2c84cfc001fb92a71811bf7384b7f865ff31ff9d
[2]: I1724113f42abe7862e8aecb6faae5a7620245e89
c8230519728b14065effd3b7d4eca273ff86160c
[3]: Ie5793fd9b40d980fa18f80246326511ed6ae0597
f0f94d129b6eb3c48624e915898d86d4f2de59ff
Test: Manuall tested as follows.
1. Build and flash an OS image.
2. Complete the setup wizard (if any).
3. tapas LatinIME && make -j
4. adb install -r out/target/product/generic/system/app/LatinIME/LatinIME.apk
5. Run a test program that keeps calling IMM#showSoftInput()
6. adb shell ime enable com.android.inputmethod.latin/.LatinIME
7. adb shell ime set com.android.inputmethod.latin/.LatinIME
8. adb shell dumpsys activity processes android
Make sure that there is a ConnectionRecord to
com.android.inputmethod.latin that has "CR !FG UI !VIS" bits.
9. adb install -r out/target/product/generic/system/app/LatinIME/LatinIME.apk
10. adb shell dumpsys activity processes android
Make sure that there is a ConnectionRecord to
com.android.inputmethod.latin that has "CR !FG UI !VIS" bits.
Fixes: 36727763
Change-Id: Ib7fa34b21e1fb8bb5b19a9b08e36d0565f3dd266
Update fonts.xml to use NotoSansKhmer-VF.ttf.
The weight range of Khmer is also extended to have 9 weight instances
(three more than Roboto with 200, 600 and 800).
The width range for Khmer is left alone partly because of an apparent
lack of support in fonts.xml for non-normal width fallback fonts.
Note that Noto Sans Khmer UI is left alone because of a baseline issue.
BUG: 22667753
Test: See the QA instruction in comment 10 of the bug.
Test: fontchain_lint
Change-Id: Idf6d4fec86822663ac08feb8979edacbc6c709a0
The configurations that are managed by "Saved Networks" page are
centered around the abstraction of AccessPoint. Since we will
need to manage Passpoint configuration in the "Saved Networks"
(for configuration removal), encapsulate necessary information
in an AccessPoint for a Passpoint configuration.
Bug: 34207710
Test: manual test
Test: runtest --path
frameworks/base/packages/SettingsLib/tests/integ/src/com/android/settingslib/wifi/AccessPointTest.java
Change-Id: Ide556f5ec6c4ef9e1f82016efe17dc9860f298de
Yum!
Also needed to have a Context.revokeUriPermission() variant that is sane,
so reasonable CTS tests can be written.
Test: new ClipDataJobTest added.
Change-Id: Ia3135ea788a6e32c971bae7dab3a844d0ef4139c
On ViewState: split value into mCurrentValue and mAutofilledValue.
On Session: replacing mAutofilledDataset by mDatasetWaitingAuth and
ViewState.getAutofilledValue() (mAutofilledDataset is still needed,
but will be removed in the first partitioning CL).
Also fixed a missed 'return' on TimePicker.autofill()
Bug: 35707731
Test: CtsAutoFillServiceTestCases pass
Change-Id: Icc32701ae3e499a77d99e6ae1daa7d070a3df631
This follows the pattern established by other "out" fields
in BitmapFactory.Options
Bug: 32984164
Test: CtsGraphicsTestCases
Change-Id: Ie72e47338b578b41c550453e2698d2d49eddf6da
It sounds like CTS prefers having the "none" lockscreen instead of
a "swipe" lockscreen, so give it what it wants. This brings us back
to matching the original behavior of the NYC test.
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.DirectBootHostTest#testDirectBootNative
Bug: 36789738
Change-Id: Ibc392362dda22b3df0bc98aa525c65fe70eeb861
All the trivial cases, plus some fixes to try to
mitigate collisions with the complex ones.
Complex services to follow in another CL,
Bug: 32584866
Test: make framework services
Change-Id: Ie9663600171d8ede11676e9d66f009dbb06def03
