History log of /frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
baecdb610b30a5d4b35345f8fc63fcbc2133c149 18-Feb-2017 Jack Yu <jackyu@google.com> Added device state monitor

Added DeviceStateMonitor to replace the legacy screen state RIL
API. Instead of sending the screen state to the modem, the new
device state monitor can explicitly turn on/off the unsolicited
response from the modem based on difference scenarios (e.g.
tethering, charging, screen state). It also sends more device
state to the modem including charging state, power saving state,
and low data expected state.

Note that in order to support the old vendor RIL, framework will
still invoke the legacy screen state API to ensure the best
user experience on those devices.

Test: Manual. Unit tests.
bug: 32223897, 20125037, 28294587
Change-Id: I76ce307bde1d3160af2ac44a57f101e4cafc7ae4
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
9af99511111eeb5e9930185dc44259502811e3b6 14-Nov-2016 fionaxu <fionaxu@google.com> add SimActivationTracker for voice/data act state

- new activationtracker module to keep track of states
- interact with notifier/phoneStateListeners
- add unit test for simActivationTracker

Bug: 31061369

Test: runtest --path frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/SimActivationTrackerTest.java
Change-Id: I1d12901a3aafd2e02337febeff6ebca4ee86d674
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
361fd7439d65b54b9b064942bc2050f86ab4823b 27-Jan-2017 Chen Xu <fionaxu@google.com> Merge "fix multi-part sms issue" am: 8144860281 am: 832eea3d3f am: a19b7cb3d5
am: ee43b8b912

Change-Id: I163d06a0db6200f2275c7be431630d831350ec3d
af7bc32573007f2ea1185fc5cb4f3980e1ff1304 24-Jan-2017 fionaxu <fionaxu@google.com> fix multi-part sms issue

- sending multi-part SMS via Email was broken in NYC since we are using display
originating address to group multi-part messages.
- In a common case, only the fist SMS comes with the right email
displaying address, thus fails to group sms together.
- Fix is keep using originating_address to aggregate Multi-part SMS and introduce a new column:
display_address in the raw table to check blocking addresses for both
phone number and email address

Bug: 34118154
Test: Manual & telephony unit tests
Change-Id: Ibd902e5ccbad34c0e1e97d7c699258dc4d2c867a
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
b5771d36210a751e6ec916556ad0f20fcb9b4288 18-Nov-2016 fionaxu <fionaxu@google.com> Initial change on carrier signal filtering

- support new carrier configs with two signal list per carrier app
- support new broadcast mechanism to comply with background-check restriction on O.
- add carrier action agent for dispatching carrier actions

Bug: 30958215
Test: runtest --path
frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/CarrierSignalAgentTest
Change-Id: Ibf7496bdb1ba8c85384da0b667a5610a52b45d80
Merged-In: CHANGE-ID I4e9e2f56e991e9d6753f8d7e877add5ada595972
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
6a7fb078d1cacba7cf2e83b71242bb5c4c27c975 18-Nov-2016 fionaxu <fionaxu@google.com> Initial change on carrier signal filtering

- support new carrier configs with two signal list per carrier app
- support new broadcast mechanism to comply with background-check restriction on O.
- add carrier action agent for dispatching carrier actions

Bug: 30958215
Test: runtest --path
frameworks/opt/telephony/tests/telephonytests/src/com/android/internal/telephony/CarrierSignalAgentTest

Change-Id: I4e9e2f56e991e9d6753f8d7e877add5ada595972
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
b4a28109bedc71afa5465247a86473a86d4b31fa 19-Nov-2016 Chad Brubaker <cbrubaker@google.com> Add single use App specific incoming SMSes

This allows applications to request that an upcoming incoming SMS be
routed directly to the calling application and to do so without
needing the RECEIVE_SMS permission.

This is especially important for ephemeral applications which we do not
want to have the ability to get the RECEIVE_SMS permission but do want
to support SMS based phone number verification. Ephemeral apps can use
this API to receive and SMS from their backend but will not be able to
access other SMSes on the device.

This is done by providing the app a token which when included in a
subsequent SMS message causes the application provided PendingIntent to
be sent with the SMS message data attached.

Test: Verified that an SMS containing the code is routed to the app.
Test: runtest --path GsmInboundHandlerTest.java
Test: cts-tradefed run cts -m CtsPermission2TestCases

Bug: 33047670
Change-Id: I7d2d259f09370bc8fac90dc5654231df4edd7e85
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
91c714c06cc426b4f1af05a758c4d560b16f6d24 11-Jul-2016 Tyler Gunn <tgunn@google.com> Finalizing Multiendpoint functionality.

1) Finish plumbing of PULLING call state.
2) b/29522023 - Handle case where the maximum number of calls across all
devices has been reached and a new call cannot be placed; report a new
Telephony disconnect cause which maps to an appropriate user friendly
message.
3) b/29633039 - Make the ImsExternalCallTracker keep track of the last
call pull state for each external call. Also, track whether the device is
in a call, and whether video is enabled on the device. Use this to enforce
the rules that an external video call cannot be pulled if video is not
enabled on the device, and that calls cannot be pulled when there is an
active call on the device.
4) Fixed a circular initialization dependency between ImsPhoneCallTracker
and ImsExternalCallTracker. Previously, the ImsPhoneCallTracker would
spool up the ImsMultiEndpoint service and set the ImsExternalCallTracker
as a listener. HOWEVER, the ImsEXternalCallTracker isn't actually
created until AFTER the ImsPhoneCallTracker is. It just so happens the
ImsPhoneCallTracker init happens on a thread, so ImsExternalCallTracker
would normally be initialized before ImsPhoneCallTracker. Whoops.

Bug: 29522023
Bug: 29633039
Change-Id: Iddabb61dcad79c93665c28e07b333e807cbc576d
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
93da8529345711fd1a5617f3c8b15c0921eececb 15-Apr-2016 Tyler Gunn <tgunn@google.com> Wire up IMS framework APIs and call pull.

1. Wired up the IMS framework APIs so that the modem can inform us of new
dialog event package changes.
2. Wired up the call pull API so that calls to it make it down to an
ImsExternalConnection.
3. In ImsExternalCallTracker, listen to the call pull requests on the
external connections, and use this to trigger the actual pull of the call,
which is essentially a dial with an extra specified (per QCOM).
I abstracted away the idea of pulling the call using the ImsPullCall
interface, which ImsPhoneCallTracker implements.

Bug: 27458894
Change-Id: Idd20a95c2993b29dcd0a7e6c71fb6232cff88736
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
6e4abd849e12860a7459f7ec74496ca02b9d7ee0 28-Mar-2016 Amit Mahajan <amitmahajan@google.com> Changes to de-dup messages in SMS raw table.

Bug: 27820591
Change-Id: Ie3a28cdbbb533c74f456b7e942ddfc2cd0d66bb0
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
fec523bdc5d2b6dd90212c8076bf34bcc2ab08b2 01-Apr-2016 Tyler Gunn <tgunn@google.com> Add ImsExternalCallTracker and support for multiendpoint.

- Adding new ImsExternalCallTracker which is responsible for responding to
dialog event package information received via IMS framework.
- Added TelephonyTester intents so that I can inject fake dialog event
package data into the ImsExternalCallTracker.

Bug: 27458894
Change-Id: Icc7c4f9e25ad553107fc1cb9d5501ba45c5a1e45
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
871a2ec0bc8e8198aeb1913e7bf6cb22a7ff3604 18-Mar-2016 Amit Mahajan <amitmahajan@google.com> Unit tests for SmsBroadcastUndelivered.

The behavior that needs to be verified is strongly tied to
InboundSmsHandler so adding the tests in GsmInboundSmsHandlerTest.

Bug: 25691379
Change-Id: Icf62bf50c417964bb3a27587ec03452ea34c1cbd
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
ecac744a4e585e3c7af95ffa06fa3e711131200c 02-Mar-2016 Amit Mahajan <amitmahajan@google.com> First unit test for ImsPhone.

Bug: 25691379
Change-Id: I61a2f0805220782e7dbebaf50604b596ef3ba24b
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
27f471647b2da3ff50620a766c048ebef8d45ae1 18-Feb-2016 Amit Mahajan <amitmahajan@google.com> New unit tests for InboundSmsHandler.

Bug: 25691379
Change-Id: I5fcbc95467cc7bd75f3f8a7da42c3814c1d2dac8
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
60a81bdb47cf64972c8edf5b0c51e8059765e5a0 28-Jan-2016 Amit Mahajan <amitmahajan@google.com> Unit test for WapPushOverSms

Bug: 25691379
Change-Id: I26eebb8711c9369c5ab85e740254a86483125bf5
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
ec334adf4017ca172f44612d01456e671f922344 19-Jan-2016 Amit Mahajan <amitmahajan@google.com> First unit test for SMS (EVENT_NEW_SMS in GsmInboundSmsHandler).

Bug: 25691379
Change-Id: Iacb24b23c224a8889cc549d02aa0dbd415e3c3d7
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
30646d039eb54def9efd55fc54772e111b5ef115 17-Dec-2015 Amit Mahajan <amitmahajan@google.com> Removed unnecessary proxies.

Bug: 25793157
Change-Id: I692f140b89d23448a5261fec8cdeb60305287662
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java
0a567c9ed954f295df83c753239646c6f6a04128 24-Nov-2015 Amit Mahajan <amitmahajan@google.com> Adding initial tests for GsmCdmaCall and GsmCdmaPhone.

Also includes:
- Changes to fix/comment out failing tests
- Some cleanup in CallManager related to deletion of PhoneBase and
PhoneProxy
- ContextFixture containing mock Context for all telephony tests
- Phone test that exercises BroadcastReceiver support in the mock
Context
- Test showing how static function can be mocked

Bug: 25691379
Change-Id: Ia38423cef3cfb86389d044cac4e601983fae1192
/frameworks/opt/telephony/src/java/com/android/internal/telephony/TelephonyComponentFactory.java