Closed Bug 1040566 Opened 11 years ago Closed 11 years ago

[UICC][STK] GET_INKEY, GET_INPUT timeout duration doesn't work

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:2.0+, b2g-v1.3 wontfix, b2g-v1.3T wontfix, b2g-v1.4 wontfix, b2g-v2.0 fixed, b2g-v2.1 fixed)

RESOLVED FIXED
blocking-b2g 2.0+
Tracking Status
b2g-v1.3 --- wontfix
b2g-v1.3T --- wontfix
b2g-v1.4 --- wontfix
b2g-v2.0 --- fixed
b2g-v2.1 --- fixed

People

(Reporter: jjoons79, Assigned: promise09th)

References

Details

Attachments

(1 file)

- User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; CNS_UA; AD_LOGON=4C47452E4E4554) - Steps to reproduce: Process SimToolkit Command (GET_INKEY, GET_INPUT). - Actual results: time duration is not working. - When processing GET_INKEY, GET_INPUT command, time duration didn't set normally. I think time duration value have to set below. (icc_work.js, icc.js) Please check source icc_worker.js, icc.js 1. icc_worker.js [Before] var timeout = (options.duration && icc.calculateDurationInMS(options.duration)) || icc._inputTimeout; [After] var timeout = (options.duration && icc.calculateDurationInMS(options.duration.timeUnit, options.duration.timeInterval)) || icc._inputTimeout; ========================================================================== icc.js [Before] calculateDurationInMS: function icc_calculateDurationInMS(timeUnit, timeInterval) { var timeout = timeInterval; switch (timeUnit) { case this._iccManager.STK_TIME_UNIT_MINUTE: timeout *= 360000; break; [After] case this._iccManager.STK_TIME_UNIT_MINUTE: timeout *= 60000;
Please review the patch.
Flags: needinfo?(wchang)
Attached file Bug_1040566_patch.html
ni?frsela Fernando, do you still review STK code?
Flags: needinfo?(wchang) → needinfo?(frsela)
Comment on attachment 8458516 [details] Bug_1040566_patch.html Thank you !
Attachment #8458516 - Flags: review+
Flags: needinfo?(frsela)
Nominating this for 2.0 as partner needs this fixed on their product. According to comment 0 it's a trivial bug that needs fixing, without the fix it might impact STK cert testing.
blocking-b2g: --- → 2.0?
blocking-b2g: 2.0? → 2.0+
Assignee: nobody → promise09th
Unable to verify this issue because it is a backend issue.
QA Whiteboard: [QAnalyst-verify-][QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-verify-][QAnalyst-Triage?] → [QAnalyst-verify-][QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: