Firefox OS v1.3 Mozilla build ID:20140422024003 DEFECT DESCRIPTION: REPRODUCING PROCEDURES: 1,Not store voice mail number before; 2.Received a voicemail from NOWSMS. 3.Pull down the notification bar then tap the voicemail icon,MS back idle.(ko) EXPECTED BEHAVIOUR: ->Should pop-up the set voicemail number message,then set it normal. ASSOCIATE SPECIFICATION: TEST PLAN REFERENCE: TOOLS AND PLATFORMS USED: USER IMPACT: REPRODUCING RATE: For FT PR, Please list reference mobile's behavior:

This issue is blocked by LATAM, please help to check. Thanks a lot!

(In reply to Mingming ZHAO from comment #1) > This issue is blocked by LATAM, please help to check. Thanks a lot! Hi Mingming - Please provide the logs for the voicemail packet. thanks

The adb logcat

Cert blocker for TEF in LATAM

Can you please show the screenshot for the notification? If it's a "real" voicemail notification, then it's handled by System. If it's a SMS notification, then it's handled by the SMS app.

Alexandre worked on voicemail stuff in the System app, so Cc him.

(In reply to sync-1 from comment #0) > Firefox OS v1.3 > Mozilla build ID:20140422024003 > > DEFECT DESCRIPTION: > > REPRODUCING PROCEDURES: > 1,Not store voice mail number before; > 2.Received a voicemail from NOWSMS. > 3.Pull down the notification bar then tap the voicemail icon,MS back > idle.(ko) > > EXPECTED BEHAVIOUR: > ->Should pop-up the set voicemail number message,then set it normal. > > ASSOCIATE SPECIFICATION: > > TEST PLAN REFERENCE: > > TOOLS AND PLATFORMS USED: > > USER IMPACT: > > REPRODUCING RATE: > > For FT PR, Please list reference mobile's behavior: I'm not sure to get the reported bug at 100%, but it smells a lot like bug 983459. This is fixed on v1.4 but it was marked as not affecting v1.3.

QA Wanted to check 1.3 latest.

I am unable to get to a state where the voice-mail notification doesn't call voice-mail, nor can I make it so the voicemail number is never set. This seems to happen as soon as the SIM is plugged in, and even when changing it to something else in Settings -> Call Settings it doesn't seem to make a difference. Also once I restart the device it is set back to normal again. Could we get some further clarification here? Device: Buri 1.3 BuildID: 20140619024031 Gaia: 5f4211ac94cc158a07269d0a0beca3c7937d78cc Gecko: 64c14d11b5cf Version: 28.0 (1.3) Firmware Version: v1.2device.cfg

(In reply to Julien Wajsberg [:julienw] (away June 21 to 30) from comment #5) > Can you please show the screenshot for the notification? > > If it's a "real" voicemail notification, then it's handled by System. > If it's a SMS notification, then it's handled by the SMS app. Hi, I used the "Now SMS" to send the voicemail. I think it should be a real voicemail.

(In reply to Mingming ZHAO from comment #10) > Created attachment 8444190 [details] > 2014-06-11-23-56-17.png > > (In reply to Julien Wajsberg [:julienw] (away June 21 to 30) from comment #5) > > Can you please show the screenshot for the notification? > > > > If it's a "real" voicemail notification, then it's handled by System. > > If it's a SMS notification, then it's handled by the SMS app. > > Hi, I used the "Now SMS" to send the voicemail. I think it should be a real > voicemail. Hi MingMing - Could you reproduce it on Buri as well? Thanks

(In reply to Alexandre LISSY :gerard-majax from comment #7) > > I'm not sure to get the reported bug at 100%, but it smells a lot like bug > 983459. This is fixed on v1.4 but it was marked as not affecting v1.3. Hi, I also think it is like the bug 983459. However the patch for the bug 983459 still has some problems. 1. Receive a voicemail then set the voicemail number in Settings, the voicemail notification still display "One new voicemial", not "Dial 123456". 2. Click the voicemail notification then the voicemial number is be dial out, but the voicemail notification does not disappear. 3. Receive two voicemail, it is display only one voicemial notification. (In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #11) > Hi MingMing - > > Could you reproduce it on Buri as well? > > Thanks Hi Vance, Yes it can reproduce on Buri, click the notification there is nothing happen, but the notification will disappear.

Can we land patch of Bug#983459 on 1.3?

(In reply to Mingming ZHAO from comment #12) > (In reply to Alexandre LISSY :gerard-majax from comment #7) > > > > I'm not sure to get the reported bug at 100%, but it smells a lot like bug > > 983459. This is fixed on v1.4 but it was marked as not affecting v1.3. > > Hi, I also think it is like the bug 983459. However the patch for the bug > 983459 still has some problems. Let's please explain what you think are issues. > > 1. Receive a voicemail then set the voicemail number in Settings, the > voicemail notification still display "One new voicemial", not "Dial 123456". You want the already sent notification to be updated when the Settings value changes ? That's not a minor change. > 2. Click the voicemail notification then the voicemial number is be dial > out, but the voicemail notification does not disappear. That is what we wanted when switching to the new Notification API: instead, voicemail notification will be removed when the carrier notifies us that there are no more voicemail. > 3. Receive two voicemail, it is display only one voicemial notification. Again, exactly what was requested to be implemented: we receive a new voicemail status change, we update the notification.

(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #13) > Can we land patch of Bug#983459 on 1.3? This bug was not even a 1.4+, and it depends on at least bug 985090, bug 985117 and bug 994262 to make sure that the behavior is correct. It also introduces new strings. According to the landing procedure https://wiki.mozilla.org/Release_Management/B2G_Landing#v1.3.0 we can probably get it in v1.3, but I'm unsure regarding strings.

(In reply to Alexandre LISSY :gerard-majax from comment #14) > (In reply to Mingming ZHAO from comment #12) > > (In reply to Alexandre LISSY :gerard-majax from comment #7) > > > > > > I'm not sure to get the reported bug at 100%, but it smells a lot like bug > > > 983459. This is fixed on v1.4 but it was marked as not affecting v1.3. > > > > Hi, I also think it is like the bug 983459. However the patch for the bug > > 983459 still has some problems. > > Let's please explain what you think are issues. > > > > > 1. Receive a voicemail then set the voicemail number in Settings, the > > voicemail notification still display "One new voicemial", not "Dial 123456". > > You want the already sent notification to be updated when the Settings value > changes ? That's not a minor change. > > > 2. Click the voicemail notification then the voicemial number is be dial > > out, but the voicemail notification does not disappear. > > That is what we wanted when switching to the new Notification API: instead, > voicemail notification will be removed when the carrier notifies us that > there are no more voicemail. > So the new Notification API is in 1.3? because in Buri 1.1, the voicemail notification will be removed once place a call to the voicemail number. > > 3. Receive two voicemail, it is display only one voicemial notification. > > Again, exactly what was requested to be implemented: we receive a new > voicemail status change, we update the notification. What our partner wants is if the device receive 2 voicemail notification from carrier, there should be two voicemail notifications in the pull-down status tray.

(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #16) [...] > > So the new Notification API is in 1.3? because in Buri 1.1, the voicemail > notification will be removed once place a call to the voicemail number. Yes. > > What our partner wants is if the device receive 2 voicemail notification > from carrier, there should be two voicemail notifications in the pull-down > status tray. Clearly not what was requested when we implemented the feature. And from my personnal point of view, it's very disturbing. And I don't remember of any device showing this behavior.

(In reply to Alexandre LISSY :gerard-majax from comment #17) > (In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #16) > > [...] > > > > > So the new Notification API is in 1.3? because in Buri 1.1, the voicemail > > notification will be removed once place a call to the voicemail number. > > Yes. > > > > > What our partner wants is if the device receive 2 voicemail notification > > from carrier, there should be two voicemail notifications in the pull-down > > status tray. > > Clearly not what was requested when we implemented the feature. And from my > personnal point of view, it's very disturbing. And I don't remember of any > device showing this behavior. Ya agree...i think a better ux design is to show the number of the unread voicemail in front of the voicemail notification. Something similar to what iOS does now. ni UX team to evaluate

(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #18) [...] > Ya agree...i think a better ux design is to show the number of the unread > voicemail in front of the voicemail notification. Something similar to what > iOS does now. ni UX team to evaluate This is already done. If the voicemail event coming from the Voicemail API does not contains a returnMessages, then we build a title that includes the number of unread messages. This is handled at https://github.com/mozilla-b2g/gaia/blob/5f4211ac94cc158a07269d0a0beca3c7937d78cc/apps/system/js/voicemail.js#L41 Given that we use the voicemailNotification tag, it should all be properly updated when message count changes.

(In reply to Alexandre LISSY :gerard-majax from comment #19) > (In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #18) > > [...] > > > Ya agree...i think a better ux design is to show the number of the unread > > voicemail in front of the voicemail notification. Something similar to what > > iOS does now. ni UX team to evaluate > > This is already done. If the voicemail event coming from the Voicemail API > does not contains a returnMessages, then we build a title that includes the > number of unread messages. > This is handled at > https://github.com/mozilla-b2g/gaia/blob/ > 5f4211ac94cc158a07269d0a0beca3c7937d78cc/apps/system/js/voicemail.js#L41 > > Given that we use the voicemailNotification tag, it should all be properly > updated when message count changes. Cool...so it is in since 1.4?

(In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #20) > (In reply to Alexandre LISSY :gerard-majax from comment #19) > > (In reply to Vance Chen [:vchen][vchen@mozilla.com] from comment #18) > > > > [...] > > > > > Ya agree...i think a better ux design is to show the number of the unread > > > voicemail in front of the voicemail notification. Something similar to what > > > iOS does now. ni UX team to evaluate > > > > This is already done. If the voicemail event coming from the Voicemail API > > does not contains a returnMessages, then we build a title that includes the > > number of unread messages. > > This is handled at > > https://github.com/mozilla-b2g/gaia/blob/ > > 5f4211ac94cc158a07269d0a0beca3c7937d78cc/apps/system/js/voicemail.js#L41 > > > > Given that we use the voicemailNotification tag, it should all be properly > > updated when message count changes. > > Cool...so it is in since 1.4? This is in v1.3

So what's the deal with this? Do we still uplift or this is obsolete because it's in 1.4? Please advice, I don't want open bugs sitting in our queue unassigned. Thanks!

After discussing with partner, we don't need to uplift this one in 1.3. Issue close as won't fix. Thanks