Database Users

Sound cut off if call not picked up with call waiting

There seems to be a very annoying bug on my new XDAII that is running the 1.6O O2 ROM.
If I am on the phone and i receive a call that alerts me that there is a call is waiting, and I decline to answer it, the sound is cut off and I can't hear the caller anymore. Cancelling the current call and re-dialling is the only way of getting 'sound back'.
Furthtermore, another irritating bug is that if the phone rings and I answer after only 1-2 rings, I can't hear anything for a few seconds and have to wait those couple of seconds before i can speak to the other person. This doesn't seem to happen if the call is answered after 3-4 rings.
Any help would be appreciated.

Me too - only answer I found was to turn off call waiting.
Poor solution.

Same for me, i too had to turn off call waiting, however i found that if you are using a bluetooth headset when the second call comes in and you decline to answer it, it just transfers the current call the the phone and you can continue it there

Same problem here.
I find that if you put the call on hold and then resume - the voice will come back.
VERY irritating.

Same for me too, I have T-Mobile 1.60 and using BTHTools 1.1.0.0...
Do you use BTHTools?

yes l am using BT tools.
regards,
hasnain

I performed a hard reset...
Did NOT install BT Tools - and had the same problem.

Mine did this long before using BT tools also.

I also have the same problem....
Is it an incompatibility between the phone and Bt Tools?
Is there any solution other than turning off call waiting?

Does anyone face the 2nd problem that I mentioned:
Sometimes when I pick up the phone after it rings, it takes a couple of seconds before i can hear the caller. This happens more often when picking the phone up within 1 or 2 rings.

This problem was aroung in the I-mate ROM 1.66.
They fixed both with the 1.72 ROM.

ketinson said:
This problem was aroung in the I-mate ROM 1.66.
They fixed both with the 1.72 ROM.
Click to expand...
Click to collapse
i DON'T THINK THIS IS FIXED IN 1.72. i STILL HAVE THESE SAME PROBLEMS TOO, RUNNING t-MOBILE 1.72.
While running 1.60 I replaced the Radio Stack only with the O2 original release version - sorry don't remember version number - and it worked without these two very annoying bugs in the phone. i think it is a problem with the readio stack version only.
After losing the voice with an incoming call I can get the voice back without redialing by placing the call on hold and then resuming.
I have the same problems with or without bluetooth tools and with or without a BT headset.
Now, I have T-Mobile's 1.72 installed and am afraid to reload the working radio stack becasue of the "downgrade disaster" with 1.72. I am anxiously waiting for either a stable 1.72 or XDA Developers to help us out of this mess with this ****ty ROM.
This forum is fantastic. Thanks to everyone.
Steve

I had the problem in the 1.66 ROM, and no longer have it with 1.72!

I've just installed the new O2 1.72 ROM and am still having the same problem.
I am also suffering from a problem I was having on the old ROM. Many times when I receive a call and press the green answer button, it takes between 2-5 seconds for me to hear the person calling. The person calling also hears a similar period of slience before he/she can hear me.
The same thing also happens sometimes when I call out, where only once 2-3 rings into the call or if the other party has already picked up thephone can I hear or say something.
I'm not sure if caller ID or Photo ID has anything to do with it as I have around 1380 contacts on my xda.
This problem is extremely annoying and was wondering if there is anyone out there who has faced the problem and may have an answer for it.

Us too
We have two xda2 with 1.72, and same thing, there is a 5 second delay upon recieving any call, and sometimes there is a hangup duriong call waiting???

I never had that problem until I installed Bluetooth Tools...now it always happens. Though as someone's suggested, holding and resuming seems to do the trick.

Hero Call issues.

Hey,
My fiancee has a HTC Hero and she's having some issues with it today.
She was on a call when all of a sudden the voice when all scrambled and screachy. Then the call dropped out.
After that, she hasn't been able to make or recieve calls.
When she tried to make a call the phone is silent on the dialing screen, then beeps once and returns to the phonebook.
She just recently received the OTA 2.1 update.
Thanks in advance!

If it wasn't a network outage (other handsets work at same location), tty rebooting (with battery removal), and if that doesn't help, return the phone for replacement. Some component inside might have burned out.

Thanks, she tried a reboot again and it seems ok. I did notice that she had WiFi turned on, so I have now turned it off to see if the issue occurs again.
Thanks,
Sent from my HTC Magic using XDA App

Jesterarts said:
Hey,
My fiancee has a HTC Hero and she's having some issues with it today.
She was on a call when all of a sudden the voice when all scrambled and screachy. Then the call dropped out.
After that, she hasn't been able to make or recieve calls.
When she tried to make a call the phone is silent on the dialing screen, then beeps once and returns to the phonebook.
She just recently received the OTA 2.1 update.
Thanks in advance!
Click to expand...
Click to collapse
I get this occasionally as well, calls drop and then not able to connect, despite having full signal. A reboot does tend to help, I too have noticed that if WiFi is on it seems to happen more often. Its a shame, I hoped this may be resolved by the 2.1 update

Bump!
I have had many calls missed as "calls are barred to this number" It is a joke! please help!

Missing calls

I've read a few similar threads and it seems that many people have noticed the same but haven't seen any real solution.
I noticed that when I try to call my phone, the 1st attempt will be missed (it will either redirect to voicebox due to unavailability or it will ring as disconnected and never get notified). The 2nd attempt will ring ok.
I haven't seen anything helpful except from turning 3g off but I have it on auto and use the mobile widget which I assume does the same.
Anyone noticed the same? it's worth to try it though because you may have the same and be unaware of it. (Try to ring your phone when its in standby and hasn't been used for several minutes)

I bought the DHD yesterday, in the few hours i used it i didn't notice the issue you describe. Just to be sure i called my phone a minute ago and i had no problem.
I have 3G turned off and i'm not using voicebox (using missed call alert instead).

i have a feeling its because if you turn the phone over it rejects the call. i keep doing this because my phone is in a slip case all the time. anyone know how to turn it off?

rossysaurus said:
i have a feeling its because if you turn the phone over it rejects the call. i keep doing this because my phone is in a slip case all the time. anyone know how to turn it off?
Click to expand...
Click to collapse
No, it doesn't . It just mutes the sound but if it's already turned over when it receives a call, it will ring. You can change this behaviour in settings-call as well as volume control for flip case.
I tried several more times and it doesn't happen now. It just happened a few times when I tried to test. The only setting I changed now was for GSM-3G not to force 3G connection on for all the time. Maybe that helped but now I'll have to see how my data connection is affected.

andreasy said:
No, it doesn't . It just mutes the sound but if it's already turned over when it receives a call, it will ring. You can change this behaviour in settings-call as well as volume control for flip case.
I tried several more times and it doesn't happen now. It just happened a few times when I tried to test. The only setting I changed now was for GSM-3G not to force 3G connection on for all the time. Maybe that helped but now I'll have to see how my data connection is affected.
Click to expand...
Click to collapse
Yesterday whilst in town, a friend said he had tried to get me several times, only to get a network message that the phone was unavailable. seems fine each time i test it though, and there is a strong 3g signal around here. I put it down to everyone in town christmas shopping and net network cell being clogged up with people calling each other to find out where there other half is lol.

What network are you on? I'm on Orange, and get this all the time. It seems to be when I'm in an area where there's only gprs which cannot work with voice calls simultaneously. For some reason the data signal is given priority and the voice call is rejected. Surely it should be the other way round? Not sure if this is a network problem or a software problem... if the latter, is it HTC or Android?
Sent from my Desire HD using XDA App

Intermittent no in-call sound on incoming calls

Hi all,
I have a bone stock Moto G4 running Marshmallow and have been experiencing an intermittent problem when receiving calls, where neither I nor the caller can be heard. It's as if both of us have our mute buttons on, or as if neither of our speakers is working. The phone rings audibly and the call is logged correctly when I answer it, so evidently the call is "going through". All other sounds play normally; only in-call sound is affected.
When this happens, if I immediately call the person who called me, the call goes through and we can each hear each other fine; i.e., the problem only occurs intermittently on inbound calls.
If I reboot the phone, the problem goes away but eventually comes back.
I've seen numerous reports of "no sound during calls" posted here and elsewhere but most of the posts I've seen are pretty old, and don't seem to apply to my phone.
I posted this question over on the Lenovo site but I haven't gotten any responses so I thought I might also check with the experts here.
Thank you for any help.

Inbound Intermittent Call Ring
Hi,
I have a Zenfone 3 Max ZC520TL, with Android Nougat and the latest firmware (14.14.1808.121) running on T-Mobile network...
For the longest time I've had an issue with incoming calls most of the time going directly to voicemail, no matter how many bars I have...
I've been researching this for sometime now and most blogs (after they recommend advice on fixing the issue), want you as a final resort to do a backup and perform a Factory Reset...which people say didn't work, so that's wasted time...
I have an extremely easy fix for this which will take you about 30 seconds...
All you have to do is change your 'Preferred network type' from 4G to 2G...you can do this by going to: Settings/More/Cellular networks/Preferred network type...tap Preferred network type and choose 2G...that's it!!! Your phone will now ring every time there's an incoming call unless the number is blocked...
By choosing 2G, you may lessen the internet download, upload, movie and video watching speed and image download speed in texts but increase the signal range...I personally am willing to give up image in text speed to receive incoming calls with no issues...
If you want to download or upload or watch movies and videos from the internet or download images in texts instantly, just change the 2G setting back to 4G temporarily...
I hope this post helps and saves others from spending hours looking for a fix for this issue.
Cheers,
Vinny

Dialer Delay Bug?

Does anyone have this issue? When ever I am dialing out, there are times it seems like the call is going through, but I have to "end" the call so the call initiates... Its odd, but generally after that my calls are fine. Doesn't matter if its through Bluetooth, wifi calling, or regular calls through the phone itself.
How can I fix this if there is a fix? Running latest OTA, NMJ51B via Sprint.

~~Tito~~ said:
Does anyone have this issue? When ever I am dialing out, there are times it seems like the call is going through, but I have to "end" the call so the call initiates... Its odd, but generally after that my calls are fine. Doesn't matter if its through Bluetooth, wifi calling, or regular calls through the phone itself.
How can I fix this if there is a fix? Running latest OTA, NMJ51B via Sprint.
Click to expand...
Click to collapse
I've had this happen across a couple of phones with the Google Dialer... And actually with a Samsung just before I got my PH-1...

Happens every day to me

~~Tito~~ said:
Does anyone have this issue? When ever I am dialing out, there are times it seems like the call is going through, but I have to "end" the call so the call initiates... Its odd, but generally after that my calls are fine. Doesn't matter if its through Bluetooth, wifi calling, or regular calls through the phone itself.
How can I fix this if there is a fix? Running latest OTA, NMJ51B via Sprint.
Click to expand...
Click to collapse
Nope

I've had happen several times where after dialing (regular phone app) and it shows the call "connected", it takes about 5 to 10 seconds or so before there is any audio. Once the other end had already answered before the audio comes on, but usually I hear the ringing after the delay. Doesn't happen all the time. I don't make many phone calls out.

I usually see the app hang at the end of the call. Not all the time about once every day or two.