Hey everyone!
So I'm running into a issue and I don't think it has anything to do with the Zeus rom I have flashed since it started when I got the phone.
Every time I check my voicemai (by hitting 1 on my phone), I have to input my mail box number (phone number) and my passcode.
I never had to do this before with my captivate. Is there a setting that I can change to auto correct this or is this something on the ATT side?
Of course I have a Samsung Infuse
Thanks in advanced!
Newb4ever said:
Hey everyone!
So I'm running into a issue and I don't think it has anything to do with the Zeus rom I have flashed since it started when I got the phone.
Every time I check my voicemai (by hitting 1 on my phone), I have to input my mail box number (phone number) and my passcode.
I never had to do this before with my captivate. Is there a setting that I can change to auto correct this or is this something on the ATT side?
Of course I have a Samsung Infuse
Thanks in advanced!
Click to expand...
Click to collapse
AT&T's
Sent from my SGH-I997
all this started with the rupert murdoch thing.
more secure vm.
you can go to att vm setup and remove the extra security
Google Voice. That is all.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Related
Hey guys I purchased an unlocked G2X off of craigslist after my HD2 died on me :/ now I am running all of the Stock OS no mods nothing. This phone is unlocked as is working with at&t. I am able to access 2g which lets me get on the internet and browse (even thought it is slow it works really good). well the phone is great except I cannot download picture messages (MMS) it just keeps saying failed?!? idk what I am doing wrong? I tried to talk AT&T about it but they are saying that since they do not have a similar phone to it they cannot check the settings for me which sucks! I was just wondering if anyone else has had this issue and found a way to fix it?? **I HAVE GOOGLED, AND READ UP ON VARIOUS TOPICS BUT I HAVE NOT BEEN ABLE TO FIND ANYONE WHO HAS THE SAME PROBLEM AS ME!*
Thank you for all of your help!! Someone please get back to me! THank you ago
Stef
Stefo1990 said:
Hey guys I purchased an unlocked G2X off of craigslist after my HD2 died on me :/ now I am running all of the Stock OS no mods nothing. This phone is unlocked as is working with at&t. I am able to access 2g which lets me get on the internet and browse (even thought it is slow it works really good). well the phone is great except I cannot download picture messages (MMS) it just keeps saying failed?!? idk what I am doing wrong? I tried to talk AT&T about it but they are saying that since they do not have a similar phone to it they cannot check the settings for me which sucks! I was just wondering if anyone else has had this issue and found a way to fix it?? **I HAVE GOOGLED, AND READ UP ON VARIOUS TOPICS BUT I HAVE NOT BEEN ABLE TO FIND ANYONE WHO HAS THE SAME PROBLEM AS ME!*
Thank you for all of your help!! Someone please get back to me! THank you ago
Stef
Click to expand...
Click to collapse
I have the same issue with Simple Mobile. I think the images being sent are larger then what we can accept.
yeah i thought about that also, but it wont even let me send a message out, it just fails at that part too. I have tried using Handcent, resizing the images myself everything.
What I am thinking that it is, is the fact that MMS Proxy settings inside of the APN settings?
any suggestions?
Stefo1990 said:
yeah i thought about that also, but it wont even let me send a message out, it just fails at that part too. I have tried using Handcent, resizing the images myself everything.
What I am thinking that it is, is the fact that MMS Proxy settings inside of the APN settings?
any suggestions?
Click to expand...
Click to collapse
It definitely has a lot to do with apn settings. What I suggest is to find out what is the apn settings for one of at&t's (& Simple Mobile's) Android phone and copy it to the G2x and that should most likely fix the MMS issue. I fixed a myTouch 3g for somebody having MMS issues and all it took was Googling the apn settings of the carrier and then add it to the phone and you should be golden.
Sent from my LG-P999 using XDA Premium App
Have you checked your APN'S... Cuz that's the part you need to fix if it isn't set up for Att.
Usually you would need APNbackup from market or sideload it and backup and then alter apn for att then restore.
If not try using goSms and fill in mms proxy/apn info
Sent from my LG-P999 using XDA Premium App
I have had my Galaxy S 4G about 1 month now and I'm a newb to Android. I've not rooted or done anything other than load more apps from the Market to try and learn more about this phone. It is out of the box stock as of 9/2011
My Wifi shows that it is on and logged on to my router at home and when I run the SpeedTest.net app it shows that ping works (though slow) and then the download runs but then times out with a network error.
All I do is toggle off the wifi and then back on again and try it again and suddenly it works fine for some extended time.
I have an I-pod touch that always works along with a laptop that has no issues with the 802.11 g connection from the same chair that I'm sitting in with the phone.
It is an annoyance to keep having to check for "quality of service" issues with an internet connection. You never know when you will have to toggle the service back on again or if you are just looking at a server issue on the other end of the connection
Is this a known problem with either Froyo, Samsung Galaxy or T-Mobile?
My config:
[t959v] = [SGH-T959V]
Firmware version
2.2.1
Kernal Version
2.6.32.9
Build #
Froyo.vuvkd1
Thanks in advance.
ggregor said:
Is this a known problem with either Froyo, Samsung Galaxy or T-Mobile?
Click to expand...
Click to collapse
Not to my knowledge. I had my SGS4G back in February before the KD1 update and never had the problem. It wouldn't be a T-Mobile issue as, whatever the problem is, is between your phone and the router. So T-Mobile is out of that equation.
Maybe try a factory data reset? Just a thought to see if it helps. I can't think of a good reason it would but it's just an idea. Given that you're not rooted nor running any custom ROMs or firmware I don't want to even think about pointing you down that road.
Have you tried it with more than the 1 router in the house? If it's a problem with wifi in general it could be defective hardware. If it's only with the 1 router then there could be other variables at play (type of router, security on it, & the SGS4G not liking that, etc.)
I'm rambling...but stumped a bit.
Called t_mobile support and once I got to the second level support person she had me stop by a store and get an updated Sim card.
My original card was 7 years old. I really didn't think that would matter, but so far it seems to have done the trick.
Sent from my SGH-T959V using XDA App
ggregor said:
Called t_mobile support and once I got to the second level support person she had me stop by a store and get an updated Sim card.
My original card was 7 years old. I really didn't think that would matter, but so far it seems to have done the trick.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Awesome. Glad you got it working.
Click here to jump to the fix, or PAGE 9 for further details!
http://forum.xda-developers.com/showpost.php?p=24872502&postcount=83
Give a big thanks to Jboxer to sticking it out and solving the issue that was a pain in the butt!
if you have, do you have the issue where you can not send SMS over 4g... only on edge and wifi calling. me and a few (confirmed) others have the issue that tried the experimental rom and now can not send sms/mms over a 4g data connection.... please do respond so we can figure this out. I am not in any way throwing jboxer under the bus, I appreciate all what he is trying and doing for us just something happened to a few of us that messed stuff up.
mt3g said:
if you have, do you have the issue where you can not send SMS/MMS over 4g... only on edge and wifi calling. me and a few (confirmed) others have the issue that tried the experimental rom and now can not send sms/mms over a 4g data connection.... please do respond so we can figure this out. I am not in any way throwing jboxer under the bus, I appreciate all what he is trying and doing for us just something happened to a few of us that messed stuff up.
Click to expand...
Click to collapse
Nope can restore to his builds and no issue check your apn settings
Sent from my CM 7.1.0 G2x using XDA app
Can someone put a screenshot of their apn settings, tmo
You did do a.backup first right?
Sent from my LG-P999 using xda premium
mojorisin7178 said:
You did do a.backup first right?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1336796
read the OP post, this is exacly what is happening to some people, me included :/
Try restoring a backup or look at one of those FULL stock GB Nvflash images.
It will erase all partitions, set them back up, format, and flash the official GB rom. Fully stock 100%.
Or download the froyo nandroid, then back to a different custom.
Radio settings aren't touchable via normal flashing means so its just something carrying over.
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV
did he fixed the issue where we couldnt get no signal at all? maybe i missed that. what is the latest version? the last one i downloaded was version 6
I restored numerous backups and nothing worked a few of us are PMing and going through what we have tried. I've put my sim in other T-Mobile phones and all was okay, I've wiped everything only thing left is restoring to a fully stock setup but someone said that they tried it with no luck.
Sent from my LG-P999 using xda premium
mt3g said:
i restored numerous backups and nothing worked a few of us are pming and going through what we have tried. I've put my sim in other t-mobile phones and all was okay, i've wiped everything only thing left is restoring to a fully stock setup but someone said that they tried it with no luck.
Sent from my lg-p999 using xda premium
Click to expand...
Click to collapse
i will be glad to help in anything. If you have a signal fix. About the apns i can talk to my friend from tmous tech support to give me an idea of the apns the might work
I only get SMS problems on stock based ROMs. I don't have any problems on MIUI or CM7.
Sent from my MIUI G2x using XDA Premium App
can someone with a working sms, gimme their tmo smsc #? maybe is that :/
*#*#4636#*#* , phone info, smsc , refresh
C0dy said:
I only get SMS problems on stock based ROMs. I don't have any problems on MIUI or CM7.
Sent from my MIUI G2x using XDA Premium App
Click to expand...
Click to collapse
I want to test this lol I'm okay using cm7 based roms
Sent from my LG-P999 using xda premium
Let us know if it works.
Thanks
Sent from my LG-P999 using XDA App
mmandros said:
Let us know if it works.
Thanks
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Nope still have the issues I restored an MIUI, after work tonight I'm going to be reverting back to stock.
mt3g said:
Nope still have the issues I restored an MIUI, after work tonight I'm going to be reverting back to stock.
Click to expand...
Click to collapse
I am also having this issue only after that build...
I also using MIUI now and I think I saw part of the issue. MIUi stock messaging is giving an error that there is an issue on apn crash. I just cant get a screenshot since I checked don't ask again. I will try to recreate the error and post screenies maybe someone can help.
To all, if you checked another link, the common denominator started on one build.
Sent from my Calculator with Android.
FeloHFP said:
can someone with a working sms, gimme their tmo smsc #? maybe is that :/
*#*#4636#*#* , phone info, smsc , refresh
Click to expand...
Click to collapse
This is one of my suspect also. I am on Simple Mobile and it is the first time I saw an smsc# with letters.
Edit: I tried editing smsc# to +12063130004 and it gives unsuccessful error.
Sent from my Calculator with Android.
ya reverted back to stock recovery and everything, nandroided back to 2.2 v10f image and thinking about trying the LG tool so that I can update up to v21e maybe it will do something good for me even though I'm already on the july 15 baseband. just wishful thoughts, lol.
mt3g said:
ya reverted back to stock recovery and everything, nandroided back to 2.2 v10f image and thinking about trying the LG tool so that I can update up to v21e maybe it will do something good for me even though I'm already on the july 15 baseband. just wishful thoughts, lol.
Click to expand...
Click to collapse
Tried almost everything already. Even tried kdz update and nvflash update where partition are rewritten.
I hope I can find the march kdz, maybe that will help.
Sent from my Calculator with Android.
Have any of you gone back to Froyo to check your SMSC number? Have you put another sim in the phone to try and send sms. Many Android phones, especially since GB 2.3.3, dont display the SMSC number is ascii. Some use a format called PDU which is a 16 digit hexadecimal number, always beginning with 07. It seems that the P999 is displaying the number in some other format completely. I have been searching on Google but I cannot figure it out. Using a sim from T-Mobile USA, AT&T USA, TOT3G Thailand, AIS Thailand, TrueMove Thailand and DTAC Thaland I get what appears to be a 48 digit hexadecimal number. If I try to enter the PDU equivelant of the message center number for that sim I get an update error. But if I enter one of the 48 digit sequences it shows when you hit refresh the update takes. If you take the sim and put it in a non Android phone it will display the message center number correctly in ascii, so whatever LG is doing is some strange format I have not figured out yet.
Also, I have tested sms sending capability on all the networks in Thailand and, even with the 48 digit smsc number that I see when I refresh in phone info, all the sms were successfully sent and received. My phone also had the LG UI Experimental flashed to it (many times) and i can still send and receive sms with no problems, so I do believe something else is going on here.
Are all of you that are having this problem on the same carrier? Is it Videotron or Wind Canada? Since you all seem to believe my rom was the nexus of this issue, I would like to help you resolve this issue. One person said he even reflashed the baseband using a KDZ update. That would have obliterated any possible remnants of my rom, but the rom cannot write to the baseband, so I don't see how the rom could have affected it.
Reply with what carrier you are on and what value you get when you refresh your smsc number in phone info. So far the number I have are as follows:
Here is what I could come up with based on the smsc values on the LG P999. This is very bizarre and I hope some math whiz can help me crack this code, but look below and it appears to make some sense. The numbers are 48 digit numbers with a prefix of "002B" (I believe this represents the "+" symbol). Then every fourth digit is the next digit in the smsc for that carrier with a prefix of "003". So this numbering scheme of LG's, whatever the heck they came up with, has some logic to it. We just don't know what it is.
T-Mobile U.S.A.
SMSC in Ascii: +12063130004
SMSC from P999: 002B00310032003000360033003100330030003000300034
AT&T U.S.A.
SMSC in Ascii: +13123149810
SMSC from P999: 002B00310033003100320033003100340039003800310030
TOT3G Thailand
SMSC in Ascii: +66893200101
SMSC from P999: 002B00360036003800390033003200300030003100300031
Mind you, the other sim I have checked all follow the same smsc scheme and the numbers work out exactly the same. To prove my theory I am going to guess what Wind Canada is showing on the P999. Mind you, I do not have a Wind Canada sim here in Thailand. I only have TMO, AT&T and the old Cingular sims. So this coding is based purely on how i believe the P999 is storing and displaying the P999 in its memory.
Wind Canada (conjecture by jboxer)
SMSC in Ascii: +16135009000 (obtained from Googling it)
My guess of SMSC from P999: 002B00310036003100330035003000300039003000300030
(Please let me know if this is what your phone is showing to confirm my theory.)
Edit:
Upon further research I have figured out what LG is doing. They are showing the smsc number in Unicode encoding, rather than converting it to Ascii for humans. This is just another example of sloppy programming on LG's part. Unicode is how foreign character sets are encoded. Android uses Unicode so it can support any character set used in the world. LG should present the smsc in Ascii. Who in the heck knows why they are showing it in raw Unicode; and to update it you must enter the smsc in Unicode only.
Unicode Encoding
002B = + (plus sign)
003X = numerical digit X
0030 = 0
0031 = 1
0032 = 2
0033 = 3
0034 = 4
0035 = 5
0036 = 6
0037 = 7
0038 = 8
0039 = 9
So if you are on Wind Canada and your smsc is not showing as the number I have above (that I guessed) enter that number and press udpate. It will update and you will not get an error. I hope this helps you guys. You can also use a regular phone that displays the smsc in ascii, enter it in the regular format [plus sign] [area code] [number] with no spaces and update your sim and then put it back in your P999.
I appreciate you chiming in, I'm on stock 2.2 rom from T-Mobile it does still have SU permissions though. I'm on the Jul15 base band. I go into hidden menu (with 4g connection) when I press refresh i get 002B00310032003000360033003100330030003000300034, which is what you have up top...
If I press update it stays on with all the numbers
pressed home went to messaging application
texted myself and it worked
I tried a second time and it failed lol... WTF. I literally sent "test" and it went through,
sent a 2nd one saying eating (meant "testing" typed fast to see if it would work again)
Grrrrrr I just want my phone to be normal again lol.
I can't send text or phone calls after CWM recovery flash.
I initially rooted my i535 sg3 using this method http://forum.xda-developers.com/showthread.php?t=1840030
I then flashed 4.2.2 Pacman. Used this for a few days and everything was ok but battery life was horrible so I flashed, I think CleanRom, then Liquid RC1. I'm not sure where in the process of flashing but I noticed that my reception was weak compared to stock and then I couldn't send outgoing text or calls all together. I've searched everywhere and I have seen similar issues/symptoms but non of the fixes have worked for me. Here's my current setup.
Model SCH-I535
Android Version 4.1.2
Baseband I535VRBMA2
Kernal 3.0.30-861013
Build JZO54K.I535VRBMA2
Status
Netowork = Unknown
Mobile Network Type = 1xRTT.6
Service State = In Service
Roaming = Roaming
Mobile Netowrk State = Disconnected
My Phone # = 000-000-8561 (last 4 aren't even correct)
IMEI looks correct
IP Address = Unavailable
Thanks for any help/advice.
Pozman1 said:
I can't send text or phone calls after CWM recovery flash.
I initially rooted my i535 sg3 using this method http://forum.xda-developers.com/showthread.php?t=1840030
I then flashed 4.2.2 Pacman. Used this for a few days and everything was ok but battery life was horrible so I flashed, I think CleanRom, then Liquid RC1. I'm not sure where in the process of flashing but I noticed that my reception was weak compared to stock and then I couldn't send outgoing text or calls all together. I've searched everywhere and I have seen similar issues/symptoms but non of the fixes have worked for me. Here's my current setup.
Model SCH-I535
Android Version 4.1.2
Baseband I535VRBMA2
Kernal 3.0.30-861013
Build JZO54K.I535VRBMA2
Status
Netowork = Unknown
Mobile Network Type = 1xRTT.6
Service State = In Service
Roaming = Roaming
Mobile Netowrk State = Disconnected
My Phone # = 000-000-8561 (last 4 aren't even correct)
IMEI looks correct
IP Address = Unavailable
Thanks for any help/advice.
Click to expand...
Click to collapse
Have you tried odining back to stock? Somewhere along the way from AOSP back to TW you might have lost/changed some sys data.
Feels like it lost the IMEI, even if it looks correct. Getting stuck on roaming and possibly the weird phone number may mean that's what went wrong.
Sent from my SCH-I535 using xda app-developers app
sworld said:
Feels like it lost the IMEI, even if it looks correct. Getting stuck on roaming and possibly the weird phone number may mean that's what went wrong.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I was able to Odin back to a stock unrooted 4.0.4 rom but it did not fix the issue. Is there a good way to restore IMEI?
Did you try to reprovision after you used Odin to get back to stock 4.04? A lot of people have had success after doing that, including myself. Be warned, it will completely wipe your phone.
HHF2 said:
Did you try to reprovision after you used Odin to get back to stock 4.04? A lot of people have had success after doing that, including myself. Be warned, it will completely wipe your phone.
Click to expand...
Click to collapse
I'm somewhat new to this and have no clue what "Reprovision" does. I found this comment on one post "reprovision your device with dialer code *2767*3855#". When I dialed this it said that when roaming that you have to use an area code and then hangs up? I really hope I don't have to dish out $600 to Verizon! I'm at a loss right not.
You need to enable the hidden menu before you can use the reprovision code. Dial *#22745927 and enable the hidden menu. Now the reprovision code should work. You shouldn't have to hit send at the end of the code. It should work as soon as you enter the last digit. This is assuming you are still on ICS.
Pozman1 said:
I'm somewhat new to this and have no clue what "Reprovision" does. I found this comment on one post "reprovision your device with dialer code *2767*3855#". When I dialed this it said that when roaming that you have to use an area code and then hangs up? I really hope I don't have to dish out $600 to Verizon! I'm at a loss right not.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066731
I think I found a thread that has solved this for me.
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/show....php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
OMG THANK YOU GUYS!! This thread saved my sanity! I had flashed the latest MIUI 4.1.2 and wasn't a big fan so I flashed my backup and *POOF* no data! I had no clue how it happened (still don't fully understand it), tried every basic "go-to fix" in the book, and scoured the forums for two days without luck. The suggestions in Pozman1's last thread post to flash back to the VRALG1 4.0.4 ROM and the I535VRLHE radio did the trick! The only thing I had to do differently was use the *#7780# Factory Reset Code instead of the *2767*3855# Reprovisioning Code, for whatever reason that code just wouldn't work. Anyway, thanks again!
Thanks!
I spent all last night and most of this morning trying to figure out what was wrong with my phone. I was not connecting to the network and went through the forums searching for the solution to my problem. I odin'ed, flashed, prayed, hoped and then did it all over again all the way back to 4.04. until I landed here.
I was finally ready to give up, so I went to the Verizon site to see if my IMEI was listed and if it matched my phone. Both my phone and my wife's phone were different than the phones we actually have. I got on chat with verizon support and they fixed it right up. I got my 4g back. Now, I'm updating my way back up to the present.
I've been able to solve every problem I've had by lurking/searching these forums. I've been doing this for a couple years now. I really should have registered and started thanking people a long time ago. I have bought apk's off of google play and donated some beer money, but probably not enough. After I post this, I'll take some time and spread the thanks I owe.
I've registered and planted this response here so that if someone else is having the same problem, they might think to go check their account and make sure they've actually got the same phone their carrier thinks they do. Sometimes, it helps to start with the simple stuff.
Thanks to everyone!
I know people have been doing this for years on previous Sprint phones, but it doesn't seem to "take" on the Nexus 5. If you enter in 0.0.0.0 in the RTSP field and 0 in the port field, reboot phone and return back to the same screen, the sprint info is populated in there again. I have also tried to leave both fields blank and get the same result.
Anyone been able to successfully do this?
What does this do it again I remember doing this a long time ago on one of my other Android phones I can't remember exactly what it was for
Sent from my Galaxy Nexus
Ep3n3wp said:
What does this do it again I remember doing this a long time ago on one of my other Android phones I can't remember exactly what it was for
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1283229
Have you tried it yet?
Sent from my GT-P3113 using Tapatalk 4
I'm seeing the same issue. It wont save the settings after reboot.
wonder if this actually does anything positive or if it's an old wives tale??