Closed Bug 1117661 Opened 10 years ago Closed 10 years ago

[FFOS7715 v2.1][STK] USAT case 27.22.4.3.5 GET INPUT SEQ 5.2, TR with wrong length is responded.

Categories

(Firefox OS Graveyard :: Gaia, defect)

x86_64
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1123204

People

(Reporter: Jinghua.Xing, Unassigned)

Details

(Whiteboard: [sprd390573])

Attachments

(2 files)

[Testing Steps ]:USAT case 27.22.4.3.5 GET INPUT SEQ 5.2 GET INPUT, default text for the input with max length, successful [Expected Result ]:case pass [Test Result ]:Display the input interface but when clicking OK, return to idle but no TERMINAL RESPONSE returned.
Summary: [FFOS7715_v2.1]USAT case 27.22.4.3.5 GET INPUT SEQ 5.2,display the input interface but no TR returned when clicking OK → [FFOS7715 v2.1][STK]USAT case 27.22.4.3.5 GET INPUT SEQ 5.2,display the input interface but no TR returned when clicking OK
Whiteboard: [sprd390573]
Ni Shawn to find proper people to check this one
Flags: needinfo?(sku)
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/icc.js#L677 should reply the TR already. Could you please help provide device/radio log for us to check?
Flags: needinfo?(sku) → needinfo?(Jinghua.Xing)
this issue is a little trouble, pls jinghua have a quick prepare
Severity: normal → critical
Flags: needinfo?(Jinghua.Xing)
Xianmao: Please help to handle this. Thank you.
Attached file device log (deleted) —
Attached file radio (deleted) —
Hi shawn, I have checked log and USAT case 27.22.4.3.5 GET INPUT SEQ 5.2 GET INPUT, I found our gecko sends a TR, but it lack of one hexOctet as the test case required. our gecko TR: 81 03 01 23 00 02 02 82 81 83 01 00 8D A1 04 2A 2A 2A 31 31 31 31 31 31 31 31 31 31 23 23 23 2A 2A 2A 32 32 32 32 32 32 32 32 32 32 23 23 23 2A 2A 2A 33 33 33 33 33 33 33 33 33 33 23 23 23 2A 2A 2A 34 34 34 34 34 34 34 34 34 34 23 23 23 2A 2A 2A 35 35 35 35 35 35 35 35 35 35 23 23 23 2A 2A 2A 36 36 36 36 36 36 36 36 36 36 23 23 23 2A 2A 2A 37 37 37 37 37 37 37 37 37 37 23 23 23 2A 2A 2A 38 38 38 38 38 38 38 38 38 38 23 23 23 2A 2A 2A 39 39 39 39 39 39 39 39 39 39 23 23 23 2A 2A 2A 30 30 30 30 30 30 30 30 30 30 23 23 23 test case required TR: 81 03 01 23 00 82 02 82 81 83 01 00 8D 81 A1 04 2A 2A 2A 31 31 31 31 31 31 31 31 31 31 23 23 23 2A 2A 2A 32 32 32 32 32 32 32 32 32 32 23 23 23 2A 2A 2A 33 33 33 33 33 33 33 33 33 33 23 23 23 2A 2A 2A 34 34 34 34 34 34 34 34 34 34 23 23 23 2A 2A 2A 35 35 35 35 35 35 35 35 35 35 23 23 23 2A 2A 2A 36 36 36 36 36 36 36 36 36 36 23 23 23 2A 2A 2A 37 37 37 37 37 37 37 37 37 37 23 23 23 2A 2A 2A 38 38 38 38 38 38 38 38 38 38 23 23 23 2A 2A 2A 39 39 39 39 39 39 39 39 39 39 23 23 23 2A 2A 2A 30 30 30 30 30 30 30 30 30 30 23 23 23 Our gecko TR is lack of "81" in the black space of TR, but I do not know what it means. Please help check! Thanks!
Flags: needinfo?(sku)
Hi shawn, I found the following detail in protocol, The length is coded onto 1 or 2 bytes according to TS 101 220 [31] Length Byte 1 Byte 2 0-127 length ('00' to '7F') not present 128-255 '81' length ('80' to 'FF') As the current length is 161(0xA1),we should use 2 bytes to code the length,but our TR does not has such process. Please help check. Thanks!
Flags: needinfo?(sku)
Summary: [FFOS7715 v2.1][STK]USAT case 27.22.4.3.5 GET INPUT SEQ 5.2,display the input interface but no TR returned when clicking OK → [FFOS7715 v2.1][STK] USAT case 27.22.4.3.5 GET INPUT SEQ 5.2, TR with wrong length is responded.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: