We can proceed to the data enablement screen as soon as the device
confirms the requested slot is active. Waiting for an actual data
connection kinda breaks the point of that screen :)
Addresses CYNGNOS-660 and CRACKLING-503
Change-Id: I975508852b37c0e4b112612ac10aacb71ded97b3
Invalid sims and bad connections causes huge delays when switching. This disallows switching to invalid sims. It also fixes a bug were the next button would get enabled while waiting on a switch.
CRACKLING-503
Change-Id: I6cf7391910cc23554bb418c3083e736a3f06e037
(cherry picked from commit 4ef509ac48)
When changing the default data sim for msim, disable the next action until the operation completes.
This PS also refactors how the wait for radio logic a bit.
CRACKLING-503
Change-Id: I38ba3ea00f63d3e42c260e5b0e8558c3bc9d347f
(cherry picked from commit 62db452188)
Introduced in Ia1a81c4443cfd5bc3c3e5fd84758ff0ba2a2a140, this causes
an NPE in some situations.
Change-Id: I13239eb92b69087fe2c91b46482ff76748ab1c19
Ticket: CYNGNOS-707
(cherry picked from commit 4ea986255f)
* Always pass ALLOW_SKIP to GMS, it's smart enough to know when it
can't be applied.
* Don't bring up the authentication screen if no-network and canSkip
Still CYNGNOS-707
Change-Id: Ia1a81c4443cfd5bc3c3e5fd84758ff0ba2a2a140
(cherry picked from commit 649a5ec162)
System property ro.com.android.mobiledata is no longer used
issue-id: JALEBI-135
Change-Id: Iac088d50dc50227e805b58b537c38082b6797291
(cherry picked from commit c92c4b6a3a)
Fingerprint setup should occur after the user has setup any accounts
and before the customization page.
Change-Id: I1305d89e17da1f8d405c8bd5b8b8b5268a2ba38c
(cherry picked from commit 6d93813829)
Ticket: SAMBAR-189
See also
frameworks/base
libhardware
Settings
Enroll fingerprint via SetupWizard [2/2]
Squashed-Id: Ieabfb0f3b789b02ddd1e17aba1eadfda52b21384
Change-Id: I456b54e4946dba9448757d9fa75e13e9b8fa1270
We were incorrectly passing the phone ID to TelephonyManager instead of
the subscription ID. Pass the correct identifier to retrieve the network
operator name.
Change-Id: I266d2ce39c72db6e97eff5a36c5fec6242d516cc
(cherry picked from commit b31cb54361)
Telephony throws this exception in some cases when retrieving SIM state
Change-Id: I87e14aaa328d46ebba4990559f6531de4e961d68
(cherry picked from commit b72e820a96)
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
Fugu has both com.android.settings and com.android.tv.settings so
currently it brings up a selector dialog for how to handle the wifi
intent, which leads to "Activity is launching as a new task, so
cancelling activity result." Fix this by passing the component name
in the intent if FEATURE_LEANBACK is present
Change-Id: I470590315d3f95a32b7796dd4a916a543392fcd6
SubscriptionController exists in the telephony process and cannot
be accessed by SetupWizard.
getInstance() will always return null.
Change-Id: I017682d3aad539e1954348664b1c1fec7f76009d
