Roman Birg fccccda787 SetupWizard: add a CM-specific setup-complete settings key ... Android uses Settings.Global.DEVICE_PROVISIONED and Settings.Secure.USER_SETUP_COMPLETE and the system responds to those database entries, such as allowing the keyguard to be visible, or maybe pulling the statusbar down. Since we still depend on some of Google's setup wizard, it also keys off the same table rows and it may decide that the device is now provisioned when we still haven't finished our own setup wizard, so let's add another key that we have control over to show the real state of OUR setup wizard. Ticket: CYNGNOS-2431 Change-Id: Ic21689625f6d80e209161762ace741918b972aba Signed-off-by: Roman Birg <roman@cyngn.com>		2016-04-22 08:29:40 -07:00
..
res	SetupWizardTest: Add a test to mark as setup complete	2015-01-26 16:25:28 -08:00
src/com/cyanogenmod/account/tests	SetupWizard: add a CM-specific setup-complete settings key	2016-04-22 08:29:40 -07:00
Android.mk	SetupWizard: Fix test app building in 13	2016-02-01 13:53:56 -08:00
AndroidManifest.xml	SetupWizard: Refactor for better transitions out of OOBE	2015-03-09 14:49:31 -07:00