commit 762ed8f1b0716eda3e9bcace78ac8beb1f2cf5c6
author Hall Liu <hallliu@google.com> Wed Nov 11 10:21:22 2015 -0800
committer Hall Liu <hallliu@google.com> Wed Nov 11 11:41:20 2015 -0800
tree bb8cda486c95040e5dd0f2d0105953e826e26acb
parent e52b94ac7311ce253987d30e71508ed741abf804

Fix incorrect in-call notification

There was an issue where the in-call notification would still show
content appropriate for a ringing call. The in-call UI may be showing
before Telecom has updated the call to the active state, so it may be
the case that state can be Call.State.Incoming while notificationType is
NOTIFICATION_IN_CALL. Since the contents of the notification are mostly
dependent on state, this causes a mismatch between the contents of the
notification and notificationType.

Thus, a notification may be displayed that has the contents of a ringing
call notification, but it will store NOTIFICATION_IN_CALL into
mCurrentNotification. When the call gets updated to the active state,
the previous notification will not be cleared, resulting in the
incorrect behavior.

Bug: 25598950
Change-Id: Ic0b3700587322b8d3cf0787a724577e58e0bb701