Closed
Bug 1035823
Opened 10 years ago
Closed 10 years ago
[DSDS] The SIM manager page is not refreshed if configuration changes
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:2.0+, b2g-v1.4 fixed, b2g-v2.0 verified, b2g-v2.1 verified)
People
(Reporter: julienw, Assigned: eragonj)
Details
(Whiteboard: [p=1])
Attachments
(3 files)
STR:
Prerequisite: have a DSDS phone with enough RAM (Dolphin works fine, not Tarako) and with 2 SIMs: SIM1 and SIM2
1. open the Settings app
2. open SIM Manager
3. set all configuration to SIM1
4. from another device, send a MMS to SIM2
5. from DuT, wait MMS arrives, tap the notification
6. tap "download"
7. tap "OK" when the dialog asks to change the SIM
8. press home, open Settings again
=> it should not have been killed, so the same panel is opened
Expected:
* we should see "SIM2" for the "data" configuration
Actual
* we see that the panel still reads SIM1 in the "data" section
Requesting 2.0? blocker status. It's not really a regression (the issue was probably here in 1.3t already) but it was not an issue on Tarako because the memory pressure would kill the settings app. This is now an issue with devices that have more RAM.
Moreover it should be really easy to fix.
Comment 1•10 years ago
|
||
Julien, can you please help to understand if you are able to reproduce this on flame and dolphin ? and also what is the build id you are using ?
Updated•10 years ago
|
Flags: needinfo?(felash)
Reporter | ||
Comment 2•10 years ago
|
||
I was using Dolphin, but I flashed it with a v1.4 build since then so I don't have the previous buildid anymore.
Haven't tried on Flame but I'm confident the issue is there too.
IMO it should block whatever release will be used on a DSDS phone with at least 256MB of RAM. Maybe request qawanted if you want to test on different devices and branches?
Flags: needinfo?(felash)
Updated•10 years ago
|
Assignee: nobody → ejchen
blocking-b2g: 2.0? → 2.0+
Whiteboard: [p=1]
Target Milestone: --- → 2.0 S6 (18july)
Assignee | ||
Comment 3•10 years ago
|
||
Arthur I just made the patch for this bug, please give it a try when you have time ! Thanks.
Attachment #8455154 -
Flags: review?(arthur.chen)
Comment 4•10 years ago
|
||
Comment on attachment 8455154 [details] [review]
patch on master
Thanks for proposing the patch so quickly. Please check my comments in github, thanks.
Attachment #8455154 -
Flags: review?(arthur.chen)
Assignee | ||
Comment 5•10 years ago
|
||
Comment on attachment 8455154 [details] [review]
patch on master
Arthur, just addressed all your comments, please give a check ! Thanks :)
Attachment #8455154 -
Flags: review?(arthur.chen)
Comment 6•10 years ago
|
||
Comment on attachment 8455154 [details] [review]
patch on master
r=me, thank you!
Attachment #8455154 -
Flags: review?(arthur.chen) → review+
Assignee | ||
Comment 7•10 years ago
|
||
Merged into
Gaia/master : e411b11f085cb895e6a5cf3b494fba236e65ee48
Gaia/v2.0 : b0ef6563d8dbd29f49bc11f8a7960e0e78e50637
Thanks all.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v2.0:
--- → fixed
status-b2g-v2.1:
--- → fixed
Comment 9•10 years ago
|
||
Hi EJ,
Can you see if this fix is suitable for 1.4 and required? if so please send a 1.4?approval to :preeti
Thank you,
Wayne
blocking-b2g: 1.4? → 2.0+
Flags: needinfo?(ejchen)
Comment 10•10 years ago
|
||
I recommend we include for 1.4 as well since data settings on SIM may lead to customer care calls if not correctly reflected.
Assignee | ||
Comment 11•10 years ago
|
||
I think this patch is ok for 1.4 and not risky, so let me ask for approval.
Flags: needinfo?(ejchen)
Assignee | ||
Comment 12•10 years ago
|
||
Comment on attachment 8455154 [details] [review]
patch on master
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: users may get confused if they changed defaultId to receive mms while settings app was open, the UI would not be consistent with real situation.
[Testing completed]: yes
[Risk to taking this patch] (and alternatives if risky): low because this happens rarely.
[String changes made]: no
Attachment #8455154 -
Flags: approval-gaia-v1.4?
Updated•10 years ago
|
Attachment #8455154 -
Flags: approval-gaia-v1.4? → approval-gaia-v1.4+
Comment 13•10 years ago
|
||
status-b2g-v1.4:
--- → fixed
I had to revert this from 1.4 for Gu test failures: https://tbpl.mozilla.org/php/getParsedLog.php?id=46308580&tree=Mozilla-B2g30-v1.4
https://github.com/mozilla-b2g/gaia/commit/c63ba42425986371adf3eff74744c0e017734456
Flags: needinfo?(ejchen)
Assignee | ||
Comment 15•10 years ago
|
||
This is the same patch taken from merged patch in master and fixed a test bug.
Assignee | ||
Comment 16•10 years ago
|
||
Everything looks nice and merged into Gaia/v1.4 : https://github.com/mozilla-b2g/gaia/commit/14cb1ccc34ea99bf191c0b04d1531556d26a3a12
Flags: needinfo?(ejchen)
Comment 17•10 years ago
|
||
This issue has been verified successfully on Flame 2.0 and 2.1
See attachment: Verify_1035823.MP4
Reproducing rate: 0/3
Flame 2.0 build:
Gaia-Rev 8d1e868864c8a8f1e037685f0656d1da70d08c06
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/29222e215db8
Build-ID 20141203000201
Version 32.0
Flame 2.1 build:
Gaia-Rev dbaf3e31c9ba9c3436e074381744f2971e15c7bf
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ebce587d2194
Build-ID 20141203001205
Version 34.0
Updated•10 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•