I installed the Sprint TV cab that comes with the new ROM but every time I start the application I get this message.
Unable to get billing system indicator for the MDN(12)
MDN : ##########
CID : AFB52 - 73E8C- 16332
I noticed that the value of MDN is supposed to be my phone number but it's wrong. One of the numbers does not match with my phone number and I'm pretty sure that's what the problem is but I don't know how to change my device's phone number
Does anyone know how to change the phone number on Windows Mobile???
I'm sure the information is on this forum somewhere, but I'd say just give sprint a call. I can't rem. the exact steps so I won't tell you them as I don't want you wrecking your phone due to my poor memory...
I do know when I ported my number after getting my Mogul on Tuesday I was walked through some steps punching in various codes and the like and I was able to edit the phone number and something else on my phone.
jrobertiko said:
I installed the Sprint TV cab that comes with the new ROM but every time I start the application I get this message.
Unable to get billing system indicator for the MDN(12)
MDN : ##########
CID : AFB52 - 73E8C- 16332
I noticed that the value of MDN is supposed to be my phone number but it's wrong. One of the numbers does not match with my phone number and I'm pretty sure that's what the problem is but I don't know how to change my device's phone number
Does anyone know how to change the phone number on Windows Mobile???
Click to expand...
Click to collapse
I have the same problem with my Touch Pro. How do we change the MDN without going through Sprint CS? I have had enough of their crappy CS so I would rather get the info through the helpful mates on this forum.
dial ##778# send
then enter your MSL code, select edit, then select VIEW softkey, select NAM settings, there you'll find MDN, tap and hold with stylus and edit.
Hope this helps.
Oops, I just realized how old this was. Sorry, as it's probably already been resolved for the OP long ago.
I purchased a G1 from craigslist. Turned out it was an ADP device. I updated the recovery image, updated to Haykuro SPL, and Cyanogen ROM.
Everything worked except that SMS messages would not send... (I didn't try MMS messages).
I checked and double checked everything. ON another forum I found advice to acquire access to some Phone Info settings using "ANYCUT" - a free app.
Create a shortcut to your desktop using ANYCUT: Shortcuts>Activity>Phone info.
The above suggestion stated to use the above shortcut to turn off - then, back on - the phone's radio. That did not work for me. Also, in that shortcut was a space for a SMSC - whatever that was.
I called ATT and spoke to a knowledgeable associate who asked if my SMSC had been set and what was my number. I remembered seeing the SMSC setting in the above shortcut. I was provided with the ATT SMSC number for an HTC device for my area as "+13123149810" I used the above shortcut to enter the number and selected "update"
This solved my problem.
If you have similar problem I would suggest attempting the above. Call your provider and ask for the correct SMSC and enter it in using the above method.
I observed several posts on various forums where persons where told to go get a new sim card. I don't know if that would work or not. But, it was not necessary in my case.
Thank you for the post!
This worked for me.
My ulocked G1 was working fine with Cyanogen 4.0.4. I upgraded to 4.2.1 and lost my ability to send and receive SMS messages.
I followed your instructions, but for some reason I lost my 3g when I opened the Phone Info via the AnyCut link. I changed to GSM only and got Edge, at least. Guess I need to play with it more.
Anyway, I'm on the STC aljawal network here in Saudi Arabia. (Jawalnet) using an unlocked G1 and sending and receiving SMS messages again. Yay!
If there happens to be anyone else having SMS issues, the number on the STC website is +966505031999
I think this is the SMSC number, because when I put it in the SMSC box on the Phone Info I was able to send SMS messages again.
I haven't been able to get Google Voice to function as voicemail on the Aria, either by using the in-phone command, the call commands specified by the website, or the bootleg "type in the number" method that I used to get it working with my G1. There are actually commands missing from the call settings menu (the additional GSM call settings): principally the "call forwarding" commands. AT&T meddling, or am I missing something?
klyon said:
I haven't been able to get Google Voice to function as voicemail on the Aria, either by using the in-phone command, the call commands specified by the website, or the bootleg "type in the number" method that I used to get it working with my G1. There are actually commands missing from the call settings menu (the additional GSM call settings): principally the "call forwarding" commands. AT&T meddling, or am I missing something?
Click to expand...
Click to collapse
I have had no problem using GV as my voice mail and forwarded number as well.
Made sure i set it up on the website first then ran GV and set it up following the prompts. Skipping the step where i tried to change the voice mail settings automatiically. Use the settings option on the website to give me the # 004 # etc.. code which set up the forwarding without much problems.
When I go to Menu > Settings > Call > .., at the very bottom I see call forwarding, Call barring settings, Additional Settings, etc.
As for Google Voice, I don't believe you need to change anything using the settings within the Aria. For me, anyway, I left my voicemail settings intact on the Aria, and my calls still get directed to Google Voice (I figure by keeping the carrier voicemail settings, it'll default to that if Google Voice fails). So if you changed the voicemail settings ON the Aria (via Menu > Settings > Call > ..) then change them back to the AT&T settings?
Don't have the phone with me now, but when I tried the *004 etc# thing it returned some kind of incorrect code error message. I'll try it again tomorrow. I'm just glad to hear that's it working for someone.
Works for me using *004*.... method.
It failed for me thru the Google Voice App, but worked when I activated via the Google Voice website...make sure you type it in exactly as they tell you to on the website.
I did it a couple of times, and very carefully; got the same error message each time. So I don't know what's going on. I'll try it again tomorrow (it's not my phone). I do like the phone, however. It's a lot snappier than my G1 and I like the size. I don't think I'd miss the extra cpu or screen size of the nexus and I can get it for almost nothing; I'm thinking about it. But then there's that Legend...
I did it a couple of times, and very carefully; got the same error message each time. So I don't know what's going on. I'll try it again tomorrow (it's not my phone). I do like the phone, however. It's a lot snappier than my G1 and I like the size. I don't think I'd miss the extra cpu or screen size of the nexus and I can get it for almost nothing; I'm thinking about it. But then there's that Legend...
Hmmm... well, Google Voice began working immediately for me on my non-rooted Aria, after I installed GV and did the set-up (coming from a Nexus). It sometimes has trouble deleting messages from voicemail, but that's about it. I didn't touch anything, and GV was one of the first apps I installed.
damn pixie said:
Hmmm... well, Google Voice began working immediately for me on my non-rooted Aria, after I installed GV and did the set-up (coming from a Nexus). It sometimes has trouble deleting messages from voicemail, but that's about it. I didn't touch anything, and GV was one of the first apps I installed.
Click to expand...
Click to collapse
Calling out to Google Voice voice mail may not work correctly if you rooted and used fluffy's original app sideloading procedure, which has since been fixed. There was an 'android_id' problem with the original method. I think non-rooted users should be okay.
Unfortunately, they only way I know of to correct the android_id problem is to wipe data (restore factory settings) and start fresh, and then use the new sideloading patch. This uses your existing settings and not someone else's.
When I did that, at least all off my downloads showed up in android market so all I had to do was redownload and install them. It saved a lot of searching for the apps I had downloaded previously.
The HTC dialer can be quirky somethings. I would try *004*+12223334444# where that is the GV number, the plus may help I am not sure though.
If that doesn't work call 611 and have them forward unanswered and rejected calls to you GV number. They can set the option on there end since it isn't phone dependent, but rather dependent on the network.
I did a wipe and reinstalled, used the new sideloading method and still cannot get GV to work. Getting a MMI error code.. Tried adding the + in as well, no luck.
I have now tried everything mentioned. Any attempt to dial the google code, with or without the "+", returns: Connection problem or invalid MMI code.
Any attempt to change the call forwarding numbers returns: "Unexpected response from network."
I'm glad it's working for everyone (nearly) else, but it just isn't here. I talked to an att rep; they didn't have a clue. I suppose I'll have to try another one...
Okay, I finally found a tech at att who could sort it out. And while he was doing so -- it took a while -- he admitted he himself didn't know what network quirk made it not work the way it should in my case.
So for anyone else with this unexplainable, network problem: persevere until they bump you up to a serious tech.
klyon said:
Okay, I finally found a tech at att who could sort it out. And while he was doing so -- it took a while -- he admitted he himself didn't know what network quirk made it not work the way it should in my case.
So for anyone else with this unexplainable, network problem: persevere until they bump you up to a serious tech.
Click to expand...
Click to collapse
Glad to hear you got it worked out, was it on their side or did you have to do something to the phone?
Why are some of you guys sideloading GV? It's in the market. Install it from there.
I don't think it is that we are sideloading it, it was the original sideloading "fix" that was posted may have had something to do with the GV issue, at least that was the hope for me, but I still cannot get it to work.
bobj said:
Glad to hear you got it worked out, was it on their side or did you have to do something to the phone?
Click to expand...
Click to collapse
It was completely on their side. And they couldn't even explain why it wasn't working the way it should.
I just called AT&T because my regular VM wasn't working, callers were getting a fast tone busy when I was on the line, also call forwarding wasn't working. They tinkered around a bit, turns out my VM number was in only one place where it is supposed to be in two, so it was a programming error. Once that was fixed I tried GV again and was able to set it up using the *004* method and it does now work! Hope this helps others...
I have just found out that I can't send text messages, I can receive them just not send them. From talking to the phone company they have asked me to make sure my message setting number is correct but they couldn't tell me where it was and I couldn't find it.
Apparently this number is used when sending text, can anyone help by letting me know where this setting is.
I don't believe it is the rom or radio as since I found the issue I have been trying all types of roms and reverted my radio back down to 26I, no joy.
Currently I have CyanogenMod 5.0.8 installed
Found this answer from "Nexus One","BryanNexus1"
Dialing *#*#4636#*#* AKA *#*#INFO#*#* brings up a troubleshooting/statistics menu page. Dial that and select Phone information and at the bottom you can enter the SMSC (Short Mail Service Center) number. If the phone can receive but not send SMS it could be a carrier outage or issue 90% of the time. Morlin it is not risky to update the SMSC number. Kerorek gave the correct one for T-Mobile (12063130004). SMS is a voice issue and has nothing to do with data. Morlin try to update the SMSC number and powercycle the phone and test sending SMS.
Click to expand...
Click to collapse
for New Zealand the number is +6421600600
I had a similar issue some time ago. I remember trying to fiddle with various settings, but that didn't really do me any good.
I ended up wiping the phone and restoring all my SMS/Contacts/etc. Worked like a charm.
Just had this issue, after stupidly messing about in the very area I need to be in to fix it, ( pressed update smsc number with no number typed in, could receive messages, but not send them), full data+cache wipe did not fix this, nor did flashing other roms, since the SMSC reset wipes it from SIM I believe.
Looking up the correct SMSC number for my network and entering this fixed it however, and sms behaviour is back to normal.
So thanks for this, and remember folks, no matter how smart you think you are, all it takes is one stupid moment to remind you, you are just like everyone else
Hi
I have a little problem. Normally I should be able to just hold the "1 button" in the dialer and it should call the voicemail number stored on the simcard, but instead it says that the number is not setup and that I should configure it in settings. I then press settings and try to put in the voicemailnumber, but then I get an error that it couldn't be said and that I should contact my provider if the error persists.
I have called my provider but it hasn't helped much (they tried taking reassociate my voicemail from their side, they got me to change simcard and reset the phone, but still no solution)
So there are 2 problems:
Nexus4 is not reading the voicemailnumber stored on the simcard
and
I cannot manually set the voicemailnumber
This is on stock android 4.2.1 and the number is ported from a normal sim to a micro sim(and I know am running on another micro sim the said I should try)
Does anyone know what is failing and what I can tell my provider to get this fixed. I know it is minor annoyance and I am just calling voicemail from my contacts instead.
Best Regards
Hasse
Alfafa said:
Hi
I have a little problem. Normally I should be able to just hold the "1 button" in the dialer and it should call the voicemail number stored on the simcard, but instead it says that the number is not setup and that I should configure it in settings. I then press settings and try to put in the voicemailnumber, but then I get an error that it couldn't be said and that I should contact my provider if the error persists.
I have called my provider but it hasn't helped much (they tried taking reassociate my voicemail from their side, they got me to change simcard and reset the phone, but still no solution)
So there are 2 problems:
Nexus4 is not reading the voicemailnumber sotred on the simcard
and
I cannot manually set the voicemailnumber
Does anyone know what is failing and what I can tell my provider to get this fixed. I know it is minor annoyance and I am just calling voicemail from my contacts instead.
Best Regards
Hasse
Click to expand...
Click to collapse
Don't no what ROM ur using ( guessing stock ) but works just fine on aokp ROM , I no this helps u NONE , but thought ID mention anyway
drawde40599 said:
Don't no what ROM ur using ( guessing stock ) but works just fine on aokp ROM , I no this helps u NONE , but thought ID mention anyway
Click to expand...
Click to collapse
Thanks. I have edited the post to include that I am running stock
working fine on stock for me for the 3 network.
is it in the APN settings?
Alfafa said:
Hi
I have a little problem. Normally I should be able to just hold the "1 button" in the dialer and it should call the voicemail number stored on the simcard, but instead it says that the number is not setup and that I should configure it in settings. I then press settings and try to put in the voicemailnumber, but then I get an error that it couldn't be said and that I should contact my provider if the error persists.
I have called my provider but it hasn't helped much (they tried taking reassociate my voicemail from their side, they got me to change simcard and reset the phone, but still no solution)
So there are 2 problems:
Nexus4 is not reading the voicemailnumber stored on the simcard
and
I cannot manually set the voicemailnumber
This is on stock android 4.2.1 and the number is ported from a normal sim to a micro sim(and I know am running on another micro sim the said I should try)
Does anyone know what is failing and what I can tell my provider to get this fixed. I know it is minor annoyance and I am just calling voicemail from my contacts instead.
Best Regards
Hasse
Click to expand...
Click to collapse
Do you have google voice app installed on your phone? If you do try removing and then try adding the number,.
Thanks for the suggestions. The apn settings is correct - so they must have been read correctly from the simcard
I don't have Google voice installed(seems I cannot even get it in danish play store)
The problem also exists after doing a factory reset and 3/three has also replaced my simcard, but I still cannot set my voicemail number (in the settings of the dialer). So I'm thinking that 3/three in Denmark maybe are doing something wrong with the simcards? I will try later to put it into another phone and see how that work
Sent from my Nexus 4 using xda app-developers app