Closed Bug 926350 Opened 11 years ago Closed 11 years ago

[B2G][User Story] [DSDS] Call configurations

Categories

(Firefox OS Graveyard :: RIL, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: khu, Unassigned)

References

()

Details

(Keywords: feature, Whiteboard: [ucid:DSDS5a, 1.3:p1, ft:RIL] [L2])

As a user, I should be able to specify call forwarding, call barring, and call waiting in settings.
blocking-b2g: --- → 1.3+
Depends on: 926169
We(Enpei, Carrie, Hsinyi, ...) made some testings on other DSDS reference phones, and found that other phones allow users to configure these settings on both SIMs.
The current user story, quite different from reference phone [1], is:
"As a user, I should be able to specify call settings & SIM security (list: refer to existing v1.2 call setting list), for both the primary (active) subscription."

As comment 1 said, if two SIMs are *standby*, then it should be feasible for user to specify a card call settings go for. It's the design of the reference phone. Of course, we should wait for the setting result for one sim card coming back from network before setting the other card.

But if one SIM is in-call (in this case, I say the SIM is the *active* one), then I could imagine that there are technical difficulties for allowing 'non-active' SIM in settings due to vendor's DSDS solution. It's also the design of the reference phone [1]. 

So, the user story DSDS5a makes sense to me if it becomes:
"As a user, I should be able to specify call forwarding, call barring, and call waiting for both SIMs while they both are standby. While a SIM is in use, i.e. active, I could set only that active one."

However, the other question came to my mind: how could we know which sim card the modem is occupied by? For example, if user is talking to a call incoming from SIM1, could we have any indication from modem that SIM1 is active so that SIM2 should be disabled for settings or other activities for a while? 

Anshul, I need your input for checking technical issues here. Thank you.

[1] Quote from Enpei in another discussion thread:
[Enpei] We checked on reference phone, user can configure each SIM while both SIMs are active. Only when one is on call that user will not be able to setup call settings.
Flags: needinfo?(anshulj)
> As comment 1 said, if two SIMs are *standby*, then it should be feasible for
> user to specify a card call settings go for. It's the design of the
> reference phone. Of course, we should wait for the setting result for one
> sim card coming back from network before setting the other card.

If Anshul confirms from the modem perspective, I am okay here. 
 
> However, the other question came to my mind: how could we know which sim
> card the modem is occupied by? For example, if user is talking to a call
> incoming from SIM1, could we have any indication from modem that SIM1 is
> active so that SIM2 should be disabled for settings or other activities for
> a while? 

Will let Anshul to confirm if there is an RIL API to use to check this.
(In reply to Sandip Kamat from comment #3)
> > As comment 1 said, if two SIMs are *standby*, then it should be feasible for
> > user to specify a card call settings go for. It's the design of the
> > reference phone. Of course, we should wait for the setting result for one
> > sim card coming back from network before setting the other card.
> 
> If Anshul confirms from the modem perspective, I am okay here. 
Sandip what kind of confirmation are you looking from me here? As Hsin-Yi mentioned, if modem is on call with 1 SIM the modem won't be able to reach the network for the other SIM and therefore can not update the network settings such as call forwarding, call waiting and so on.

>  
> > However, the other question came to my mind: how could we know which sim
> > card the modem is occupied by? For example, if user is talking to a call
> > incoming from SIM1, could we have any indication from modem that SIM1 is
> > active so that SIM2 should be disabled for settings or other activities for
> > a while? 
> 
> Will let Anshul to confirm if there is an RIL API to use to check this.
Modem doesn't provide such information and it doesn't need to. Dialer can query respective telephony/call objects to find out which one is in service and therefore know the subscription information.
Flags: needinfo?(anshulj)
Update acceptance criteria from PM:
1) User should have a way to specify call settings list: (refer to existing v1.2 call setting list), for boths SIMs whey they are in standby. 

2) User should have a way to specify SIM Security settings list: (refer to existing v1.2 SIM security settings list), for both the SIMs. 

3) While a SIM is in use, i.e. active, user can't access these menus.

4) This menu could be under calling options which in turn bring the UI back to select the SIM subscription first and then do applicable settings for that service. (upto UX guidance)
Updating the latest user story for DSDS5a:

"As a user, I should be able to specify call settings & SIM security (list: refer to existing v1.2 call setting list), for the both SIMs while they are in standby. While a SIM is in use, i.e. active, user can't access these menus."
Depends on: 928295
Whiteboard: [ucid:DSDS5a, FT:RIL, 1.3:p1] → [ucid:DSDS5a, FT:RIL, 1.3:p1] [L2]
update moztrap URL.
Blocks: 928294
Remove blocking-b2g flag from User Story bugs. Use whiteboard to indicate what FxOS version we target.
blocking-b2g: 1.3+ → ---
Whiteboard: [ucid:DSDS5a, FT:RIL, 1.3:p1] [L2] → [ucid:DSDS5a, FT:RIL, 1.3:p2] [L2]
Keywords: feature
Whiteboard: [ucid:DSDS5a, FT:RIL, 1.3:p2] [L2] → [ucid:DSDS5a, FT:RIL, 1.3:p1] [L2]
Blocks: b2g-dsds-1.4
No longer blocks: b2g-dsds-1.4
Update whiteboard tag to follow format [ucid:{id}, {release}:p{1,2}, ft:{team-id}]
Whiteboard: [ucid:DSDS5a, FT:RIL, 1.3:p1] [L2] → [ucid:DSDS5a, 1.3:p1, ft:RIL] [L2]
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Bug 959986 breaks AC3, link bug to this user story and keep status in resolved fixed until 959986 being fixed.

Verified on Fugu
Gaia      726ae682da9022bdccc057f29e836eff6a738677
Gecko     6ea72307375cfa123d2ec81f29ccc86976134b2a
BuildID   20140120153149
Version   28.0a2
Depends on: 959986
Verified on Fugu.
Fugu
Gaia      77fdf058ccb77f40497fb696912a1ce12192eea7
Gecko     9c7f92ffaa19db4a004103104d2da78b8cbd2056
BuildID   20140129130749
Version   28.0a2
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.