Listen to your Pocket PC on your traditional mono Bluetooth headset and/or use its built-in microphone for PDA-based recording!
(I’ve been constantly receiving questions about all these questions on various Pocket PC boards and newsgroups; now that I’m tired of answering the same question at least five times a day, I’ve decided to dedicate a complete write-up to it.)
I’ve published several articles on A2DP and AVRCP (please see the Bluetooth category in the Smartphone & Pocket PC Magazine Expert Blog), which is a great way to listen to music wirelessly in (almost) Hi-Fi quality and stereo.
The “traditional” headset mode, on the other hand, may be much more useful for much more Pocket PC users because
There are much more cheap, “traditional”, mono Bluetooth headsets than expensive and bulky A2DP stereo headphones. They are available in all phone shops everywhere and are used by, it seems, everywhere. An example of them is the X3 micro, of which Jack Cook has just published an excellent review
To listen to, say, GPS navigation, the (not very good, phone-grade) quality of these headsets may be sufficient
Furthermore, they offer two serious (!) advantages over the A2DP mode, because of which you may want to go for the traditional headset mode instead of the high-quality A2DP mode even if you have a full-blown A2DP stereo headphone:
when you actively connect a headset device to your PDA, you will not only use the PDA-to-headset sound routing, but also the opposite direction. That is, if you, for example, want to use your PDA to record your speech (and that of your environment), and the slightly degraded (recording) sound recording quality (which won’t really be an issue when you only plan to record speech) isn’t an issue, you may want to opt for using your headset to record your speech as opposed to your PDA, which, then, can even be in your pocket or even in your suitcase.
the CPU usage of the “plain” PDA-to- headset unit will be about an order of magnitude less than that of A2DP. For example, on the non-overclocked HTC Wizard, device.exe consumes between 28 and 35% with A2DP, depending on the quality. With simple non-Hi-Fi / non-stereo sound routing, device.exe doesn’t consume anything at all, compared to the default (sound isn’t routed) case. That is, when battery life and / or responsiveness is of paramount importance and the heavy sound quality degradation / lack of stereo, you may want to prefer the low-quality, mono but non-battery-consuming headset mode to high-quality, but heavily battery-consuming mode, which also makes your Pocket PC much less responsive.
Being able to constantly (!) route the sound of your PDA to your mono headset, first, depends on the maker of your built-in Bluetooth stack. In here, Widcomm / Broadcom users (Widcomm is used in most PDA’s with operating systems prior to WM5 except for the Phone Edition models of HTC; as far as WM5 models are concerned, all Acers, HP iPAQs have sticked with this stack; the majority of Fujitsu-Siemens Pocket PC’s (except for the T8x0) and all Dell Axims (which were all Widcomm-based in the pre-WM5 times) have switched to the Microsoft BT stack), as usual, have a lead because they don’t need additional hacks / third-party applications, as opposed to the Microsoft stack.
Widcomm / Broadcom BT stack
The newer Widcomm / Broadcom BT stack versions (starting with BT stack 1.5 built into most Widcomm-based WM2003SE devices; this is also true with 1.6 and the latest 1.7, which is used in current Widcomm-based WM5 Pocket PC’s) all natively support routing the sound to your mono headset (and, of course, vice versa) as can be seen in this and this screenshots. That is, in these devices, just go to Bluetooth Manager / New, switch the headset to discoverable mode and select Hands-free / Headset setup. After creating a shortcut to the connection, just double-click it to connect (or, press the button on your headset / switch it on; then, they may automatically connect. Note that, with some headsets (for example, the Plantronics Pulsar 590A and the Dell Axim x51v with the Widcomm BT hack, the "hacked" (see below) HP iPAQ 2210 or the WM5-upgraded iPAQ hx4700), after connection, you'll need to press the headset button once more, when you hear a ringing sound. It's only then that the sound routing will be started.)
Older Widcomm versions (up to 1.4 built into most pre-WM2003SE Pocket PC’s; for example, the HP iPAQ 2210), however, don’t offer Hands-free / Headset setup in the Bluetooth Manager, in the New / Connect! list as can be seen in the following screenshots: 1 2. There, all you will need to do is
changing HKEY_LOCAL_MACHINE\SOFTWARE\ Widcomm\BtConfig\ Services\0005\ Enabled from 0 to 1 in the Registry as can also be seen in here. After this, a new item, Connect a headset, will be added to the above New / Connect! list as can be seen in here.
changing HKEY_LOCAL_MACHINE\ Drivers\ BuiltIn\ WaveDev\ Dll to btceif.dll. Make sure you export (or, at least, remember) the original name of this if it's different from wavedev.dll - you'll need it when you want to switch back to the built-in speaker.
Note that this tutorial also elaborates on these two steps (it, however, adds no relevant information so you don't have to read it) and I've also uploaded two registry import files to make the switch much easier. Here's the registry import file to enable sound routing and here's the one to disable it. Also note that you must reset your device after applying the registry changes as, unlike the BT stack-only hacks, which "only" make it necessary to restart the BT stack itself, the second, HKEY_LOCAL_MACHINE\ Drivers\ BuiltIn\ WaveDev\ Dll hack, will only be used after a reset because it's a system-wide hack.
After this hack, you can go on as usual: after selecting Connect a headset, the device will find the headset, you just enter the PIN (0000 or, in very few cases, 1234) and, by clicking Finish here, let the system create the shortcut for you.
Note that, despite being able to connect to the headset now, these "hacked" pre-WM2003SE devices are not guaranteed to flawlessly work with the headsets. For example, some HP WM2003 Pocket PC models are known not to be able to use them at all; for example, the HP iPAQ 4150. Unfortunately, in these cases, installing the well-known HP 1.6 BT update (see my A2DP articles on what it is) doesn’t help either: as opposed to the registry hack (which doesn’t help with this BT stack version any more) it won’t list “Connect to headset” (or, as it's called in never, 1.5+ Widcomm versions, Hands-free / Headset setup) any more in New (1 2 3) and, when you directly discover the services of a headset and select the (only) “Headset” profile they offer, connection attempts will always fail.
Microsoft BT stack
The situation is in no way so easy as with the Widcomm BT stack as it’s only with phone calls (if the device contains a phone at all) that it will actively use the headset, nothing else (for example, music, GPS instructions etc).
Therefore, you’ll need to use third-party applications to re-route the sound.
There are several solutions to this problem:
BTAudio 810 (also see this and this thread). Works great on the Wizard (with the 2.26 Molski ROM) but not on the Axim x51v (none of the audio re-routing solutions worked on it; therefore, you may end up having to install the Widcomm BT stack on it, which also offers flawless sound redirection to mono, non-A2DP headsets).
Installation: The ZIP file contains three files; just copy them anywhere on your Pocket PC (simply BTAudioToggle.exe may be enough) and, when you want to toggle the sound target, just execute BTAudioToggle.exe (or, alternatively, when you want to start/stop the sound routing, execute BTAudioOn.exe/BTAudioOff.exe, respectively.)
TP.com Btaudio (also see this) didn’t offer anything of importance in the case of the x51v either: with my AKU2.3 A12 ROM, the PDA still wouldn’t discover the Hands-free profile of my headset (only the wireless stereo, but it, in our case, has no use at all). It didn't work on my Wizard either. You may have better luck though; also make sure you read the linked thread (and also look around for other, related threads at XDA-Developers.)
Installation: The downloadable ZIP file contains a CAB file; just install it on your PDA.
Bluetooth sound: (also see this): while it’s reported to work great on the HTC TyTN (Hermes), it has no effect on the Dell Axim x51v / HTC Wizard at all (and is also reported not to work on the HTC Universal either). After installing it, BTAudio 810 stopped working; fortunately, the uninstall worked OK and, then, BTAudio 810 started to work again.
Installation: The downloadable ZIP file contains a CAB file; just install it on your PDA.
Teksoft's BlueMusic: (also see this): you may want to give this title a try too. It doesn’t work on my HTC Wizard (only if you previously enable sound re-routing with BTAudio 810; then, it’ll be able to switch it off and on but this functionality can also be used with the “original” BTAudio 810 and, therefore, there is not much point in installing (and, for that matter, paying for) BlueMusic in addition to the free and smaller BTAudio 810) and Axim x51v, but others have reported success with other models.
Installation: Install the software following the tutorial in install.en.txt in the downloadable ZIP file.
BTAudioNav by infamous PPC hacker, co-author of the Dell Axim x50/x51 Widcomm BT stack hack beemer: this hack allows for redirecting the sound of a particular (for example, GPS) application only. It also makes sure it reconnects to the headset after a phone call, unlike (some of?) the alternatives. It's available here; if you don't want to register yourself in the forum to be able to download the file, you can also get it from here (I've mirrored it there). Please see either the above (Spanish) thread or beemer's comments here for more information on the usage.
Verdict
If you have the Microsoft BT stack, check out BTAudio 810 first - or beemer's BTAudioNav. It’s the smallest and cleanest, free solution, which seems to be working just great. If you have the Widcomm BT stack, just use the built-in headset redirection capabilities (with the necessary hacking with earlier BT stacks if needed).
UPDATE (11/05/2006): discussions of this article: HowardForums.
Tutorial updated
Cingular 8525 BT Audio
Thank you for your help here. However, not matter what I've tried, I can't seem to get the audio to stream from my Cingular 8525 to my Plantronics 510 headset.
If anyone has specific advice on the 8525, please let me know.
Thank you.
HogFarmer said:
Thank you for your help here. However, not matter what I've tried, I can't seem to get the audio to stream from my Cingular 8525 to my Plantronics 510 headset.
If anyone has specific advice on the 8525, please let me know.
Thank you.
Click to expand...
Click to collapse
Strange. Have you checked out http://forum.xda-developers.com/showthread.php?t=278778 ?
Yes. I tried that. Just to be sure...
1. I uninstalled everything I tried previously.
2. Soft Reset
3. Installed the .cab at http://forum.xda-developers.com/showthread.php?t=278778
4. Soft Rest
5. Turned on BT
6. Turned on my BT Headset
7. Music in WMP and TCPMP still plays through the speaker, not my headset
Any help is appreciated.
My mistake.
I missed the part about initiating the Voice Command function from my headset. Sure enough, that did the trick!
Thanks for your help!!!!
Please help me!!!!
I cant get my blackjack to stream the music to my BT headset, I have a WEP170 Samsung headset and i cant hear the music through the headset. please help me out with this situation. the phone says that it is bluetooth mode but there is no sound in the headset.
Please Help???????
Results of BTAudio 810 on Blackjack
Prior to using BTAudio 810 on my Blackjack, I found that I could listen to WMP using a wired headset (though the volume was very low), but it would not send WMP audio to my Jabra BT350. Regular phone operation with the Jabra worked fine.
When I tried the BTAudio 810, I could hear a slight hiss in my Jabra, as if something was happening, but alas no WMP audio was coming through. Notably, WMP audio was no longer coming through the device speaker. I switched to the Notes app and recorded a note through the Jabra - that worked.
I looked around for reasons why BTAudio wouldn't work on the Blackjack, and didn't find much. There was a xda dev thread that hypothesized that Samsung had done something with the audio gateway portion of the MS BT stack.
I'm still hoping for a solution to get audio to my Jabra.
what works???
There has to be someone out there who has found something that works. i am getting desperate. i have tried every program out there and nothing works. i have the same problem. i here a hiss but nothing works. is there a hack that can rewrite the BT stack or something!!!!
newbienew said:
is there a hack that can rewrite the BT stack or something!!!!
Click to expand...
Click to collapse
You may want to check out the Wizard / TyTN Widcomm stack threads.
UPDATE (12/26/2006): Should you have audio reconnection problems, check out THIS.
Music on my Cingular 8525 using plantronics mono bt!!
Thank You!! I had about given up all hope when I transferred your cab over to my device, ran it, did a soft reset, and then pushed my voice command button after reboot. I then started my wmp and voila! Works perfectly. You are the best!!!
mshilot said:
Thank You!! I had about given up all hope when I transferred your cab over to my device, ran it, did a soft reset, and then pushed my voice command button after reboot. I then started my wmp and voila! Works perfectly. You are the best!!!
Click to expand...
Click to collapse
You're welcome and welcome to XDA-Dev
Blackjack Mono Bluetooth
Still nothing related to piping the audio through a standard Bluetooth headset on the Samsung i607 Blackjack? I'm simply shocked that the stack is implemented in such a proprietary way. I just can't seen using a full Stereo Bluetooth Headset at work or anywhere else for that matter. If anyone has any info on whether or not Samsung is planning to fix this issue (and when), please post... I'm definitely willing to wait for a fix, or even a Bluetooth earbud that supports A2DP. Thanks!
Anything that works on Trinity?
Treo 700w?
Anyone manage to accomplish this on the treo 700w/wx yet?
BT AudioNav
For the record, I used BTAudioNav for a couple of days, using it to invoke TomTom v6. The audio connection worked flawlessly, but it seemed to cause TomTom to lag badly. It consistently gave instructions 200-800 metres later than it should (distance was speed dependent). I was warned of a radar camera after I had passed it ... not fun eh?
I dropped it and went on with my search for the ideal. Just installed the Mortscript solution provided several posts higher so we'll see how things work when I drive home tonight
<update>Didn't work. TomTom failed to come through the headset. Perhaps I was doing something wrong so I'll re-read everything tonite.</update>
<ashamed>Me again ... Ignore the last load of rubbish </ashamed>
I installed to non-default places so its no wonder I naffed up! The Mortscript/Vijay solution is giving me sound, and resets itself after I've switched to voice command with the phone button, and after I've received a phonecall. Tom Tom will have to wait 'till I go home this p.m. but right now I have to say ... YAAAHOOOOOO !!
Bluetooth Sound on Dopod D810
Bluetooth sound works for me on my Dopod D810. Thanks for the info and file link!
hi,
i have an artemis, and bt audio works great to route the sound to my headset, but i want to route the mic of the headset to the phone ...
(to use with voip software, sjphone, skype)
but i don't find a solution to route mic to the pda ans not use the internal mic ...
Thank you very much
Hi there,
I don't know where to ask this, so it went to "General".
I've got a JasJar running WM6 and it happily runs stereo music on my Motorola HT820 bluetooth headset. I also have Sony BT2500 car stereo system which supports bluetooth phone as well as A2DP. with my HT820, I just turn the headset on and jasjar sees the headset and connects to it, but with the BT2500 only the phone part is automatically connected. if I want to listen to music I have to (on my jasjar) go to settings/connections/bluetooth and tap and hold on my xplod (my sony BT2500) and set it as wireless stereo.
is there any way to avoid this step (as I'm usually driving when i have to do this)? if not, is there an easy way to do it with one hand and no tap and hold ?
Cheers,
Shafa
Hey Shafa,
I've got the same problem with my Prophet and a Pioneer BTB200. So far i found no solution, so i most likely will have to write a program to connect to a BTdevice as wireless stereo, if it autoconnects as a handsfree device and is a2dp capable.
hey Lemmz,
I'm very interested to know what API you have to call to do this...
Cheers,
Shafa
HTC Faraday
Hello all,
Are there any resources here for the Cingular 2125 , I would like to port linux on the 2125. sorry if i have mis-posted.
thanks,
rvb
@shafa:
there is a Bt_api.h in the wm5 SDK which defines a function called RequestBluetoothNotifications; so far i found
RequestBluetoothNotifications
Handling Events from the Bluetooth Stack
Retrieving AVDTP Connection State
My idea would be to monitor all bluetooth connection events (most likely via a service), see which device (auto)connects and if it is a handsfree-device and supports wireless-stereo, initiate pairing for the latter.
i will try to do some coding later today. i'll keep you informed.
Cheers,
lemmz
Ok, so far i can recieve bt-related events. unfortunately i've found no info on how to initiate an a2dp connection microsoft-style. There's tons of code for AudioGateway stuff, but imho thats pretty useless.
Looking at the registry i found in HKLM\Software\Microsoft\Bluetooth\Services\0000110B-(...) reference to "Wireless Stereo" and bthutil.dll. looking at the WM6 SDK, bthutil.h, there are just two functions, BthGetMode and BthSetMode, for turning BT on and off.
I'm also looking at the sources for the (settings->connections->bluetooth)-Dialog, btenum.cxx and btmgmtui.cpp, maybe there is some info on this.
Edit:
btw, this 0000110B thing is referred to as AudioSinkServiceClass_UUID. But no luck on that either.
Soo, i think i'm quite close now...
DRVM_MAPPER_PREFERRED_SET -- with waveOutMessage you can switch soundoutput to different devices, unfortunately for a2dp it returns NOTSUPPORTED.
But within the a2dp driver i found some messages:
WODM_BT_SCO_AUDIO_CONTROL, WODM_OPEN_CLOSE_A2DP, WODM_PARAM_OPEN_A2DP
they seem to initiate a connection and set the preferred output device, just like the DRVM_MAPPER_PREFERRED_SET should. Tonight i'll experiment with it.
SUCCESS!!
It worked just as i though: a single command does all the work.
waveOutMessage((HWAVEOUT)devId, WODM_OPEN_CLOSE_A2DP, WODM_PARAM_OPEN_A2DP, NULL)
The device to connect to has to be paired and, of course, in range. I'm now going to clean up the code and build a litte configuration-tool.
Freeware tool
EDIT: Version 1.0.rc-2 uploaded . Find the download link below:
http://teksoftco.com/index.php?section=freeware
I've just uploaded version 1.0.rc-1 of the A2DP plugin. It can be downloaded and used as freeware (0 cost) from http://teksoftco.com/index.php?section=freeware , or find it below attached to this message, including a short usage guide.
New in this release (as many users requested):
-signal indicator
-3 modes for headset: OK, Off, Err
-settings panel added
-Handle Bluetooth option
-Execute File after start option
-applet added in start->settings->system to start settings
-a2dp.exe included in the package, that with parameters: a2dp.exe -bluetoothn|off -a2dpn|off or a2dp.exe -bluetooth:1|0 -a2dp:1|0
------------------
Actually devices that support A2DP (most wm6.0 bluetooth devices), come with 2 audio drivers installed:
1) The "Audio Output" Driver (supported since ppc 2002)
2) The "Bluetooth Advanced Audio Output" Driver, that is responsible of sending audio data over a L2CAP Bluetooth connection, as per A2DP protocol
When the user connects a Stereo A2DP headset, and selects the "Wireless Stereo" profile, the Bluetooth Adv. Audio Output becomes the nr. 1 audio output route, and is indexed as the First audio driver. Any application will output sound by using that driver.
The problem is that sometimes we are already listening to audio in the device's speaker's, and then suddenly we want to switch the output to our a2dp headsets - this is sometimes problematic, as the First audio driver changes from "Audio Output" to "Bluetooth Adv. Audio Output" and the applications currently playing audio need to be restarted.
For such issues, I have provided a tool, as freeware, that will install as a today plugin and provide the user with the possibility of instantly switching the audio between Device Speaker and A2DP Stereo Headset.
It is designed for WM6.0, Microsoft Bluetooth stack, please download it and let me know how it works for you. There are some more modifications that will be done, so this is only Beta-1
The CAB installer and instructions are in the ZIP attached.
(tested on ultimate 8150/wm6.0 and eten m600+/wm5.0, the gfx was made for vga but works on qvga too)
Hello Radhoo,
first times thank you, after such a thing I searched for a long time in vain.
tool functions on the Artemis with WM6 perfectly.
If the Tool were still developed further, I would be pleased genuinly, and would like to call hereby gladly my desires:
1. Bluetooth automatically switch on and off
2. Komandozeilensteuerung
3. Traybuttons without Todayplugin
4. Automatic start of a desired program after activation of A2DP (Mortplayer)
thanks Menkul
Hello menkul, Thanks for the feedback.
What is Komandozeilensteuerung?
Sorry Komandozeilensteuerung ist german.
I mean a Funktion a2pd.exe blueon A2DPon
a2dp.exe blueoff
or so.
Also a exe with startparameter
Menkul
Great idea
Any way to indicate bluetooth 1.2 or 2.0 status/line speed, signal strength, bandwidth?
bjrmd said:
Great idea
Any way to indicate bluetooth 1.2 or 2.0 status/line speed, signal strength, bandwidth?
Click to expand...
Click to collapse
Will try to
I have two spare days for research (wow!) so I'll try to come up with something.
lemmz
lemmz said:
SUCCESS!!
It worked just as i though: a single command does all the work.
waveOutMessage((HWAVEOUT)devId, WODM_OPEN_CLOSE_A2DP, WODM_PARAM_OPEN_A2DP, NULL)
The device to connect to has to be paired and, of course, in range. I'm now going to clean up the code and build a litte configuration-tool.
Click to expand...
Click to collapse
I am sorry I've "invaded" this thread, without first saying thanks to lemmz for his work, as I very well understand the effort needed to perform this kind of research.
While I wasn't aware of his findings (which are available in AK :
bt_ddi.h, WM520\PUBLIC\COMMON\OAK\INC\ ) I just wanted to give another free tool to the community, so I posted this in a few threads where users where requesting A2DP tools. I hope this is ok.
Dear Lemmz,
thanks a lot, i will take a look asap.
thanks again
Shafa
Hey Lemmz,
where do you get the devId from?
I'm thinking about writing the application, but I'm not a C++ guy (anymore atleast) I need to write it in C#...
Cheers,
Shafa
me again. should i use WAVE_MAPPER for device ID? if so, what is the value for it or even better, where can i find the whatever.h that has the value? is there an SDK i should download?
Cheers,
Shafa
menkul said:
Sorry Komandozeilensteuerung ist german.
I mean a Funktion a2pd.exe blueon A2DPon
a2dp.exe blueoff
or so.
Also a exe with startparameter
Menkul
Click to expand...
Click to collapse
Done, original post updated, download 1.0.rc-1
Signal indicator also added: it shows the bluetooth connection strength!
shafa said:
me again. should i use WAVE_MAPPER for device ID? if so, what is the value for it or even better, where can i find the whatever.h that has the value? is there an SDK i should download?
Cheers,
Shafa
Click to expand...
Click to collapse
You should use waveOutGetNumDevs() to get the number of wave devices.
Then you can use their index directly: 0 , 1 , eg.:
int idWAVE_BTAudio = 0; // or 1
waveOutMessage((HWAVEOUT)idWAVE_BTAudio ...
Where:
Code:
0. Audio Output
1. Bluetooth Advanced Audio Output
Be careful, the index changes when one device is selected, so you should check the WAVE devices each time you want to switch the audio.
Personally I've used waveOutGetNumDevs() then waveOutGetDevCaps to see what kind of device is each of the enumerated ones.
Hope this helps.
Can someone please explain why a paired BT microphone will not simply replace the internal microphone on an android device in the same way as it does for a wired headset ?
I have found that BT mics only work during a phone call, or when trying to initiate a call via a voice dialer app. Audio input for any other app is routed via the built in mic, but sound output is always routed to the paired BT speaker or earphone.
This problem seems to affect most android devices and BT headsets. It has been written about in many forums, including the google/android forum, but the reason has never been explained. Within XDA the question has been raised a number of times, but even the smart guys on this forum seem to be stumped, or are part of a general conspiracy not to answer this question .
If I am a complete idiot and have missed some basic point don't spare my feelings, but please answer the question !
Please understand the whole Bluetooth A2DP Protocol has been designed around voice communication. Conceptually the kernel allows for acceptance of inputs from any valid compatible hardware resources at its disposal. This is why you'd see Voice dialer apps being able to effectively utilize bluetooth. However, this usage of external BT devices that are not always connected to phone, requires extensive programming on part of the Application to establish a listener and check for a BT device each time. App developers potentially will have to do a balance study between benefits and amount of time, and effort involved. This does include testing for myriad variety of Bluetooth devices and phones.
You may wish to post in
Hardware Hacking > Hardware Hacking General
so that the right experts may chime in.
Perseus71 said:
Please understand the whole Bluetooth A2DP Protocol has been designed around voice communication. Conceptually the kernel allows for acceptance of inputs from any valid compatible hardware resources at its disposal. This is why you'd see Voice dialer apps being able to effectively utilize bluetooth. However, this usage of external BT devices that are not always connected to phone, requires extensive programming on part of the Application to establish a listener and check for a BT device each time. App developers potentially will have to do a balance study between benefits and amount of time, and effort involved. This does include testing for myriad variety of Bluetooth devices and phones.
You may wish to post in
Hardware Hacking > Hardware Hacking General
so that the right experts may chime in.
Click to expand...
Click to collapse
Thanks for the reply Perseus71 and I have also reposted on the link you suggested, but I have not fully understood your meaning.
The fact that my BT mics work OK when in call proves hardware and software functionality. Why can't this working code be invoked when I am using another app which requires mic input?
Does the Android kernel somehow earmark BT audio "for telephony only" and deny other apps access to the audio stream.
Why would it matter to the Android OS if BT sourced audio data is being sent a file as opposed to the telephone network?
Thread Closed. Thank you.