907622 - When we try to get imei from window.navigator.mozMobileConnection.sendMMI('*#06#') on gecko level, get a strange error.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: RIL, defect)

Description

[滕飞]

Attachment: imei.zip

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET4.0C; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2; TCO_20130821161325)

Steps to reproduce:

I'm from zte corporation and we are now developing engmode on  version v1.1.

The func window.navigator.mozMobileConnection.sendMMI('*#06#')  works well on the gaia level. We could get the imei num from the dialer interface or the setting app.

But when we try to use the func to get the imei on gecko level,  it returns a strage error.


Actual results:

The steps like that:
1. vendor/qcom/proprietary/b2g_telephony/Phone.cpp, we add code to func Phone::DialCall to add engmode num;
2. gecko/b2g/chrome/content/engmode  we mkdir the "engmode" dir and we add new files in this dir. 
3. gecko/b2g/chrome/content/shell.js  we add code to observer the engmode number
4. gecko/b2g/chrome/jar.mn  we add new files str(files in engmode dir) to the files.

Most of interfaces show all right but the IMEI interface.

we used the same function(window.navigator.mozMobileConnection.sendMMI('*#06#')) to get the imei number, but we get a error log like this:

01-27 03:28:55.519: E/GeckoConsole(112): [JavaScript Error: "NS_ERROR_FAILURE: 
Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMMozMobileConnection.sendMMI]" 
{file: "chrome://browser/content/engmode/testitems/js/imei.js" line: 15}]

The line 15 code:
var req = window.navigator.mozMobileConnection.sendMMI('*#06#');
from the path ---> gecko/b2g/chrome/content/engmode/testitems/js/imei.js.
 




Expected results:

Please see the attachment.There are some codes and screenshots.

Pls give me a hand .
Tks a lot.

Comment 1

[David Palomino [:dpalomino]]

Thanks Teng Fei,

Do you think could be related with: 
https://bugzilla.mozilla.org/show_bug.cgi?id=910087

Can you check if, once bug #910087 is fixed, this is still reproducible?

Thks a lot!
David

Comment 2

[滕飞]

Thanks a lot for the help,
I'm afraid that the problem is not fixed yet last week.
I will check it on daily building version again and try to find the reason.

Comment 3

[Gabriele Svelto [:gsvelto] (PTO)]

Moving to the RIL component. To the reporter, have you had the chance to test this on a recent build? Is this still a problem?

Comment 4

[Gabriele Svelto [:gsvelto] (PTO)]

I've never managed to reproduce this and there hasn't been any activity in the past few months so closing it. Reopen if this is still a problem.