Closed Bug 934404 Opened 12 years ago Closed 12 years ago

[DSDS][STK] STK menu and events management

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 951586
1.4 S3 (14mar)

People

(Reporter: noemi, Assigned: frsela)

References

Details

(Keywords: feature, Whiteboard: [ucid:, 1.4, ft:comms][L2])

Attachments

(2 files)

As I user, I should be able to manage STK menu and events from each SIM *I am able to access to STK menu from each SIM once SIM card is available (unblocked card) *The STK menu will be simultaneously available for both SIMs from settings *I am able to send STK events from STK menu (once SIM card/s is/are available) *I am able to receive STK events from each SIM (once SIM card/s is/are available) **In case of STK events coming from both SIMs simultaneously, they will be managed following a FIFO (First In First Out) approach *I am able to specifically differentiate between SIMs when accessing to STK menu from settings or receiving STK events (UX input needed here)
Blocks: b2g-dsds-1.3
blocking-b2g: --- → 1.3?
Sandip, here is a new user story request to v1.3. Can you help to make a decision? Thanks.
Flags: needinfo?(skamat)
blocking-b2g: 1.3? → 1.4?
Hi, WebIccManager api is going to change in master in the following days, hopefully tomorrow, so we need to work at least for guaranteeing STK single SIM card scenario for v1.3, notice that it will be broken once the new api lands (we need to adapt to the new interface)
Hi Noemi, Can this wait till 1.4? Trying to reduce the risks for 1.3 delivery. ALso if we need to make it flag-based for dsds devices vs single sim.
Flags: needinfo?(skamat)
(In reply to Sandip Kamat from comment #3) > Hi Noemi, Can this wait till 1.4? Trying to reduce the risks for 1.3 > delivery. ALso if we need to make it flag-based for dsds devices vs single > sim. As far as we know, the old api and the new one are not going to coexist in parallel (new api is not backwards compatible), just the new api will be available so there is no alternative, at least, we need to work on modifying the interface to avoid breaking single SIM card scenario.
Whiteboard: [L2]
Remove blocking-b2g flag from User Story bugs. Use whiteboard to indicate what FxOS version we target.
blocking-b2g: 1.4? → ---
Keywords: feature
Blocks: b2g-dsds-1.4
No longer blocks: b2g-dsds-1.4
It should be the 1.4 feature.
Blocks: 938433
No longer blocks: b2g-dsds-1.3
Blocks: b2g-dsds-1.4
No longer blocks: 938433
Blocks: 947220
blocking-b2g: --- → 1.4?
blocking-b2g: 1.4? → 1.4+
Depends on: 942096, 946165
Hi Wilfred, is this in 1.4 DSDS? if so, this isn't in the Google doc excel DSDS Sheet. Can you confirm? Thanks
Flags: needinfo?(wmathanaraj)
Summary: [B2G][DSDS][User Story] STK menu and events management → [DSDS][STK] STK menu and events management
this blocks 947220 - which is in the google doc - this is a bug the dev team is working on.
Flags: needinfo?(wmathanaraj)
Joe, Can we work on this bug for 1.3? QC seems to need it in 1.3.
Flags: needinfo?(jcheng)
Preeti - we discussed this and agreed this will be implemented in v1.4. Sandip was going through the v1.3 CS bug and working on ensuring the bugs are moved. If this has not happened by tomorrow I would suggest we move this to v1.4.
Blocks: 951586
Blocks: 951595
Blocks: 951599
No longer blocks: 951599
No longer blocks: 951586
No longer blocks: 951595
Depends on: 951595
Depends on: 951586
Flags: needinfo?(jcheng)
Assignee: nobody → nhsieh
I guess these features are all in operator's design. So for FFOS we already provided DSDS guideline for this.
Michael Please add this is a dependency blocking 1.4 QC CS meta bug.
Flags: needinfo?(mvines)
ftfy
Flags: needinfo?(mvines)
Depends on: 951599
No longer depends on: 955599
Attached file [DSDS] STK_14-0121.pdf —
Assignee: nhsieh → nobody
features should not block release, remove blocking flag
blocking-b2g: 1.4+ → ---
Whiteboard: [L2] → [ucid:, 1.4, ft:comms][L2]
Flags: in-moztrap?(atsai)
QA Contact: atsai
Flags: in-moztrap?(atsai) → in-moztrap?(echang)
Flags: in-moztrap?(echang) → in-moztrap+
QA Contact: atsai → echang
Target Milestone: --- → 1.4 S3 (14mar)
Assignee: nobody → frsela
Implemented in bugs 951599 and 951586
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: