| a1fd99a6910a97470cab01fbc28bfea82e832dab |
|
28-May-2015 |
Narayan Kamath <narayan@google.com> |
GsmMmiRecords: Fix bogus null check.
The intent clearly is to check this.mIccRecords, and not
mPhone.mIccRecords. Moreover, the latter is never null because it's
a public final AtomicReference<?>.
Change-Id: I8f42368198e19656bd676f83a70dc3aa04e7a102
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 09b65da3b46e18c8acc146d722047ba2fb161bfe |
|
19-Oct-2012 |
Preeti Ahuja <preetia@codeaurora.org> |
STK CC feature implementation
Support to display the current request is changed by STKCC.
Support to display alpha messgae from STKCC.
Support to display informatiom from new SS message.
Add FLAG_RECEIVER_FOREGROUND to alpha broadcast intent.
Bug: 17646476
Change-Id: I89671830eeef62a48e3133a2e3afbdeb096ecf3c
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 0aa03d22e29d57d1064c292bcdb4e762e9abca01 |
|
21-Oct-2014 |
Anju Mathapati <anjucm@quicinc.com> |
ussd: Suppress error dialog when ussd release received
Remove the prompt sent when network releases USSD session
Bug: 17782840
Change-Id: I4ca1d6db3be89ce2f28986cbc96824276edc6c7f
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 6103b5df6705c89193f452c35eaf5e9a26c188cf |
|
29-Aug-2014 |
Jing Zhao <zhaojing@motorola.com> |
AT&T short dialing code
User should be able to dial 0 or 00 in AT&T network.
The code should not be taken as MMI Code.
Bug: 17314389
Change-Id: I2f4187ddcbad6d78ee8d8c1881648b96a9da76dd
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| a8467dd0c524787104b1ccdddc5e8af10ba729ed |
|
13-Jun-2014 |
Wink Saville <wink@google.com> |
Merge kwd to master
Change-Id: Idb607c0aa32f80fe4fe1539aedea7a221e9e7f04
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| f4f5308a309d43fcfca8d0d5fbb54bc38c82ca3f |
|
05-Jun-2014 |
Yorke Lee <yorkelee@google.com> |
Follow API change in PhoneNumberUtils
Bug: 15432083
Change-Id: I88b5ace925e3704bd032dc9694b0c2dd871b9cf9
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 8697e0eb16fd00420efaf626ba4da3d548de3b59 |
|
19-Mar-2013 |
Magnus Karlsson <magnus3.karlsson@sonymobile.com> |
Fix order of '+' in call forwarding return result in RTL locales
The '+' is presented at the end of the phone number
instead of in the front.
Phone numbers should be presented left-to-right even
for right-to-left oriented languages (e.g. Hebrew),
hence the '+' should be placed accordingly.
Change-Id: I07d89078de4d81609e08099f93fc929a81ec172b
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 6d3c836bb8991e9cf7ffb322ebabf48c2446126d |
|
04-Nov-2013 |
Wink Saville <wink@google.com> |
Do not display dialog when PUK attempts remaining is 0.
When using MMI codes to set a new pin and the attempts remaining becomes
zero the lock screen, KeyguardSimPukView, will be handling resetting the
PIN using the PUK. Therefore we set the MmiCode state to CANCELLED which
causes the dialog to be dismissed. If we don't do this then after setting
the new PIN from the lock screen the dialog will still be present
indicating the user still needs to set the PIN.
Bug: 9928717
Change-Id: Ic7dc51ba684a1fd623f2cab0a89f40ef8ff491d5
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 3522c54a64f577f2b657a775dae9b4eb2d8003d5 |
|
25-Oct-2013 |
Wink Saville <wink@google.com> |
Few PIN/PUK fixes
Following changes have been made as part of this:
-> Changes done to display retry counter on wrong entry of
PIN1,and message to indicate Code accepted/PIN1 blocked
during PIN1 verification as per certain carrier requirements.
-> The current APIs that are used to verify the PIN and PUK only convey
whether the operation succeeded or failed. As a result on ANY failure
clients ask the user to re-enter the PIN.
Add 2 new APIs that report the actual error code and returns the
number of attempts remaing in case of failure.
-> FDN Service state was derived based on the state of PIN2. Update the
state of FDN service based on the FACILTY_LOCK messages instead.
-> Change the default value of function getIccLockEnabled to false.
When sim is deactivated/absent & user navigates to
Settings->Security->Set up SIM/RUIM card lock,
checkbox for "Lock Sim Card" option should be
unchecked by default.
-> PIN1 can be changed only after enabling SIM lock. RIL returns
REQUEST_NOT_SUPPORTED error if user tries to change PIN1 without
enabling SIM lock.
Handle the error and display appropriate message when trying to
change PIN1 using MMI code.
-> Added MMI support for change PIN1/PIN2 and unblocking PIN2
Bug: 9928717
Change-Id: I73718c9e6a8aa7244097e0dd4593a6226ff0ac08
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 21fe62acc2d11ace0410b2b6d83263a96081c092 |
|
27-Sep-2013 |
duho.ro <duho.ro@lge.com> |
telephony: redirect call barring MMI code to other purpose
Some operators redirect call barring MMI codes to other purpose.
For instance, *333# should be processed as USSD code with Indonesia
Axis SIM and Indonesia Hutchison SIM. This change is adding an array
for call barring MMI code to config.xml. So, we can redefine the array
for redirecting the call barring MMI codes. The MMI code is compared
with the call barring MMI codes from config.xml.
Bug: 10101303
Change-Id: Ib21540a90c64e105cd4bc1864238329d594cd056
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 31ae682ff511ddde4073c3f94eff15da2f7fade6 |
|
18-Sep-2013 |
Wink Saville <wink@google.com> |
Telephony: Update CF number in EF_CFIS.
When call forwarding is enabled, only status is updated in EF_CFIS.
CF number is not updated. Added support to update CF number as well.
Bug: 10642929
Change-Id: Ia764b872b7837d71ffad206e37e9b261e4db7a83
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 22d85a8e3a575a6d01d2c788587971657dfe20c6 |
|
23-Feb-2013 |
Wink Saville <wink@google.com> |
Clean up member variables.
Change-Id: Ib60f350131ade626aca682407ea0b4377b16f6c6
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| cbaa45bbf2cab852b6c9c3a887e9f803d4e857ea |
|
23-Feb-2013 |
Wink Saville <wink@google.com> |
Clean up
- Add @Overrides where needed.
- Update javadoc comments
- Remove extra semi-colons
- Rename DataConnection.java to DataConnectionBase.java
- Rename GsmDataConnection.java to DataConnection.java
- Add defaults to switch statements
- Remove/fix most "if (false)" statements. Fixed by using a CONSTANT
- Fix hidden variables by hoisting to base class or renaming
- Tweak some debug output
Change-Id: If38de2fdeaacafbf40cdfd7f84dc5c52030ba2a3
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 5f6b9345f8fe5545f576d29fb7ff9f3405d9dc05 |
|
23-Jan-2013 |
Bin Li <libin@marvell.com> |
Interprete mmi code *21*num# as registration.
Per 3GPP TS 22.030 6.5.2
A call forwarding request with a singel * would
be interpreted as registration if containing a
forwarded-to number, or an activation if not.
Change-Id: Iaf5754e49454819892fe054938ef8819f759d6bd
Signed-off-by: Bin Li <libin@marvell.com>
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 10e574acd0992d22abce257b420d333f5a49e71d |
|
14-Aug-2012 |
Jeevaka Badrappan <jeevaka.badrappan@intel.com> |
telephony: Fix issue in short code ussd detection
According to the 3PGG TS 22.030 specification
Figure 3.5.3.2: A 1 or 2 digit "short code" is
treated as USSD if it is entered while on a call or
does not satisfy the condition (exactly 2 digits
&& starts with '1').
Following rule is already addressed in function
GsmMmiCode::newFromDialString.
If the user of the device enters one digit followed
by the #-key, phone shall initiate a USSD/SS command
Change-Id: I70795da1fb5144d1c91059f6200b74b5fd33de22
Author: Jeevaka Badrappan <jeevaka.badrappan@intel.com>
Signed-off-by: Jack Ren <jack.ren@intel.com>
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
Author-tracking-BZ: 28800
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| d720945f2be5ea5fe0faf67e67d9ea0e184eba67 |
|
01-Aug-2012 |
Alex Yakavenka <ayakav@codeaurora.org> |
Telephony: Move uicc classes into uicc package
Reduce constructor visibility to package where
possible
Dependent Changes:
I3b718b9aea1f21c7906c8243b4ca0db6af495a08
I80204a2f3dc57cac875abeab390bb9db7a636ff7
Ib9c19e8b157dc7ec74eb14baca5bd3b5caf08c47
Change-Id: Ib4f43374c041cb5eaf2e3883e5ea28b2eb2c9a69
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| ded9c0af7fa49504c047275ed34c2d3b22bf0c3a |
|
07-Dec-2012 |
Wink Saville <wink@google.com> |
Use Rlog
Change-Id: Ie013f51215de8380b8de74161b6056b010711cfd
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| 9225578f29e449d30380fcf71defb1ac7e8a59db |
|
25-Sep-2012 |
John Wang <johnwang@google.com> |
Handle mmi dialing number ending with #.
According to TS 22.030 6.5.2 "Structure of the MMI", the dialing
number should not ending with #. But it is okay to have # in the
middle of dialing number.
bug:6410387
Change-Id: I1838d7012a132f27a3a879e1d34a9c3b04844def
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| e287feac673ff68565b766e0e463d105fa9cef9d |
|
10-Jul-2012 |
Alex Yakavenka <ayakav@codeaurora.org> |
Telephony: Remove CdmaLteUicc objects
-Pass IccCard object to GsmMmiCode
-Create IccCardProxy
-Make IccCard an interface and pass instance of IccCardProxy to
external applications (PhoneApp). IccCardProxy will use internal
UiccCard to map Icc requests to current active application on
UiccCard to maintain backwards compatibility for external
applications
-Add documentation to UiccController
The primary advantage of UiccController is that we can work with
multiple uicc applications at the same time. And that is a
requirement for modes like Cdma/Lte. The existing code supports
Cdma/Lte only partially and with guessing on modem side. However,
some things modem can guess, while others - it can't.
For instance, when a user tries to edit the fdn list the current
code will pass ef_id for fdn (0x6F3B). But the modem will have no
clue which fdn list the user wants to edit (csim or usim, both
have path 7FFF), and it's impossible for modem to guess correctly
all the time. All the modem can do is try to be consistent and
hope another device is doing same things. Imagine you bring your
card from another Cdma/Lte device to your new Cdma/Lte device:
if this modem uses different fdn file, it won't work as all
existing entries won't be there.
Another example is when the modem's guess is wrong for files like
csim/ef_li (7FFF 6F3A) versus usim/ef_adn (7FFF 6F3A). They have
same ef_ids so Android really should pass aid of the app it wants
to access. Without aids there is no way modem can know for sure
which file Android wants to read! However, in the current code
even Android doesn't know which aid it wants to read file from
since CdmaLteRecords has only 1 aid.
All of these problems cause more and more hacks, both in the modem
and in Android side. UiccController cleans up current code and
provides framework to work with multiple Uicc applications at the
same time.
Change-Id: I60216887b14140bdf833a8ed579ba16cad932bdc
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| bb36adde615d3d85fa0fc23935197c6bc6a799ed |
|
27-Jul-2012 |
Alex Yakavenka <ayakav@codeaurora.org> |
Telephony: Dynamically instantiate IccCard
Instantiate when get_sim_status request returns
Change-Id: I9c9333d23f1e0b23256731b245577d1a25721647
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|
| c38bb60d867c5d61d90b7179a9ed2b2d1848124f |
|
12-Jul-2012 |
Wink Saville <wink@google.com> |
Create telephony-common - DO NOT MERGE
telephony-common was created by moving some of
frameworks/base/telephony
to:
frameworks/opt/telephony
Change-Id: I32cbb5eec1fa239c1587e055c8f7ef4fc48fb62c
/frameworks/opt/telephony/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java
|