Hey everyone.
My LG G2X is running Cyogenmod 7.2.
Just last week my phone apparently started to not be able to receive phone calls. I called T-mobile and told them about the issue, however they tried calling me and it went through without an issue.
I am lost for words, i've had people from AT&T and Verizon try to call me and no calls go through.
Any ideas?
Kind Regards,
Jordan
What baseband are you on? If you're on a baseband that is not supported by the ROM then you may need to flash one of these zip files to make your phone capable of making calls. See this thread: http://forum.xda-developers.com/showthread.php?t=1776843
chowdan said:
Hey everyone.
My LG G2X is running Cyogenmod 7.2.
Just last week my phone apparently started to not be able to receive phone calls. I called T-mobile and told them about the issue, however they tried calling me and it went through without an issue.
I am lost for words, i've had people from AT&T and Verizon try to call me and no calls go through.
Any ideas?
Kind Regards,
Jordan
Click to expand...
Click to collapse
If test calls come through, and calls from other t-mobile phones come through, then it is clearly a t-mobile problem, NOT a phone problem. There is nothing ON your phone that rejects only calls from specific carriers.
You will need to call them back with specific examples of people (phone # and carrier) who cannot call you. Perferably you will also have some examples (landlines, other carriers) who CAN call you.
You also need to make sure to have more than one example, otherwise it could be on the other person's side.
Armed with that information you can prove a pattern and that it is not your phone.
On the other hand, if it is random as far as whether a call comes through or not, then it could be either your phone or t-mobile. A pattern is what you're looking for.
Source of information: I was once a T-Mobile Tier 2 PDA Tech.
I am having an issue with my verizon Galaxy S3. Whenever I travel a little over two hours from home , I lose the ability to make or receive calls as well as text. I can still use the internet. I unregistered the phone and registered it under a different phone number under the same account, and the pho e works fine. Verizon can't figure out the issue. I'm wondering if anyone has encountered this problem. Thanks for any help. Joe G.
Also, I'm using the latest version of Clean ROM.
Do you have it set to lte only? or changed Apn's?
Under about phone, status, eri is supposed to be 5.
Cruzin the Galaxy SIII via SynergyRom/Anthrax kernels
That happened to my first GS3. Verizon could never figure out the issue and ended up giving me a replacement.
I think I have a similar problem with my MiFi Jetpack..after a certain amount of time it seems like it wigs out on me and won't work like it should. It only started doing it after it was unregistered and re-registered under a new number & sim.
Do you use the same SIM, or a new one ?
My problem is, other carriers don't get any texts but can get phone calls from me and I can, get there texts from them and they dont get my replies. Anyone on sprint gets them. A few of my friends have AT&T and they been getting on my s#&t why I never text them back.
I show them that I have msgd them back.
Has anyone else run into this problem?
Phone is stock not rooted and my girlfriend is still on an S3 and she don't have this problem.
My dad is on AT&T and has no problem receiving sms/mms. I got a friend on Verizon and another 2 on Straight Talk. No one has issues receiving my texts or mms.
Pimpin' Like Clinton
Sprint is sending me a new phone. I couldn't figure it out and they couldn't either
Welp got the new phone and the same problem. Sprint can't fix so they have me a 72 hour window for some one from tech support to call me.
Has no one had this issue ever?
Turns out I was blocked by AT&t and T-Mobile. Don't ask how but it's fixed now
I spent over 2 hours last nite with att reps trying to enable numbersync to work between the s3 and s8 phones.. the s8 phone is an unlocked phone (not bought through att), only to find out today via another rep that the phone must be bought via ATT or truly att branded.. which i find a bit absurd, as i think others have succeeded..
Is this really the case.. anyone know or have this same experience?
Specifically this error would appear after going through the get started via the watch then on the phone (after creating a seperate accessid):
Oh darn! We can't enable device syncing on this phone. Want to find out more? Call us at 800.331.0500 so we can help.
(MSSITWINREL12)
If this turns out to really be an unlocked phone issue (which is a bit ridiculous), i think i read that it might be possible to take my sim card out of that phone and put in another phone that is att branded, enable number sync then put the card back in my s8 and go from there
Thanks
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
pasco8525 said:
The phone does not have to be AT&T branded, I have a T-Mobile Note 4 and until the last update numbersync worked. Updated my S# over the weekend after avoiding it for as long as possible, and now numbersync is no longer an option on my S3.
Click to expand...
Click to collapse
Thanks for the reply.. your saying you had an unlocked tmobile phone on att and it was working till a recent tizen update then?
The rep further told me to take the phone to the best buy samsung experience store and have it flashed with the att firmware to get around this issue.. maybe not needed then? (which i assume means a wipe and possibly lose my unlock)
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
karlkarloff said:
I had the same problem with my Gear S3 and my Axon 7. Worked on for a solid hour with an ATT rep in store and another hour on phone with someone else. Finally it was determined that it wouldn't work on an unlocked phone. Haven't tried the sim swap with an ATT branded device yet, but if I do, I'll let you know if it works.
Click to expand...
Click to collapse
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
markm75 said:
Spoke to an att rep again today who called me.. basically in my case the 950U1 s8 phone.. because its this model it wont work with numbersync they say.. they also contradicted the previous reps suggestion of taking the phone to the samsung experience place and having the att firmware flashed on it (or doing it at home).. saying it wont help.. that they need HD voice provisioned and it wont let them provision it (the phone wont).. they said swapping the sim card to a real att phone only may help for a short period, till the system does a sweep, sees a non att phone and reverts it (same with just adding the imei to the database).. There is also a good chance the recent update to either the s3 or the samsung s8 caused numbersync to do a detection for unlocked phones and not allow this (they indicated).
They said i could still try doing the firmware flash but it probably wouldnt work (i dug around online trying to find out which flash it would be and i didnt get too far, short of going to the store to do it at best buy samsung experience)
Really sucks, as the alternative, if i were that desperate to enable this feature (i dont think i am willing to go this far) would be to sell the old phones and get new att branded ones.. end up costing me the price of a new watch in the mix just to do that
Click to expand...
Click to collapse
.
When I first bought the watch it was for the numbersync feature. My first problem was even though the Samsung rep and the bestbuy rep said that it would work with my Note3, it did not. took several calls and many hours of trying to figure out the HD Voice (VOlte) provisioning. Bought a TMobile Note 4, rooted and rom'ed this worked to setup numbersync. the only problem was it would occasionally turn off numbersync, this occurred about once a month. Then if failed completely said that this line is not accceptabl;e for numbersync. this was after about six months. Discovered that it appeared to be age of firmware related, I was on a TM firmware that was several updates out of date. When I odin flashed the latest firmware numbersync worked again until the recent update to 3.0.0.1 on the gear firmware. Now I have the line not acceptable for numbersync again. I'm going to try to update firmware again to see if that works. If not I will probably look to change carriers to TM. will cost the price of a new watch, but will get me out of AT&Ts locked boot loader.
BTW, setting up numbersync on a different phone and switching back will not work, Tried several times and as soon as you turn on the phone that is not HD Voice capable with your SIM card in it the system sees it and turns off numbersync almost instantly. went throught that trying to get my Note 3 to work.
In all my experience the Samsung and AT&T reps were not a good resource. Numbersync does not appear to be a very popular feature and they do not know much about it.
pasco8525 said:
.
When I first bought the watch it was for the numbersync feature. .
Click to expand...
Click to collapse
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
markm75 said:
My main motivation for it has been that.. someone correct me if this isnt accurate.. if your phone dies or is off.. when you dial someone from the watch or text them it will still show the cell phone phone number, not the watch phone number as it does now if bluetooth isnt on.
I'm in the process of gathering the files i need to do the att firmware flash and hopefully hd voice works then (as others say it has).
Click to expand...
Click to collapse
Yes, that is the whole point of numbersync. The watch uses the phones number not it's own.
Tried updating to the latest firmware and a ROM based on it. No luck still get a rather comical response "Oh darn! We can't enable device syncing on this phone. " worked until the tisen update.
There also seems to be confusion on numbersync with the att reps.. one person told me the watches dont need their own numbers.. that numbersync is all we need (but how would the watch make a call if the phone is off).. another said yes they need external numbers for number sync or solo
edit: i see your last post.. so the latest reps are correct then.... so they assigned us numbers and $10 access fees each with activation fees for no reason basically.. ugh
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Just a quick note...i too spent 3 hours in an AT&T store trying to get numbersync to work..., finally returned the S3 Frontier cancelled the number in it and left frustrated...i now have a GS8 unlocked on AT&T through my work...that is synced to a Verizon Gear S3 Classic lte and i simply use call forwarding with YouMail. If i do not answer my phone after 3 rings it gets sent to my watch and if I still do not answer then Youmail picks it up..If I call out or text with the watch separately then I just let my customers know that I have 2 numbers 1 for my cell and one for their watch. I just don't think AT&T is ready for the Numbnersync technology yet and they just don't care enough to train their own people on it, sad as it is a good promise...
Sent from my iPad using Tapatalk
pasco8525 said:
The watch has to have it's own number, that is it's address on the network. Without it numbersync would have no way to send calls to it. Same as with the LTE enabled iPads they could not make a call, but had to have an address on the cellular network.
Click to expand...
Click to collapse
I meant phone number.. are you saying phone number? After the rep said i didnt need a phone number for each watch, she credited me back the cost of the two lines and said just to contact them that they would enable the numbersync once i had the phones ready.. I'm assuming number means imei, which they still have in the system.
Yes each watch has to have it's own phone number. I believe this is another case of AT&T rep not understanding number sync.
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
markm75 said:
I managed to firmware update so that i have the att bloatware (didnt even need reset, all software was kept).. i confirmed HD voice is working but WiFi calling throws an error to contact ATT.. hd voice was the key for numbersync.. however.. despite this.. and 2 hours on the chat line with ATT.. i still get an error when you do the s3's get started numsync and it opens the page on the phone.. the oops, device sync cant work with your phone (which went from a 950U1 to a 950U btw, which is good as well).. They escalated to another backend team, but i highly doubt they will get it working.. most likely they'll still complain that my phone (was) an unlocked phone, despite adding the att firmware to it.
Click to expand...
Click to collapse
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
markm75 said:
Update here.. i managed to get everything working by going with a new sim card.. wifi calling works now.. and i was able to complete numbersync setup.. the only remaining issue i have is that my callerid seems to be blocked on the receiving end.
Click to expand...
Click to collapse
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
eaglerugby04 said:
With the Firmware did you have to go through the full process where you changed the CSC and flashed the ATT firmware? Currently I am running a Sprint phone that is unlocked an running the US Unlocked firmware. Even running the ATT firmware they still were not able to get HD Voice or WiFi calling working for me.
Click to expand...
Click to collapse
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
Thanks. It sounds like the latest firmware they did seems to fix some of the issues from bringing a non-ATT phone over but does not resolve everything. It looks like I won't be able to do this though. ATT and the ebay seller are unable to clear the ICCID on my watch, I have to sadly do a return now.
Kinda unrelated, yet ATT was horrible even for normal Sammy phone/watch. After dumping ATT service/hardware for various reasons a few moths back... Sammy watch/phone from Verizon hardware/service works flawlessly. Am carrier neutral, but one works reliably, one didn't.
BTW, Sammy pay via watch hiccuped via ATT at times, yet works flawless via Verizon.
markm75 said:
The full steps, or mostly full.. are here in this thread..
The short of it was that i only ran regular odin at first.. just did HOME_CSC (using the verizon firmware which covers all carriers).. then rebooted the phone and did all the check boxes and the regular CSC.. after rebooting nothing was wiped and att bloatware was there... at this point hd voice was working.. wifi calling wasnt.. so i went to the store, got a new sim card today, then wifi calling was working.. numbersync took the code on the phone without error.. however.. now i'm realizing it isnt really working.. when i turned the phone off, and texted, it showed my s3 phone number.. and my callerid is still botched.. i think att botched something in this whole process.. so yet another call to them needed.
Click to expand...
Click to collapse
well 5 chat people later they finally fixed the unknown callerid issue.. apparently there is an internal back end feature for numbersync regarding it set to active and on.. both toggles were on.. the rep removed the "on" and now my callerid shows my number when calling from my phone (and from the watch when watch is in solo mode too).. everything works! :laugh:
Before I get on hold with AT&T tech support, I wanted to ask the experts if anyone else has had this issue.
I bought my new A32 about a month ago. It was branded for T-Mobile, but was unlocked already.
In the past, I just put my AT&T sim card in the new phone and it was ready to go (I don't mind the T-Mobile start screen).
It worked fine for a couple of weeks, then T-Mobile sent out an update and it stopped receiving texts. AT&T put in a new sim card, and that fixed the text problem, but now it won't make or accept phone calls. Calls go right to voice mail. When I try to dial a number, it just disconnects immediately.
Anyone have any idea of what could be wrong?
Thanks.
You bought an unlocked phone for a different carrier, unlocked by a third party, and updated it.
the phone can have some issues if...
1. the software version running is different (each carriers may have different versions they approved and pushed to update for their customers, hence not supporting some versions)
2. If you have unlocked and the carrier is some minor name carrier and not the main ATT then the phone may not be supported by them.
You should backup all your data to either Google or Samsung account or whatever option is shown... then ask to have the device flashed with the latest market software version from ATT. Hope this helps.
TheImpalaKid said:
Before I get on hold with AT&T tech support, I wanted to ask the experts if anyone else has had this issue.
I bought my new A32 about a month ago. It was branded for T-Mobile, but was unlocked already.
In the past, I just put my AT&T sim card in the new phone and it was ready to go (I don't mind the T-Mobile start screen).
It worked fine for a couple of weeks, then T-Mobile sent out an update and it stopped receiving texts. AT&T put in a new sim card, and that fixed the text problem, but now it won't make or accept phone calls. Calls go right to voice mail. When I try to dial a number, it just disconnects immediately.
Anyone have any idea of what could be wrong?
Thanks.
Click to expand...
Click to collapse
I have the same problem. Acquired a NIB T-mobile Samsung A32 that is confirmed unlocked but doesn't work on PuretalkUSA when it came to calling or receiving calls. Texting and websurfing works but call get immediately terminated and calls made to the phone go automatically to VM. I spent three hours on the phone with Puretalk tech to make sure the settings were correct. The tech had me attempt to update the carrier configuration version to no avail. It refused to update and remained at version 0.0.0. I then stuck an T-mobile sim in the phone and noticed that the carrier config version change to some series that I currently do not recall. However, I still could not make or receive calls. I then purchased a prepaid ATT sim and stuck it in the phone. The carrier config version changed back to 0.0.0 but I was able to make and receive calls. I'm putting one more call in to puretalk to make sure I've tried everything before giving up on the phone.
I recommend that you check this guy's video on youtube. He seems to be on to something: