Closed Bug 836257 Opened 12 years ago Closed 12 years ago

Be aware of GECKO_CARDSTATE_UNKNOWN new card state in Gaia apps.

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:tef+, b2g18+ fixed, b2g18-v1.0.1 fixed)

RESOLVED FIXED
blocking-b2g tef+
Tracking Status
b2g18 + fixed
b2g18-v1.0.1 --- fixed

People

(Reporter: jaoo, Assigned: jaoo)

References

Details

(Keywords: late-l10n)

Attachments

(1 file)

This is a follow-up bug of bug 822522. Since a new card state has been added to the possible ones we need to be sure that all apps that listen for `cardstatechange` event ( or where we switch/case the values of `mozMobileConnection.cardState` property) handle the SIM card states properly after landing bug 822522.
Depends on: 822522
bug 822522 is tracking+ so nominating tracking-b2g18.
tracking-b2g18: --- → ?
Once this is done we should figure out something about bug 827741 also.
Blocks: 827741
Depends on: 837755
No longer depends on: 822522
Assignee: nobody → josea.olivera
No longer depends on: 837755
Depends on: 837755
:jaoo you have not requested a review. I can review the Contacts settings part and I think FCampo the FTU part.
Flags: needinfo?(josea.olivera)
(In reply to Jose M. Cantera from comment #4) > :jaoo you have not requested a review. I can review the Contacts settings > part and I think FCampo the FTU part. Yep, I still need to figure out how the dialer app gets affected for the new SIM card states specially why it's not dealing with all different card states here [1]. I'll request review at some of you guys once I get that done. Thx! [1] https://github.com/mozilla-b2g/gaia/blob/master/apps/communications/dialer/js/telephony_helper.js#L42-L47
Flags: needinfo?(josea.olivera)
Comment on attachment 715464 [details] Pointer to Github PR: https://github.com/mozilla-b2g/gaia/pull/8186 The logic for notifying ICC card status changes to content (bug 837755) has been updated a bit and a new state (`unknown`: transition between states) has been added. This PR is about reviewing (follow-up) the bits in Gaia where we check the ICC card status. Until we get r+ here bug 837755 should not land.
Attachment #715464 - Flags: review?(jmcf)
Attachment #715464 - Flags: review?(fernando.campo)
Attachment #715464 - Flags: review?(etienne)
Attachment #715464 - Flags: review?(21)
Comment on attachment 715464 [details] Pointer to Github PR: https://github.com/mozilla-b2g/gaia/pull/8186 r=me for the dialer changes
Attachment #715464 - Flags: review?(etienne) → review+
Comment on attachment 715464 [details] Pointer to Github PR: https://github.com/mozilla-b2g/gaia/pull/8186 I feel like others review will be enough but I would like to understand the logic changes.
Attachment #715464 - Flags: review?(21)
I checked the Contacts part and the FTU part and it was working ok. However I made a comment about a weird block of code in the settings part.
Comment on attachment 715464 [details] Pointer to Github PR: https://github.com/mozilla-b2g/gaia/pull/8186 ok for the FTU part. thanks Jaoo :)
Attachment #715464 - Flags: review?(fernando.campo) → review+
Comment on attachment 715464 [details] Pointer to Github PR: https://github.com/mozilla-b2g/gaia/pull/8186 with the nits typo addressed r+.
Attachment #715464 - Flags: review?(jmcf) → review+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment on attachment 715464 [details] Pointer to Github PR: https://github.com/mozilla-b2g/gaia/pull/8186 NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): User impact if declined: ICC card state is being reported as 'absent' when airplane mode is on. Testing completed: Yes. Risk to taking this patch (and alternatives if risky): Low IMHO. String or UUID changes made by this patch: Yes.
Attachment #715464 - Flags: approval-gaia-v1?
This is the remaining work to fix bug 830287, that is already merged in v1-train. Well, there is no dependency between both of them, as no extra work is need in bug 830287, but this bug should be fixed to have the problem described in bug 830287 totally fixed. Sorry, maybe it sounds like a tongue twister, but I could not find a better explanation. :-)
Attachment #715464 - Flags: approval-gaia-v1? → approval-gaia-v1+
To uplift this bug to v1-train we also need bug 837755 to be a+, as it is the gecko part of the bug fixing and marked as a dependency.
Please, don't uplift this until bugs 848765 and 837755 land on b2g18.
Depends on: 848765
(In reply to José Antonio Olivera Ortega [:jaoo] from comment #16) > Please, don't uplift this until bugs 848765 and 837755 land on b2g18. Sorry I meant bugs 822522 and 837755.
Depends on: 822522
No longer depends on: 848765
822522 is still not landed on b2g18, waiting for it land there.
Uplifted commit c76e97d635f9a6205a9a3933a79e90e27b25f4c9 as: v1-train: 2a5ddb6758272227c1877b45984e053989189e36
(In reply to John Ford [:jhford] from comment #19) > Uplifted commit c76e97d635f9a6205a9a3933a79e90e27b25f4c9 as: > v1-train: 2a5ddb6758272227c1877b45984e053989189e36 This patch has been uplifted without doing the same with its gecko counterpart. I'll request checkin-needed for those bugs.
Blocks: 828996
Asking for tef+ flag. See bug 822522 comment #30
blocking-b2g: --- → tef?
blocking-b2g: tef? → tef+
Uplifting 2a5ddb6758272227c1877b45984e053989189e36 results in a merge conflict. It looks like it's mainly a conflict in cleanup that didn't land to 1.0.1
(In reply to John Ford [:jhford] -- If you expect a reply from me, use needsinfo? instead of CC from comment #22) > Uplifting 2a5ddb6758272227c1877b45984e053989189e36 results in a merge > conflict. It looks like it's mainly a conflict in cleanup that didn't land > to 1.0.1 Thanks for trying the uplifting John, do you need a patch that applies cleanly in 1.0.1 gaia branch?
Flags: needinfo?(jhford)
jaoo, you can simply try to uplift and push yourself, but if you're not comfortable, just push your commit to a branch in your repository and John or I would apply it.
Flags: needinfo?(jhford) → needinfo?
Flags: needinfo?
Can you please provide steps to verify this fix - as we will blackbox test from the UI?
Flags: needinfo?
Can you please provide steps to verify this fix - as we can perform blackbox testing from the UI?
Flags: needinfo?
Flags: needinfo?
Check that "unknown state" appears in the lockscreen when the phone just started.
Flags: needinfo?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: