The parameter was always true (it was a remnant of a previous
approach).
Test: atest FrameworksCoreTests:com.android.internal.power.MeasuredEnergyStatsTest
Bug: 174818228
Change-Id: I3be5392966c3455b2df145044809a581abbf245c
Data stored to disk are extracted into an incident report for timeseries
visualization which shows walltime and may span multiple reboot sessions
so storing walltime is better suited than relative time since device boot.
Bug: 179712445
Tests: atest FrameworksServicesTests:PowerStatsServiceTest
Signed-off-by: Thierry Strudel <tstrudel@google.com>
Change-Id: I5ae8e2fe22f1ab9ea960e5be8fef4e9fb1cc10f0
Add more server flags that can be pushed to devices to influence geo
detection service behavior.
This renames DeviceConfig as ServerFlags and introduces an intermediary,
the ServiceConfigAccessor, to hide details and handle changes to config
values that need the location_time_zone_manager to restart.
Simulating server flag changes example:
adb shell cmd device_config put \
system_time primary_location_time_zone_provider_enabled_override false
Inspecting manager / provider states:
adb shell dump location_time_zone_manager
The following manual tests were conducted to check the plumbing:
Modifying settings behavior:
adb shell cmd device_config put \
system_time location_time_zone_detection_setting_enabled_override true
<Confirm the settings value cannot be changed by user>
adb shell cmd device_config put \
system_time location_time_zone_detection_setting_enabled_override false
<Confirm the settings value can be changed by user>
adb shell cmd device_config delete \
system_time location_time_zone_detection_setting_enabled_override
<Confirm it returns to normal>
Disabling the feature / location_time_zone_manager:
adb shell cmd device_config put \
system_time location_time_zone_detection_feature_supported false
<Confirm SettingsUI (after restart) doesn't show the geo detection option>
<Confirm manager is not started>
Enabling the feature / location_time_zone_manager:
adb shell cmd device_config put \
system_time location_time_zone_detection_feature_supported true
<Confirm manager is restarted>
Note: "cmd device_config" doesn't allow multiple config keys to be
changed at once, and any change to service config keys cause the
location_time_zone_manager to restart. When changing multiple, set
"location_time_zone_detection_feature_supported false" to stop the
manager, and "location_time_zone_detection_feature_supported true" when
all changes are done.
Test: Manual testing (see above)
Test: treehugger
Bug: 178107773
Change-Id: I07b57add1ed47197587907b9f0a85f38acc0a76a
This is the changes in Settings (to store the current screen side) for
the one-handed keyguard. This also checks in symbols.xml to expose the
platform config to SysUI (the lines in symbols.xml are currently in
config.xml; I'm assuming that a previous revert didn't remove them).
Bug: 170858298
Test: included.
Change-Id: I9d91a9360c821562634e83295f5e2e340f6de1d5
We cannot try to enable icon overlay on managed users because neither
launcher nor the wallpaper picker is installed on managed profiles.
Trying to do so will result in a SecurityException.
Fixes: 180461062
Test: manual
Test: atest ThemeOverlayApplierTest ThemeOverlayControllerTest
Change-Id: I25a07f7a6aa41b6c92c8928091219c4b0fb22770
Fix a race condition where the ProcessRecord has been invalidated
but it hasn't been removed from LRU list, meanwhile another thread
iterates the LRU list with the ProcLock, thus the ProcessRecord
should be validated.
Bug: 180849723
Test: atest CtsAppTestCases:ActivityManagerTest
Test: Manual - randomly kill other processes during above test
Change-Id: I76570a7717b98b499b865acf590af7a2133c36d9
When window has options to specify the target root id, by default it
should be attach to the target root.
Also cleanup some documentation.
Bug: 155441180
Test: atest WmTests:DisplayAreaPolicyBuilderTest
Change-Id: I9cbfc974cd502a6cadd919b169cb9b8f9ce634f7
