796657 - (MMI/Gaia) USSD/MMI codes handling in Gaia

Status: RESOLVED FIXED

(Firefox OS Graveyard :: Gaia, defect)

Description

[GH to BZ]

[GitHub issue by lissyx on 2012-09-15T21:58:18Z, https://github.com/mozilla-b2g/gaia/issues/4766]
As far as I can tell, MMI codes seems not being correctly handled.
See http://www.etsi.org/deliver/etsi_ts/122000_122099/122030/04.00.00_60/ts_122030v040000p.pdf#11 for the specifications and https://android.googlesource.com/platform/frameworks/opt/telephony/+/master/src/java/com/android/internal/telephony/gsm/GsmMmiCode.java for Android.

Some examples:
 - *#06# is expected to return the IMEI
 - *#21# is expected to return the call forwarding status

Currently, it seems all those codes are sent as USSDs which is invalid.

For example, Android 4.1.1 on Nexus S, when sendind MMI code *#21#, |logcat -b radio| shows:
D/GSM     (  479): dialing w/ mmi 'GsmMmiCode {State=PENDING action=*# sc=21 poundString=*#21#}'...

This behavior is explained as of https://android.googlesource.com/platform/frameworks/opt/telephony/+/master/src/java/com/android/internal/telephony/gsm/GSMPhone.java in method dial(), which calls processCode() of the GsmMmiCode class. One can see that all MMI codes defined in this GsmMmiCode have specific handling.

Following the call forwarding status example, we can see that it finally calls a phone.mCM.queryCallForwardStatus(), which is defined in https://android.googlesource.com/platform/frameworks/opt/telephony/+/master/src/java/com/android/internal/telephony/RIL.java which clearly does not looks like a USSD request.

Comment 1

[GH to BZ]

[GitHub comment by lissyx on 2012-09-15T21:58:49Z]
@fabi1cazenave since call forwarding configuration might be useful in settings, you could be interested in this issue.

Comment 2

[GH to BZ]

[GitHub comment by lissyx on 2012-09-18T13:14:15Z]
Should also add this document: http://www.quintillion.co.jp/3GPP/Specs/22030-800.pdf#23

Comment 3

[GH to BZ]

[GitHub comment by ferjm on 2012-09-21T15:40:58Z]
This requires some platform work https://bugzilla.mozilla.org/show_bug.cgi?id=793178

Comment 4

[Fernando Jiménez Moreno [:ferjm]]

Once Bug 793178 we need to do the appropriate front-end bits to also support MMI codes.
Since MMI support in the platform is blocking+ I am requesting blocking? for the front-end part too.

Comment 5

[Dietrich Ayala (:dietrich)]

Is there any new UX work required around MMI code support?

Comment 6

[Fernando Jiménez Moreno [:ferjm]]

(In reply to Dietrich Ayala (:dietrich) from comment #5)
> Is there any new UX work required around MMI code support?

No, it should be the same experience as for USSD

Comment 7

[Guillermo López :willyaranda (probably SLOW response)]

The idea that Germán told me yesterday is to show the possible result dictionary as a pair of label:value in the USSD screen. Or just the value if it's a simple object.

Comment 8

[Fernando Jiménez Moreno [:ferjm]]

This has been fixed in Bug 798832, please fill follow-up bugs like Bug 799435 if needed.

Comment 10

[Fernando Jiménez Moreno [:ferjm]]

This bug should have not be marked as dup, I'd like to keep it as tracker for all the rest of bugs related to MMI/USSD support in Gaia.

Comment 11

[Fernando Jiménez Moreno [:ferjm]]

I am clearing the blocking+ since we don't want to block on tracker bugs.

Comment 12

[David Palomino [:dpalomino]]

Hi!

We think it's related also to bug #857944. Thus, nominating for tef+ and adding cert meta bug for Spain.

Comment 13

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Can we close this?

Comment 14

[Fernando Jiménez Moreno [:ferjm]]

Yes!