I think I found a fix for the BT Hands Free not working the way it should.. I can even use call waiting now and it does not kill the mic when I switch back to the first call..
I set the phone settings to automatically pick up after one ring.. No, it will not automatically pick up after one ring but, now I am getting the name to display in the caller ID field of my xLive mp3-BT headset. and it is working consistently.. I HAVE NEVER gotten it to work consistently before.. NEVER. i will try it with my Jabra BT800 later too.
I think it makes a "deeper" or better connection by making the phone try and make the BT headset device automatically answer???
I am using 2.20 OS and it is the only one that I have found to work, (not fully but it does work BETTER), please try this with other Hands Free devices like car kits and HBH660 etc.. Also try this with 2.02 and 2.06
ccrrazzzy said:
I think I found a fix for the BT Hands Free not working the way it should.. I can even use call waiting now and it does not kill the mic when I switch back to the first call..
I set the phone settings to automatically pick up after one ring.. No, it will not automatically pick up after one ring but, now I am getting the name to display in the caller ID field of my xLive mp3-BT headset. and it is working consistently.. I HAVE NEVER gotten it to work consistently before.. NEVER. i will try it with my Jabra BT800 later too.
I think it makes a "deeper" or better connection by making the phone try and make the BT headset device automatically answer???
I am using 2.20 OS and it is the only one that I have found to work, (not fully but it does work BETTER), please try this with other Hands Free devices like car kits and HBH660 etc.. Also try this with 2.02 and 2.06
Click to expand...
Click to collapse
umm. a bit confusing. care to rephrase.
In depth
With 2.02 or 2.06 or the Sin's merged OS, ANY BT headset device or car kit device that needs to use the Hands Free profile, the mic does not work on the device and there is sound that comes out of the XDAII speaker and only the mic on the XDAII works.
People can not hear you when the only mic that is working is on your phone..
Now on the 2.20 translated OS, Hands Free profile does work BETTER. It does not work fully! The caller ID is not displayed right all the time and the most frustrating part is, when the phone receives a call on call waiting, you can switch over to the other call BUT when you switch back, it acts like 2.20-2.06 and the mic only works on the phone, not on the BT device and both the speakers are going giving you a "stereo" affect.
Well, why not just use the Headset Profile you ask???
I LOVE the ability to be able to scroll through my recent call list, see who is calling via the small caller ID display on my BT device and make phone calls... ALL without having to open up my PDA case or look around for my briefcase and find my XDAII.
I have all the power of a regular phone on my ear or around my neck.
BT devices that need to use Hands Free profile are ones like the BT800
http://www.expansys.com/product.asp?code=BT800
or The HBH 660
http://www.expansys.com/product.asp?code=114271
or the new one that has not been released with the only difference of it has a battery life display too.
http://www.expansys.com/product.asp?code=118678
xLive
do a search at http://www.expansys.com/ for xlive.
The xLive MP3 player - Hands Free phone device also allows me to punch in the numbers with the little joy stick and make a call. (It has other bugs though. Wait until a newer version than 1.23c comes out. They still have the old version listed. http://www.alfa-tech.com.hk/index_download.html )
Other devices that require Hands Free profile, are devices like Car Kits..
They require Hands Free profile so the caller ID is displayed and and other more robust feature can be activated.
Headset profile does not support caller ID nor other more powerful features.
My fix...
With the Hands Free profile, and setting the phone to auto answer after one ring, the caller ID is displayed with the name if it is in your contacts AND most importantly, the duel speaker and only mic on the XDAII thing does not happen when you receive another call and switch back to the original call. :lol: :wink:
Hello,
I have stumbled upon the BT problem also, and am having problems since then. I installed BT Tools, and removed the handsfree setting, but still a lot of problems.
I was quite happy seeing your post, so i Removed BT Tools, paired my HBH-660, and used your "fix".
Obervations:
When pairing, the ppc asks to set the headset as handsfree devide, and twice to set is as headset. When clicking Yes for the three, my PPC
does the following: When set not to auto-answer, the phone number is displayed on my headset, when answering, the stereo and mike effect appears.
When set to auto-answer, the phone number is displayed once, when clicking to answer the call on the headset the headset stops, the handsfree icon dissapears on the ppc, the headset icon appears, and a normal conversation is possible, without stereo and mike effect.
When i only select handsfree pofile when pairing, the stereo and mike effect appear with and without auto-answer.
I also never get the name in the display, only the phone number, eventhough the name appears on the PPC, is this a setting somehwere, or just my headset (HBH-660)
Conclusion
What OS are you using?
I am assuming 2.02 or 2.06 with the registry hkey local M, software, Microsoft, Bluetooth, "HandsfreeProfileOn"
On my Jabra BT800, I still only receive a phone number if I do not have their number in the PPC call history or as long as it is not in my Contacts too.. IE.. It only displays if it is a brand new number.
On the Xlive, it displays the number or the name, no matter what.. Well that is until the xLive times out.. Now do not go out and buy one yet, my version 1.23c is the newest OS but it needs an update. It only works for about 10 min and then you have to turn it off and back on and push the BT button 2 times and then it will work again for another 10 min!!!! :evil: :? This also happens on my wife's MPX300 with the latest ROM so it is not a problem with the XDAII software.
Bottom line = With the 2.20 OS and my "fix", The stereo affect is gone on all of my devices.. ANYCOM HS-880, Jabra BT800, Xlive XBM-100, Motorola HS810 and some other Motorola BT headset that has a AAA battery in it..
(Yes, I have bought a lot of them.. I loose things and I was hoping they would work.) :roll:
Now about your 2.02 or 2.06 OS, When you said, "When set to auto-answer, the phone number is displayed once, when clicking to answer the call on the headset the headset stops, the handsfree icon dissapears on the ppc, the headset icon appears, and a normal conversation is possible, without stereo and mike effect. " I would like to know what happens when you set it to answer on 2 or 3 rings, maybe it will display the caller ID longer. Also, I would like to know if the stereo affect comes back when you get another call on call waiting.
I tried it in version 2.06 and it does not work. It can connect the bt earpieces, but no sound. It kills the connection with the original MS bt stack as well.
I believe the OS you are using is 2.20, just wonder is it a Simplified Chinese OS ?
adad said:
I tried it in version 2.06 and it does not work. It can connect the bt earpieces, but no sound. It kills the connection with the original MS bt stack as well.
I believe the OS you are using is 2.20, just wonder is it a Simplified Chinese OS ?
Click to expand...
Click to collapse
If you use OS 2.20 the problem is gone. During pairing select ONLY the first time is asks for Handsfree/headset. Discard the second time. (I Don't know why exactly)
Be aware that no matter how "simple" a headset looks, they have their own set of problems by themselves, not only XDA-II related.
And BT specs for protocol 1.2 is already out there....
:?
Man!!!! I do not know what is up now! :x :? :shock: :evil: :twisted:
On my BT800, I have tried setting it to No Auto Answer, un paring, re pairing with Selecting Yes to Serial, AND YES to both Handsfree/Headset prompts and I can not get it to mess up when another call comes in.
I have tried Selecting Cancel to Serial, Yes to the first Handsfree/Headset prompt and No to the second.. Still no problems.
I have tried only selecting the second Handsfree/Headset prompt and still no problem..
Now, remember, the BT800 sucks! The caller ID is not working BUT that is a Jabra BT800 issue.. It just sucks! Same problem with no caller ID on my wife's MPX300.
The only thing that I can see as my problem was I used to have BT Tools installed and I never could get it uninstalled all the way until I renamed the bthserial.dll. So, I am assuming that BT Tools also had it's own DLL for Headset too???!! Thus that was my problem? I guess.
So, my "fix" is wrong.. I take it back. It makes no difference!
I am sorry.
Looking Glass said:
If you use OS 2.20 the problem is gone. During pairing select ONLY the first time is asks for Handsfree/headset. Discard the second time. (I Don't know why exactly)
:?
Click to expand...
Click to collapse
I noticed NO difference on BT800, or my ANYCOM 880, or from my two Motorola ones.. I do not know if it makes a difference on other devices.
Looking Glass said:
And BT specs for protocol 1.2 is already out there....
:?
Click to expand...
Click to collapse
Could you explain more please?
On my xLive it only has one BT Handsfree/Headset prompt but on the xLive, it lets you select the pairing mode... Hands Free or Headset.
It ALSO has excellent caller ID display! When I may have had a Partial BT Tools installed, I only got caller ID. Now, I get the name too if it is in my contacts list!
I also found out how to use the xLive without all the problems!!!
It took me about 2 hours to do this..
BT headsets...
It looks like the other devices with caller ID on them, HBH-660 and the HBH-220 do not work great and I know for SURE the Jabra BT800 is crap.. (even in Headset Mode it takes up to 9 seconds to answer a call.. In Hands Free mode, it is only 2 seconds but the caller ID does not work)
So, the ONLY solution for those who want caller ID on a handy little device is, the xLive.
I recommend the xLive now. I found that the xLive will screw up if you press certain buttons or for other reasons explained below and if you do not press them or do the other things, it works fine.
I am not sure if People can get A2DP to work on the XDAII, I have seen most say they can't, SO, the next best thing is the xLive! It also supports caller ID and will list the Callers Name if it is in your contact list AND you can DIAL phone numbers with it, all while your XDAII is 30 feet away. You can dial numbers with it through pressing the BT button, selecting "Dial" and using the little joystick to select the numbers and then press the BT button again to dial!
xLive also supports MP3 streaming though a program the give you and a your typical BT device hooked up to your PC. I have one that only cost $39 and it works for about 150 feet. You can get past it's memory limit this way.
How to use the xLive with an XDAII with 2.20 translated ROM.
1. Pair it using “Hands Free” mode, selecting “Pairing Clean”, once, (you do not have to repair again)
2. When you FIRST turn the xLive ON or if you are unable to make call through it or get calls through it, press the Bottom Right Button for 2 seconds to turn it off. Then Turn it back on with the same button. Then Press the BT button on the front left, next to the screen, wait 4 seconds, press it again and wait 6 or 7 seconds until the little BT icon appears then press the Top Left button (A-B and Record, AKA cancel)
3. Never hang up a phone call using BT button! ONLY USE THE “END CALL” function of your phone or wait until the other person has hanged up. If you press it, redo step 2! (the BT button is the one on the left of the screen)
Problems that will cause you to have to turn it Off and then back ON again,,, IE. Repeat step 2.
You can ONLY reject ONE phone call.. After you do, go redo step 2
If you Miss a call, go redo step 2!
If you reboot the XDAII or the two get out of range of each other, you only need to press the BT button and then press the Cancel button after the BT icon appears again.
http://www.expansys-usa.com/product.asp?code=111023 128 $82.95
silver.
http://www.expansys-usa.com/product.asp?code=116333 256 $128.95 Black
http://www.expansys-usa.com/product.asp?code=111492 256 $128.95 White
http://www.expansys-usa.com/product.asp?code=111493 512 meg not out yet.
ccrrazzzy said:
Looking Glass said:
If you use OS 2.20 the problem is gone. During pairing select ONLY the first time is asks for Handsfree/headset. Discard the second time. (I Don't know why exactly)
:?
Click to expand...
Click to collapse
I noticed NO difference on BT800, or my ANYCOM 880, or from my two Motorola ones.. I do not know if it makes a difference on other devices.
Looking Glass said:
And BT specs for protocol 1.2 is already out there....
:?
Click to expand...
Click to collapse
Could you explain more please?
As for you first question: It does a difference to me. Some devices use different functions if they are paired ONLY as headsets or as HANDSFREE. The mess about "what you do in the two step pairing" is probably part of the problem. I've found that the first pairing is best for headsets (HBH 35, HBH 600) and the dual pairing is needed for carkits (at least for my BMW carkit).
Second question: BT specs 1.2 means that there are more profiles and functions that now can be implemented in more devices: SO MORE TROUBLES, and more chances for something to go wrong. There is a lot on information about BT specs out there, you can read about, and wonder what will happen with a device that implements them all.... the HTC/MS way!
And finally, some comments about the "erratic" behaviour of caller ID on your headsets: I've found some remarks noting that depending if your contact info for a certain number is stored in the phone memory OR IN THE SIM CARD, it might change how the info is passed onto your BT headset! So you can see the name, the number or even nothing at all for a few seconds.
:?:
Click to expand...
Click to collapse
Sorry, I have been away from this forum for a while and have decided to come back and try and face my BT issues again.
I am running
ROM 2.06.00WWE
Radio 1.18.00
ExtROM Sin.Merged.v1.0
on an XDA11 with a Blue Ant hands free.
Before upgrading the BT was crap.....long delays in answering, no redialling facility worked and the sound quality was awful.
Since upgrade I really couldnt tell you about the other issues but sound quality appears to be worse. My incoming is fine but out going, the hands free mike is not working and the phone is still receiving on its built in mike. I have tried pairing as "Handsfree" and "headset" with no difference.
Any ideas?
Cheers
Mark
OK,
sat in the car had a beer and tried again. Selecting "handsfree" when prompted and no and no to headset enables the in car mike and allows outgoing calling. But does not allow incoming calls pickup.
Every other config of headset and handsfree combo selections removes the in car mike from working.
Go Figure?
Cheers
Mark
teknophob said:
OK,
sat in the car had a beer and tried again. Selecting "handsfree" when prompted and no and no to headset enables the in car mike and allows outgoing calling. But does not allow incoming calls pickup.
Every other config of headset and handsfree combo selections removes the in car mike from working.
Go Figure?
Cheers
Mark
Click to expand...
Click to collapse
Hi! As said before, you'll be better off with 2.20.
2.0x versions work mostly OK as far as functions, but then you have the dual mic/speaker problems....
Read the forum, there is NO perfect BT solution, in fact, there is not a official version claiming to support HandsFree profile...
Yep,
I hear you, I know the o2 is not handsfree compliant only headset.
The local gurus at Strahfields are trying to sell me the latest Nokia bluetooth hands free.
I quote,
"Its compatible with everything and my mate has got an o2 and it works fantatsically" unquote.
But they where not prepared to give me a demo.
Cheers
Sorry if I am being stupid, I currently use the Diamond 1.2 ROM and have a BT800, so I know all of the problems in trying to get the mic working etc.
Is there an English ROM with 2.20 that's easy to install?
There are so many references and links to various CAB files on here, but as I use my XDA2 for business, as well as pleasure, I don't have time to experiment I would like to find an installer, do that, and then add my own apps, and be up and running within an hour.
I bought the BT800 for the call quality, not the extra features, but now I have a headset that can do so much more, I would like to make use of all the features, but not at the expense of the PDA's stability, although saying that, Diamond 1.2 gives me the hang on reset issues, and random slow down issues too, so it may be better to change to something else anyway.
ccrrazzzy said:
I think I found a fix for the BT Hands Free not working the way it should.. I can even use call waiting now and it does not kill the mic when I switch back to the first call..
I set the phone settings to automatically pick up after one ring.. No, it will not automatically pick up after one ring but, now I am getting the name to display in the caller ID field of my xLive mp3-BT headset. and it is working consistently.. I HAVE NEVER gotten it to work consistently before.. NEVER. i will try it with my Jabra BT800 later too.
I think it makes a "deeper" or better connection by making the phone try and make the BT headset device automatically answer???
I am using 2.20 OS and it is the only one that I have found to work, (not fully but it does work BETTER), please try this with other Hands Free devices like car kits and HBH660 etc.. Also try this with 2.02 and 2.06
Click to expand...
Click to collapse
Hi,
I see you are using Xlive Bluetooth MP3 Player... so I want to know if I can use it with the Motorola HT820 ( http://www.mtekk.com.au/tabid/54/articleType/ArticleView/articleId/641.aspx ) and my xda II whit ROM 2.20 ....
Thanks
Successfully upgraded my Qtek 8500 (UK) with both the Cingular and QTEK latests ROM
Works great.
Using for 2 days and now my microphone feeds everything back through earpiece and no one hears anything other end.
Same with walk and talk headset.
Works fine when working with bluetooth headset or car kit.
Is this a hardware fault and just coincidence, or have I messed up the registry or Radio etc.
Anyone seen similar.
Many thanks
Try a hard reset. Sounds like something may be corrupt in your audio managment files.
Just tried a hard reset, but no joy I'm afraid.
I have reloaded the ROM twice as well.
Is there a way to rebuild and reload these management files.
It has to be software as the walk and talk headset uses a different electronic channel and separate mic!
Well that's my theory
http://www.jetwaremobile.com/install.htm
Here's a link to Jetware Mobile's website. Since you are obviously using a Bluetooth headset and a handsfree car kit, it may be that the BT extension is getting twisted up. You can download and install a free trial I believe for 30 days. I did not need this for my BT connections with the QTEK 8500 but these things can be very hardware specific. By the way, did you try the phone after hard reset and prior to pairing with any of your BT devices?
Sorry to clarify, it is the handset mike that is not working.
When used with BT, voice is transmitted OK to recipient.
However using handset by itself all you hear is a slightly delayed repeat of your own voice in the handset earpiece and the call recipient hears nothing.
Thanks
Danny
I had a similar thing happen to a Sony Z600 and traced the problem to a resistor that failed. Apparently this controled where to route the audio when a wired headset was plugged in and when it failed everything routed through the headset port vs the speaker. Not sure if this is what's happening to your Qtek, I've got one as well and sometimes it just acts wierd, drops calls, wont hang up, wont recognize key presses but I just attribute it to the MS operating system. By the way, you can pick up Z600's fairly cheap, it's a great 2nd phone & syncs with outlook, I picked up another after my first crapped out with no problems.
When I am playing music and I receive a call, after the call ends the bluetooth connection just disconnects. I have to press the play button on little necklace for it to connect again. Anybody have experience with this headset? My last sony headset, DR-BT30Q, works just fine. My current one that I just ordered, the HBH-DS980, plays fine, but it just disconnects after a phone call.
I searched this forum and "HBH-DS980" didn't pull up any matches. I read in the Kaiser forum some ppl installed some jetware software. I would like to get some input with Mogul owners though. Oh yah, I'm running DCD's 2.1 rom based of 3.16.
WOOT. After installing Jetware mobile, I am not getting a drop after a phone call anymore. Now I'm starting to love this headset.
http://www.jetwaremobile.com/index.htm
Do you get phone book on the headset ?
I'm not sure. I have to check back. But today, after resetting my phone, I am still getting the drop after a call. I have to press the play button and it connects right back up, but still annoying.
I do know I get the call list so that I can make a call.
yes, the contacts work.
Wow, I can't get the contacts to work
You have Mogul /Titan as well ? Any special steps you did to get it working ?
Same problem here with the phone call disconnect
Meh, I assumed they work. Earlier my PPC said allow HBH-ds980 to get contact info, or something like that, so I thught it worked. Now It doesn't do anything. I've found this Bluetooth headset works sometimes and doesn't work at other times. Sometimes off a fresh restart on my PPC it will not drop the connect, most other times it will.
Having problems with the speech feature with my car's bluetooth.
My 920 pairs fine with my car's bluetooth, and I can receive calls fine.
However, the speech feature where it reads incoming text messages is not working. Under Settings > Speech, I've got all the checkboxes checked, and I've tried everything from "Always On" to "Bluetooth and headsets" but nothing works. I receive a text, my phone plays the notification sound, and then nothing.
With my previous WP7.5 device (HTC HD7), this feature worked flawlessly with my car and other bluetooth headsets. Unfortunately I got rid of my headset so I can't test it with my 920.
Interestingly, I once made a call, and while it was still ringing, I got an incoming text message and bam - my phone spoke over the active bluetooth session and prompted me whether I wanted the message read aloud. The call went through and the phone was unable to pickup any commands.
Also, starting a voice command, while my phone is actively paired with my car, the phone can no longer "hear" my voice commands. Like it thinks it initiated the bluetooth session, but in reality it hasn't.
Anyone else having similar problems, or better yet, a solution??
I can only think of something to try out to get a little more information on the scope of the problem.
You could turn it to always on and try sending a text message to the phone while it is not connected via Bluetooth (e.g. at home while having the device on the table) and check wether it works then. If so, then it seems the problem is with the compatibility of the phone and the car's bluetooth.
Hi StevieBallz - gave that a shot and yes, that works. It seems there are some other people with this issue reported on various other sites. Which is a real bummer.
Played around with it some more, and it definitely seems like the phone thinks it has initiated the bluetooth "call" and is reading out commands to nowhere, and unable to hear commands as well.
I would say this is a bug and not mere incompatibility issue. If they had it working fine on WP7.5, there's no reason they couldn't implement it the same way
Given that they are now using the Windows 8 Bluetooth Stack instead of what was there in Windows CE I would say there are several reasons why it's implemented differently but that's not really the point. If there are other people with incompatibility issues that might lead to a fix down the road. The more interesting question though would be if there are Bluetooth pairings where this works with the 920, because if it doesn't work with any Bluetooth devices I guess that would get fixed pretty soon.
I fear I can't give you any more advice than to contact support on your issue so that they get aware of the situation (because I guess Nokia won't be scouting forums for all kinds of possible bugs). I hope they will fix the functionality for you soon.
PS: I can't count the number of times I've seen issues with Bluetooth. No matter what devices I use, Bluetooth still seems very hit and miss Working with the BMW Bluetooth but only partially but working fine in an Audi. Sometimes only with Blackberry, etc. One would believe if there is a standard they would get all this sorted out someday but somehow they don't.
ultrabob said:
I would say this is a bug and not mere incompatibility issue. If they had it working fine on WP7.5, there's no reason they couldn't implement it the same way
Click to expand...
Click to collapse
It works on my car ('10 nissan). It works on some cars/bluetooth stacks, and not others. This, by definition, is a compatibility issue. Now, why this stack fails against other stacks, when the CE stack worked, is a good question.