GitLab

Bug: 20626411
Change-Id: I0647f7d82f36b2fadd079250b5ba5e3f6d1de3f9

Change-Id: I96eda538d40dc863823d3fae4782e10da345899e

Change-Id: Ia2c46f1fd9e2a34481690687745d88fb1b0a861f

With IMS, the "multiparty" bit on an ImsCall is set to "true" when a call
is merged into a conference.  This not only occurs on the device hosting
the conference call, but also on the devices of the callers merged into
the conference.

This CL adds code to ImsCall to handle changes to the multiparty state of
the session.  It also includes code to track whether the ImsCall is the
Conference Host.  A call is the conference host if the conference was
established on the current device.

Bug: 19478784
Change-Id: I764d6381d25275980a87705b7b53e21cdbffb1ea

Change-Id: Ia2c46f1fd9e2a34481690687745d88fb1b0a861f

With IMS, the "multiparty" bit on an ImsCall is set to "true" when a call
is merged into a conference.  This not only occurs on the device hosting
the conference call, but also on the devices of the callers merged into
the conference.

This CL adds code to ImsCall to handle changes to the multiparty state of
the session.  It also includes code to track whether the ImsCall is the
Conference Host.  A call is the conference host if the conference was
established on the current device.



Bug: 19478784
Change-Id: I764d6381d25275980a87705b7b53e21cdbffb1ea

There is no reason why we cannot continue with merge cleanup
(just to be safe) on a call regardless of if the "i'm in a merge"
flag is set or not. If, for some reason, the call is not
part of a merge, its a NOOP. This handles the case when the
callbacks are out of order and we receive a callSessionMergedFailed()
after a callSessionTerminate() on the merge host. It doesn't really
make sense for the callbacks to come back that way but we should
support it either way.  I also cleaned up the processMergeFailed()
function so that it doesn't abort when there is no merge peer.
Now the logic cleans up the merge host anyways and cleans up the
peer only if it exists.
Note that this is only a partial fix for this bug. The other issue
(main issue) that we need to resolve is why the first conference
puts Telecom in a state where the second conference fails.

Bug: 19852295
Change-Id: I3acf8fd4fd5c199c01ca2c4ead4119f3876e38d5

Moved the logging from the radio log to the system log for a
better chance at seeing something from customer reports.

Bug: 19625417
Change-Id: Ib5ae7275fce0a502ba6a1ad356f32f1010d14198

When CF and CW MMI request will be triggered,
user preferred serviceclass will be sent to
the lower layers.

Change-Id: I419aca453657063941d2b9121b508a0a69a17e6a

Bug: 19697174
Change-Id: I4b1538052f4bc2bf5d7c55f78467c6c52b49efd8

Change-Id: I2b57fbcf73110b453307a936dd3c8421c51d5030

Bug 19682545
Change-Id: Ia3fbcc3aba38cc6c5bae180b512a16f02f48f457

- Add support for propagating IMS Registration error codes and error
 messages.
- Propagate the call session handover info to the UI
Change-Id: If2f2008734735f52614bd046fee144843a465ecf

* commit 'f4311129':
  Add interface to determine whether the IMS service is available

TMo requires WFC and Enhanced 4G LTE mode to be enabled/disabled independently.
IMS used to be stopped when 4G LTE was disabled and started when it was
enabled. Now we need to take WFC into account when making decision about
starting/stopping IMS.

Change-Id: Icc92097a98e07994783b2ec3579d86b05315d0a2

Bug: 19447972
Change-Id: Ida074dd6840c1c7682bdca32d858aa28db2dc71d

Change-Id: Ia6ab8e5941b707d77321059450e6235f27ecbf38

The main purpose was to simply the logic so that the code is more
explicit about what it is doing. There was also a bug in the hold and
resume flow that was fixed.

Bug: 19294176
Change-Id: I558d6da919b9d763f1fd2413e8f9a3dfa5d0e4be

When conference call is failed, the mUpdateRequest of both host and peer
imscalls should be updated to UPDATE_NONE.

Bug:  19285127
Change-Id: Ib4afcbf3223d0f0be856e3686f899ade38235e96

- revisit code to trigger processMergeComplete; we used to assume that we
were done merging when the transient session started.  We now have to
check on terminate and on hold to see if all the calls have been

Bug: 18960042
Change-Id: I682303558c6958d85d2358102757608041b8451e

Bug: 18576107
Change-Id: I79d0c44a579923cc36fecd2798754cc8a72839c6

- VoLTE is disabled if TTY is turned on and it is not supported
  over VoLTE.
- Add API indicating whether VoLTE is enabled due to TTY restrictions.
  Uses configuration of VoLTE on TTY supported and current TTY mode.
- Move code changing Settings.Global.ENHANCED_4G_MODE_ENABLED
  from MobileNetworkSettings activity.

Bug: 18593974
Change-Id: Ib2706cf5f30412a735cc6f24228accc7f1216804

Pass notification to Phone app

Bug: 18247323
Change-Id: I428f8df60ebada280c6aa16debf1ff44246533bd

Do not invoke sendToTarget ourselves. Instead, pass the message
through to the ImsCallSession implementation, and rely on that
to send the message to the target.

Bug: 18643493
Change-Id: I37a891ecf71d55b93f24f9b853b64b34a24e0910

Bug: 18576107
Change-Id: Id16ea5ed3ce0c714f658cc86b66f487199d999a7

Bug: 18576107
Change-Id: I84c66089291ffb4051ed7ef70d4a2bcf4a24c3d7

Support of start and stop dtmf tones in Imsphone

Bug: 18371919
Change-Id: I04f5d6f88088e5b77d314d4db9271fd49abf5dca
CRs-Fixed: 751797

The issue was when we set the merge peer/merge host.  We were always
setting the merge peer to the BG call.  This is fine when there is no
conference, but when we already have a conference we need to take into
account whether the FG or BG is the conference.

Bug: 18652342
Change-Id: I910a1bee3d3e04477861ed68f2a77a49d0da8471

When Conference call is on HOLD and merged, mHold flag is required
to be reset explicitly as Telephony does not send RESUME request
in this scenario.

Bug: 18625579
Change-Id: Icb0b2b52d7dfe64c456b4e7c1b2e7458640ee1da

Bug: 18446228
Change-Id: I77e0047d97be6fb4a81e4e25e0404e2cdcb16644

Bug: 18576223
Change-Id: Ia36750b121836e088ac8f75946bbbe90a5dbdf08

The ImsCall code makes extensive use of a "CallGroup".  This CallGroup has
been the source of a number of bugs, since the CallGroup concept does not
match well with how we are performing merges in IMS.

1. Removed Call Group, replacing with a "peer" and "host" references in
the ImsCall.
2. Revisited the merge logic within the context of the peer/host changes.
3. Also, changed log statements to log the ImsCall instead of the session.
This aids debugging by making it more clear what the context of the various
method operations are.

Bug: 18588383

Change-Id: I78613c44bf656c8ebf9e5d6a1145784ce630deef

Bug: 18576822
Change-Id: I7e1c79fff307a5f433529213ee2670ad58080d91

Bug: 18292176
Change-Id: Ie42fb083cf505ff5bd5c13c6424d2606dec494de

- Save the state if the call when it is merged and there is a
call group of which it is not the owner. We conclude that this
call was merged into the other call group. If the merge fails,
we set this state back to false.
- Delete updateCallGroup, as it is an unused method.
- When a merge occurs, set a call group on the background call if
the referral call's CallGroup is null. Before, when two IMS
connections were first merged into a conference, the call group
was not set on the background call and so pathway through
notifyConferenceSessionTerminated (which checks for mWasMerged)
never occurred.

Bug: 18291234
Change-Id: Ibb981bdeb8e1f8d0fca6fde3845876aba13e93e3