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	Automatic translation import	2016-04-16 21:00:27 +03:00
src/com/cyanogenmod/setupwizard	SetupWizard: add a CM-specific setup-complete settings key	2016-04-22 08:29:40 -07:00
tests	SetupWizard: add a CM-specific setup-complete settings key	2016-04-22 08:29:40 -07:00
.gitignore	SetupWizard: Initial commit	2015-01-15 16:04:44 -08:00
Android.mk	SetupWizard: fix build break for incorrect java lib linking	2016-02-09 16:33:15 -08:00
AndroidManifest.xml	Themes: Refactor themes to CMSDK [6/6]	2016-03-01 09:58:55 -08:00
proguard.flags	SetupWizard: Update proguard for play services 8115000	2015-10-23 15:23:38 -07:00