Related
Looks like ID64 has provided it for us. The bluetooth files are located on his FTP server at
ftp://akira:[email protected]
File Name 6315BT.zip
Please.. Who ever did the Bluetooth GPS... Help us out.. this is the phone edition widcomm stack and will/should work with the BT headset during phone calls.
How can I install this application?
Can't install, needs's developing
You can't install this application yet. This is out there for those who made the Bluetooth GPS work with the Widcomm stack.
We need someone out there to work with the old BluetoothGPS (original Widcomm solution) and work with these new files. We'll have a better bluetooth stack than the MS Stack.
So.. In short, this message is out there to attract the developers.
Maybe it's possible.
Maybe if someone still has Bluetooth GPS and can install it.. Then if they copy over these files on top of it, it will work.
Does anyone have the original BluetoothGPS.zip?
The files are fine, but there is no included registry settings.
We need more info
(an export of the whole registry would be a good idea)
Surur
WIDCOMM BT-PPC/PE 1.0.0 Build 1400
Compared file for file in kind between BlueTooth GPS and the WIDCOMM BT-PPC/PE 1.0.0 Build 1400 generally the later are leaner in terms of size.
The former however has more *.dll(s) - probably being an older version.
I have consolidated a list of files BTGPS installed in Xda II but was unable to make a copy but I shall try other ways to later.
After a full backup I plan to dump the WIDCOMM BT-PPC/PE 1.0.0 Build 1400 files over the BTGPS. Filenames seem to have been kept intact betweeen the two versions so hopefully the registry will not get screwed.
Registry is there
Someone has uploaded the registry. This should help
WIDCOMM BT-PPC/PE 1.0.0 Build 1400
Overwritten BlueToothGPS with WIDCOMM BT-PPC/PE 1.0.0 Build 1400 without problems but unable to initialize BlueTooth.
Will try to update registry later tonight.
Hello: I got it sorted and have put it on a new thread....
http://forum.xda-developers.com/viewtopic.php?p=57567#57567
WIDCOMM BT-PPC/PE 1.0.0 Build 1400
Good job icarusbop!
I already had BlueTooth GPS installed and running ok for a long time. Went on to overwrite it with the 6315BT files from the FTP server earlier but BlueTooth was unable to initialize.
Found out the BTTrayCE 1.0.0.1400 was not compatible somehow and causing conflict. Replaced it with the older BlueTooth GPS version and everything worked out fine. Nothing was done to my registry no changes was necessary - the old BlueTooth GPS registry was still holding up.
I may try your 1.4.1.59/60 if I run into problems. Thanks Bro.
P/S : This stack initializes very fast, no initialization or hardware errors, no incompatibilty issues with MS stack and very stable - left to test is the headset option.
Re: WIDCOMM BT-PPC/PE 1.0.0 Build 1400
Would you mind explaining step by step how did you do your setup... Just curious... Do you have problem using your headset? Have you tried it yet... ? Thanks!
[Krueger said:
Dr.Stein]Good job icarusbop!
I already had BlueTooth GPS installed and running ok for a long time. Went on to overwrite it with the 6315BT files from the FTP server earlier but BlueTooth was unable to initialize.
Found out the BTTrayCE 1.0.0.1400 was not compatible somehow and causing conflict. Replaced it with the older BlueTooth GPS version and everything worked out fine. Nothing was done to my registry no changes was necessary - the old BlueTooth GPS registry was still holding up.
I may try your 1.4.1.59/60 if I run into problems. Thanks Bro.
P/S : This stack initializes very fast, no initialization or hardware errors, no incompatibilty issues with MS stack and very stable - left to test is the headset option.
Click to expand...
Click to collapse
Steps
Not at all Bro. Well to begin with as I have mentioned I already had BlueTooth GPS installed.
I downloaded the 6315BT zip file from the FTP server extracted the files and plonked them over the BTGPS files in my Xda II. There were several files that needed to be renamed in order to overwrite completely - renamed files can later be deleted after reset - BTTrayCE.exe file should be skipped as I found the new version conflicts with Xda II MS stack.
As for the headset I have yet to test as I do not own one. Been hoping to get one but I haven't had the time to do so. Sorry.
I will see if anyone at work has a headset and give it a whirl.
Good Job!
OMFG
Where are my manners? Forgotten to thank NeoCole and ID64!
Thanks guys - NeoCole and ID64 - you guys rulez!
Re: Steps
Thanks for your reply Bro.... I have another question, Do you have two BT icon on the bottom-right of your screen or MS-BT icon goes away?
Thanks!
[Krueger said:
Dr.Stein]Not at all Bro. Well to begin with as I have mentioned I already had BlueTooth GPS installed.
I downloaded the 6315BT zip file from the FTP server extracted the files and plonked them over the BTGPS files in my Xda II. There were several files that needed to be renamed in order to overwrite completely - renamed files can later be deleted after reset - BTTrayCE.exe file should be skipped as I found the new version conflicts with Xda II MS stack.
As for the headset I have yet to test as I do not own one. Been hoping to get one but I haven't had the time to do so. Sorry.
I will see if anyone at work has a headset and give it a whirl.
Click to expand...
Click to collapse
Re: Steps
superperry said:
Thanks for your reply Bro.... I have another question, Do you have two BT icon on the bottom-right of your screen or MS-BT icon goes away?
Thanks!
Click to expand...
Click to collapse
No sweat Bro. Anytime Man.
There are still two - the same with BlueTooth GPS. Both works perfectly but individually.
Do you have the problem with "cant initialize" after softresetting, or does it just work perfectly?
Surur
Initialization
surur said:
Do you have the problem with "cant initialize" after softresetting, or does it just work perfectly?
Surur
Click to expand...
Click to collapse
No initialization problem since installation and startup yesterday. So far so good - yes even after several soft resets and wake after long standby time still no errors. Yeah I would say it's been working perfectly Bro.
Re: Steps
[Krueger said:
Dr.Stein]Not at all Bro. Well to begin with as I have mentioned I already had BlueTooth GPS installed.
I downloaded the 6315BT zip file from the FTP server extracted the files and plonked them over the BTGPS files in my Xda II. There were several files that needed to be renamed in order to overwrite completely - renamed files can later be deleted after reset - BTTrayCE.exe file should be skipped as I found the new version conflicts with Xda II MS stack.
As for the headset I have yet to test as I do not own one. Been hoping to get one but I haven't had the time to do so. Sorry.
I will see if anyone at work has a headset and give it a whirl.
Click to expand...
Click to collapse
What files should be renamed? Could you please tell me?
Re: Steps
ID64 said:
What files should be renamed? Could you please tell me?
Click to expand...
Click to collapse
Sorry. The truth is I didn't take note Bro. I renamed one by one as the copying process prompted that the files are in ROM. You can do the same. A post by mamaich has named a few of these files that needs to be renamed.
An easier solution would be to use icarusbop's 1.4.1.59/60 upgrade.
Please note that mine is only the BlueTooth GPS upgrade to WIDCOMM BT-PPC/PE 1.0.0 Build 1400 whereas mamaich's and icarusbop's is from 1.4.1.59/60 to WIDCOMM BT-PPC/PE 1.0.0 Build 1400. Theirs would be a better and newer version.
Here are screenshots of the WIDCOMM BT-PPC/PE 1.0.0 Build 1400 that I have installed.
Hi all, I was asking about if this BT solution has somenthing to do with Qtek2020 problem with BT headset and BT car kit management. I mean if I'd install BT Widcomm Bt Stack and 6315BT.zip, could I use both togheter?
Thanx a lot!
We currently have 3 NK.nbf WM2003SE ROMs to play with and I've stumbled on a way to create a better version out of the 2 English ones:
2.02.t1WWE : 4.21.1088 (Build 14132)
PROS:
Stable - no reboot hangs or delays
The faster of the English versions
BT Handsfree - allows the Handsfree profile to be activated
CONS:
ClearType - not worth using in this version
BT Handsfree - early version, can disable radio randomly. Blocks activesync when activated and if Handsfree mode isn't enabled, Headset mode won't work.
BT Profile - plays hide'n'seek
Newer "Outlook integrated" MMS clients not sending/receiving correctly
No Media Player 10
2.06.00WWE : 4.21.1088 (Build 14132)
PROS:
ClearType - looks and works great
BT Headset - no handsfree option but works seamlessly with activesync
CONS:
Unstable - can lock-up in OS & suffers hangs/delays on reboot
BT Profile - plays hide'n'seek
Newer "Outlook integrated" MMS clients not sending/receiving correctly
No Media Player 10
:!: NOTE: This is only my experience of the above and you may not have experienced any/some of the above
Combining ROM's
By first flashing with the 2.02.t1WWE ROM (& 1.18.00 Radio + Extended ROM), then setting up BT and detecting all devices but before adding additional software, I ran an activesync backup. The reason I used activesync was to capture the registry and system state but not an image of the whole ROM.
I then flashed with the 2.06.00WWE ROM + 1.18.00 Radio & Extended ROM, but this time I restored from the activesync backup. Rather than what I expected (everything good about 2.06 to be blown away), activesync restore did a merge of the 2 registries and overwrote the files not in use.
The end result came as a surprise:
I now have a version 2.06.00WWE that doesn't hang/delay on reboot, runs faster, looks great with cleartype and now has BT Handsfree as an option. Handsfree works great, though still blocks activesync via BT (a reboot auto disables it) but it doesn't interfere with the radio now.
Are you sure they didn't just rename BT Handsfree in 2.02t1WWE to BT Headset in 2.06.00WWE? (same functionality, just no menu option in the later)
The reason I'm posting this, is not to produce a backup file for installation, but to give those of us playing around with the ROMS's food for thought.
I'm curious what would happen if someone installed an English version, deleted Media player 9 & it's registry as much as possible, then backed up. Then installed the Chinese version (2.20.07CHS with Media Player 10) and restored the original backup over it.
Would you end up with a combined Chinese version in English with Media Player 10?
(Before you ask why I don't try it myself - I need a break so I'm going back to work :wink: )
Man!
it seems working for me also now i have 2.02 stability with 2.06 advantages (i.e clear type).
one thing,,, how did you think about it? i mean it is always advised to avoid restoring from different ROM!
thanx man :wink:
how do you restore from activesync? after a reflash, the partnership is removed right?
can you guys post step by step? thanks
Yup this is true... just folow there steps...
http://forum.xda-developers.com/viewtopic.php?t=14240
I would love to try this but pardon my ignorance but correct me if i'm wrong.... isn't it when you do a hard reset or ROM/extROM upgrade you loose partnership with activesynch? I had this problem eversince that's why i use sprite backup. How do you restore from activesynch after loosing partnership?
The steps are outlined here, but you'll have to obtain the correct ROM's to suit your region, model & carrier.
Can we have both registries posted here?
Hi Sin,
Can you posted the vanilia registries of 2.02 and 2.06 ROM?
I will love to check the difference between both ROMs and make a stable ROM by adding registry changes after the upgrade. Many thanks.
Re: Can we have both registries posted here?
Sorry, I missed your request. Here's a link to one I posted today.
Sin said:
The reason I'm posting this, is not to produce a backup file for installation, but to give those of us playing around with the ROMS's food for thought.
I'm curious what would happen if someone installed an English version, deleted Media player 9 & it's registry as much as possible, then backed up. Then installed the Chinese version (2.20.07CHS with Media Player 10) and restored the original backup over it.
Would you end up with a combined Chinese version in English with Media Player 10?
(Before you ask why I don't try it myself - I need a break so I'm going back to work :wink: )
Click to expand...
Click to collapse
Sin,
Have you try this process? And if you did what was the result? I am just curious. (I don't have enough knowledge to do this, that's why I asked)
Thanks!
Can you tell me what is the use of these file... can i delete it?
CprogHook.WM2003_2577.CAB
OEM_CHS_OU_04110301.sa.CAB
Version_OU.sa.CAB
Is it safe to delete those files? Tnx
removed those from my ext rom... but i do have version_BA
Can u tell me whats the diff about this two files:
Version_OU.sa.CAB
and
version_BA
Tnx again..
I honestly dont know dude.... but my EXT rom says it is 1.12.924.wwe
maybe in your case it states 2.02? can you send me the file or attach it here and I'll try it
TIA
double_ofour said:
Can u tell me whats the diff about this two files:
Version_OU.sa.CAB
and
version_BA
Tnx again..
Click to expand...
Click to collapse
version_BA = 1.12.924
Version_OU.sa.CAB = 2.06.100a
:arrow: ExtendedROM versions ( chose 1 you indulge )
CprogHook.WM2003_2577.CAB = mamaich contacts extension ( useful! )
OEM_CHS_OU_04110301.sa.CAB = additional configuration for chinese version = safe to delete in english ROMS
Yup.. yup.. yup.. maybe thats the thing... cuz when i used the DCS ExtROM with Version_OU it says that my ExtROM is 2.06.100a and when i installed the ExtROM asian Version provided by one of our kabayan.. with version_BA it says that my ExtROM are now 1.something.something... but anyway heres the file.
And one thing... what is the use of:
tFlashMan.exe
NFlashman.exe
CFlashman.exe
AFlashman.exe
Cuz when i deleted those files... my device increased a bit of speed when reset...
again.. is it safe to delete those files? Thanx again...
those flashman..... are for permanent save applet....
I dont use permanent save.... so I deleted those four flashmen
double_ofour said:
Yup.. yup.. yup.. maybe thats the thing... cuz when i used the DCS ExtROM with Version_OU it says that my ExtROM is 2.06.100a and when i installed the ExtROM asian Version provided by one of our kabayan.. with version_BA it says that my ExtROM are now 1.something.something... but anyway heres the file.
And one thing... what is the use of:
tFlashMan.exe
NFlashman.exe
CFlashman.exe
AFlashman.exe
Cuz when i deleted those files... my device increased a bit of speed when reset...
again.. is it safe to delete those files? Thanx again...
Click to expand...
Click to collapse
tFlashMan.exe
NFlashman.exe
CFlashman.exe
AFlashman.exe
:arrow: PPC flash player manager files for playing animated plug-ins ( Animatedtoday, flashdash, etc...)
delete if you wont be using those "moving" thingy which S-L-O-W-S your fone big time..
TTFN kabayan....
yes its also used by permanent save thingy... :wink:
yep.. its for setting the version
Yeah... now i've got WM2003SE 2.06WWE more faster and very stable... i've just followed these steps...
===========================================
Posted by Sin:
By first flashing with the 2.02.t1WWE ROM (& 1.18.00 Radio + Extended ROM), then setting up BT and detecting all devices but before adding additional software, I ran an ActiveSync backup. The reason I used ActiveSync was to capture the registry and system state but not an image of the whole ROM.
I then flashed with the 2.06.00WWE ROM + 1.18.00 Radio & Extended ROM, but this time I restored from the ActiveSync backup. Rather than what I expected (everything good about 2.06 to be blown away), ActiveSync restore did a merge of the 2 registries and overwrote the files not in use.
The end result came as a surprise:
I now have a version 2.06.00WWE that doesn't hang/delay on reboot, runs faster, looks great with cleartype and now has BT Handsfree as an option. Handsfree works great, though still blocks ActiveSync via BT (a reboot auto disables it) but it doesn't interfere with the radio now.
Are you sure they didn't just rename BT Handsfree in 2.02t1WWE to BT Headset in 2.06.00WWE? (same functionality, just no menu option in the later)
The reason I'm posting this, is not to produce a backup file for installation, but to give those of us playing around with the ROMS's food for thought.
I'm curious what would happen if someone installed an English version, deleted Media player 9 & it's registry as much as possible, then backed up. Then installed the Chinese version (2.20.07CHS with Media Player 10) and restored the original backup over it.
Would you end up with a combined Chinese version in English with Media Player 10?
(Before you ask why I don't try it myself - I need a break so I'm going back to work )
Source: http://forum.xda-developers.com/viewtopic.php?t=14227
===========================================
and if your not using the flashmans files then delete those flashmans file on startup... now ive left in my startup are the "CheckAutoRun, ChgDfLnk, IA_Caller_ID, poutlok, RegNotify, stk" and makes your PPC fast. Try it...
Just install the 2.02 WM2003SE DCS Rom then use activesync backup.. (Dont install anything after the 2.02 was installed just backup after upgraded to 2.02) after the activesync backup were completed reflash again, use the 2.06 WM2003SE Mamaich Rom then Restore the backuped files from activesync... then delete those flashmans... then VOILA!!!
Result: Fast and Stable, For me no hangs for reboot fast load when reboot and more stable... (For me... i dont know for you...)
Just try...
mines working the way i want it ( no hangs etc ) for more than a week now...got tired on reflashing and flashing...im testing the whole phone to the extreme ( calls, texts, games, movies, etc ) since the last time i flash and so far, its quite stable...
the reason : i just streamlined the today plugins to the one designed to run on SE ( RhinoCode plugins ) , thou i got a near-full ExtendedROm with extended-extended ROm ( \storage ), i dont even get unplanned soft resets till now... :wink:
this is my experience so far....
double_ofour said:
Yeah... now i've got WM2003SE 2.06WWE more faster and very stable... i've just followed these steps...
===========================================
Posted by Sin:
By first flashing with the 2.02.t1WWE ROM (& 1.18.00 Radio + Extended ROM), then setting up BT and detecting all devices but before adding additional software, I ran an ActiveSync backup. The reason I used ActiveSync was to capture the registry and system state but not an image of the whole ROM.
I then flashed with the 2.06.00WWE ROM + 1.18.00 Radio & Extended ROM, but this time I restored from the ActiveSync backup. Rather than what I expected (everything good about 2.06 to be blown away), ActiveSync restore did a merge of the 2 registries and overwrote the files not in use.
Click to expand...
Click to collapse
Perhaps you can upload both registries so we can do a comparison to see what is the difference between the 2 registries. Worth the check, if it does solve a few problems for those installed with either 2.02 or 2.06 ROM.
regards,
Henry
err, i wouldn't delete those "flashman" applications, as they're not from, lol, shockwave flash player.. those are there to detect inserted SD/MMC/CF cards as far as i know...
my 2 €urocents
double_ofour said:
By first flashing with the 2.02.t1WWE ROM (& 1.18.00 Radio + Extended ROM), then setting up BT and detecting all devices but before adding additional software, I ran an ActiveSync backup. The reason I used ActiveSync was to capture the registry and system state but not an image of the whole ROM.
Click to expand...
Click to collapse
Please, can you upload one Backup.stg file from 2.02?
dutty... dont worry, i deleted them flashmen..... my sd card still works..
if you have doubts, relocate them to a new folder and test the xda
[quote="henrylim
Perhaps you can upload both registries so we can do a comparison to see what is the difference between the 2 registries. Worth the check, if it does solve a few problems for those installed with either 2.02 or 2.06 ROM.
regards,
Henry[/quote]
Interestingly enough, there's a posting that suggests that there is actual difference in the registry settings of 2.06 versus 2.02 ROM...
http://forum.xda-developers.com/viewtopic.php?t=13820&highlight=
Perhaps we should pursure the registry differences between the 2 if it does make our ROM more stable?
for stable Radio signal strength
i managed to gain additional bar of Radio signal strength here in Pi. How? read and download the radio stack here . Thanks to Zman for trying... :wink:
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\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
"BTDUN.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
"BTSPP.dll"=dword:00000000
"Default"="Active Sync"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
"BTSPP.dll"=dword:00000000
"Default"="Serial Port"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\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\Services\0000111E-0000-1000-8000-00805F9B34FB]
"btagsvc.dll"=dword:00000000
@="Handsfree"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"btagsvc.dll"=dword:00000000
"headset"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BthASPlugIn.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\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\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAudioModule"="OEMExtDll.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Settings]
"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?
[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\AudioGateway]
"BTAudioModule"="OEMExtDll.dll"
This above not in 2.2
& also in 2.2
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
@="Handsfree"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
"BTDUN.dll"=dword:00000000
About BTProfile...
darren_the said:
[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001
Click to expand...
Click to collapse
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.
Anyone has ideas why this is so?
darren_the said:
& also in 2.2
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
@="Handsfree"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
"BTDUN.dll"=dword:00000000
Click to expand...
Click to collapse
Yes, essentially the same thing that I found out. See the Services serial numbers, it's identical.
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:
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
henrylim said:
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\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
"BTDUN.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
"BTSPP.dll"=dword:00000000
"Default"="Active Sync"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
"BTSPP.dll"=dword:00000000
"Default"="Serial Port"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\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\Services\0000111E-0000-1000-8000-00805F9B34FB]
"btagsvc.dll"=dword:00000000
@="Handsfree"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"btagsvc.dll"=dword:00000000
"headset"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BthASPlugIn.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\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\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAudioModule"="OEMExtDll.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Settings]
"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?
Click to expand...
Click to collapse
can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working
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.
mmmmmmm
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.
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
[quote="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[/quote]
Here it is.
problems with BT in all SE upgrades
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.
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
henrylim said:
[quote="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
Click to expand...
Click to collapse
Here it is.[/quote]
thanks man but looks harder than i thought could you post your registery file, are you 2.20 chs?
Re: problems with BT in all SE upgrades
steverae said:
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.
Click to expand...
Click to collapse
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
Not there yet...
Re: problems with BT in all SE upgrades
steverae said:
2) BT Activesync does not work end of story
Click to expand...
Click to collapse
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?
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
Rabia said:
henrylim said:
[quote="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
Click to expand...
Click to collapse
Here it is.
Click to expand...
Click to collapse
thanks man but looks harder than i thought could you post your registery file, are you 2.20 chs?[/quote]
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?
Re: problems with BT in all SE upgrades
henrylim said:
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?
Click to expand...
Click to collapse
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!
ACTIVESYNC BT WOES...
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?
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.
widcomm drivers
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!
Re: widcomm drivers
Looking Glass said:
They don't even have SW upgrades in their web site!
Click to expand...
Click to collapse
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:
Thanks
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:
I have upgraded my OS from 1.23 to 2.06 (cingular OS only, no extROM).
Voice Command 1.5 installs properly but gives an error when launched
Voice Command 1.6 refuses to install at all
Both versions of VoiceCommand are French not US (though you would need to know that )
I have tried to do that just after a hard reset not to be polluted by my other apps, but I have the same result
I have tried with and without the "allow non-certified applications" flag from HTC tweak 2.0. Same result...
I got 1.5 to work on this os after a sprite restore with sbu from OS1.23, but the PIM database was corrupted. So I had to restore without it and get it back from ActivSynch. I do not think there should be a relationship between the 2 however...
1.5 was working after the twicks to remove Speed Dial as indicated on the Wiki (but with corruped PIM database)
But since I have a clean PIM database, no way to get Voice Command to work despite desinstall, clean any trace of it in the registeries and reinstall...
Any hints from the experts on the group?
That would be much appreciated as I am running out of ideas to try!
Odd,
It worked for me. Of course, knowing me I probably copied the CAB down to the device over USB and ran it there.
Of course, I'm using the english version since all the people I know have english names (joke).
Rob
I did try to install it thru a cab execution on the device as I do usualy (I like to keep all the cabs for easy reinstall if necessary)
Any hint why I get an exec error on 1.5? I would stick to it if it worked as I found some ways to get it to work with BT
Try setting all parameters in the regional settings to US. then reinstall. revert afterwards to French settings.
I have come across an other Microsoft product which needed US settings.
Simple.
Cingular OS2.06 is AKU3 = No VC1.5
MS Voice Command v1.5 will NOT work on AKU 3.x ROMs; VC v1.6 should work (does for me with Cingular 8500 w/OS 2.06)
Good Luck!
Cingular 8500
OS 2.06
Radio 1.27
drbowden said:
MS Voice Command v1.5 will NOT work on AKU 3.x ROMs; VC v1.6 should work (does for me with Cingular 8500 w/OS 2.06)
Good Luck!
Cingular 8500
OS 2.06
Radio 1.27
Click to expand...
Click to collapse
I second that! 1.5 would not work at all. Only 1.6 did on the latest Cingular AKU 3.3 ROM.