d3b06b720a761677ab3412a40d0f1fc6e328f249 |
|
10-Mar-2016 |
Sudheer Shanka <sudheersai@google.com> |
Show admin support dialog when DISALLOW_OUTGOING_CALLS is set. Bug: 26762992 Change-Id: If30918918d0aff44717286ebc3fb683574969b34
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
24b10bebff4939daeabef78e906ee447212b0c5a |
|
22-Feb-2016 |
Tony Mak <tonymak@google.com> |
Skip DISALLOW_OUTGOING_CALLS checking in managed profile. In pre-N, DISALLOW_OUTGOING_CALLS is not checked in managed profile as ACTION_CALL is always forwarded to personal side. In N, ACTION_CALL is now handled in managed profile and hence we do check DISALLOW_OUTGOING_CALLS. It does not align with the javadoc in http://developer.android.com/intl/ja/reference/android/os/UserManager.html#DISALLOW_OUTGOING_CALLS. After offline discussion, we decide to keep the pre-N behavior, because user can always copy and paste the phone number from work side to personal side anyway. Bug: 27165111 Change-Id: Id696c0ce1f3bb3fff56addc8646e997a3dfb5a42
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
0040d3f19b9ab78949949623b257d0b5656d17b2 |
|
02-Feb-2016 |
Tyler Gunn <tgunn@google.com> |
Remove call preventing video calls when TTY enabled. am: 5abd468129 * commit '5abd468129d77e9187d95450b57b2f2e3da861e2': Remove call preventing video calls when TTY enabled.
|
5abd468129d77e9187d95450b57b2f2e3da861e2 |
|
29-Jan-2016 |
Tyler Gunn <tgunn@google.com> |
Remove call preventing video calls when TTY enabled. This code was originally put in Telecom, and it really doesn't belong there. There is no reason why we should impose a telephony restriction in Telecom. Further, the code which generates a Toast in this scenario actually causes Telecom to crash. Moving this check to Telephony instead. Bug: 20090652 Change-Id: I777c0a8bfad59f9aea9abc6680f46284548912c4
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
000b6355e12b0cf1a5ed200ea66cc0a9264822b3 |
|
28-May-2015 |
Tyler Gunn <tgunn@google.com> |
Remove vt emergency call barring code from Telecom. Removing code in Telecom to prevent dialing emergency calls as a video call (this is moved to frameworks/opt/telephony). Also ensured video emergency calls are not blocked when TTY is enabled; filing follow-up bug 21474288 to ensure this gets reviewed again as I think we want to ensure this is the correct behavior. Bug: 20089489 Change-Id: I6a5f54cd6280f67b273dc0939c35fab353ad62b0
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
0749f894446f71763b0e42f9af45f4031ff43601 |
|
28-May-2015 |
Tyler Gunn <tgunn@google.com> |
Remove vt emergency call barring code from Telecom. Removing code in Telecom to prevent dialing emergency calls as a video call (this is moved to frameworks/opt/telephony). Also ensured video emergency calls are not blocked when TTY is enabled; filing follow-up bug 21474288 to ensure this gets reviewed again as I think we want to ensure this is the correct behavior. Bug: 20089489 Change-Id: I6a5f54cd6280f67b273dc0939c35fab353ad62b0
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
578a4e6661fc1be20d164458acb335356d742f72 |
|
23-Nov-2015 |
Tony Mak <tonymak@google.com> |
Add field to store who is initiating the call Insert userhandle of user that initiate the call before forwarding the intent to primary user. Previous ACTION_CALL flow: Fire ACTION_SEND (managed user) -> UserCallActivity in Telecom (parent user) -> PrimaryCallReceiver (parent user) Current ACTION_CALL flow: Fire ACTION_SEND (managed user) -> UserCallActivity in Telecom (managed user) -> PrimaryCallReceiver (parent user) The field can be used for: 1. Filter phone accounts for outgoing call 2. Insert call log based on who initiates the call 3. Pass the field to in-call UI which may uses it to indicate it is a work call. Change-Id: I78611a4394f00ce0655c37d52b7b456f213ec802
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
64196864859c3b46502002edacc235fc83f4aa32 |
|
13-Oct-2015 |
Xiaohui Chen <xiaohuic@google.com> |
clean up USER_OWNER in Telecomm Bug: 22956426 Change-Id: I7a046d8c05e4e9d3958742a23493979055d39b42
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
cf497c9f72d3f7bac609ca6d5a64ddf2e28f6dbe |
|
29-Aug-2015 |
Yorke Lee <yorkelee@google.com> |
Enforce CALL_PHONE permission for default/system dialer for non emergency calls This CL fixes a bug where a default/system dialer targeting SDK 23 would be allowed to place phone calls without the CALL_PHONE permission. This is because for the default/system dialer, the Telecom system was only enforcing the CALL_PHONE app_op. In order to enforce runtime permissions for both SDK 23 and pre SDK 23 apps, both OP_CALL_PHONE and CALL_PHONE permission must be checked. Bug: 23607431 Change-Id: I57b6388349e0637df02799c14a2850c2c6e5a300
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
e954371bc0af81ae0f74387475d53d40d4f2672d |
|
25-Jun-2015 |
Yorke Lee <yorkelee@google.com> |
Fix for startActivity(ACTION_CALL) Apps that use startActivity(ACTION_CALL) will currently always fail to have the CALL_PHONE permission when checked in Telecom because the package name is always null at this point. We already check for the permission before this so if the app does not have the permission it will already be rejected with a SecurityException. Bug: 22071972 Change-Id: Ibebadd052a13652d8390c8a30f18441110485336
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
5dc42ee62c21ee81d51a411a0cfb61653fdf2858 |
|
19-Jun-2015 |
Yorke Lee <yorkelee@google.com> |
Disallow non-emergency outgoing calls without CALL_PHONE permission Bug: 21925398 Change-Id: I9cef6cd2c11f767740d03ebce99b8b54efd1f68a
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
5b8824979e929250a46791c785b8459512236585 |
|
03-Jun-2015 |
Tyler Gunn <tgunn@google.com> |
API Cleanup: Remove references to VideoState class. - Replace use of VideoState static methods with VideoProfile equivalent. - Replace use of VideoState consts with VideoProfile equivalent. Bug: 21573551 Change-Id: I567abaf4b6c0de51656869d1c7367a7ff3e51cd1
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
4e4ed74f1c29ede44450f78354755bfabfb1fc4f |
|
06-May-2015 |
Yorke Lee <yorkelee@google.com> |
Use current userhandle when querying for default dialer Also update TestDialerActivity to use placeCall API. Bug: 20696062 Change-Id: I65f9585f7659009e76456c4613de48f0558dd0b5
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
b3feab5a6ad30161726cf2decf4c0b06a78f5d41 |
|
30-Apr-2015 |
Yorke Lee <yorkelee@google.com> |
Fix issues with UserManager.DISALLOW_OUTGOING_CALL * Make sure the correct user is checked when using the TelecomManager.placeCall API. * Since a toast cannot be shown without an activity context, show the error using the ErrorDialogActivity instead. Bug: 20665346 Change-Id: I353cb009e8f90572a52b560259582180898370d2
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
81050722a5236234e5a127f30a139f0238d316ed |
|
24-Apr-2015 |
Yorke Lee <yorkelee@google.com> |
Fix wiring to allow default dialer to make emergency calls UserCallIntentProcessor was previously hard-coded to only check for the system dialer. Bug: 20304255 Change-Id: Ie8ad56445f664056c196a1c88e7b7d711533a2dd
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
d240fe8e16205623eb6cb73c3d42448554690033 |
|
02-Apr-2015 |
Rekha Kumar <rekhak@codeaurora.org> |
IMS-VT: Change parameter type of data usage Change Data Usage methods to take parameters of type long instead of int. Change-Id: I6a277dedb5976261035084955ed8a90da256061a IMS-VT: When TTY is ON, do not allow MO VT call When TTY mode is ON, the user SHOULD NOT be allowed to make a Mobile Originating (MO) VT call and an UI alert message will be displayed explaining MO VT call cannot be initiated. Propagate the call substate changed message to the UI IMS-VT : Set the flag to start call with speaker on for incoming VT calls - There seems to be a race condition between when InCallUI enters the video mode and sets the speaker phone on and when call state changes to active. - As a result, the audio route gets reset to earpiece as we are not setting speaker phone on flag for the incoming case. This change fixes that issue. IMS-VT: Set speaker phone to true only if bluetooth or headset is not connected IMS-VT: Convert emergency video call to voice call. Convert emergency video call to voice call. Change-Id: I09b82dcb6308a1177716b77e87da68161000518b IMS-VT: Enable Video conferencing. Enable Video conferencing. Change-Id: Ief145e0592e58de46c7a75d858effdd72fa8b476 IMS-VT: Check for property before enabling speaker for MT VT calls Check persist.radio.ims.audio.output before enabling speaker if property is set to disable speaker then MT VT calls should not use the speaker. Change-Id: I0c6288a8fd672c9b7a13edac11e29875d0df4eb7
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|
8d5d9ddc66b55b6906364ab3c0e244dab4d58f13 |
|
12-Mar-2015 |
Ihab Awad <ihab@google.com> |
Make Telecom synchronous Remove main-thread handlers and add a systemwide lock object. Change-Id: I6334fdfa6c244836f6375bea302404f61c81301b
/packages/services/Telecomm/src/com/android/server/telecom/components/UserCallIntentProcessor.java
|