diff options
| author | sqian <shuoq@google.com> | 2020-01-27 14:18:02 -0800 |
|---|---|---|
| committer | sqian <shuoq@google.com> | 2020-01-27 14:20:09 -0800 |
| commit | 6cd260243aa735dc5201b765ab09fffe34c51ab0 (patch) | |
| tree | ef4a7248e8940b394e40317eb22022a0e0556472 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 9f85cd1bdbd4bbfcc2b6b92433972c7a7e6ef07d (diff) | |
Support always reporting signal strength phone state listener
We should not allow other stack (such as Bluetooth) to directly control
modem indication reporting. The hidden API
TelephonyManager.setRadioIndicationUpdateMode added before do not
support multiple clients and do not support the case when clients'
process die.
The new solution would be adding a new listener
PhoneStateListener.LISTEN_ALWAYS_REPORTED_SIGNAL_STRENGTH and let
telephony registry (which is running under system process) to tell
telephony whether to always turn on signal strength update if any client
is listening to this event.
Introduce a new system API for TelephonyRegistry
to tell Telephony module this listening mechanism.
Introduce a new permision for this function
Test: WIP (Have this CL out to try to catch up the API deadline)
Bug: 147322848
Change-Id: Iaee832c75b29d89dbc9e5c6659e1a7e89c4a467f
Merged-In: Iaee832c75b29d89dbc9e5c6659e1a7e89c4a467f
(cherry picked from commit 93642d44330d5c124d20f4c00c09dc645987fda8)
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions