Related
hey, searched the forum a bit but there is no real answer to this one..
where can i get the widcomm btstack for 2003se. i'm using 1.5.0.0801 from mamaich but it's not working properly..
edit: not working correctly meaning freezing today screen items like CT PLUS, spb plus. sometimes freezing entire ppc, start menu not accesible etc..
my widcomm stack 1.5.0.0801 is not conflicting with other apps ( spb apps, etc. ) but always display "could not be correctly initialized " when other apps is opened. we all know that widcomm stack is memory hogger..i think there is a .reg patch to apply to make it more stable in SE..
i have the same probs as dutty
Widcomm BT 1.5
Hi Guys!
First of all:
Copy all the BT files to windows directory, then place the BTCE in windows\startup
Second:
Use the regeditor and delete the HKLM\Software\Microsoft\Bluetooth
Use the reeditor and delete de HKLU\Software\Microsoft\Bluetooth
soft-reset the pda...and that's all folks!!! the bt works like a charm, you can put the BT in "ON" and soft-reset your device that it connects again without problems!!
Sorry....
I forgot to say that you must run the file with the reg settings that exists in this forum.
errr cant find it (the reg) ^^
Here it goes....
Well... i'm sending in attach the file.
Cheers!
Sorry....
I forgot the file...
well, thx for the reg, but same prob as before
mbsb0812 Posted: Tue Dec 07, 2004 06:25 Post subject: Widcomm BT 1.5
--------------------------------------------------------------------------------
Hi Guys!
Copy all the BT files to windows directory, then place the BTCE in windows\startup
Second:
Use the regeditor and delete the HKLM\Software\Microsoft\Bluetooth
Use the reeditor and delete de HKLU\Software\Microsoft\Bluetooth
soft-reset the pda...and that's all folks!!! the bt works like a charm, you can put the BT in "ON" and soft-reset your device that it connects again without problems!!
=========================
i already did that procedures before and my BT stack is working but as i said, it intermitently flashes " could not be initialized" when you opened an app, said internet explorer. it seems to hog all of my memory...i reckon a .reg patch to prevent it. ( just forget where.. )
PS.
upon applying that .reg. you should run this patch for the sound to run well..
[/quote]
where is the widcomm software itself since we already have the registry patch?
thanks
tried on the MDA Compact, doesn't run (same thing for the 1.4.59).
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!
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:
tomtom is the only thing stopping me for to go to magneto
i tried it for a while its nice but i need my tomtom
if you know a way for using it ?
please no other soft sugestions because for the moment
my budget is to low for buying something new
TomTom 4.40 is working perfect under WM 5
TomTom3 + Magneto
Hi,
when i try to install TT4.4 the installer crashes!
What can i do about that?
best regards!
Re: TomTom3 + Magneto
Dodger said:
Hi,
when i try to install TT4.4 the installer crashes!
What can i do about that?
best regards!
Click to expand...
Click to collapse
I was also having the same trouble with the installer. Setup.exe kept on crashing. So I resorted to installing the program off the pda.
What you need to do is copy the following files to the pda:
wzd.cab
voice.cab
ttn.cab
gps.cab
Then run each one off the pda and the program should then be installed.
To install the maps just go through the setup to install it onto the storage card.
Oh and if you encounter the backlight problem whilst running Tomtom then you will need to press the "Red Disconnect Call Button" so it can be minimized, you will then need to go into the backlight settings and readjust them accordingly.
Good Luck!
when instal 4.40 i wont take my key
any suggestions ?
yeah, you could buy it instead.
any solution for backlight problem with tomtom 4.40 ?
Problem of backlight
Explore Cd Tomtom 4.40 to go in the folder voice then to take the files voice04.cab and voice05.cab (are the English voices UK) Initially to put it to Program Files for example then to launch the cab since to this folder (Program Files) in your pocket PC
Voice11 and Voices12 (are the french voices)
This procedure corrects the problem of backlight
what do you mean ?
if you install a voice the backlight problem is gone ?
In my case that corrected the problem
I had this problem of backlight
During installation of files wzd.cab ttn.cab gps.cab
and for my part after to have installed the file voice 11 and Voice 12 .cab (women and men french voices) the backlight error disappeared
That was the good solution in my case
The backlight is automatically returned and work good after voice.cab installation
So I suppose that the 4 cab files describes above must be all present so that tomtom 4.40 run correctly
But it's not the same problem for everyone
Dutch Voice Cab files
Hi everone,
Does anybody knows the numbers of the dutch voice.cabs.
:?:
Greeting from holland
Re: Dutch Voice Cab files
[email protected] said:
Hi everone,
Does anybody knows the numbers of the dutch voice.cabs.
:?:
Click to expand...
Click to collapse
can someone upload one ? or a download link :roll:
TomTom 4.4 filestructure
Hi,
First: thanks Nightspider and Dherrero for your tips!
it's hard working, but thanks to your tips TomTom 4.4 is beginning to work
on my XDAII.
I had to put the Benelux.CAB on the Storagecard. Only then it would install.
But I've ran into another problem, it says now "no maps found"
I suspect this have to do with the name and/or the place where you put
the directory with the maps. Can anyone who has a working TomTom 4.4
tell me the exact names of the directory, where the are and what files are in them?
TIA
Re: Dutch Voice Cab files
Hi Everyone,
When you want Dutch language you need to install the following cabs
voice14.cab = "Bram" a male voice
voice15.cab = "Eva" a female voice
voice16.cab = "Nora" i think (not tested)
Now the problem is where to put the Benelux map.
Greetings [email protected]
TomTom 4 Benelux map
I've found it!
Put the Beneluxmap in \Storage Card\.
During executing Beneluc.cab it was stored on
\Storage Card\My Documents\Benelux.
So you have to put the Benelux map in the root of Storage card!
TomTom 4 activation
Damn, now the bloody thing is asking for the activationcode.
Anyone?
TomTom 4 activation
Thanks for the solution.
I installed the map with a cardreader.
Works as wel
But i get the same activation problem
TomTom 4.40
Sorry,but 4.40 tom tom italian language with wm2005 blacklight doesn't work anyway
I have the same problem like Venom...
We need same help!!
TomTom 4.40
Same problem with the Dutch Language.
Pressing the hangup button and then go to the power settings to chance the backlight, solves the problem for the time being.
But i prefer a solution that works ever time.
Any can help us
I'm interested in couple of things:
1. is there a functional FM RADIO module inside th unit?
2. is there a functional GPS module inside th unit?
If YES, how to enable them?
fm radio on rw681
Yes, there is a fm radio module in rw6815.
with file explorer go to windows folder and you will find FMRADIO file, click and you will see the application. You must have earphone connected as antenna.
If you don't see the application, first be sure you select in file explorer menu, "show all files" ( not sure the reel term because I use a french version of rw6815, in French it's " afficher tous les fichiers" ), second,use reso explorer.
Hope this help you.
no answer for the second question.
Regards
uvelicko said:
I'm interested in couple of things:
1. is there a functional FM RADIO module inside th unit?
2. is there a functional GPS module inside th unit?
If YES, how to enable them?
Click to expand...
Click to collapse
NO! There are not fm or gps module in rw6815
thanks a lot...
Is it maybe possible to upgrade rw6815 to wm6 somehow?
use search http://forum.xda-developers.com/showpost.php?p=1703709&postcount=95. Originl metod by Pda-Hack team