Aries Dogfood build 20151130 1. Power on the device. 2. Wait till an event that should be notified happens. 3. Notice sometimes: a) The lockscreen is opened and the notifications' icons are present. b) The lockscreen remains closed and no notifications show up, not even after unlocking the screen This issue is present for all kind of notifications (emails, Telegram, sms). Sometimes the notification sound is present, others it's not.
Gaby: When the next dogfood update comes up, can you check this again? I will also check on my dogfood phone to see if it can be reliably reproduced.
Marcia: Yes, I will! According to Naoki, we should have received an update these days but we didn't so he filed a bug related to the issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1239043
I updated to 20151230. I can still reproduce and it's even worse: sometimes I don't even get the notifications!
(In reply to Gabriela [:gaby2300] from comment #3) > I updated to 20151230. I can still reproduce and it's even worse: sometimes > I don't even get the notifications! Gaby: I think in order to be actionable we really need to know exactly which notifications you aren't getting - can you keep a log when it happens with which app (SMS, Telegram, etc)? I haven't seen any other reports of this happening consistently, but in order to get to the bottom of it we definitely need more information. Thanks!
The Telegram and Email app notifications have the same erratic behaviour: sometimes I get the notification sound, the homescreen wakes up and I notice the notification's icons. Other times there is no sound, the homescreen does not wake up but if I check, (pressing the on/off button) I see the notification icons in the homescreen. Other times I get no sound, the homescreen remains black and pressing the on/off button there's nothing even after receiving Telegram and/or email messages. Sometimes I can open the notifications directly from the locked homescreen, other times the notifications shows just a few seconds making it impossible to tap the icon to open the message. Maybe this is another issue? If so, please tell me so I'll file a new bug!
You need to log in before you can comment on or make changes to this bug.