Database Users

Bluetooth Stack revisited

Now that we're likely to get a working solution for our Bluetooth worries thanks to TOWA it seems sensible to revisit the BT-stack implementation on the XDA II. I spent some time working through the Microsoft documentation to come up with this assessment.
All previous PDA's have used the Widcomm stack, which supports a multitude of BT-profiles,specifically the Serial Port Protocol, which it emulates as a COM-port. Unfortunately, the Widcomm stack does not support the Headset service, which is required for the phone. This is why the installation of the Widcomm stack on the XDA eventually failed -just couldn't support the headset.
The Microsoft stack actualy also supports the serial port profile, but uses a different implementation. Their BT-stack is socket based and aligned very close to the IRDA-implementation we all know from our PC's. Just as the PC generally requires that famous "IRCOM"-applet, so does the Microsoft BT-stack (this is basically what TOWA is working on).
The Microsoft Bluetooth stack is actually very flexible, which gives us hope of seeing the XDA II support more and more Bluetooth functions as time goes along.

But why did MS not implement the COM port? If it takes TOWA a week to do the job with limited resources, why couldn't MS have done the same? And if the MS Stack is flexible, why do they leave out functions when they release it?

I'm sure MS could have done it, but the they didn't do it for IRDA either.
I think they are trying to push their implementation architecture upon us.

[email protected] said:
Now that we're likely to get a working solution for our Bluetooth worries thanks to TOWA it seems sensible to revisit the BT-stack implementation on the XDA II. I spent some time working through the Microsoft documentation to come up with this assessment.
All previous PDA's have used the Widcomm stack, which supports a multitude of BT-profiles,specifically the Serial Port Protocol, which it emulates as a COM-port. Unfortunately, the Widcomm stack does not support the Headset service, which is required for the phone. This is why the installation of the Widcomm stack on the XDA eventually failed -just couldn't support the headset.
The Microsoft stack actualy also supports the serial port profile, but uses a different implementation. Their BT-stack is socket based and aligned very close to the IRDA-implementation we all know from our PC's. Just as the PC generally requires that famous "IRCOM"-applet, so does the Microsoft BT-stack (this is basically what TOWA is working on).
The Microsoft Bluetooth stack is actually very flexible, which gives us hope of seeing the XDA II support more and more Bluetooth functions as time goes along.
Click to expand...
Click to collapse
I would like to take this oppertunity to thank Towa for the great job he did with the TOM TOM gps bt issue. I will be getting my imate(xda2...) ppc soon, and I have the following questions, as I am quite a novus:
1. does the gps doohicky that Towa wrote enable the xda2 to work with the bt headset as a handsfree profile, since the xda2 only supports headset profile? or is it only to create a port so the tom tom can find it and work with it?.
2. If no to question 1, then I would like to share my expieriance with bt headsets, which I cannot understand untill this day and may be you can help?. I currently use a Nokia 6310 and previously was using it with the Ericsson hbh-20. Since, the Nokia phone did not suport voice activation or reject a call from the headset, I could only voice dial through the headset after I pushed a button on the 6310. So I thought, no biggie it was Nokia's fault since I successfuly voice dailed when paired to my friends t 68. Then I tried my 6310 with my other friends hbh-30 bt carkit, and wouldn't you know that the voice activation from the bt carkit's button worked like a charm (stumped. who to blame know, we always need someone to blame.) So, after that my third friend bought me the new Nokia clip-on bt headset, it works as a complete handsfree headset with my old Nokia 6310, rejecting, auto answer, voice dialing ... all from the headset. So, my question is do I have too many freinds? (just kidding), how do you expect the xda2 and the new Nokia clip on headset to communicate with each other?. In headset profile or handsfree profile?.
3. If your answer to question 2, is headset profile, then will we have to beg the "Great One" also known as "The Man" (as qouted earlier on gps bt forum of this site" Mr.TOWA himself, to write us another doohiky to make them work in handsfree profile.
p.s. In my opinion, anyone who has downloaded Towa's doohiky for gps and had a positive result, should donnate something for this hard worker.
Thank you, and sorry for being so boring.[/quote]

TOWA's great app only fixes the serial port issue, by basically establishing a permanent virtual com-port using the functionality built into the Microsoft BT-stack.
Unfortunately, inmplementing a Handsfree profile will be much more complex, so don't expect a quick fix on that. I'm sure HTC and Microsoft are working on it, but I wouldn't expect a fix this year.
Regarding your BT-observations, it seems that the implementation of the profiles on each device is different and probably none of them are really complete.
I think the Bluetooth Org will have to do something to improve its performance and compatibility testing! :evil:

Thank you for your kind reply.

Whenever I receive a call, it is automatically transferred to my SE BTH-60 headset, so I am using it handsfree mode actually. I can accept/reject the call thru the headset.

palmop said:
Whenever I receive a call, it is automatically transferred to my SE BTH-60 headset, so I am using it handsfree mode actually. I can accept/reject the call thru the headset.
Click to expand...
Click to collapse
Handsfree profile lets you use the automatic feature, which automaticaly accepts and answers (after a you specify the number of rings) the call without pressing any button on the bt headset.
Also, the handsfree profile lets you use the voice dial feature by activating it from the bt headset and without touching the mobile phone. and other features...
Does, anyone have any expirence with new nokia clip-on bt headset and the xda2.
Thanks

[email protected] said:
TOWA's great app only fixes the serial port issue, by basically establishing a permanent virtual com-port using the functionality built into the Microsoft BT-stack.
Unfortunately, inmplementing a Handsfree profile will be much more complex, so don't expect a quick fix on that. I'm sure HTC and Microsoft are working on it, but I wouldn't expect a fix this year.
Regarding your BT-observations, it seems that the implementation of the profiles on each device is different and probably none of them are really complete.
I think the Bluetooth Org will have to do something to improve its performance and compatibility testing! :evil:
Click to expand...
Click to collapse
Thank you again for your kind reply.
Sirs, I believe the time has come for me to beg the great one "TOWA" to write us a new doohicky, to make the xda 2 work in handsfree profile with handsfree bt headsets and others.
So, Towa, if your reading, have you ever had someone to beg you for something in writing?? :lol:
Must be nice bieng the man!!

Upgrade Pocket Bluetooth Tools 1.0.1.2

The current version 1.60 of the ROM includes already a virtual serial port but unfortunately it is a dynamic port, which is not visible to many applications. Also the ActiveSync support is difficult and complicated to use and if you want to synchronize with different computers you have always to couple the device again.
For future releases I plan the following improvements:
Support for Bluetooth headsets
Support for Bluetooth network access points
Send contacts and files through Bluetooth
http://www.angeltowns.com/town/bluetooth/

i am looking also for handsfree bluetooth support if any help on that

Yeah, headset works fine, it's the handsfree profile we need, that's the one adding enhanced features....

Do you know why some headsets work better than others? I understand that the profile does not work and therefore you can not use the functions on the headsets, but I'm curious if your recent fix will help headsets such as the Jabra BT250 communicate better with the device. The HBH-65 has no issues, but Jabra does note, often very slow to connect. I like the Jabra because I can hear better-age you know.

gratefuled said:
Do you know why some headsets work better than others?
Click to expand...
Click to collapse
Maybe because of the headsets itself ? I bought a HBH-35 and can do [/quote]anything with it, walk out of range and back, turn it off and on, reset the MDA, chanrge the headset etc etc. without having to re-pair...
I understand that the profile does not work and therefore you can not use the functions on the headsets, but I'm curious if your recent fix will help headsets such as the Jabra BT250 communicate better with the device. The HBH-65 has no issues, but Jabra does note, often very slow to connect. I like the Jabra because I can hear better-age you know.
Click to expand...
Click to collapse
What headset-functions do you mean ? Caller ID ? Voicedial etc. ?
That's not in the headsetprofile, that's in the handsfree profile. the headsets with enhanced functions use the handsfreeprofile also, nut just the headsetprofile...

downloaded and installed 1.0.1.2 fantastic my new bt gps works! However I can not use my gps and hbh-65 headset at the same time, any ideas please

Simply stated I was wondering if the new blutooth fix might help the Jabra BT250 work better. I know other headsets work without issue, but Jabra seems to have some problems, and I doubt that this is a Jabra problem, I believe it is a BT Device profile issue.

Can I have another link to the software cause the link is blocked from my ISP, or can any body upload it here or any other palce...
Best regards,,,

I have a new HBH-200, it works ok to answer a call but all the other features are not working, such as caller number etc.

Like i said; It's not i the headsetprofile. The headsetprofile doesn't do much except making a wireless headset possible. Answer, dosconnect and talk and listen, that's all...
Everyting else is in the handsfreeprofile (handsfree is used for advanced options for headsets and carkits)...

Link down????? :?:

not for me

Handfree Profile
I have 2 phones, XDA II and a Nokia 8910i.
My bluetooth Headset is the Ericsson HBH65.
To my surprise, I have paired the HBH65 with both phones and I am able to receive calls from both phones (not at the same time of course) without any problems. Whichever phone rings first get the use of the HBH65. In conflicts however, the Nokia seems to have priority over the XDAII, which is fine with me, but I am so happy that it actually works.
As others are mentioning, I am really missing the enhanced functions of the Handsfree Profile. Can anyone suggest any solution or perhaps work on resolving this issue as a lot of people are waiting for this. I was aware that Towas was planning to release a new version to his BT Stack Fix, has he got anywhere with that by any chance? or anyone else?

* It's possible * - Using BT Headset for Voicedialing etc...

Ok. Got your attention didn't I?
Well, I thought that the limitation of using a headset bluetooth
for things other than just during a conversation was actually
a limitation of the Pocket PC WM2003SE OS. And not just a
specific issue with the PDA2K. Well I guess I was WRONG.
I have the Logitech BT freedom headset (2nd generation ver).
I just ran accross this article :
http://www.pdabuyersguide.com/tips/logitech_mobile_freedom.htm
The writer who knows what he's talking about writes in his
review that the Logitech BT headset worked great with
MS Voice Command! (He didn't talk about any special tweakings
that he had to make for that!). At first, I thought it may just be a mistake,
then in the same review, he writes about the quality of hearing MP3 was
acceptable with the Logitech BT headset on his Ipaq 6315 !
Makes me /\/\ad to think about the fact that my Logitech BT headset
doesn't work for anything other than during the conversation,
yet Ipaq 6315 users are enjoying it for voice dialing as well..GGrr... :x

Has anybody tried it practically on an XDA2?
Is it possible to hear sound other that a phone conversation?

isn't it possible to extract the rom of an ipaq & install it in an xda II ? or at least the BT stack, someone can tell us any info about that

Voice Command Over Bluetooth

Voice Command 1.6 seems to be a bit of a nightmare and i have given up on my hermes for now.
My trinity though is almost ok, the only thing that doesnt work is when i push the voice button on the headset the sound comes out the phone speaker.
If i use the button on the phone though the sound comes out the headset.
How can i change the action of the button on the bluetooth headset to do what the button on the device is doing.
Thanks all.
Rob.

rjefferis said:
If i use the button on the phone though the sound comes out the headset.
How can i change the action of the button on the bluetooth headset to do what the button on the device is doing.
Click to expand...
Click to collapse
FYI I use a SonyEricsson stereo BT headset and I don't experience this problem.

Rjefferis, I experience the same problem as you.
I have a Jabra JX10 headset.
Confirmation voice always comes out of phone speaker, not headphone... and irritatingly, it takes microphone readings from the phone body too. Kind of defeating the idea of hands free voice dialling.

FuzzMunky said:
Rjefferis, I experience the same problem as you.
I have a Jabra JX10 headset.
Confirmation voice always comes out of phone speaker, not headphone... and irritatingly, it takes microphone readings from the phone body too. Kind of defeating the idea of hands free voice dialling.
Click to expand...
Click to collapse
Yeah this seems to be the problem on the hermes too. On mine it works correctly if i use the voice dial button on the phone. So the button on the headset and the button on the phone must be calling slightly different functions. All i need to know is what reg key i have to edit to make the headset button do the same as the phone one.
Try yours to see whether it works using the phone button. I think maybe my a2dp is getting involved somewhere as well.

There is an option about Notifications and Bluetooth devices in the Voice command settings... does this solve you problem?

Not for me.
It is set to read only through handsfree. I havent got my headset here, so I will see what happens if I switch it to the opposite like rjefferis implied.

yeah i doesnt make a difference using the options in voice command.
I think maybe when i push the button on the phone it works through the a2dp to the headset which obviously it shouldnt be.
When i use a non stereo headset then i think it always comes out the phone no matter what.

There are a number of threads regarding this issue and some semi-working fixes to get initiating a voice call through a mono bluetooth headset.
The problem seems to be a difference in the trinity passing audio through the audio gateway using a mono bluetooth headset. Not sure if this is a problem with the implentation of Microsoft's bluetooth stack on the TyTn/Trinity but I'm assuming that's the case.
According to Microsoft's Voice Command site, they indicate that the TyTn (put the Trinity in the same situation) passes audio through the device speaker. They also make note that devices running Windows Mobile build prior to 15097.3.0.0 will pass announcements through the device speaker. This leads me to believe that Microsoft fixed audio to a mono bluetooth headset but I've seen lot's of messages from people running roms higher than this version who still have the problem so sounds like HTC hasn't implemented it.
I've sent emails to HTC who indicate that it's a 3rd party program and there is no guarentee they will fix it as it's a Microsoft problem. I haven't been able to get word from Microsoft if it is being fixed but from their website, seems both parties are passing the buck on this one.
Considering HTC's lack of commitment in releasing updates for their branded products and the delay, we probably won't see another rom after their first release for a while if any since they seem more committed to releasing new products increase their bottom line without keeping their current customers happy. So if it's not in their upcoming rom update and Microsoft isn't releasing a fix, we could be waiting a while. I'd recommend anyone who cares about this issue to send an email to HTC Support. You'll get the generic response but hopefully if enough people complain about it, a fix might fall into their update

Bluetooth headset with voip

Hi.
Is there a way to use my bluetooth headset with voip program (I'm using Nimbuzz right now) on my Htc HD ?
Thanks.

This is exactly my BIG problem at the moment too. Like you I want to run a VOIP softphone, but it's useless without a headset.
Microsoft (in their infinite wisdom) decided that ONLY the phone app would be able to use mono Bluetooth headsets, although anything will use A2DP stereo BT.
There are 2 solutions I have successfully used elsewhere:-
Teksoft's BlueMusic
David May's BTAudio
BUT, the former can only work with Microsoft's BT stack (which I don't believe the Touch HD or HD2 does and the latter speeds up the audio one way so you sound like you're breathing Helium. So neither is a solution for my HD.
I do find it simply extraordinary that any developer (even those idiots in Redmond) could make such a stupid decision to NOT allow any other app to use a mono BT headset. The big issues for me are Sat Nav and now VOIP softphones, both of which require the ability to be able to do this. How come after so many years producing Windows Mobile, Microsoft still haven't grasped such basic concepts. They obviously haven't got a clue, never did have and looks like they never will have.
It is possible that Teksoft will be updating their product to work with other stacks, but I'm still waiting for a response about the BTAudio problem.
Is android crippled like this?
Roll on a stable release of Android for the HD (or HD2).