Tomtom 3.01 and xda2 registry - MDA III, XDA III, PDA2k, 9090 Accessories

Once installed bttols (for handfree profile) I lost connection between xda2 and gps (Dconnex DC-230); no problem between this bt gps and its sw on pda (gps viewer on com5, br 9600). Nothing happened when I tried to up/downgrade TT gps software(3.07; 2.07) nor with widcomm stack :idea: . I tried also to uninstall bttools without success. The only way to run properly ttn3 is hard reset and re-install ttn software alone; but when I restore (using spritebackup, including registry), ttn3 freeze on start and a message advice that it cannot laun :idea: ch gps control panel (to select the properly gps engine), so I need soft reset to restart. In the registry (I use PHM registry) the tt gps engine is set on com1 (by default, I think it's the wired model).How can I solve this trouble? I wouldn't manually re-install the several softwares I'm using for about 1 year.Thanks in advance to everyone, expecially developers, able to help me.
Cor

When you installed bttools did you remove any existing bluetooth devices from the bonding? You should remove the gps, reset then rebond gps. Try choosing tomtom wireless gps in top box and gps on bt in lower box if the com5 doesnt work. Are you sure about the 9600 setting, if not try 4800.

I've done all these steps I think properly. But now cannot access tt gps control panel (even starting from wizard) to select the gps device (two messages: "cannot launch gps control panel" or "no gps engine please reinstall", even if tomtomgps.exe and ttgpseng.exe are in windows directory. Work properly only after hard reset.
Should search for gps cabs in installation CD?

Related

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

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 GPS control panel

Something happened to my mda2 (rom ITA 1.72) installing some sw (bttools, pzp,etc).
Now TTN 3.01 freeze on start needing soft reset to restart pda.
I tried to upgrade to 3.07 without success. I can run navigator software (map planning) only if in registry (HKLM) tomtom gps folder is removed; obviousely this way there is no bond between pda and gps. A message appear trying to choose for the bt gps I owe: "GPS control panel can not be launch".
Someone can help me to manually install in right folder files to launch the panel (from installation CD or downloading from the web or creating working registry folder)?
You can see picture of ttgps control panel on http://support-uk.tomtom.com/cgibin...admin=&p_li=&p_faqid=104&p_created=1105411260
(I'm not able to add picture in this body message from pda; please someone add to this topic)
Useful help highly appreciated.
Cor

Tomtom GPS control panel

Something happened to my mda2 (rom ITA 1.72) installing some sw (bttools, pzp,etc).
Now TTN 3.01 freeze on start needing soft reset to restart pda.
I tried to upgrade to 3.07 without success. I can run navigator software (map planning) only if in registry (HKLM) tomtom gps folder is removed; obviousely this way there is no bond between pda and gps. A message appear trying to choose for the bt gps I owe: "GPS control panel can not be launch".
Someone can help me to manually install in right folder files to launch the panel (from installation CD or downloading from the web or creating working registry folder)?
You can see picture of ttgps control panel on http://support-uk.tomtom.com/cgibin...admin=&p_li=&p_faqid=104&p_created=1105411260
(I'm not able to add picture in this body message from pda; please someone add to this topic)
Useful help highly appreciated.
Cor

Tomtom GPS control panel

Something happened to my mda2 (rom ITA 1.72) installing some sw (bttools, pzp,etc).
Now TTN 3.01 freeze on start needing soft reset to restart pda.
I tried to upgrade to 3.07 without success. I can run navigator software (map planning) only if in registry (HKLM) tomtom gps folder is removed; obviousely this way there is no bond between pda and gps. A message appear trying to choose for the bt gps I owe: "GPS control panel can not be launch".
Someone can help me to manually install in right folder files to launch the panel (from installation CD or downloading from the web or creating working registry folder)?
You can see picture of ttgps control panel on http://support-uk.tomtom.com/cgibin...admin=&p_li=&p_faqid=104&p_created=1105411260
(I'm not able to add picture in this body message from pda; please someone add to this topic)
Useful help highly appreciated.
Cor

[Q]Help needed - Bluetooth not working

G'Day All,
I have a T9193 that's about 3months old and have run into a Bluetooth issue.
When I start up the phone I get the message "BTTrayCE.exe is not a valid Pocket PC application"
When I try to turn on Bluetooth from Settings I get the message "Can't turn on Bluetooth"
I have had Bluettoth working before and the only thing that I think could have caused this is a failed installation of Tom Tom on the first go. I did eventually manage to successfully install Tom Tom but still can't get my Bluetooth function to work. I've tried a soft reset but that has made no difference.
Anyone have any ideas? Any assistance would be greatly appreciated.
Cheers,
Franz
I would suggest a hard reset. It looks like a system file corruption to me.
tomtom jacks up the bt files by replacing them with outdated ones. go to this post and unzip the bt files and put them in your windows folder (either by activesync or total commander).
http://forum.xda-developers.com/showpost.php?p=3900678&postcount=8

Categories

Resources