Database Info

[Q] Verizon SMS not coming through...

Seems to be a really odd issue that I have no idea how to fix. About 3 days ago, I realized that I didn't seem to be receiving texts. At first, I thought it was from everybody and an issue of my phone. Then I realized that the people I had all texted were Verizon customers, so now I don't quite know where the issue is.
So... I had everybody I knew text me and report what carrier they have. All SMS messages received my phone except the people who have Verizon (for the record, I received texts from Sprint, US Celluar, AT&T, and T-Mobile networks just fine). I can send to them and they receive it. But when they send to me, it seems to go through on their end just fine but I never receive it. And as I said, this is something that only started a few days ago. All their texts were reaching me just fine before that.
It's worth noting that if I have them send me an MMS message, that reaches me just fine. It's only Verizon SMS messages that don't actually make it to my phone.
The only thing I've done to my phone around that time is "fixed" the APN data so it had all the T-Mobile information instead of being mostly blank as it had come. As I thought that might be the issue, I changed everything back to the way it was before, but that hasn't helped at all.
So does anybody have any idea what the problem might be? I thought it must simply be Verizon, but those people who can't send me SMS messages can still text other people just fine apparently. I haven't had the opportunity to thoroughly test that with different carriers like I have with my phone, but for the moment I'll take their word for it.

Gamesoul Master said:
The only thing I've done to my phone around that time is "fixed" the APN data so it had all the T-Mobile information instead of being mostly blank as it had come. As I thought that might be the issue, I changed everything back to the way it was before, but that hasn't helped at all.
Click to expand...
Click to collapse
You filled in what?

Gamesoul Master said:
Seems to be a really odd issue that I have no idea how to fix. About 3 days ago, I realized that I didn't seem to be receiving texts. At first, I thought it was from everybody and an issue of my phone. Then I realized that the people I had all texted were Verizon customers, so now I don't quite know where the issue is.
So... I had everybody I knew text me and report what carrier they have. All SMS messages received my phone except the people who have Verizon (for the record, I received texts from Sprint, US Celluar, AT&T, and T-Mobile networks just fine). I can send to them and they receive it. But when they send to me, it seems to go through on their end just fine but I never receive it. And as I said, this is something that only started a few days ago. All their texts were reaching me just fine before that.
It's worth noting that if I have them send me an MMS message, that reaches me just fine. It's only Verizon SMS messages that don't actually make it to my phone.
The only thing I've done to my phone around that time is "fixed" the APN data so it had all the T-Mobile information instead of being mostly blank as it had come. As I thought that might be the issue, I changed everything back to the way it was before, but that hasn't helped at all.
So does anybody have any idea what the problem might be? I thought it must simply be Verizon, but those people who can't send me SMS messages can still text other people just fine apparently. I haven't had the opportunity to thoroughly test that with different carriers like I have with my phone, but for the moment I'll take their word for it.
Click to expand...
Click to collapse
First of all, APN settings have NOTHING to do with regular SMS messages. Secondly, if you only cannot receive from one carrier, it is a network issue. I work in tech care, and believe me, it's more common than you might think. Call tech care and they will file a ticket with engineering to get it fixed. Shouldn't take too long either!

Call T-Mobile that happened to me when I had a Nexus S. They fixed it
Sent from my HTC Sensation 4G using Tapatalk

Thanks. I called T-Mobile today, and the guy did something (I don't know what) that required me turn off my phone, but that didn't work. He commented that they have a note in the system about T-Mobile phones not receiving texts from Verizon people who have signatures set, but that's obviously not the problem either.
So he was going to send me to advanced support, but then decided that because I had ported my number over, that might be the issue. No idea how he came to that conclusion since everything worked perfectly fine until a few days ago, and the issue is almost certainly not porting-related.
But regardless, he sent me to some hard-to-understand guy (unlike the first guy) that decided that they needed to rebroadcast some kind of programming/service signal to my phone, and he said "I guarantee that by tomorrow, your service will be completely working". Also mentioned it having to take up to a full day (which it never does for me), and I *thought* he said something about not having service for a while. Except that it's been about 8 hours now and I have yet to lose service, nor is it fixed though.
So basically, when I wake up tomorrow and see that it's still not working properly, I'll be calling them back and speaking with advanced support to hopefully find a better answer for why this is happening to me (and nobody else apparently?).

Gamesoul Master said:
But regardless, he sent me to some hard-to-understand guy (unlike the first guy) that decided that they needed to rebroadcast some kind of programming/service signal to my phone, and he said "I guarantee that by tomorrow, your service will be completely working". Also mentioned it having to take up to a full day (which it never does for me), and I *thought* he said something about not having service for a while. Except that it's been about 8 hours now and I have yet to lose service, nor is it fixed though.
So basically, when I wake up tomorrow and see that it's still not working properly, I'll be calling them back and speaking with advanced support to hopefully find a better answer for why this is happening to me (and nobody else apparently?).
Click to expand...
Click to collapse
Yeah the people you spoke with did not know what the hell they were doing apparently. They have to file a trouble ticket in Tech Care so engineering can get it fixed for you.

Yeah, when I called them back yesterday, they ended up doing just that. So hopefully by tomorrow, they'll have some kind of idea and hopefully a fix.

[q] att htc vivid issue

Hi I am using the ATT HTC VIVID
I bought this phone last Nov 11, and I stated noticing my phone was not receiving any calls if I stay at home(jersey city). If anyone calls to my number it will not connect at the same time it will not sent to voicemail also. It will say "call couldn't be completed".
After 2 months fight with ATT, they tried
1. they did a factory reset on my phone - it didn't help
2. changed the sim card - it didn't help
3. finally they replaced a another HTC vivid
even that didn't help
finally they said there was issue in near to my home and they fixed it.
now i a started receiving calls but now the issue i am having is, if I call to my number it will not connect first time it will go to voicemail, and second time if i try then it will ring. (First time also my phone is idle) This is happening randomly and ATT is not helping on this situation. As per them I am not able to replicate when they were testing on my phone.
Because of this issue I am missing calls which is making me really frustrated. After three week of research I found this is happening in not only near to my home its happening at my work place (NYC) and if I go around also its happening.
Can someone please give some advice to fix the issue that would be really great

Sounds like an issue that IMEI is conflicting :'(
Low end cheap bro.....

First of all, thanks for the response
But I am not getting the answer clearly
Can you please explain more and what should I do
Do I need to contact ATT or something

[Q] G2X with Cyogenmod 7.2 not able to receive calls

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.

[Q] Constant Voice Roaming Notification

I have been trying to find a solution for this since I activated the phone (Verizon HTC One (M8)) on Friday March 28th.
The phone constantly displays voice roaming notification. It includes the roaming triangle and you cannot swipe it away from the notifications. My only solution is to click the app info and select force close the app. This gets rid of the notification but the roaming icon is still visible above the 4G signal. I have gone to VZW went threw the typical settings changes with an inevitable swap of the phone for a newer device resulting in no success. VZW put in a trouble ticket but i haven't heard back from them and it has been 5 days already. I'm going to be contacting them soon.
For whatever reason the ERI Version is displayed as "not available." To me this seems like a software bug with the radios. They will probably push out an update to patch it but I don't know if I want to wait for it. VZW seems to take forever to push out updates
This seems to be a semi common and known issue by VZW from what I have read on other threads on other forums.
To my knowledge the only solutions have been wiping the partition cache in the recovery and swapping the device for a new phone.
What is everyone else's experience with this? Are there any solutions? Any suggestions?
Thanks in advance all!

htcdude123 said:
I have been trying to find a solution for this since I activated the phone (Verizon HTC One (M8)) on Friday March 28th.
The phone constantly displays voice roaming notification. It includes the roaming triangle and you cannot swipe it away from the notifications. My only solution is to click the app info and select force close the app. This gets rid of the notification but the roaming icon is still visible above the 4G signal. I have gone to VZW went threw the typical settings changes with an inevitable swap of the phone for a newer device resulting in no success. VZW put in a trouble ticket but i haven't heard back from them and it has been 5 days already. I'm going to be contacting them soon.
For whatever reason the ERI Version is displayed as "not available." To me this seems like a software bug with the radios. They will probably push out an update to patch it but I don't know if I want to wait for it. VZW seems to take forever to push out updates
This seems to be a semi common and known issue by VZW from what I have read on other threads on other forums.
To my knowledge the only solutions have been wiping the partition cache in the recovery and swapping the device for a new phone.
What is everyone else's experience with this? Are there any solutions? Any suggestions?
Thanks in advance all!
Click to expand...
Click to collapse
It is a software bug, Verizon is no longer replacing the phones that this happens on, an update will be coming. Ask this according to a business/ government support agent I talked to yesterday. He said they were no longer swapping out phones, as he took my address to send me a brand new one. He said it was a known issue. Take that for what it is worth.....
Sent from my HTC6525LVW using Tapatalk

SDC_Bolts said:
It is a software bug, Verizon is no longer replacing the phones that this happens on, an update will be coming. Ask this according to a business/ government support agent I talked to yesterday. He said they were no longer swapping out phones, as he took my address to send me a brand new one. He said it was a known issue. Take that for what it is worth.....
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I know this is a software bug. When I called VZW when I first had the issue the associate told me this. But he also said this issue didn't effect all the devices. He suggested taking it in and swapping the phone for another. I am just frustrated that VZW doesn't have their stuff together because yesterday I was on the phone with another person to check up on the situation since I hadn't heard from them in 5 days. She told me that they had fixed the issue, it was a manufacturing defect and new phones were being shipped out. Sounds like she didn't know what she was talking about because she couldn't ship me a phone, not unlike you situation. However she assured me that the VZW stores were shipped "new" phones with this issue has been fixed. She said to go to the nearest store and swap out the phone again.
I got to the store and they basically told me to piss off. Even though this lady put notes in my account to swap the phone. I just wish VZW would inform all their employees of this issue so they are all on the same page because every VZW employee is saying something different to me and its really starting to piss me off. One employee is saying its a hardware issue the other is saying software. GET IT TOGETHER!
I'm almost to the point where I want to take the phone back entirely.
Sorry just have to vent a little bit. :laugh:

I understand, I really debated on this phone or wait for Z2 (if coming to Verizon), G3,possibly even S5. But decided on build quality of this phone. Buddy at work got his the day after release and has had no problems at all. Only issue with mine is the ERI voice roaming deal, just annoying really. The guy on the phone did mention that newer phones would have the issue resolved but he eluded to it being a software issue and was going to have them send me one of the newer models they had in. Hope you get your situation resolved.

htcdude123 said:
I have been trying to find a solution for this since I activated the phone (Verizon HTC One (M8)) on Friday March 28th.
The phone constantly displays voice roaming notification. It includes the roaming triangle and you cannot swipe it away from the notifications. My only solution is to click the app info and select force close the app. This gets rid of the notification but the roaming icon is still visible above the 4G signal. I have gone to VZW went threw the typical settings changes with an inevitable swap of the phone for a newer device resulting in no success. VZW put in a trouble ticket but i haven't heard back from them and it has been 5 days already. I'm going to be contacting them soon.
For whatever reason the ERI Version is displayed as "not available." To me this seems like a software bug with the radios. They will probably push out an update to patch it but I don't know if I want to wait for it. VZW seems to take forever to push out updates
This seems to be a semi common and known issue by VZW from what I have read on other threads on other forums.
To my knowledge the only solutions have been wiping the partition cache in the recovery and swapping the device for a new phone.
What is everyone else's experience with this? Are there any solutions? Any suggestions?
Thanks in advance all!
Click to expand...
Click to collapse
I had this issue when I bought the phone on launch day, spent three hours on the phone with tech support and finally swapped phones the next day. Now I see it's a known problem. Verizon feels you aren't charged for voice roaming so it's okay to wait for a fix but it's nuts, I think it will drain your battery a little faster as well.

pj1980 said:
I had this issue when I bought the phone on launch day, spent three hours on the phone with tech support and finally swapped phones the next day. Now I see it's a known problem. Verizon feels you aren't charged for voice roaming so it's okay to wait for a fix but it's nuts, I think it will drain your battery a little faster as well.
Click to expand...
Click to collapse
pj did the phone swap fix your issue? or do you still have the same problem.
As for the battery it might be drained faster but its an overall astonishing improvement over my Galaxy Nexus I had before the HTC. I would have to charge that 2-3 times a day depending on use. Currently my phone lasts all day. its off the charger from about 5:45 in the morning to 9:30-10 at night and I might have 30-40% battery left at that point.

htcdude123 said:
pj did the phone swap fix your issue? or do you still have the same problem.
As for the battery it might be drained faster but its an overall astonishing improvement over my Galaxy Nexus I had before the HTC. I would have to charge that 2-3 times a day depending on use. Currently my phone lasts all day. its off the charger from about 5:45 in the morning to 9:30-10 at night and I might have 30-40% battery left at that point.
Click to expand...
Click to collapse
I had this very same issue. Troubleshot with all kinds of people. Even used the Sim from my wife's. Same thing. Its the phone/software. Took it back and swapped it and problem solved immediately.
Tech support was unable to contact the phone. Under about->software in settings there was no eri number (all my other phones have 5). It wasn't just voice roam but data roam as well.
Sent from my Nexus 7 using Tapatalk

I am still convinced that this is software related. but this is the latest conversation I had via chat with VZW. She is claiming hardware.
Please excuse my typos I was at work and trying to double task at he same time.
Please hold for a Support Representative to assist you.
Thank you for contacting Verizon Wireless.
Your Chat Session ID is --------------------------.
My name is Lain, how may I assist you?
Lain: Good morning what can I help out with today?
HTCdude 123: I have an on going issue with my phone that needs to be addressed
HTCdude 123: there are notes on my account about the issue that I am having on my htc one m8 with the voice roaming
Lain: Sorry to hear that you've been running into some problems with your phone and voice roaming HTCdude 123, especially with a brand new device like the M8.
HTCdude 123: the last person I talked to wanted me to go to a Verizon store and exchange the device for another. She put notes in my account to make sure they would even though I have already exchanged the phone under the 14 day no hassle but the store wouldn't do anything
HTCdude 123: i want to know why i would be told something from Verizon by one person and another from someone in the store
HTCdude 123: I just want a phone that works
HTCdude 123: before i am forced to keep this phone because it passes its 14 day window
Lain: Thats terrible to hear and certainly not what should have happened! If you are having problems with your phone and you are within the 1st 14 days of having it the store you got it from should have no problems exchanging it for the same type of phone. Can I ask what happened when you went in?
HTCdude 123: i purchased the phone online
HTCdude 123: after getting the phone by mail i activated and had this issue. i called vzw they couldn't fix it and told me to go to a store to exchange it. i went to one store. they exchanged the phone and i still had the same issue. they couldn't do anything so they filed a trouble ticket and said they would get back with me
HTCdude 123: they never did
HTCdude 123: so 5 days later i contacted again asking about the status of the trouble ticket
HTCdude 123: the lady said there was an issue with the phone and it has been addressed all phones shipping out now are fixed. she was going to send me a replacement but there were none to send so she said to go to another store and they should swap the phone out again
Lain: Thanks those are good details to have, though of course an annoying problem to run into with a new phone.
HTCdude 123: i went to another store on my way home from work and the guy i spoke to woulnd exchange the phone because it had already been exchanged once. he told me it was a software update that needed to be addressed
Lain: So the store told you that there was going to be a software update, let me look and see what I can find on this. Can I have a minute or two to see what I can find?
HTCdude 123: yes
Lain: Thanks its appreciated
Lain: Thanks for your patience I'm still looking to see what I can find on any software updates on here
Lain: Thanks for your patience while I was checking on this and I do not show any details about a software update being in the works to resolve this. What I show on here is that we supposed to replace the device which since you are within the 14s of having your phone. I'm uncertain why the store said that they would not replace it for you and I'm sorry that this happened. I would recommend reaching back out to the store and I will note the information on here regarding this to help.
HTCdude 123: and what should happen if the store does the same thing?
HTCdude 123: you are telling me you don't see anything about any roaming issue with this phone?
HTCdude 123: no issue at all with the device?
Lain: The thing is that they shouldn't do so. The direction that we have been provided with on this issue with roaming is that it was a production issue and not software related and that replacing the device needed to resolve this
HTCdude 123: so you know that this is not a software related issue at all. its indeed hardware
Lain: Based off of everything I can see on thats right
HTCdude 123: where do you get your information? shouldn't the stores all have the same information? should Verizon not have pulled all of the old phones off the shelves and put out new phones with the issue resolved?
HTCdude 123: im asking all these questions because the last person i talked to online told me the same thing and the person at the store i went to exchange the phone told me something completely different
Lain: Yes all of our direct stores should have had this information and I wish that I could say why they did not. I'm just sorry that they did not and that you ran into a problem when you went it. I will make certain that all of this is noted on here to help when you go into the store. So long as you are within the 14 days of having this phone they will be able to help replace it.
HTCdude 123: i should be able to replace the phone even though i have replaced it already? because i was told that you can only do that once.
Lain: So long as you are not trying to go to a different model of phone and you are within the 14 day period they should be able to still replace it for you.
HTCdude 123: how can i be certain that they have a fixed models in stock?
Lain: Thats a great question and they should have them. What we have been told is that this problem was linked to a small number of the M8's
HTCdude 123: but the current shipment they have might be part of the batch with the same issue no? will they just keep replacing my phone till they find a good one
Lain: Thats an answer I do not have, though I wish that I did. I would expect at this point that the store should have received additional M8's to use due to this so you should not have to go through multiple replacements from here on this
HTCdude 123: ok. thank you for your time
Lain: Glad to help!
Your chat transcript will be sent to ---------------------.com at the end of your chat.
Lain: Anything else that I can help out with today?
HTCdude 123: no thanks

Issue Temp Fixed
Ok guys, please hit the thanks button if this works for you.
Go to settings->App Manager->All-> scroll down to "Phone"-> click force stop.
It comes back after reboot, but at least its a start!

I would say this issue has now been solved. I ended up getting my phone exchanged again and the issue went away. 3rd time is a charm right? Either way I believe there was an update to the VZW M8 a month or so after its release that addressed this issue.

Call Waiting?

Not sure if this is a carrier thing or the device? I switched from AT&T to Verizon when this device came out. When on a call and a call comes in I place original call on hold and answer incoming call. If I then hang up on that call it hangs up on both people. Is there no call waiting?
Never had to tell someone they need to hang up so I can switch back to the other person on hold. Seems like either a bad carrier issue or bug? Never had CDMA carrier before so hopefully not an issue I'm stuck with?

deeznuts said:
Not sure if this is a carrier thing or the device? I switched from AT&T to Verizon when this device came out. When on a call and a call comes in I place original call on hold and answer incoming call. If I then hang up on that call it hangs up on both people. Is there no call waiting?
Never had to tell someone they need to hang up so I can switch back to the other person on hold. Seems like either a bad carrier issue or bug? Never had CDMA carrier before so hopefully not an issue I'm stuck with?
Click to expand...
Click to collapse
This is a CDMA bug since it happens with Sprint as well. I was like you, I switched over from AT&T about 4 years ago. It absolutely drove me crazy for about a year until I just finally gave up and accepted it. I'm hoping that things will chnage when VoLTE becomes the standard:fingers-crossed::fingers-crossed::fingers-crossed:
UPDATE:
http://forums.androidcentral.com/sp...nd-just-one-call-while-another-call-hold.html

There is a solution on wikipedia
mademan420 said:
This is a CDMA bug since it happens with Sprint as well. I was like you, I switched over from AT&T about 4 years ago. It absolutely drove me crazy for about a year until I just finally gave up and accepted it. I'm hoping that things will chnage when VoLTE becomes the standard:fingers-crossed::fingers-crossed::fingers-crossed:
UPDATE:
http://forums.androidcentral.com/sp...nd-just-one-call-while-another-call-hold.html
Click to expand...
Click to collapse
This just worked for me
https://en.wikipedia.org/wiki/Call_forwarding#Keypad_codes

easilybigger2 said:
This just worked for me
https://en.wikipedia.org/wiki/Call_forwarding#Keypad_codes
Click to expand...
Click to collapse
What worked? Must have not seen the solution reading the link.

Keypad Code
deeznuts said:
What worked? Must have not seen the solution reading the link.
Click to expand...
Click to collapse
If you have Sprint dial *38 and/or *720 to restore your call waiting. And for other mobile companies ##21#. But you can read through and find the correct deactivation. The problem happens because somehow call forwarding was active. I think it happened for me when I used my sprint number as my Google Voice number.