GitLab

    When user is writing password in STK and then rotates the device,
    the password numbers are displaying. And STK send the unexpected
    Terminal Response to the UICC, so it causes wrong behavior.
    Bug: 10383311, 10382809

Change-Id: I2fbce28a73fa15183e45bfc85791d4b11612aa4b

* commit '5d357cb3':
  Fixed for confirm button and cancel button is opposited in Stk dialog

* commit '6ac0fe8b':
  Fix to launch browser to home page

Certain STK commands don't provide a URL with which the browser
should be launched. For those tests, launch the browser with
the default homepage.

Bug:8312291
Change-Id: Ie9799dbe7bd73e9deeea65832af2bf58a71488d6

* commit 'f32d1e94':
  Stk notifications has purple background

Code was introduced in frameworks/base
96fd7c1c1acc03b40b1813ef65793560c175ef80 that makes notifications
refering to status_bar_latest_event_content.xml directly show up
in purple.

Using internal resource directly is discouraged, or at least the author
bids the user of this directly to have fun with the purple background.
The recommended way is to use the class Notification.Builder (Api 11)
to build your notifications. This commit uses Notification.Builder
class which setup the correct notification layout and background.

Change-Id: Idd850a16b7b68a40726a21947adc58cdcdfa1183

* commit '534cedc2':
  Dismiss Get In Key dialog after the timeout sent by the card

Don't use the default timeout for the dialog if the proactive command
explicitly specifies one.

Change-Id: I4e54d9e37ac6df832c4dcf93e6749eaff74756e1

* commit '68fdeeae':
  StkAppSerice: Stop the service when CatService Instance is null

* commit '7557b76d':
  Changed timeouts for Stk

The SIM Toolkit interface in Android uses one common
timeout for UI commands. This is not good practice,
as there is a very clear difference between use cases.

A DISPLAY TEXT command with the option “clear after delay”
and with option “Wait for user to clear” should not have
the same timeout, which is the case without a patch. The
timeouts have in the patch been set to 15 s for
“clear after delay” (i.e. automatically removed), 60 seconds
for “Wait for user to clear” and 30 s for other UI timeouts.

The times are both in accordance with ETSI 102.223 and
operator requirements.

Change-Id: I61262bf36a84f071ec4f223eb187f92e2026b68b

* commit '5020557a':
  Stk: Fix issue in DISPLAY TEXT-Sustained text

* commit '7cf07cb5':
  Added missing icon support to SETUP_CALLs setup phase

Change-Id: I973240f513e10da4b6a2693651ece7c19afe61be
Signed-off-by: Christian Bejram <christian.bejram@stericsson.com>
Signed-off-by: Patrik Ryd <patrik.ryd@stericsson.com>

3GPP TS 31.124 test case 27.22.4.1.4/1 Display Text -
sustained text is failing.

As per the CAT specification, text shall
be sustained until a subsequent proactive command
is received containing display data. Existing
dialog showing the text is not replaced with
the newly received text message resulting in
conformance case failing.

waitForUserResponse not set correctly and also
Intent.FLAG_ACTIVITY_MULTIPLE_TASK is used
resulting in a starting of a new task even if there
is an existing task.

Fix the issue by setting the waitForUserResponse
to false on response not needed and on screen
not available. Also, Intent.FLAG_ACTIVITY_CLEAR_TASK
is used as one of the flags in creating the intent
for launching the dialog.

Change-Id: Ic614f96883aaa92696982ca41d85a02341bcb132
Author: Jeevaka Badrappan <jeevaka.badrappan@intel.com>
Signed-off-by: Jeevaka Badrappan <jeevaka.badrappan@intel.com>
Signed-off-by: Shuo Gao <shuo.gao@intel.com>
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
Signed-off-by: Jack Ren <jack.ren@intel.com>
Author-tracking-BZ: 61998

Since ICS the confirm button should be on the right and the cancel
button should be on the left. So exchange them.

Change-Id: Ie6377e7080e5f0df20c5f472118f8745cc4d8d49

ANR is seen in StkAppService because of ServiceHandler is not
created due to CatService is not running.

Stop Stkapp Service if Catservice is not running to avoid ANR.
Whenever service is started using StartService first onCreate
followed by onStart will be called. Next time onwards only
Onstart will be called due to this ServiceHandler will not intialize.
Hence moving corresponding code to onStart from onCreate.

Change-Id: I5a0a78d2012e3bf5aff2b5512dd21aa7bb96ec4a

* commit 'ac72bff9':
  More issue #7226656 second user seeing primary user's apps

Don't launch this when a user is starting.

Change-Id: Ic264a8e1060407d500138d7d182414988aa03938

Change-Id: If183d04405b1a6948bc7cb9f4a96fb4674375187
Auto-generated-cl: translation import

* commit 'a8e4f50a':
  Fix mVibrator initialization.

getSystemService cannot be called during java#init, moving initialization
of mVibrator into onCreate.

Bug: 6886400
Change-Id: I644aa674fffb11ea755bd6d96169e43896c839f2

* commit '598b3dd8':
  No response sent when backlight is OFF

* commit '8e36a0a6':
  No response sent when backlight is OFF

* commit '3420f3cc':
  No response sent when backlight is OFF

Change-Id: If042bb40e8dc0c54319d38362e2aa209f3eafc5a
Auto-generated-cl: translation import

When the LCD backlight is OFF while receiving a
PLAY TONE command, the onDestroy() method is called
immediately since the app is in the background.
In onDestroy() the STOP message is removed from the
handler queue which leads to no response is sent back to
StkAppService. This causes the RIL layer to send
TR 'ME currently unable to process command' back to the SIM.
Solution is to check if a response is sent before
removing any messages from the handler queue.

Change-Id: I7ac2e99b85b38576acfe72370aa55850cdc304a0

* commit '558abb1d':
  Stk: Fix crash due to race condition

* commit 'af0dd9f0':
  Stk: Fix crash due to race condition

StkAppService doesn't really need mStkService reference in the
constructor. It will need it to respond to proactive command.
By that time StkService has to exist (proactive command comes
from it)