931299 - [HOMESCREEN] Incorrect homescreen showing with Belgian SIM card roaming on AT&T network

Status: RESOLVED INVALID

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

Description

[John Hammink]

Device: Leo
Branch 1.2
Gaia:     b67568c07ccde602b43115efade3170234ac95a5
Gecko:    http://hg.mozilla.org/releases/mozilla-aurora/rev/5eabd267ef04
BuildID   20131025004000
Version   26.0a2


* Procedure:
1. Insert Belgian (base telcom) SIM Card.  Note that in roams in US on AT&T
2. Execute the command "MOZILLA_OFFICIAL=1 GAIA_DISTRIBUTION_DIR=../qa-testcase-data/customization/reference make production" to flash the device.
2. Complete the FTE.

* Expected result
For our ATT Configuration, default homescreen is the red screen.  variant.json points to ""wallpaper": "attus/attus_wallpaper.png" for AT&T networks, which this Base telecom card is roaming on.

* Actual result
Default homescreen is that as indicated if NO SIM card is inserted, in otherwords
"reference/wallpapers/default.png"

Comment 1

[Jason Smith [:jsmith]]

What's the MCC & MNC on that SIM card when it's roaming?

Comment 2

[Antonio Manuel Amaya Calvo (:amac)]

The MCC and MNC of the card usually don't change, except on some rare cases which I don't think apply here. And the configuration that's applied is linked to the SIM, not to the hosting network. That means the configuration that will be applied is the one assigned to the Belgian card, or the default one if there's no "Belgian card" configuration defined. 

In other words, the described behavior looks like the expected behavior.

Comment 3

[John Hammink]

When I was in IOT earlier this year, I saw the MCC and MNC change to reflect the roaming network (or else return blank values), so I'm a little surprised about that.

Jason I need your tool to check the MCC\MNC to be sure.

Comment 4

[John Hammink]

If the MCC|MNC is returning blank values, then I'm not surprised about this behavior either.

Comment 5

[Antonio Manuel Amaya Calvo (:amac)]

There are two MCC/MNC values. The network one, which should return the current network one, and the SIM one, which for all normal cases should return always the same value for a given SIM, independently if its roaming or not. The exception is that some SIMs, on some roaming networks, return a different MCC/MNC for peering agreement reasons. And that was a corner case that our product decided to ignore (the case being someone on country A buys a phone and then without activating it goes to country B which has a roaming agreement with country C but not country B and so the SIM when used in country B returns the MCC and MNC of a country C operator and not the correct one from country A). 

And the reason to ignore that case, besides being a very corner one, was that AFAIK there's no way to get the original MCC/MNC from the SIM on that cases.

Comment 6

[John Hammink]

Thanks for the explanation, Antonio!  This makes testing the feature a bit more complicated than I had originally suspected, because there are different scenarios to bear out.  CC'ing also AUS for clarification.

Comment 7

[Jason Smith [:jsmith]]

John - Can you check the MCC/MNC used for the target SIM you used to test this? That will determine if this bug is valid or not.

Comment 8

[John Hammink]

206 	20 	BASE 	KPN Group Belgium is what I'm getting.  

So apparently this is expected.