Related
hi.
i just bought a motorola bluetooth handsfree for my car HB830. i paired it to my exec and it started working. now the problem is that sometimes the pairing fails and the phone doesnt transfer the call to the handsfree i.e the call remains in the phone. when this happens the exec shows that bluetooth is turned off which i switch back on but the problem comes back after the next call. i.e the phone doesnt seem to be able to transfer the call to the handsfree.i have upgrade my ROM to Rom:1.30.107 WWE
Radio: 1.09.00
Ext ROM: 1.30.162 WWE
is this a problem with the new radio ? should i downgrade to the older radio? if yes then which one and how do i? please help me guys.. thanx
My Uni does the same with my parrot CK3100 car kit...
Its a major pain in the ass....
Seems to work fine with my Jabra JX10 tho..
:roll:
Same problem here with a medion bluetooth car radio.
Most of the times my universal thinks it's paired (icon in the calling screen), but when making or receiving a call it disappears.
After a succesfull bluetooth call, it isn't posible anymore to call handsfree.
Bluetooth also regulary turns itself off. Tricks found in another topic are not the solution for me
if you enable the device lock start\settings\personal\lock
Prompt if device is unused for 16.7 hours
set simple pin
the phone and the parrot device keep there pairing with no problem at all i have been testing it for the last 48 hours
if you disable the above it loses the paring straght the way.
strange is they anyone else who can try this
Thanks
Paul
bluetooth headest problem
hi.
1st thing how do u set it for 16.7 hrs.... it just gives me options of rounded off hours.
i tried setting it for 12 hrs.. it works better but still a problem
Maybe this is a clue:
I use the newest Qtek German Rom, which is from April or May. This should be same version like WWE version.
Since I upgraded to this Rom, all my problems with Bluetooth disappeared. It works fine with my Logitech mobile pro 2 headset. I assume, the problems are only because of the rom.
try upgrading and see, how it works.
Hello there.
I'm a newbie to using A2DP/AVRCP, sorry about that, but I have big issues.
I have huge lag when trying it out.
Specs:
HTC Universal
Midget's WM6 (Crossbow)
Radio 1.14
Bootloader 1.01?
Sony DR-BT20NX (really nice ones).
Anyways. I pair it up, no problemo at all. Tried a few calls. Works fine. Selected both handsfree and wireless stereo from profiles ofcourse.
So, I tried playing a movie in TCPMP. Audio and Video stutters every second. Tried playing a MP3 file in Media Player. Audio lag every second.
DAMN!
So, I went in to all these threads about A2DP/AVRCP in the forum (read them before) and checked out fixes etc. Everything seems to already be applied in this ROM. Priority256 value exists (in another folder though as described for another device, HKLM/BuiltIn/Drivers/WavDev I think)
What the heck can I do? I'm not comfortable applying different patches because I think A2DP support in every manner is already applied, so as the registry values.
HELP ME!!
Following the development/information on MS BT Stack change to Widcomm BT Stack on following links
http://forum.xda-developers.com/showthread.php?t=279236
http://forum.xda-developers.com/showthread.php?t=285419
http://forum.xda-developers.com/showthread.php?t=285696
http://forum.xda-developers.com/showthread.php?p=1073003
Any one know more?
Just a thought. Is it possible to deactivate SBC (recoding/decoding) of MP3's?? My Sonys support direct MP3 streaming.
http://forum.xda-developers.com/showthread.php?t=285419&page=20
Tried out BT Stack change for Hermes patch/program.
TEST RESULTS ON UNIVERSAL WITH WM6 (Midget aka Helmi unreleased)
Sound IS great. But other than that, this program does not work very well on my device. Of course this is designed for Hermes but I gave it a shot.
Issues:
1:
Screen flickers (only when this BT is turned on).
Flickers really bad and unable to use device.
Fix: set the device to standby (power button) and wake it up again. Flickering gone
2:
Once BT is deactivated for a few minutes I can't start it again.
Fix: No fix found yet. Only a Soft-reset and directly activate BT works.
3:
I can't use my GSM/UMTS connection anymore. Trying endlessly. Even after soft-reset's I can't connect. WiFi works fine though.
Fix: No fix found yet.
4:
Unable to uninstall this program. Tried several times. I get to the "Soft Reset Device Yes/Cancel". I soft reset, program still there and working.
5:
Hard-Reset, complete setup with WAP, MMS, MAIL etc.
Installed Widcomm BT Stack again.
Soft-reset:
Screen flickering (fix)
No 3G/UMTS connection avalible anymore. Even when BT stack is completly shut down.
We need a specific one for our Universal. Who's up to fixing this for us?
KEEPING this post updated.
EDIT 06: 18:40 @ 21/01/07
ANYONE into programming/developing interested in taking this as a sideproject so all of us Universal users can benefit from this great software?
PS. No, Nuclear (aka Infidel)! Pleace do not participate in other than testing. And if you do, please don't be too exited and write lies/bs in this thread. Thank you. Ta ta
I'm currently using Midget's WM6 with a set of Motorola HT820 bluetooth headphones without any problems.
In fact I've tried a couple of WM6 roms now and both have had working a2dp & avrcp and if anything quality is as good as the AKU3.3 I was previously running.
AVRCP & connecting up seems to be a little more reliable than the last rom as that would occasionally lose the pause control, something I don't think has happened on WM6 yet.
It might be worth trying your device with a different set of bt headphones to see if the problem persists.
Taz69 said:
I'm currently using Midget's WM6 with a set of Motorola HT820 bluetooth headphones without any problems.
In fact I've tried a couple of WM6 roms now and both have had working a2dp & avrcp and if anything quality is as good as the AKU3.3 I was previously running.
AVRCP & connecting up seems to be a little more reliable than the last rom as that would occasionally lose the pause control, something I don't think has happened on WM6 yet.
It might be worth trying your device with a different set of bt headphones to see if the problem persists.
Click to expand...
Click to collapse
Hmm. Headphones shouldn't matter, should it?? It's one thing if the sound in my headphones is bad, but it is the DEVICE that has problems actually outputting to the recoder fast enough. It works fine with the Widcomm!!
Taz69 said:
I'm currently using Midget's WM6 with a set of Motorola HT820 bluetooth headphones without any problems.
Click to expand...
Click to collapse
Did you need to do any extra tweaking on Midgets ROM to get them to work properly?
edeplano said:
Did you need to do any extra tweaking on Midgets ROM to get them to work properly?
Click to expand...
Click to collapse
i've hs-12W. I'm using it with midget's first vanilla crosbbow rom without any problems. without any tweaking.
I have tried the broadcomm stack on WM6 but couldn't get my jabra bt620s stereo phones to connect to both the headset AND stereo profile at the same time - if I connected it to the stereo profile, then it sounded great, with no log, but wouldn't act as a headset. If I connect it as a headset, it works fine, but all audio is mono, even stuff that shouldn't be. Should I be able to get this working for both at the same time?
Worked straight away without needing any tweaking.
Both stereo & phone headset work okay.
Also had Stereo configured with Universal and Phone paired with a hermes since getting a second data SIM and that setup is working okay as well.
Taz69 said:
Worked straight away without needing any tweaking.
Both stereo & phone headset work okay.
Also had Stereo configured with Universal and Phone paired with a hermes since getting a second data SIM and that setup is working okay as well.
Click to expand...
Click to collapse
Thanks Taz!
Is it true that this headset can store two pairing profiles (ie I can have them paired with my Qtek and my PC)?
Hello all,
Thanks for the help you provide in this forum. I am wondering if bluetooth is working for you in the official WM6 rom? My Trinity does not want to recognize any bluetooth devices. I have three - my laptop, my glasses and my headphones. Non are pairing and it says it cannot find any bluetooth devices. In the WM5 rom, it was no problem. Can anyone help?
Best regards,
Gilbert
edit: sorry ignore me
Gilbert said:
Hello all,
Thanks for the help you provide in this forum. I am wondering if bluetooth is working for you in the official WM6 rom? My Trinity does not want to recognize any bluetooth devices. I have three - my laptop, my glasses and my headphones. Non are pairing and it says it cannot find any bluetooth devices. In the WM5 rom, it was no problem. Can anyone help?
Best regards,
Gilbert
Click to expand...
Click to collapse
I'm using with a jabra handsfree BT250v and there is no problem using it - works very well.
Plantronics Pulsar 590A , headset and wireless stereo working perfect.
VM
Infact the WM6 is faster in detecting present of my iTech bluetooth headset.
I just wish they would have fixed their stack to work with Microsoft Voice Command on mono headsets! It always amazes me how Microsoft can take the few great ideas they have and f**k them up! Not that it's entirely their fault but you think they'd have had it working on the more popular devices, especially with those of the company they are always raving about!
any improvement with a2dp at all with wm6?
drewy said:
any improvement with a2dp at all with wm6?
Click to expand...
Click to collapse
OS is moving faster with A2DP activated. I can listen mp3 over WiFi without sound drops.
VM
Bluetooth connection is much faster and better than that of WM5.
No problem in connection to WMP via my Itech Bluetooth earphone.
ckleea said:
Bluetooth connection is much faster and better than that of WM5.
No problem in connection to WMP via my Itech Bluetooth earphone.
Click to expand...
Click to collapse
I have an itech clip II how can I listen to WMP or Destinator navigation sounds through my BT?
Hmmm... Got different experiences, found that bluetooth on new official WM6 has some issues with my HT820 A2DP headset.
1. Every time to start the mp3 will skip first 2-3 seconds.
2. The connection will getting unstable after 30-40 minutes continue playing.
3. Randomly my HT820 will lost connection with my CHT9100, also in the Comm. Manager will showed Bluetooth "disabled", but the blue LED still blinking as usual. Tried to turn it off and on but no success, have to push the reset button to clear out the mass.
Hope this might make you feel better, you are not alone...
Cheers,
katsj said:
I have an itech clip II how can I listen to WMP or Destinator navigation sounds through my BT?
Click to expand...
Click to collapse
It is plug and play.
watchsat said:
Hmmm... Got different experiences, found that bluetooth on new official WM6 has some issues with my HT820 A2DP headset.
1. Every time to start the mp3 will skip first 2-3 seconds.
2. The connection will getting unstable after 30-40 minutes continue playing.
3. Randomly my HT820 will lost connection with my CHT9100, also in the Comm. Manager will showed Bluetooth "disabled", but the blue LED still blinking as usual. Tried to turn it off and on but no success, have to push the reset button to clear out the mass.
Hope this might make you feel better, you are not alone...
Cheers,
Click to expand...
Click to collapse
I am having the exact same issue with my S805's. Both made same time by moto, so similar setup I would say.
Gilbert said:
...My Trinity does not want to recognize any bluetooth devices. I have three - my laptop, my glasses and my headphones...
Click to expand...
Click to collapse
I don't use any Bluetooth devices (sometimes my laptop), can someone tell me what Bluetooth Glasses are???
Thanks
is there still a high cpu usage with a2dp playing? Is the os still usable for other functions?
The CPU usge for a2dp is still high with this WM6 Rom, but it does not drop at all. The usage is
I have Contacts(with 500 entries), Resco File Explorer 2007, calander, phone, and not forgotten the Core Player loaded with the ram down to 19Mb, there is still no drop in the audio. One exception is the touch screen, if you touch and and move with frequency then u will surely experience drop in audio. I am sure we Trinity or D810 user had known this issue since day.
the updated rom seems so far so good. All I have put on is trinity hacks and tomtom so far, so I wonder if it has to do with all the other junk or the update.
its called RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship.exe
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.
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!