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
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!!
Anyone can help on this please:
Any way to listen MP3 by bluetooth handfree using mini??
Many many many thanks
Not at the moment.
The M$ stack does not support the audio gateway profile.
In fact the consensus is that the M$ stack is ****e.
There are other stacks that can be installed, bluesoil and Toshiba IIRC, but they are buggy and I dont know if they do the audio gateway profile.
let us pray that HTC see the light and release a better BT stack!
Thanks, let see anyone can break through this problem.......
Do you mean something like this :-
Media Player Headset with Bluetooth wireless technology
http://www.itechdynamic.com/html/products.htm
Yes, but I think they don't work on O2 mini, because of the microsoft BT stack...... hope some body can make the patch for this.
download bluetooth update patch for PPC, it pass test on o2 mini. for detail please check http://www.pocketpc.com.hk/bbs/viewthread.php?tid=18189
it is CHINESE web site from Hongkong.
They said it is not support on O2 mini.........
If I installed a BT dongle on a PC... it support all... including audio gateway.. I can listen mp3s via headset...
why O2 just can't do it the same way... :? since all are based on BT technology...
samsonlo, some message from that web site said: It can support O2 MINI.
I'm not sure, Maybe?
Thanks anyway, will have a try tonight.............
If O2 mini can be supported. please send some sugeestion here, thanks!
yes please keep us updated
The Hands free profile is not meant for audio streaming and i doubt that the wave output of the Magician is connected to this profile - it also isn't for the headset profile.
You need the A2DP profile, which is not included into the MS-Stack - and this has so much nothing to do with O2. It was HTCs decision to include the MS Stack into the Magician, not O2 or any other reseller. The Broadcom update is for their stack, not MS. Someone posted that some (commercial) developers are working on the A2DP profile for the Magician, which is not available yet, from what I know.
The Eten M500 (which uses the M$ Stack) has now been patched to allow Voice command over Bluetooth. People are trying to dump the rom so we can see how it has been done.
There is a threrad running on HoFo
http://www.howardforums.com/showthread.php?t=655524
Any one on here got an Eten?
andyhe said:
download bluetooth update patch for PPC, it pass test on o2 mini. for detail please check http://www.pocketpc.com.hk/bbs/viewthread.php?tid=18189
it is CHINESE web site from Hongkong.
Click to expand...
Click to collapse
This update is for the Widcomm stack. Not the MS stack that the JAM uses. It will NOT work on the JAM...it would be nice, but it doesn't.
Dave
Aitch said:
Do you mean something like this :-
Media Player Headset with Bluetooth wireless technology
http://www.itechdynamic.com/html/products.htm
Click to expand...
Click to collapse
Hey, that's my bluetooth headset, I-Tech Stereo Headset. It does work fine with the Magician with the headset profile. But since there is no support from MS Stack for A2DP, there is no way to listen to Media Player on it.
I do use it with my PC bluetooth dongle v1.2 (with Bluesoleil stack) with the A2DP.
Dandie said:
Someone posted that some (commercial) developers are working on the A2DP profile for the Magician, which is not available yet, from what I know.
Click to expand...
Click to collapse
That would be great news! Hope to hear news from that soon.
Cheers
Hi,
I've got a Qtek s100. Recently I bought a Thomson BT handsfree. With regards to handsfree function it works perfectly, but I would also like to use it to listen to music. Is it possible to create some kind of audio gateway to my handsfree, so that all sound played on my qtek is heard in the handsfree?
Sorry if this has already been answered, but I didn't find anything about it. Please point me in the right direction if so.
Also, I read something about a camera fix. Is there one, and where can I get it?
I have the standard ROM and MS bt stack. No upgrades. I also have MS Voice Command installed.
Best Regards,
The sound issue isn't possible.
You can find the latest camera software on the FTP. Doesn't help much though.
Impossible, why?
Why is it impossible? Because of phone version, bluetooth stack or is there just no software for it?
It is possible to send any kind of audio over the bluetooth protocol. We're already sending voice audio, so it shouldn't be that different to send music. Some Nokia phones has this implemented.
And also, wich ftp? The link points nowhere...
Best Regards,
You haven't found anything about the sound routing problem in conjunction with bluetooth? Ridiculous, really.
Can anyone help.
I have the HP Bluetooth Stereo Headset and I assume that I need to have the Widcomm/Broadcomm stack to use it.
I have used it with the Xda IIi and Xda 2S and it worked fine(with the appropriate patch)
I have since tried it unsuccessfully with both the Universal and the Wizard.
I know these devices are running Windows Mobile 5 and I guess this is the reason.
Is there any patch available to make the headset work
Thanks for any help
Hi there,
I think everyone WISHES they could give you an answer on that one...
Apparently, Windows Mobile 5 has the Microsoft BT stack instead of the excellent WIDCOMM stack... the MS stack does NOT include A2DP.
Apparently, there will be a patch for it from Microsoft by the end of the year... but who knows if that's true...
By the way, there are a LOT of topics on this... try a search next time to reduce duplicate posts... thanks !
JonBoy8841
there is a hardware difference between the HTC universal and Wizard with regards to the Bluetooth stacks they have. Apparently in the Universal it is 1.2 and doesn't support Stereo (forgot the actual mode name); whilst the Wizard is (I think)Stack 2.0 - but in any case -DOES support Bt stereo - so u should be able to enable it somehow on the K-Jam. now as to how to actually achieve that.... :roll:
Stero Headset is not functionally?
Are You sure? I've buyng Motorola HT820, AND iT WORK PERFECTLY, with phone and MP10, with and without cable, with and without Bluetooth.
Stero Headset is not functionally?
Are You sure? I've buyng Motorola HT820, AND iT WORK PERFECTLY, with phone and MP10, with and without cable, with and without Bluetooth.
Dear all,
I know that Microsoft is developing WM5 AKU2 which will include A2DP protocol; however I just can't wait for it. I saw many BT providers like Widcomm, BlueSoleil had released the A2DP stack. How can I know the BT version used on wizzard, so I can try those stacks. Many thanks in advance.
Michael
unfortunaitly those will not work on wm5, they only work on wm2003.
(have tried)
if you go into bluetooth settings you will only have three buttons at the moment, "Mode,Devices,COM Ports" you have got bt v1.2
one thing to watch out for also, is that some of the new bt headset's with a2dp with not work with voice dial, you can answer or hangup from headset, but you have to dial from the phone.
I think this is because the headset is able to be used for AVRCP (Audio Video Remote Control Profile).
(but i may be wrong)
aliendad said:
unfortunaitly those will not work on wm5, they only work on wm2003.
(have tried)
Click to expand...
Click to collapse
Thanks! I tried too. Need to hard rest to bring it back.
Does this mean that we just can't do anything but waiting for MS? That's bad.
Michael
yep or someone else to do it first