Constant Voicemail "Received on Watch"

I've had this issue for a while and I'm surprised the solutions are so complex. My personal experience with T-Mobile over the phone has been very time consuming and with mixed results…. Generally the more time spent after they mix up something with my account, the closer I can get to breaking even or maybe actually solving the original issue, solving the new issue and getting some sort of credit to my account that made my time worthwhile. (And I'm talking about hours on hold, random disconnects, no record whatsoever of multiple prior conversations on my account with one rep, then everything there with the next, etc.).

I actually resolved this issue for a few days on my own, but don’t recall how exactly (pretty sure you just need to use the watch to delete a voicemail from the phone through to completion, and it’s gone). 

That's no good for someone like me who always has some saved voicemails, use the spam blocking, which is a whole other world of chaos (btw it works, and it's free if you already have VM-to-Text), so I still receive VM without my phone ringing and it may even be true that I got a VM on my watch without getting it on the phone like it thinks. But it doesn't matter because you still have to go through the watch to access VM and delete, and next thing you know, the battery is dead.

I have a Galaxy Classic4 and I really just needed a watch with some sort of notification ability, and this was the simplest solution . Unfortunately I simply cannot comprehend how a watch with activity tracking and sleep tracking can be sold, period, when you cannot use either one of those features more than once before recharging the watch. I.e. Sleep tracking is probably for when you're not active, I'm presuming from the name that it's for while you're sleeping, and all the other features are obviously for (just a guess) use when you are not asleep, like turning the dial, perhaps even doing a physical activity. So this may be hard for someone in Marketing at Samsung to follow, but if it takes more than (conservatively) 30-60 minutes to shower, etc & charge the watch, then the charging time is taking away from it's usefulness for wearing it. Plain and simple I have mine on Power Save, barely use my watch to even check the time, and spend about 4 hours over 2 days giving it enough time to charge. I can split it up into smaller increments over more days, but the point is that this watch is useless for using 2 of the most basic functions WITH power save on. 

The process of taking the watch out of power save, turning on everything you need to get rid of the VM message, and getting back to where you started uses up about 15% of the battery life right there. (Minimum of 20 minutes charging to get that back.) Am I just not used to wearing a true Smart Watch?

The VM issue really bothers me, but seriously, if you check your VM with your watch (and don't have the VM icon on your phone on - or maybe you can, as it should go away), the moment you actually get to the prompts and follow through with the tiny keyboard (I don't do the voice thing, yet) the notification will go away. It will come back though if you reboot or possibly break off the connection with your watch  & phone, depending on the options selected. It always comes back, and the entire process of enabling everything just to get to the VM through the watch take time and a lot of battery power (more time). So I guess my point is that (and I got the bigger Classic4 BECASUSE of the battery issues people mentioned with the smaller one), something has to be done regarding the battery longevity on my watch at least, because I'm used to the annoying notification knowing the tradeoff is even more precious time. Which is funny, considering...

Over two years with my Galaxy Watch 3 and I'm still having this issue. It went away a couple months ago but when I paired it with a new phone, it came back almost immediately.

What I did to fix this issue was, go to settings>apps>visual voicemail>clear cache.  Then open visual voicemail and click the 3 dots and select mark all voicemail as read. And boom it works

What I did was I just had to sign into my voicemail and do some things and it stopped giving me them. I would just try logging into your voicemail

Listening to my voicemails did not help at all. Nor did resetting my phone. My husband 5 Pro doesn't have the battery drain or voicemail issue with the same settings.

After watching videos and changing my settings constantly, I realized that T-Mobile had set my Samsung Watch 5g (905) watch's number as my default voicemail number in my phone. To find this and verify:

1. (On phone) Tap call/phone icon

2. Select 3 dots & then call settings 

3. Scroll and select "voicemail" from list. 

4. The following should be available for view: Service Provider, voicemail number, and notification settings. 

Note: I could not manually change this to my primary number on my Fold 4 even in developer mode so I had to go in a T-Mobile store.) 

HOPE THIS HELPS!! 

Wren Rosenbridge wrote:

If you turn bot your phone and watches Bluetooth off and then reconnect it can fix it. Aswell as doing that and also restarting both devices. Worked for me. Good luck.

This worked for me! Super easy fix!

So I solved this by going into messages and marking all texts as read and clearing any that seemed to be prompting me to respond.  Then just clear the notice on the watch and it goes away.  Not sure WHY it works as my text messages have nothing to do with my voicemail but meh.  I have a galaxy watch 5

t-Mobile tech here with the resolution: Make sure you have no unread VMs on your primary line (your phone). Next, disconnect your watch from your device (disable BT on your phone and also turn off wifi on the watch). Wait until your watch connects to T-Mobile for it's data connection on LTE. Call to your mobile phone from another number and leave a VM. Then, while keeping your watch and phone disconnected from eachother, call into VM (or us the VMM client) to listen to and delete the VM so that you no longer have any unread VMs in your account. This should send the VM MWI off message to the watch.

TECH-LL wrote:

t-Mobile tech here with the resolution: Make sure you have no unread VMs on your primary line (your phone). Next, disconnect your watch from your device (disable BT on your phone and also turn off wifi on the watch). Wait until your watch connects to T-Mobile for it's data connection on LTE. Call to your mobile phone from another number and leave a VM. Then, while keeping your watch and phone disconnected from eachother, call into VM (or us the VMM client) to listen to and delete the VM so that you no longer have any unread VMs in your account. This should send the VM MWI off message to the watch.

Tried this and it didn't work 😞

TECH-LL wrote:

t-Mobile tech here with the resolution: Make sure you have no unread VMs on your primary line (your phone). Next, disconnect your watch from your device (disable BT on your phone and also turn off wifi on the watch). Wait until your watch connects to T-Mobile for it's data connection on LTE. Call to your mobile phone from another number and leave a VM. Then, while keeping your watch and phone disconnected from eachother, call into VM (or us the VMM client) to listen to and delete the VM so that you no longer have any unread VMs in your account. This should send the VM MWI off message to the watch.

6 months ago, that worked for me, and every month since then. Now the problem has gotten worse, and this no longer fixes my issue. 

I don’t feel like anyone is adequately trying to help or resolve this multi-year software issue.