Database Info

Need help with apache phone number update

I have an apache witch I recently updated to wm6.1, after this I rang up to get it signed up to the telecom network. All went well until the next day I still hadn't been singed up. I rang up and they said I had to add my phone number into the device and they told me to type this into the dialer "##482243" then press the green phone key to get a type of popup. When I did it though nothing happened all it did was try to dial the code I had put in, could this be because I have updated my phone to wm6.1? Is there another code I could enter to get the same effect as the one telecom gave me?
Thanks a lot,
Aaron

[Q] Can send MMS but not SMS?

Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!

SMS seems good on my end :/ maybe just an issue in your area?

slowz3r said:
SMS seems good on my end :/ maybe just an issue in your area?
Click to expand...
Click to collapse
Possibly, thanks for checking. I wish there was a way to manually enter a SMS service number in messaging settings like in previous android versions. I was thinking maybe for some reason my SIM card is too old, and suddenly decided to not be recognized properly. Looks like I'll be going to t-mobile tomorrow,

May wanna give them a call. going into a store they wont be able to help you

I've found that the primary merit to taking my phone to T-Mobile when it's messed up is so the guy behind the counter has to go through the list of things you already tried that the phone support agent is required to tell you to try again instead of having to do it myself. At least I can check out some cool phones and accessories while I wait. >.>

slowz3r said:
May wanna give them a call. going into a store they wont be able to help you
Click to expand...
Click to collapse
I spoke to a lovely Tmobile rep. She lead me through troubleshooting, except it was for Froyo, not gingerbread. When I brought this to her attention, and reminded her this was a nexus s, she connected me to samsung , and the call never went through.
Could a 5 year old SIM card magically stop working properly for SMS?

mprziv said:
I spoke to a lovely Tmobile rep. She lead me through troubleshooting, except it was for Froyo, not gingerbread. When I brought this to her attention, and reminded her this was a nexus s, she connected me to samsung , and the call never went through.
Could a 5 year old SIM card magically stop working properly for SMS?
Click to expand...
Click to collapse
honestly tell them you have an extremely old SIM and they will give u a free new one...if it deosnt help. then hell you got a free sim

Yeah. Unfortunately, since the Nexus S isn't supported by T-Mobile, giving you a new SIM card is about all they'll probably do, unless you're lucky and get a rep who's actually tech savvy.

zorak950 said:
Yeah. Unfortunately, since the Nexus S isn't supported by T-Mobile, giving you a new SIM card is about all they'll probably do, unless you're lucky and get a rep who's actually tech savvy.
Click to expand...
Click to collapse
The @Tmobile twitter is way handy and the reps who run that, are actual engineers so send them a tweet

This could be many things... does the Nexus S not have the ability to do the *#*#4636#*#*?
That is the code on every Android phone (save a very few POS) to get into the "engineering" menu. Select "phone" from that menu, then scroll to the bottom and bingo, SMS service center number entry... first hit refresh to see what is shows, if not correct delete, enter in the correct one, then update.
If the phone doesn't have the *#*#4636#*#* menu, not sure... perhaps your SIM doesn't have the SMS service center # saved to it anymore? New SIM would correct that, or putting your sim in an basic phone, then changing the service center # on that phone would put it back on the SIM.
Also, have you tried texting yourself to make sure it isn't a cross carrier issue? I know Verizon, for example, doesn't play very nicely with other carriers (actually all carriers prioritize in network traffic over cross carrier traffic, but Verizon seems to be especially bad in my experiences).
(FYI, I was looking through as I am thinking about getting a Nexus S and saw this thread, and couldn't help but toss in a word or two given I sell cell phones and have to deal with things like this all day).

mprziv said:
Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
Click to expand...
Click to collapse
I have the exact same issue.Stock phone with Mobilicity. I don't know what their service number is.

Went in to T-mobile store today, got a new sim...everything is working properly now.

mprziv said:
Went in to T-mobile store today, got a new sim...everything is working properly now.
Click to expand...
Click to collapse
did you pay for it or was it free?

slowz3r said:
did you pay for it or was it free?
Click to expand...
Click to collapse
Since when has anyone ever charged for SIM cards?

zorak950 said:
Since when has anyone ever charged for SIM cards?
Click to expand...
Click to collapse
Last i checked its like 30 bucks to replace a SIM from tmo.

slowz3r said:
Last i checked its like 30 bucks to replace a SIM from tmo.
Click to expand...
Click to collapse
Huh. I've never known T-Mobile to charge to replace a SIM card that needed replacing, whether due to its being outdated or simply worn out. Maybe I just got lucky.

zorak950 said:
Huh. I've never known T-Mobile to charge to replace a SIM card that needed replacing, whether due to its being outdated or simply worn out. Maybe I just got lucky.
Click to expand...
Click to collapse
last i went was because i needed a replacement sim cuz my phone wouldnt pick up 3g and called a rep and said he put a note on my account so i can run into a store and get a free sim

SMSC Update Error - Solved
I had the same problem - but found a way to solve it without replacing sim.
What you need to do is to insert the sim into an older phone and update message central number from there.
I fixed it using a nokia 3210 - after having tried using an n95 with no success.
While trying to figure out what was wrong i tested with another sim also - and when reading out the SMSC from the *#*#info#*#*-menu i found that the number is stored in some strangely obfuscated way.
Here is how it stores number for two of norways major operators:
Netcom: +4792001000 - shows as 06917429000100
Telenor: +4790002100 - shows as 06917409001200
What the first 4 digits are for, i'm not sure, perhaps a code for '+' but whats interesting is the last 10 digits - they are basically swapped around in pairs of two.
I tried inputting the digits for the other central in this manner, and sure enough - it saved ok!
Hope this help someone

grab another phone and put your SIM card in it
then try to send a SMS
see if that works properly or not.
if that works, then it might be a SNS setting issues
if the SIM card does not send SMS on another phone, then you'll need to swap your SIM card with a new one.
I had the exact same problem just few weeks ago
mprziv said:
Really strange. I suddenly lost the ability to send SMS messages. I can still receive them, and I can still send MMS, pictures...etc., but NOT SMS.
This has happened before once on my Nexus One, I went into messaging, opened settings, and there was an option for "Service Center number" or something similar...I was then able to input the SMSC # "12063130004" and all was well.
However, in Gingerbread on the nexus S, there is no such option under messaging settings
I tried *#*#info#*#* as well, went to the SMSC box which was blank, entered "+12063130004", then clicked update...but I keep getting "Update Error".
I'm not sure if this matters or not, but when I choose "Refresh" to the right of the blank SMSC box, instead of obtaining the correct telephone number, I get "00".
If anyone has encountered this, or has any other possible ideas...I'm all for it. I've tried some basic stuff, cycling battery, restoring from nandroid...even flashing a stock 2.3.1 and unrooting/unlocking the Nexus S, and I am still stuck, totally unable to send an SMS. Please help!
Click to expand...
Click to collapse

a one-phone solution from www google com tw/support/forum/p/Google+Mobile/thread?tid=078232a74455bbf0&hl=en
Code:
OK, I managed to fix this. I'll post the answer because this was buried deep and is a pain.
Answer is here:
http://forum.xda-developers.com/archive/index.php/t-926771.html
The relevant text is below. One thing I'd say is that the link is a bit vague on how to do the conversion. You need to put your SMSC number in the page, clear the rest of the info and press convert. You then need to ignore the numbers after 11.
For example, my vodafone +447785016005 goes to 0791447758100650110000910000AA00, which shortens to 079144775810065011. Go to the *#*#4636#*#* menu and put that in SMSC and hit update. Messages now send!!!. Hopefully I can save someone else the grief I've had all day...
"
to update the SMSC in android,
the number first need to be encoded
please use below url to encode the SMSC
http://www.twit88.com/home/utility/sms-pdu-encode-decode
for example, if your SMSC is number is +4531300000,
after encode, it is 0691541303000011
put this in the info page, and it will work.
"

[Q] Infuse Network PIN Issue

A rundown of my issue. One morning I woke up, got on facebook mobile on my phone and the phone crashed. Once it booted it up it asked for a Network Control Key(only 10 attempts allowed).
I had no idea at the time what a NCK was so I took my phone to ATT and the associate tried random keys until the phone wouldn't let her enter anymore keys (as instructed by another ATT employee). Well now the message says "Network unlock PIN number is entered incorrectly. Contact your Service Provider."
One odd thing I've noticed is that the IMEI number in the phone is a wingding type text, something like a number and then boxes and non-traditional fonts.
So a problem I ran into is that Samsung has denied my claim to get a replacement(this phone is a refurb), and it's still under warranty for about 20 more days. No idea why it's denied as the ATT employee was talking to Samsung in my behalf.
Last night I decided to root my phone, which was successful.
So with my IMEI number jacked up is my phone still able to be fixed?
Thanks in advance!

[Q] Transferring Atrix 2 to Tmobile

I just switched my unlocked Atrix 2 phone from ATT to Tmobile. I can make and recieve both phone calls and text messages. Unfortunately, I have been unable to get voicemail to work. When I dial the number, I get a menu that asks for my phone number and then says that it cannot find an account for that number. I've tried talking to tmobile, and there only solution was to wait up to 72 hours for the number porting to complete. Is there a chance that this is some setting I need to change, or will I just need to wait.
On a side note, if I try to enable a mobile hotsot, I get a message that it is not allowed by my att account. Will this ultimately switch/is there a setting I can change, or will i never be able to use this feature.

Having problem with Samsung account,

Hi guys,.
I bought samsung galaxy s6,
Now I got problem, when I try to setup phone I getting message that phone is lock, please enter the samsung account which was used previously, I read some tutorials and we can work around, but I need imei number, but I am locked out phone so I can't use, it the Android systems to get imei, I don't have box so I can't see in it as well, I tried on emergency call page *#06# but didn't work, is there any way to unlock the phone and find imei number.
Thanks
Sent from my SM-G900I using xda-developers.com, powered by appyet.com

The IMEI # should be on the back of the phone. Text is pretty small.

^ What he said.
Backside of the phone, at the bottom.
You can find both IMEI and S/N there (Very transparent text though so not easy to read)
- Renolz

Cool, but I don't know what format it needs to enter on Samsung website, I registered a Samsung account and try to register this phone but when I am entering and clicking submit its not accepting it, if I need to include slash(/) in imei number which I enter and also how many digits long IMEI numbers are.
Thanks for reply fuya

You should only need to type in the 15 digits
- Renolz

Thanks