1084531 - SIM Manager periodically not showing Outgoing Calls/Messages Status

Status: RESOLVED WORKSFORME

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

Description

[Marcia Knous [:marcia]]

Attachment: 2014-10-17-10-56-16.png

Flame, after OTA to:

Gaia   abef62c0623e5504a97b4fd411e879a67b285b52
SourceStamp ae1dfa192faf
BuildID 20141017040208
Version 36.0a1
v. 184

STR:
1. After an OTA, open Settings | SIM Manager

Expected: I would see the SIM settings I previously had set
Actual: Dropdowns are blank

Screenshot attached.

During this testing session the phone had crashed several times as a result of another bug, Bug 1083965

Comment 1

[Tony Chung [:tchung]]

EJ ,arthur, any ideas?

Comment 2

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

No sure what's wrong in this scenario.

@Marcia, can you help me check mozSettings about these mozSettings "ril.telephony.defaultServiceId", "ril.sms.defaultServiceId", "ril.data.defaultServiceId" ?

I am curious about the value of these values.

Comment 3

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

(In reply to EJ Chen [:eragonj][:小龍哥][ni? if you need me] from comment #2)
> No sure what's wrong in this scenario.
> 
> @Marcia, can you help me check mozSettings about these mozSettings
> "ril.telephony.defaultServiceId", "ril.sms.defaultServiceId",
> "ril.data.defaultServiceId" ?
> 
> I am curious about the value of these values.
                                        ~~~~~~
                                 typo : mozSettings keys

Comment 4

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

From engineering perspective, especially from Sim Manager, I can't see any part of code would do the data migration here.

And also, I tried to reproduce this problem after OTA on my phone but can't reproduce it.

I think we may need QA's help for this.

== Device info ==

Gaia-Rev        13973ab50760d1e8bb773082163f0dff19d35a44
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-aurora/rev/6e317e075d04
Build-ID        20140928160204
Version         34.0a2
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141016.194928
FW-Date         Thu Oct 16 19:49:39 EDT 2014
Bootloader      L1TC10011800

Comment 5

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

Tony, it seems this bug got forgotten by QA and reporter, are we going to fix this or not ?

If not, I want to close this bug directly.

thanks.

Comment 6

[Tony Chung [:tchung]]

(In reply to EJ Chen [:eragonj][:小龍哥][ni? if you need me] from comment #2)
> No sure what's wrong in this scenario.
> 
> @Marcia, can you help me check mozSettings about these mozSettings
> "ril.telephony.defaultServiceId", "ril.sms.defaultServiceId",
> "ril.data.defaultServiceId" ?
> 
> I am curious about the value of these values.

passing this qawanted request to see if it can be reproduced again. Please apply the logging values from this comment.

Comment 7

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

I was unable to reproduce this issue after three updates to the latest 2.1 and 2.2 Flame KK builds.

From Environmental Variables:
Device: Flame 2.1
BuildID: 20141015001201
Gaia: 379ea4c9dd6d3f8ca2f79ce59c15f6afe6e557c3
Gecko: 4853208cb48a
Version: 34.0 (2.1) 
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

To Environmental Variables:
Device: Flame 2.1
BuildID: 20141104001202
Gaia: 8b0cf889ae0d48a9eb7ecdcb9b67590de45cc5e5
Gecko: 388b03efe92d
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


From Environmental Variables:
Device: Flame 2.2
BuildID: 20141016040204
Gaia: 841d0d7d1b879f0ff4b5a8727f5dd23c7b0000a9
Gecko: a280a03c9f3c
Version: 36.0a1 (2.2) 
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

To Environmental Variables:
Device: Flame 2.2
BuildID: 20141104040207
Gaia: 3c50520982560ccba301474d1ac43706138fc851
Gecko: 54d05732f29b
Version: 36.0a1 (2.2) 
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Comment 8

[Joshua Mitchell (Inactive)]

(In reply to EJ Chen [:eragonj][:小龍哥][ni? if you need me] from comment #5)
> Tony, it seems this bug got forgotten by QA and reporter, are we going to
> fix this or not ?
> 
> If not, I want to close this bug directly.
> 
> thanks.

Hi EJ - the QAWanted tag was in the whiteboard instead of the keywords where it goes so this did not show up in our queues - We were not able to repro but there is still a NI on the reporter, perhaps they will have better luck?

Comment 9

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

(In reply to Joshua Mitchell [:Joshua_M] from comment #8)
> (In reply to EJ Chen [:eragonj][:小龍哥][ni? if you need me] from comment #5)
> > Tony, it seems this bug got forgotten by QA and reporter, are we going to
> > fix this or not ?
> > 
> > If not, I want to close this bug directly.
> > 
> > thanks.
> 
> Hi EJ - the QAWanted tag was in the whiteboard instead of the keywords where

Ahh, it seems the reporter set the QAWanted at the wrong place to make this confusion hmmm.

> it goes so this did not show up in our queues - We were not able to repro
> but there is still a NI on the reporter, perhaps they will have better luck?

Not sure, I set the ni? on the reporter one week ago but there is no any response yet. I'll wait till the end of this week, if there is still no response, based on our current observations, I would mark this bug as invalid.

Thanks !

Comment 10

[Marcia Knous [:marcia]]

I haven't yet been able to reproduce this in current builds. Closing as WFM For now.

Comment 11

[EJ Chen [:eragonj][:小龍哥][Contributor mode on](inactive)]

Thanks all !