Update (April 16):
One of the moderators on the relevant thread on the company’s official European help forum recently said
I confirm that the symptom occurs randomly on some S9 / S9 +, but not on all. Samsung has already planned to release a resolutive update as soon as possible. We recommend constantly checking for new updates via OTA or via Smart Switch.
Original story:
As if the widely reported call dropping issue on Galaxy S9 wasn’t enough, users of S9+ are now complaining of not receiving missed call notifications as well.
A significant number of Galaxy S9+ users across the company’s official European help forum, XDA, Reddit, and other help forums have been chiming about their device not notifying/alerting for the unanswered calls. As a result, users don’t even realise that they missed any calls, unless they check the call log.
Take a quick look at how those affected explain the problem in question:
On my dual SIM s9+ I seem to be experiencing a weird bug with missed call notifications. Quite often no notification are shown for not answered calls. I only realize that there was a missed call when I open the phone app. I was not able to identify any clear pattern that leads to a bug but close to 50% of missed calls on my device do not result in a notification in the status bar and the on the always on display.
I have been having the same issue along with a few other people. Prior to March update it was all fine it’s only since March update that I have found this has happened and literally no option anywhere to make sure missed calls are still displayed on notifications.
I seem to have all my notifications on but I cant get it to show missed calls on my lock screen or on the top notifications bar like it used to on my S7. Any ideas? Its a MUST have for my work as I get so many calls I need to call people back without having to constantly check to see if I missed a call.
No missed call notifications in my lock screen, or in small notifications bar at top after I unlocked phone.
Not only help forums, similar reports can be seen on micro-blogging site Twitter as well.
https://twitter.com/andrewmheff/status/975840058002599936
https://twitter.com/APurton/status/974017119460450304
Going by user observations, the problem appears to have creeped in after the March security update.
What’s appeasing is that Samsung is aware of the issue. One of the moderators on the company’s European help forum confirmed the same while reverting back to one of the complainants, saying the matter has been escalated.
I’ve escalated it to our software guys – but any software log files you folks can send them will help them narrow down exactly what’s going on and fix it quicker.
This must give the complainants a breath of relief. But, how long will Samsung take to acknowledge and then fix the glitch, that’s not known yet. Rest assured, we are keeping a close tab on all related developments, and will update the story as and when anything news worthy comes up.
Meanwhile, the only user-suggested workaround that seems to help is disabling Caller ID and Spam Protection.
Stay connected with us on Twitter (@PiunikaWeb) to hear about all related developments as and when they occur