Closed
Bug 1003745
Opened 10 years ago
Closed 10 years ago
[B2G] [RIL] [Tarako] get the right fail cause for a call after REQUEST_DIAL fails
Categories
(Firefox OS Graveyard :: RIL, defect)
Tracking
(blocking-b2g:1.3T+, b2g-v1.3T fixed, b2g-v2.0 unaffected)
Tracking | Status | |
---|---|---|
b2g-v1.3T | --- | fixed |
b2g-v2.0 | --- | unaffected |
People
(Reporter: hsinyi, Assigned: aknow)
References
Details
(Whiteboard: [p=2])
Attachments
(1 file, 1 obsolete file)
1.06 KB,
patch
|
aknow
:
review+
|
Details | Diff | Splinter Review |
This is valid for only v1.3T. We simply assign "UnspecifiedError" to fail cause for a call after REQUEST_DIAL fails but this is not correct. We should check if a pendingMO call has been hung up before. 1) If yes, assign the fail cause manually. 2) If not, go query GET_LAST_FAIL_CAUSE_CODE.
Reporter | ||
Comment 1•10 years ago
|
||
nominate 1.3T+ because it blocks another 1.3T+ bug 1001729.
Assignee | ||
Comment 3•10 years ago
|
||
The case of hanging up pending call is handled in hangUp(). Then it just do nothing in REQUEST_DIAL handler => _removePendingOutgoingCall().
Attachment #8415126 -
Flags: review?(htsai)
Reporter | ||
Comment 4•10 years ago
|
||
Comment on attachment 8415126 [details] [diff] [review] Get correct fail cause Review of attachment 8415126 [details] [diff] [review]: ----------------------------------------------------------------- Thank you :) ::: dom/system/gonk/ril_worker.js @@ +5254,5 @@ > }; > RilObject.prototype[REQUEST_DIAL] = function REQUEST_DIAL(length, options) { > // We already return a successful response before. Don't respond it again! > if (options.rilRequestError) { > options.callIndex = -1; Please remove this as it's useless.
Attachment #8415126 -
Flags: review?(htsai) → review+
Assignee | ||
Comment 5•10 years ago
|
||
Attachment #8415126 -
Attachment is obsolete: true
Attachment #8415156 -
Flags: review+
Updated•10 years ago
|
Flags: needinfo?(mhenretty)
Keywords: checkin-needed
Updated•10 years ago
|
Flags: needinfo?(mhenretty)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S1 (9may)
Assignee | ||
Updated•10 years ago
|
Whiteboard: [p=2]
You need to log in
before you can comment on or make changes to this bug.
Description
•