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)
Helps with an issue where qsb widget doesn't work when
running through oobe without network.
CYNGNOS-2833
Change-Id: I83666deea5a27d74669691c4ab991b1b618edb0a
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
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
* Launches GMS TOS per documentation
* Filters out redundant location page if GMS present
* Uses setupwizardlib for some helper functions
* Hide notification icons
Issue-id: CYNGNOS-2599
Change-Id: I4b59592f0b84d0eb0eafe365eab3bad77c1f76ff
People generally identify their SIMs by the emitting carrier, not
the network they attach to. In roaming or MVNO scenarios, these
are likely not to be the same, leading to confusion in SIM selection.
Ref CYNGNOS-2496
Change-Id: I0ecd8e7511fd4229d6ce7629b1f97aa83a1a6254
If a user goes through the gms flow, logging in, disabling
backup, getting kicked over to restore, and deciding to
set the device up as new, the existing logic would reprompt
since the flow causes the load action to happen again.
Now check for account existance, and skip the setup if true.
Change-Id: I3502294d54fcb4e202dca37ff7c6165da4401808
TICKET: CYNGNOS-2459
(cherry picked from commit fe7ac15220)
If a user skips through google setup, make sure we're handling
the result correctly.
Change-Id: Ie2385dbd45c187dc1a90eab4a519094eae2caa72
TICKET: CYNGNOS-2258
(cherry picked from commit 0410f846bb)
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
(cherry picked from commit d114a09647)
If a user logs into Google's SetupWizard with their
gmail account, they need to be prompted with a restoration
picker -- otherwise, if they have a valid restoreToken
and restoreAccount, we can assume that they came from a
Tap & Go scenario and begin restoring as needed.
Change-Id: Ifa9ce978822f365996a509edeb3023001a07be84
TICKET: CYNGNOS-2233
(cherry picked from commit 6baab03bd8)
Since the restore process (or any external setup wizard
process) can take a long time to finish execution, save
the current page and restore it on recreation when necessary.
Change-Id: I575cf58047eb307c95408a0955dd7e5b50a62107
TICKET: CYNGNOS-2233
(cherry picked from commit 57080c360c)
Googles SetupWizard expects a specific flow for the restoration
process -- amend the intent for gms restore to abide.
Change-Id: Idf4c3b813676c5456770627067a42697ab756bb0
TICKET: CYNGNOS-2233
(cherry picked from commit 744827989c)
Since Marshmallow broke the ability to utilize complex
matrix queries against the SettingsProvider because it
is now backed by XML, rewrite the logic for the backup
enabled flag to work within the new constraints.
Change-Id: I8ad993564184fa14b5a3267689c69af2f7e8638e
TICKET: CYNGNOS-2233
(cherry picked from commit 0d83f7c062)
