914469 - [Buri][Shira-51603]'The DUT opens the SMS client after recieving OTA-Message.

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia::SMS, defect, P2)

Description

[sync-1]

Mozilla build ID:20130902041201
 DEFECT DESCRIPTION:
 After performing the SAT-Menu update, no OTA-Message is shown by the device instead it is opening the SMS(Messaging) client. It seems that the DUT recievs the OTA message from the server but not able to differentiat SMS,MMS or OTA-Message.
 
  REPRODUCING PROCEDURES:
 
 Steps to reproduce:
 - Insert  SIM D-N2 or D-V3 into the mobile and power on MS.
 - Verify that the SIM SAT (SIM Application Toolkit) services menu item is available at the device menu
 - Select the SIM SAT menu item
 - Update the SAT-Menu
 Select "Extras" from "Special" Menu.
 "Men

Comment 1

[Julien Wajsberg [:julienw]]

Fernando, is it a STK problem ?

Comment 2

[Fernando R. Sela (no CC, needinfo please) [:frsela]]

(In reply to Julien Wajsberg [:julienw] from comment #1)
> Fernando, is it a STK problem ?

Apparently no, since OTA is independent of STK. STK is used to launch the OTA process (probably, sending a message)

Anyway, can you share log traces to check STK commands?

Thanks in advance.

Comment 3

[Julien Wajsberg [:julienw]]

please see comment 2

Comment 4

[Joe Cheng [:jcheng] (please needinfo)]

not in partner blocker list. koi? for consideration in v1.2

Comment 5

[Joe Cheng [:jcheng] (please needinfo)]

ni? reporter
minus for now before we get more information

Comment 6

[Julien Wajsberg [:julienw]]

Gabriele, Do you know if what we call "OTA" here is a wappush message?

Comment 7

[Gabriele Svelto [:gsvelto]]

We usually use the OTA acronym for over-the-air updates but I don't think this is the case here. I have a hard time understanding what is going on from the STR in comment 0 and to figure out if a WAP Push message is involved or not. We need at least a logcat and a way to reproduce on our devices.

Comment 8

[Julien Wajsberg [:julienw]]

Ok, since there is no partner activity on it since some months, I'll close this bug.

Please reopen with more information or file a new bug if necessary.