see posts below for instructions and files needed 8) .

ive got a S1HP…
do you think that the patch will also work with my notebook ??
would be great to use my HBH-600 with skype

I did like Bushman said and its all working now!

okay, i guess i need some clarification.  i’ve already got a tr with internal bt mod running with widcomm, also have an x505 with the sony bt dongle.  i’ve rationally though through bushman’s procedures, but am unsure how i should implement.  now i’m a little further thrown by luchao18’s additions.  it’s great to hear that you all are successful, but any recommendations as to how i should procede?

Clarification: The latest v2.0+EDR module that SONY uses on new VAIO models already have BT audio profiles (Headset, Audio Gateway, A2DP…etc) enabled, as SONY is officially promoting its new VAIO models + Skype + BT headset, NO MORE PATCH NEEDED. :D

The following procedure are tested on listed VAIO models with SP2 Bluetooth Stack preinstalled. If you have one of the listed models but has other stacks installed, the best way to avoid conflicts is to turn your bluetooth/wireless switch on and do a clean installation of windows xp with sp2 before proceeding.

————————————————————————————————————————————————————————————————————————————————————————————————————————
For VAIO-TR with v1.1 Internal Bluetooth Module

Patching and Installing, every step is VITAL, don’t ignore any of them(see bottom for the patch download link)

:!: Prevent SP2’s Bluetooth Support from running
1. Stop the SP2’s “Bluetooth Support Service” in Control Panel—>Administration Tools—> Services

2. Open command prompt, type the following commands, pressing Enter after each line:

CD /D %SystemRoot%\Inf
rename Bth.inf Bth.oldinf
rename Bth.pnf Bth.oldpnf
exit

3. Run “msconfig”—> go to “startup” column—>unclick “rundll32.exe bthprops.cpl…..”

4. Go to Control Panel—>System—> Hardware—>Device Manager

5. Manually (Have Disk method) replace the “USB Bluetooth Device” under “Bluetooth Radio” with the driver “Alps module with CSR Bluecore Bluetooth” in the patch file “csrbc01.inf”.

Have Disk method: click on “Update Driver”—> Select “Install from a list or specific location”—> Select “Don’t search, I will choose the driver to install”—> Click on “Have Disk”—> Point to “csrbc01.inf” in the patch folder—> Click “OK”—>There should be 1 single device listed, named “Alps module with CSR Bluecore Bluetooth”—> Click “Next”—> Click “OK”.

From

To

6. switch the bt/wireless off,Reboot

Patching
1. after reboot, switch on the bt/wireless, Run Patch.bat in Command Prompt:
Successful patching should end like this:
“usb on \\.\csr0 at 12000000bps
psset 427 0
bccmd_getresp sn:0x0001 ps ok hostio_map_sco_pcm d len:0x0001 0x0000
quit
Adieu!”

2. REBOOT

Install New Bluetooth Stack, You can choose between Bluesoleil (WITHOUT 5MB LIMITATION) or SONY (Toshiba OEM) stack (recommanded).  
see other posts for installing WIDCOMM Stack

Install Bluesoleil Stack:
1.  Download the edited :twisted:  Bluesoleil from
http://rapidshare.de/files/7070500/BlueSoleil_1.4.9.5_for_TR.rar.html

2. Install

3. overwrite the original file with the :twisted:  :twisted:  included.

4. Reboot, the “Alps Module with CSR Bluecore Bluetooth” under Universial Serial Bus Controllers should be replaced by “ALPS Bluetooth Device” under Bluetooth USB

Install Toshiba BT Stack:
1.Remove the bt driver “Alps module with CSR Bluecore Bluetooth”—> turn BT off—> reboot (DO NOT switch on your bt after reboot).

2.download the stack, this is the 3.20.01 version, tested and works, although a bit old, as current version is v4.xx.
http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_dtlViewDL.jsp?soid=1032745&moid=997820&BV;_SessionID=@@@@1542939006.1141576930@@@@&BV_EngineID=ccceaddheemhmeecgfkceghdgngdgmn.0&ct=DL

3. replace tosrfusb.inf in the driver folder “A5_Bluetooth.zip\Bluetooth\Windows\inf” with my edited tosrfusb.inf, download links:
http://rapidshare.de/files/7120049/Edited_tosrfub_for_TR.rar.html

or you can edit tosrfusb.inf yourself
Under [Standard], add:
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3001
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3002
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3003
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3004
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3007

Under [ControlFlags], add:
ExcludeFromSelect = USB\VID_044e&PID;_3001
ExcludeFromSelect = USB\VID_044e&PID;_3002
ExcludeFromSelect = USB\VID_044e&PID;_3003
ExcludeFromSelect = USB\VID_044e&PID;_3004
ExcludeFromSelect = USB\VID_044e&PID;_3007

Under [Strings], modify:
MSFT = “SONY”
StdMfg = “UGX”
Also add a line:
TosrfUsb.DeviceDesc2 = “Bluetooth USB Controller (ALPS)”

4. Install the stack, turn bt on when toshiba stack installation prompts you
*Reminder: some users get stucked at 56% of installation, it was a result of switching (atl+tab) away from the Toshiba installer before it finished. The “Please plug in the bluetooth device now” dialog is obscured from poping-up.

Solution: Don’t switch away the installation task.

5. Reboot

6. Make sure “Connect only to a device that is copyright-protected by SCMS-T method” under “Copyright Protection Setting” is unchecked (default is unchecked )

—————————————————————————————————————————————————————————————————————————————————————————————————————————
For VAIO-T, S, A with v1.2 Internal Bluetooth Module (PID 3007 only)

Patching and Installing, every step is VITAL, don’t ignore any of them (see bottom for the patch download link)

:!: Prevent SP2’s Bluetooth Support from running
1. Stop the SP2’s “Bluetooth Support Service” in Control Panel—>Administration Tools—> Services

2. Open command prompt, type the following commands, pressing Enter after each line:

CD /D %SystemRoot%\Inf
rename Bth.inf Bth.oldinf
rename Bth.pnf Bth.oldpnf
exit

3. Run “msconfig”—> go to “startup” column—>unclick “rundll32.exe bthprops.cpl…..”

4. Go to Control Panel—>System—> Hardware—>Device Manager

5. Manually (Have Disk method) replace the “USB Bluetooth Device” under “Bluetooth Radio” with the driver “Alps module with CSR Bluecore Bluetooth” in the patch file “csrbc01.inf”.

Have Disk method: click on “Update Driver”—> Select “Install from a list or specific location”—> Select “Don’t search, I will choose the driver to install”—> Click on “Have Disk”—> Point to “csrbc01.inf” in the patch folder—> Click “OK”—>There should be 1 single device listed, named “Alps module with CSR Bluecore Bluetooth”—> Click “Next”—> Click “OK”.

From

To

6. switch the bluetooth/wireless button off. Reboot

Patching
1. after reboot, switch the bt/wireless on, Run Patch.bat in Command Prompt:
Successful patching should end like this:
“usb on \\.\csr0 at 12000000bps
psset 427 0
bccmd_getresp sn:0x0001 ps ok hostio_map_sco_pcm d len:0x0001 0x0000
quit
Adieu!”

2. REBOOT

3. For v1.2 bt module (PID 3007) you can also enable A2DP stereo headset profile after the above patch being successfully applied and REBOOTED.
JUST:
In Command Prompt, run the patch file “a2dp.bat”.
Succesful patching should end like this:
“btcli (built Feb 20 2003, 18:55:01)
Version 1.18
Copyright (C) 2000-2002 CSR Ltd. All Rights Reserved.
usb on \\.\csr0 at 12000000 bps
psset 996 1416
bccmd_getresp sn:0x0001 ps ok loop_filter_trim d len:0x0001 0x0588
quit
Adieu!”

4. REBOOT

5. Remove the bt driver “Alps module with CSR Bluecore Bluetooth”—> turn BT off—> reboot (DO NOT switch on your bt after reboot).

Install SONY (Toshiba OEM) stack:
currently only Toshiba OEM stack provides best quality on A2DP stereo audio over stereo bt headsets.
1.download the stack, this is the 3.20.01 version, tested and works, although a bit old, as current version is v4.xx.
http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_dtlViewDL.jsp?soid=1032745&moid=997820&BV;_SessionID=@@@@1542939006.1141576930@@@@&BV_EngineID=ccceaddheemhmeecgfkceghdgngdgmn.0&ct=DL

2. replace tosrfusb.inf in the driver folder “A5_Bluetooth.zip\Bluetooth\Windows\inf “with my edited tosrfusb.inf, UGX or UGT(really rare) depends on your module, you can find it when “new hardware detected” windows pops up, use the appropriate one for replacing.
edited torsrfusb.inf for UGX module, download links:
http://rapidshare.de/files/7262218/tosrfusb_UGX_module.rar.html
edited torsrfusb.inf for UGT module, download link:
http://rapidshare.de/files/7262253/tosrfusb_UGT_module.rar.html

or you can edit tosrfusb.inf yourself
Under [Standard], add:
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3001
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3002
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3003
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3004
%TosrfUsb.DeviceDesc2%=TosrfUsb_Device, USB\VID_044e&PID;_3007

Under [ControlFlags], add:
ExcludeFromSelect = USB\VID_044e&PID;_3001
ExcludeFromSelect = USB\VID_044e&PID;_3002
ExcludeFromSelect = USB\VID_044e&PID;_3003
ExcludeFromSelect = USB\VID_044e&PID;_3004
ExcludeFromSelect = USB\VID_044e&PID;_3007

Under [Strings], modify:
MSFT = “SONY”
StdMfg = “UGX” or StdMfg = “UGT” , Depends on your module, you can find it when “new hardware detected” windows pops up
Also add a line:
TosrfUsb.DeviceDesc2 = “Bluetooth USB Controller (ALPS)”

3. Install the stack, turn bt on when toshiba stack installation prompts you
*Reminder: some users get stucked at 56% of installation, it was a result of switching (atl+tab) away from the Toshiba installer before it finished. The “Please plug in the bluetooth device now” dialog is obscured from poping-up.

Solution: Don’t switch away the installation task.

4. Reboot

5. make sure “Connect only to a device that is copyright-protected by SCMS-T method” under “Copyright Protection Setting” is unchecked (default is unchecked )

for better quality:
Detail—>Sound Quality

Patch download, included CSR driver supports PID 3003, 3004, 3007 modules.
http://chrisrae.com/hosting/Vaio_Bluetooth_stereo_patch.rar (thank you pugwash75 for hosting )
http://rapidshare.de/files/6986066/Vaio_Bluetooth_stereo_patch.rar.html

Hint:
Q: how to know my module’s PID when SP2 bt stack is installed?
A: If you have sp2 bt stack installed, find out your module’s PID by:
Device Manager—> Bluetooth Radio—> USB Bluetooth Device—> Details—> Hardware Ids

(Patch and Photos are courtesy of Master Snowwhite )

I can provide some clarification for those who want to use WIDCOMM stack.

download here
link dead

Lourenco,
I have Widcomm stack, could you please provide some clarification? Thanks!

Firstly and most important of all, you´ll need a special .inf file tha contains a WIDCOMM driver for the inernal bluetooth module. I may need to send it so someone could host it. Anyone?

I have a Sony Vaio T150 P/L and although it has an upgraded version of the ALPs CSR bluetooth module (bluetooth 1.2 compliant, PID version 3007), I suspect that the same firmware code error still exists in this bluetooth module version also. From reviewing other forums and sites, it seems that all VAIO models have this same audio headset bug—not just the older TR model.  Do forum members think this patch, or a variant )might work on other VAIO models, including the most recently released?  I am using the widcomm stack (version 4.0.1.700) and everything seems to work including connecting/disconnecting to audio headset and audio gateways, but no sound other than an occasional buzz).  A general fix would be of great assistance accross the whole VAIO community since bluetooth headphones are very convenient in VOIP phone conversations (Skype, etc.)  I would not hold my breath expecting Sony to offer a software update based upon their track record of customer support so far.

Found this thread comment on a Skype user forum dealing with bluetooth headset issues

http://forum.skype.com/viewtopic.php?t=10822&postdays=0&postorder=asc&start=60

According to the Sony knowledge base, Sony provides the following response back to an inquiry regarding bluetooth headset operability

“SOLUTION:  Sony® notebook computers are not compatible with Bluetoothâ„¢ wireless technology headsets “

While Sony for whaterver undisclosed reason (they do not state it is because they rely on MS XP bluetooth profiles) has chosen not to implement this bluetooth profiile despite it now being available on most other internal/external bluetooth modes brands, , hopefully some code savvy members of this forum can provide us Vaio users a genralized patch to add this capabilty accross the Vaio model lines

[quote author=“T150user”]I have a Sony Vaio T150 P/L and although it has an upgraded version of the ALPs CSR bluetooth module (bluetooth 1.2 compliant, PID version 3007), I suspect that the same firmware code error still exists in this bluetooth module version also.

Thats bad news! :-(

[quote author=“T150user”]
From reviewing other forums and sites, it seems that all VAIO models have this same audio headset bug—not just the older TR model.  Do forum members think this patch, or a variant )might work on other VAIO models, including the most recently released?

I think it will work with any CSR based bluetooth module, I think it’s safe to try.
If the driver don’t work, then the patch can’t patch.
Have a go, and report any failure/success!

Just change (in csrbc01.inf) the PID on this line:
%ALPS.DeviceDesc%=CSRBC01.Dev,      USB\VID_044e&PID;_3003     ; ALPS

From 3003 to 3007.

If this works it would be nice to add more DeviceDesc to fit every sony laptop with this “bug”.

Which VID/PID have this “silence/buzz” bug?

/Bushman

Thank you, thank you, thank you, this bug had me going crazy.

Works perfectly on S270F+Internal BT mod+Widcomm 4.0.1.700+Sony Ericsson HBH-600

Now I can use Skype with no wires

My module had VID 044e PID 3007 (I think is the same as in the T series)

Jbanos, glad you got yours working!  Assume that my T150 will work as well since we share the same VID/PID numbers on our bluetooth modulel.  Did you use the patch as is that was provided by luchao18 (except for changing vid/pid settings in csr as suggested by bushman) or did you also use a different widcomm “.inf “driver as offered by Lourenco?  How is the audio quality (both receive and transmit)?

Some explicit instructions would be of help to us that are as not as familiar with firmware patches and are nervous about inadvertantly screwing up their bluetooth module.

Thanks for all the great help out there on this forum. I have been trying to solve this problem for weeks!  :D

I have received a couple of messages asking for more detailed info so here it is:

I first removed all BT stacks, if you are using the MS stack just rename the following files in your /windows/inf folder

bt.pnf -> bt.pnf.old
bth.inf -> bth.inf.old

Remove the entries under bluetooth in the device manager

modify csrbc01.inf in the patch folder (for download see above, thanks Chris for hosting it)

modify line 34: %ALPS.DeviceDesc%=CSRBC01.Dev,      USB\VID_044e&PID;_3003 ; ALPS

and replace your VID and PID Numbers, the PID for my module is 3007

save

reboot

if you are using the Widcomm stack I don’t think you have to uninstall it just remove the entries under bluetooth in device manager (if this does not work then remove all the widcomm stack, you can follow the info on  

reboot

upon reboot you will receive a new hardware found message, install the driver in the patch folder under csrbc01.inf if you modified the VID and PID to match your module it will install as a USB bus controller.

Run the patch from a command window.

change the driver of the ALPS USB bus controller for Widcomm driver (if you had the Widcomm Stack installed) reboot and you are done.

If you did not have the Widcomm Stack Installed now it’s the time to do it, there are plenty of resources on the net just google widcomm 4.0.1.700
and follow instructions. If you are installing the stack with these instructions you have to add your VID and PID to btwusb.ini in the widcomm install package.

I hope this helps

The fix works for a T150 also!

Uses the same mods to as Jabonos used for his S270

modify line 34 in the csrbc01.inf file as follows: %ALPS.DeviceDesc%=CSRBC01.Dev, USB\VID_044e&PID;_3003 ; ALPS

Thanks to all of you for the detailed instructions and suggestions —especially to bushman for first isolating the problem and providing the patch.  Can not believe that Sony and Alps have not bothered to provide a bug fix in all this time.  Hope that the TR forum continues to expand to cover support of all Vaio notebook models.