1. duhawk2013's Avatar
    About 2 times a week I will get a notification that I have a voicemail, yet my phone never rang. it can't be because of data activity because I won't be on the internet and won't be sending a sms message.

    I'm on a 8330 on the sprint network running .160.

    Anyone else have this issue?

    Posted from my CrackBerry at wapforums.crackberry.com
    06-09-09 08:11 PM
  2. lastraid's Avatar
    NOt sure how this is done on Sprint, but you might try getting your PRL updated. Also try a battery reset. Short of that, it might just be sprint.
    06-09-09 08:56 PM
  3. blackngray70's Avatar
    .160 is probably the problem. Did this ever happen before you upgraded?

    Posted from my CrackBerry at wapforums.crackberry.com
    06-09-09 08:58 PM
  4. duhawk2013's Avatar
    This happened before I upgraded to .160 as well.

    And what is a PRL???

    Posted from my CrackBerry at wapforums.crackberry.com
    06-09-09 09:09 PM
  5. blackngray70's Avatar
    Preferred Roaming List.

    When you dial *228 send option two.

    Updates your roaming capabilities.

    Posted from my CrackBerry at wapforums.crackberry.com
    06-09-09 09:15 PM
  6. Jared DiPane's Avatar
    I happens to me on occassion as well, the phone never rings then boom a voicemail. it could be that they call at the exact time your sending or receiving a text or email?
    06-09-09 09:17 PM
  7. blackngray70's Avatar
    You do it a different way with Sprint I think.

    Posted from my CrackBerry at wapforums.crackberry.com
    06-09-09 09:17 PM
  8. duhawk2013's Avatar
    Yeah I think its done differently, because when I called *228, it brought me to the typical sprint menu with "1 for activation, 2 for billing etc."

    So does anyone know how to update PRL with sprint?

    Posted from my CrackBerry at wapforums.crackberry.com
    06-09-09 09:48 PM
  9. Jared DiPane's Avatar
    Best bet would be to call sprint and ask them, they would be able to give you the best answer.
    06-09-09 09:49 PM
  10. duhawk2013's Avatar
    Okay. Well I will take care of that tomorrow because they incorrectly charged me on my previous bill for my data plan, so I need to get that squared away anyway.

    Posted from my CrackBerry at wapforums.crackberry.com
    06-09-09 10:39 PM
  11. duhawk2013's Avatar
    I found somewhere else on this forum that if you dial *18, you will hear some beeps, and then your PRL should be updated.
    06-10-09 01:57 AM
  12. ohio_golfer's Avatar
    .160 is probably the problem. Did this ever happen before you upgraded?

    Posted from my CrackBerry at wapforums.crackberry.com
    The same kind of thing is happening to me. It never happened before I installed the .160 upgrade.

    I do get vibrations when holstered.

    Is there a known fix?

    Regards.
    06-10-09 06:32 AM
  13. duhawk2013's Avatar
    I talked to sprint today, and asked to be flagged for a PRL.....so let's see where it takes me.
    06-10-09 11:25 AM
  14. juniorfan's Avatar
    I hated my time with Sprint, including the fact that you have to call to do a PRL update, but in this one occasion, I would say it isn't their fault.

    I heard many people say that with .160 running your profile sounds may just go mute, and experienced this when I was running .160. Just try downgrading back to .131 or .138 and that in itself should fix the problem.
    06-10-09 11:43 AM
  15. duhawk2013's Avatar
    But i was experiencing these problems before I upgraded to .160 too so i dont think that it is the only issue.
    06-10-09 11:45 AM
  16. Crayons15's Avatar
    i have Verizon and I see you have Sprint so it may be different, but i know on Verizon if you update your roaming capabilities it usually solves that problem. its *228 for verizon, so whatever is equivalent to that on sprint!
    06-10-09 11:46 AM
  17. ohio_golfer's Avatar
    I hated my time with Sprint, including the fact that you have to call to do a PRL update, but in this one occasion, I would say it isn't their fault.

    I heard many people say that with .160 running your profile sounds may just go mute, and experienced this when I was running .160. Just try downgrading back to .131 or .138 and that in itself should fix the problem.
    I did a battery pull and that seems to have fixed the problem, at least for now.
    06-10-09 12:03 PM
LINK TO POST COPIED TO CLIPBOARD