SW12A AU_LINUX_GECKO_ICS_STRAWBERRY_V1.01.00.01.019.105 Firefox os v1.0.1 Mozilla build ID:20130512070209 +++ This bug was initially created as a clone of Bug #455656 +++ DEFECT DESCRIPTION: [GCF][STK]case 27.22.4.1.1/2 (DISPLAY TEXT normal priority, Unpacked 8 bit data for Text String, screen busy) REPRODUCING PROCEDURES: 1 run GCF case 27.22.4.1.1/2 (DISPLAY TEXT normal priority, Unpacked 8 bit data for Text String, screen busy) 2 after send display text command,return TR is wrong-->KO. EXPECTED BEHAVIOUR: return TR should with Result General Result: Terminal currently unable to process command Additional information: Screen is busy Coding: BER-TLV: 81 03 01 21 80 82 02 82 81 83 02 20 01 ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior: ++++++++++ end of initial bug #455656 description ++++++++++ CONTACT INFO (Name,Phone number): DEFECT DESCRIPTION: REPRODUCING PROCEDURES: EXPECTED BEHAVIOUR: ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:

Can you provide more information? For example logcat traces (with Gaia STK DEBUG level enabled as explained in https://bugzilla.mozilla.org/show_bug.cgi?id=873906#c6) With that log I can try to reproduce it in my device

Hey Fernando, This looks to be a GCF TC. The description in the 3GPP TS 51.010-4 says this in the first step: - The ME will be set to a mode so that normal priority text commands shall be rejected. After this, the remaining steps just send a DISPLAY_TEXT like any other text with normal priority. I'm not sure what state the device has to be such that a "normal priority text" would be rejected. I assumed that if I was in a phone call (dialer app launched with a connected call), that the text would be rejected. However, in this case, I do a DISPLAY_TEXT come to screen. PDU used: D01A8103012180820281028D0F04546F6F6C6B697420546573742031 Thoughts on this?

this is the log with gaia debug flag true

You're giving me more reasons to move main of the STK code to system instead settings since settings didn't care about other apps status. To fix this bug we should refactor main of the STK code, probably for leo release we can work on this.

This cannot be fixed in time for 1.0.1, I'd suggest we do it for leo

Comment from Mozilla:This cannot be fixed in time for 1.0.1, I'd suggest we do it for leo

Blocking based on allowing it to be pushed out from v1.0.1 to v1.1 for GCF.

Based con Carol's comment #2 we need to define the priorities. My suggestion is to use an Attention Screen but with less priority than the current one used to receive calls. Anyway, other priorities can be defined (some apps like dialer or sms has more priority than STK?) These priorities should be defined by UX team.

We're actually going to not block on this, since it didn't block the previous release and will require new UX.

Can you retest this with last release? It's supposed to be fixed. Thanks

4 months without feedback. If continues failing, Reopen it.