Respect forceNonSystemPackage param when creating new Setting objects.
Previously, new settings created via DeviceConfig.setProperty() resulted in the forceNonSystemPackage param being ignored and the makeDefault param being overwritten to true. This caused new Setting objects added this way to always save their initial value as the default value. This caused problems in tests that tried to make local changes and later reset them to the prior state. Test: atest FrameworksCoreTests:DeviceConfigTest Bug: 147862338 Change-Id: I98a4585fc39cb8c39e630c0dcd318b05a085fcc3
Loading
Please register or sign in to comment