Develop Bugs

Bluetooth randomly disconnects using LVSW

Well I'm using LVSW 04-08-07, and I'm having issues with my Bluetooth staying connected.
Basically it will just randomly shut off on the phone and I have to re-enable it in order for my headset to work.
At first I thought that it was my headset ( Jawbone ) but then I tried it in my car with my Motorola T305 speaker and it does the same thing.
Does anyone know what could be causing this?

I had the same problem too. I am using my sony bluetooth headset witht eh latest LVSW 4-8-2007 rom which I didn't have problem with any other roms. Maybe there are specific settings that we missed out ???

Well it's good to know it's not just my phone with this issue...

Make sure that you have the bluetooth voice command set to "enabled".(start>programs>b/t voice command config>enabled) I have not had any disconnect issues since I set that up.
Hope this helps.........Later

BT
Same here, until 04 version it was ok (on the other LVSW versions). Now it randomly disconnects.
Also seems like my battery is draining WAY faster.

nukenine said:
Same here, until 04 version it was ok (on the other LVSW versions). Now it randomly disconnects.
Also seems like my battery is draining WAY faster.
Click to expand...
Click to collapse
Be sure to check/turn off I/r beam function.I had horrible battery life until I looked and found that the receive incoming beams was checked. I unchecked it and my battery life has increased greatly!
Hope this helps........Later
BTW I have had this issue with ALL LVSW roms, not just the latest one. But the roms are so damn good that I am willing to fix the few small issues they may have.

^^^ Beam now off - thanks.
But BT still disconnects like it's going out of fashion. Will probably downgrade to 03-26 which to mee seemed more ok than this one. Thanks anyho.

nukenine said:
^^^ Beam now off - thanks.
But BT still disconnects like it's going out of fashion. Will probably downgrade to 03-26 which to mee seemed more ok than this one. Thanks anyho.
Click to expand...
Click to collapse
Do you have the bluetooth voice command config in your programs? If so, open it and enable the b/t. If not, it is in one of the threads regarding m$ voice command issues. It seems to help keep the bluetooth connected.
Later...............

ahfunaki said:
Well I'm using LVSW 04-08-07, and I'm having issues with my Bluetooth staying connected.
Basically it will just randomly shut off on the phone and I have to re-enable it in order for my headset to work.
At first I thought that it was my headset ( Jawbone ) but then I tried it in my car with my Motorola T305 speaker and it does the same thing.
Does anyone know what could be causing this?
Click to expand...
Click to collapse
I had similar issue with LVSW 040807 and bluetooth headset (specifically with M$ Voice Command) but I did not the issue with the 032607. It might have something to do with the AD2P fix that was applied in that version.
Also how his the Jawbone headset, is it as good as the marketing?

Same proble here!, my TyTn randomly disconnect from my Parrot bluetooth car hands free, it's a really annoying thing.
I had sam problem using previous LVSW version.

Not using voicecommand at all - battery gone after half a day.
BT disconnects left, right & center.
Previous LVSW version worked fine.
I'll downgrade as soon as I find some time (to re-install my stuff ).

Same here using 05.04.07 (or LVSW-547)

I am using LVSW and it drops out maybe once to twice a day.
Battery life is good. I easily get a good day out of the phone with out charging. That includes several hours of talk time.
Hopefully in future realease he fixes the problem.
Great Rom.

Hmm if there is no solution to this I might just have to downgrade...

Thread for Bluetooth Problems with Black 3.0.1

I did a search on the other thread and found many people with the same issue. In order to organize our thoughts on this topic I would go ahead and open a thread for it and maybe this will help jj and community members to find a solution.
My problem is much like everyone else. I can connect my motorola S9 they will play music; however, when I go to try to make a phone call or answer a call all I get is a slight hum through the headset with no audio and a possible freeze of the device. The slight hum is initiated by pressing the phone icon button on the headset.
I hope I haven't pissed people off by starting this thread I just thought it was necessary to come together on this because it is not just noobs having this problem but members and senior members.
EDIT: It looks like from the other thread JJ just came on and addressed this issue and is working on a fix. mods please remove this thread.

donsaxena said:
I did a search on the other thread and found many people with the same issue. In order to organize our thoughts on this topic I would go ahead and open a thread for it and maybe this will help jj and community members to find a solution.
My problem is much like everyone else. I can connect my motorola S9 they will play music; however, when I go to try to make a phone call or answer a call all I get is a slight hum through the headset with no audio and a possible freeze of the device. The slight hum is initiated by pressing the phone icon button on the headset.
I hope I haven't pissed people off by starting this thread I just thought it was necessary to come together on this because it is not just noobs having this problem but members and senior members.
EDIT: It looks like from the other thread JJ just came on and addressed this issue and is working on a fix. mods please remove this thread.
Click to expand...
Click to collapse
yes... still investigating this issue... the drivers i used have A2DP issues...

Widcomm bt project?
My problem:
Parrot ck3100 paired and sincro without problem. But no sound, just static.
Nothing original, as I can read in meny posts.
I wonder if somebody tried widcomm bt drivers (the project for hermes) with black 3.0.1.

I've been seeing a weird issue where the phone doesn't seem to know if BT is on or off. The Comm Manager will say BT is off -- but the blue LED is blinking. You go into BT settings, and it's unchecked (and presumably off) -- but it's still discoverable from PC's. Also hitting the BT button on the comm manager doesn't always toggle BT -- sometimes it works, sometimes not.
It's not a major deal to me, since I only use BT for PAN and file transfers, but that's only because I lost my really nice BT headset.

I have the Motorola HT820.
Black 2.0, not working
LVSW 5/5 working but phone only sometime answers
Black 3.01 - Success! All buttons work and sound is fantastic with stereo. Headset seems to work for call.
Widcom stack on my lappy seems to connect ok, although it seems slower than previous roms for transferring files

I'm currently testing an uncooked version of this ROM and BT is working without any problems

Am using a Jabra BT 250 headset. Initially paired it fine but went to use it an hour later and would not connect.
Re-paired it and it worked but with static.

sag said:
My problem:
Parrot ck3100 paired and sincro without problem. But no sound, just static.
Nothing original, as I can read in meny posts.
Click to expand...
Click to collapse
Mute and Unmute by pressing the Green button twice should bring back the sound.

donsaxena said:
when I go to try to make a phone call or answer a call all I get is a slight hum through the headset with no audio and a possible freeze of the device. The slight hum is initiated by pressing the phone icon button on the headset.
Click to expand...
Click to collapse
Having the same problem on 3.0.1 flashed back to 2.5 untill the fix.
awesome speed of Black 3 looking forward to the fix

Parrot
has anyone got a way to fix that problem with the ck3100 ? i have found i can connect and dial out but my handsfree dosent give out any sound, when i try to hang up on the handsfree it wont. can anyone help me?
sag said:
My problem:
Parrot ck3100 paired and sincro without problem. But no sound, just static.
Nothing original, as I can read in meny posts.
I wonder if somebody tried widcomm bt drivers (the project for hermes) with black 3.0.1.
Click to expand...
Click to collapse

whats wrong with posting this in the thread for black 3.1? i guess this issue will never be solved not the bluetooth the stupidity

If the BT issues are a problem, do as I and many others did; flash Black 2.5 back onto the phone. Hopefully, your backup will be better than mine
But, the reality is that these are ROMs that are put together by volunteers, and use the latest available software. It can, by its very nature, contain bugs. It is NOT JJ's issue to fix them all--he's done a great job (walshieau too!) making these kick-ass roms. If you want to complain about the roms, flash the official carrier rom, and call them and complain. If you want to be on the bleeding edge, you are going to have to READ, LEARN and UNDERSTAND what you are doing--and be proficient enough to at least TRY to fix your own problems.

A2DP pitch problem

I have a Cavalier with it's original WM6 (not 6.1) ROM and I am having some stereo bluetooth headset issues and wondered if anyone has a solution.
On my Jabra BT320s (with Latest firmware) as well as my Motorola DC800 I have issues with it playing consistently. From time to time it will start to loose it's pitch. This sounds a lot like an old record player with the disk slowed down. This will continue for some time and then be ok for a bit again. It can also have drop outs from time to time as well. I've tried insuring nothing is running in the background, and even turned off the cell to insure the phone is not getting busy. In reading around the web this is not an uncommon issue. Has anyone had this problem and found a solution? Is the BT stack in 6.1 better than in 6? Is my solution to upgrade to 6.1? Could anything else be the cause? This never happens with a wired headset btw ...
Thanks in advance for your time, I love my Cavalier. Probably one of the best WM devices I've played with to date!!

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!