Closed Bug 1117705 Opened 10 years ago Closed 10 years ago

[FFOS7715 v2.1][STK]USAT case 27.22.7.5.1 USER ACTIVITY EVENT SEQ 1.1 fail，Press any key，no ENVELOPE EVENT DOWNLOAD -USER ACTIVITY

Categories

(Firefox OS Graveyard :: RIL, defect)

Product:
Firefox OS Graveyard
Component:
RIL
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(b2g-v1.4 wontfix, b2g-v2.0 wontfix, b2g-v2.0M affected, b2g-v2.1 affected, b2g-v2.2 affected)

Status:
RESOLVED DUPLICATE of bug 1126687
Tracking Flags:
Tracking Status
b2g-v1.4 --- wontfix
b2g-v2.0 --- wontfix
b2g-v2.0M --- affected
b2g-v2.1 --- affected
b2g-v2.2 --- affected

People

(Reporter: Jinghua.Xing, Assigned: Jinghua.Xing)

References

Details

(Whiteboard: [sprd390814])

Attachments

(1 file)

stk_event.patch
(deleted), patch
edgar
: feedback+
Details | Diff | Splinter Review
[Testing Steps ]:USAT case 27.22.7.5.1 USER ACTIVITY EVENT SEQ 1.1 EVENT DOWNLOAD -USER ACTIVITY [Expected Result ]:case pass [Test Result ]:Press any key，no ENVELOPE EVENT DOWNLOAD -USER ACTIVITY
Whiteboard: [sprd390814]
In 3GPP TS 51.010-4 Case request return： D6 07 19 01 04 82 02 82 81 Truly return: D6 07 82 02 82 81 99 01 04 But in ETSI TS 101 267, it also say the Event list tag can be 99 or 19. What should we do with this case?
And does the difference between the tags' order of the truly returned and the requested can cause the case failed?
Flags: needinfo?(sku)
As in the protocol ETSI TS 101 267, in the ENVELOPE EVENT DOWNLOAD returned, the Event list tag should be placed before the Device identities tag. Do I understand this right?
Flags: needinfo?(frsela)
Attached patch stk_event.patch (deleted) — — Splinter Review
I have made a patch for this issue. Can you help me review it? Thank you.
Attachment #8544439 - Flags: review?(frsela)
Comment on attachment 8544439 [details] [diff] [review] stk_event.patch Review of attachment 8544439 [details] [diff] [review]: ----------------------------------------------------------------- Change to proper owner for review.
Attachment #8544439 - Flags: review?(frsela) → review?(echen)
Hi Jinghua: After checking 3GPP TS 11.14, event list should come before device identities (see section 11). But for tag part, both 19 or 99 are okay for Event list tag. Hence, I think you patch should be able to work properly. Hi Edgar, Since this involves the change in ril_worker.js, could you please help review it?
Flags: needinfo?(sku)
Change to proper component.
Component: Gaia → RIL
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
(In reply to shawn ku [:sku] (OOO 01/06 ~ 01/09) from comment #6) > Hi Jinghua: > After checking 3GPP TS 11.14, event list should come before device > identities (see section 11). > But for tag part, both 19 or 99 are okay for Event list tag. > > Hence, I think you patch should be able to work properly. > > > Hi Edgar, > Since this involves the change in ril_worker.js, could you please help > review it? Sure I will take a look. Thank you.
Flags: needinfo?(frsela)
Blocks: b2g-stk
Comment on attachment 8544439 [details] [diff] [review] stk_event.patch Review of attachment 8544439 [details] [diff] [review]: ----------------------------------------------------------------- Patch looks good, but please help to generate a HG patch by following below link, https://developer.mozilla.org/en-US/docs/Mercurial_FAQ#How_can_I_generate_a_patch_for_somebody_else_to_check-in_for_me.3F Thank you. :)
Attachment #8544439 - Flags: review?(echen) → feedback+
Hi Jinghua, I assume you will handle this bug, otherwise please feel free to kick back to me, thank you.
Assignee: nobody → Jinghua.Xing
Blocks: 1123554
Status: NEW → ASSIGNED
Status: ASSIGNED → 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: