1172837 - [FLAME-L] Unable to detect SIM after reboot

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: RIL, defect)

Description

[Eric Chang [:ericcc] [:echang]]

Attachment: no_sim.log

### STR
1. FLAME-L with a SIM in it, 
2. After FTU, reboot the device

### Actual
"No SIM card" shown in Sim manager


### Version
Local build

Build ID               20150601113003
Gaia Revision          59b859d1cdce2619d4fbf84558b3db376aded83b
Gaia Date              2015-06-01 03:11:33
Gecko Revision         n/a
Gecko Version          41.0a1
Device Name            flame
Firmware(Release)      5.0
Firmware(Incremental)  eng.viralwang.20150601.111147
Firmware Date          Mon Jun  1 11:13:04 CST 2015
Bootloader             L1TC00011L60

Comment 1

[Hermes Cheng (inactive after July 27, 2015)]

Attachment: screenshot.png

I did not insert SIM card until reboot the device. Then, the display would like the attachment.

No SIM card is shown at Settings app but scanning signal icon is shown at status bar.

Comment 2

[Hermes Cheng (inactive after July 27, 2015)]

Attachment: dialer_crash - 2.log

No crash report can be found at '/data/b2g/mozilla/Crash Reports/submitted'

Get a logcat log with gaia-debug=on and ril output=on.

@Ben, I am not sure if it is a RIL bug or a gaia one. Do you know who can take this?

Comment 3

[Hermes Cheng (inactive after July 27, 2015)]

Comment on attachment 8629208 [details]
dialer_crash - 2.log

sorry, paste to wrong bug.

Comment 4

[Ken Chang[:kenkai]]

Bevis, any idea?

Comment 5

[Bevis Tseng[:bevis][:btseng](Exited)]

From the log, there is no further action in RIL_Worker[0] after receiving UNSOLICITED_RESPONSE_SIM_STATUS_CHANGED.
It seems that all requests from ril_worker to modem are blocked somehow.

I'll have a build locally to figure out the root cause.

Keep NI on me.

--
01-05 07:00:23.147   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"isAvailable":true,"rilMessageClientId":0,"rilMessageToken":4,"rilMessageType":"reportSmsMemoryStatus"}
01-05 07:00:23.156   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"rilMessageClientId":0,"rilMessageToken":6,"rilMessageType":"getCurrentCalls"}
01-05 07:00:23.160   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"disabled":false,"rilMessageClientId":0,"rilMessageToken":8,"rilMessageType":"setCellBroadcastDisabled"}
01-05 07:00:23.167   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"searchList":"","rilMessageClientId":0,"rilMessageToken":10,"rilMessageType":"setCellBroadcastSearchList"}
01-05 07:00:23.167   248   586 I Gecko   : RIL Worker: [0] cell broadcast configs not ready, waiting ...
06-01 11:48:34.868   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"attach":true,"rilMessageClientId":0,"rilMessageToken":12,"rilMessageType":"setDataRegistration"}
06-01 11:48:39.153   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"on":true,"rilMessageClientId":0,"rilMessageToken":14,"rilMessageType":"setScreenState"}
06-01 11:48:58.744   248   586 I Gecko   : RIL Worker: [0] Handling parcel as UNSOLICITED_RIL_CONNECTED
06-01 11:48:58.745   248   586 I Gecko   : RIL Worker: [0] Detected RIL version 10
06-01 11:48:58.745   248   586 I Gecko   : RIL Worker: [0] this.v5Legacy is false
06-01 11:48:58.747   248   586 I Gecko   : RIL Worker: [0] Handling parcel as UNSOLICITED_RESPONSE_RADIO_STATE_CHANGED
06-01 11:48:58.747   248   586 I Gecko   : RIL Worker: [0] Radio state changed from '-1' to '1'
06-01 11:48:58.752   248   586 I Gecko   : RIL Worker: [0] Handling parcel as REQUEST_GET_CURRENT_CALLS
06-01 11:48:58.753   248   586 I Gecko   : RIL Worker: [0] Handling parcel as REQUEST_REPORT_SMS_MEMORY_STATUS
06-01 11:48:58.767   248   586 I Gecko   : RIL Worker: [0] Handling parcel as UNSOLICITED_RESPONSE_SIM_STATUS_CHANGED
06-01 11:49:01.088   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"enabled":true,"rilMessageClientId":0,"rilMessageToken":15,"rilMessageType":"setRadioEnabled"}
06-01 11:49:02.379   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"enabled":false,"rilMessageClientId":0,"rilMessageToken":17,"rilMessageType":"setVoicePrivacyMode"}
06-01 11:49:02.419   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"mode":2,"rilMessageClientId":0,"rilMessageToken":19,"rilMessageType":"setRoamingPreference"}
06-01 11:49:17.647   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"on":false,"rilMessageClientId":0,"rilMessageToken":22,"rilMessageType":"setScreenState"}
06-01 11:49:21.602   248   586 I Gecko   : RIL Worker: [0] Received chrome message {"on":true,"rilMessageClientId":0,"rilMessageToken":24,"rilMessageType":"setScreenState"}

Comment 6

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

[Tracking Requested - why for this release]:

Comment 7

[Bevis Tseng[:bevis][:btseng](Exited)]

Hi Hermes,

After further testing locally, I found the symptom is inconsistent and these symptoms are reproducible with flame-l base image.
The symptoms after device restart with SIM inserted are:
1. No SIM detected
2. SIM will be detected after a while.
3. SIM detected normally.

Can you help to do more comparison to narrow down the problem?

I think this is more likely to be vendor's issue and we should report this problem to device vendor instead if you can also reproduce these symptoms with flame-l base image.

Thanks!

Comment 8

[Hermes Cheng (inactive after July 27, 2015)]

Bevis, since Flame L is dropping, I would pause the test for this issue.

Comment 9

[Bevis Tseng[:bevis][:btseng](Exited)]

Flame-L is dropped.