Contacts with phonenumbers beginning with '+' lose the '+' in the
phonebook when imported from SIM.
This was only noticable on ADN-records with unknown NPI-values which
isn't very usual.
Change-Id: I181249759ae3d4181dd3cf627c7a588394b80419
Fixing incorrect data type of RIL_UNSOL_RESPONSE_NEW_BROADCAST_SMS
in Android RIL.
The Android RIL specifies that the unsolicited response signal
RIL_UNSOL_RESPONSE_NEW_BROADCAST_SMS should contain a raw byte
array (ril.h). However, in the implementation of the Java RIL and
the C++ RIL daemon, the data is unpacked as a string. This causes
data delivered from the network stack to be garbled.
Changing so that both the C++ RIL deamon in platform/hardware/ril
and the Java RIL in frameworks/base follows the specification.
Change-Id: I9b9b26d16cd39422c43d9fa7aadfcff3e60c78ae
The terminal disallows USSD, SMS, Voice Call and Supplementary services
operations for numbers not in the Fixed Dialing Number (FDN) list when the
FDN service is enabled. FDN_CHECK_FAILURE error is sent from the RIL and the
message needs to be displayed to indicate the failure.
Change-Id: I49bd63f69a3f0201125b17cd16db2e8fcf93ddc3
Changed FDN delete to abort when number is empty rather than
when name is empty
3GPP TS 31.102 (USIM application) v9.1.0 states in chapter
4.2.24 EFFDN (Fixed Dialling Number) that the Dialling Number
field is mandatory whereas the Alpha Identifier is optional.
The current implementation of the user interface for editing
the fixed dialling list blocks creation and deletion list
entries without a name (corresponding to the Alpha Identifier)
but instead permits entries without a number. This is incompatible
with the USIM specification and
implementation.
This contribution corrects the implementation in line with
the USIM specification.
Change-Id: I7e2ca06e20401b517d705fc45c8b873b5c21cc4c
- Two Javadoc comments in telephony/cdma/SmsMessage.java had the wrong parameter name in @param.
- Typo in private constant defined in telephony/cdma/sms/BearerData.java.
Change-Id: I3c210383f74a5fef022e0958ab56ef9b7be8e97c
- Fix typos in comments in TelephonyProperties.java
- Move two .java files in telephonytests to the correct package directory.
Change-Id: Ie69da31c128899d149d4f5d5aababe8d017d8f18
When user dials an invalid number, network returns an error indicating
"unobtainable number" (See the Table 10.5.123/3GPP TS 24.008 for
the possible failure causes). Changes done to display message to
indicate user that an invalid number has been dialed.
Change-Id: I477d64bc3b59cc205396f911ff9630c640f619f3
It is for bug 2571583 to provide better failure information of network operator selection.
Network selection returns ILLEGAL_SIM_OR_ME when the failure is
permanent and no retries needed, such as illegal SIM, ME, HRL config, etc.
Change-Id: Iaf70bef64d3cbf35e4d9915418cbb5b78607f73e
SPDI-file on SIM and BCD encoded PLMN-entries wasn't parsed correctly
causing us to display wrong networknames.
Change-Id: I09d80deec45b4b3ad525a9359b4866de7549e39e
- Fixed a bunch of typos in comments (plus a few variable names)
- Removed unused import lines from telephony classes
- Added @Override attribute to overriding methods
- Made SmsMessage.PduParser inner class private & deleted unused constructor
- Added type specifiers to declarations of ArrayList and HashMap
- SimulatedCommands.getRegistrationState() had an ArrayIndexOutOfBoundsException
trying to write to index 14 of a 14-element array. I removed the
out-of-bounds assignment.
Change-Id: I054b5156aa64ab6639028d5b45a7e688b2deee08
Also change phone's ConnectionStateTrackers to use it directly,
rather than through the INetStat binder interface.
Bug: 2578938
Change-Id: I8858e2609cbec3be845a0ce5178cb03f67e01b41
For bug 2536842 to show signal strength in Emergency mode.
The STATE_EMERGENCY_ONLY of ServiceState is not in-use.
So add a hide interface to indicate Emergency mode.
Change-Id: I19398ac5e73a722dcaaf744347f961d1fa7513ac
Fixed some comment typos and cleaned up logging of unexpected calls to
CDMA-specific methods on a non-CDMA device.
Change-Id: Ia6e5fba765122cbf3186fd9fecca7a3931a76dcc
It uses the data profile paramater when setting up the connection to indicate
it's a tethered connection. We get different behavior from vzw afterwards, so
it is getting picked up.
bug:2422545
Change-Id: Ic022845088726d723813b82e166d15d7b2945da1
In change I5776324a I made DataConnection.reset asynchronous.
That was a mistake as callers to cleanUpConnection assumed
it was synchronous. Added DataConnection.resetSynchronously
as a fix, someday the trackers will become asynchronous and
this won't be necessary.
Change-Id: I4669901e5c47a712212bb388c35fbb9f9ff603a7
