tree 13f0b46bcc8e6d748f79e790a4ac48888a087338
parent 10e5134f49994e2ee20ba87166cbb2fe8ccd1d15
author Srikanth Chintala <srikchin@codeaurora.org> 1394794617 +0530
committer pkanwar <pkanwar@google.com> 1499353969 -0700

Do not inform user when the alpha identifier is a null data.

This code change has below fixes related to play tone
proactive cmd.

1. Current code is not in accordance with the spec
3GPP TS 11.14, 6.4.5. Play Tone, as user is informed when the
alpha identifier is a null data.

With reference to the spec, if there is no alpha identifier,
show the text message to the user depending on the config setting.

If alpha identifier data is null, play only tone and do not
inform the user.

Move the code to handle play tone from ToneDialog to StkAppService
in cases where only tone needs to be played and no user inform needed.

Dismiss the tone dialog from StkAppService after play tone finish.

Send the intent to StkAppService from ToneDialog to finish
the play tone, when user presses back key.

Ref spec: 3GPP TS 11.14, 6.4.5. Play Tone.

2. Send the correct Message object for the Play Tone command.

When stopping the tone that is playing due to the Play Tone command,
a delayed Message is sent to StkAppService with its 'arg2' field
containing a flag that indicates if tone dialog activity needs to be
closed. But when handling the received messages, StkAppService expects
the Message object's 'arg2' field to contain the slot Id on which the
command is received. This causes unexpected behavior when executing
the Play Tone command.

Use a different field in the Message object to send the the value of
the flag which indicates if tone dialog activity needs to be closed.

3. set slotId in message for OP_STOP_TONE

- unable to send the response to the
correct sim card
- Set the slotId as arg2 in the message

Bug: 35615464
Test: manual
Change-Id: Ib25986efe1d7c26976015f666580a3deb28bb328