Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.06WW

[henrylim]

Hi all,

I believe there's a lot of discussion generated on the merits and faults of the various Himalaya WM2003SE default Microsoft BT implementations.

I have looked at the 2.20 BT Registry and found the following settings:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\1]
"ProfileUsed"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Headset/Hands-Free"

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\2]
"EventIndex"=dword:00000000
"SvcName"="Serial Port COM5"

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\3]
"EventIndex"=dword:00000000
"SvcName"="ActiveSync"

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\4]
"DUNsetup"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Dial-up Networking"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
@=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001103-0000-1000-8000-00805F9B34FB]
"BTDUN.dll"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0350278F-3DCA-4e62-831D-A41165FF906C]
"BTSPP.dll"=dword:00000000
"Default"="Active Sync"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001101-0000-1000-8000-00805F9B34FB]
"BTSPP.dll"=dword:00000000
"Default"="Serial Port"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0000111E-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001108-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000

I believe that the first 4 "CurAvailSvc" entries are used together with the BTBond_UI.exe that is called after BT pairing. For those who don't know what I am taking about, BTBond_UI.exe is called in 2.20 ROM after pairing to display a page with 4 checkboxes (Headset/Hands-Free, Serial, Dial-up Networking, ActiveSync). These 4 entries are missing from 2.02 and 2.06 registry.

In addition, comparing the registry against 2.02 and 2.06, you will find that 2.20 is using different BT files for enabling BT ActiveSync, Serial Port, Dial-up Networking and Headset/Handsfree:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0000111E-0000-1000-8000-00805F9B34FB]
"btagsvc.dll"=dword:00000000
@="Handsfree"


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"btagsvc.dll"=dword:00000000
"headset"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BthASPlugIn.dll"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BthASPlugIn.dll"=dword:00000000


These particular registry entries are missing from 2.06 ROM but available in 2.02tl and 2.20 ROM:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
@=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se ttings]
"IgnoreExternal"=dword:00000001

SIN has did his investigation and found that the second "AudioGateway" entry should not be updated as it prevents the mic from working when you paired your BT headset with "headset" mode instead of "handsfree" mode.

Under Magician BT registry, there is an additional entry:

[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001

You will find that this entry is not enabled in 2.02/2.06 or 2.20 ROM. Any ideas how it helps?

[darren_the]

[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001

If I m not wrong

It is with 2.2 & 2.06 also




[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

This above not in 2.2


& also in 2.2

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices]


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0000111E-0000-1000-8000-00805F9B34FB]
@="Handsfree"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BTSPP.dll"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BTSPP.dll"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
"BTDUN.dll"=dword:00000000

[henrylim]

[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001

The entry is with 2.02/2.06, but my device with 2.06 has the entry as 0x0 instead of 0x1. I'm not sure what it does though.

[henrylim]

& also in 2.2

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices]


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0000111E-0000-1000-8000-00805F9B34FB]
@="Handsfree"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BTSPP.dll"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BTSPP.dll"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
"BTDUN.dll"=dword:00000000

Yes, essentially the same thing that I found out. See the Services serial numbers, it's identical.

[Rabia]

good job, this might help us, any recomendation for me? i have 2.02t the handsfree works to an extened but the mic as some of you know is not working, any recomendation for that? anyone think i should try ssomething from the above, i backup daily :lol:

[Rabia]

Hi all,

I believe there's a lot of discussion generated on the merits and faults of the various Himalaya WM2003SE default Microsoft BT implementations.

I have looked at the 2.20 BT Registry and found the following settings:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\1]
"ProfileUsed"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Headset/Hands-Free"

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\2]
"EventIndex"=dword:00000000
"SvcName"="Serial Port COM5"

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\3]
"EventIndex"=dword:00000000
"SvcName"="ActiveSync"

[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\4]
"DUNsetup"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Dial-up Networking"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
@=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001103-0000-1000-8000-00805F9B34FB]
"BTDUN.dll"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0350278F-3DCA-4e62-831D-A41165FF906C]
"BTSPP.dll"=dword:00000000
"Default"="Active Sync"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001101-0000-1000-8000-00805F9B34FB]
"BTSPP.dll"=dword:00000000
"Default"="Serial Port"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0000111E-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001108-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000

I believe that the first 4 "CurAvailSvc" entries are used together with the BTBond_UI.exe that is called after BT pairing. For those who don't know what I am taking about, BTBond_UI.exe is called in 2.20 ROM after pairing to display a page with 4 checkboxes (Headset/Hands-Free, Serial, Dial-up Networking, ActiveSync). These 4 entries are missing from 2.02 and 2.06 registry.

In addition, comparing the registry against 2.02 and 2.06, you will find that 2.20 is using different BT files for enabling BT ActiveSync, Serial Port, Dial-up Networking and Headset/Handsfree:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0000111E-0000-1000-8000-00805F9B34FB]
"btagsvc.dll"=dword:00000000
@="Handsfree"


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"btagsvc.dll"=dword:00000000
"headset"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BthASPlugIn.dll"=dword:00000000


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se rvices\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BthASPlugIn.dll"=dword:00000000


These particular registry entries are missing from 2.06 ROM but available in 2.02tl and 2.20 ROM:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Ha ndsfreeProfileOn]
@=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Au dioGateway]
"BTAudioModule"="OEMExtDll.dll"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Se ttings]
"IgnoreExternal"=dword:00000001

SIN has did his investigation and found that the second "AudioGateway" entry should not be updated as it prevents the mic from working when you paired your BT headset with "headset" mode instead of "handsfree" mode.

Under Magician BT registry, there is an additional entry:

[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001

You will find that this entry is not enabled in 2.02/2.06 or 2.20 ROM. Any ideas how it helps?

can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working

[tumtum]

By the way, does anyone know about BlueTooth patch for BlueAngle ?
I still look around but found nothing.

Can we use that patch to make WM2003SE for XDA2 use Bluetooth more stable?

And thank for everyone who still work on this topic.

[Girly girl]

Is that why my active sync isnt working with BT?
I have upgraded my rom to the 2003SE and now i cant manage to sync by BT.
I can use my car BT though with the device without a problem, but i can activesyc by BT.
Also, when trying launch the destinator and use it with BT GPS it says the driver is occupied (or something).

Is the problem because of the 2003SE upgrade? should I downgrade and all will work just fine?

Please help me.

[henrylim]

can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working


Here it is.

[steverae]

I hve found the following problems with the BT stack on all the SE updates available

1) BT Headset reception is rubbish, tried the bluetrek G2 and Itech Clip and sound quality in the callers end is really quiet compare to the wm2003 original rom

2) BT Activesync does not work end of story

3) BT icon on today screen for headset keeps dissappearing

My opinion :-

Stick with 2003 and use SRS to rotate the screen to landscape until a fix is found for the SE os.

I have tried all versions of se 2.02, 2.06 (which really zapped my battery) and 2.20.07chs translated, all have they own lttle problems and none are 100% complete, however i have found 2.02 is probably the most stable.

[Rabia]

can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working


Here it is.

thanks man but looks harder than i thought could you post your registery file, are you 2.20 chs?

[Looking Glass]

I hve found the following problems with the BT stack on all the SE updates available

1) BT Headset reception is rubbish, tried the bluetrek G2 and Itech Clip and sound quality in the callers end is really quiet compare to the wm2003 original rom

2) BT Activesync does not work end of story

3) BT icon on today screen for headset keeps dissappearing

My opinion :-

Stick with 2003 and use SRS to rotate the screen to landscape until a fix is found for the SE os.

I have tried all versions of se 2.02, 2.06 (which really zapped my battery) and 2.20.07chs translated, all have they own lttle problems and none are 100% complete, however i have found 2.02 is probably the most stable.

Your'e right, but....

ONLY SE really has a bare minimun support for handsfree devices.
No matter what you feel about WMP 10, ugly skins, or wrong keyboard maps, if you WANT or NEED handsfree your only choice is 2.XX

:cry:

Not there yet...

[henrylim]

2) BT Activesync does not work end of story



I've got it working. I don't use to have BT USB dongle, but bought one since I've curious why so many thinks that BT ActiveSync is a gonna.
I did do some research on the Net, and found quite a number of gems from iPAQ users complaining about the same thingie.

Are u using XP SP2 or SP1?

[henrylim]

can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working


Here it is.

thanks man but looks harder than i thought could you post your registery file, are you 2.20 chs?

I'm 2.06 base. I'm posting the 220 reg file, based on a conversion of default.fdf from the 220 ROM package. I do hope that I've the full reg converted since it appears that the file has a few things missing from the exported reg of an installed ROM.

Perhaps someone with 220 ROM installed can comment?

[zimo]

I've got it working. I don't use to have BT USB dongle, but bought one since I've curious why so many thinks that BT ActiveSync is a gonna.
I did do some research on the Net, and found quite a number of gems from iPAQ users complaining about the same thingie.

Are u using XP SP2 or SP1?

Would you be so kind and post here step by step config of Active Sync over BT, you did? There are probably more of us with this problem. :wink:

Thanks!

[Looking Glass]

Hi Everybody!

I've noticed some increased troubles when, after having a BT equipped PC with Widcomm drivers, (the most usual) you upgrade to Win XP SP2.

Some of you are pointing to this, and it might be part of the trouble, but this is also true that versions 2.02 and 2.06 did permit me syncing via BT, and version 2.20 does not. So it looks like some kind of incompatibility among XP SP2 and some 2003 SE versions on our XDA.

Since I've been unable to upgrade my Widcomm BT drivers on my PC, I can't either assure this is only a Microsoft mess (Widcomm seems a bit guilty in my opinion)

Any guess or idea for getting BT ActiveSync back to work in 2.20?

[lbretth]

This is a little OT, but the problem with XP SP2 and Widcomm drivers is that MS has added BT drivers to Windows that are digitally signed. As a result when you connect you BT device it will always install the MS drivers as default because the Widcomm ones aren't certificated. In order to get round this you have to remove the device from device manager and re-install it picking the drivers yourself.

[Looking Glass]

Nice try, but, how did you get a workaround to the "license" message when reinstalling or upgrading the widcomm drivers? They don't even have SW upgrades in their web site!

:(
PD I've been forced to restore my laptop hard disk to factory state when failing to get BT back to work after "upgrading" the widcomm drivers. This is crazy!

[Sin]

They don't even have SW upgrades in their web site!

Here's the Widcomm XP installation package extracted from the latest Logitech SetPoint 2.22 update for my diNovo KB & Mouse.

When installed as part of the Setpoint 2.22 upgrade, it provides the drivers for my Bluetooth wireless hub.

With 2.20XX, the BT ActiveSync won't initialise but I've had no problems using BT ActiveSync on 2.02.t1WWE, 2.06.00WWE & a merge of both.

:arrow: NOTE: I've only attached the Widcomm installation package, you'll still need to provide your own drivers for your BT Hub/Dongle.

Hope it helps: :wink:

[Looking Glass]

Thanks a lot Sin, will make another try.

In fact I tried installing the whole thing downloaded from the Logitech Site, but again it failed to install properly.

The BT in my laptop is factory built-in by Acer, and this is the annoying part, since Acer don't even provides an upgrade for it. In their site you can read: "Before installing XP SP 2, remove your BT drivers, and reinstall them after upgrading to SP 2", but the whole thing failed, and there were not way to get rid of the license message.

The Activesync problems only appeared after moving to 2.20.07 "translated", but it was the only way to solve the "dual-stereo" bug, so I feel mostly stuck: pick one of...

- No Hands free profile
- Dual Stero mic and earphone... or
- No BT Active Sync.

Take your bets ladies and gentlemen...

Will try with your drivers and help.

Regards.
:wink:

[henrylim]

Thanks a lot Sin, will make another try.

In fact I tried installing the whole thing downloaded from the Logitech Site, but again it failed to install properly.

The BT in my laptop is factory built-in by Acer, and this is the annoying part, since Acer don't even provides an upgrade for it. In their site you can read: "Before installing XP SP 2, remove your BT drivers, and reinstall them after upgrading to SP 2", but the whole thing failed, and there were not way to get rid of the license message.

The Activesync problems only appeared after moving to 2.20.07 "translated", but it was the only way to solve the "dual-stereo" bug, so I feel mostly stuck: pick one of...

- No Hands free profile
- Dual Stero mic and earphone... or
- No BT Active Sync.

Take your bets ladies and gentelemen...

Will try with your drivers and help.

Regards.
:wink:

Perhaps you can try changing the 220 serial port DLL to the 206 serial port DLL ONLY. I reckon that can be done if you are careful to compare and port the settings.

Thanks a lot Sin, will make another try.

In fact I tried installing the whole thing downloaded from the Logitech Site, but again it failed to install properly.

The BT in my laptop is factory built-in by Acer, and this is the annoying part, since Acer don't even provides an upgrade for it. In their site you can read: "Before installing XP SP 2, remove your BT drivers, and reinstall them after upgrading to SP 2", but the whole thing failed, and there were not way to get rid of the license message.

The Activesync problems only appeared after moving to 2.20.07 "translated", but it was the only way to solve the "dual-stereo" bug, so I feel mostly stuck: pick one of...

- No Hands free profile
- Dual Stero mic and earphone... or
- No BT Active Sync.

Take your bets ladies and gentlemen...

Will try with your drivers and help.

Regards.
:wink:

What have we learnt from all this..... ?

Does the mic on a BT headset (under 2.02t1 WWE) work correctly when paired in headset mode / handsfree mode or not at all in any modes ?

Can BT activesync be initialised and will it work properly, (with some tweaking) - is it a WM2003SE problem or a Windows XP SP2 problem.

If someone could answer these two questions i guess it would save alot of people time trawling through the reems of posts on this subject.

Cheers

[Looking Glass]

What have we learnt from all this..... ?

Does the mic on a BT headset (under 2.02t1 WWE) work correctly when paired in headset mode / handsfree mode or not at all in any modes ?

Can BT activesync be initialised and will it work properly, (with some tweaking) - is it a WM2003SE problem or a Windows XP SP2 problem.

If someone could answer these two questions i guess it would save alot of people time trawling through the reems of posts on this subject.

Cheers

AFAIK from my experience:

ONLY 2.20.07 "translated" (unable to try the pure CHS version) allows you to set during pairing a device to be JUST headset or handsfree. This seems related to how the "dual stereo" problem in previous 2.02t1 and 2.06 has been solved.

The 2.0X versions have an erratic behaviour depending on your headset/handsfree device: no headset mic, both speakers, both mics, echo on the other side of the call, etc.

However, for some unknown (to me) reason, 2.20.07 has some kind of imcompatibility with BT ActiveSync, allegedly due to SP2 on Win XP Systems, since other guys in the forum seem to have it working.

Agree? Disagree? More Info?

[steverae]

What have we learnt from all this..... ?

Does the mic on a BT headset (under 2.02t1 WWE) work correctly when paired in headset mode / handsfree mode or not at all in any modes ?

Can BT activesync be initialised and will it work properly, (with some tweaking) - is it a WM2003SE problem or a Windows XP SP2 problem.

If someone could answer these two questions i guess it would save alot of people time trawling through the reems of posts on this subject.

Cheers

Woops, that was me who posted that message.. I installed 2.06 to night with the 2.06 extended rom for orange customers. I setup my bluetooth connection the same way as i always do and hey IT WORKED ! connected now as i type this....

What i do is pair my m1000 with my laptop (belkin PCMCIA BT card) and let it set the serial port.

I then swittch on both ports on my m1000 (com4 and com5).

After that i use the connection wizard to create a serial post (com4)

Then i set activesync to use COM5 (Don;t ask me why)

The final step is to remove the laptop from the ipaq and re-pair it this time do not set up the BT serial port, go into activesync on the M1000.

Connect the serial port on the PC, then click the connect via BT option on the M1000 and hey presto, it connects.....

Just gotta get my itech BT clip to function correctly now.

So i've managed to crack the BT activesync problem, next i need to find a way to get my mic on my BT headset (itech clip) to work, it won't activate unless in headset mode and then the mic doesn't seem to work to well, very quiet, guess it's picking up the sound from the pda mic, now in 1.72 it worked fine

how do you set this to handsfree mode as i only get the option when pairing to select headset ?

[powershot-g2]

I have tried all versions of se 2.02, 2.06 (which really zapped my battery) and 2.20.07chs translated, all have they own lttle problems and none are 100% complete, however i have found 2.02 is probably the most stable.

That was also my conclusion and the reason why I downgrade it back to 1.72 wich is a VM2003. It's rock stable (for the most) and my headset, a Jabra BT200, works at a glance with that ROM. I have also triede the English translation of the Chiness 2.20 but for now fall back to 1.72 wich i think works best for me. Also have i tried the 2.02 and thats really p****** me of with the support of my headset in that version.

Steven

[henrylim]

What have we learnt from all this..... ?

Does the mic on a BT headset (under 2.02t1 WWE) work correctly when paired in headset mode / handsfree mode or not at all in any modes ?

Can BT activesync be initialised and will it work properly, (with some tweaking) - is it a WM2003SE problem or a Windows XP SP2 problem.

If someone could answer these two questions i guess it would save alot of people time trawling through the reems of posts on this subject.

Cheers

Ok, perhaps gotta make it clear down here. The default ROM installation for either of the 3 WM2003SE ROM has their fair share of BT problems.

However, you will find that it can be minimized by either of these 4 methods:
(a) use base 2.02tl or 2.06WWE ROM, merge the 2 ROMs as per SIN's work.
(b) use base 2.02tl or 2.06WWE ROM, merge the 2 ROM's registry
(c) use 220 ROM, use 2.02tl or 2.06WWE BT serial port drivers for BT ActiveSync
(d) use 202tl, 206WWE or 220 ROM, replace 172WWE BT drivers and registry settings with either of the 3 ROMs.

The interesting fact about 172WWE ROM is that it as all the drivers that 202 and 206 ROM has with regards to BT. The funny thing is that it doesn't have the registry settings for handsfree profile or use of BTIcon.dll to enable the system tray icon.

Don't ask me what's my experience as I've mix the drivers/registry settings for 202,206 and 220 and got my BT working fine for me. (headset mic with headset mode, XDA2 mic with handsfree mode, BT ActiveSync, Web surfing with BT ActiveSync connection etc)

Due to request from one of my friend who couldn't pair his archane BT headset with 206, I've port over some 172 BT drivers to 206 and my BT is still working the same for me. Perhaps someone else can experiment?

I mean, how do you tell the difference if there was none?

Hey, good news though. Sin is merging 206 and 202 ROM installation to have a more stable ROM. DrStein is experimenting with Widcomm Phone BT on XDA2 (porting from XDA2s I believe). I wish them great success!

[henrylim]

Commonly Used and Implemented Bluetooth Profiles



Generic Access Profile
Foundation for all other profiles. Provides access and security functions to other profiles.

Service Discovery Application Profile
Used to discover other devices and the services on those devices. Allows a Bluetooth requesting device to discover the services offered by a another device. Included on all Bluetooth devices.

Serial Port Profile
Used with ActiveSync or HotSync software to synchronize a PDA with a portable computer. Also used for other legacy serial applications. Provides RS-232 serial cable emulation for Bluetooth devices. Legacy applications can use a Bluetooth link without any modification as a serial cable link.

Dial-up Networking Profile
Allows a mobile phone or dial-up modem to be used to access a network. Connects a computer device to a WAN through a dial-up networking gateway device such as a mobile phone or dial-up modem. The WAN can be a digital mobile network such as GPRS or the Public Switched Telephony Network (PSTN).

Object Push Profile
Used to exchange business cards (vCard), appointments (vCal), or to "push" objects. Uses the Generic Object Exchange profile to transfer specific objects between devices. Also used to send objects to a Bluetooth printer.

Generic Object Exchange Profile
Used as a foundation for other object-oriented profiles to perform tasks such as printing or file and business card transfers. IrDA replacement. Used with an application layer to provide a method for file transfer, object push, or synchronization between two devices. Uses a Bluetooth version of the IrDA OBEX layer. (The OBEX layer is above the RFCOMM and L2CAP layers of the Bluetooth protocol stack.)

Human Interface Device (HID)
Profile Provides support for devices such as a Bluetooth mouse, keyboard, joystick, or gamepad. Uses HID protocol from the USB specification. Provides quality of service for low-latency performance. On the PC, this is a new Bluetooth profile. Microsoft plans to make this profile available in a future version of the Pocket PC operating system.
Hard Copy Cable Replacement (HCRP) Profile Allows two Bluetooth devices to establish the equivalent of a wired connection (for example, a Windows driver-to-printer connection). Provides application-layer connectivity. The application and device must handle the protocol. For example, a Microsoft® Windows® driver formats the printer output that is sent over a Bluetooth HCRP connection to the printer, just as if it were a wired connection.

Audio Gateway/Headset Profile
Allows Bluetooth audio headsets to link wirelessly to telephony devices. Uses a Synchronous Connection Oriented (SCO) channel for full-duplex telephony audio and an Asynchronous Connectionless Link (ACL) for control signaling. Provides telephony-grade audio, rather than high-fidelity stereo sound. May not be directly relevant for portable computer applications.

PAN Profile
Used to connect Bluetooth devices in a personal area network. While the new PAN profile is not yet widely available, it is a fundamental profile being developed by the Bluetooth SIG that will be supported in future Microsoft operating systems.

File Transfer Profile
Used to transfer files between Bluetooth devices. Allows files or folders to be browsed, pulled, pushed, and deleted between two devices. Files can also be transferred using the Object Push or PAN profiles. On the PC, the PAN profile may supercede the File Transfer profile over time.

[henrylim]

Both profiles enable audio to be transmitted bidirectionally between two Bluetooth devices.

The difference is in what the two devices expect from each other in terms of capabilities.

Originally the Headset profile was designed to be the primary way to connect with....pay attention here....headsets.

The Hands Free profile was meant for devices like car speakerphones, where it was assumed there would be more buttons an easier to operate set of controls.

So in terms of capabilities, the Headset profile does the basics. Initiate a call, end a call. You can transfer audio from the phone to the headset in the middle of a call, too. That's pretty much it.

When you initiate a call from a headset, or try to transfer audio in an existing call, the headset tries to connect to the (one) device it is paired with. Prior to that, it had no connection at all, and the other device had no idea if it was even around.

Hands Free, on the other hand, can do much more. You can reject a call, redial the last number dialed, transfer audio back to the other device - and initiate and end a call, of course.

When you turn on a Hands Free device, it will look for any of the potentially multiple devices it is paired with. When it finds one, it will register with it so that the other device (presumably a phone), will know that it is there.

The headset and phone are now on more equal terms, and as such can do the more advanced functions like transfer sound back and forth.

This is an over simplifcation, of course, but it gives you the basics.

[steverae]

I'd like to take this oppotunity to thank Darren_the and SIN for they contributions to making my wm2003se based m1000 work with my bt headset and activesync over bt.

thank you.


I am a happy camper know.....

[[Krueger]Dr.Stein]

To henrylim Good Job Bro!

As per our PM exchange my status of the Broadcom 3500 on the Xda II has hit the wall. ActiveSync and the other profiles works perfectly but so much I can say about HandsFree profile.

Regards to the HFP I have managed to transfer audio to the G2 but the mic input still stays on the Xda II.

I have recently acquired the M$ Voice Command however to make this a success I need the complete registry of the Xda IIs.

Any contributors please?

[henrylim]

Dr.Stein]To henrylim Good Job Bro!

As per our PM exchange my status of the Broadcom 3500 on the Xda II has hit the wall. ActiveSync and the other profiles works perfectly but so much I can say about HandsFree profile.

Regards to the HFP I have managed to transfer audio to the G2 but the mic input still stays on the Xda II.

I have recently acquired the M$ Voice Command however to make this a success I need the complete registry of the Xda IIs.

Any contributors please?

Check out this 2 postings:

http://forum.xda-developers.com/viewtopic.php?p=79646#79646

Posting 1 is a Widcomm upgrade that claim to make mono AM Radio-quality music pipe-over to the headset as well, but it may not work for XDA2.

http://forum.xda-developers.com/viewtopic.php?p=79740#79740

Posting 2 is trying to port MS BT voice dialing from Moto MPX.

For some reason, I've experienced a lot of "insufficient memory" error if I just put Widcomm things into a cab file to install. If I painstakingly copy files over to /Windows, I'm ok. I'm suspecting that WM2003SE don't take too well to registry merge using CAB method.

Any, just this morning, my connection to G2 headset failed and refuses to be connected. Can you try to see if the Mono sound piping works for Widcomm stack?

BTW, I managed to get a copy of HP phone's registry. Guess what? They have a more complete set of MS BT profiles (the LAN access, Voice Gateway etc) than we do, just that they kept the KEYs and remove the rest of the parameters underneath.

What that means is MS may have actually released the ROM with a more or less complete set of BT profiles. It is probably up to the device manufacturers to test and release compatible drivers.

Hey, any M$ fellas here... we know you are reading the forums... :twisted:

[Looking Glass]

Ok, perhaps gotta make it clear down here. The default ROM installation for either of the 3 WM2003SE ROM has their fair share of BT problems.

However, you will find that it can be minimized by either of these 4 methods:
(a) use base 2.02tl or 2.06WWE ROM, merge the 2 ROMs as per SIN's work.
(b) use base 2.02tl or 2.06WWE ROM, merge the 2 ROM's registry
(c) use 220 ROM, use 2.02tl or 2.06WWE BT serial port drivers for BT ActiveSync
(d) use 202tl, 206WWE or 220 ROM, replace 172WWE BT drivers and registry settings with either of the 3 ROMs.

The interesting fact about 172WWE ROM is that it as all the drivers that 202 and 206 ROM has with regards to BT. The funny thing is that it doesn't have the registry settings for handsfree profile or use of BTIcon.dll to enable the system tray icon.

Don't ask me what's my experience as I've mix the drivers/registry settings for 202,206 and 220 and got my BT working fine for me. (headset mic with headset mode, XDA2 mic with handsfree mode, BT ActiveSync, Web surfing with BT ActiveSync connection etc)

Due to request from one of my friend who couldn't pair his archane BT headset with 206, I've port over some 172 BT drivers to 206 and my BT is still working the same for me. Perhaps someone else can experiment?

I mean, how do you tell the difference if there was none?

Hey, good news though. Sin is merging 206 and 202 ROM installation to have a more stable ROM. DrStein is experimenting with Widcomm Phone BT on XDA2 (porting from XDA2s I believe). I wish them great success!

Hi Henry!

Following you and SIN across several threads, You are the only two guys that got both BT problems solved under 2.02 and/or 2.06, How exactly?

No matter the combination -not registry tweaks yet- I am stuck with one or the other problems across the BT options: dual stereo mic, etc, No handsfree or No BT ActiveSync (2.20).

Any further help?
:cry:

[Looking Glass]

Thanks a lot Sin, will make another try.

In fact I tried installing the whole thing downloaded from the Logitech Site, but again it failed to install properly.

The BT in my laptop is factory built-in by Acer, and this is the annoying part, since Acer don't even provides an upgrade for it. In their site you can read: "Before installing XP SP 2, remove your BT drivers, and reinstall them after upgrading to SP 2", but the whole thing failed, and there were not way to get rid of the license message.

The Activesync problems only appeared after moving to 2.20.07 "translated", but it was the only way to solve the "dual-stereo" bug, so I feel mostly stuck: pick one of...

- No Hands free profile
- Dual Stero mic and earphone... or
- No BT Active Sync.

Take your bets ladies and gentelemen...

Will try with your drivers and help.

Regards.
:wink:

Perhaps you can try changing the 220 serial port DLL to the 206 serial port DLL ONLY. I reckon that can be done if you are careful to compare and port the settings.

Sorry to bother you again, Could you provide some instructions on that?
:wink:

[Rabia]

this is cools how can i make it work on my imate device?

[tumtum]

To Looking Glass

after i try flash and flash ROM around here (2.02t1, 2.06,1.72).
Only 1.72 and 2.06 can make my bluetooth headset work properly.
I try with Sin method to merge ROM. it still has problem (no sound on bluetooth mic).

But now, I can use my bluetooth.
The way to do is so simple.

First ,flash to ROM which you can use Bluetooth, pair your device and then, export registry from
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth.

Second, flash to ROM which you want to use (for me is 2.02t1 + 2.06), delete your registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth
and then import your registry from the first ROM.

Now, it work fine. I try in both 2.02t1 and 2.06.

[Looking Glass]

To tumtum:

Thanks for help.

I've tried your method, as explained by sin in other thread in the forum, and I've got the same results as the "pure" 2.o2t1 version, it is, "dual stereo": both mics and speakers in XDA and headset/handsfree WORK SIMULTANEOUSLY.

I`m actually making one more try with last sin version (packaged).

one more try...

Not there yet..

[tumtum]

To Looking Glass

Yesterday, I've flash my ROM down to 1.72 for test something and I export Bluetooth from ROM172 registry.

You can try to import it. It may help you about bluetooth issue.

Please backup you device before Import

[916senna]

To Looking Glass

Yesterday, I've flash my ROM down to 1.72 for test something and I export Bluetooth from ROM172 registry.

You can try to import it. It may help you about bluetooth issue.

Please backup you device before Import

:cry: I feel dumb asking this, but how do you you import part of the registry?
I can delete the existing bluetooth keys but cant work out how to insert the revised ones. :evil:
I cant just double click it and add it like in XP, If i try that it just loads the entire current reg in regedit.

I'm sure it will be obvious but I just cant work it out :?:

TIA

Jon

[Looking Glass]

To Looking Glass

Yesterday, I've flash my ROM down to 1.72 for test something and I export Bluetooth from ROM172 registry.

You can try to import it. It may help you about bluetooth issue.

Please backup you device before Import

Thanks for help, will keep trying.

BTW I've handled to install 2.20.07 CHS translated with the new "compact" ExtRom from Sin, with mixed results. Most things work OK, though there are programs that have support in files in the ExtRom that now are missing (WMP 10 Skins to name one of them).

The point here is that BT behaviour has changed, since you can now pair audio devices, but after a few seconds the headset icon in the top bar disappears. ??

Any help on wich files in ExtRom modify the way BT stack works? Maybe we can extract those from version 2.20.07 and made a combo over last Sin's made package.

Not there yet...
:wink:

[tumtum]

To Looking Glass

Yesterday, I've flash my ROM down to 1.72 for test something and I export Bluetooth from ROM172 registry.

You can try to import it. It may help you about bluetooth issue.

Please backup you device before Import

:cry: I feel dumb asking this, but how do you you import part of the registry?
I can delete the existing bluetooth keys but cant work out how to insert the revised ones. :evil:
I cant just double click it and add it like in XP, If i try that it just loads the entire current reg in regedit.

I'm sure it will be obvious but I just cant work it out :?:

TIA

Jon

You need to use some registry editor program such as resco
or PHM registry edit(freeware)

[Looking Glass]

To Looking Glass

Yesterday, I've flash my ROM down to 1.72 for test something and I export Bluetooth from ROM172 registry.

You can try to import it. It may help you about bluetooth issue.

Please backup you device before Import

Hi again!

I inspected the reg file you kindly sent, but I'm afraid I'm not sure wich keys are involved with the BT problems. I've read about BT profiles in other forums, and this largely exceeds my knowledge about BT, and since the whole set of options for the BT stack are too wide for a "trial and error" procedure, and flashing ROMs is such a time consumming job, it looks like it will be a never ending issue, unless someone comes out with a 2.20 WWE ROM for XDA II.

BTW I'm about to giving up on BT Active Sync with my laptop, since this is the "last" of my BT priorities as time being. Will return to IR Syncing meanwhile...

:? :(

[henrylim]

To Looking Glass

after i try flash and flash ROM around here (2.02t1, 2.06,1.72).
Only 1.72 and 2.06 can make my bluetooth headset work properly.
I try with Sin method to merge ROM. it still has problem (no sound on bluetooth mic).

But now, I can use my bluetooth.
The way to do is so simple.



Hi,

Just to clarify one thing. When you say "no sound on bluetooth mic", is that the HEADSET mode or HANDSFREEPROFILE mode?

I've friends who can't pair his BT headset on 2.06 ROM as well, and I've asked him to use 1.72 BT files to overwrite the 2.06 BT files. It seems to work for him as well.

[tumtum]

To Looking Glass

after i try flash and flash ROM around here (2.02t1, 2.06,1.72).
Only 1.72 and 2.06 can make my bluetooth headset work properly.
I try with Sin method to merge ROM. it still has problem (no sound on bluetooth mic).

But now, I can use my bluetooth.
The way to do is so simple.



Hi,

Just to clarify one thing. When you say "no sound on bluetooth mic", is that the HEADSET mode or HANDSFREEPROFILE mode?

I've friends who can't pair his BT headset on 2.06 ROM as well, and I've asked him to use 1.72 BT files to overwrite the 2.06 BT files. It seems to work for him as well.

Ok

No sound on bluetooth mic occur in
- ROM 2.02t1 in both HandsfreeProfile and Headset Profile
- ROM 2.06 + 2.02t1 (merge ROM) in both Handsfree and Headset

I think some registry ot bluetooth in ROM 2.02t1 is not work correctly for Bluetooth Headset.

In ROM 2.06 and 1.72, Bluetooth work well in Headset mode, but in HandsfreeProfile is not work.

To solve Problem, I export bluetooth registry from 2.065 and 1.72 and then, import TO ROM 2.06+2.02t1. Then Bluetooth is work well in Headset mode (Not in HandsfreeProfile---->no sound bluetooth mic)

But it has some problems.
In Bluetooth registry from 2.06, After I import it, everytime I turn on my device. Blue light is blinking without bluetooth-on ,but Headset is work well.
The second problem, when you have an incoming call, Bluetooth headset is delayed for 2 second.

In Bluetooth registry from 1.72, It work fine.
No blue light blink when turn on and no delay whern has incoming call.
I didn't try Bluetooth activesync because I don't have it.

My conclusion, Bluetooth registry from ROM 1.72 work perfectly for Bluetooth Headset in Headset Mode.

[tumtum]

To Henrylim

As far as I know, XDA2 doesn't support Handsfree profile.
It has written on FAQ page from O2 website about Bluetooth issue.

It should be the reason why no sound on mic of bluetooth in Handsfree Profile.

[henrylim]

To Henrylim

As far as I know, XDA2 doesn't support Handsfree profile.
It has written on FAQ page from O2 website about Bluetooth issue.

It should be the reason why no sound on mic of bluetooth in Handsfree Profile.

Hi,

I read that many moons ago, in 1.03ROM, there was the handsfree.exe that supports handsfree profile. Then, there was upgrade which makes the implementation goes to Handsfree_Dll.dll, which change the Mic to External Speaker.

Anyone tried the handsfree with Handsfree.exe instead of Handsfree_Dll.dll???

[Looking Glass]

To Henrylim

As far as I know, XDA2 doesn't support Handsfree profile.
It has written on FAQ page from O2 website about Bluetooth issue.

It should be the reason why no sound on mic of bluetooth in Handsfree Profile.

Hi,

I read that many moons ago, in 1.03ROM, there was the handsfree.exe that supports handsfree profile. Then, there was upgrade which makes the implementation goes to Handsfree_Dll.dll, which change the Mic to External Speaker.

Anyone tried the handsfree with Handsfree.exe instead of Handsfree_Dll.dll???

AFAIK version 1.03 DID NOT support handsfree profile at all (My Qtek 2020 arrived with that version to me) It only worked with Headsets.

Headsets have been working OK (to me HBH 30, HBH 35) with all versions until the arrival of SE (2.XX ROMs). ONLY version 2.20 fully and correctly works with both, Headsets and Handsfree profiles devices, but at the cost of no ActiveSync BT and the rest of the missing things)

Until a 2.20 WWE ROM arrives, the non-chinese speakers are out of luck.

:?

Not there yet...

[Rolex]

Hi guys,
Has anyone tried this new PATCH:
Broadcom Bluetooth "upgrade" for i-mate PDA2K

In Mysteryman/Fianlzero RoM(2.06.00WWE)?

Here the link:http://www.ppcw.net/?itemid=2210#cmt9554

[henrylim]

To Henrylim

As far as I know, XDA2 doesn't support Handsfree profile.
It has written on FAQ page from O2 website about Bluetooth issue.

It should be the reason why no sound on mic of bluetooth in Handsfree Profile.

It doesn't support handsfree profile, true. But I found the files and reg settings in 2.20, and then in 1.72!

Anyway, I've attached the registry settings for 2.06 for the guys with 2.20CHS guys to test the registry settings.

BUT remember to backup before you try it!

[henrylim]

upz!

anybody got ActiveSync working for 2.20CHS???

Got the feeling that perhaps we have to concentrate our efforts to enable 2.20 since it seems to have a few defects to correct before we get all what we wanted......oh well...just a thot..

[unapproachable2kx]

No,it dosn't work with your reg and dll modifications.

[Looking Glass]

Just for info:

I've been able to push files via BT from my 2.20 ROM to my laptop, (Pairing was Ok, etc), but not ActiveSyncing. So it seems we are quite close, though...

[henrylim]

No,it dosn't work with your reg and dll modifications.

thanks for the feedback. Ok, confirm that it is something more than reg and dll then. I will point the culprit at the activesync module in 220...

[egtan]

Sorry if this is a stupid suggestion on my part.... but has anyone tried BTTools to solve your Bluetooth Activesync problems?

http://www.bluetooth.jazztel.es/

I'm using ROM 2.06 WWE and I couldn't activesync on bluetooth at first but after installing BTTools, all my problems were solved.... Only thing I really miss is that BTTools doesn't support Bluetooth Network Connections. I used to access my LAN through my Bluetooth to my desktop PC where I had bridged my Bluetooth Network with my LAN connection.

[unapproachable2kx]

of course it doesnt solve.

[xda2_user]

of course it doesnt solve.

After I saw what the XDAIIs can do, I immediately looked for an upgrade for my XDAII. I find the XDAIIs much faster than mine so I began my quest. Luckily I enountered this site and learned a great deal in upgrading my unit. I had a few hiccups but overall it was successful.

Performance wise I would say that my start menu became a lot faster than it used to be when I was still using 1.66.00WWE. I have less hang times now after upgrading to 2.06WWE. However, every now and then I still encounter some programs slowing down. Hey it's part of the windows family what do you expect.

I read so many BT problems in this forum so I got curious and tried it myself. I'm using a BT dongle from MSI. I was able to pair the XDAII w/ my PC but activesync still couldn't recognize the device. Btw, I'm using Activesync 3.8. I was originally using BTTools 1.1.0.0 and tried selecting activesync and serial port in different occassions and still couldn't get it working. Finally, I ran out of combinations to test so I uninstalled BTTools and whalla! It worked!!! Now I can do BT Activesync w/ my XDAII.

Before I got rid of the BTTools I couldn't see the "Connect via bluetooth" option in my XDAII. But after uninstalling the program and repeating the instruction below, I was able to get the "Connect via bluetooth" option.

I tried to re-install BTTools again knowing that I can already do Activesync via BT, unfortunately the option disappeared again. So I had to choose between BT activesync or automatic BT activation for headsets. Since I don't have a BT headset yet, I chose option 1.

I followed this site in configuring my device:
http://www.geekzone.co.nz/content.asp?contentid=2417

Next experiment: XDAII w/ BT headset.

[victoradjei]

Henrylim

Following the instructions above I have been able to active sync my device using Fujitech bluetooth dongle installed on windows xp sp1.
Am also using bt headset HBH 65. Only problem is call is cut off bt when device turns off.

Will try syncing with xp sp2 when I go home.

cheers

Henrylim

Following the instructions above I have been able to active sync my device using Fujitech bluetooth dongle installed on windows xp sp1.
Am also using bt headset HBH 65. Only problem is call is cut off bt when device turns off.

Will try syncing with xp sp2 when I go home.

cheers

Please inform of the result.
Be carefull, I had to revert my Notebook to factory status (formatting hard drive) to get my BT back to work, since SP2 unsinstalls Widcomm dirvers, and there is NO WAY BACK! Even system Restore (XP) failed!

Good Luck!

[victoradjei]

xp sp2 did not allow the install of driver for the dongle. Removed the default and tricked system but to no good result.

[tuanmai]

<<<[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001 >>>

I think this one indicates the headset mode disabled/enabled.

"ON=1": enabled
"ON=0" : disabled,


That's all

:?: :?: :?:

[davidong328]

Hi,

Can anyone attached a copy of resco or PHM registry edit(freeware) so that I can import the registry file. I am having the same problem with my BT 'There is no Bluetooth hardware installed on this device' error. I am using a XDA II with 2003 SE. Can I use the attached registry (bluetooth172.rar)?

[edsub]

Can anyone try to post the 2.20 version of "BTSPP.dll" or is this dll also xip"protected"??

[Valyo]

Here you go...

[davidong328]

Sorry, I am not too good in this. What should I do with the .dll? Where should I copy it to?