Closed Bug 905059 Opened 11 years ago Closed 11 years ago

[zffos1.1] Can't get IMEI. There are more logs & shortscreenss

Categories

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

defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WORKSFORME
blocking-b2g -

People

(Reporter: teng.fei33, Unassigned)

References

Details

(Whiteboard: [u=commsapps-user c=dialer p=0 s=v1.1-bugs-sprint-20130819][POVB])

Attachments

(2 files)

54.54 KB, application/octet-stream
Details
5.25 MB, application/octet-stream
Details
Attached file log+pic.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_20130814144945)

Steps to reproduce:

We can't get the IMEI in some places.
1. the engineer mode;
2. the settings -> device information -> more information -> IMEI
3. dial "*#06#"  on the dialer interface




Actual results:

we can't get the imei information and we got an error occurred when dial the num.

Pls see the attachment. We attached some logs and pics.


Expected results:

2013-08-14-03-56-19.png : shows setting's interface
2013-08-14-03-58-41.png : shows the error  interface after dialing *#06#
06.txt : print logs after dialing *#06#
Diag_lib.txt : it's starting up logs; We may could exclude the possibility that An operations  occurred on drive level.
Blocks: 899451
leo+ requested per bug 899451.
blocking-b2g: --- → leo?
Need to fix it since IMEI info is important for the users
blocking-b2g: leo? → leo+
Could we know a bit more ? Which version, where does it comes from ? Did you tested with several SIM cards/carriers ?

What do you call the « Engineer mode » ?
Flags: needinfo?(teng.fei33)
(In reply to Alexandre LISSY :gerard-majax from comment #3)
> Could we know a bit more ? Which version, where does it comes from ? Did you
> tested with several SIM cards/carriers ?

What do you call the « Engineer
> mode » ?

Dear lissy,

I'm so sorry for the unclear descrption.

The software version is OPEN_LATAM_FFOS_V1.1.0B01(Latin America).

I have tested with some SIM cards and We couldn't get the imei as well.

The engineer mode is used by out test engineers to test some function such as bluetooth, lcd, led, etc. 

Do you need other more informations?
Flags: needinfo?(teng.fei33)
(In reply to 滕飞 from comment #4)
> (In reply to Alexandre LISSY :gerard-majax from comment #3)
> > Could we know a bit more ? Which version, where does it comes from ? Did you
> > tested with several SIM cards/carriers ?
> 
> What do you call the « Engineer
> > mode » ?
> 
> Dear lissy,
> 
> I'm so sorry for the unclear descrption.
> 
> The software version is OPEN_LATAM_FFOS_V1.1.0B01(Latin America).
> 
> I have tested with some SIM cards and We couldn't get the imei as well.
> 
> The engineer mode is used by out test engineers to test some function such
> as bluetooth, lcd, led, etc. 
> 
> Do you need other more informations?

Yes, I don't know what's « OPEN_LATAM_FFOS_V1.1.0B01 ». Where is it available ? Which gecko and gaia does it contains ?

How can I access this engineer mode ? Is it part of our gecko/gaia ?
Flags: needinfo?(teng.fei33)
Whiteboard: [u=commsapps-user c=dialer p=0]
Whiteboard: [u=commsapps-user c=dialer p=0] → [u=commsapps-user c=dialer p=0 s=v1.1-bugs-sprint-20130819]
Hi Alexandre,

OPEN_LATAM_FFOS_V1.1.0B01 is the full build package provided by ZTE and it is available on ZTE FTP site. As far as I know, your phone is v790 (Inari) so that I don't suggest you using this full package to flash you phone. It will damage your phone. The latest build now is OPEN_LATAM_FFOS_V1.1.0B04 on ZTE's FTP site. Gaia/gecko build is based on 8/12. Hope this help. Hope this help.
(In reply to Ivan Tsay (:ITsay) from comment #6)
> Hi Alexandre,
> 
> OPEN_LATAM_FFOS_V1.1.0B01 is the full build package provided by ZTE and it
> is available on ZTE FTP site. As far as I know, your phone is v790 (Inari)
> so that I don't suggest you using this full package to flash you phone. It
> will damage your phone. The latest build now is OPEN_LATAM_FFOS_V1.1.0B04 on
> ZTE's FTP site. Gaia/gecko build is based on 8/12. Hope this help. Hope this
> help.

Well, we still don't know how much it diverges from our codebase, and if there's no Inari build, I won't be able to reproduce anything. Getting IMEI works well here. The provided logs are totally useless: either they were not produced with the correct debug level or they were not taken while the real issue was happening.

Could it be possible to have full radio and logcat from boot ? With the RIL and libril in debug ?
Assignee: nobody → lissyx+mozillians
Attached file no network.rar
Dear Tsay,
Thank you very much for the information.

Dear LISSY,
The attachment is the adb log.
We found that the ril level could get the right IMEI num.

Please unzip the attachment,open the file logcat_main.txt,search the key word "imei",you will find some relative logs.

08-15 15:37:41.469   117   200 D Diag_Lib: RID 0 corresponds to as_id 0
08-15 15:37:41.469   117   200 D Diag_Lib: RIL=>AMSS [ label = "nv_cmd_ext_remote() - Read NV_MEID_I" ];
08-15 15:37:41.469   117   200 D Diag_Lib: Reply to RIL -->  IMEI 865460010004992, IMEISV 00, ESN 00000000, MEID 00000000000000
08-15 15:37:41.469   117   200 D Diag_Lib: UI <--- RIL_REQUEST_DEVICE_IDENTITY (98) Complete --- RIL [RID 0, Token 4, Success, Len 16 ]

At the same time,we found the gecko level could also get the imei from ril:

08-20 09:20:45.559   115   115 I Gecko   : -*- QCContentHelper_QC_B2G: sendRequestResults: RIL:SendMMI:Return:OK
08-20 09:20:45.689   620   620 I Gecko   : -*- RILContentHelper: Received message 'RIL:CancelMMI:Return:OK': 
{"requestId":"id{c9ce4037-24fb-49d4-b164-c7dcf238f180}","errorMsg":null}
08-20 09:20:45.689   620   620 I Gecko   : -*- RILContentHelper: handleSendCancelMMI {"requestId":"id{c9ce4037-24fb-49d4-b164-c7dcf238f180}","errorMsg":null}

08-20 09:20:45.689   620   620 I Gecko   : -*- RILContentHelper: Received message 'RIL:SendMMI:Return:OK': {"requestId":"id{d5b0e86e-83d4-477a-ae2c-4d40f86d6f29}","result":"000039485642710"}

08-20 09:20:45.689   620   620 I Gecko   : -*- RILContentHelper: handleSendCancelMMI {"requestId":"id{d5b0e86e-83d4-477a-ae2c-4d40f86d6f29}","result":"000039485642710"}

We hope the logs could be useful and we will analyse the code in detail.
Flags: needinfo?(teng.fei33)
Thanks, I'm gonna study this while riding the train. Looks like it might be something failing in gaia then ...
The attached logs does not contains anything talking about MMI/RIL like you pasted in your last comment, it's not helping at all. Please, give us correct logs ...
Flags: needinfo?(teng.fei33)
We found that it may caused by Qualcomm 's patch.
Now We are trying to find solution.

Tks a lot.
Flags: needinfo?(teng.fei33)
QA Contact: atsai
marking [POVB] per comment 11 and remove the assignee as well 
Hi Teng.Fei, would you take this bug? Thanks
Assignee: lissyx+mozillians → nobody
Flags: needinfo?(teng.fei33)
Whiteboard: [u=commsapps-user c=dialer p=0 s=v1.1-bugs-sprint-20130819] → [u=commsapps-user c=dialer p=0 s=v1.1-bugs-sprint-20130819][POVB]
Dear sirs,
last night we update Qualcomm 's code .
The mmi works well on today's build version.

Thanks a lot for the help.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(teng.fei33)
Resolution: --- → WORKSFORME
blocking-b2g: leo+ → -
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: