If com.google.android.gms is installed when
com.google.android.setupwizard is not,
our setup wizard crashes.
Fix this by checking Google's setupwizard exists,
and if not, not attempting to launch it.
Change-Id: I6120304dd13dddf07c2769245765a3e98dec51fc
We are working towards a totally new SetupWizard model, so a temp fix
here will get jettisoned when that merges
Change-Id: I01d5cde69515bb46b54e896a1005fe0ffcdb002c
The current version of GMS's SuW has the main activity return as
CANCELED when no network is available. This is the same result as
an actual cancellation (by pressing "Back"), and there's no extra
data to distinguish the two, so the user gets stuck in a loop between
the "no network" page and the one preceding it, unless connectivity
is somehow established. Making connectivity mandatory for OOBE isn't
acceptable, so skip GMS entirely if network is absent (and FRP
isn't enforcing). The only thing it was presenting was a "you
have no network" dialog anyway.
Change-Id: I2abadc79a0823e94da7d3a875ce6db8eae8f143b
(cherry picked from commit d82b2dc88a)
Altough uncommon, development boards and emulators don't have a wireless
interface. In those cases, don't show the wireless setup page.
Change-Id: I0017b2277defdccf7f0bd61cb9606254509f78cc
FRP is kind of pointless if the device is freely accessible. Suggest
setting up a secure lockscreen during setup.
Ref CYNGNOS-3252
Change-Id: Ia807142ab08f388d533b5ee45d1fcbe81071f6d1
- Created and added ModGuide panel.
- Added the ability to chnage navigation color.
- Added the ability to start an app after wizard completion.
Issue-Id: MSC-14
Change-Id: I8e17735d1a9edbd529339982981f8270cde83d96
Both waiting for radio and waiting for data used "is the progress
bar visible" as the "allow to continue" clause. If radio service
state changes arrived while the wait-for-data was ongoing, this'd
terminate the progress bar and make it wait forever.
Additionally, if wifi is connected, don't wait for data at all
Ref CYNGNOS-3126
Change-Id: I81792ac8be00c6a6746af88a62220c727cddc6d8
Instead of waiting for the telephony stack to catch up to the default,
take advantage of the fact that the intent already carries the ID as
an extra.
Also, we were using slotId and phoneId interchangeably, and they're not
the same thing. While it's likely they'll match on a freshly reset
phone, don't assume that. Index everything to subId for consistency.
Ref CYNGNOS-3126
Change-Id: Ibcd767d0124b05d669886190f5d9a98f1a6e5bd7
Handle the possibly thrown ActivityNotFoundException.Changed the generic catch block into a specific catch block to handle ActivityNotFoundException.
Change-Id: Ica1106bab3e569aaa7883898ce6adb3a1a2dd99f
