Adde the indication update mode support so that a system
component can control the behavior of indication update. This
will be used by the bluetooth stack when some BT devices such like
carkit is connected, modem will continue update the signal strength
even when the screen is off.
Test: Manual
Bug: 65112388
Change-Id: I4bb4894eaaba401f655e5dc25138275f5e8498e1
If the reported CDMA location is ~= (0, 0), which
is in the middle of the Gulf of Guinea, assert that
there are no CDMA cell towers within range (there
are not) and force the location to a saner default
value of Integer.MAX_VALUE which is out of the range
of valid lats+longs.
Bug: 32364031
Test: runtest frameworks-telephony
Change-Id: I3f50054dd37cf7cef56b1bd16c3313c02da34c31
The CellSignalStrengthCdma class previously allowed
the values in the class to be kept as negative ints
but expected them to be parceled as positive ints.
This led to a confusing mess that is best unwound
by calling the actual constructor for the class and
letting the parcel values be an implementation detail.
This CL removes all of the parcel-time coersion and
instead expects that the class be constructed using
a constructor rather than by manually parceling and
then using the class to un-parcel. In addition, the
range checking for inputs is now done only once, and
values are no longer mutated in the parcel/unparcel
process.
Bug: 32364031
Test: runtest frameworks-telephony
Change-Id: I59ce8c9df1bd99547f3de941a30d6c3cea8f2b8f
-Allow zero as a valid value for CDMA ECIO. Zero
is allowed for EVDO ECIO and is equally valid for
CDMA. Making them consistent by allowing zero here.
-Set EVDO ECIO to -160 if unreported rather than
setting it to -1. The "unreported" value is
undocumented, and since -1 is well within the range
of valid values, makes no sense. Since CDMA ECIO was
setting an unreported value to a very low number,
again making them the same.
-Allow 0 for EVDO SNR. This value has a range that is
documented both in the RIL and in SignalStrength to
include zero, but we were previously disallowing 0.
Making the range check inclusive in line with the
existing documentation, which was self-consistent.
Bug: 32364031
Test: runtest frameworks-telephony
Change-Id: Ie0ca5abb4998d1b0b5abdbff9d51f364fe6db858
Min and max thresholds are fixed.
Bug: 73775507
Bug: 70698348
Test: manual and ServiceStateTrackerTest
Change-Id: Ie7fbda0627615f49b6205142c22ad48e88735f80
Merged-In: Ie7fbda0627615f49b6205142c22ad48e88735f80
Min and max thresholds are fixed, and should not be customizable.
Bug: 73775507
Bug: 70698348
Test: manual test on 311480 and ServiceStateTrackerTest
Change-Id: Ie7fbda0627615f49b6205142c22ad48e88735f80
hashCode() and equals() should appear together.
Bug: 73785903
Test: test on phone
Merged-In: I7f9d8943f6a0e1039815e21ff6dfe035bd674639
Change-Id: I7f9d8943f6a0e1039815e21ff6dfe035bd674639
1. Added support for message priority(indicates the priority of a
SMS to the network in the PDU) in 3gpp2
2. Added support for link control(indicates whether network can
expect more messages or not so it can decide whether to retain
the radio link or not) while sending multiple messages
3. Added support for validity period(indicates how much time the
SMS is valid at the SMSC) support in 3gpp
4. Amended UT test cases for API changes and add UT validity period
test case
Test: Verfied sending short SMS, long SMS, MMS, SMS with emoji on
live network
Bug: 34962629
process.
* Document who can send and who can receive the broadcast. What are the security restrictions?
The implication here is that there should be some. What are the wake-up semantics?
* Document who can receive SECRET_CODE action and under what circumstances,
and what permissions are needed to receive and send it.
Bug: 73751267, 73392896
Test: Basic telephony sanity
Change-Id: I1b6138c9ddf4cb3d84d8b652e18d4e57f410ee4d
Also make the possible SIM_ACTIVATION_STATE parameters @SystemAPIs
Bug: 67750905
Test: TelephonyManagerTests#test{Voice/Data}ActivationState
Change-Id: Ib2c672db1e78afdbc25c4d36da478c3b88ffe232
Merged-In: Ib2c672db1e78afdbc25c4d36da478c3b88ffe232
Use CARRIER_APP_WHITELIST to store app certificate mapped to package
name (instead of just package name as we had before).
Bug: 70042722
Test: SettingsBackupTest
Test: UiccProfileTest#testParseWhitelistMapFromString() for parsing map
Change-Id: Ia0c7c364cd8154272ef62cbbf412036b4eae1b21
No longer allow legacy apps to access cell info location data when
location is turned off in settings.
Bug: 69637693
Test: manual
Change-Id: Ibff3cc75898dc189632f2f9427892423a404333f
* Explain what developers should use instead in the @deprecated note for Telephony#BEARER
* Please add more documentation for network type bitmask - reference to just TelephonyManager is not sufficient because it has so much stuff in it.
* Also remove the @hide tag for private constants in ServiceState.
Bug: 73751228
Test: Basic telephony sanity
Change-Id: Ie7405a961db4494104750bf406f20b1b4fb8191a
