Previously we were returning "other terminal problem" to the network, but this
had the potential of blocking MT SMS messages for days at a time (eg, if the
problematic message is resent). Sending the "encoding problem" cause code is
reasonable since in most cases the we have encountered an error while trying
to parse the message.
Addresses b/2200412.
We need this info in the ServiceState, but rather than calcing it every time
a ServiceState is requested, we can update the values whenever the constituents
change.
bug: 2182568
When Android Telephony receives response to GET_REGISTRATION_STATE
message from RIL it may contain few fields set to NULL. Due to a parsing
exception encountered while parsing that field, the remaining fields will
not be parsed even if they are valid data. Ignore all fields that are NULL
while letting it parse non-NULL data.
For Latitude and Longitude, the values should not be hexadecimal. They
shall be parsed as decimal values as specified in the 3GPP2 C.S0005-A
specification. Invalid value is changed from -1 to Integer.MAX_VALUE.
Bug: 2201613
Change-Id: I13dd02fcfa2ae7fcb6f21c4b94b830786bd7270c
Merge commit '60be84855435c2f354833a98e1bf6154cc45078c'
* commit '60be84855435c2f354833a98e1bf6154cc45078c':
Let PLUS occur once anywhere in dial-str network portion.
Create a new extractNetworkPortion() function, since the old one is
public, that does effectively the same thing but is more flexible as
just mentioned.
Addresses issue:
http://buganizer/issue?id=2013998
Change-Id: Ie5df08ef9c871881e8728a44abf0385908000823
Merge commit '2312b65ddf3b9bff11fc31caef8d145faed106ea'
* commit '2312b65ddf3b9bff11fc31caef8d145faed106ea':
Log exception if we hit an error parsing an incoming SMS message.
Merge commit 'cd1b99125205aa7b773d9d2bcf344f1e88d2fcb1'
* commit 'cd1b99125205aa7b773d9d2bcf344f1e88d2fcb1':
Make sure CF icon updates when using "all CF" MMI.
Merge commit 'a614b948e18189adfe8e2553754db574ecb3fd7a'
* commit 'a614b948e18189adfe8e2553754db574ecb3fd7a':
Make PhoneStateListeners not call TelephonyManager
Setting WebCore cache limit depending on the memory class.
Allow the ERI overlay file to specify the text for any built-in strings.
Currently only the hard-coded strings are used for those.
Bug: 2170881
Change-Id: I5d6169696a4558e62587585e17f908f823c54a2b
Since the StatusBarPolicy is run in the System Process and shouldn't therefore call into
the Telephony process we decided to make sure all the needed info was passed along with the
original notifications.
bug: 2173053
This is independent of whether or not the ConnectivityManager wanted any particular APN on
and allows us to track the two seperately - so when data is re-enabled we don't turn
things on that CM wants off.
bug: 2158290
RIL_REQUEST_CDMA_VALIDATE_AKEY to
RIL_REQUEST_CDMA_VALIDATE_AND_WRITE_AKEY
Add failure cause for CDMA call failures due to access blocked by the
CDMA network. Rename RIL_REQUEST_CDMA_VALIDATE_AKEY to
RIL_REQUEST_CDMA_VALIDATE_AND_WRITE_AKEY. This change needs to go in
with the corresponding change in ril.h (1141)
In GSM network the data roaming (from +CGREG) and the voice roaming (from +CREG) could be different. Set GSM roaming based on both data and voice roaming status and set it true if either indicates roaming.
This solves the unwanted roaming billing issues and respects the download roaming setting in systemUpdater, DownloadProvider, and MMS downloader. For more details refer to bug 2052473.
We dropped an onTrySetupData call because onEnableNewApn calls that automatically on GSM,
but CDMA was not doing anything. Made CDMA simply call onTrySetupData.
Also, isApnTypeActive for CDMA was returning true even when no data was working. Changed
to report true when initing or connected, like GSM.
It was clearing the interfacename when it was needed later in the process - the prevented us
from clearing the route to private dns servers and clearing the flag that this was set.
Consequently future uses would not set the private dns servers (since it thought they were already
set) and our lookups would fail.
bug: 2146929
NeighboringCellInfo works in GSM and UMTS network.
In GSM network, the locaiton value is the combination of LAC and CID.
In UMTS network, the locaiton value is PSC code.
NeighboringCellInfo should access and store those two values seperately.
It involves the change of Public API.
1. Add new API getRadioType(), getLac(), and getPsc() to get location info in GSM and UMTS.
2. Deprecate setCid() and NeighboringCellInfo(int cid) because cid is set by interpreting network type.
This routine returns integer values defined in the Phone interface,
derived from RILConstants values. Direct references to the
RILConstants are replaced by references to these new ones for
consistency.
API CHANGE:
unhide TelephonyManager.PHONE_TYPE_CDMA
Addresses issue:
http://buganizer/issue?id=1905415
Change-Id: Icfec6d457231b098c031677a66770b5e57be4a44
Specifically, wait for data to be deactivated when setPowerStateToDesired()
is called during data activation.
Bug: 2101430
Change-Id: Ia97dd799f779c3f88f66bc1235e7a65958e1e04f
1. Continous ringing after receiving a call waiting while in a call,
and before user answers the call waiting, the 1st call drops. If another
MT call comes in, while it rings, it also drops, the phone will keep
ringing.
2. Data call is not re-initiated if emergency MO call collides with an MT call.
Bug: 2123287
Change-Id: I6b12a900ec60b478691544ab5326eac4952ce834
Some networks may not play ring back tone, RIL will send UNSOL ringback notification.
Apps can register for ring back tone msg and play tone to user for receiving ALERTING message.
The return value indicates to play or stop ring tone.
As per several discussions, we stick to the default behavior now.
In stead, we provide compareStrictly() as a hidden method, so that some
internal components are able to use the method if needed.
Since these are static methods, they cannot refer to the configuration files,
whose values can be obtained only via Resources object.
Please make callers' side if you want to use strict version of compare().
Internal issue number: 1892808
When parsing an SMS message as email, extractEmailAddressFromMessageBody()
checks parts.length >= 1, but then proceeds to access parts[1] (which
may not exist). Instead, check for parts.length >= 2, and treat
parts.length = 1 as non-email.
b/2122698
Resolves these specific cases:
- 8475766800;,1234
- 8475766800,;1234
Both of these should be converted to 8475766800;1234
Change-Id: Ic329007a3a6e99b1dd55cd8cdec7239dd734c3ca
