Hello,
On a stock unrooted EVO 4G, I have a new issue with Google talk not notifying me when a certain contact messages me. Others will, but a specific contact, who was hidden from my viewable list, and still showed notifications when they messaged me, all of the sudden I am no longer notified. No led, mp vibrate, no sound, no icon up top. I basically have to open their chat window to see if they've written anything.
Anyone know how to bring my alerts back? I've tried hard reset, clearing app cache and messing with notifications.
Anyone help?
Hey guys, so I've been trying to resolve this issue that I've been having with my SGS3 today. Whenever I receive a text message it comes to the device and I can read it fine. The only problem is; is that I don't receive any notifications and they're always set to read, so I can't even see them through my DashClock extension. This is kind of a big deal, because I happen to text a lot with friends, and family, and they get kind of pissed when i reply an hour later once I finally open up the Messaging app and see I got a message.
Thanks!
UPDATE ------ This was being cause by the AT&T Messages app. It was installed on the device but not set up and it was blocking Notifications from other SMS applications (Ex. FB Messenger or Stock Messages)
Hi all, ever since I upgraded to marshmallow, my Whatsapp icon does not display unread message count. My phone is rooted though. But I remember issue is already there before rooting.
Anyone else encountering the same thing? Or is it only my phone? Thanks in advance.
Update: Fixed by latest Whatsapp update. Closed.
I like the badge count feature, a great improvement from android 7.x, but on my s9 the count is not representative of the actual number of unread messages and emails I have- for example, when I get a new text message, the badge count usually says 3, and 3 or 4 unread emails gives me a badge count of between 35 and 45!
Has anyone else had this issue, or any ideas how to fix it?
Thanks!
with the new Android version, the badge count reflects not only NEW notifications but older, unread ones also. That may be the issue.
Thanks for the reply- not that though, I have zero unread messages but it always shows 3 as a badge when I get a new one.
I guess I am the only one with this issue, so maybe a wipe and rebuild is in order
I have same problem on my S9+. Using textra, I have deleted all text messages and still when I get a new message, it shows 2 instead of 1. When using Signal app, the badge rarely if ever even shows any count. All other apps seem to be accurate.
Gmail randomly shows 999 for me..only sometimes
I have this issue, too. Currently ZERO unread messages, but when I get a new text, the counter says "5".
ive come from s7 edge with touchwiz from s8 installed previously and badges there worked as intended (unread count, not notification count).
when i recovered all apps and settings on my new s9 notifications worked the same as on the old phone (unread count). when i reset the device and recovered nothing but messages and contacts it started to act as for every1 (notification count).
Same goes for the samsung keyboard. for freshly set keyboard i dont seem to be able to enable swype typing, when i recover keyboard data from old phone recovery swype get "enabled" tho no option is present in settings
maby there is some hidden option to reenable unread badges again
Badge count incorrect
I've had the same problem with my new Galaxy S9. The badge icon will show 5 new messages, but there will only be 2 or it will show 2 new messages and there will only be 1. And, no there aren't any hidden unread messages. Hopefully, it will get corrected soon.
Same issue
shmck28 said:
I've had the same problem with my new Galaxy S9. The badge icon will show 5 new messages, but there will only be 2 or it will show 2 new messages and there will only be 1. And, no there aren't any hidden unread messages. Hopefully, it will get corrected soon.
Click to expand...
Click to collapse
I have the same issue. It started after Telstra sent notification of change to my MessageBank. Message received was
"Your mobile is now Telstra Messaging capable. Your Telstra MessageBank voice mail will now be delivered to the RCS messaging inbox on your device. This feature requires your device to have the latest Android updates. For more information, including control of this feature browse Telstra. com/rcs"
That message was also sent as an audio (MMS)
Then the problems started.
The Message badge shows incorrect numbers - if I have one voicemail it can show as 3 or 4. It shows as 2 or 3 if it is a text message. If I press the Message badge it then shows 2 bubbles. The first grey bubble will say 101 Message Bank - the second white bubble is an audio MMS which can only be played with speaker on.
I have spoken with 8 people in Telstra, and they are still trying to fix. Have tried switching off the Rich Communications in Chat Settings. Have sent AUDIO OFF to 144 as per Telstra website.
The Audio messages are now stopped but badge still shows incorrect numbers and message now says
"You have received a new voicemail, please call 101."
I then have to go back to keypad and dial 101.
Previously I never dialled 101 just pressed the bubble and it took me directly to voicemail. As of 30 mins ago - Telstra still trying to find out what has changed.
If they figure it out I will post the instructions!
Also having this problem, though only noticed it after updating to Android P. For the record, I found a few suggestions online about wiping the data/cache for the app "BadgeProvider" and rebooting, but that hasn't helped.
---------- Post added at 12:16 PM ---------- Previous post was at 12:08 PM ----------
I think I found a fix for SMS. It's annoying though, and might not be universal.
I'm using the stock android messaging app for texts instead of the Samsung one, so badge I'm seeing is over the stock messaging app. In that app is a menu item to "mark all read" which I've used a few times. But while there's no badge after, I can get one message and have a badge that says I have three.
Here's the deal: the Samsung messaging app, even if it isn't the default SMS app, has its own unread count and hides it.
So, if you open the *Samsung* messages app (and say cancel when it asks if you want to set it as your default texting app) it'll load up with a tab on the bottom for Conversations. If you wait a minute, a blue badge will appear next to it with a number. Scroll down and look for a similar badge on different conversations on the right side, and open each one. When there's no badge next to conversations anymore, exit the app.
That *should* do it. I've now gotten a single text message and been given a badge that says 1.
That worked for me - thanks!
jptiger said:
Also having this problem, though only noticed it after updating to Android P. For the record, I found a few suggestions online about wiping the data/cache for the app "BadgeProvider" and rebooting, but that hasn't helped.
---------- Post added at 12:16 PM ---------- Previous post was at 12:08 PM ----------
I think I found a fix for SMS. It's annoying though, and might not be universal.
I'm using the stock android messaging app for texts instead of the Samsung one, so badge I'm seeing is over the stock messaging app. In that app is a menu item to "mark all read" which I've used a few times. But while there's no badge after, I can get one message and have a badge that says I have three.
Here's the deal: the Samsung messaging app, even if it isn't the default SMS app, has its own unread count and hides it.
So, if you open the *Samsung* messages app (and say cancel when it asks if you want to set it as your default texting app) it'll load up with a tab on the bottom for Conversations. If you wait a minute, a blue badge will appear next to it with a number. Scroll down and look for a similar badge on different conversations on the right side, and open each one. When there's no badge next to conversations anymore, exit the app.
That *should* do it. I've now gotten a single text message and been given a badge that says 1.
Click to expand...
Click to collapse
:good: That worked for me - thanks!
How to enable unread budges instead of notification budges in samsung galaxy S9+ one UI 2.1.
shoyab1 said:
How to enable unread budges instead of notification budges in samsung galaxy S9+ one UI 2.1.
Click to expand...
Click to collapse
i dont understand the question, could you rephrase it please?
Youdoofus said:
i dont understand the question, could you rephrase it please?
Click to expand...
Click to collapse
In my samsung galaxy s9+ budge icon only shows for notifications in tray. I wanted to know if any way I can enable budge for unread msgs.
shoyab1 said:
In my samsung galaxy s9+ budge icon only shows for notifications in tray. I wanted to know if any way I can enable budge for unread msgs.
Click to expand...
Click to collapse
firstly, i believe theyre called "badge" notifications
so, to make sure i understand, youre getting notifications for other stuff up in the top bar where the time, battery level and signal icons are located, correct? And youre wanting your text message badge notifications to show there as well?
Sorry for the mistakes,
I'm talking about badge on the app icon that either count notifications or unread messages.
In galaxy s9+ it counts notifications. Please guide if I can enable that for unread count i.e., the unread messages in whatsapp, gmail, twitter, etc.
Please let me know if need more charity. Happy to answer.
Thanks!
I'm wondering if anyone else has this same issue (or can test it).
I have the Watch GT2 and I am aware that it is only able to display notifications and not repsond. When I receive an SMS message I can see the notification and the message, however if the message is sent from another user and we both have Google RCS messaging enabled (Chat) then if the message is sent via this the notification isn't sent to the watch, only see I've got a message when I look on the phone screen.
Tried resetting the watch and the phone, repairing, checking the notification settings for the watch and app, etc but still nothing. I've raised a service ticket with Huawei but I don't think their UK team understand the issue.
Problem is still present in 2023