will this work on the xv6600?

I don't know, but I can tell you that it should work on any PDA that uses the Microsoft bluetooth stack and has hardware support for channeling system audio to the Bluetooth chip.

hmm. ill have to try it. i left my headset in my truck and i didnt take the truck today.

so this just channels the rest of the audio over, mp3s, videos, etc.

I tried it on the PPC-6601 with no success.
Mick

Mrailing, could you link this into the FAQ?

It may be too late, but here is a little icon like what I described earlier.



D.

That's great! Any objections to switching it?

Yes, I object. I feel it is lacking quality and artistic merit. The production of an obviously troubled and mentally challenged person.

[Please disregard this post. It as submitted by my weekend personality. He come out early this week.]

Thank you for your attention.

D.

So are 99% of the posts on these forums

Thanks for working on this.. Now i can get stereo BT headphones

I'd hold off on the Stereo part, I'm pretty sure the BT headset profile only supports mono. The good quality audio profile is A2DP and that isn't likely to be working on the i730 any time soon or ever.

We may have to wait until Windows Mobile 5 for stereo audio. At least I think WM5 supports A2DP. Also, WM5 includes Microsoft's Voice Command, solving another pet peeve for those that are not Voice Signal fans

So whats the eta on the i730 supporting this... either with wm 5 or a2dp? What is the quality for mono like?

this utility will work with VC if you rename the Voice Command executable to voice signal as discussed in SD's hack ... still can't get VC to anounce who it is calling over the audio ... but it does try ... I get bits and pieces of it when I have the audio on ... so I'm guessing this is on the right track

Fuzzy

__________________
Fuzzy
Kyo 6035, Sam I300, Sam I330, Kyo 7315, Treo 600, Sam I600, Sam I700, GL1000, HP6315, SX56, PDA2K, Jam, Xv6600 W/cam, Treo 650, I730 Wm2K3, Treo 700W, I730 w/WM 5.0, XV6700, Moto Q (Silver), Treo 700WX, xv6700 wm6, Moto Q Black, Moto Q9m, Sam I760, xv6800, xv6900, Q9C, Touch Pro, iPhone 3G 16G, iPhone 3gs 32G ... not even gonna list the non converged units

sarcasmsra
Firstly, I want to thank you for all of your excellent work on the 730.

Secondly, I'd like to ask you if you considered some alternatives on the A2DP approach. From some of your other posts it sounded like the problem with A2DP on the 730 might relate to a limit in bandwidth capacity on one or more of the 730's chips, rather than a software specific barrier. If that's the case, I was wondering if A2DP might work with lower bandwidth media files, and if there might be some bandwidth (or compression ratio) that works with A2DP, within the hardware limitations, but might still provide an audio quality improvement over the current approach.

Bandwidth requirements, might also be reduced (with higher relative quality) by using files which have been converted to mono. Any thoughts on these issues?

Pete

Pete,

1) Thanks.

2) As far as I know, the quality of the A2DP stream is not dependent on the media file being played. It would of course be possible for an application to packetize a pariticular media file appropriately and send it out over A2DP, but I don't believe that's how it's done. The A2DP spec says that the devices are supposed to choose the codec bitrate based on what is available on the channel, which implies on-demand re-encoding. Also, A2DP implementations are only required to support the SBC codec, which is NOT a standard codec for media files, again implying re-encoding. SBC is not very good compared to optional codecs of MPEG1, 2, or 4 audio. I don't know which codecs the Widcomm A2DP implementation supports, but the probem could be more than bandwidth. Since it is doing the encoding with software, it could be that it just can't encode fast enough to keep up with realtime. Or it could be that it isn't choosing a low enough bitrate. If Mpeg-4 were supported, even 96kbits sounds pretty good, and the i730 can handle that speed no problem.

The biggest problem for A2DP with the MS stack is that there is simply software implementation of the A2DP profile for any Windows CE 4.2 devices running the MS bluetooth stack. And unfortunately, implementing one would be very difficult or impossible. A2DP is a layer on top of AVDTP, a protocol which is not implemented in the Microsoft stack, and which is on top of L2CAP protocol, which is implemented but there is no interface to interact with it in Windows CE 4.2 (not documented interface, but there must be a way).

When I had Voice Command on a PDA2K, I remember that if you tried to use the "announce caller" feature and had a ring sound selected, they essentially stepped over each other and you got garbagy sounds. I had to turn the ring sound off in order to get VC to announce callers. Just a thought...

Thanks for the response.

On the hardware side:
My comment about bandwidth related to a post I thought I remembered from you, which indicated that you had seen some choppy audio transmission, and in which I thought you said the hardware might not be up to the task. (Perhaps my memory is wrong here.)

On the software issue:
As you probably know the iPaq has compatible "high quality" bluetooth stereo headphones. Would it be helpful to you (assuming you're interested in exploring this), to see if anything can be learned from what iPaq has done? There must be some folks here owning both an i730 and an iPaq, who would be interested in helping here. Is there any software on their iPaqs that they could send you that might help you get your questions answered?

The Bluetooth Stereo Headphones are compatible with HP iPAQ h2200, h4000, h5100, h5500, hx2000, rx3000 and hx4700 series Pocket PCs.

Pete

For those who commented they weren't having success, make sure your headset is on and paired before trying to switch the audio. This may be blatenly obvious but I thought I would state it for those having difficulty, the utility needs a device to switch to

__________________
Rock

I tried this with the audio going to the headset ... the announcements still go to the speakers ... so I just turned it off ... alas ... the world is not a perfect place ...

Fuzzy

__________________
Fuzzy
Kyo 6035, Sam I300, Sam I330, Kyo 7315, Treo 600, Sam I600, Sam I700, GL1000, HP6315, SX56, PDA2K, Jam, Xv6600 W/cam, Treo 650, I730 Wm2K3, Treo 700W, I730 w/WM 5.0, XV6700, Moto Q (Silver), Treo 700WX, xv6700 wm6, Moto Q Black, Moto Q9m, Sam I760, xv6800, xv6900, Q9C, Touch Pro, iPhone 3G 16G, iPhone 3gs 32G ... not even gonna list the non converged units