Telephony: Add getLteOnGsmMode() method (2/2)

Same functionality as the existing getLteOnCdmaMode, but for GSM
LTE devices.
Enable with the telephony.lteOnGsmDevice system property

From CM 10.0: Ibfb47ca608e51393b99d3308e0a6c66050b3f32e
- Moved getLteOnGsmModeStatic() to TelephonyManager.
fix for Samsung CDMA incoming SMS bug

ported from CM7/9/10

requires: http://review.cyanogenmod.org/#/c/26917/

Change-Id: I6189dd0c6aeffb0b8b530bab7994a07bb390c32c
SamsungExynos3RIL: buffer CAT Proactive Command

The RIL sends a CAT proactive command (init) before the registrant
is registered causing the command to be missed and STK menu to
not show up. Buffer it and fire it when the registrant is registered.

Change-Id: I021ce911e55b30c1a2d95d8060f7d9ff72e3b742
Add Samsung STK support (telephony part)

Support for SMS-based SIM applications.
Partially rewritten the original patch by Jüri Schultz to be less intrusive.

Change-Id: I15d2de1781a2823e24941dd792db3d372578aa9f
Samsung STK: Add USSD support

Allow USSD-based STK applications to work

Change-Id: I483f37a44a6c3ed43eefcf979e17b84877d03f93
core and telephony: Additional HSPAP support

Change-Id: I5e921d2308d873678d6ef67a91cff50d383a176b
	RIL for Samsung v6 RIL CDMA devices, based on SamsungRIL.

Change-Id: Icaf256d55a22c94d47038e9b3ea640c24d093d72
patch responseSignalStrength

Change-Id: I4f2861e765d6b112b0351e89711025a7ea1f25e4
Samsung STK: Fix SMS-based STK

SEND_SMS was falling through to SEND_USSD (which used to do nothing
until USSD support was added) causing an Exception because cmdParams
is not an instance of SendUSSDParams.

Fix by using type-checking instead of checking if Samsung STK is
enabled (because SendSMSParams and SendUSSDParams will only be
created if Samsung STK is enabled.)

Change-Id: I671014e295e9e529aad25a8b6fbd5a2e5788fc44
RIL: add HTC radio state and RIL class

Patchset 4: restore more HTC unsol message resoponses support from patchset 2.

Patchset 5: move HTC-specific messages into HTCQualcommRIL

Change-Id: I619198437c421348df3c3ff5d0a24f839c5ac43f
Prevent NPE on some CDMA devices

When the remote caller disconnects, it caused a NPE which killed the phone app
and caused other side effects such as a 'Return to call' button on the lockscreen,
and possibly more.

Change-Id: Ibbb679bde52f84c2730749d16779b1b19ff88dd3
Telephony: Forward port National data roaming and make it optional (1/2)

  by Robin Morawetz (Rdlgrmpf) and Davor Bertovic (LorD ClockaN)
  Id: Ief840d818ecf4b8ebb088fab34f01878d0a9f2d7

Change-Id: Icaaeeebdb85b2c066e0ce2cccc43daac3fa37daa
SamsungQcomCDMARIL: Add support for SIM.

Change-Id: I3194c30f36eb6436c7f77883224376386d9bd9a6
CdmaLteServiceStateTracker: simultaneous voice and data support on CDMA (e.g: SVDO)

rebased from CM10 commit

Change-Id: I228802b3d2e258892f93e28dbf9dfed8ea8960d1
SamsungQualcommCDMARIL : fix cdma/lte signal strength implimentation

From
James Roberts		Dec 10

SignalStrength.java seems to expect 99 in response[7] in 3g, and now lte rsrp is handled directly there now. What seems to work both ways (on d2vzw at least) is:

if (response[7] == 99) {
// If LTE is not enabled, clear LTE results
// 8-11 must be -1 for cdma/evdo signal strength to be used (see
// frameworks/base/telephony/java/android/telephony/SignalStrength.java)
response[8] = -1;
response[9] = -1;
response[10] = -1;
response[11] = -1;
}

and then leave response[8] alone when response[7] != 99.

Also seems SignalStrength uses 0x7FFFFFFF for INVALID on 8, 9, 10, 11 when all values are not wanted instead of -1 but seems to work either way for me.

Sorry for the long comment. Didn't want to push up a patchset on someone else's commit in case this is wrong.

Test shows:

-104 dBm 36 asu -- LTE

-88 dBm 2 asu -- CDMA - eHRPD

Change-Id: I3c182041387a698e2928e04547989e87773ef9fa
Add notification type constants.

Change-Id: I3bafac72744d0e77436324db5aafec965ca2cd45
Allow registering for supplementary service notifications.

Change-Id: Id40d320cb6935ddf4cceefa8ddb42f9229b66efa
Set audio mode after accepting the call

Set the audio mode to incall immediately after accepting the call and not wait
till call is reported as ACTIVE by RIL. This is done to speed up time taken for audio
to set up the voice path

(CM change: Remove calls to Rlog, since we haven't imported that yet)

Bug: 7612431
Change-Id: I8008edc64928016ab94aa6d770de248b5d85dc93
Fix ringing audio focus handling.

Test case:
- enable increasing ringtone starting at volume 0
- start any music player
- get an incoming call

Previous behaviour:
When ringtone volume is increased from 0 to 1, music continues playing
even
though ring tone is playing as well.

New behaviour:
When ringtone starts, music is attenuated to make user aware of incoming
call. When ringtone volume is increased to 1, music stops playing.

Change-Id: Ifc32ea162d4527572be0574024116d10ee9bca66