Closed
Bug 933524
Opened 11 years ago
Closed 7 years ago
[1.3][Inari][Helix] T-Mobile SIM card is not detected on M-C
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(blocking-b2g:-)
RESOLVED
WONTFIX
blocking-b2g | - |
People
(Reporter: nhirata, Unassigned)
Details
Attachments
(4 files, 2 obsolete files)
Gaia fe5c8d08fd3c9757b3f3c9d88cc09abd7eaa82e4
SourceStamp f0d363d72753
BuildID 20131031040201
Version 28.0a1
Inari
1. flash the device with today's build
2. go to settings
Expected: Cellular & Data shows vendor
Actual: Cellular & Data shows ???
Note:
no bars in the notification; can't search for service provider.
Georgia,
can you help to check this?
Assignee: nobody → gwang
Comment 2•11 years ago
|
||
Dear Naoki,
I've tried the build. (inari.zip from below link)
https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/nightly/mozilla-central-inari/latest/
Signal bar shows well, settings can display operator name.
Could you double check if it's device hardware or SIM problem? Or might help provide RIL log for us~ Thank you!
Flags: needinfo?(nhirata.bugzilla)
Reporter | ||
Comment 3•11 years ago
|
||
Hi Georgia
This is what I found :
+ The AT&T sim works fine;
- T-mobile SIM does not work. I think it's some sort of setting for T-Mobile US?
Flags: needinfo?(nhirata.bugzilla)
Reporter | ||
Comment 4•11 years ago
|
||
To note, I think it may be our configuration file as I had a similar issue with Helix 1.1 HD... (bug 921615)
Comment 5•11 years ago
|
||
Hi Naoki,
As I comment on bug 921615, the T-mobile SIM card state shows ready on log.
But device couldn't get network's mcc/mnc, radio kept reporting searching/unregistered.
Usually, for GSM/UMTS card, there's no need to do specify configuration.
Is it possibly network coverage problem? Or prepay sim out-of-date?
We tried several local operator in Taipei, the behaviour is normal on Inari.
It's hard to repro this issue here since lake of active T-mobile SIM.
Flags: needinfo?(nhirata.bugzilla)
Comment 6•11 years ago
|
||
Btw, our expired T-mobile's SIM has the same behaviour as bug description.
Reporter | ||
Comment 7•11 years ago
|
||
Ok, so it sounds like an issue with the T-mobile configuration?
Flags: needinfo?(gwang)
Comment 8•11 years ago
|
||
As I previous said, the behavior should happened on "expired" SIM.
It's just like specific SIM issue, should not happen on T-mobile normal SIM.
Flags: needinfo?(gwang)
Reporter | ||
Comment 9•11 years ago
|
||
This happens on a non-expired T-Mobile SIM.
Flags: needinfo?(nhirata.bugzilla) → needinfo?(gwang)
Hi, Naoki-san
Can you kindly help to enable debug for RIL (https://bugzilla.mozilla.org/show_bug.cgi?id=811605#c5) and attach some log for us to check?
adb logcat -b radio -b main
Thanks.
Comment 11•11 years ago
|
||
Dear Naoki, Please see Yoshi's Comment 10, could you help capture log for us?
Flags: needinfo?(gwang)
Comment 12•11 years ago
|
||
(In reply to Georgia Wang from comment #11)
> Dear Naoki, Please see Yoshi's Comment 10, could you help capture log for us?
Flags: needinfo?(nhirata.bugzilla)
Reporter | ||
Comment 13•11 years ago
|
||
I found that the bug does not occur with the rildebug turned on. The bug only occurs with the ril debug turned off. This may be why you did not see the issue.
Flags: needinfo?(nhirata.bugzilla)
Comment 14•11 years ago
|
||
I just got a T-mobile's 3G SIM and try on this build. It can camp on network & get operator name.
No matter enable or disable rildebug, the T-mobile SIM works well.. It is difficult to debug here..
Dear Naoki,
Here's some question need to check:
1. Is this 100% repro? (With any T-mobile's SIM, not just specific one)
2. The SIM is 2G, 3G, or LTE?
3. How about the SIM's behavior on other device? Like unagi, or Android's phone.
4. Capture log without rildebug. (make sure airplane mode is off)
5. The string below Settings->Cellular & Data, Call settings, SIM Security (screenshot is ok)
Thank you again for your help~
BR
Georgia
Flags: needinfo?(nhirata.bugzilla)
Reporter | ||
Comment 15•11 years ago
|
||
> Here's some question need to check:
> 1. Is this 100% repro? (With any T-mobile's SIM, not just specific one)
Yes
> 2. The SIM is 2G, 3G, or LTE?
3G
> 3. How about the SIM's behavior on other device? Like unagi, or Android's
> phone.
the t-Mobile sim works on the Buri device as well as android
> 4. Capture log without rildebug. (make sure airplane mode is off)
nhirata-19333:b2g-distro 3 nhirata$ adb logcat -b radio
Note: log switch off, only log_main and log_events will have logs!
> 5. The string below Settings->Cellular & Data, Call settings, SIM Security
> (screenshot is ok)
Flags: needinfo?(nhirata.bugzilla)
Reporter | ||
Comment 16•11 years ago
|
||
screenshot.
Reporter | ||
Comment 17•11 years ago
|
||
Attachment #8335415 -
Attachment is obsolete: true
Reporter | ||
Comment 18•11 years ago
|
||
Are you doing a shallow flash (gecko/gaia) or a complete flash using images?
Reporter | ||
Comment 19•11 years ago
|
||
I am seeing the very same issue on the Helix device.
Before going to 1.3, I am using 1.1 and it shows the SIM card. After updating to 1.3, this is what I get.
Attachment #8335417 -
Attachment is obsolete: true
Reporter | ||
Updated•11 years ago
|
Summary: [1.3][Inari] SIM card is not detected on M-C → [1.3][Inari][Helix] T-Mobile SIM card is not detected on M-C
Comment 20•11 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #18)
> Are you doing a shallow flash (gecko/gaia) or a complete flash using images?
I'm complete flash the daily build on comment 1.
Hi Naoki-san
Since you said that the behavior is gone when you enable the debug from RIL,
can you capture the *radio log* for us?
adb logcat -b radio
I will try to find any useful information from the radio log.
Thanks
Comment 22•11 years ago
|
||
I am getting this error (or related) on the ZTE Open. Info about the device:
configured with
ANDROIDFS_DIR=/Users/ryan/hd2/rtemp/b2g/system BRANCH=v1.2f ./config.sh inari
git commit info
f13307550 (https://github.com/mozilla-b2g/gaia/commit/f13307550640e1ace0f600e6858a73bd6166e801)
loaded to the device with
./build.sh
./flash.sh
After the flash, and on the first boot of the device, I am prompted with the configuration wizard. After that the cellular connection is Available! I can send and receive texts, calls, etc. Then after a restart of the device, The cellular is not available. In the settings, I see "Cellular & Data) and under the header is "???"
I have followed the suggestions to edit user.js and enable the debug from the RIL. Below is the output of adb logcat -b radio (I start the logs with airplane mode on, and then turn that off). Hopefully enough info!
I/Gecko ( 456): -*- RILContentHelper: Received message 'RIL:CardLockResult': {"lockType":"pin","requestId":"id{5ac3561e-1c13-4e86-97e2-0eeed64f0895}","rilMessageToken":9,"rilMessageType":"iccGetCardLockState","facility":"SC","password":"","serviceClass":7,"rilRequestType":42,"rilRequestError":0,"success":true,"enabled":false}
I/Gecko ( 456): -*- RILContentHelper: fire request success, id: id{5ac3561e-1c13-4e86-97e2-0eeed64f0895}, result: {"lockType":"pin","enabled":false,"success":true}
I/Gecko ( 486): ###################################### forms.js loaded
I/Gecko ( 486): ############################### browserElementPanning.js loaded
I/Gecko ( 486): ######################## BrowserElementChildPreload.js loaded
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Gecko ( 112): -*- RadioInterface[0]: 'ril.radio.disabled' is now false
I/Gecko ( 112): -*- RadioInterface[0]: Reported radio state is off, desired radio enabled state is true
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Gecko ( 112): -*- RadioInterface[0]: RIL is not ready for data connection: radio's not ready
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/wpa_supplicant( 501): rfkill: Cannot open RFKILL control device
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/wpa_supplicant( 501): wlan0: Trying to associate with SSID 'polestar'
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/wpa_supplicant( 501): wlan0: Associated with e0:cb:4e:3e:79:f9
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/wpa_supplicant( 501): wlan0: WPA: Key negotiation completed with e0:cb:4e:3e:79:f9 [PTK=TKIP GTK=TKIP]
I/wpa_supplicant( 501): wlan0: CTRL-EVENT-CONNECTED - Connection to e0:cb:4e:3e:79:f9 completed (auth) [id=2 id_str=]
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
I/Gecko ( 112): -*- RadioInterface[0]: RIL is not ready for data connection: radio's not ready
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
Comment 23•11 years ago
|
||
More logs that look interesting:
D/memalloc( 112): /dev/pmem: Freeing buffer base:0x48b75000 size:49152 offset:3252224 fd:164
D/memalloc( 112): /dev/pmem: Freeing buffer base:0x48b69000 size:49152 offset:3203072 fd:161
I/Gecko ( 456): -*- RILContentHelper: Sending MMI *#06#
I/Gecko ( 112): -*- RadioInterfaceLayer: Received 'RIL:SendMMI' message from content process
I/Gecko ( 112): -*- RadioInterface[0]: SendMMI {"mmi":"*#06#","requestId":"id{c9b9d893-c6c1-4be6-9ee0-e06bf674c221}"}
I/Gecko ( 112): RIL Worker[0]: Received chrome message {"mmi":"*#06#","requestId":"id{c9b9d893-c6c1-4be6-9ee0-e06bf674c221}","rilMessageToken":12,"rilMessageType":"sendMMI"}
I/Gecko ( 112): RIL Worker[0]: SendMMI {"mmi":"*#06#","requestId":"id{c9b9d893-c6c1-4be6-9ee0-e06bf674c221}","rilMessageToken":12,"rilMessageType":"sendMMI"}
I/Gecko ( 112): RIL Worker[0]: MMI {"fullMMI":"*#06#","procedure":"*#","serviceCode":"06","dialNumber":""}
I/Gecko ( 112): RIL Worker[0]: New outgoing parcel of type 38
D/RILC ( 115): UI --- RIL_REQUEST_GET_IMEI (38) ---> RIL [RID 0, token id 104, data len 0]
D/RILC ( 115): RID 0 nv srv 3GPP(1): modem id=0, ma=Multimode(0), net pref=GSM WCDMA preferred(0)
D/RILC ( 115): [RID 0] ReqList entries :
D/RILC ( 115): RIL_REQUEST_RADIO_POWER (23), token id 5
D/RILC ( 115): RIL_REQUEST_RADIO_POWER (23), token id 26
D/RILC ( 115): RIL_REQUEST_GET_IMEI (38), token id 104
D/RILC ( 115): RID 0 corresponds to as_id 0
D/RILC ( 115): RIL=>AMSS [ label = "nv_cmd_ext_remote() - Read NV_UE_IMEI_I" ];
I/Gecko ( 112): RIL Worker[0]: Outgoing parcel: 0,0,0,8,38,0,0,0,104,0,0,0
D/RILC ( 115): Reply to RIL --> IMEI 865460010289080
D/RILC ( 115): [RID 0] ReqList entries :
D/RILC ( 115): RIL_REQUEST_RADIO_POWER (23), token id 5
D/RILC ( 115): RIL_REQUEST_RADIO_POWER (23), token id 26
D/RILC ( 115): UI <--- RIL_REQUEST_GET_IMEI (38) Complete --- RIL [RID 0, Token 104, Success, Len 16 ]
I/Gecko ( 112): RIL Worker[0]: Received 52 bytes.
I/Gecko ( 112): RIL Worker[0]: Already read 0
I/Gecko ( 112): RIL Worker[0]: New incoming parcel of size 48
I/Gecko ( 112): RIL Worker[0]: Parcel (size 48): 0,0,0,0,104,0,0,0,0,0,0,0,15,0,0,0,56,0,54,0,53,0,52,0,54,0,48,0,48,0,49,0,48,0,50,0,56,0,57,0,48,0,56,0,48,0,0,0
I/Gecko ( 112): RIL Worker[0]: We have at least one complete parcel.
I/Gecko ( 112): RIL Worker[0]: Solicited response for request type 38, token 104, error 0
I/Gecko ( 112): RIL Worker[0]: Handling parcel as REQUEST_GET_IMEI
I/Gecko ( 112): -*- RadioInterface[0]: Received message from worker: {"mmi":"*#06#","requestId":"id{c9b9d893-c6c1-4be6-9ee0-e06bf674c221}","rilMessageToken":12,"rilMessageType":"sendMMI","rilRequestType":38,"rilRequestError":0,"success":true,"errorMsg":null,"statusMessage":"865460010289080"}
I/Gecko ( 112): RIL Worker[0]: Next parcel size unknown, going to sleep.
D/memalloc( 456): /dev/pmem: Unmapping buffer base:0x4597e000 size:2564096 offset:2539520
D/memalloc( 456): /dev/pmem: Unmapping buffer base:0x46381000 size:2588672 offset:2564096
E/GeckoConsole( 456): [JavaScript Warning: "The character encoding of a framed document was not declared. The document may appear different if viewed without the document framing it." {file: "app://settings.gaiamobile.org/resources/obtaining_source_code.html" line: 0}]
I/Adreno200-EGLSUB( 112): <CreateImage:991>: Android Image
I/Adreno200-EGLSUB( 112): <GetImageAttributes:1256>: RGBX_8888
D/memalloc( 456): /dev/pmem: Unmapping buffer base:0x472d5000 size:3301376 offset:3252224
D/memalloc( 456): /dev/pmem: Unmapping buffer base:0x465f9000 size:3252224 offset:3203072
I/Gecko ( 456): -*- RILContentHelper: Received message 'RIL:SendMMI': {"mmi":"*#06#","requestId":"id{c9b9d893-c6c1-4be6-9ee0-e06bf674c221}","rilMessageToken":12,"rilMessageType":"sendMMI","rilRequestType":38,"rilRequestError":0,"success":true,"errorMsg":null,"statusMessage":"865460010289080"}
I/Gecko ( 456): -*- RILContentHelper: handleSendCancelMMI {"mmi":"*#06#","requestId":"id{c9b9d893-c6c1-4be6-9ee0-e06bf674c221}","rilMessageToken":12,"rilMessageType":"sendMMI","rilRequestType":38,"rilRequestError":0,"success":true,"errorMsg":null,"statusMessage":"865460010289080"}
Assignee: gwang → allstars.chh
Hi Ryan,
the log information is not enough to see what went wrong.
Can you copy the full logs to pastebin, or attach it as a attachment here?
Thanks
try get the log with
adb logcat -b radio -b main
Comment 26•11 years ago
|
||
This is a log of the device already booted up, in airplane mode, and turing the airplane mode off, and not being able to connect via the sim card to the cellular network
Comment 27•11 years ago
|
||
Complete boot sequence captured, with adb logcat -b radio -b main > ../debug4.log
In this case, the cellular network was NOT available. This is the usual condition.
Comment 28•11 years ago
|
||
I was actually surprised, on this boot, it the cellular network was available via the SIM card. This captures that occurrence.
(In reply to ryan.ramage from comment #26)
> Created attachment 8342182 [details]
> adb logcat -b radio -b main > ../debug.log
>
> This is a log of the device already booted up, in airplane mode, and turing
> the airplane mode off, and not being able to connect via the sim card to the
> cellular network
I didn't see too much information in this log, not be able to judge what happened here.
(In reply to ryan.ramage from comment #27)
> Created attachment 8342185 [details]
> adb logcat -b radio -b main > ../debug4.log
>
> Complete boot sequence captured, with adb logcat -b radio -b main >
> ../debug4.log
>
> In this case, the cellular network was NOT available. This is the usual
> condition.
I didn't find anything wrong for *RIL* in this log, except some error in processing ICC IO, but that won't hurt you.
It seems modem cannot register to voice network, always in 'searching' state.
I guess there's some problem in the modem side,
however that needs chipset-vendor to check this.
(In reply to ryan.ramage from comment #28)
> Created attachment 8342186 [details]
> adb logcat -b radio -b main > ../debug2.log
>
> I was actually surprised, on this boot, it the cellular network was
> available via the SIM card. This captures that occurrence.
Also nothing wrong with RIL this time,
After line 5600, it seems modem could register to the voice network now.
But in all your logs(debug.log and debug4.log), I can tell your SIM card is detected,
I think you met different problem from Naoki-san.
Please file another bug for it (and move your logs to that new bug),
I will try CCing some staffs from device team to see if they can help.
Thanks
de-assign myself for no action over a month.
Assignee: allstars.chh → nobody
Updated•11 years ago
|
blocking-b2g: --- → -
Comment 33•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•