Age | Commit message (Collapse) | Author |
|
pi-qpr2-release
Change-Id: I4c1de53f26b7ec12b51f01cf3e548330ae3a3760
|
|
When BluetoothRouteManager is told to connect with a null device or with
a device that doesn't match anything in the availablity list, and the
active device as reported by the BT stack is null, don't just give up.
Try connecting to just any other device.
Bug: 112018166
Test: unit, manual
Change-Id: Iaf6c570e715311c6b263c0373a7ac70e157aaf7b
Merged-In: Iaf6c570e715311c6b263c0373a7ac70e157aaf7b
|
|
pi-qpr2-release
Change-Id: Id5dc1e58e21ec6c7e8cbd53cee567aaaca5046e7
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: If5616e8fbeb3b4abde95e9ee74f94beea3b55985
|
|
pi-qpr2-release" into pi-qpr2-release
|
|
pi-qpr2-release
Change-Id: I1624b0e664d01e59ff0ab4a95b4c13ec2ff2c423
|
|
pi-qpr2-release
Change-Id: Iba0bfaea7b15a6bb542cc417ddf1e2f5049995aa
|
|
These includes,
1. The source where user initiated the call.
2. The duration between START_CONNECTION and REQUEST_DISCONNECT.
Bug: 112168722
Bug: 111818008
Test: manual and check the result of
'adb shell dumpsys telecom' for metrics data
Change-Id: I7d57ac29ad4bb6c8506b7a37b2f1bc63253fa9cb
Merged-In: I7d57ac29ad4bb6c8506b7a37b2f1bc63253fa9cb
|
|
pi-qpr2-release
Change-Id: I4c037ddb3ca7e59b077a56aa3176474db43c6379
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I7ae1d96e3db646356c2f59652fd9e309968a9f4e
|
|
4948531, 4946116, 4948532] into pi-qpr1-release
Change-Id: I0b8f2268cf9796147f18e41506e938d5bbef09c3
|
|
Test: Add unit test for PhoneAccount equality.
Bug: 112884689
Merged-In: I563d1dfbb1f6c9b20f7b4ecd50b671009451c2c4
Change-Id: I563d1dfbb1f6c9b20f7b4ecd50b671009451c2c4
(cherry picked from commit 78722fde80f8870d226294791543902196a9962a)
(cherry picked from commit 1b05f949002b6dfff830f4879e3cf22c8417b075)
|
|
Test: Add unit test for PhoneAccount equality.
Bug: 112884689
Merged-In: I563d1dfbb1f6c9b20f7b4ecd50b671009451c2c4
Change-Id: I563d1dfbb1f6c9b20f7b4ecd50b671009451c2c4
(cherry picked from commit 78722fde80f8870d226294791543902196a9962a)
|
|
pi-qpr1-release
Change-Id: If37bab7faa53792230dba917f4de5045317942eb
|
|
Test:
adb shell dumpsys telecomm
Hardware Version: EVT2.0
BUG:112541087
Change-Id: I108b7b43d6fbd9899b4adba51720f0dd9ef3980b
|
|
pi-qpr1-release
Change-Id: I9c6c3fdd138ed777ee0cf3cb966ab7e8b488951b
|
|
For regulatory requirements, prevent certain sensitive numbers from
being logged in the call log. The numbers can either be specified in the
carrier config or in the mcc config for the device.
Bug: 111470439
Test: unit, manual
Change-Id: I95040d6927d75b4104b5994e585b9498122448b0
|
|
pi-qpr1-release
Change-Id: Iee7f61ab2c2aad94a391e5421aefc3492b054b83
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I9446e02b2f05d98c6317212662c397aef827e5be
|
|
* Call updateHeadsetWithCallState(true) when BluetoothHeadset service is
connected
Bug: 109790139
Test: toggle Bluetooth while call is active
Change-Id: I8f0d981cf1cfc29409e4f50bd54a66a41280330e
(cherry picked from commit 9c0d4be940f8e4834bc061dd12d5377dabda39bb)
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I5b28168690aca1af82d63dbc10081d101c7990e1
|
|
|
|
|
|
Don't call onStartRtt inside the call connection property change unless
the RTT property flipped to on -- this'll send spurious RTT requests if
RTT was already on.
Change-Id: If8ee4e9bf994f1ed6c6fc58c3f224445493f9c5d
Fixes: 110855750
Test: manual
|
|
The rejectCall method in InCallAdapter was performing a check to see if
reply via sms is allowed, however it was doing this outside of the
"clearCallingIdentity" block. This was causing a crash when trying to
determine if the device is locked.
Test: Reject call as primary user from lock screen.
Test: Reject call as secondary user from lock screen.
Bug: 78463911
Merged-In: I85b5793a1e64c2567df035cfb3d7b6e0daa3181f
Change-Id: I85b5793a1e64c2567df035cfb3d7b6e0daa3181f
(cherry picked from commit a286b7b8f59a59290cdcc384de502b279234876f)
|
|
Check whether an outgoing call is placed to a voicemail number before
setting the RTT property on it.
Bug: 110271520
Test: manual
Change-Id: I5035372b28b8566d9b6908db7925e620a3c93e18
|
|
Currently AsyncRingtonePlayer will check every 3 seconds to see if the
ringtone has stopped playing and restart it if it has. Adding a config
option so that we can isntead opt to just set the ringtone to loop by
itself.
Default is to use existing 3 second handler check.
Bug: 75947705
Test: manual incoming ringer test
Merged-In: I0cb30b423c412d8e6c8603472b23c9f4aa65d31d
Change-Id: I0cb30b423c412d8e6c8603472b23c9f4aa65d31d
(cherry picked from commit 631c8039322fad01d81fbc3d5d97d7a7ce63a714)
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I21f15622f6da38463c1c5da7e88c291ce5b725b8
|
|
|
|
When the ConnectionService turns on the RTT property unexpectedly, call
startRtt to pass down the RTT pipes.
Bug: 80257914
Test: manual
Change-Id: I1882a867812eb83dd915ede6d8391231113dec08
|
|
The method holdActiveCallForNewCall is used to ensure that an active call
is either held or disconnected when there is a new incoming call.
There is a special case logic block which applies for Telephony calls
where there is an active call and a held call, and a new incoming call
comes in which the user answers. The special case is intended to
drop the held call so that the current active call can be held so that
the ringing call can be answered.
There was a flaw in that code which was causing the self-managed CS
CTS verifier test to fail. Essentially the special case logic block was
being invoked, and as a result when there was another active call which
could not be held from a different connection service, the call would be
held instead of disconnected.
Test: Ran CTS Verifier test and ensures it passes.
Test: Manually reproduce the telephony scenario which the special case
block is intended to handle.
Bug: 80407839
Change-Id: I348da7de84f83b1749af41d6985526bcefcc606a
|
|
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: Iebb57450fd2716eb8899c83393224d8802309c00
|
|
Send a BT_AUDIO_CONNECTED message right away if we try to connect to BT
audio and we find that it's already connected. This way we don't get
stuck in a quiescent state.
Change-Id: Idbfb4b77a243d300d47703643e22d5f1d8a2474c
Fixes: 79501344
Test: added a unit test.
|
|
|
|
Remove volume logging from CARSM -- getStreamVolume is prone to long
waits, which screws up the inner workings of CARSM.
Change-Id: I43db6e39fbdc3bdce39926ae1ebfcba8b134798d
Fixes: 79563800
Test: manual
|
|
|
|
|
|
Call.getHandle() can return null for some self-managed connection
services. CallLogManager sometimes would throw a NPE that gets swallowed
by the binder.
Add null checks throughout Telecom for the call handle. Also add logging
in CSW to actually display exceptions that happen during binder
transactions.
Also replace some unholy tabs with rightous spaces in CSW.
Change-Id: I816f86441a969a410095bb12bae307323c517fed
Fixes: 78811915
Test: manual
|
|
|
|
Account for the BT active device being null sometimes (and not starting
calls on BT when so)
Follow the BT stack's changes on the BT active device
Fixes: 79231275
Test: unit, manual, BT team's regression suite
Change-Id: Ib6ced6baa9e0ca5fa17b854ae58f19e9d49a80fd
|
|
Change to support the call focus management caused a regression in the
disconnect logic when placing an outgoing call. Some carriers do not
support holding of calls so the new logic would always disconnect a single
active call.
Reverting to the previous logic which relies on other means to tell if
we have reached the max number of held calls. In the case of a carrier
which doesn't support call holding, we'll still place the emergency call
while leaving the previous active call alone.
Test: Ensure that single active call is not disconnected when dialing
emergency call.
Test: Ensure that where an active and held call is present, the active
call is disconnected to make room for emergency call.
Fixes: 79381233
Change-Id: I248804fe7a8402fe4a6a9263ea1224a04073e03f
|
|
pi-dev
|
|
|
|
Do not include the address reported by an app implementing the self-mgd
ConnectionService API. Aothough we want to report the fact we're in
a call using the phone state broadcast, it is not desirable to include
the call identifier information reported by a third party app. The phone
number is included in the phone state broadcast to help wearable
companion apps and call blocking apps, for example, operate. Since none
of these apps can operate on self-managed calls it makes no sense to
expose the number to these apps.
Test: Manual test using test app.
Bug: 79343159
Change-Id: I29eca34bba5e1ec636fdc245bb1221b2f63bbcb1
|
|
Allow EITHER MODIFY_PHONE_STATE or ANSWER_PHONE_CALLS permission to use
this API.
Test: Manual test via test app.
Test: Added CTS tests.
Bug: 78290258
Change-Id: Ia5beade115387d0c07550a84aca3f210442e3516
|
|
Auto-generated-cl: translation import
Bug: 64712476
Change-Id: I186e0963673b87ca9809a4be4baedc5c0d550ab9
|
|
|
|
Don't store a view of the available BT devices in CARSM's version of
CallAudioState. Create a new list instead.
Change-Id: Ib66706ca1844fdb2b7d6ba1a7713840d598722f3
Fixes: 79154559
Test: manual
|
|
|