Closed Bug 870253 Opened 12 years ago Closed 11 years ago

[Buri][IOT]The DuT does not resume the PDP context after to hung up the call.

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-)

RESOLVED FIXED
1.0.1 IOT1 (10may)
blocking-b2g -

People

(Reporter: sync-1, Assigned: pgravel)

Details

(Whiteboard: Chile, IOT, buri)

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #451185 +++ DEFECT DESCRIPTION: The DuT does not resume the PDP context after to hung up the call when the ""USB tethering"" option is currently used. EXPECTED BEHAVIOUR: The dial-up PDP context must remain active after to receive an incoming voice call. REPRODUCING PROCEDURES: DuT in 2G only in the ""Network type"" menu 1. Connect the DuT to PC via USB. 2. Activate the option ""USB tethering"" and start a file downloading through a FTP server. 3. Wait until the download has been started. 4. Enable the firewall in the PC and notice that the traffic is stopped. 5. From another terminal establish a voice call to DuT. 6. Disable the firewall in the PC and wait 10 minutes. 7. Hung up the call and verify that the PDPc remains active. 8. Notice that is not possible navigate from the DuT nor PC." ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: 100% For FT PR, Please list reference mobile's behavior: AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.092 Firefox os v1.0.1 Mozilla build ID:20130430070201 ++++++++++ end of initial bug #451185 description ++++++++++ CONTACT INFO (Name,Phone number): DEFECT DESCRIPTION: REPRODUCING PROCEDURES: EXPECTED BEHAVIOUR: ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:
blocking-b2g: --- → tef?
Assignee: nobody → echen
triage with tef: tef+. this is a blocker. please provide logs. thanks
blocking-b2g: tef? → tef+
Flags: needinfo?(sync-1)
bugs tef+ from IOT#1 automatically milestoned for May 10th to be included in IOT#2 testing. Understand the schedule is tight, if not able to make it, please raise. Thanks
Target Milestone: --- → 1.0.1 IOT1 (10may)
QAWANTED to help confirming this. thanks b
Keywords: qawanted
during the triage, might have missed to look into the detailed reproduce steps with tef. Upon a second look, with such a complicated reproduce steps, i'd like to re-triage this one
blocking-b2g: tef+ → tef?
This has not been reported as blocker in the certification process, I think we should minus it. If the reporter increase the priority and provide logs of the issue we can investigate it further.
Whiteboard: Poland, IOT, Buri
per comment 5, tef-. Thanks Beatriz
blocking-b2g: tef? → -
Whiteboard: Poland, IOT, Buri → Chile, IOT, buri
Created an attachment (id=409076) ADB LOGS PDP CONTEXT DEACTIVATED
Flags: needinfo?(sync-1)
Created an attachment (id=409076) ADB LOGS PDP CONTEXT DEACTIVATED
I cannot reproduce this on my unagi device. Gaia: de0f1fc6 Gecko: dd0500910 QC-RIL: AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.092 My steps: 1. Set network to "2G only". (Setting->Cellular & Data->Network operator->Network type). 2. Connect DuT to PC via USB. 3. Enable Usb tehtering. 4. Start ping 8.8.8.8 on PC. 5. Initiate voice call from another device. 6. Wait few minutes. 7. Hung up the call. 8. Check the ping on PC is resumed. 9. Try to browse on device. Could you capture bugreport when issue occurred? Maybe we could find some clues from the bugreport. You can get bugreport by 'adb bugreport > bugreport.txt'. (It takes few seconds to dump all status) Thanks
Reporter feedback: By the way, to reproduce the issue on my side you have to be on the call more than 10 minutes, then hang off call, I was wondering if is there any timer on device in order to sent RESUME (allow data connection again), I mean, meybe after "suspend" connection because of the MTC mobile is not able to "resume" after 5 minutes....check if there is any setting like this. Could you please try, whether you can reproduce? bugreport will come later. (In reply to Edgar Chen [:edgar][:echen] from comment #9) > I cannot reproduce this on my unagi device. > Gaia: de0f1fc6 > Gecko: dd0500910 > QC-RIL: AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.092 > > My steps: > 1. Set network to "2G only". (Setting->Cellular & Data->Network > operator->Network type). > 2. Connect DuT to PC via USB. > 3. Enable Usb tehtering. > 4. Start ping 8.8.8.8 on PC. > 5. Initiate voice call from another device. > 6. Wait few minutes. > 7. Hung up the call. > 8. Check the ping on PC is resumed. > 9. Try to browse on device. > > Could you capture bugreport when issue occurred? > Maybe we could find some clues from the bugreport. > You can get bugreport by 'adb bugreport > bugreport.txt'. (It takes few > seconds to dump all status) > > Thanks
(In reply to Amelie Kong from comment #10) > Reporter feedback: > > By the way, to reproduce the issue on my side you have to be on the call more > than 10 minutes, then hang off call, I was wondering if is there any timer on > device in order to sent RESUME (allow data connection again), I mean, meybe > after "suspend" connection because of the MTC mobile is not able to "resume" > after 5 minutes....check if there is any setting like this. Hi Anshul, Do you have any input about above description? Thanks > > Could you please try, whether you can reproduce? Sure, I will try to reproduce on my side with > 10 minutes. Thanks > bugreport will come later.
Flags: needinfo?(anshulj)
Phil, please have a look.
Flags: needinfo?(anshulj) → needinfo?(pgravel)
Oh, I can reproduce the same symptom, not able to access network, after on call more than 10 minutes. No connection drop reported and routing/interface is good. It seems modem did not "RESUME" data connection successfully. Thanks.
I have reproduced the issue and am looking further into the root cause.
Flags: needinfo?(pgravel)
Hi Phil, I will change the assignee to you. Please help on this. Thanks!
Assignee: echen → pgravel
As it can be reproduced, I mark tef? again.
blocking-b2g: - → tef?
(In reply to Edgar Chen [:edgar][:echen] from comment #13) > Oh, I can reproduce the same symptom, not able to access network, after on > call more than 10 minutes. > No connection drop reported and routing/interface is good. It seems modem > did not "RESUME" data connection successfully. > Thanks. seem like the reproduce step is as easy as making a call for 10+ minutes
Sounds like this is reproducible then. I'll pull the keyword as such.
Keywords: qawanted
David, with the latest comments about how to reproduce this, should it become a blocker?
Flags: needinfo?(dpv)
checked on buri partner build dated May 15th. cannot reproduce comment 13. comment 13 only reproducible on unagi
For us, if it is possible to establish a new connection after finishing voice call (not resuming the previous one), then it'd not be blocking. After voice call during 10 minutes, it's not extrange that data connection would not be not resumed. It could be also affected by some network issues. Usual requirement is the device to be able to resume connectivity after *1-minute* voice call ongoing. Thanks! David
Flags: needinfo?(dpv)
blocking-b2g: tef? → -
dears any feedback?
This issue should be resolved in AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.136 or later.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: