Closed Bug 909259 Opened 11 years ago Closed 6 years ago

[wasabi] 3G icon is still on notification bar even after change roaming preference to "Home" while using a roaming UIM card.

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: echu, Unassigned)

References

Details

(Whiteboard: [FT:RIL, POVB])

Attachments

(1 file)

When data call is connected with a roaming account, change roaming preference to home should disable both voice and data call. But now 3G icon can still be seen on notification bar and when trying to access data call, UL/DL animation will show.

* Build Number                
Gaia:     f94d4a9b56e8cc253089fe5ff680eb3cde303243
  B-D     2013-08-26 02:13:16
Gecko:   f216c745e68da490fd5591991398092d56d35294
BuildID   20130826061633
Version   26.0a1

* Reproduce Steps
1. Insert CT UIM in wasabi.
2. Enable data roaming and set roaming preference to Any.
3. Make sure data call is working(APN must be set for CT)
4. Set roaming preference to "Home".

* Expected Result
Signal bar has no level, data icon off, both voice and data call are not working. When try to open website, soon will get problem loading page message.

* Actual Result
Signal bar has no level,3G data icon is still there, although voice and data call are not working, when try to open website, DL/UL animation would show yet page keeps in loading progress, no page will be loaded but no problem loading page shows.

* Occurrence rate
100%
blocking-b2g: --- → koi?
Assignee: nobody → echen
Update APN info:

China Telecom
APN: ctnet
Identifer: ctnet@mycdma.cn
Password: vnet.mobi
Authentication: CHAP
Comment on attachment 795366 [details]
Change to Home and try to open website around 17:54, 8/26.

After setting roaming preference to "Home", there is no UNSOLICITED_DATA_CALL_LIST_CHANGED triggered. And the data registration status is still "registered". Those status comes from modem/ril daemon. 

==========================
08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Parcel (size 56): 0,0,0,0,253,0,0,0,0,0,0,0,6,0,0,0,1,0,0,0,49,0,0,0,255,255,255,255,255,255,255,255,1,0,0,0,54,0,0,0,255,255,255,255,2,0,0,0,50,0,48,0,0,0,0,0
08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Solicited response for request type 21, token 253, error 0
08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Handling parcel as REQUEST_DATA_REGISTRATION_STATE
08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Received dataRegistrationState network info.
08-26 17:53:47.417 I/Gecko   (  201): RIL Worker[0]: Queuing dataRegistrationState network info message: {"regState":1,"state":"registered","connected":true,"roaming":false,"emergencyCallsOnly":false,"cell":{"gsmLocationAreaCode":-1,"gsmCellId":-1},"radioTech":6,"type":"1xrtt","rilMessageType":"dataregistrationstatechange"}
Blocks: 890809
(In reply to Edgar Chen [:edgar][:echen] from comment #2)
> Comment on attachment 795366 [details]
> Change to Home and try to open website around 17:54, 8/26.
> 
> After setting roaming preference to "Home", there is no
> UNSOLICITED_DATA_CALL_LIST_CHANGED triggered. And the data registration
> status is still "registered". Those status comes from modem/ril daemon. 
> 
> ==========================
> 08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Parcel (size 56):
> 0,0,0,0,253,0,0,0,0,0,0,0,6,0,0,0,1,0,0,0,49,0,0,0,255,255,255,255,255,255,
> 255,255,1,0,0,0,54,0,0,0,255,255,255,255,2,0,0,0,50,0,48,0,0,0,0,0
> 08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Solicited response for
> request type 21, token 253, error 0
> 08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Handling parcel as
> REQUEST_DATA_REGISTRATION_STATE
> 08-26 17:53:47.407 I/Gecko   (  201): RIL Worker[0]: Received
> dataRegistrationState network info.
> 08-26 17:53:47.417 I/Gecko   (  201): RIL Worker[0]: Queuing
> dataRegistrationState network info message:
> {"regState":1,"state":"registered","connected":true,"roaming":false,
> "emergencyCallsOnly":false,"cell":{"gsmLocationAreaCode":-1,"gsmCellId":-1},
> "radioTech":6,"type":"1xrtt","rilMessageType":"dataregistrationstatechange"}

And the original data call is still in data call list after setting roaming preference to "Home". 

===================
08-26 17:54:42.375 I/Gecko   (  201): RIL Worker[0]: New incoming parcel of size 872
08-26 17:54:42.385 I/Gecko   (  201): RIL Worker[0]: Parcel (size 872): 1,0,0,0,242,3,0,0,6,0,0,0,20,0,0,0,0,0,0,0,255,255,255,255,0,0,0,0,1,0,0,0,2,0,0,0,73,0,80,0,0,0,0,0,6,0,0,0,114,0,109,0,110,0,101,0,116,0,48,0,0,0,0,0,15,0,0,0,49,0,49,0,53,0,46,0,49,0,54,0,57,0,46,0,51,0,46,0,54,0,48,0,47,0,51,0,48,0,0,0,25,0,0,0,49,0,49,0,56,0,46,0,56,0,53,0,46,0,49,0,51,0,54,0,46,0,49,0,32,0,49,0,49,0,56,0,46,0,56,0,53,0,46,0,49,0,51,0,54,0,46,0,50,0,0,0,12,0,0,0,49,0,49,0,53,0,46,0,49,0,54,0,57,0,46,0,51,0,46,0,54,0,49,0,0,0,0,0,0,0,0,0,255,255,255,255,1,0,0,0,0,0,0,0,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,0,0,0,0,255,255,255,255,2,0,0,0,0,0,0,0,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,0,0,0,0,255,255,255,255,3,0,0,0,0,0,0,0,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,0,0,0,0,255,255,255,255,4,0,0,0,0,0,0,0,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,0,0,0,0,255,255,255,255,5,0,0,0,0,0,0,0,255,255,255,25
08-26 17:54:42.385 I/Gecko   (  201): RIL Worker[0]: We have at least one complete parcel.
08-26 17:54:42.385 I/Gecko   (  201): RIL Worker[0]: Unsolicited response for request type 1010
08-26 17:54:42.385 I/Gecko   (  201): RIL Worker[0]: Handling parcel as UNSOLICITED_DATA_CALL_LIST_CHANGED
=========================================
According to comment #2 and comment #3, I think this issue was caused by modem does not handle this situation correctly.
Assignee: echen → nobody
Whiteboard: [FT:RIL]
Component: General → RIL
(In reply to Edgar Chen [:edgar][:echen] from comment #4)
> According to comment #2 and comment #3, I think this issue was caused by
> modem does not handle this situation correctly.

Agreed to minus this bug.
blocking-b2g: koi? → -
Hi Kevin,

As today's triage meeting we talked about how to process all modem related issues, I will change this to koi? again and mark it with [POVB]. Let's disscuss it in next triage meeting.
blocking-b2g: - → koi?
Whiteboard: [FT:RIL] → [FT:RIL, POVB]
Hi Ivan,

I will send out another mail to explain why I change owner of this issue to you. This is because it's partner image related issues, we would like to have your support to discuss this with partner later.
Assignee: nobody → itsay
Remove koi?. Since Wasabi is the old model from 2 years ago and currently not the official project for our partner, partner won't have timely support on this one. Partner said they can help on the issue analysis but won't be able to provide fix even the issue is identified in the vendor's build.
Assignee: itsay → nobody
blocking-b2g: koi? → ---
blocking-b2g: --- → -
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: