ericiu
10th August 2007, 02:44 AM
Hey all. I've tried searching over and over for the forums, but I can't find an answer to my specific problem. So, here's the deal:
I use a regular/mono bluetooth headset. I have a Cingular 8525 which originally had WM5. I had no problem with my bluetooth headset. Ever since the WM6 ROMs have been made available, I've tried a few different ones. No matter which one I've tried, my bluetooth headset now starts randomly stops pairing/dropping the call in a middle of a conversation.
It's strange because technically a bluetooth headset disconnect shouldn't drop my call at the same time, but it seems to do both. I have a good signal strength, so that's not the issue. I've tried the different radio ROMs (now I'm on ROM 1.50.00.10 or something), and it still does the same thing.
I've read where maybe it's the A2DP settings that is messing up with my headset, but I'm not sure if that's it. What do you guys recommend or is anyone having a similar problem? It's very annoying that I keep getting my calls via headset dropped, and I'd like to avoid just reverting back to WM5 to fix the problem...
Thanks.
I use a regular/mono bluetooth headset. I have a Cingular 8525 which originally had WM5. I had no problem with my bluetooth headset. Ever since the WM6 ROMs have been made available, I've tried a few different ones. No matter which one I've tried, my bluetooth headset now starts randomly stops pairing/dropping the call in a middle of a conversation.
It's strange because technically a bluetooth headset disconnect shouldn't drop my call at the same time, but it seems to do both. I have a good signal strength, so that's not the issue. I've tried the different radio ROMs (now I'm on ROM 1.50.00.10 or something), and it still does the same thing.
I've read where maybe it's the A2DP settings that is messing up with my headset, but I'm not sure if that's it. What do you guys recommend or is anyone having a similar problem? It's very annoying that I keep getting my calls via headset dropped, and I'd like to avoid just reverting back to WM5 to fix the problem...
Thanks.