n00b can't get Voice Mail Notification. - Page 2

the18thtee · #11 (**permalink**) 08-10-2007, 10:55 AM

Oh, btw, the reason I asked about the DN and MNN are because the *228 changes settings in the provisioning menu and there is a posinbility that the changes you made manually didnt stick. (It has happened to me)

woodyman4916 · #12 (**permalink**) 08-10-2007, 05:24 PM

Sorry about the non response....waiting for my wife to come home so I can verify settings. Will post asap.

woodyman4916 · #13 (**permalink**) 08-10-2007, 09:07 PM

Just checked the settings they are the same as when I entered them per the Verizon rep's instructions. The MIN1 and MIN2 and the SID were the settings I changed. They have retained there values. Also SMS works from Sprint and Cingular and MMS has been tested from Verizon and works (I haven't tested it from another network). Any Ideas?

the18thtee · #14 (**permalink**) 08-11-2007, 04:15 PM

Well, the only help I can offer is what has worked for me when I was having text messaging problems. What i did was reflash to stock rom, hard reset, let it go through all the setup stuff, *228, (basically everything you would do with a new phone on a new service), then flash to the kitchen rom (1.0.4 now) with the blank ms_.nbf, hard reset, then DONT do any of the activation stuff. With your carrier customizations built into the kitchen rom thats all you need.
I was having some serious problems with SMS (mainly with the threaded app, but sometimes without) where I would get a text message from a certain group of people (always the same people) and the body of the text would be "The contents of this message cannot be displayed." After roughly 3 months of research and experimenting, I found a pattern. When reflashed/hardreset the first thing I would do is a *228 to reactivate my phone (thats what my carrier uses to reactivate, not just update PRL). This for some unknown reason would cause everything to mess up. The only way I figured this out was that one time, as soon as I reflashed one time, during bootup, before I had a chance to *228, I recieved a text message that I could actually read to body contents from one of the people that I always got the error from. So, I sent a text to them to verify, and got another message from them that I could read. So, I dialed *228 as an experiment, soft reset, and test it again, and I got the error message from that person.

Anyways, enough ranting, just give this a shot and let me know what happens.

woodyman4916 · #15 (**permalink**) 08-11-2007, 06:59 PM

Thanks, I will give it a go...stay tuned for results