The feature provider contains API that query aware info.
By default it's false.
Test: make -j RunSettingsRoboTests
Bug: 122574999
Change-Id: I7148258768a4dad1967fd0e0b23b79654e5a3d41
When a device has multiple SIMs, at the bottom of the SIM details page
we show a chooser with an icon for each SIM card. This UX design is
being supplanted by the new network and internet v2 design where there
is a list of networks you can get to from the Network & internet
homepage. So when the v2 mode is turned on, we don't want that bottom
navigation to appear.
Bug: 116349402
Test: visual (will remove existing tests for this feature eventually)
Change-Id: I9cae479a1f4e689adcc4f4262661b10edbbbf2d3
When a device supports simultaneous connection to multiple mobile
networks, we want the "Mobile network" entry on the Network & internet
page to list the number of active SIMs and when clicked, go to a page
that lists them all.
Bug: 116349402
Test: make RunSettingsRoboTests
Change-Id: Ie642d7801cda07dcbbe74d42c234db6605566be4
mIsHalfWidth in ContextualCard is too generic to identify its
responsibility, it is used to hold the value of is_support_half from
database and used to decide the card width. Also, it limits the
relationship of CardType-to-Renderer not to be extended to one-to-many.
To deal with this, we replaced mIsHalfWidth with mViewType to implement
one-to-many relationship of CardType-to-Renderer, and removed all
related logic of mIsHalfWidth.
Bug: 121303357
Test: robotests, visual
Change-Id: I03e14392272194424f317d11bf9d0d794a6133f4
The following Activity classes in the Settings have been marked with
PRIMARY_PROFILE_CONTROLLED = true since work profile was originally
implemented [1].
* Settings$AvailableVirtualKeyboardActivity
* .inputmethod.InputMethodAndSubtypeEnablerActivity
* UserDictionarySettingsActivity
* .inputmethod.UserDictionaryAddWordActivity
This means that even if they are explicitly launched for a managed
profile user, they are always re-launched for the profile owner user
For instance, the following command just ends up launching the system
IME settings for the user 0, not user 10.
adb shell am start --user 10 \
-a "android.settings.INPUT_METHOD_SETTINGS"
In order to enable per-profile IME mode, we need to remove
PRIMARY_PROFILE_CONTROLLED from those classes.
Unfortunately, the settings is baked into ApplicationManifest.xml
hence we canot simply hook it up with the runtime flag
InputMethodSystemProperty.PER_PROFILE_IME_ENABLED. Thus this CL
simply remove PRIMARY_PROFILE_CONTROLLED from those classes, with an
assumption that users basically will not see those Activity classes
running under managed profile users unless per-profile IME flag is
enabled. This is because both LanguageAndInputSettingsActivity and
SettingsActivity are still marked PRIMARY_PROFILE_CONTROLLED=true.
This means that almost all user-visible entry points are still be
running with profile owner's user ID.
Note also that because of Settings redirection implemented with
Settings#CLONE_TO_MANAGED_PROFILE, what are shown on those Activity
classes are basically correct. What they cannot do without enabling
per-profile IME is updating actual secure settings.
[1]: If3ec3866778282219267481b8f419774f7f2c9de
2513851ace
Bug: 120748696
Test: Manually done as follows.
1. adb root
2. adb shell setprop persist.debug.per_profile_ime 1
3. adb reboot
4. Install Test DPC.
5. Enable managed profile with Test DPC.
6. Open "Files" app for the main profile.
7. Tap the search box to show AOSP Keyboard.
8. Long tap the comma key, then "Lauguage" on the "Input options"
dialog.
9. Uncheck "Use system languages" then check "English (UK)".
10. Open "Files" app for the work profile.
11. Long tap the comma key, then "Lauguage" on the "Input options"
dialog.
12. Make sure that "Use system languages" is checked.
13. adb shell am start --user 10 \
-a android.settings.INPUT_METHOD_SETTINGS
14. Make sure there is no Toast message
"You're using this app outside of your work profile".
15. adb shell am start --user 10 \
-a android.settings.INPUT_METHOD_SUBTYPE_SETTINGS
16. Make sure there is no Toast message.
17. adb shell am start --user 10 \
-a android.settings.USER_DICTIONARY_SETTINGS
14. Make sure there is no Toast message.
Change-Id: I6ee1f226a616bb5f802f8e1d3b6f1dbbe492c6e5
Uses connected access point to start DPP in Configurator-Initiator role directly.
Bug: 118794978
Test: RunSettingsRoboTests
Change-Id: Ie2d5661fdef3588bb597d4a7e4dfe5f981737c84
1.Scan valid access points for DPP configurator by using WifiTracker.
2.Allow user to add a new network for DPP configurator.
Bug: 118794978
Test: RunSettingsRoboTests
Change-Id: I36504d28dec7d2c9091aa6c35ebe2495045681f7
1. Don't create UiBlockerController if there is no related controller
2. Don't update visibility if UiBlockerController is null
3. Use findPreference() from DashboardFragment, which already has null
check.
Change-Id: Iee24c64317fb9d5a1cf2076d25728af485d390c5
Fixes: 122807414
Fixes: 122805831
Test: RunSettingsRoboTests
current "link speed" in UI is renamed to "Transmit link speed".
Also Added Receive link speed in network details.
Bug: 120497598
Test: Connected to AP and verified the Rx link speed in Network details.
Change-Id: I01cf7362a27ad78ddfaef68efae4d07cbd14fc55
All DPP public API and constants renamed to use Easy Connect,
which is the WFA public technology name. Update the settings code to use the
new API names.
Bug: 122851551
Test: atest DppManagerTest
Test: act.py -c ../WifiDppConfig.json -tc WifiDppTest
Change-Id: Ib531393a81526c468c978e31f1c62c5022245d55
This change makes the default SMS shortcut in App info launch the new
default app UI based on roles, since we've migrated default SMS
mechanism.
Bug: 110557011
Test: atest DefaultAppShortcutPreferenceControllerBaseTest && atest DefaultSmsShortcutPreferenceControllerTest
Change-Id: I074e41433fe912309082f1e9c54bf74200297dd1
am: 850fdb32e9 -s ours
am skip reason: change_id Ia2548355282498bceeffddb564de32a6cb857c66 with SHA1 16322a0271 is in history
Change-Id: Iab476273c6b332525177fe76f5f8d779ffe0f0c7
