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>
If a device lacks NFC feature, pass an extra to googles
setup wizard to spress the device to device setup.
Change-Id: I05341f14c4a4753cb5a595734eb337eb10d505a4
TICKET: CYNGNOS-2258
Googles SetupWizard expects a specific flow for the restoration
process -- amend the intent for gms restore to abide.
Change-Id: Idf4c3b813676c5456770627067a42697ab756bb0
TICKET: CYNGNOS-2233
This reverts commit 070fbeaf5d.
We still need to show the fingerprint setup screen which allows
the user to skip setting up a fingerprint if they choose to do so.
Change-Id: Ifa49ad1ac0e5cf113290b973ac5e9cd8abdbed9a
TV devices like fugu don't have a default input method and expect to
be able to pair the bluetooth remote during setup without having to
manually initiate it with the bottom button on the device.
Change-Id: I88246fe9b28a85dc334c0108b818e78cb29491bb
This patch is to mitigate theming problems with multiple users.
Once themes properly support multiple users we can revert this.
Change-Id: Idc89a273bc1563fc668ca2a5a591cf133e8d5406
(cherry picked from commit 836f867086ce22c6c9c2c26bba4440177b1d9099)
Roman Birg