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
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
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
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
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
SubscriptionController exists in the telephony process and cannot
be accessed by SetupWizard.
getInstance() will always return null.
Change-Id: I017682d3aad539e1954348664b1c1fec7f76009d
Context is assumed to be SetupWizardActivity and blindly cast. Just make the Context reference a SetupWizardActivity.
Change-Id: I3d7ffd08980fbff0fbea51b45b28002b49813038