Closed
Bug 894271
Opened 11 years ago
Closed 10 years ago
[Buri][SMS]When enable 'Delivery reports',after sent message successfully,can not see the report
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Firefox OS Graveyard
Gaia::SMS
Tracking
(tracking-b2g:backlog)
RESOLVED
WORKSFORME
tracking-b2g | backlog |
People
(Reporter: sync-1, Unassigned)
References
Details
Attachments
(1 file)
306.11 KB,
image/jpeg
|
Details |
SW171 AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.152 Firefox os v1.1 Mozilla build ID:20130702230206 DEFECT DESCRIPTION: When enable 'Delivery reports' in message settings,after sent message successfully,can not see any report. REPRODUCING PROCEDURES: 1.Enter Settings-->Celluar&Data-->message settings-->enable 'Delivery reports'-->tap 'OK' 2.Use unicom SIM card to send a message -->when the message received well-->can not pop up report and have no way to view the report.--KO EXPECTED BEHAVIOUR: Should pop up or give the way to view the delivery report 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:
Comment 1•11 years ago
|
||
FFOS does support handling delivery report for SMS only. The receiver's phone should also be capable of sending the delivery report back. Need to make sure this feature is indeed available and enabled on the receiver's end.
Comment 2•11 years ago
|
||
Is this a regression from v1.0.1? Adding regressionwindow-wanted to see if we're able to reproduce, and identify the regressing bug.
Keywords: regressionwindow-wanted
Comment 3•11 years ago
|
||
V1.0.1 doesn't support delivery report for SMS or MMS. It's only available on V1.1 for SMS and going to be supported on V1.2 for MMS.
Comment 4•11 years ago
|
||
Switching to qawanted - is this reproduced the delivery report seen with SMS messages on the latest v1-train build? If this is MMS-related, then per comment 3, this is not a 1.1 feature.
Keywords: regressionwindow-wanted → qawanted
Comment 5•11 years ago
|
||
No delivery reports when sending an SMS on Buri running 7/19 v1-train build Build ID: 20130719070225 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/6b6e80e9aaf0 Gaia: ce5a75acd4ad6cd0d53dad77c058a0f1002f98b1 Platform Version: 18.1 RIL Version: 01.01.00.019.164 *have used AT@T SIM card
Keywords: qawanted
Comment 6•11 years ago
|
||
(In reply to nkot from comment #5) > No delivery reports when sending an SMS on Buri running 7/19 v1-train build > > Build ID: 20130719070225 > Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/6b6e80e9aaf0 > Gaia: ce5a75acd4ad6cd0d53dad77c058a0f1002f98b1 > Platform Version: 18.1 > RIL Version: 01.01.00.019.164 > > *have used AT@T SIM card Do you notice the "tick" icon? That would be the delivery report. If this is not showing anymore then this would be a regression.
Flags: needinfo?(nkot)
Comment 7•11 years ago
|
||
(In reply to Wayne Chang [:wchang] from comment #6) > Do you notice the "tick" icon? That would be the delivery report. > If this is not showing anymore then this would be a regression. currently v1.1. is supposed to support 1. send/receive MMS 2. delivery reports for SMS at our region we are unable to send/receive MMS, that makes me think that delivery reports might not be available for us as well.. I have not seen it neither on latest 7/22 build nor on older builds from 5/09 when the feature was just implemented I think it would be the best if someone who has the ability to send/receive MMS will address the "qawanted" request from comment 4
Keywords: qawanted
Updated•11 years ago
|
Flags: needinfo?(nkot)
Comment 8•11 years ago
|
||
Comment 9•11 years ago
|
||
Verified by pvt build Gaia: f851c8834688d8d960562ec55253dd44051929cd B-D 2013-07-16 10:48:05 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/034825df3f19 BuildID 20130715230201 Version 18.0 both on buri and leo is ok.
Updated•11 years ago
|
blocking-b2g: leo? → -
Comment 10•11 years ago
|
||
(In reply to Paul Yang: pyang: pyang@mozilla.com from comment #9) > Verified by pvt build > Gaia: f851c8834688d8d960562ec55253dd44051929cd > B-D 2013-07-16 10:48:05 > Gecko: > http://hg.mozilla.org/releases/mozilla-b2g18_v1_1_0_hd/rev/034825df3f19 > BuildID 20130715230201 > Version 18.0 > > both on buri and leo is ok. However, short message with a illegal number like "123" also is dealt with as the legal number. It display a green 'tick' icon which shouldn't. Compare with other system, it's unreasonable.
Comment 11•11 years ago
|
||
(In reply to 田旻 from comment #10) > > However, short message with a illegal number like "123" also is dealt with > as the legal number. It display a green 'tick' icon which shouldn't. > Compare with other system, it's unreasonable. Just make sure we are sync-ed. 1. Does this bug can't be reproduced? Is it verified ok with latest build? 2. Using the same build and perform the steps in #10 , 123 is invalid in TW so the message is failed to send. Please provide environment/more steps, thanks.
Comment 12•11 years ago
|
||
Then I will update to the new version(Mozilla build ID:20130715070218) and have a try.
Comment 13•11 years ago
|
||
(In reply to Paul Yang: pyang: pyang@mozilla.com from comment #11) > (In reply to 田旻 from comment #10) > > > > However, short message with a illegal number like "123" also is dealt with > > as the legal number. It display a green 'tick' icon which shouldn't. > > Compare with other system, it's unreasonable. > > Just make sure we are sync-ed. > 1. Does this bug can't be reproduced? Is it verified ok with latest build? > 2. Using the same build and perform the steps in #10 , 123 is invalid in TW > so the message is failed to send. Please provide environment/more steps, > thanks. After I update my system to the new version(Mozilla build ID:20130715070218), I found the problem still exist. Invalid number can be send correctly and display a 'tick' icon as success.
Comment 14•11 years ago
|
||
Which phone number are you using? "123" again?
Comment 15•11 years ago
|
||
The original bug "When enable 'Delivery reports',after sent message successfully,can not see the report" seems not to reproduce. For the other one, just flash today's build (20130724205326) Here is the number I tried (delivery report is enabled, tw environment, fartone sim car): 123: pop up a screen says service unavailable, message sent fail. 095556: the same as above alphabet sequence: the same as above 133: message sent but NO delivery report 09xxxxxx(a valid number): message sent and get delivery report successfully.
Comment 16•11 years ago
|
||
We don't have that version now, but I will keep follow this problem and test it on the version you mentioned.
Koi has ui for the setting of this. We should get the confirmation working if we're going to have ui for it.
blocking-b2g: - → koi?
Comment 18•11 years ago
|
||
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #17) > Koi has ui for the setting of this. We should get the confirmation working > if we're going to have ui for it. OK.
Updated•11 years ago
|
Updated•11 years ago
|
Assignee: evelyn → nobody
Comment 20•11 years ago
|
||
The delivery report can work now, even if a invalid number is inputted.
Comment 21•11 years ago
|
||
Does it mean we can close this bug?
Updated•10 years ago
|
blocking-b2g: --- → backlog
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•