Develop Bugs

Bluetooth Headset Fails

As everybody know, its quite annoying use Universal as mobile. then, i decided to start to use the Bluetooth headset!
But doesn't work all the time.
If i set one headset, it works fine for few hours, then, after a while, without any message, bluetooth in my Universal turns off it self!!
At begin i though that would be my headset, then i tested with my other headset, and is the same!
Beside that, when i try to pair it them once more, it has static on it.
So, to be able to use it again, i need to:
- Remove device in my bluetooth list
- restart headset
- Search for device once more
And then, it works for a while again.
Well, i have tested in two headset over here, The Dopod H1 and Targus.
Does anybody knows what is going on or had same problem?
Thanks in advance!

Same here
I have experienced the same problem with my JasJar. The bluetooth radio seems to turn itself off from time to time. I think it is somehow related to WM2005, because I had the same issue with a Himalaya running WM2005. What is weird is that the blue light continues to blink. If you go to the wireless manager applet, it sometimes shows the bluetooth as on and sometimes as off, but if you go to the bluetooth setting, it shows the radio as off.
Any suggestions?
TIA
Panabax

Buzz_lightyear may have the solution here: http://www.buzzdev.net/index.php?option=com_content&task=view&id=60&Itemid=41
I'm trying this at present. BT stayed on overnight, despite very low battery, and I'll put it into use all of today. If I go a full day without losing BT then it's solved for me cos I was losing it ALL the time 2 days ago.

Hmm, I had a better day with this reg hack - but I did lose BT once. SO, inconclusive at present.

Guys - I have searched the whole internet and can confirm that there is a problem with the ROM
Until it is fixed Bluetooth will not work as it should

This is a problem i had with original jasjar rom (september 2005). First official upgrade and all subsequent roms have solved this problem. I'm actualy using helmi's aky 3.5 1.3.1 and sony hbh660 dayly without any problem.

Bluetooth headset disconnection...

Hello,
I tried many kind of WM6 and 6.1 ROMs and faced the same problem with different frequency rate: my bluetooth headsets disconnect very often (also during phone calls) and actually I don't have any idea what should be the problem.
The HW I have is: H200 with Logitech BT mobile pro and Plantronics voyager 510 (of course not together the latters).
I tried different radio versions and different roms: the only variance is the "well-work" period. If it lose the connection I have to set off/on the BT in connection manager. Does anybody have this problem or know the root cause/soution to fix? I really appreciate any kind of help/suggessions.
Thanks

I have the same problem as you... I tried WM5 and WM6 (Official Spanish ROMs) and no solution found. My hardware is H200 and Parrot CK3000Evo. I think may be a hardware problem. Any help please???

vampirox said:
I have the same problem as you... I tried WM5 and WM6 (Official Spanish ROMs) and no solution found. My hardware is H200 and Parrot CK3000Evo. I think may be a hardware problem. Any help please???
Click to expand...
Click to collapse
Don't think there's any easy answer. Often seems to be a combination of headset firmware and BT settings in your WM device.
There are good discussions of some of the problems and issues in this thread and this thread.
Other than that, you could try different firmware versions for your headsets - that solved my problem with a Jabra 8010 (till it just crapped out completely).
Alternate solution is to cut the crappy earphones off your standard USB headphone and solder on a 3.5mm stereo plug. I haven't quite got to that stage yet, but have come perilously close many times.

e_gregious said:
Don't think there's any easy answer. Often seems to be a combination of headset firmware and BT settings in your WM device.
There are good discussions of some of the problems and issues in this thread and this thread.
Other than that, you could try different firmware versions for your headsets - that solved my problem with a Jabra 8010 (till it just crapped out completely).
Alternate solution is to cut the crappy earphones off your standard USB headphone and solder on a 3.5mm stereo plug. I haven't quite got to that stage yet, but have come perilously close many times.
Click to expand...
Click to collapse
Do you think it refer to the A2DP problem? I don't want to use my HS to listen to music; otherwise these aren't A2DP compliant neither. I just want to use for phonecalls as it designed for.

_sasa_ said:
Do you think it refer to the A2DP problem? I don't want to use my HS to listen to music; otherwise these aren't A2DP compliant neither. I just want to use for phonecalls as it designed for.
Click to expand...
Click to collapse
I want to use for phonecalls too. I'm sure there is a bluetooth problem, perhaps a hardware problem. I have same problems using BT GPS...

I have the same issue with my Cardo headset and my BTGPS unit.
On a call and the headset cuts out and call diverts to handset.
BTGPS working fine then suddenly no connection to BTGPS.
Are any of you using MS Voice Command with BT Fix? My problems seem to have started right around the time I began using it. Before that I don't recall having any headset drops. Can not say the same about GPS as I've only had it a short time and have not un installed VC to test.
BTW. I'm using the stock WM6 update and radio for AT&T 8525 H100 hardware.

Heykrop said:
Are any of you using MS Voice Command with BT Fix? My problems seem to have started right around the time I began using it. Before that I don't recall having any headset drops. Can not say the same about GPS as I've only had it a short time and have not un installed VC to test.
Click to expand...
Click to collapse
I'm not using voice command, and i probe it using clean official WM5 and WM6 ROM. Today I installed schaps WM6 ROM, but i have the same problem.

I have the same problem too. It will be ok for a few days, then wont be able to use BT (Plant 250). Then either I have reset the phone or turn off BT in phone and turn it back on, then it will work.
I believe it is a hardware issue, cuz I had a 8525 before, and never had this issue. But with the set I got now, its been a problem from day one.

I don't use voicecommand at all. The strange thing is that I use a Nokia BT GPS and it works fine always: no disconnection on long trips neither.

_sasa_ said:
no disconnection on long trips neither.
Click to expand...
Click to collapse
Do you use headset and BT GPS at same time? When headset disconnects BT GPS still working?

vampirox said:
Do you use headset and BT GPS at same time? When headset disconnects BT GPS still working?
Click to expand...
Click to collapse
Yes, the HS is dropping but the GPS still working forward. Strange, but because of that I think it's not HW problem.

_sasa_ said:
Do you think it refer to the A2DP problem? I don't want to use my HS to listen to music; otherwise these aren't A2DP compliant neither. I just want to use for phonecalls as it designed for.
Click to expand...
Click to collapse
Sorry if I mislead you with the A2DP stuff. Didn't realise you were having issues with just the basic audio.
As I mentioned in the other post, though, there seems to be compatibility issues between the MS BT stack and some headsets. Changing ROMs probably won't help, because they still all use the same BT stack. Better to try playing round with the headset - see if you can change firmware in that, if possible.
I know there are some people trying to port the Widcomm BT stack to WM6, but I haven't heard of any real success yet.

Bluetooth headgear disconnect mid-call

Sorry if I'm posting a question that's been answerred before, but I haven't been able to find a thread to this problem:
sometimes my Nokia BH-102 will disconnect in the middle of a conversation in the car. The only option at that time is to pull the TP2 from it's holder and put it to my ear.
Whether it's the headset or the phone, I don't know, but it used to work in combo with the old Nokia E60 I used to operate......
Chances are it's the TP2, but how to fix it?
Only 'tweak' was to install tomtom, but without the 2 dll's which have been causing some problems.
Has anybody experienced anything similar?

Bluetooth visor problem
I have had problems with my headset - Supertooth Visor One Bluetooth Car Kit. Not quite the same as you though - the problems I have is that when I make an outgoing call, everything works fine but when I recieve an incoming call the audio stays on the handset rather than coming out of the bluetooth headset - which means I have to pick up the phone. I also have installed TomTom 7 and I had to do the 2 dll fix as my bluetooth was completely broken otherwise. So I guess maybe TT7 is responsible in some way. Only thing is, I dont want to do a hard reset to find out!!

I'd already read about the Tomtom BT-issue so I cleared the 2 dll's out of the cab prior to installation.
So the originals should still be in use. BT is/was working and I have been synching using BT. That's not the problem.
There should be threads out here pointing you to the original dll's. you could past them over the current ones and see if it helps.

I experiencing the same problem, and didn´t install tomtom.

So now it looks like it's a problem in the TP2 then.
Hopefully a BT-guru can investigate? This is way beyond my capabilities.
In the meantime I'll know what to do if and when it happens: take a chance on the cops seeing it and issuing a ticket.....

I'm having a similar issue, my headsets plural, have this problem. It will disconnect but what is happening is the headset is shutting down. If I hold the power button on the headset it comes back on and will work again.
If it was one headset I would think it is faulty but I've had this problem with three headsets and the Bluetooth in my car.
Is it possible that the phone is sending a shutdown command? BTW I am using the stock TMOUS 6,5 ROM and have tried some of the cooked ROMS with the same effect.

bluetooth paring problems WM6.5

Yesterdaty I updated to WM6.5 and now try to get everything working again. Somehow my TP2 won't pair with my bluetooth carkit anymore. With WM6.1 this was no problem. The phone still pairs perfectly with my computer (also bluetooth connection) so I think the bluetooth connection is ok.
When parining to my carkit it finds the device, then I have to enter a password on the TP2, and after that it just sais "pairing connection failed", and it will not work. I am sure the password is not changed since yesterday. I tried it several times. I do not know what to do anymore. Could this be a setting somewhere? I get the feeling my password is not send properly but have no idea.

Meanwhile I tried pairing my carkit with another phone and no problems there. So my conclusion is: something has changed with bluetooth, updating to WM6.5 which makes it now impossible to pair my TP2 with my carkit.
Is there maybe a programm for the TP2 which give me more controll over bluetooth (like maybe go to an older standard)?

I have exactly the same problem as you

good to hear I am not the only one. Hope someone will come up with a solution for this.

I did nor observed any issues when pairing my TP2 after reflashing to WM6.5
There is another issue however - I can not hear any voice until it is charging.
Unplugging of the charger fixes this issue immediately. Horrible...
Seems, HTC guys are saving money on testing by using us as Beta Customers.

Would a custom ROM be a solution for us?

I updated to the "energy 6.5.1 rom" and guess what..............
The same problem. The rom is very nice, but my TP2 still won't pair with my BT carkit which is very big problem for me.
Is there maybe a way to downgrade just the BT part of a rom to WM6.1. I read on different forums there is something that is called a BT stack. Could this be the problem?

I have a ton of problems with bluetooth pairing now. However, I don't know whether it's the fault of 6.5 or the Tilt 2. Here is what I am experiencing...
- On car deck or headphones, the skip buttons don't do anything
- on car deck or headphones, I have to disconnect Stereo Audio and then reconnect to actually get sound. It NEVER works when it auto connects.
- Music will do a brief skip when you shut the screen off
- Stupid message about volume control every time it connects (resolved by switching to custom rom)
- SMS or any kind of alert tone now turns music way down so that the tone is the only thing you hear. Which is super awesome when I'm driving my drunk friends around and they are singing along to a song when suddenly it mutes so everyone can hear my incoming text message.
Not a single one of these issues existed when I had my Fuze.

Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM

orb3000 said:
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
Click to expand...
Click to collapse
No I do not think so, because I used the official WM6.5 with the same problem. Does someone know a way around this issue. I strongly believe that if only I could pair I have some options to work with it (in 6.1 it worked like a charm). If I only could pair without having to send the passkey it would be great step forward. I presume with sending the passkey, the bluetooth of the TP2 sends out other "rubbish" that confuses my carkit.

My problem is solved and guess what, it had nothing to do with my TP2. The problem was my carkit. It has a maximum number of bluetooth devices (5) it can pair to and the last one (the WM6.1 version of my phone) had been reached. So a hard reset on the bluetooth carkit and the problem was solved.
Well, at least I now know how to flash a rom to my phone and I think I learned more about the phone reading through all the forums. Thanks all for thinking with me on this problem!

Does anyone else still have this problem?? I have removed all the devices from my car and continue to have the same pairing error just after entering the passcode. Stock Spint ROM worked great, but multiple 6.5 upgrades don"t pair..............suggestions/ideas??????

bluetooth settings, advanced, enable beam data exchange,check the box

Interesting.....I actually found a fix. Instead of pairing the phone with the car, I paired the car with the phone. I didn't even know that this was possible, but it did the trick!

[Solved] Blutooth 4.0 Comapitbilty issue.

[SOLUTION IN THIS POST]
There seems to be a compatibility issue with the new Bluetooth 4.0 of my HOX when pairing with some devices that have BT 3.0 version.
My own issue is with the Car Audio System of my 2008 C350 Mercedes Benz. The Bluetooth telephony worked perfectly with my DHD.
Now, I can pair my HOX with the system, but when I receive a call I can hear the other party only for 2 seconds then the voice is gone. As if we've both muted the call.
On the other hand, when I call someone, the phone call goes through just fine.
I've been reading a lot concerning this subject, and it seems that people are having the same problem with their SGIII.
A software update of the SGIII that was released for some carriers seems to have fixed the issue.
Also, my sister's iPhone 4S works fine with the system, even though it has BT 4.0.
So I believe this issue can be fixed, but it needs one of the Gurus on XDA to come up with a fix

My issue was slightly different (phone would pair but not connect) and I got onto my car kit manufacturer (in this case was a parrot system used in a mitsubishi) and found out I could update that. Since updating my car kit have had no problems at all.

That's good to hear. I read somewhere that updating the car system could be a solution.
But I'm hoping a solution could be made on the phone's side.

xbiggyl said:
That's good to hear. I read somewhere that updating the car system could be a solution.
But I'm hoping a solution could be made on the phone's side.
Click to expand...
Click to collapse
there might be nothing wrong on the phones side, have you checked to see if you can update your devices that are having problems as suggested?
i've had no issues running even bt2.1 stuff

Updating did not fix the issue.
Other phones (with older versions than BT 4.0) work perfectly.
I don't have access to updating my car's audio system atm, so I'm hoping something could be done on the phone's side.
But since this isn't a very wide spread problem among XDA users, I'm thinking it's not going to be an easy task.

Update:
Today, I tried something. After answering a call, the same thing happened (after 2 seconds I could no longer hear the other party but the call didn't drop)
On my HOX I chose Speaker and I was able to hear the other person talking; switched it back to BT handsfree (my car's audio system) and it worked.
Even though this is not a solution, but at least now I can answer a call when I'm driving. I just have to switch to Speaker then BT... Still better than nothing

Having a similar problem with mine, it pairs fine, I can access the phonebook etc but as soon as you try to make a call the bluetooth disconnects. However, i've found that if you turn the bluetooth off and back on again and re-pair it, it seems to work properly.
Would be nice if it just worked first time though.

p5x said:
Having a similar problem with mine, it pairs fine, I can access the phonebook etc but as soon as you try to make a call the bluetooth disconnects. However, i've found that if you turn the bluetooth off and back on again and re-pair it, it seems to work properly.
Would be nice if it just worked first time though.
Click to expand...
Click to collapse
Which ROM/Kernel are you using? And which car audio system are you trying to connect to?

bmw car
viper x rom but tried it on others and had the same problem

p5x said:
bmw car
viper x rom but tried it on others and had the same problem
Click to expand...
Click to collapse
After reading about this subject extensively, it seems that updating your car audio system is the best solution.
I suggest you take an appointment with the BMW service station and have them update your system.

yeah, i'm going to look into it. did you get yours sorted?

Bmw bluetooth 4.0
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.

p5x said:
yeah, i'm going to look into it. did you get yours sorted?
Click to expand...
Click to collapse
No I haven't yet. But I guess I'll try to get an appointment for next week.
For the time being, the workaround I came up with (switching to speaker phone then back to BT during a call), is working for me.
staalduinen74 said:
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
Click to expand...
Click to collapse
Does the call drop completely? or you simply stop hearing the other party?

I noticed something new today.
During a phone call (connected to Car Audio System), and I receive an SMS, the same thing happens (but the workaround still works).

staalduinen74 said:
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
Click to expand...
Click to collapse
have you checked with them recently?
Have you tried other phones with the car? wondering if the SGS 3 would have the same problem...
---------- Post added at 10:23 PM ---------- Previous post was at 10:21 PM ----------
xbiggyl said:
For the time being, the workaround I came up with (switching to speaker phone then back to BT during a call), is working for me.
Click to expand...
Click to collapse
thing is, when I try to make a call the bluetooth connection drops so I have to turn the bluetooth off and back on again to be able to reconnect

p5x said:
thing is, when I try to make a call the bluetooth connection drops so I have to turn the bluetooth off and back on again to be able to reconnect
Click to expand...
Click to collapse
Have you tried a custom kernel? I recommend Faux

SOLVED
Even though this is an old thread, I wanted to let you know that this issue has been fixed.
By updating my Hboot to 1.31 and using a jelly bean ROM, I no longer have a problem with Handsfree over Bluetooth.
For those of you who are still facing this issue, I hope this helps.
NOTE: Before updating to new Hboot, you need to make sure your CID allows it. Check here.
Also you need to flash a jelly bean ROM afterwards, I use ARHD and it's pretty good!
.
Cheers!