* Asks the device what set of capabilities are supported on the device
with respect to the Radio Hal
* The capabilities struct is left empty and will be filled
in once the first set of radio hal capabilities are nailed down later
in Android S
Test: Added cts, ran cts, and std tests
Bug: 163085807
Change-Id: I867f26bc649005e89ebf7a0b74f6fbeb2f44ac93
This reverts commit 83e3ca82e6.
Reason for revert: Change will not be supported by modem, so HAL for RadioConfig is no longer necessary.
Change-Id: I2eb83fd2356134ef45a782d99174fdd65f8c5a13
Change PhoneCapability structure to contain static capabilities for:
* the entire device
* each modem/radio
* each SIM slot
Created SimSlotCapability and SlotType to hold information about
device SIM slot capabilities (separate from SimSlotStatus).
Created ModemFeatures to express modem capabilities as a bitfield
of concurrently supportable modem features.
PhoneCapability has fields for UE categories, bands, access networks,
and modem switching linger time. It also contains a lists of logical
modem UUIDs, SIM slot capabilities, and all possible concurrently
supportable modem features.
TelephonyManager will have an API that returns
* the PhoneCapability for the device
* active set of ModemFeatures
Apps with CARRIER_PRIVILEGE can use these APIs to access all
capabilities of a device (eg. 5G capable, DSDS capable, etc.) and
use them to make decisions based on what the device can support.
Test: atest FrameworksTelephonyTests
Bug: 143238237
Bug: 143238191
Change-Id: I424ef176086d2308a4bf53b2c79407eabafb3178
