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.
I have a weird bug on my wizard. like the title says, the flash light just switches on randomly. luckily only at a very low level, but still, its an unwanted powerdrain. I can switch it off again by starting the camera and switching the flash on and then off again. I had this using NBD 8.1, also after reflashing it with that, and also with the latest TNT ROM. Is this a known problem? I have never managed to find any information on it.
another problem is that i was missing calls, which could be solved now by using the TNT rom. but the problem was that my phone would seem to work just fine, i could make outgoing calls, but i was missing incoming calls. the phone wouldn't ring, it wouldn't show any missed calls and the other party wouldn't notice anything wrong either, it would just give the normal tones when you ring people. Is this a radio ROM problem? It seems to have started when i moved to the netherlands, i think it was never a problem when i lived in germany.
I posted this in the big NFSFAN thread but I think that has taken a new course towards WM 6.5 so this may get over looked.
Just something I've noticed re v1.31. I just upgraded from 1.18. (took me a while to bite the bullet and change to the touchflo.) It seems my voice command will not announce incomming calls. The ring volume does drop to allow for the announcement, but nothing is heard.
The settings are correct.
Announce incomming calls, not during free time only, and play through BT headset when available. Does not work through headset or speaker phone. Also does not work when set to announce through phone speaker only.
I've reflashed the ROM twice, and went back to the bell OEM ROM between flashes. Everything else works fine except the above. It worked fine on 1.18, and it works fine on my girlfriends Touch with the same ROM. The issue is the same right off the reflash with absolutely no other programs installed.
Can anyone offer some insight?
Thanks
BUMP
Anyone? I really miss it.
Hello Everyone,
I'm having some odd problems that seemed to have started when I updated to CRB43. There are 2 consistant things I've noticed so far and these all happen when a headset adapter device is plugged into the phone.
1. If I'm listening to music in my car and a phone call comes in, the music stops (as it should), but there is no ring, just vibrate. When I try to unplug the adapter and answer the call, there is silence and the call goes to voicemail even though the phone appears to be in the call.
2. While listening to music, if I get any kind of notification, the sound goes dead even though the music is still playing.
In both cases I have to reboot the phone to get back to normal.
Any ideas?
Thanks,
Tim
I had the same problem.
Use Lucid's script and restore the Audio to stock.
If that doesn't work, reinstall the radio from HTC.
I finally got mine working by doing both on the same reboot, so I'm not sure which one fixed it when I was using JF's rom. Whichever, the combo of both did the trick for me.
I must have not done the radio update, because that's what worked for me, it's working good now. Thanks for the reply!
Super.
Glad it worked.
I'm not exactly sure how mine got overwritten either. But I figure it was one those causing the problems.
Now...
I've been trying the audio hack, and I simply cannot get it to work. No combination of versions work without phone calls and notifications completely stopping the audio server. Regardless of the build I choose. Luckily, I don't give up
First of all, my phone has root access and its unlocked using the bootloader method(I boughted like this a week ago).
The first 4 days the phone worked perfectly, but now im having this trouble:
When i make phone calls or i recieve phone calls, the microphone and the speaker mutes.
For example, if i call Jhon he receives my phonecall, but he can not hear me and i can not hear him. Also i can not hear the first tones if im making the phone call and waiting the other person to answer.
If i make a hard reset, everything starts working fine again. But after a few hours this malfunction comes back.
I changed my sim card, but nothing changed.
I think this might be a ROM's bug.
What do you think?