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.

XDA II Delay in Receiving Calls

Been having a problem on my XDA II in that when I receive a call and answer it, it takes a few seconds before I can hear the other person. Sometime it woks fine and others the person can hear me but I can't hear them ?
It has been back for repair 3 times and it still does the same thing. The speaker is fine as it works loud and clear, it's only on incoming calls not on outgoing.
The place where I have bought it will now swap it out for a XDA IIi as you cant get the II anymore around here. That's great but I would still like to know why it went wrong ? Anyone got any clues ?

plz explain what is delayed.
Could it be just too much s/w running?
I found that when I am running activesync, calendar & contacts sometimes there is an awful delay in the response of the MDAII. Especially the BT headset has delays then of more then 20seconds (so I answer call on MDAII and then transfer it to headset when this occurs).

delay on phone
:shock: Me too!
Not sure if I should answer on screen,accept or reject,or green button.Both seem to delay,often with caller ringing again.

When the phone rings and you answer it. You hear nothing. It's a case of hello ? hello ? etc. They can hear you but I can't hear them then all of a sudden their sound will just kick in.
Actually sometimes when I dial out, I never hear a ringing tone and all of a sudden the person cuts in.
There is a delay. I have no software running at all. It does this from a hard reset as well.
What bugs me is that it has gone back 3 times and they claim it has been tested and fixed. It clearly hasn't.
Hope the XDA IIi is better, cos this was very annoying.

Hi Ekko,
Would you happen to be running Pocket Bluetooth Tools?
Cheers,
Pete

Hi, the phone was fine until about 6 mths old when it started doing this. I had Pocket Bluetooth on it and it used to be totally fine. This never affected it at all.
Obviously once this problem arose, I have hard reset the machine on a number of occasions and have used it as a clean machine. Same problem ? So not down to Bluetooth Tools.

Hands Free mode
In order to use an Himalaya with a BT headset you need to run 2.20 translated. The Hands Free profile works better and it will even support caller ID and there is no delay when answering calls.

Call ends after 1 hour

Hi there.
I did search for an answer, but could not find one.
Because of the nature of my work, I frequently make calls longer than an hour. I have noticed the following (very irritating) phenomenon. The call will end by itself at around 58-59 minutes, and I can not call back!
If I make a call, I get the dialing screen, and nothing happens. After a couple of minutes of waiting with this screen, the call will go through. I can turn flight mode on and off to no effect. All subsequent calls will then "pause" like this for a minute or so before going through.
If I restart the phone everything is fine.
My phone is a Imate K-Jam with 2.16.9.1 WWE ROM. The radio rom has been updated to 02.61.11. This problem occurs with the default radio rom and the updated one.
If I keep an eye on call length and stop the call and dial back after, say, 50min, there is no problem.
Does anyone have any suggestions?

care to list out software that you have installed? sounds like.. there is a monitoring software going on .. which do something after a certain amount of time, however it has bug and hanged.. making your phone .. unavailable. That's what I think.

Sure thing.
I only have Total commander, TCPMP, Stoptime (a stopwatch/timer program), the ampda Camera Speckle Fix, and Magicall.

Call Connection Problems

Hey, I've been lurking these forums for a while but I thought I'd come on to ask a question. I tried asking on sprintmogul.net but they didn't really help.
I've had my mogul for a few months but lately it's been developing a really annoying problem. I'm really not sure where it started exactly so I can't blame any apps in particular. When I receive a call the caller ID / ring and vibrate go off perfectly - the problem happens when I try to answer the call. Generally one of three things happens:
1 - The call connects instantly and just works - this happens pretty rarely, I remember the last time it happened the person calling was also on Sprint, if that makes any difference.
2 - The phone will just sort of hang there for about 10 seconds, caller ID popup still there, the ring stops though. Eventually the popup disappears and I get a missed call notification, as if I never clicked the answer button. This is what usually happens.
3 - The phone hangs like in situation 2, but the call eventually connects. This only happens if I press answer almost immediately after the phone starts to ring.
I'm on winMo 6.1 with the latest radio and am not running any major mods or hacks, just a few reg edits. I'll probably try a hard reset soon but ideas on things to try would be appreciated!

I am seeing this also, on both my own xv6800 and my wife's. It's VERY annoying.

Freece 14 sec in a call.???

Several times every day my HD2 freeces 14 sec in a call.
Most often when someone calls me.
I notice first that there is no sound.
The call seconds continue counting as if the call is still going, but only hardbutton on/off is working. After 14 sec the display freeces.
Using the hard button will close the display, but not turn off the phone.
Diplay on works as well but the slider does not, so only batt out or reset button will help.
Anyone knows?
Had the same problem using Rom1.48 and now also on 1.66.

hi
i do have this problem and all the time its stucks after or befire a call
i have to remove the battary every time
what should we do and why is it fulks?

FM radio in use - could be the problem?
Someone wrote on a Norwegian forum that the phone freece if you pull the headset without closing the music/radio program first WHEN an incomming call is displayed.
Anyone?
I listen to the FM radio during the day, and this might be what's happening. I pull out the coard/plugg before answering the call without closing FM radio first.