If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[SIMToolkit] MT call menu is not shown after finishing a received voice call

NEW
Unassigned

Status

Firefox OS
Gaia::System
P2
normal
5 years ago
4 years ago

People

(Reporter: isabelrios, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: IOT, Spain, Ikura)

Attachments

(1 attachment)

14.87 KB, application/octet-stream
Details
(Reporter)

Description

5 years ago
Created attachment 735118 [details]
log file

Bug filed during certification in Spain.
Device Ikura, Buildid "20130321070205"
gecko commit: b5183c99228bdc5be33340e359efd1b4f0859e92 
gaia commit: 577d13088ebdbd353d13910d3317e713a140415b

*This bug is not 100% reproducible but is easily seen*
PROCEDURE
1.- Put SIM Nº 11.
2.- From other phone, with a national number, make a voice call to the number of SIM Nº 11.
3.- Accept the voice call in ZTE Open. 
4.- Finish the voice call.
5.- The Smart Call menu is not displayed.

EXPECTED
If the “MT call” event is part of the list of events sent in the SET UP EVENT
LIST command, when the handset receives a SETUP message, it will inform the SIM
about what has happened, using the Envelope command (Event download - MT call).

The calling phone number must be shown with the international phone number and
national number, after to select the first item of the menu (Visualizar)

ACTUAL
Menu does not appear on the screen to test the application MT Call.
Please see log file attached
Probably is because the STK events are managed by settings so it's needed that settings should be open during the text.

I suggest to move this part of STK to system, but we should assure that this is the cause. ¿Could you repeat with settings app opened?
Flags: needinfo?(isabelrios)

Updated

5 years ago
Whiteboard: IOT, Spain, Ikura

Comment 2

4 years ago
Hi Isabel,

I just wanted to get a better understanding here, are you expecting an STK menu to be displayed after the "MT call" event? I'm looking through the logs and I don't see any STK proactive commands in there. It seems like you are expecting to see an STK menu once "MT call" event occurs but perhaps our interpretation of the issue here is incorrect..
(Reporter)

Comment 3

4 years ago
(In reply to Fernando R. Sela [:frsela] from comment #1)
> Probably is because the STK events are managed by settings so it's needed
> that settings should be open during the text.
> 
> I suggest to move this part of STK to system, but we should assure that this
> is the cause. ¿Could you repeat with settings app opened?

(In reply to Carol Yang from comment #2)
> Hi Isabel,
> 
> I just wanted to get a better understanding here, are you expecting an STK
> menu to be displayed after the "MT call" event? I'm looking through the logs
> and I don't see any STK proactive commands in there. It seems like you are
> expecting to see an STK menu once "MT call" event occurs but perhaps our
> interpretation of the issue here is incorrect..

Sorry, currently we do not have that SIM Card to test this again or to give a better explanation for the problem. We will ask the guys working on the certification to give more details so there is no misunderstanding about the correct expected.
Will update the bug when I have more info.
Thanks
Flags: needinfo?(isabelrios)
Hi, 

Expected behaviour should be: 

1. User finish voice call
2. Then, the STK menu is launched to the user with for options (in Spanish): 

 a. Visualizar
 b. Enviar tarjeta
 c. Activar buzón
 d. Salir

Comment 5

4 years ago
Hi David, if that's the case, I definitely do not see any STK proactive commands in the logs that Isabel provided. Have you tried this SIM card on an Android device and see the STK menu come up? If so, please share adb logs (main & radio).
Flags: needinfo?(dpv)
Hi Carol!

We don't have this SIM card in the office, but I'll try to get those logs. I'll let you know... 

Thks!
David
Flags: needinfo?(dpv)
You need to log in before you can comment on or make changes to this bug.