Closed Bug 963467 Opened 10 years ago Closed 6 years ago

[DSDS][Fugu] setRadioEnabled wont return if we set outgoing call to SIM 2 and observe the radiochange event on SIM2 under airplane mode

Categories

(Firefox OS Graveyard :: Vendcom, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: eragonj, Assigned: sam.hua)

References

Details

(Whiteboard: [POVB][dsdsrun1.4-1])

Attachments

(4 files)

In airplane_mode.js, I tried to addEventListener on SIM2 (connection 2) to make sure we can finish the airplane flow as what we did when observing SIM1 (connection 1). But it's kinda weird that if we set outgoing call to SIM 2 (in simcard manager), turning on airplane mode and dial out an emergency call later.

After doing this, we can still hear the voice from the speaker but the whole UI got suspended and users can't do anything even we tap the home button. After asking Aknow about this case, it seems that modem doesn't respond the message back to finish the whole flow. 

We need to investigate why modem wont respond in this scenario and the whole UI got suspended.
Attached patch changes on gaiaSplinter Review
This is what I did in Gaia.
This bug is related to bug 962964 because I am writing the patch about it and found this problem.
Attachment #8364922 - Attachment mime type: text/x-log → text/plain
Attachment #8364923 - Attachment mime type: text/x-log → text/plain
Hi Sam,

From radio log, it seems that modem doesn't send back the response of "[0127]> RADIO_POWER (1)"
Do you know why?

01-24 16:07:57.257   965  1107 D RILC    : [w] [0020]> RADIO_POWER (0)
01-24 16:07:57.277   965  1107 D RILC    : [w] [0020]< RADIO_POWER
01-24 16:07:59.307   966  1104 D RILC    : [w] [0002]< RADIO_POWER
01-24 16:07:59.857   966  1106 D RILC    : [w] [0019]> RADIO_POWER (0)
01-24 16:07:59.877   966  1106 D RILC    : [w] [0019]< RADIO_POWER
01-24 16:08:00.977   966  1104 D RILC    : [w] [0029]> RADIO_POWER (1)
01-24 16:08:00.977   965  1103 D RILC    : [w] [0049]> RADIO_POWER (1)
01-24 16:08:03.487   966  1104 D RILC    : [w] [0029]< RADIO_POWER
01-24 16:08:06.635   965  1103 D RILC    : [w] [0049]< RADIO_POWER
01-24 16:08:36.763   965  1105 D RILC    : [w] [0114]> RADIO_POWER (0)
01-24 16:08:36.763   966  1108 D RILC    : [w] [0093]> RADIO_POWER (0)
01-24 16:08:38.253   966  1108 D RILC    : [w] [0093]< RADIO_POWER
01-24 16:08:38.253   965  1105 D RILC    : [w] [0114]< RADIO_POWER
01-24 16:10:00.633   966  1106 D RILC    : [w] [0106]> RADIO_POWER (1)
01-24 16:10:05.013   965  1107 D RILC    : [w] [0127]> RADIO_POWER (1)
01-24 16:10:05.103   966  1106 D RILC    : [w] [0106]< RADIO_POWER
Flags: needinfo?(sam.hua)
It looks like Channel1 crashed.

could it be reproduced?
Flags: needinfo?(sam.hua)
(In reply to sam.hua from comment #6)
> It looks like Channel1 crashed.
> 
> could it be reproduced?

Yes.

STR:
1) apply gaia patch: attachment 8364924 [details] [diff] [review]
2) go to Settings --> SIM Manager --> select sim2 for outgoing call
3) turn on airplane mode
4) go to dialer, dial out an emergency call

Expected result:
Radio of client2 is automatically turned on for making an emergency call. Later, radio of client1 is turned on as well.

Actual result:
Radio of client2 is automatically turned on for making an emergency call. But the UI hangs... and radio of client1 is NOT on eventually.
Hi Sam, can you reproduce this problem and fix this bug in rilc? Or what's your suggestion?
Flags: needinfo?(sam.hua)
nominate as 1.3+ because it's the blocker of 1.3+ bug 962380
blocking-b2g: --- → 1.3?
Hi,
now i am checking the problem:
https://bugzilla.mozilla.org/show_bug.cgi?id=946593 comment 51

i will try this one tomorrow.
Flags: needinfo?(sam.hua)
(In reply to sam.hua from comment #10)
> Hi,
> now i am checking the problem:
> https://bugzilla.mozilla.org/show_bug.cgi?id=946593 comment 51
> 

Sam,

Are you saying https://bugzilla.mozilla.org/show_bug.cgi?id=943215? 
I cannot find comment 51 on bug 946593 ;)

> i will try this one tomorrow.
Yes
https://bugzilla.mozilla.org/show_bug.cgi?id=943215

sorry for mistake.
(In reply to sam.hua from comment #12)
> Yes
> https://bugzilla.mozilla.org/show_bug.cgi?id=943215
> 
> sorry for mistake.

In case you are not aware, we opened bug 963054 for discussing the radio control issue you reported on bug 943215 comment 51. We got a root cause, see bug 963054 comment 4.
(In reply to Hsin-Yi Tsai (OOO Jan. 29 ~ Feb. 5th) [:hsinyi] from comment #13)
> (In reply to sam.hua from comment #12)
> > Yes
> > https://bugzilla.mozilla.org/show_bug.cgi?id=943215
> > 
> > sorry for mistake.
> 
> In case you are not aware, we opened bug 963054 for discussing the radio
> control issue you reported on bug 943215 comment 51. We got a root cause,
> see bug 963054 comment 4.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sorry, see bug 963054 comment 3. :)
Based on comment 9, nominate this bug to 1.3+. and per discussion thread here, the work will be on gecko RIL part.
blocking-b2g: 1.3? → 1.3+
Component: Gaia::Settings → RIL
Whiteboard: [ft:ril]
(In reply to Ivan Tsay (:ITsay) from comment #15)
> Based on comment 9, nominate this bug to 1.3+. and per discussion thread
> here, the work will be on gecko RIL part.
We haven't got any idea of the root cause yet. Seems something wrong with modem/rilc, and we are waiting for our partner's feedback.
Hi Sam,
I guess Hsin-Yi is expecting feedback. Please kindly reply.
Flags: needinfo?(sam.hua)
bug 964974 and bug 960706 are also linked to a setRadioEnabled request that won't return.
See Also: → 964974, 960706
PM reviewed: blocks
Seem like on partner side adding POVB
It looks like Sam is the best person to fix this bug, assign to Sam for now. 
Please unassign or reassign if you don't feel you are the right assginee. Thanks
Assignee: nobody → sam.hua
Whiteboard: [ft:ril] → [ft:ril][POVB]
Component: RIL → Vendcom
Should we remove the blocker bug since it's POVB?  We may want to add a milestone to be able to track this for 1.3.
(In reply to Chris Lee [:clee] from comment #21)
> Should we remove the blocker bug since it's POVB?  We may want to add a
> milestone to be able to track this for 1.3.

Yeah - let's do that.
blocking-b2g: 1.3+ → ---
Hi,
it can work,but there are another problem:

E/GeckoConsole(  107): [JavaScript Error: "A promise chain failed to handle a rejection.
E/GeckoConsole(  107): 
E/GeckoConsole(  107): Date: Mon Feb 24 2014 17:06:23 GMT+0800 (UTC)
E/GeckoConsole(  107): Full Message: TypeError: _timer is null
E/GeckoConsole(  107): Full Stack: ._createTimer@jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js:690
E/GeckoConsole(  107): ._handleMessage@jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js:662
E/GeckoConsole(  107): ._processNextMessage@jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js:572
E/GeckoConsole(  107): ._executeRequest@jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js:708
E/GeckoConsole(  107): ._handleMessage/<@jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js:659
E/GeckoConsole(  107): Handler.prototype.process@resource://gre/modules/Promise.jsm:767
E/GeckoConsole(  107): this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm:531
E/GeckoConsole(  107): " {file: "jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js" line: 690 column: 0 source: "690"}]
Flags: needinfo?(sam.hua)
Attached file test1.txt
the logs
Gecko build id: v1.3t
commit 983294139088ebd3aab14dfeb2a7fcf47f242009
Issue in Comment 23 will be resolved by Bug 974580
Hi Sam,

Do you have further update of this bug based on comment 26?
Flags: needinfo?(sam.hua)
Whiteboard: [ft:ril][POVB] → [ft:ril][POVB][dsdsrun1.4-1]
Hi Enpei,

no update
Flags: needinfo?(sam.hua)
Whiteboard: [ft:ril][POVB][dsdsrun1.4-1] → [POVB][dsdsrun1.4-1]
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

Created:
Updated:
Size: