Database Info

Fuze doesn't receive calls

I've been having a problem with my Fuze randomly not being able to receive text messages or calls.
Sometimes when people call, they say it rings twice and goes to voice mail. All the while, I never hear anything or get a notification. This happened once after I texted someone to call me when they get a chance. They tried 3 times and then texted me back to say that they were getting sent to voice mail. I didn't get notification for either until after I called this person myself 20 minutes later. Right when the call connected, I got notification of a new text message.
Another time, somebody was calling me for 3 days. I didn't know he was trying to reach me until he finally left a voice mail and I got the notification for that (no missed call notifications).
I called AT&T and their tech support did some tests (called my phone) but since it isn't reproducible 100% of the time, they couldn't offer any explanation.
This isn't a bars/signal issue either as this is occurring in the same spot where my Tilt would always receive calls fine.
Has anyone else seen this?

I had the exact same problem with my Sprint Touch Pro & ended my contract early & switched to at&t. Hopefully it's not a fundamental hardware problem.

8notime said:
I had the exact same problem with my Sprint Touch Pro & ended my contract early & switched to at&t. Hopefully it's not a fundamental hardware problem.
Click to expand...
Click to collapse
Did you get a Fuze when you switched? Has that worked better for you? I'm still within my 30 days, so I'm debating exchanging it or just returning it and giving up.

I'm having the same problem. I did a quick search and found this;
This AT&T Forum Post
I tried the workaround and haven't had a chance to really test it yet though. I also noticed a few other settings in there that might have accounted for it.
One selection inside the phone settings had to do with whether calls went to voicemail when you're "Unavailable" or "Busy." I'm not familiar enough with the phone to know when it might tag me as either one so I unchecked both and I'm going to recreate my missed calls this morning.
Someone called after the phone had been sitting on my desk all night so I thought maybe it thought I was "Unavailable" due to inactivity (I dunno, I'm winging it) so I'm letting it idle for a few hours and getting a call later to see what happens.
Incidentally I have the exact same problem, no call coming in, but then I get the voicemail message after I try calling someone.

Unless I'm misunderstanding your point, "Unavailable" just means that your phone is switched off or out of signal, and "Busy" means you are already in a call. It's nothing to do with the behaviour or features of the phone.
Cheers,
Steve.

Yeah, I'm wondering if the phone is becoming "Unavailable" for some other reason than me being out of range. I have full bars in the house and that's where this all happened.
I've noticed, too, that I didn't get any email (I have it set to check every hour, even hit send/receive after someone told me they sent me something and it still didn't find it until I sent a second email to myself from another address)
Again, I don't know much about phones but it almost seems like the phone has bars but drops off the network for accepting calls/messages until you do something to activate the system again... or something. I dunno, just speculating.

Last week I went in and exchanged my Fuze for a new one since it was still within the 30 days. Up until tonight, I thought the problem was fixed. I was chatting with my wife over IM and she told me that she tried to call but that it just went to voicemail. I asked her to call back and leave a voicemail to see if it would notify me. I also asked her to send me a text. I didn't get notification for either. I checked my data connection by starting up Opera and going to a few sites. So I know that I had a verifiable connection to the network. I called my voicemail and checked the message I knew that she had left. Only after I made the call did I get notifications for the text messages I had missed. I never got any notification for the voicemail or missed calls.
Unfortunately, it seems this is a problem that isn't related to individual hardware as this is my 2nd phone with the same problem. I've also replaced my SIM card since a salesperson at an AT&T store suggested that it might help. I'm running the stock AT&T ROM minus the bloat, so it's not a custom ROM issue either. At this point, I'm not sure what I should do.
The only other thing I can think of that makes me unique is that I currently reside in Washington state but my number is one that I had ported from California. Is there anything about you're (skyau) situation that makes you unique?

Well the same thing happened again tonight. I received text messages 10 minutes late and I didn't get a voicemail notification until I initiated a call. As much as this sucks, I'm hoping it will stay this consistent so that I can have tech support replicate the problem and then try and fix it.

You may have a problem with your phone number. I'd try changing it.

Have you had experience with a problem like this? Is the phone number really the issue?
If that's what the problem actually is, I'm willing to get a new number. But I don't want to change it just to check and see if that fixes it.

same problem! Really pissing me off I just lost a important job because of this issue a few moments ago! Is everyone running a stock rom? I tested a few, now back to stock no apps nothing trying to find this gremlin WTF!

I'm running stock ROM without the bloat.
I exchanged my Fuze (I'm now on my 3rd) on Saturday and changed my phone number yesterday. I'm waiting to see if the issue happens again. If it does, I'll probably do stock ROM, all the bloat, no apps. If there are still problems, I'll probably try different ROMs.
I was able to get AT&T tech support on the line when the problem was occurring luckily. We went through his battery of tests and he verified that there was a problem. It would seem that the phone forgets/loses it's connection to the towers/network. Notifications (calls, texts, voicemails) aren't received until after the phone remembers/reconnects to the network. It remembers/reconnects when you initiate a call or send a text (essentially require the phone to use the network).
The tech told me that as far as he could tell, it was a hardware issue and that I should exchange my phone. So I'm on number 3 now and hoping for the best. I changed my number because I've been in a different state for 2 years and I had no ties to previous area code. So I figured now was as good a time as any to get a full fresh start (phone/number/SIM).
That sucks about losing the job.

Bump, I just realized a few moments ago that my phone rings once and then it says missed call, i always assumed they called me and then hung up after one ring in case i was in class or i was busy so that i could call them back. this is not the case? Also a few cases a call will drop every now a then... is this due to the radio rom i flashed? typical symptoms of a incompatible radio for a specific location? I'm using the .25.35 blackstone radio in ithaca, ny.

Having the same issue. Phone is asleep, then alerts me to a VM. Missed call doesn't show up in missed call list.
Really pissing me off and I think is responsible for my issues with Slide2Answer somehow.

The only time I have missed calls is because of MSVC. If someone calls and it is private or unknown, it will not ring. If it is somebody in my phone book or who doesn't have a private number, the phone will ring.
So I turned MSVC off and the private callers and the unknown callers will ring in.

it happens to me sometimes as well sometimes the d pad area will flash but i cant answer and it wont appear on screen then it wont say missed call.
sometimes if i try to hit the dial button it will also drop connection and instantly pick it up again
annoying but not a huge problem for me
and of course not on stock rom

[Q] Skype for Android on 3g buggy?

Hello!
I recently got a Droid Eris to replace my aging Rooted G1, and am got it all set up on Verizon. My intention was to use Skype for all calls and not get a voice plan, as I already use Skype as my business line anyways.
I installed the hacked .apk, and after several initial troubles got a call to go through over 3g. However since then, unless I am on wi-fi, I have massive issues making and sending calls over 3g.
When calls come in, Skype rings, I hit answer, and it goes into the screen like you are in the call however it keeps ringing and never actually answers the call. From that point on, unless i restart Skype, it just keeps popping up that call as incoming in the top taskbar.
Outgoing most of the time just fail to go through.
Is this normal with the hacked Skype, or am I just having weird problems?
(Note: I have reinstalled Skype twice already)
Thanks!

Bumping this to see if anyone knows anything. I got about 2 hours left to cancel the pre-paid plan and still get all my $ back, so if anyone knows hit me back!
Thanks!

Same here arrrrrrghhhhj

FlyingEagle200 said:
Same here arrrrrrghhhhj
Click to expand...
Click to collapse
Damn well I canceled the plan. But if someone knows a trick I don't please let me know as I have no problem signing up again!
Thanks!

I cannot make calls with my G2x

This is my second G2x and both have exhibited the same behavior. It will dial a number, whether from the phonebook or the dialer itself, and the phone application will say that it is dialing. After 30 seconds or so, and no ringing on the other end of the line, the call ends itself.
I usually have to enable Airplane mode, then disable it, to be able to make a call. sometimes I have to go as far as rebooting the phone completely after which it may or may not work. Incoming calls fail as well so I am missing quite a few calls and texts...but thhe emails and other data messages come through.
Oddly, data works perfectly regardless of whether the phone is having problems calling. This happens in 2g as well as 4g. I have manually selected 2g and could not call and had the same trouble in WCDMA only mode. I thought it was related to Wifi calling but enabling that has no effect.
Any ideas? I am trying my other line to see if that SIM card is having trouble. I just have no other ideas at this point.

pinhead said:
This is my second G2x and both have exhibited the same behavior. It will dial a number, whether from the phonebook or the dialed itself, and the phone application will say that it is dialing. After 30 seconds, no ringing on the other end of the line, the call ends itself.
I usually have to enable Airplane mode, then disable it, to be able to make a call.
Oddly, data works perfectly regardless of whether the phone is having problems calling. This happens in 2g as well as 4g. I have manually selected 2g and could not call and had the same trouble in WCDMA only mode. I thought it was related to Wifi calling but enabling that has no effect.
Any ideas? I am trying my other line to see if that SIM card is having trouble. I just have no other ideas at this point.
Click to expand...
Click to collapse
happened to me today too. I have had the phone since March 20th and I have too reboot to make it work. No idea what could it be.
Sent from my LG-P999 using XDA App

I used to have this problem frequently on my MT3G. Since someone else is having this problem on a different phone, I would guess that it's something software related.

Alright, it is happening on both of my lines. It might be a program that I installed so I am loading them back on one at a time to see if can determine which it is. I am looking at either Google Voice or Beautiful Widgets as likely culprits at this time but there is not certainty. I have also avoided installing Facebook and Twitter. I am able to make calls right now. I will see if this keeps working for the next few hours...maybe through to my morning coffee. I really hope it is an application, something I can do without, because it would be pretty bad if it is the phone. My girl just ordered one of these as well since she likes mine so much.

pinhead said:
This is my second G2x and both have exhibited the same behavior. It will dial a number, whether from the phonebook or the dialer itself, and the phone application will say that it is dialing. After 30 seconds or so, and no ringing on the other end of the line, the call ends itself.
I usually have to enable Airplane mode, then disable it, to be able to make a call. sometimes I have to go as far as rebooting the phone completely after which it may or may not work. Incoming calls fail as well so I am missing quite a few calls and texts...but thhe emails and other data messages come through.
Oddly, data works perfectly regardless of whether the phone is having problems calling. This happens in 2g as well as 4g. I have manually selected 2g and could not call and had the same trouble in WCDMA only mode. I thought it was related to Wifi calling but enabling that has no effect.
Any ideas? I am trying my other line to see if that SIM card is having trouble. I just have no other ideas at this point.
Click to expand...
Click to collapse
Happened to me twice today, first in the AM and then again around 2200 central time. i recently started using setcpu so not sure if thats an issue or not. anyone find the app responsible?

Yes, it has happened to me too, usually after it is in standby or idle, and this is my second phone. But my second phone not happens as often as the first one. Reboot is the only way I can get it to work. I notice that the signal is very weak only 1 or 2 bars.

That is a very good point to mention...that it is almost always directly after bringing the phone out of standby. Mine just did it again.

Same problem here. I don't even know how many calls or txts I've missed since.

Had this issue with my N1 and I always chalked it up to cruddy radio and/or coverage. I've since had it on my g2x once or maybe twice I think (had g2x for 3 days now), but at least after it timed out I was able to try again and the call would go through. With my N1 it would never recover unless I toggled airplane mode or sometimes even needed to reboot.
I hope there are some improvements in this area, because bad radio was my biggest gripe with my N1, and i really want to love this phone!
Sent from my LG-P999 using XDA App

Echo on phone call...help!

Curious is anyone else can replicate this issue I am having. When I receive a phone call, the person on the other end of the line hears a really bad echo . It seems to only happen on incoming calls. If I hang up and call the person back, the echo goes away. I'm on Project Fi. I have weak cell signal so I stay connected to WiFi at home mostly. I'm not using hangouts or anything, just the regular dialer.
To produce the problem:
Receive incoming call over WiFi
Ask the person on the other end if they hear an echo?
If so, hang up call the person back (over same WiFi connection). Does echo go away?
Seems software related since calling the person back makes the echo go away. Thinking about factory reset unless others can verify it happens to them. I am on the most recent November security patch.

In case anyone cares, I contacted Fi support and they believe it is very likely to be a bug. I submitted a couple bug reports after making and receiving calls. Engineers are supposed to contact me back within 48 hours.

The same has happened to me when I call my friend with Discord. I haven't tried calling the person myself, that might fix the problem. I'm using unlocked with Verizon.

@bballjohn32 The same exact problem on first gen pixel (project fi).
Only when someone is calling me over wifi do they hear an echo. Also to note, when either making or receiving a call over wifi the phone says call via "unknown ssid". prior to Oreo 8.1 it used to name my wifi network name. I spent two hours with support and ended by performing a hard reset, that did not fix it either. They are issuing me a refurbished phone which I'm not too happy about...

Hey everyone,
For anyone experiencing this issue, I found a temporary fix until Google releases a patch.
First of all, you need a rooted phone for this to work. I'm NOT going to cover the details here on how to obtain root, but a quick Google search will certainly help you out on this one. If your phone is still under warranty, then this procedure is maybe not for you.
1 - Have a rooted phone that experiences the sound issue where an inbound caller hears himself in an echo.
2 - Install a free app called DeFluence from Google Play.
3 - Open DeFluence and grant Superuser rights to the app.
4 - Tap "Disable Fluency". If it was successful, you will see the message "DeFluence was granted Superuser rights".
5 - Reboot the phone and enjoy inbound calls without the echo issue.
The only drawback I can see from this is that the other person might hear some background noise of wherever you are located, but I think it's still a great temporary solution.
So all in all, this most probably means this is a software issue that slipped into Android Oreo, and hopefully Google will be able to find a solution soon.
What I believe is happening is that the mic used for noise cancellation is picking up the voice of the caller and echoing it back into the call, when it should really just act as a noise cancelling microphone and not a regular mic.
If you have any questions, feel free to ask.

Verizon incoming call issue. Anybody else?

I am on Verizon and have CDMA-Less profile enabled. However, my incoming calls (and some outbound calls) are often not working. What i mean by this is that I hear the person on the other end of the line as garbled noise, not necessarily static, but more just jumbled electronic noises. The other person says I sound fine. Hanging up and calling back doesn't resolve the issue. If i voice call over Duo it works. Running latest 9.5.11 and the update still didn't solve the issue. This doesn't occur all of the time, but it is more often than not.

I see no one has replied and my reply won't be much help but let you know I've had my OP7 pro since release on Verizon with no issues at all after the CDMA less setting. Possibly toggle on and off the air plane mode after it happens and try the call back. Just a shot maybe.

Try calling Verizon and get them to sync the account. There might be some configuration error on the billing/technical side. I've seen this work for a couple people who described the same issue you are currently having.

Just an update. I went to Verizon and had a new SIM installed. Did a couple test calls using the phones there without issue. Attempted calling my wife and issue sprung up again calling her S10+. Tested calling their S10+ in the store without issue. Tried calling wife again and had the same problem.
Later went to another Verizon store and could not duplicate the problem, but switched her SIM card anyway.
Did a little research on the S10+ and it seems the problem may be related the phone set to Global vs. LTE/CDMA. Changed her setting to LTE/CDMA and haven't had the issue happen. Calls also seem to sound better too when i call her.
Very strange all around.