1. decouple disconnectCause and preciseDisconnectCuase from
preciseCallState.
2. expose preciseCallState to SystemAPI and expose
onPreciseCallStateChanged to System API
3. remove/hide ImsReasonInfo from PreciseDisconnectCuase
4. expose DiconnectCuase and PreciseDisconnectCause to System API
5. new onDisconnectCauseChanged API on PhoneStateListener for CS call
and use ImsCallSessionListener for IMS call(imsreasonInfo)
6. add read_precise_phone_state to shell apk to enable GTS test
Bug: 119890559
Test: atest GtsGmscoreHostTestCases:TelephonyHostTest#testPhoneStateListener
Change-Id: If9256feff16b6bcaef1dfe194c2b0df2a48436b0
(cherry picked from commit 6a942d488a)
Merged-in: If9256feff16b6bcaef1dfe194c2b0df2a48436b0
Adding a new disconnect cause shown to the user when they attempt to place
a call when OTASP provisioning is in process.
Test: Manual with test intent.
Test: Added unit test.
Bug: 70843686
Change-Id: I5cecb79948c9467b4d297ac3ea06df6cc7fd41bd
The "can dial" method does a lot of complicated checks which end up
boiling down to a not so intuitive error to the user.
Making this better.
Test: Update unit test for can dial basic operation.
Test: Manual test these scenarios.
Bug: 73902028
Bug: 116453747
Change-Id: Ifdf681a1428c7cbb925cdf7f0c66c2d011c3d492
For packages:
android.telephony
android.telephony.cdma
android.telephony.data
android.telephony.euicc
android.telephony.gsm
android.telephony.ims
android.telephony.ims.aidl
android.telephony.ims.compat
android.telephony.ims.compat.feature
android.telephony.ims.compat.stub
android.telephony.ims.feature
android.telephony.ims.stub
android.telephony.mbms
android.telephony.mbms.vendor
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Change-Id: I02d900d6d0ec9a6b2172a71911fec61d04e4d235
Merged-In: I22547ac0ed384d74d61cfd51d20c140e392a597f
Adding new ImsReasonInfo and corresponding DisconnectCause code.
Test: Manual, added unit test for code remapping.
Bug: 69024173
Change-Id: I30da4f2493fe19fe04365b9067c7feeb90a917a3
-- Add interface in IImsUtListener to get data for
UNSOL_ON_SS.
-- Add new file ImsSsData to store the data received
as part of UNSOL_ON_SS.
-- Add approprate error codes and strings to support
to show error dialogs to user.
-- Add ImsUtInterface API's to indicate UNSOL_ON_SS
to ImsPhoneCallTracker.
Test: Manual
Bug: 64685331
Change-Id: I023c1af0d521e5b19ecce1576c4caa299ae468e3
Dial emergency call like 112 use China Unicom card, and if wait
remote server end the call, then disconnect code will be 31(NORMAL_UNSPECIFIED),
this code will be treat as DisconnectCause.ERROR in telecom-service at last,
and cause redial in telecom-service.
To fix, I change it to DisconnectCause.OTHER.
Test: Build pass
Define connection event to notify
Telecom/InCallUi about change in
account handle after redial and extra
for emergency phone handle.
Bug: 27059146
Change-Id: Ie72ab2901ec05d972204ed11f115a05b79173c1d
LOW_BATTERY is for disconnect mid-call due to low battery.
DIAL_LOW_BATTERY is for failure while dialing due to low battery.
Test: Manual.
Merged-In: Ife7a4ca5645b3fb42ab20effb4d8d4a8fef8116b
Change-Id: Ife7a4ca5645b3fb42ab20effb4d8d4a8fef8116b
Fixes: 63936576
Adds the ACCESS_CLASS_BLOCKED Disconnect cause in order
to allow the dialer to take action when this happens
during a VT call.
Bug: 33821263
Test: Build
Change-Id: I9afdd90f0a8a562b626b730dbb1b03cf37776ebd
New disconnect cause used when wifi call is dropped due to loss of wifi
connection.
Test: Manual, unit.
Merged-In: Iedaa9f54ff6dbfe90a6ce01fc9eb0aad126d05f0
Bug: 32571209
Change-Id: Iedaa9f54ff6dbfe90a6ce01fc9eb0aad126d05f0
New disconnect cause used when wifi call is dropped due to loss of wifi
connection.
Test: Manual, unit.
Bug: 32571209
Change-Id: Iedaa9f54ff6dbfe90a6ce01fc9eb0aad126d05f0
Adds support for supplying custom call forwarding prefixes in the carrier
config. When a prefix supplied in the carrier config is matched to the number
being dialed, we do not complete the call and instead show an error message
on the dialer UI.
Test: Manual
Bug: 30458052
Merged-In: I3149a565b0fd631d69ab0c0f27be509237b80177
Change-Id: I3149a565b0fd631d69ab0c0f27be509237b80177
Adds support for supplying custom call forwarding prefixes in the carrier
config. When a prefix supplied in the carrier config is matched to the number
being dialed, we do not complete the call and instead show an error message
on the dialer UI.
Test: Manual
Bug: 30458052
Change-Id: I3149a565b0fd631d69ab0c0f27be509237b80177
The radio has the ability to send back a "redial on the other slot"
DisconnectCause. This adds that DisconnectCause definition.
Bug: 31498841
Change-Id: I9a59cc81ba03562531b0445e3acb5eeec99b1aba
Adding reason code and disconnect causes for:
1. disconnects due to user disabling data.
2. disconnects due to data limit being reached.
Bug: 30702393
Change-Id: Id6ea5ee4f5aac1a8602094315f893e2f7b3cc8d6
1) Finish plumbing of PULLING_CALL state.
2) Add new disconnect cause used when maximum number of calls across
all devices has been reached.
3) Add PII mask for toString of ImsExternalCallState.
Bug: 29522023
Change-Id: I78a0a9f3c3d846cfc58a1c5bcc6f105027602cbc
A few disconnect cause mappings were missing for the multi-endpoint
disconnect causes. Adding them here.
Bug: 29236416
Change-Id: I669bd72290c0e823c54eb6062ebd658743882852
1. Adding telephony disconnet cause for use when a call was pulled.
2. Added helped method to phone number utils which can be used to reformat
a telephony number stored as a SIP URI into a tel URI.
Bug: 27458894
Change-Id: Idef25bbc7b80258b361eb913d4c94b8bb34d7a4a
Due to the way the radio works, it isn't possible to make a video call
when tty is enabled. Adding a new telephony disconnect cause to handle
this case.
Note: This was previously handled directly in Telecom which is not
correct.
Bug: 20090652
Change-Id: I90b7d6486fe00c84efe7bb1c0f30edf33a1502bc
When merged, IMS calls are consolidated into one call. Thus they
"disconnect", even though the user can continue to comminucate
with the party on that call.
We want to recognize this scenario so we can control relevant
behaviors (ie.don't play the "end call" tone in this case).
Bug: 18291234
Change-Id: I93247f88ed74467470504bec88fcfb7ed714f0ff
+ Add a hidden "UNKNOWN" default type to ToneGenerator.
- Hide the Telephony DisconnectCause from the public API.
+ Add a Telecomm DisconnectCause. This is parcelable, and contains
information (code, user facing message, non-user facing reason,
and tone) to help describe the disconnect state and what behaviors
an application can implement for the user experience. This reduces
the causes for a disconnect to a more generic set.
+ Lots of work to pipe this through. DisconnectCause replaces the
code and message which were formerly passed around.
Bug: 17241433
Bug: 17329632
Change-Id: I9d337e478a8784bcc0ade02267c2df52cac9bf17
- Changing package from android.telecomm to android.telecom
- Changing package from com.android.telecomm to
com.android.server.telecomm.
- Renaming TelecommManager to TelecomManager.
Bug: 17364651
Change-Id: I192cb5d189f55db012ea72ee82ccc5aedbc21638
The original change was submitted into lmp-preview-dev and should
not have been auto-merged to master.
This reverts commit 80327f7a31b19213ec48e1ab66e6bdc8e76cb0fe.
Change-Id: I9ff8a868ffa3135583c52ef97b15311107716899
* Make context the first argument for isLocalEmergencyNumber and
isPotentialLocalEmergencyNumber
* Hide DisconnectCause
Bug: 15432083
Change-Id: I88b5ace925e3704bd032dc9694b0c2dd871b9cf9
Implement reporting of connection errors from ConnectionServices through
Telecomm to the InCallUI.
Bug: 15195720
Bug: 15117141
Change-Id: I0e1443f75a175a212fb19afde5a7eadef15d239d
The Android code base defines call disconnect codes in three places:
- android.telephony.DisconnectCause
- android.internal.telephony.Connection.DisconnectCause
- com.android.services.telephony.common.Call.DisconnectCause
This CL consolidates the code to use the integer codes from
android.telephony.DisconnectCause everywhere.
Change-Id: I84a3fd5182a51d07fc7d81076e4b2c15ff26c61c
Added new AndroidManifest permission:
android.permission.READ_PRECISE_PHONE_STATE
Added the following PhoneStateListeners and corresponding broadcast intents:
onPreciseCallStateChanged(PreciseCallState callState);
onPreciseDataConnectionStateChanged(PreciseDataConnectionState dataConnectionState);
broadcastPreciseCallStateChanged(int ringingCallState, int foregroundCallState, int backgroundCallState,
int disconnectCause, int preciseDisconnectCause)
broadcastPreciseDataConnectionStateChanged(int state, int networkType, String apnType, String apn,
String reason, LinkProperties linkProperties, String failCause)
Added TelephonyManager intent actions with their extras and constants:
public static final String ACTION_PRECISE_CALL_STATE_CHANGED = "android.intent.action.PRECISE_CALL_STATE";
public static final String ACTION_PRECISE_DATA_CONNECTION_STATE_CHANGED = "android.intent.action.PRECISE_DATA_CONNECTION_STATE_CHANGED";
public static final int PRECISE_CALL_STATE_*
Moved public static final int DISCONNECT_CAUSE_* from PreciseCallState.java to a new class DisconnectCause.java
Moved public static final int PRECISE_DISCONNECT_CAUSE_* from PreciseCallState.java to a new class PreciseDisconnectCause.java
Change-Id: If3b88c679507c529b746046c4a17cf6d9974bd09
