Bundle 2426 does not work with Sprint Visual Voicemail

[jwolf6589]

I updated to the latest Sprint Bundle a few days ago and after the update Visual VoiceMail has become quite problematic to keep working. I regularly have to reboot my BB to play messages. The only temporary solution is to call my VM system, but the Visual VM system stinks compared to the old Sprint VoiceMail system, as messages are not kept longer than a week, and a third of the features are gone. I have looked and even called both Sprint and BB tech support and both are clueless. Sprint sent me updates to my phone via the network, asked me to remove the battery, ran the update profile and update PRL options in the mobile options screen, etc.. My next step is to take it into the Sprint repair center and have them downgrade the OS or do whatever they need to do. The previous Sprint build worked just fine with Visual VoiceMail so not sure what the problem is. Is anyone else experiencing this bug and how did you fix it? I am more limited as I am on a Mac. I wish I would have kept the previous build, as I unfortunately deleted it to save space (last time I will ever do that).


John

[9of13]

Im now on the 3rd build (.234, .407 and now .522) and mine has never worked. went thru the same steps as you did. And even though i knew taking it to the Sprint repair center wouldnt help cause all they did was a "hard reset". BAsically reload the OS. I wish i knew how yours worked. one person on the Sprint.com forums and someone said to have someone call and leave a VM and then you can reset the vvm from your phone to work but this didnt work for me either. I hope we can find a fix

[konaman]

Hey folks, had the same issue after my update. I went into my sprint voice mail (press and hold 1) then followed the prompts to VM menu, playback options> set for auto playback-on, then exit. It seemed to work for me. I started getting my Visual VM right away and it seems to work, for now. We'll see how it goes though. Good luck.

[9of13]

Thanks Konaman. I just made the changes and i hope that works. Ill update about it later. Lets hope that worked

[jwolf6589]

Originally Posted by konaman

Hey folks, had the same issue after my update. I went into my sprint voice mail (press and hold 1) then followed the prompts to VM menu, playback options> set for auto playback-on, then exit. It seemed to work for me. I started getting my Visual VM right away and it seems to work, for now. We'll see how it goes though. Good luck.

This was already on in the first place.

[jwolf6589]

Originally Posted by 9of13

Im now on the 3rd build (.234, .407 and now .522) and mine has never worked. went thru the same steps as you did. And even though i knew taking it to the Sprint repair center wouldnt help cause all they did was a "hard reset". BAsically reload the OS. I wish i knew how yours worked. one person on the Sprint.com forums and someone said to have someone call and leave a VM and then you can reset the vvm from your phone to work but this didnt work for me either. I hope we can find a fix

The previous build worked perfect for me. Bye the way do you have AIM or yahoo? Perhaps we can chat and I can help you.

[jwolf6589]

I tried leaving myself a VM and after of which got a screen saying that my VoiceMails could not be downloaded and that I had to call in the VoiceMail system to listen to messages.

[konaman]

Originally Posted by jwolf6589

I tried leaving myself a VM and after of which got a screen saying that my VoiceMails could not be downloaded and that I had to call in the VoiceMail system to listen to messages.

That's the same thing I got after the upgarde. When I called in it didint tell me much so I went to settings, that's when I found my auto play was off, it was previously on. When I turned it back on it sent my messages to vvm. It may have been a fluke though. It could be sprint, they seem to have had a lot of problems with vvm in os6 everytime there's an upgrade, the forums have quite a few posts about their vvm not working when people upgrade versions. Turning auto-play on seems to have worked for now but it may quit later. I'll update if it doesn't keep working. The whole things a pain. Good luck.

Posted from my CrackBerry at wapforums.crackberry.com

[jwolf6589]

Originally Posted by konaman

That's the same thing I got after the upgarde. When I called in it didint tell me much so I went to settings, that's when I found my auto play was off, it was previously on. When I turned it back on it sent my messages to vvm. It may have been a fluke though. It could be sprint, they seem to have had a lot of problems with vvm in os6 everytime there's an upgrade, the forums have quite a few posts about their vvm not working when people upgrade versions. Turning auto-play on seems to have worked for now but it may quit later. I'll update if it doesn't keep working. The whole things a pain. Good luck.

Posted from my CrackBerry at wapforums.crackberry.com

My auto play is on so thats not a solution for me. I think the problem is Sprint, although they say the problem is me, as it works well for others.

[tankhokie]

After I upgraded from bundle 1609 to 2426, my VVM has been crashing.

Basically, I get a voicemail, it goes to VVM, but when I open VVM, the application locks up. I can't scroll, I can't select, I can only go out to the main screen. (I can't close the VVM application either).

The only fix it to do a battery pull. Then it is only fixed until I get my next voicemail....then it locks up again.

I wish I could downgrade to bundle 1609 - VVM worked flawlessly with that build (for me).

[omegafritz]

Hey the set auto play idea worked for me. Mine was set to auto play so i turned it off and hung up. I called again turned it back on and now im set voicemails go through hope that helps

[DrivinDixie]

The auto-play made no difference to me. This happened right after I updated. It intially started just locking up, now it will occasionally say it can't download them. It doesn't always do that-it does always lock up after a few uses. And it doesn't delete the messages from the mailbox when I delete them from visual voice mail now (this just started happening recently.) It's really annoying, does anyone have a work around yet? Based on what I've read, calling Sprint would be useless.

[extinguisher911]

I'm having the same issues since upgrading. I too have the 2426 Bundle. I never had an issue with VVM, and it has always been set to auto-play. If I miss a call, I get the download error. I do the 3 button reboot, and magically the message shows after the phone comes back up. It may work for a call or two, but fails again.
I am pretty annoyed about this...and can't wait for it to be fixed.

BTW VVM Version 3.0.0.135

[tankhokie]

Does anyone know how you report this bug to BB or Sprint?

I used BBSAK to wipe the phone and reinstall the previous build (1609) and it seemed to work fine. I had other issues, so used BBSAK to wipe again and reinstall the latest 2426 build.

It worked for a couple of voice mails but it has returned to locking up

I even tried accessing the VVM's through the message icon only (never clicking the VVM icon) and it still locks it up. When it is in this locked up state, my phone will not report ANY new voice mails either. Battery pull is only fix.

Also, VVM Version 3.0.0.135

So I want to make sure "someone" in BB or Sprint is aware of this bug - Does anyone know how you report this bug to BB or Sprint?

[Ray III]

Since this is a double post I have to link to my original reply...
http://forums.crackberry.com/showthr...50#post6466350

As for the replies in this one, I found my auto-play setting was not on so I turned that on, that did not really fix the problem since the VVM froze up again and I don't feel like waiting for another reboot.

Also, I did not get ANY notification whatsoever for the last 4 voice mails I got. I did not find out about the important ones until my dad asked me if I got his message one day, which tipped me off that something was seriously wrong, so I called in and there they were! Then when I tried to save the important ones, Sprint deleted them anyways because they were more than a week old. Thanks a lot guys.