For some reason, my phone will not ring. I have had several voice mails, but my phone never rings. I am in an area with good Edge only service, but always have 2 bars.
I have tried calling from a land line, and several cell phones, and on average the other phones ring 3 times before my Fuze rings the first time.
try a forum search here or on howard forums. I've seen this issue pop up
but I cant remember where I saw it, but it has been noted before.
Related
15 years of using mobiles, never heard anything like it. I can hear myself when I talk.
It doesn't happen all the time, but happens at least several times a day.
It's NOT an echo. There's no delay at all. When I speak, it comes directly to my hearing.
It's not a network issue, as it happens with different networks and with VOIP as well (Line App etc...).
It's usually okay in the beginning of the conversation, but then within a minute or two it's like a "switch" is thrown and I all of a sudden can hear myself talking and it doesn't switch back until the phone call ends (often it will continue into the next call as well, for example if i call them right back).
damian5000 said:
15 years of using mobiles, never heard anything like it. I can hear myself when I talk.
It doesn't happen all the time, but happens at least several times a day.
It's NOT an echo. There's no delay at all. When I speak, it comes directly to my hearing.
It's not a network issue, as it happens with different networks and with VOIP as well (Line App etc...).
It's usually okay in the beginning of the conversation, but then within a minute or two it's like a "switch" is thrown and I all of a sudden can hear myself talking and it doesn't switch back until the phone call ends (often it will continue into the next call as well, for example if i call them right back).
Click to expand...
Click to collapse
Bumps... I also should mention the phone is brand new.
Think this is a driver issue? or something that could be debugged? The shop thinks I'm crazy because when I go to the shop I can't get the problem to reproduce.
I would assume its a hardware fault. Contact the phone provider and get it tested/fixed.
Sent From My Omega'd Galaxy S3 ...
The issue was found out. When the phone was switching networks between CDMA and GSM in the middle of the call was when it would happen. This was determined by making 30+ calls in various subscription modes and visually seeing the network type switch from H to G and then suddenly being able to hear myself talk. With the phone on GSM only or CDMA only as opposed to auto, the problem never occurred.
I have read through the FAQs and seen several posts from users of other phones and other networks with the same issue, but there has not been an answer to be found.
I've experienced this issue with 4 different ROMs now, so it's not ROM-based. I've tried 3 different radios, so it's not likely modem-based.
The issue is that I will get voicemail notifications for calls I miss, but I'm sitting at my desk with my phone and it didn't ring, nor is there a missed call indication. 5 minutes later, someone else might call me and the call comes through fine. It appears to be purely random. People who call me sometimes get through, sometimes not. It's not the same person who can't get through, or the same network.
Does anyone have an idea what is happening?
dontezuma said:
I have read through the FAQs and seen several posts from users of other phones and other networks with the same issue, but there has not been an answer to be found.
I've experienced this issue with 4 different ROMs now, so it's not ROM-based. I've tried 3 different radios, so it's not likely modem-based.
The issue is that I will get voicemail notifications for calls I miss, but I'm sitting at my desk with my phone and it didn't ring, nor is there a missed call indication. 5 minutes later, someone else might call me and the call comes through fine. It appears to be purely random. People who call me sometimes get through, sometimes not. It's not the same person who can't get through, or the same network.
Does anyone have an idea what is happening?
Click to expand...
Click to collapse
Your description definitely sounds familiar. There are times when the phone was under clothing or left on vibrate, then there are those back to back instances where you notice because the first call went straight to voicemail and the next one gets through.
Ideas? Maybe not, but there may be some clues worth considering. Every wireless carrier I've used suffers dead spots where you are 99% guaranteed to have your call drop in progress driving by.
Locally (NJ) AT&T has 2 on the westbound "covered roadway" leading to the skyway. My point is I've observed where they won't affect my passenger's TMobile calls. Oddly, when I experience this there, the call has usually gone on uninterrupted through the Holland Tunnel. Must be an infrastructure quirk.
The drive by carrier dead zone is a fixed location call deterrent. An expert could probably say how much each example is based on tower locations versus radio interference. I guess a similar scenario might be possible wherein the call recipient is stationary, like at your desk, and some moving interference breaks a fragile tower connection. I have to say it seems a lot less prevalent with SR vs. previous smartphones and with my current ROM / Modem vs. former ones.
pc103 said:
Your description definitely sounds familiar. There are times when the phone was under clothing or left on vibrate, then there are those back to back instances where you notice because the first call went straight to voicemail and the next one gets through.
Ideas? Maybe not, but there may be some clues worth considering. Every wireless carrier I've used suffers dead spots where you are 99% guaranteed to have your call drop in progress driving by.
Locally (NJ) AT&T has 2 on the westbound "covered roadway" leading to the skyway. My point is I've observed where they won't affect my passenger's TMobile calls. Oddly, when I experience this there, the call has usually gone on uninterrupted through the Holland Tunnel. Must be an infrastructure quirk.
The drive by carrier dead zone is a fixed location call deterrent. An expert could probably say how much each example is based on tower locations versus radio interference. I guess a similar scenario might be possible wherein the call recipient is stationary, like at your desk, and some moving interference breaks a fragile tower connection. I have to say it seems a lot less prevalent with SR vs. previous smartphones and with my current ROM / Modem vs. former ones.
Click to expand...
Click to collapse
Thanks. No, this is definitely chronic and not related to dead spots. I have my phone with me at my desk, 3 or 4 bars, no issues. Just doesn't come in. It's been really bad since moving to the JB ROMs. It pretty much never happened without explanation (dead zone, etc.) when I was on ICS and earlier. :/
One other performance problem that my Captivate had resembled this.
When I complained to Customer Service, they did some kind of remote (non-destructive) "reset" of my account. That corrected the random call drops I had reported then.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
pc103 said:
One other performance problem that my Captivate had resembled this.
When I complained to Customer Service, they did some kind of remote (non-destructive) "reset" of my account. That corrected the random call drops I had reported then.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Were you dropping calls midstream, or not receiving calls? My problem is with not receiving calls when I'm somewhere I usually do and at times when my cell service looks fine (adequate bars).
dontezuma said:
Were you dropping calls midstream, or not receiving calls? My problem is with not receiving calls when I'm somewhere I usually do and at times when my cell service looks fine (adequate bars).
Click to expand...
Click to collapse
Now that you mention, I recall it was a mix. Bars were good, some calls were silently missed, others FCd the phone app while ringing in, forcing reboot. Good, stable calls surrounded the (<5%) failed ones. AT&T's account reset corrected both issues. Stock ROM back then was Éclair or Froyo.
My new phone is exhibiting strange behavior that I haven't seen any postings about. (okay, one posting, but it didn't have any replies http://forum.xda-developers.com/showthread.php?t=660243 )
I had a Note 2 (AT&T) that worked great for about 6 months until the usb port died. Several ROMS, several modems, no signal problems.
I warranty returned it, and new phone constantly loses or maintains a week signal, until I make a call. Using data, the signal stays pretty weak, and drops a lot. Typically around 1 bar. Browsing the web, the pages hang for minutes at a time. Outbound text messages frequently fail with an error. Incoming calls frequently go straight to voicemail. But, if I dial voicemail, the signal bar immediately jumps to full bars. Now I can hang up, and use a strong data connection for about 3-5 minutes, until the signal slowly drops back down. Toggling airplane mode, or rebooting does not seem to jump start the signal. Making a voice call though, jump starts it immediately every time. Additionally, the battery life seems to be much worse, but I haven't actually benchmarked it. It is the battery from the original phone.
I've tried the phone bone stock with the latest 3 modems, and with CleanROM and latest 2 modems, and with stock and Adam kernels. The behaviour is exactly the same in all cases. It's like the radio just sort of goes to sleep until I make a call.
At first I just assumed it was a hardware issue, because the old phone worked just fine, but the fact that a phone call wakes it up makes me wonder if there's more to it. I took it into my local AT&T store and they found the IMEI was listed as the old phone, and corrected it. Of course, my phone worked perfectly in the store, even before the IMEI change. I figured that was the problem though, and it actually seemed to work for the rest of the day, but the next morning it was back to a weak signal.
At this point I guess I'll return it, and try another one, but I figured I'd check here and see if there was a better solution.
I thought it was me because I was driving or at a bad place in my home but I was wrong. My edge drops calls almost exactly at the 30-40 minute mark in my phone calls. It has happened all week but it was really noticable when it dropped and I looked at the time during one conversation. Anybody have this happen to them? I was told to replace it at a store. And we all know how plentiful the phones are… .:/
I recently had this problem occur again. This is after having a new phone. I called t-mo tech support and they said that the facebook messenger app has been causing a lot of problems with the call connectivity of the phone. I just uninstalled the app and am waiting to make a long phone call to see if this was the true culprit.
sent from the Edge
I think its just T-Mobile. My calls disconnect all the time. And my phone says no network connection a lot. (Even before I got the Edge) I think when the network connection drops, so does the call. This was even worse for me on the Sprint network though so I just live with it now that I'm with T-Mobile.
Galaxy Note Edge- phone call dead
My problem is from time to time phone call will be dead like no sound at all on either side even though there is network signal and the phone is showing call duration. I have to restart the phone in order to make phone call then its fine for unspecified amount of time then it happens again. Had my Note Edge for 3 weeks now and its pain in the neck. BTW I'm from Australia.
I've had a strange long-term issue where the phone will ring for the party calling in, but won't ring on my end. No missed call shows up. It occurs about half the time with or without WiFi calling on. This issue has plagued me since my Verizon Note 4 with Verizon service, my T-Mobile Note 4 with T-Mobile, and is still occurring on my T-Mobile Note 5.
The only way I know I've missed calls is that I use YouMail's email notification service which lets me know that someone got to my YouMail voicemail even if they don't leave a message.
I thought it had to do with my poor (1-2 bar) service in my rural area but I've had WiFi calling on my past two devices, WiFi always on, and it still happens frequently. For example, I got three calls from my girlfriend while I was home today. Full WiFi signal strength the whole time. Her first call came through fine but the following two I never received any missed call for. The only reason I know she called was because of the email notification I received from my YouMail voicemail service. I have a new SIM card through T-Mobile so I know it's not that as it previously happened with my Verizon SIM and Note 4 while on their network.
Very frustrating. Any idea what is going on?
I can say that T-mobile wifi calling is not stable. It got so bad I had to turn it off and just deal with poor signal.