If the database needs to be created, it will not be upgraded. So, if the
device was provisioned and the table wasn't created, we don't upgrade
and so we cannot bring the old flag to the new location.
Fix this by setting the new cm provisioned flag on database creation.
Ticket: CYNGNOS-3017
Change-Id: I1e961f1cb2d06c55c1e92ef63c6dbaee17dbc304
Signed-off-by: Roman Birg <roman@cyngn.com>
The database is innaccessible during creation through
the android resolver interfaces, thus, no defaults were
loaded even though the code would execute.
So rewrite the DatabaseHelper to create a singular bulk transaction
per table when default settings are to be loaded, and provide
verification tests for the CMSettingsProvider.
TICKET: CYNGNOS-1706
Change-Id: I3d8c5f25704ec9620fe57b82865531fb976a516f