1078915 - [Flame] SIM Manager shows "searching" when in First Run

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::First Time Experience, defect)

Description

[Marcia Knous [:marcia]]

Attachment: Screenshot of issue during first run

Flame, while running:

Gaia   470826d13ae130a5c3d572d1029e595105485fb0
SourceStamp e0d714f43edc
BuildID 20141006040204
Version 35.0a1
base: vv180

STR:
1. Start the first run process with 2 SIMS, one which isn't functioning
2. Observe the attached screenshot

Expected: It would say no operator like it does later when I finish the First Run

Comment 1

[Marcia Knous [:marcia]]

Attachment: Screenshot after First Run in Settings

Comment 2

[Doug Sherk (:drs) (inactive)]

I think this is either a system or RIL issue, and I tend toward system.

Comment 3

[Anthony Ricaud (:rik)]

It could also be a FTU issue where they use the wrong string or not listen to the good states.

Comment 4

[Michael Henretty [:mikehenrty][:mhenretty]]

Heh, yeah this was done on purpose in bug 958041, since we showed "No operator" even in the case where a working SIM hadn't connected yet. The problem is that we don't distinguish between a non-working SIM and a SIM that hasn't connected yet.

Comment 5

[Doug Sherk (:drs) (inactive)]

(In reply to Michael Henretty [:mhenretty] from comment #4)
> Heh, yeah this was done on purpose in bug 958041, since we showed "No
> operator" even in the case where a working SIM hadn't connected yet. The
> problem is that we don't distinguish between a non-working SIM and a SIM
> that hasn't connected yet.

Should we resolve this then?

Comment 6

[Michael Henretty [:mikehenrty][:mhenretty]]

No, this is still bad UX and I imagine we can do better. It's not a high priority though.

Comment 7

[BMO Automation]

Firefox OS is not being worked on