The softap supports more features which related hardware.
The config store from cloud will meet the convert will not only for band
but also for others config. Revise the code to make it more general.
PS: UI wording change will in another CL# which need to discuss with
UX designer.
Bug: 142752869
Test: Manual test, restore from cloud to see if notification show or
not. And check the log.
Change-Id: I279e62841d4b14d3ba5b6792bc289c0adb8a223d
Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library.
Bug: 145132366
Test: m && diff unsupportedappusage_index.csv \
git diff HEAD^ HEAD | grep '^[+-][^+-]' | grep -v '.import'
Change-Id: I853372f3c6fef905553bb31be4f1bb48df735f7a
SettingsBackupAgent will send out the notification
itself instead of delegating it to WifiManager.
Bug: 144218444
Test: Removed AP Band conversion check to always trigger
notification when restoring from backup.
Follow steps at: https://developer.android.com/guide/topics/data/testingbackup
Verified that notification is displayed when restoring
from backup.
Verified that expanding notification by dragging down
shows full notification text.
Verified tapping on the notification opens the tethering
Settings page, and also dismissed the notification.
Change-Id: I729b1cbf443229687c086982d51b96f326b534e1
Currently the validators static initialiser gets triggered when the
relevant settings class is accessed. Moving them out to the
SettingsBackupAgent (which is the only place they're used) has two
main advantages;
1) All apps accessing the Settings classes no longer trigger the
static initialisers and so are faster.
2) Putting them in SettingsBackupAgent gets them off the
bootclasspath of all apps and makes the framework jars smaller.
Bug: 139449903
Test: atest SettingsProviderTest RunBackupFrameworksServicesRoboTests CtsBackupTestCases CtsBackupHostTestCases GtsBackupTestCases GtsBackupHostTestCases
Change-Id: Ie740c1ea25a01c715964175094677af2e3328732
We're currently importing the whole of SettingsLib into the Settings
Backup Agent just to access a single static method. This seems to
have contributed to a the regression which relates to b/139373401.
This CL separates the 3 related methods out into their own build
target so the amount of code included in SettingsBackupAgent is
much smaller.
A later CL will remove the original location after all usages
have been redirected to this new location
Bug: 139373401
Test: atest SettingsProviderTest SettingsLibRoboTests
Change-Id: I36fbc21daddcf068491b58db01b66f540ac26cf7
Adding the device information to the backup will allow us to restore
data which is device specific if it's appropriate to do so (e.g. device
density)
The device specific settings which will be backed up are;
Settings.Secure.DISPLAY_DENSITY_FORCED
Test: atest SettingsProviderTest SettingsBackupTest
Test: Manual - Density changes during SUW when setting is restored
Fixes: 28437818
Change-Id: Ibc3595cdece3f1ccb4fccaff8212c1c3cb5c9756
