summaryrefslogtreecommitdiff
path: root/docs/html/sdk/api_diff/24/changes
diff options
context:
space:
mode:
authorSvet Ganov <svetoslavganov@google.com>2016-05-10 08:44:48 -0700
committerSvet Ganov <svetoslavganov@google.com>2016-05-10 08:48:00 -0700
commita8f9026d22dae7fcb385bd06ed475a5dd36993c3 (patch)
treed972412d6beb882b15416c7a24dafd54f311795c /docs/html/sdk/api_diff/24/changes
parentba83e90e1825f3e40a16370babc83b8ac0645cf9 (diff)
Persist settings on a dedicated background thread
Settings were persisted on the system background thread but during first boot the device is under heavy load and persisting settings competes with other system components using the shared background thread. As a result persisting settings can be delayed much longer than the expected 200ms. This can cause issues with setup wizard being skipped/went over and its component disaabled being persisted but the setting whether the device is provisioned not being persisted - now if the device boots it will have no SUW but also the home button would be missing. Generally, we need a tansactional abstraction in the system process to peform all delayed operations atomically. bug:25472484 Change-Id: I8e0cf7ffa32e86e36e777964eb0c3cc7de02d3c3
Diffstat (limited to 'docs/html/sdk/api_diff/24/changes')
0 files changed, 0 insertions, 0 deletions