PDA

View Full Version : Creative CB2530


thardie
5th May 2006, 06:08 AM
I wanted to let everyone know that these headphones, although they seem to support some sort of A2DP (Can talk to them from a laptop supporting A2DP), they will not talk to windows Mobile 5 with A2DP. I have the Cingular 8125 (aka HTC Wizard), with the A2DP additions loaded on it and the 2.17 firmware. I have my wizard talking A2DP to Motorola headphones, and to a Scosche A2DP car receiver. They both work great, and even though the wizard will see the creative headphones (I have 2 of them, so I know it's not 1 defective set), and will see the "Wireless Stereo", when I try and connect the wireless stereo, I don't get the Headphones with the note icon like I do with the other A2DP devices.

FYI for anyone else considering the Creative CB2530

lmjabreu
6th January 2007, 12:22 AM
I can use them with my Trinity, but it was a little tricky.

The problem was with the Microsoft Bluetooth Stack, it tries to establish a secure connection when it is not required. Worked fine with my laptop(widcomm) and previous pocket pc(iPAQ H6365-widcomm) but the latter was unusable due to the lack of bandwidth.

I'm not sure if this is really the solution
but I believe you must add the CB2530 without entering a password first, the headphones will try to connect right after confirmation of the services we want to use(wireless stereo in this case),

"the device cb2530 is trying to connect... yes/no" - something like that

the pocket pc will request for a pin, enter 0000 and wait, the phones will disappear from the paired devices list, try again, this time insert the pin 0000 right after selecting the CB2530 from the found devices list and voilà, an A2DP connection will be established.

It's a little weird tough, the system sounds sound choppy, even with jointstereo off and increased bitpool(512 lol), PocketPlayer doesn't stream the audio through A2DP, and media player does it right and the sound quality is nice(only a few other skips but overall pretty nice and the original transmitter wasn't perfect either), but maybe because of the load of audio conversion on the CPU the whole UI gets sluggish, odd.(or maybe it's the bitpool value I used)

It works.