After using a K600i from Sony Ericsson, I found a really cool feature!
The K600i supports Bluetooth HID service.
You can use it as a remote for your computer, driverless under XP..
Would it be possible to create such a function in our Universal?
The hardware should surely support it, but I guess we'd have to mod the BT stack?
Related
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!!
Hello can anyone who owns a JasJar answer this question:
Do you have a WidComm/BroadComm Bluetooth Stack or a Microsoft Based one?
:roll:
eman said:
Hello can anyone who owns a JasJar answer this question:
Do you have a WidComm/BroadComm Bluetooth Stack or a Microsoft Based one?
:roll:
Click to expand...
Click to collapse
MS...
sadly its MS ..not widcomm as many of the websites have LIED
And it's supports headset or/and handfree profiles?
And no AD2P?
:shock: AAARRRGGGG :shock:
oh well... A2DP is a protocol, it can be implemented from a 3rd Party Media Player for all I know. The problem is no Media Player has implemented this protocol yet within their system.
Just like Resco utilizing its own protocol to send a file over bluetooth, a 3rd Party media player can be used to play media over A2DP audio receivers. Problem is... Where? If anyone knows of a program that does this please let us know... This should be a good feature in the existing media player applications.
Btw, one very good thing I taught about having MS Stack is the ability to use MobiLuck (www.mobiluck.com), unfortunately it seems that it still gives errors since the MS Stack used is probably different from the developer's one.
Has anyone with WM5 managed to use MobiLuck for BlueJacking... else what program should we use for that?
Hmmm. I thought that in Windows Mobile 5, the new MS stack was supposed to be more Widcomm-like - including support for A2DP? Maybe someone who has one right now can confirm?
If not, then I don't know how MS can keep avoiding support for A2DP. Well, actually I do know how they can, but it would be stupid for them to do
I tested it, WM5, and I also have a Stereo Headset, it does recognize Headset and HandsFree from the Anycom Stereo Headset, but I find no way to connect to it.
The bluetooth stack is nothing like WidComm, its exactly like Microsoft with a few more features.
unfortunately I only have a Blue Angel not a Universal, thats why I was hoping the Universal had a different bluetooth stack.
I wonder if XDA Exec will have MS stack too
I wonder if XDA Exec will have MS stack too
I hope one of the gurus here can help me with this one:
- I have the O2 Exec, with MS BT stack
- I have the Logitech MX 5000 BT Laser Desktop (http://www.logitech.com/index.cfm/products/details/CA/EN,CRID=2158,CONTENTID=10776)
- this comes with a choice of the Widcomm stack(which they recommend), or you can use the MS BT stack
I have set up BT Activesync using the MS BT stack, without a hitch, but would like the extra goodies that the Widcomm stack offers.
What I want to know is:
- can I use the Logitech Widcomm stack (which requires that I disable the MS BT stack on my pc) and still set up Activesync with my Exec?
- Or, because the Exec uses MS BT, must I set up all peripherals to use MS BT to get them to communicate?
I have checked Logitech's support forum and done an extensive search here, but I can't find a definitive answer:
- if your HTC devices uses a particular BT stack, must you use that stack on your pc , as well?
Thanks in advance...
Huisie, you *should* be able to use any bluetooth stack on the desktop.
Just ansure that you have a incoming BT port set up, point Activesync to that incoming port, and set up a partnership.
Lekker, ou seun, dankie vir die help daarmee!
So, snorbaard, I can run the Widcomm or MS BT stack on the desktop, but I'm limited to the ...uh, limited...MS BT on the Exec.
Still, I believe that Widcomm doesn't do hands-free, is that right?
is it possible to use universal as bluetooth headset for the comp???
if yes how???
M$ stack does not support the audio gateway profile. (I think its audio gateway) Anyway, because of this you cannot use the Computer as a mic for your universal, and you cannot use the universal as a mic/speaker for the pc, or other phones. I used to use an older At&T sony erricson to talk on skype through the computer via bluetooth, so I know how useful the feature can be. Sorry.
sess could u help me out????
i get the audio gateway profile listed as supported by universal on my comp...
do u remember what happened when u connected your se with the comp..
i get a msg..waiting for call
maybe we can get it to work
I believe that what you are seeing is actually your computers bluetooth drivers supporting the headset or handsfree profile. You need it to be teh opposite direction, because as it stands, I think if you're successfully able to pair the two, you'll find that the Universals phone audio will come out of the computer speakers and input from teh mic. AFAIK its not possible to do what you want with those M$ drivers alone.
I want to know what the supported bluetooth profiles are for the XPERIA X10. As far as I know from experience there is HSP (Headset Support Profile), A2DP (Advanced Audio Distribution Profile), and AVRCP (Audio/Video Remote Control Profile). But what about PAN (Personal Area Networking for bluetooth tethering), HID (Human Interface Device for using bluetooth keyboards), or SAP and PBAP (Sim and PhoneBook Access Profile)?
I've tried pairing my X10 with my desktop with stock Microsoft bluetooth drivers and my Sony VAIO laptop with Toshiba bluetooth drivers and neither shows anything! Is this a limitation of the phones hardware or android 1.6 software?