1. Invoke it in BOOT_COMPLETED
2. Set it periodic
3. Change the anomaly history from 3 days to 30 days
Bug: 72385333
Test: RunSettingsRoboTests
Change-Id: Ib59a85f3dffd6c094ff400a75bec44d4c65bce44
If it is excessive bg anomaly and auto restriction is on, then
restrict the anomaly in receiver and store it in database.
Also in this cl we move the anomaly logic to a JobService, so all
works are done in a background thread and won't interfere the main
thread.
Bug: 72385333
Test: RunSettingsRoboTests &&
Will add auto restriction test once robo framework is updated(b/73172999)
Change-Id: Id0ec5fb449ce26bf19a292bcbe63838d621cfd8e
Store a local version number in Settings. If new version comes,
upload config to StatsManager.
Bug: 72385333
Test: Will add robo test once robo framework is updated(b/73172999)
Change-Id: I03f5ee6f6e013746397d39b8d2b52ce587825b11
This BroadcastReceiver is triggered when anomaly happens. Inside it
we need to extract anomaly info and store it in the database.
Bug: 72385333
Test: Will add robo test once robo framework is updated(b/73172999)
Change-Id: Ib36af377fa2dff8026e7f0fcbec9575366e39cf9
