Age | Commit message (Collapse) | Author |
|
In onPostDialWait, onDetailsChanged, and onConferenceableCallsChanged
callbacks, check to make sure the call list contains a mapping for the
Telecom Call object.
Bug:23031241
Change-Id: I2a9703d9c303fe0b2e320d811d21c71e5c429269
(cherry picked from commit 71a6555ac854303dc023c5e6c9a27c63ec956e3d)
|
|
|
|
Bug: 22924782
Change-Id: I1da931b805658376fb9db418210662273d9c1db8
|
|
|
|
|
|
Bug: 22155815
Change-Id: Ie82b9970d1d5794b8ff7e7606fd63df14516e480
|
|
|
|
Bug:22925987
Change-Id: I20ad0ea5e40342805a2004654e6b78f420c33873
|
|
|
|
In MT InCallScreen, the customMessage dialog
which appears when user tries to reject a call
with message, is not set to null when user
cancels the dialog.
InCallUIActvity is not finished if there is any
pending dialog which is not null and hence this
issue is seen.
Set the dialog variable to null once the dialog
is cancelled by the user.
Bug: 22254547
Change-Id: I86d314461c760387cb5f8099a01da9afe4a79085
|
|
|
|
Bug: 22646355
Change-Id: Iad8f4ed9b29f97b3c6d403b63f9fdf7f3b26f460
|
|
|
|
Change-Id: If10314ac8f18e57c4ad5938086aa3c302c7f6c8d
Auto-generated-cl: translation import
|
|
Bug: 22442874
Change-Id: Id3d522415db3a551c646950a7023478226182ae9
|
|
Bug: 22442874
Change-Id: Id3d522415db3a551c646950a7023478226182ae9
|
|
|
|
|
|
It is not really useful and is distracting when a lot of
information changes happen at once.
Other animations (like fading in of elapsed call time) will
still continue to work.
Bug: 22274741
Change-Id: I303f776a6873dab3d07569a2518fda039d64becf
|
|
|
|
The AnswerPresenter is responsible for initiating the creation
of the UI during a new incoming call, so there is no need
to do a null check on getUi in onIncomingCall.
Original fix was made in ag/651766 but seems to have been
lost in a series of merges.
Also, if the same instance of InCallPresenter is reused across
activity teardown and setups, this can result in mAnswerPresenter
getting lost from the set of incoming call listeners. To fix this,
always readd it at setup.
Bug: 22357229
Change-Id: Iecd80fa0187d756181ada7631c4246ad48f7131e
|
|
|
|
Bug: 22275083
Change-Id: I0e955a2bca1af9d0059082872aaa2b7f4e6e8042
|
|
|
|
Change-Id: Ia2f59aef96ca80fb3b727a68f18cb36b2d12b88e
Auto-generated-cl: translation import
|
|
|
|
Change-Id: Iaaa35d62cd06f4d675592fcc5d61cea44bfc7671
Auto-generated-cl: translation import
|
|
|
|
|
|
|
|
|
|
The previous behavior relied on WINDOW_STATE_CHANGED events to
announce outgoing/incoming calls, at which point in time
the CallCardFragment was not guaranteed to be non-null.
Bug: 20172391
Change-Id: I65bf86bc1a5edf5430ae5aabcb3535f42d1ccb08
|
|
Show InCallActivity in recents (only during an active
call)
Bug: 17411752
Change-Id: I2c69c517f7278df78454bf69fce93880bc00997a
|
|
Reusing a previously HUN for a non-incoming call notification
can lead to unexpected behavior with the NotificationManager.
Instead, keep track of what kind of notification we are currently
displaying, so that we can cancel the old HUN and display a new
notification if the need arises.
Also log a little less verbosely when creating notification actions.
Bug: 21926442
Change-Id: Id888b65aeecded6b9ca22f7cf36b265af3d93327
|
|
An accessibility click on the glowpad now exposes the touch targets
as virtual views to accessibility services. Performing an accessibility
click on each virtual view performs the same function as swiping towards
that target.
Mark contact photo as unimportant for accessibility, it doesn't provide
any useful context or functionality.
Bug: 19075527
Change-Id: I2e980394175bf77379f5cb99126dd5970e0f0555
|
|
|
|
|
|
|
|
Setting a second InCallActivity before destroying the first is
unexpected but not irrecoverable, so don't crash.
Bug: 21806586
Change-Id: I817041ff6bae900c3b9f225ec66fe223c877e68d
|
|
|
|
into mnc-dev
|
|
Bug: 21959749
Change-Id: I6662d96b9caaf3c5c94cfc0453cdd226ab850cec
|
|
STATE_NEW has no meaning within InCallUI and can confuse
the internal logic. Treat it as STATE_CONNECTING for purposes
of state tracking.
Also, track whether the activity is visible rather than
whether it is the foreground activity (by tracking onStart/onStop
vs onResume/onPause). This fixes some unexpected UI transitions
when a dialog (e.g. wifi-calling dialog) shows up over the InCallUI.
Bug: 19217176
Change-Id: Ifa5953e27aa4ed777ed8798c628df1bdc96ed1eb
|
|
mnc-dev
|
|
Increase the delay before disconnecting the call for
DisconnectCause.ERROR, so that the user has time to acknowledge
the error.
To avoid regressing on b/20956721, keep track of any calls
that are pending a disconnect. If the user has explicitly dismissed
the error dialog, disconnect the call immediately to avoid blocking
the UI any further.
Bug: 21436856
Change-Id: I339cdbf1ba99fda5b1f5c8c31f722c97b64f487f
|
|
|
|
|
|
Along with checking if the call ID's are the same, add a check to see if
the 2 phone call numbers are still the same to correctly update the
contact info cache used to present the UI to the user.
Bug: 20032056
Change-Id: I81bcc6b31df9fa12c3a399ce6a2897662a1be74b
|
|
|
|
Nova Wi-Fi calling allows you to switch between Wi-Fi and
cell by clicking on the status label.
Unfortunately many users are accidentally triggering this
with their face.
As a work around I'm switching the trigger from click to
long press.
Change-Id: I68d7c597cf4d74a3f6b5bfee06e470b4ddcfc1ee
|