I first reported this problem under "Ringer doesn't work" title, which was misleading. I decided to start a new thread (Mods, please don't merge, this is a big bug IMO), since I've investigated this issue with my phone in more depth and I feel that this is a very bad bug and, at least to me, this is even worse than the GPS issue.
I use Bluetooth headset with my Captivate all the time and never had any issues, until I updated to 2.2
Here is what happens, once you use your bluetooth headset once on a phone call, right after that speaker on the handset itself stops working. There are no notification sounds coming out of it, no ringing when someone calls, not even audio if you try to play music, simply nothing. It seems like it's in Silence mode but it's not. This issue can be replicated 100% of the time. I use BlueAnt Q2 headset and also a built-in bluetooth in my car.
I found 2 ways to fix this:
1. Restart the phone. This fixes the problem 100% of the time, until you use the bluetooth headset again, then the problem occurs again.
2. Disconnect your bluetooth device from the phone and make a phone call and put it on the speaker on the phone, once it starts ringing you can hang up and the sound is back on the phone. But this doesn't work as consistently as solution 1. Again, this breaks as soon as you use your bluetooth device again.
Has anyone seen anything on this or experienced the same issue?
Also, I'd like to mention that this happened on 2 phones now. This happened when I first updated my original Cappy to 2.2. I called AT&T and they gave me a refurbished Cappy as a replacement, and this issue happened on the replacement phone as well. This never happened with 2.1, by the way.
Last night, I flashed the phone to Cognition 4.1 and again, the same issue happens.
As I stated above, this is a BIG issue for me, because I've already missed a few important phone calls, because the phone doesn't ring.
I remember when a lot of people said, regarding the GPS problems, that hey, this is a phone not a GPS. Well, ability to ring is a big part of any phone.
Thanks.
I use Bluetooth headset with my Captivate all the time and never had any issues, until I updated to 2.2
Here is what happens, once you use your bluetooth headset once on a phone call, right after that speaker on the handset itself stops working. There are no notification sounds coming out of it, no ringing when someone calls, not even audio if you try to play music, simply nothing. It seems like it's in Silence mode but it's not. This issue can be replicated 100% of the time. I use BlueAnt Q2 headset and also a built-in bluetooth in my car.
I found 2 ways to fix this:
1. Restart the phone. This fixes the problem 100% of the time, until you use the bluetooth headset again, then the problem occurs again.
2. Disconnect your bluetooth device from the phone and make a phone call and put it on the speaker on the phone, once it starts ringing you can hang up and the sound is back on the phone. But this doesn't work as consistently as solution 1. Again, this breaks as soon as you use your bluetooth device again.
Has anyone seen anything on this or experienced the same issue?
Also, I'd like to mention that this happened on 2 phones now. This happened when I first updated my original Cappy to 2.2. I called AT&T and they gave me a refurbished Cappy as a replacement, and this issue happened on the replacement phone as well. This never happened with 2.1, by the way.
Last night, I flashed the phone to Cognition 4.1 and again, the same issue happens.
As I stated above, this is a BIG issue for me, because I've already missed a few important phone calls, because the phone doesn't ring.
I remember when a lot of people said, regarding the GPS problems, that hey, this is a phone not a GPS. Well, ability to ring is a big part of any phone.
Thanks.