Le 22/11/2013 12:31, Johannes Bauer a écrit : > 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?
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 > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
