Okay, so I switched from Verizon to AT&T to purchase this phone and for that reason I am unsure if the issues I am having are normal for AT&T or if it's something with the phone.
Whenever I get an incoming call, I hear the phone ring at least once maybe even twice before the screen wakes up for me to answer. Is this happening to anyone else? This issue definitely seems like a software thing not a network thing.
When I make outgoing calls there's about half of a second to a second delay before the call connects. This I feel is probably more of an AT&T thing than a phone thing but again I wanted to ask.
Please let me know if you have had any similar experiences.
Thanks in advance!
Related
A few weeks ago I got a HTC Desire on Virgin Mobile (I believe they use T-Mobile's network) in the UK.
I'm having a bit of a problem with it, though. At seemingly random points, if somebody tries to phone me, it will go straight to my voice mail. If I then try to phone them back it will work. And usually, if they try to phone me back after that it will work too.
At first I thought it might be a problem with my phone being on standby, as that's when it seems to happen the most. But I have received calls when it's on standby and I've also had a few calls go straight to voicemail when the phone isn't on standby too.
Does anyone have any ideas why this might be? I've tried looking through the phone settings for anything obvious that could be causing this problem but I can't see anything.
same thing here
weird problem, kind of a biggy, my phone wont receive calls. I've run through several pages of google search over this issue, no answer, though I came across a few people with similar issues. I figured xda would be my best bet, if you guys can't help me...
Everything else works great, web, email, sms, outgoing calls, everything but incoming. This is kind of a big deal, I sort of need my phone to be working. When I get an incoming call, the phone vibrates, rings once, then goes silent. There's nothing on the caller id, but I did note that the signal drops to zero when it rings, dropping the call. From the other end, you just get cut off, it doesn't direct you to voice mail even.
I am currently running paragon rc6 rom, but just swapped over from the phoenix 5.2 rom tonight, as I mistakenly thought the issue was with the rom, but considering that it has continued even after flashing a new rom, it would seem to be something else entirely.
I don't know what the issue is, I swapped sims with my wife's phone, worked just fine calling her phone with my sim, but my phone still wouldn't work with her sim in it.
I have had the battery in and out a half dozen times in the past 24 hours, so I don't think that's going to fix the issue......I don't know what else to try. Can't very well call Rogers since they'll just blame the issue on the fact that I was screwing around with my phone, and since it flashes back to a stock at&t confige, I can't very well flash it back and pretend I never did anything
appreciate your help, stressing me out a little, need my phone for work, and my wife will have my balls if I broke it
My S3 has been giving me a no sim card issue. It happens when I try to text or make a call. I then have to wait approximately 30 seconds for it to reconnect then try to send the text or make the call again. This is very annoying. So annoying that I am thinking about taking the phone back into verizon and getting a different phone.
I have read others on the net that have had this issue as well. Are there different radios or is there something else I can do to resolve the issue? I like this phone but this 1 issue is ruining it enough to where I am thinking about trading it for a different model.
I got that after having the phone for about a month the first time last night when I received a call. It asked if I wanted to accept my friends call or send to voicemail. Then it started flipping out with no SIM card notification and screen turning off and refusing to stay on. Had to reboot to fix the issue. No idea what, but something went terribly wrong and definitely scared me. Network here gives all sorts of trouble on any 4G phone.
I'm currently using the 3g AT&T Galaxy Watch S2 with a NumberSync on and for whole day, I wasn't able to get any calls.
Whenever someone calls me, it directs to 'this number cannot receive a call.'
It's weird since I can still receive a text message and I can still call from my end, just unable to receive any call, not even a voicemail. (Not getting on my phone and my watch)
And when I disabled the NumberSync, my phone suddenly worked like a charm.
NumberSync has been working nicely until today and I'm wondering what's going on.
Anyone has the same problem as me?
P.S. I talked to AT&T Customer Support for like 2 hours and they were not able to solve the issue. What my rep told me was it seems like an error from the AT&T Service side.
Mine did that too today!!!
So I found a quick fix to this issue, I turned the bluetooth off on my watch (with NumberSync On) and it seems working.
And the watch only says "Connected Remotely AT&T" rather than connected with bluetooth.
BTW, when I tried the combination of Bluetooth on + NumberSync Off, I couldn't get a call. It might have been just one day but at least this combination used to work when I found the problem 3 days ago. Now it just doesn't.. Only option I have for me right now is to completely disconnecting with bluetooth.
I have no Idea why there's a problem between having bluetooth on and getting a call.
This really disturbs me since disconnecting with bluetooth limits a lot of stuff, like I cannot control my phone music on my watch ..
I don't know who's to blame as in AT&T or Samsung but I hope this issue gets fixed.
P.S. I actually got an exchange on my watch thinking it might be a manufacturer error but nope, same problem.
paoloroeseke said:
Mine did that too today!!!
Click to expand...
Click to collapse
I found out rather the hard way, luckily not in an emergency or anything, that my HTC U12+ will not put calls through to 911. Actually before I got the phone I had read some posts about it and knew that I would have to go to Verizon to have the messaging issue fixed right out of the box, so done and done. Meanwhile several months into my ownership I had to call 911 for an accident I witness, luckily not life or death or anything, and it just said dialing. Never rang, never left the dialer screen, which displayed a circle with exclamation point and that was it. I used my son's phone to call and got right through. Meanwhile I thought, hey I'll probably just have to go the Verizon and have them flip a switch just like with the messaging, but they said it wasn't on their end. Told me that it appeared to be a known issue, after doing some web browsing, and there was nothing they could do for me. So now I have a phone that won't do what any phone with a charge, no service and no SIM will do. A quick search of my own didn't reveal any known issues to me but I did find a help page about it at HTC and it said, Make sure you have a network signal, open the dialer, dial your local emergency number and press call. Thanks HTC for explaining how to make a call. All of these years and I've been doing it wrong. I've never once checked to see if I had a network signal before making a call. SMH. Anyway, a heads up if you've been fortunate enough to have not needed to use 911, you might want to try just to be sure yours works, and a sort of cry for help if anyone knows how to solve this. Guess you could say I'm putting out the 911 to get the 411. Hey at least I can laugh about it, for now. FYI this is not an emergency.