The lingering network type is actually the bit that controls network
torn down. UNKNOWN here means the APN can work on any RAT.
Just copy network type into lingering network type, so network torn down
can work normally.
Fix: 341006308
Test: unit test
Change-Id: Ia60ad3e012bec7364aa35535de1363cd7c0ccdda
later in the background.
Bug: 327052480
Test: atest com.android.settings.accessibility
Flag: EXEMPT bugfix
Change-Id: I9940772e60e2137aad2b3b70902565e36fb7aad6
As strict mode is in place, the default strict_mode is now set to true. We are encourage teams to write tests in strict_mode to make tests Bivalent (able to run on device and devicelessly)
For more info on strict mode: go/roboStrictMode
Test: atest SettingsRoboTests
Bug: 334089788
Change-Id: I4381446dac381a34747043c564cf5288a2e16725
Merged-In: I4381446dac381a34747043c564cf5288a2e16725
AccessibilityActivityPreference to encapture the method for loading the
content for AccessibilityService and AccessibilityShortcutInfo
Bug: 327052480
Test: atest com.android.settings.accessibility
Flag: EXEMPT mechanical refactor
Change-Id: I698a1d366e8ab82c8efdcae293a1ba1771925121
When launch setting page for specific keyboard, it will route to PK
setting first, add flag NO_HISTORY to make PK setting not been added in
stack.
So that when user navigate back, it will not back to PK setting,
which will be more consistent.
Update navigation path from:
Device Detail -> Physical Keyboard Setting -> Keyboard Detail Setting
to
Device Detail -> Keyboard Detail Setting
Bug: 330130137
Flag: N/A
Test: verify on device
Change-Id: I8d6d6a8a534dec5cd7330c4d47b38a46be76fc4d
This version still only loads preferences once, but the previous attempt
commit 774bbc1ff2
created a "sliding" effect as the preferences were loaded after the page
became visible to the user.
Also reorders methods so that their position in the source file matches
the Activity lifecycle ordering.
Bug: 327052480
Test: existing A11y Settings robotest presubmit
Test: Launch this page from the Settings app, observe no sliding UI
Flag: NONE low risk visual bug fix
Change-Id: I44312ada359aef7dec8eb27c57cde2a8e00f254b
Also a couple of icon-related fixes:
* Use the proper context, since we need theming (this also means it cannot be stored in IconLoader, which is a singleton, and must be supplied).
* Force apply the standard size and tint, since app-provided icons may be arbitrary.
* Fix the schedule-time icon (the viewport size was incorrect).
Bug: 308819461
Fixes: 333528437
Flag: android.app.modes_ui
Test: atest com.android.settings.notification.modes
Change-Id: Iae447c8c4a0218a8bc989c01d1d56d0c06abd8e7
- Show cdma network mode choices if current radio supports 3GPP and
3GPP2 radio technologies at the same time
Change-Id: I2d849e2eddc2c5bef289f39c015ebc6c744edcab
If in ECBMode, start ACTION_SHOW_NOTICE_ECM_BLOCK_OTHERS to show a
dialog instead.
This align with the current airplane mode switch.
Fix: 191943857
Test: adb shell cmd phone emergency-callback-mode
Test: unit test
Change-Id: Icf646cd76990d621121b4367ec0fd02a3880b85c
