EDIT2: I am on GSM. I can make phone calls and send text messages, but I cannot receive either. The signal is usually 3 bars, my network comes up as Rogers (Canada). I have this same issue on Stock, as well as CM10/AOKP. Any ideas? This is without build.prop changes.
pm2gonzales said:
EDIT2: I am on GSM. I can make phone calls and send text messages, but I cannot receive either. The signal is usually 3 bars, my network comes up as Rogers (Canada). I have this same issue on Stock, as well as CM10/AOKP. Any ideas? This is without build.prop changes.
Click to expand...
Click to collapse
For SMS try disabling SMS routing in build.prop.
For not being able to receive a call, you mean it doesn't ring or you hear no sound after the call is placed? For the first I have no solution. For the second, put some pressure on the back of the phone next to the camera. If this helps, your speaker has a bad connection.
Trust me, it happens. I know of three people (including myself) who have the luck this only happens when receiving a call. Applying gentle pressure solves this. Only way to repair it is to send it back, or open up the backplate (screen) en jamming a small piece of paper in there so the pressure is applied all the time.
Die Bruine said:
For SMS try disabling SMS routing in build.prop.
For not being able to receive a call, you mean it doesn't ring or you hear no sound after the call is placed? For the first I have no solution. For the second, put some pressure on the back of the phone next to the camera. If this helps, your speaker has a bad connection.
Trust me, it happens. I know of three people (including myself) who have the luck this only happens when receiving a call. Applying gentle pressure solves this. Only way to repair it is to send it back, or open up the backplate (screen) en jamming a small piece of paper in there so the pressure is applied all the time.
Click to expand...
Click to collapse
It doesn't ring at all. I have to wait like 20-25 seconds and then it goes straight to voice mail. But I will try your suggestion as soon as I can and post how it goes. Thanks!
UPDATE: I tried both of what you suggested, and neither of them worked (both editing build.prop and apply pressure). I don't understand what could cause it to not receive calls or texts, but send them just fine. The phone radio must be working if it can send them, right?
Related
ok i have a slueth rom http://forum.xda-developers.com/showthread.php?t=366284&highlight=slueth and have been running it since 6/08 and had no major problems. so in the last few days when i have tried to make a call it will just act like it is going to call and then it will say "call ending". when i reset the phone(shut off) it will make a call but after that it stops making calls, it will try to call and it seems like it is looking for service. it can have full signal and still nothing, i can't receive calls either.
oh wow this is exactly what has been happening to me! What service/region are you?
Does it happen with texts as well?
yes it does i dont get text, im from fl i just drove up to boston mass on sunday. i have att wireless.
I am from northern VA and here is my problem more in depth, hopefully we are having somethign similar so this thread can serve a purpose to us both:
Note: this started when I first flashed Hyperdragon3 (with m2d) and persisted with L26 Kaisertouch (flashed because I thought it was a problem with ROM compatibility.
From time to time, the tilt decides to, from what I've acquired, not make a proper connection to the network. Although it displays 2 bars or 4 bars whatever, it is unable to make calls, receive texts, or connect to 3g/edge. The calls turn out like so, I call, the phone says "dialing" for about 6-7 seconds and then makes the ubiquitous sound of a call ending the beeping noises.
Regarding texts, when this problem surfaces I can't send any texts "Your message cannot be sent" and cannot receive any either (usually receive them all at once a little later).
Soft-resets used to fix this problem but they don't anymore.
So far I have restored my tilt to factory rom/spl/radio and still the exact same problem is there...
This leads me to believe that it may be a hardware problem?
Any suggestions?
yeah it sounds like the same problem, i did try something that worked for the rest of the day. i took the battery out for about 20min and put it back in and it seem to have done the job. ill try tomorrow and see if it stays working. im quite sre this might not be the real answer but for now its a band-aid.
that doesn't seem to work consistently for me.
This is really bothering me, I don't know what to do.
any help?
I live in Fresno, CA and all the suuden my 1 year old tilt stopped working consistently and went from 3G to EDGE to nothing and I could not make or recieve calls etc and my batterys drained quickly. I doenloaded a 3G toggle to turn off 3G and just use EDGE (auto to GPRS). This worked but who wants to work on EDGE. Funny thing is that 3G worked in Sanger which is 15 MIles east of Fresno. SAnger just recently got upgraded to 3G.....
Long story short, I took my phone in and they exchanged it since I had 3 days left on my warranty. The new Tilt with Windows 6.1 is sweet with some new bells and whistles.
Every time my wife calls she says she can't hear me for perhaps 2-3 seconds after I think the call has connected.. My previous phone did not do this, but the Nexus One does.
Anyone heard of this, and have any suggestions? I have Google Voice call on by default, but she's calling my cell number so I don't think it'd affect anything. As far as I can tell, the call is connected, but she can't hear me say anything for several seconds. I usually wind up going "Hello? Hello? Hello?" and she finally answers.
Glad to see I am not the only one this happens to..well not glad but i just hope this means its not just my phone.
I know when they call one of my numbers (either Google Voice or Cell Phone # not sure which) it says incoming call from <Name> press 1 to answer and press 2 to send to voicemail
@sandtiger
this is from google voice it is a filter setting you can change by going to to the setting on the google voice website.
But this is a different issue (im assuming) then the OP
Blueman101 said:
@sandtiger
this is from google voice it is a filter setting you can change by going to to the setting on the google voice website.
But this is a different issue (im assuming) then the OP
Click to expand...
Click to collapse
Yeah, I think I muddied the waters mentioning Google Voice, but these are calls directly to me cell number..
I might try disabling Google Voice just for S&G just to see what happens.. Seems when I place calls, they're connected when I expect them to be, but the delay could be more critical when answering.
I haven't yet, but going to try calling myself from my work phone to see what kind of delay I'm hearing.
I am having this problem also...did you ever find a solution?
Using BT headset by any chance?
In that case, it's normal.
Nope, no headset. Just the phone.
I need to test some more, but I think this has gone away for me.. Delay answering, plus the other party was "dropping out" often, ie: if it got quiet on their end, their voice disappeared entirely, and sometimes faded in or out while doing so.
Only thing I've changed is I disabled Google Voice as being my default call method, but this thread is about answering calls so I doubt it matters, especially since the calls were directly to my cell number not my GV number.
I might turn GV back on the way I had it and test some more, but maybe it was something weird with AT&T?
Im noticing this problem too, both on 2.1 and 2.2.
It seems to be a problem specific to AT&T N1's.
I also experience this. I've adjusted to swiping the answer button, pausing, then saying "Hello." I typically pause about 0.75 or 1 full second, and rarely do I need to do it longer.
The opposite seems to be true of the vibrate-on-connect feature: about 1 second after the person picks up, then the phone vibrates in my hand. How is that useful?! =P
Upgrade to 2.2 with radio, but I am having a weird problem. Phone shows I am registered on ATT, and can make calls, receive texts and send texts, however receiveng calls is sporadic. Most of the time the phone does not show an incoming call. I find if I go to the settings menu and re-register on ATT I can receive a call or two, but then it stops. As I said however I can always make calls and send/receive texts. It always shows good signal and edge connection. Any Idea where to start troubleshooting.
What I have done:
Disable google voice in case this was causing problems.
Nand restore back to Cyanogen and flash old radio - Everything works
YES!!! I was having this crazy problem with receiving call also! In fact that's what I was searching for when I found your post.
My receiving calls were very sporadic... and the incoming calls would NEVER ring! I would see the incoming call on my display... but I would get NO sound, even with the sound rockers turned all the way up!
I went back to Cyan's ROM cause it was totally unacceptable.
I recently switched from an iPhone 5 to the One Dev Edition. After having some signal issues, I went to AT&T, got a microSIM, they switched me an Android data plan, etc. But I'm still having an issue where I can't reliably send and receive calls, especially from my desk at work. I can dial the number and hit Call but that's it. No ringing, nothing. Just dead air, then the "call" ends. If the call does go through, I can hear the other person but they can't hear me. Same thing when receiving a call. I'll hear them but they can't hear me. Sometimes my phone won't ring and it just rolls to voice mail. I can see the signal switching from LTE to H, etc, and I have practically full bar strength. I just don't understand why the calls aren't going through.
Is this an issue with the phone itself? Something with AT&T? Is there a newer radio firmware I can try flashing? I didn't have any issues with the iPhone 5, and I even had my coworker put his iPhone into field test mode so we could compare the numeric signal and they're about even, though the iPhone usually does have a slightly better db signal. I really like the One but not being able to send or receive calls while at my desk is a deal breaker.
Thanks!
From the sounds of it, you are running the stock firmware still? Any root or other possible modifications? If you answered Yes then no to those questions, I would head back to the AT&T store and have them try it out, if anything they should be able to take your SIM card and put it into another Android device and see what happens.
What about text/data, do those work?
You said mainly at your desk you notice this issue, so does that mean it happens at other places as well, same symptoms (full bars, allows to send call then nothing?) You may just be the lucky contestant with a defunct unit, HTC should be able to help you out.
I would suggest first going to AT&T store, try out their suggestions, then if anything give HTC a call/email to see if they can be of any help. At this point I would stay away from flashing custom radios as they may void your warranty then you will really be up $hit creek.
Sounds like att.
I had this problem with tmobile once. The signal wasn't strong enough and it wouldn't call.
Some please are spotty.
Something is wrong with your phone. That should be obvious. Of course the vast majority of people who got this phone can reliably make and receive calls or it would be the biggest mobile phone bust in history.
Sorry to be blunt but you already know it's not the signal so it has to be a defect in the phone.
Thanks for the suggestions. This is the stock Dev Edition ROM. I haven't made any changes other other than just installing apps.
I haven't made a lot of calls but I don't seem to have an issue any where else.
No issues with LTE. Data has been fine.
I wasn't sure if AT&T would assist since this is the Dev Edition but that's worth a shot to have them run some tests on it. Otherwise I'll try to get a replacement (or refund) from HTC.
Thanks!
Sent from my HTC One using xda premium
I've had an issue twice now where I can't make or answer voice calls. When I answer I get nothing but silence, and the other person says it keeps ringing, and when I call I get nothing but silence (no ring or anything on my end, but it does ring for the person I'm calling.). I updated to the OTA after getting it yesterday, and things seemed to be fixed, but today it is doing it again. I have great signal (both LTE and the older network), IMS registered, and not roaming. Has anyone else had this problem? It is extremely frustrating.
Edit: Texts work, mobile data works, everything except calls.
I've noticed the call quality on 1X has been pretty poor. Also, I've had call roaming pop up a couple of times where I've never had any problems in the past. I haven't experienced exactly what you describe tough. We need VoLTE, and we need it quick.
It's still going today. I'm going to take the phone back to Verizon. Completely unacceptable.
Update: Verizon swapped out two SIMs and still couldn't figure it out. Sending me a brand new one.
Sent from my XT1254