986232 - [tarako] SIM Manager/Cellular & Data Settings show incorrect SIM cards if one is switched

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Dialer, defect)

Description

[John Hammink]

Tarako v1.3t build
--------------------------------------------------------------------
Build ID: 20140313135844
Gecko: d400d3a715c7c90291596b32412be56f46f2293e
Gaia: 7329446974f0ea3b14d61bd38f205eb17a5ce62d


Steps to reproduce
--------------------------------------------------------------------
1. Flash the device with no SIM cards.
2. Place an AT&T and T-Mobile SIM inside and restart the device
3. Observe which SIM cards are shown on each of Home Screen, and in Settings => SIM Manager and Cellular & Data Settings (Note:  Showed SIM 1: At&T SIM 2: T-Mobile)
4. Now power down the phone and switch one of the SIM cards (I used emome: Taiwan)
5. After powering up, and entering SIM PIN: recheck SIM listings in all the places in Step 3:

Actual Result:
SIM 1: At&T SIM 2: T-Mobile

Expected Result:
SIM 1: emome (and something in Chinese) SIM 2: T-Mobile

Frequency: 2/2

Comment 1

[John Hammink]

On further investigation, all my hamachi's on each branch are showing my Emome SIM Card as AT&T:

1.4
Gaia      53edbf08b0a750c31e8c6b2c20f2b1315b1412d1
Gecko     https://hg.mozilla.org/releases/mozilla-aurora/rev/9b482d6994fd
BuildID   20140320000349
Version   30.0a2
ro.build.version.incremental=eng.tclxa.20131223.163538
ro.build.date=Mon Dec 23 16:36:04 CST 2013

and 1.3:
Gaia      4982b2680645e1506d72159ae73b04b14718ee6b
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/155d55074aaa
BuildID   20140319164001
Version   28.0
ro.build.version.incremental=eng.tclxa.20131223.163538
ro.build.date=Mon Dec 23 16:36:04 CST 2013

I am not myself sure when we are destined to ship in Taiwan.  Nonetheless, I'm nomming this for 1.4.

Comment 2

[Joe Cheng [:jcheng] (please needinfo)]

hi Shawn, do you mind taking a look at this? is this a tarako specific issue? thanks

Comment 3

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

My guess is that since the US doesn't have an Emome network, the SIM is defaulting to a network that Emome is partnered with... which is most likely AT&T.

Comment 4

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I still have a valid My Call SIM card from the Oslo work week and it's registering as AT&T.
I believe that comment 3 is correct.

Comment 5

[bhavana bajaj [:bajaj]]

Shawn, please renom this if you think this is a real issue and not due to a network discrepancy . In parallel we should also check the Taipei QA folks to check this bug with valid SIM's and network. NI Brain to get help on that.

Comment 6

[Brian Huang [:brianhuang][:brhuang]]

Mike, please check this. thanks.

Comment 7

[shawn ku [:sku]]

Hi John:
 Could you please try below command to get log, and attach it to bugzilla?

// With AT&T sim at slot 1. And T-Mobile at slot 2.
adb logcat -b radio -b main -v threadtime > /tmp/986232_1.log

// With AT&T sim at slot 2. And T-Mobile at slot 1.
adb logcat -b radio -b main -v threadtime > /tmp/986232_2.log

Please start it from boot-up, and stop logging when you see issue symptom.
I can check it if partner issue or not after seeing it on bugzilla.

Thank!!

Comment 8

[Mike Lien[:mlien]]

I verify with FET, TCC, and CHT on the latest build and it's all fine even switch the slots

Build Info:
Gaia      8132b88334f61288060a2680857c54c7af82cdc5
Gecko     57625761da9e5c35d1ddd516221ce274a3575d15
BuildID   20140324121117
Version   28.0

Comment 9

[John Hammink]

(In reply to shawn ku [:sku] from comment #7)
> Hi John:
>  Could you please try below command to get log, and attach it to bugzilla?
> 
> // With AT&T sim at slot 1. And T-Mobile at slot 2.
> adb logcat -b radio -b main -v threadtime > /tmp/986232_1.log
> 
> // With AT&T sim at slot 2. And T-Mobile at slot 1.
> adb logcat -b radio -b main -v threadtime > /tmp/986232_2.log
> 
> Please start it from boot-up, and stop logging when you see issue symptom.
> I can check it if partner issue or not after seeing it on bugzilla.

I'm not sure what switching between AT&T and T-Mobile would actually prove, in this case.

Comment 3, I would argue is not correct, because switching out AT&T for emome gets me, on today's build:

SIM1 T-Mobile  - correct
SIM2 TMO (Roaming)  - also correct

Switching them around shows the reverse, as expected.

FWIW, I've attached two logs:

968232_2.log
SIM1 T-Mobile  - correct
SIM2 AT&T   - also correct

968232_what.log
SIM1 T-Mobile  - correct
SIM2 TMO (Roaming)  - also correct

Works for me?  I'm reluctant to close a bug that somehow magically fixed itself :-/

Comment 10

[John Hammink]

Attachment: 986232__what.log

Comment 11

[John Hammink]

Attachment: 986232_2.log

Comment 12

[John Hammink]

Apparently I was on a very old build:

Not working on:
Build ID: 20140313135844
Gecko: d400d3a715c7c90291596b32412be56f46f2293e
Gaia: 7329446974f0ea3b14d61bd38f205eb17a5ce62d

Working again on:
Gaia      8132b88334f61288060a2680857c54c7af82cdc5
Gecko     57625761da9e5c35d1ddd516221ce274a3575d15
BuildID   20140325060053
Version   28.0
ro.build.version.incremental=121
ro.build.date=Tue Mar 25 06:09:04 CST 2014

Comment 13

[Doug Sherk (:drs) (inactive)]

Based on comment 12.