No Voice mail notifications after updating to KitKat

[danfm]

I've updated my Nex 4 to 4.4 yesterday.
As soon as that was done, voice mail notification would not show up any more.
Had to turn the phone off and when it came back it showed the voicemail icon.
But, that worked only for the voicemail received before powering it off. New voicemail kept coming without any notifications.
I would need to constantly power it off and on, multiple times per day in order for the notificatications to show up which is absurd.
Is there a fix to this?
Thanks

 

[mr_nobody]

Did you clear google services framework to force the update?

 

[danfm]

I didn't.
After receiving notification that the update was downloaded on the phone I was asked to start the installation of 4.4 which I did.

 

[mr_nobody]

I guess you could try clearing cache for the dialer app... That's all I can think of.

 

[itic]

Whos your carrier? and are your voicemail setting correct in the dialer settings? Settings >Call Settings>Voicemail

 

[danfm]

I guess you could try clearing cache for the dialer app... That's all I can think of.

I just did it, cleared cach from the following apps: Phone, Google Dialer, Phone/Messaging Storage.
Still the same, it did not help.

 

[danfm]

Whos your carrier? and are your voicemail setting correct in the dialer settings? Settings >Call Settings>Voicemail

Provider is Mobilicity in Canada. The settings are good. Called their tech support, they checked it and said nothing wrong on their side.

 

[shn'g]

I am having the exact same problem.. I did clear services before update

 

[mr_nobody]

I am having the exact same problem.. I did clear services before update

Well clearing the google services framework can certainly affect notifications. You may end up having to do a factory reset...

 

[stphbkr]

I just factory resetted my Nexus 4 and it's still not giving me voicemail notifications!

 

[Reddzilla]

Try texting this to 122 Activate:dt=6

From what I've read that may resolve the issue

Posted using Nexus 4 via Android Central App

 

[kulb]

I have the same issue. My carrier is Mobilicity in Canada. I updated to KitKat on my nexus 4 few days ago. Since then, there were a bunch of issues such as voicemail, screen unlock delay. So I had to factory reset my phone. Still have issues with voicemail. I am not getting any voicemail notifications. If I power off and restart the phone, the notification appears. So far this android update has been very annoying.

Posted via Android Central App

 

[TomDroid22]

I'm having the same problem with Nexus 4 on KitKat on Rogers Canada.

I have everything normal - no root, no rom, got the update normally, nothing special at all.

Seems like a lot of Canadians having this problem. Is this primarily a Canadian site, or should we conclude that this is unique to CAnadian models or carriers (which would be rather odd)?

 

[shn'g]

I'm having the same problem with Nexus 4 on KitKat on Rogers Canada.

I have everything normal - no root, no rom, got the update normally, nothing special at all.

Seems like a lot of Canadians having this problem. Is this primarily a Canadian site, or should we conclude that this is unique to CAnadian models or carriers (which would be rather odd)?

Yeah I read another forum and I think almost all the complaints were Canadian and they were from almost every carrier. Guess we just have to be patient and wait for an update that fixes it.

 

[OntarioBlackberry]

You can add another Canadian carrier to the list: Videotron. I have not seen a single voicemail notification since updating to 4.4. Here's hoping a fix comes soon!!

 

[antonyk]

I got my KitKit upgrade when I was in the US, on AT&T, and got voicemail notifications. But after coming back to Canada (Rogers), there are no notifications.

 

[azeelex]

I have videotron and no notification alert since kitkat update

 

[Nazzrath]

I'm having the same issue with my Nexus 5 on the Bell network. =P I got a Google Voice number just for voicemail, but of course, Bell charges for call forwarding.

 

[danfm]

Just to let everyone know, this has been fixed in the 4.4.2 update which I installed yesterday.
Thank you Google.