Unknow SIM card state

[Carlos Sánchez]

Hi!

I was compile v1.2 & v1.3 branches, but Sim card not work, how can I resolve this issue? some ideas? Someone have this issue?

Thanks

[Hubert Figuière]

On 19/11/13 11:01 AM, Carlos Sánchez wrote:
> I was compile v1.2 & v1.3 branches, but Sim card not work, how can I resolve this issue? some ideas? Someone have this issue?

Perhaps telling us which phone would help us think of a reason why?

Hub

[Carlos Sánchez]

Hi hub, is an Alcatel One Touch Fire (hamachi).

[Johannes Bauer]

On 19.11.2013 17:48, Carlos Sánchez wrote:

>> Perhaps telling us which phone would help us think of a reason why?
>

> Hi hub, is an Alcatel One Touch Fire (hamachi).

I can confirm this, building the v1.2 branch and fastboot flashing onto
Alcatel One Touch Fire resulted in exactly that same error message for
me (no phone support, message "Unknown SIM card state").

When adb flashing that same built v1.2 branch onto a image that had
working phone support, however, phone support remained intact for me.

Regards,
Joe

[Julien Wajsberg]

Probably you flashed something that doesn't have the necessary hardware
drivers.

--
Julien

[Carlos Sánchez]

Hi Julien,

what software or drivers are necessary for the correctly SIM card working?

Thanks

[Julien Wajsberg]

These are proprietary.
I think you should have a look to similar threads in this mailing list
archives, you might have some helpful information.

Regards,
--
Julien

[Johannes Bauer]

On 19.11.2013 18:49, Julien Wajsberg wrote:

> These are proprietary. I think you should have a look to similar
> threads in this mailing list archives, you might have some helpful
> information.

Hmmm... I've searched and found these...

https://bugzilla.mozilla.org/show_bug.cgi?id=877757
http://www.mail-archive.com/dev...@lists.mozilla.org/msg03128.html
https://bugzilla.mozilla.org/show_bug.cgi?id=882174

...all of which boil down to uploading (probably) inari-specific files
to the phone in order to fix it (libril.so).

I was under the impression that the hardware-drivers are included in
the boot.img initrd -- but I guess this was wrong. Is there a standard
place where B2G keeps third-party drivers? And more importantly: Is
there a standard way to salvage these proprietary drivers from a stock
image and then merge them with a completely fresh build?

Best regards,
Johannes

[Johannes Bauer]

On 20.11.2013 20:01, Alexandre Lissy wrote:
> I don't get why we still have this issue. When building, the buildsystem first pulls closed source code from the device.
>
> So the libril should be okay. You might want to have a look at |adb logcat -b radio| too.
>
> Then enable the gecko side ril debug to cross check what happens.

Yes, when first building the build script did pull files from my phone
(which was pretty much in its original state, with working SIM card
drivers).

And when doing adb flashing, these drivers were also kept (SIM card was
still working).

However, when I (accidently) did a fastboot flash, I was left with an
image without SIM support, so obviously the drivers were pulled from the
device, but not included in the image files.

Currently I have a working image. Do you want me to try to fastboot
flash the (non-working) image again and then do the logcat? Just want to
understand correctly.

Best regards,
Joe

[Alexandre Lissy]

That would be useful, yes, if you know how to revert to a working state :).

>
> Best regards,
> Joe
>

[Johannes Bauer]

On 21.11.2013 11:44, Alexandre Lissy wrote:

>> Currently I have a working image. Do you want me to try to fastboot
>> flash the (non-working) image again and then do the logcat? Just want to
>> understand correctly.
>
> That would be useful, yes, if you know how to revert to a working state :).

Hehe, recovery is one of the first things I got taught here :-)

So here you go:

E/RILD ( 147): **RIL Daemon Started**
E/RILD ( 147): **RILd param count=1**
E/RILD ( 147): RIL_Init argc = 4 client = 0
E/RILPROXY( 144): Could not connect to rild socket, retrying:
Connection refused
E/RILPROXY( 144): Could not connect to rild socket, retrying:
Connection refused
E/RILPROXY( 144): Could not connect to rild socket, retrying:
Connection refused
W/RILC ( 147): RIL_onUnsolicitedSendResponse called before RIL_register
E/RILPROXY( 144): Could not connect to rild socket, retrying:
Connection refused
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RIL_register: RIL version 6
E/RILC ( 147): s_registerCalled = 1, s_started = 1,
RIL_getMaxNumClients = 1
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
E/RILC ( 147): RILD must accept socket from root
E/RILPROXY( 144): Failed to read from rild socket, closing...
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
E/RILC ( 147): RILD must accept socket from root
E/RILPROXY( 144): Failed to read from rild socket, closing...
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
E/RILC ( 147): RILD must accept socket from root
E/RILPROXY( 144): Failed to read from rild socket, closing...
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
E/RILC ( 147): RILD must accept socket from root
E/RILPROXY( 144): Failed to read from rild socket, closing...
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
E/RILC ( 147): RILD must accept socket from root
E/RILPROXY( 144): Failed to read from rild socket, closing...
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
E/RILC ( 147): RILD must accept socket from root
E/RILPROXY( 144): Failed to read from rild socket, closing...
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
E/RILC ( 147): RILD must accept socket from root
E/RILPROXY( 144): Failed to read from rild socket, closing...
E/RILC ( 147): isMultiSimEnabled: prop_val = 0 enabled = 0
E/RILC ( 147): RILD can't accept socket from process radio
[...]

the last few lines repeat forever and ever.

Image was flashed via fastboot, built BRANCH=v1.2. Is this helpful or do
you need further information?

Best regards,
Johannes

[Alexandre Lissy]

Le 22/11/2013 12:31, Johannes Bauer a �crit :

Yep. Search the list, there has been previous report of this. Basically
we use a rilproxy process for some user right reasons that I dont
remember. And there is a clash. The solution is to flash a fixed boot.img.

>
> Best regards,
> Johannes
>
> _______________________________________________
> dev-b2g mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g
>

[Carlos Sánchez]

I changed the manifest that builds hamachi sources, the current default revision is b2g/ics_strawberry, but on it, rild is crashed, I use ics_strawberry_v1 instead b2g/ics_strawberry and I have my own fork of b2g-manifest repo, by the way, the working revision for hardware/ril project on manifest is "caf", you can see anyway on my personal repo. I compiled a working rild for FirefoxOS on v1.2 branch, I'll try with master branch soon and I'll tell you.

https://github.com/cargabsj175/b2g-manifest

best regards

:)