Closed Bug 857944 Opened 13 years ago Closed 13 years ago

IMEI check. It is necessary to press "SEND" key after dial the code *#06#

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect, P1)

defect

Tracking

(blocking-b2g:tef+, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)

VERIFIED FIXED
blocking-b2g tef+
Tracking Status
b2g18 --- fixed
b2g18-v1.0.0 --- wontfix
b2g18-v1.0.1 --- fixed

People

(Reporter: brg, Assigned: ferjm)

References

Details

(Whiteboard: IOT, Spain, Ikura, Chile, khepera_43289)

Attachments

(1 file)

To check the IMEI number, it is necessary to press "SEND" key after dial the code *#06# - Steps to Reproduce: Open Dialer Dial *#06# - Actual Result: Nothing happend until user press "SEND" key - Expected Result (correct behaviour wished): It should show automatically the IMEI when dialing the *#06# Buildid "20130321070205", device: ikura
blocking-b2g: --- → tef?
Depends on: MMI/Gaia
Is this needed _only_ for the IMEI code?
Adding the need-info request for Beatriz to attend Etienne's question ;-) On the other hand, it seems to be something related to the Ikura device. At least in the Unagi it does not reproduce :-( Sadly I do not have any Ikura at hand to test it :-(
Flags: needinfo?(brg)
(In reply to Etienne Segonzac (:etienne) from comment #1) > Is this needed _only_ for the IMEI code? Yes, it is _only_ needed for IMEI code (In reply to gtorodelvalle from comment #2) > On the other hand, it seems to be something related to the Ikura device. At > least in the Unagi it does not reproduce :-( Sadly I do not have any Ikura > at hand to test it :-( Tested right now with Unagi device (unagi-ICS.user.manifest.V1-train.Rel0.4.Sprint8.B-81.Gecko-303a259.Gaia-d06432a) and I can reproduce the issue easily :-(
Flags: needinfo?(brg)
(In reply to Etienne Segonzac (:etienne) from comment #1) > Is this needed _only_ for the IMEI code? Yes, please! In other case, that would be a security issue. Some vendors use an MMI code to do a factory reset, for example. The user must confirm the send of an MMI code through the dialer send button. (In reply to gtorodelvalle from comment #2) > Adding the need-info request for Beatriz to attend Etienne's question ;-) > > On the other hand, it seems to be something related to the Ikura device. At > least in the Unagi it does not reproduce :-( Sadly I do not have any Ikura > at hand to test it :-( This is easily reproducible in any Firefox OS device. By design we don't send any MMI code until we hit the send key from the dial pad. Having this kind of certification requirement is really unfortunate... :\ I'll take this.
Assignee: nobody → ferjmoreno
As Fernando said, this has to be only for the IMEI. And I would prefer for it to still need to press the dial key if the number is passed from an activity.
Are we talking about the same "Send" button and "dialing" concepts? :-) I mean, I understood that when Beatriz said "Dial *#06#", she was referring to typing *#06# and pressing the "Call" (green) button. Regarding the "Send" button, I thought she was referring to the one shown on the upper-right corner of the USSD/MMI screen. Yeah, I am weird... :-ppp
I guess Beatriz may want to say something regarding the "Yes please" by Fernando in comment 4 as well as to Antonio in comment 5 ;-)
Flags: needinfo?(brg)
(In reply to Antonio Manuel Amaya Calvo from comment #5) > As Fernando said, this has to be only for the IMEI. And I would prefer for > it to still need to press the dial key if the number is passed from an > activity. This is blocking the certification process. Android and IOS devices do not need to press the "dial"/"green" button in the dialer. (In reply to gtorodelvalle from comment #6) > Are we talking about the same "Send" button and "dialing" concepts? :-) I > mean, I understood that when Beatriz said "Dial *#06#", she was referring to > typing *#06# and pressing the "Call" (green) button. I am talking about the green key in the dialer keypad, sorry for saying "SEND" (my fault)
Flags: needinfo?(brg)
Comment on attachment 733431 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/8996 Etienne, here it goes my naive attempt to solve this issue. Could you give me your feedback while I write a few tests for it, please?
Attachment #733431 - Flags: feedback?(etienne)
(In reply to Antonio Manuel Amaya Calvo from comment #5) > As Fernando said, this has to be only for the IMEI. And I would prefer for > it to still need to press the dial key if the number is passed from an > activity. If I am not wrong, with the attached patch, a 'dial' activity request containing a "*#06#" will still require the user to hit the dial key to be completed as an actual MMI request. http://mxr.mozilla.org/gaia/source/apps/communications/dialer/js/dialer.js#38
blocking-b2g: tef? → tef+
(In reply to Beatriz Rodríguez [:brg] from comment #8) > (In reply to Antonio Manuel Amaya Calvo from comment #5) > > As Fernando said, this has to be only for the IMEI. And I would prefer for > > it to still need to press the dial key if the number is passed from an > > activity. > This is blocking the certification process. Android and IOS devices do not > need to press the "dial"/"green" button in the dialer. For the IMEI I agree, since it's mostly harmless. For all the other cases, it should still require pressing the dial button. Android had a vulnerability not too long ago related with this, check [1] for example. That's why I would prefer for the send button to be required still when the number is passed from an activity (dunno if the certification test involves that or not). [1] http://labs.bitdefender.com/2012/10/ussd-exploit-can-lock-all-android-phone-sim-cards/
Changing prio to P1, as this is a certification blocker.
Priority: -- → P1
Comment on attachment 733431 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/8996 I've just added a test for this modification. Etienne, the conditions added in dialer.js are needed to be able to run the test. I also renamed mock_call_handler.js to mock_on_call.js which is more appropriate.
Attachment #733431 - Flags: feedback?(etienne) → review?(etienne)
Comment on attachment 733431 [details] Pointer to Github pull request: https://github.com/mozilla-b2g/gaia/pull/8996 Quick comment on github, should be easy to fix :)
Attachment #733431 - Flags: review?(etienne)
Adding some colleagues in CC
Attachment #733431 - Flags: review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: IOT, Spain, Ikura
Verfied fixed on Master Build Updated to Unagi Build ID: 20130410065939 Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/mozilla-central/rev/ee5ca214e87c Gaia: f6587418cc5fd8dfe885539ae1a798473890c7f5 Verified Not fixed on Unagi Build ID: 20130410070204 Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/935ff9a97f7b Gaia: aff876b051c51d091cecf322b90c4f0093281b5e and on Unagi Build ID: 20130410070209 Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/423f7851bdb5 Gaia: c614b3f3c956dc1e1adf93cf4cf41511ce75de80
Status: RESOLVED → VERIFIED
v1-train: f2133bee28657b8ec435d14d820a3684be491a10
Flags: needinfo?(ferjmoreno)
the needsinfo was because this does not uplift cleanly to v1.0.1
Whiteboard: IOT, Spain, Ikura → IOT, Spain, Ikura, Chile, khepera_43289
This is working as expected on Ikura device. Build id: 20130421003941
Tested with AT4 team in Chile. Working correctly on both my 4/26 and 5/13 partner builds.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: