861011 - [Buri] "SIM card not ready"

Status: RESOLVED FIXED

(Firefox OS Graveyard :: General, defect)

Description

[Lucas Adamski [:ladamski]]

Build ID: 20130411070205 (nightly)
Device: Buri
SIM: AT&T postpaid

In main settings panel, under "Call Settings" and "Cellular & Data" I get the message: "SIM card not ready"

APN list nor autoconfig seem to work, I have to enter it manually.  Once I do data seems to work ok.  Error above remains though, and the Usage app complains about not having "phone coverage".

Comment 1

[Vincent Liu[:vliu]]

Acquiring too much data from the return of REQUEST_GET_SIM_STATUS parcel is the root cause.

Comment 2

[Vincent Liu[:vliu]]

Hi mwu,

I pulled a request for this issue. Please see [1]. Can you please help me to merge it? Thanks

[1]: https://github.com/mozilla-b2g/android-device-hamachi/pull/4

Should I also uplift to v1-train?

Comment 3

[Michael Wu [:mwu]]

(In reply to Vincent Liu[:vliu] from comment #2)
> Hi mwu,
> 
> I pulled a request for this issue. Please see [1]. Can you please help me to
> merge it? Thanks
> 
> [1]: https://github.com/mozilla-b2g/android-device-hamachi/pull/4
> 
> Should I also uplift to v1-train?

Yes. If you can, push directly to v1-train and v1.0.1 branches.

Comment 4

[Vincent Liu[:vliu]]

(In reply to Michael Wu [:mwu] from comment #3)
> (In reply to Vincent Liu[:vliu] from comment #2)
> > Hi mwu,
> > 
> > I pulled a request for this issue. Please see [1]. Can you please help me to
> > merge it? Thanks
> > 
> > [1]: https://github.com/mozilla-b2g/android-device-hamachi/pull/4
> > 
> > Should I also uplift to v1-train?
> 
> Yes. If you can, push directly to v1-train and v1.0.1 branches.

Pull request for v1-train and v1.0.1 branches

https://github.com/mozilla-b2g/android-device-hamachi/pull/5
https://github.com/mozilla-b2g/android-device-hamachi/pull/6

Comment 5

[Michael Wu [:mwu]]

BTW, have you updated to the latest vendor image? If you haven't, Joe Cheng will be able to help you with that. I updated today and wasn't able to get my sim card recognized, even after removing ro.moz.ril.simstate_extra_field=true .

Comment 6

[Vincent Liu[:vliu]]

(In reply to Michael Wu [:mwu] from comment #5)
> BTW, have you updated to the latest vendor image? If you haven't, Joe Cheng
> will be able to help you with that. I updated today and wasn't able to get
> my sim card recognized, even after removing
> ro.moz.ril.simstate_extra_field=true .

No, I havn't updated it. I will find Joe to update the image and then check the issue you said. Thanks.

Comment 7

[Joe Cheng [:jcheng] (please needinfo)]

Hi Lucas, did you flash the build using the partner flash tool? if so, this is a known issue that partner is looking into
thanks

Comment 8

[David Scravaglieri [:scravag]]

Minusing waiting for Lucas feedback

Comment 9

[Joe Cheng [:jcheng] (please needinfo)]

per Lucas, he did not flash this using the partner tool, just the regular 1.1 nightly with ./flash.sh.

Comment 10

[Joe Cheng [:jcheng] (please needinfo)]

triage: partner already fixed it. please flash latest drivers from partner. if the problem persists, please re-nom. thanks

Comment 11

[Chris Kreinbring [:CKreinbring]]

Still repros on Buri 1.1 mozilla RIL.

Build ID: 20130528070209
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/611d727390a4
Gaia: 5f499ab1e4a274d3d28e20139c9cdc546dc4fc69
Version #: 18.0

Comment 12

[Joe Cheng [:jcheng] (please needinfo)]

wonder if you have flashed partner build first before flashing our build? thanks

Comment 13

[Joe Cheng [:jcheng] (please needinfo)]

cannot reproduce on my 2 buri partner build devices dated May 30th

Comment 14

[Al Tsai [:atsai]]

It's solved by partner side. Joe, could you please check with partners and see if we can get some feedback about solving the issue? Thanks.

Comment 15

[Tony Chung [:tchung]]

we are tracking a similar bug with Leo device, and i think they're related problems, for different reasons: gonk + device binaries.

https://bugzilla.mozilla.org/show_bug.cgi?id=859260#c43

This has been a big problem and is blocking moz QA/Eng from really moving forward with mozilla build testing.  how do we resolve this?  should we track this bug with Buri vendor, and the other with Leo?   At the end of the day, if what we need is support partner binaries, we need to get that from the OEMs to get unblocked.

Comment 16

[Michael Wu [:mwu]]

Um, apparently the uplifts were never merged. Both have been merged now.

Comment 17

[Tony Chung [:tchung]]

(In reply to Michael Wu [:mwu] from comment #16)
> Um, apparently the uplifts were never merged. Both have been merged now.

mwu, will this fix also affect Leo?  or is this for buri only?

in the meantime, is there a way i can just manually remove "ro.moz.ril.simstate_extra_field=true"  from the device to get this working?  or is there more involved to get me unblocked?

Comment 18

[Lucas Adamski [:ladamski]]

(In reply to Joe Cheng [:jcheng] from comment #12)
> wonder if you have flashed partner build first before flashing our build?
> thanks

It was the stock build that came with the device as I recall.  I later tried flashing the partner build and it bricked the devices, so can't help much I'm afraid.