Mozilla Build ID: 20140916000205 DEFECT DESCRIPTION: REPRODUCING PROCEDURES: Description: The device does not provide WAP Push message Inbox. WAP Push replacement is not working properly. 1. The device shows first WAP Push Service Indication containing CREATED-Attribute and ID in notification bar. # Reception of message is indicated visually and acoustically to the customer. Message rendered in a readable manner if the user select the notification, message is shown. 2. The device shows also Second WAP Push Service Indication containing CREATED-Attribute and ID. # Reception of WAP Push Service Indication is indicated visually and acoustically to the customer (shall not be indicated to the customer). 3. First received Service Indication have been replaced by second one. But if the user does not opens the first message both notification remains present in the notification bar if the user select first notification after getting the replacement popup appears that the message is expired and the user can open second message and open the link send to the device in the browser. 4. Messages will be deleted after closing the message. No option is available to view or use the service again. 5. WAP push Service Loading is working as WAP Push Service Indication. 6. MTR entries are filled with SoC: Does not Comply. But WAP-Push SI and SL is partially complies. Please add the message inbox and support the WAP-Push service properly. EXPECTED BEHAVIOUR: Please add the message inbox and support the WAP-Push service properly. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: Medium REPRODUCING RATE: 5/5 For FT PR, Please list reference mobile's behavior: Fire E 1.3 SW28C+ZZ10 is not ok.
From the description this is actually two bugs: - The one about replacement is bug 942080, please ask for approval to land the patch on 2.0 to fix that problem - The second issue about an inbox is bug 980843 and it's impossible to fix it in 2.0