I cannot start using my navi kit for many days because of one problem: I leave BT GPS receiver outside for at least 20 hrs to initialise, connect to device regularly, run NAVIGON and get always the same message - "A GPS receiver has been detected, but a convinient GPS signal is not available. The reception is obstructed, or the receiver is being initialised."
Any idea what to do?
Slaven, it could be a faulty receiver, do you have a program for viewing the signal and number of sats being received? It maybe also that the settings are wrong for the gps, what is the model of receiver you are using and details please of how you set it up when bonding etc. Have you carried out a factory reset of the receiver also? One other thing, sometimes a gps reciver will work much better for initialising first time if it is mobile rather than static, put it in the car and see if you have any results after a mile or 2. Try this program to test the gps function.
Please check your PM I have sent one to you. thanks.
I`m using BT GPS receiver delivered in original kit with Navigon 4 (made by GNS). I`ve bonded them regularly (XDA II asked for code and I entered 0000 - as described in operation manual). I have not performed factory reset of GPS rec. because don`t know how to do that. I couldn`t find any possible way to do that, except to remove BT and TMC moduls and I have done so.
Thank`s for gpsdiag, but I don`t know hoe to connect BT GPS with my notebook (with built in BT) to test it. Only service available is to connect it to serial port, but couldn`t. As you can conclude, I`m not very experienced with this, so I need really DETAILED help! Thank`s in advance.
Sorry, I sent the wrong version of diag, I will pm you the proper file.
The BT version of serail port on qtek is not compatible with wildcomm BT (used by navigon) got to navigon website and download the wildcomm patch
this will solve your problem
I was using navigon with wired gps and then tried bluetooth which dropped signal and refused to reconnect, thanks for the link I will try it.
Related
Hi all,
I have just bought a tomtom bluetooth gps system, I can bond to the gps receiver ok, but it just wn't connect. There is deffinately a connection during the bonding process but that is it, it never connects again.
Any help would be greatly appreciated.
Thanks
Steve
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Puff The Magic Wagon! said:
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Click to expand...
Click to collapse
I think the problem is that the xdaII doesn't support a bluetooth serial port profile. I have tried virtually everything and had no luck.
Please keep me posted on how you get on, I really hope we can get this sorted or I will have a gps reciever paper weight.
Steve
Hmm
Due to the nature of yesterday, it wasn't until midnight (GMT) that I could get to have a play with my XDA II & EMTAC BTGPS (& I wasn't sober )
Installed TTN2 and tried to connect - not a sauasage
There "seems" to be something using COM6 and as such TTN2 can't use that as the path to the EMTAC - check box in the GPS options won't check. Turn off BT & you can check the box, but it won't connect as something else obviously can't use it either :? Dunno - I'm not a programmer but I'm going to have to check this out.
I'll speak to a contact @ EMTAC & see if they have been sucessful in bonding to an XDA II (HTC2?) & if so how. Otherwise I'll keep on playing with it & see what I can find out.
Anyone else got any tips or ideas what might be the way of resolving this?
Have you tried turning off the "receive incoming beams" under settings/connections, that may or may not free up the first com port.
I know someone with the same problem. O2 have told him that Tom Tom are working on a new version of software to fix this specific issue and it will be downloadable from the TT site. They couldn't say when.
xdaguru
Beam off did seem to allow me to connect to COM6 but not for my device Might be worth trying Steve because TT Wireless was one I could connect to.
IIRC from iPaq Bluetooth Manager, you had to bring up the device options once bonded and then select a serial connection. Pocket Loox as well. The BT Manager in the XDA II is very basic. So I do wonder if its a TT soluble solution or does it need an upgrade to the BT Manager?
If its a problem soluble by TT then I'm prehaps more hopeful
Sorry to go off topic but I wonder if this is the same PTMW that I know?
How you doin m8?
Hello Danny
Yes it is I
Can't be that many PTMW!'s about
All's well & I'll catch you on the other side one day
Yeah I guessed there could be only one PTMW
I take it you're lucky enough to have an XDA2 already? I always knew u were a gaget fan like myself. I have a month left on my XDA1 contract
Hopefully Tom Tom will have the problem ironed out by then as I have TTN2 aswell.
Pay us a vist on Scoobycity soon. Alots changed and we're alot bigger now
Any bluetooth GPS working with the XDA2 ??
Is there anyone who got the XDA2 working with a bluetooth GPS ? I am very eager to get one (both the XDA2 and a bluetooth GPS) but I would like to hear from some who got a combination working .
Thanks,
Marco
Its being looked into Marco
It may be that the BT Manager may not have various BT options enabled, so it may need a software update/patch from O2.
Spoke to O2 this morning.
They are "aware that not everything works with BT" and are working on a software update.
No timescale offered
I have an Emtac and was going to buy the XDAii to replace my Loox but without this bluetooth connectivity I will save my money. However interestingly it does say on the XDA website...
...or use TomTom Bluetooth with Xda II and cut down the amount of wires in your car
Click to expand...
Click to collapse
I'd say this is enough to get a refund if you want one. Page in question is located here...
http://www.my-xda.com/gps.html
TomTom and Bluetooth
The fault with the TomTom software and Bluetooth lies solely in TomTom's software. TomTom have recognised this and are aggresively working to fix the problem.
The TomTom GPS software doesn't know to read the details of the virtual com port. So give them some time to fix the problem....
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Hi
I too have just upgraded to the XDA II from the Ipaq 3970, and I also have an Emtac BTGPS.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
It would be very interesting to find out if any one has a TomTom BTGPS and can serial link it to the XDA II
Dom
TomTom and Bluetooth
mother said:
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Click to expand...
Click to collapse
The fact you're able to bond with the unit shows that bluetooth is working correctly.
The issue is that the tomtom software can't read com6: (which is where bt is hiding) or do anything with it, because of the way the software works.
This is because the Bluetooth manager on Xda II is from MICROSOFT, whereas on other devices it's manufacturer specific. As far as I know this is the first ever deployment of the MS Bluetooth stack directly.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
Click to expand...
Click to collapse
Then why do they say they support TomTom on their website? Seems like a few people at O2 dont really know what's going on?
I've not known that O2 has ever supported EMTAC BTGPS 'cos the XDA (1) didn't have bluetooth support :?
Surely it is the BT manager that is at fault? Not allowing the a serial connection from the manager to the Emtac?
TomTom is looking to read Com6 (when told to) but the info its getting is not sufficient or mapable.
I've run BTGPS with a TDK B/tooth card and it needs to be told (as do other managers) to make a serial connection to the BT device.
Test for someone (I'll try & do it too)
Find an alternate mapping software that *should* accept a BTGPS device & try to connect...
Does any one else have this setup...
Im finding that as i end a phone call the gps reciever stops comunicating.
it starts again if you make another call but stops again the minute i hang up.
if i go into the gps driver page and turn off then back on the gps (using the tick box) then its fine again untill i make then end the next call.
Any comments, help or suggestions appreciated.
could possibly be the gps driver corrupted, try reinstalling just the gps driver part from the cd and see if that helps, i've had a similar problem before, but not with a serial gps, i always use bluetooth
tomtom 2 xda 2 this might help..
goto settings - connections - beam once here untick the beam default and then retry you device ........... this solved a similar problem on mine !!! post back youre findings please...
:lol:
Its not the recieve all beams check box unfortunately...
I have to have that unchecked to connect the gprs on com1 anyway...
thanks for your suggestion though - keep them comming...
I have logged a support call with tomtom - no reply as yet...
Is your car kit fully wired including radio mute etc ?? I have the same problem but I also have to disconnect the GPS from the cradle otherwise I cannot carry out a conversation on the phone. Please post if you get your problem resolved.
I didnt fully wire the car kit - i just use the supplied external speaker.
I havnt had any problems making phone calls though.
I just cant get round the fact that the gps is disconnected on terminating the call.
The only work around i have is to turn the device off then on again after each call to re-instate the serial connection to the gps receiver...
I bought my car kit from dashmounts.co.uk the backup from them is S__T It seems that audio is the problem with alot of car kits looking at forums I have emailed tomtom and will post any solution however small they may give
:?: Do I need a seperate device (i.e. gps reciever?) to run Navigation software such as Tom Tom Navigator or Route 66 on my XDAII? If I need a gps transmitter reciever, where can I get one from and can I buy one that I can permenantly install in my car?
:?
You will allways need a GPS receiver with (almost) any PocketPC based navigation solution.
From personal experience I would recommend a Bluetooth receiver. Make sure you have a 1.72 ROM version for good Bluetooth operation. There are many threads on that on the forum.
You will also need a power supply (to XDAII and to Bluetooth GPS for uninterrupted operation and quick GPS fixes)
And you would need a car cradle or 'real' carkit in oder to be able to have a good view on the screen
If you dont like to be bother by the limited storage amount a SD memory card is ver advisable, beware of the bad performing ones
Good software is TomTom Navigator 3
Like I said: This forum has lots of threads on this subject. Alternatively check out www.pocketgpsworld.co.uk
Thanx for the advice I'm still a newbe to this phone I haven't even had it a week yet. but already it looks like lots of fun 8)
Check this out:
http://www.totalpda.com/Holux-Powered-GPS-PDA-Mount-for-XDA-Series-I-Mate-Q-Tec-2020.aspx
It's a Car cradle / GPS / powered / loud speaker etc etc....all you need next is Tomtom or simular.
My mate has one and it's great. Removes the need for a seperate GPS receiver, which would need power itself. Don't know if you can get in Canada but probably.
HPJ
heck this out:
http://www.totalpda.com/Holux-Powered-GPS-PDA-Mount-for-XDA-Series-I-Mate-Q-Tec-2020.aspx
It's a Car cradle / GPS / powered / loud speaker etc etc....all you need next is Tomtom or simular.
My mate has one and it's great. Removes the need for a seperate GPS receiver, which would need power itself. Don't know if you can get in Canada but probably.
HPJ
Click to expand...
Click to collapse
Thanks looks like a Phatt product. Unfortuntely I've already bought the cradle and gps seperate.
Beware: The product looks nice BUT: It's probably useless when your car has a heat-resistant windscreen.
These windscreens have a metal-like foil in it which does not let radio (GPS are radio signals) signals thru. These windscreen however always have 1 or 2 spots (most likely next to the mirror) where the foil is absent. Meant for toll cards, but also useable to stick a GPS mouse to it. For that you do need a GPS that can be placed (I glueed a plastic box with double-sided tape to the windscreen foil-free spot in which my BT (permanently powered) GPS is sitting).
Works like a charm.
Edsud - wow, seems logical. Guess many have bought the product and spent ages trying to get it to work, without any luck. Thanks for the warning.
How good are the Bluetooth receivers? ie does the Bluetooth stay 'well connected'? What about if you want to use a BT headset as well, can you run 2 BT devices at the same time?
Cheers
HPJ
I have found BT to be VERY stable (using the 1.72 rom & standard Bt stack), also when I use both GPS & Headset at the same time.
I have fitted the BT GPS with a constant 12V wire resulting in continuous power. Which results in a permanent fix (BT GPS's seem to keep working even when there is no device connected). When I start TomTom I never have to wait for a fix, it;s there when I start TomTom.
When you do not do this you will notice a delay to get a first fix. This delay is relatively short when the GPS has not realy moved since it was last switched on. The delay also depends on the type of GPS. I know of a Holux CF GPS (wichs gets switched off when you take it out of the PocketPC) on a Dell Axim that takes about 1 minute to get its first fix again. Imagine how long that takes when you have to wait for it . . .
im using the same as ed and it runs like a dream scary i know
I use Tom Tom 3 BT with XDA II. Works great.
No BT headset yet byt it's coming soon.
Rgds
Andrew
I have installed it on 2 different XDA2's and it works brialliantly.
I have tried searching the forums and can't find much Info.
Is anybody here using the above system for telephony & GPS; If so how do they intergrate/do they work well on the XDA II (I have ROM Version 1.72 with Radio1.17)
I Know about the headset profile probs not giving full functionality of the Handsfree use of the car kit but this doesn't bother me to much as long as I can Make and receive calls.
Thanks in anticipation!
I was going to get a CK3100, but heard so many problems regarding build quality, and lack of support, I got a HCB 30 instead.
It did not help when I tried to e-mail parrot for advice and 3 different e-mail adresses bounced back.
Works Perfect!
Just had the CK3300 installed today and it works perfectly - I Knew some of the functions didn't work because the XDA2 only supports headset profile but once you have transferred your contacts to the kit via bluetooth it works well.
Also the GPS works well with CoPilot 5 live; it picked up the signal straight away ; well pleased with this set up!!
same to me have the ck3300 tested with qtek2020 - works fine. problems with 9090 but after bluetooth update now it works fine. No tests with S100 at this time.
tested GPS with destinator 3 and map&guide fleet navigator and mobileobjects fleet management system.
don't use bluetooth tools after Rom 1.66 :!: CK3x00 didn't work aber installation of this
Set up
Just had the CK3300 installed today and it works perfectly - I Knew some of the functions didn't work because the XDA2 only supports headset profile but once you have transferred your contacts to the kit via bluetooth it works well.
Also the GPS works well with CoPilot 5 live; it picked up the signal straight away ; well pleased with this set up!!
Click to expand...
Click to collapse
Any tips on setting up the CK3300 with my XDA2?
Just had the car kit fitted - i need both nav and handsfree functions - but i am not sure that i have got the phone and ck3300 to bond properly. So everything is 'greyed out' on the parrot.
Using ROM 1.72.00WWE (1.72.181) and radio 1.17.00
Thanks for any help received.
If everything is greyed out then it isn't bonded properly!
Step 1
Delete the pairings you have from XDA2 and car Kit;
Step 2
On the car kit turn the control knob untill settings appear- then scroll to 'Advanced Settings' - 'pairing a telephone' - 'windows CE device'
Step 3
Now search for devices using your XDA2 and the car kit should be shown.
Step 4
Enter passcode 1234 and accept headset and serial profiles when shown.
PAIRING COMPLETE
to access your phonebook you need to transfere the contacts via bluetooth to the car kit.
Hope this helps
XDA2 CK3300
Managed to get the GPS set up (fiddling with COM ports - even imbeciles strike lucky sometimes)
Some items are now in black. However, I am not sure that I have done it right as I cannot get it to use my phone to make calls or receive them. Which is exactly why I bought it in the first place.
So, please (please please) can you tell me how to exchange my phonebook?
I am going to sit in the car right now and have a go at your bonding advice...maybe all will become clear (but that is not often my experience!)
Thanks again for your help.
You need to bond the phones in the manner I described or it will not work ; this is clearly ststed in the Parrot instructions and on their website.
(I have noticed a strong correlation between people who do not read instructions and complain things do not work!!) - Joke
You also need to make sure your headset profile is active on the XDA 2 for it to work. Again reading the instructions for the phonebook - you tap and hold a contact on the XDA2 and select 'beam contact' - 'via bluetooth' the bluetooth search then comes up and the car kit will be found you then 'tap to send'
Now i have the opposite problem!
Believe it or not, I have now got the XDA2 and the CK3300 bonding automatically so I can make and receive calls whilst driving. It works pretty well (occasionally makes an awful noise, but only occasionally). I am impressed.
However, once I had done that, the GPS is undetectable. I have tried all sorts of combinations. I have checked the instructions - and selected the long code (ends in 9600) but I am not certain that I am using the right com port. I have tried most of them without success.
Oddly, this is the one thing that WAS working before I got the car kit to work (for calls). Somehow, either I have lost the right settings OR the XDA2 won't do both (although I read somewhere that it would) OR my ROM needs updating (uh?)
Please help.
BTW, I am due a phone upgrade - I love the xda2 but would consider getting another phone if necessary, if anyone can recommend one that is fully CK3300 and TomTom compatible.
I don't use Tom Tom myself but from reading these forums I think you need to install the patch on their website to allow Tom Tom to use the correct Port .
Your Car Kit also needs it's software updating if it makes a noise like you say. On the Car Kit go to > settings-advanced settings-information and you will find the software version (sounds like 4.03) if it makes a noise. The latest on the Parrot website is 4.10b and this will fix the noise issue.
If you need help installing this let me know.
The best Phone is surprisingly the Old Fashioned Nokia 6310i - it has a good bluetooth stack and uses the handsfree profile rather than the headset so contacts sync automatically but if you require live traffic info best stick with what you got as the Nokia will not pair with the XDAII and the car kit at same time.
Which COM port?
For the moment, I have a temporary solution.
However, I have updated the TomTom Navigator software and the GPS, but still don't know which port the GPS in the CK3300 should be connected to.
Any ideas?
And, thanks Nikpro for the excellent help so far - you are a true altruist and a star!
The outbound port on the xdaII is port 5 by default
On XDAII go to Settings - System tab - Bluetooth settings and make sure you check the tick box for outbound COM port.
There is also a chance you have deleted your serial port profile so tap on the bluetooth icon in the Today Screen and go to bonded devices. Select the CK3300 and delete partnership (do not delete pairing from car kit end!)
Then search for new devices from the XDAII and the CK3300 will again come up; create a new partenship and everything should be good.
Still having problems
Oddly, I still cannot use the GPS on the CK3300.
I am using my old TomTom at the moment for GPS and the CK3300 for headset - which works fine, but I wanted the CK3300 to do both.
When I try and reset the GPS to the (series of numbers ending in 9600) as stated in the info and the instructions (Nikpro, take note - I have read them - but your comment made me laugh), the TomTom just 'freezes'. Wait - and wait - and wait - and when it reincarnates itself, no GPS at all.
I am using the 1.72.00WWE rom and radio 1.17.00
I think that I have tried every permutation for the COM port.
Has anyone any ideas? Please?
When you initially pair your XDA to the car kit do you get a message about serial connection show on the screen? The problem must be with the tom tom software as with copilot and mapopolis it works fine? or the way you are pairing the two!
What software version is the car kit? PLEASE DESCRIBE HOW YOU ARE PAIRING THE DEVICES??
Hi all, 1st post and all that.
Have you tried falshing the parrot with the newest rom, mine picked up enough to make and recieve call, but i flashed my xdaII with 2.02.T1WWE this morning and it works even better.
Hope you get a result
nikpro said:
I don't use Tom Tom myself but from reading these forums I think you need to install the patch on their website to allow Tom Tom to use the correct Port .
Your Car Kit also needs it's software updating if it makes a noise like you say. On the Car Kit go to > settings-advanced settings-information and you will find the software version (sounds like 4.03) if it makes a noise. The latest on the Parrot website is 4.10b and this will fix the noise issue.
If you need help installing this let me know.
The best Phone is surprisingly the Old Fashioned Nokia 6310i - it has a good bluetooth stack and uses the handsfree profile rather than the headset so contacts sync automatically but if you require live traffic info best stick with what you got as the Nokia will not pair with the XDAII and the car kit at same time.
Click to expand...
Click to collapse
Use Bluetooth tools www.bluetooth.jazztel.es
and edit the registry under hkey local machine, builtin, BTIBserial, rename BTIBserial.dll into BTIOBserial.dll
and go Start, Settings, System, Bluetooth settings and check both inbound and outbound.
Delete ALL paired devices, reboot, and re pair them.
You will now have an option for two serial ports, one for each device.
This is the only way to do it if you have two devices that need a serial port. If you have a third, you are SOL.
Normally, the stupid programmers who made the MS BT program, made it so it only had one dynamic port for BT. Some people would experience having to reboot before switching BT devices, most would have to re pair every dam time.
The new 2005 does not have this problem but it has other bugs.
They smart people at MS changed the databases so Mapopolis and other third party programs can not read the contacts or have other bugs with them. Plus the 2005 version here limits your memory.
The 2.02 - 2.06 will NOT work with Hands Free and most car kits need it and if you have caller ID via BT, you are SOL too.
The 2.20 is a stable and a good OS and the Hands free works much better. The down side is, when I get a call on the call waiting, even if I did not answer, it would disconnect the BT headset and no sound through the phone too. I would have to, click on Tools, Hands Free off, tools Hands
Free on before it would work. I have lost many clients this way.
I decided to disable call waiting in the phone settings and it only has a few bugs now like I have to turn off and then back on the BT headset after ever call or it would revert to Headset mode.
The caller ID will not display if the call is in the history of my BT headset or if it is in my contacts database.
I mention my BT headset because it is like a car system when used in Hands free mode.
Good luck, let me know if you have any trouble now.
Parrot 3100 with XDA II
Hello,
I have just put in a Parrot 3100 and it works fine as a handsfree phone.
is there any way when I am not in the car though to use my Jabra 250v headset without rebonding and selecting it as the preferred headset device?
I can't seem to switch between the Parrot and the Jabra when the other one is not in use without repairing.
Thanks for any advice
BT
Try turning of one and turning on the other and soft reset..
Ok, I have just spent my entire weekend trying to get my Qtek 9090 to communicate to my newly installed Parrot CK3300 (with GPS). I have read the manual about 3 times from beginning to end, know the whole website parrot.biz by hard (ugly site BTW), and have tried about everything in configuring, but with no success so far.
Initially I had the 2 devices paired to each other, but after I installed Tom Tom 3, it is impossible for me to get them to pair again. Nevertheless, the 2 devices "see" each other (when asked in "Linked devices"), but they can not get to communicate. From all the stuff I have read on forums and sites, it seems that I need to upgrade my Bluetooth version, but I have no idea how and where to start this procedure.
Can anyone help me out here ?
Any tips are welcome !
Hi,
I use a BlueTrek earpiece (bluetooth) to enable handfree calling with my Qtek9100. I Also use TomTom Navigator.
When TomTom starts it enables the BlueTooth connections (if not allready active). This is usefull since I use a BlueTooth GPS with TomTom.
However, if I exit the TomTom Navigator application it is also disabeling BlueTooth, resulting in loosing the connection with the earpiece.
Does anybody know if this can be changed?
Perhaps a registry key I can change to solve this small, but annoyng, problem.
Gert-Jan
Turn on bluetooth before you start TomTom, then when you quit it should stay on. Does on my xda IIi anyway
The same on my magician. TT5.1 returns BT in the state it was before starting TT. TT5.0 however always shuts down BT on close.
Regards, M
I tested this last week, but came to the sam conclusion.
No matter what the state of BT, TomTom always disables BT on exit.
Gert-Jan
Ditto with my XDA2i running TomTom5 with a Qstarz BT-Q880. Slightly annoying.
However, if I press one of the hard buttons (such as the Contact List button), when the new window is brought up TomTom is minimised. Then, I can Switch (from hfrmobile.com) to Close All - and while this disconnects the GPS device, I've doublechecked and it doesn't disconnect my bluetooth headset, nor does it turn off the Bluetooth itself.
So, that in itself is a quick-and-dirty workaround hack, but I've not come up with any other solution thus far. Currently scouring the registry and the configuration files (what few there are) for a fix - it may be that someone with infinitely more coding ability needs to hack the TomTom .exe to disable this switchoff, though that's no mean feat.
You will probably find that if you reconfigure your GPS reciever in the Tomtom preferances as an "other wired receiver" select an appropriate baud rate, then select a Bluetooth com port, it will still work with a bluetooth GPS receiver but will completely leave your Bluetooth alone.
This does also mean it wont start it automatically if it's not allready on.
That doesn't work - the only way my Qstarz will work is if I configure it as Other Wired NMEA GPS and then run it on Bluetooth COM6, setting the baud rate appropriately (the Qstarz will accept any rate from 4800 to 115500 anyway, so that's rather irrelevant). Even if it's set as other wired GPS, the bluetooth is still disabled upon TT exiting.
This is also the info advised by the TomTom website if you're having problems getting your GPS to run with the software, so I'm guessing it's the only way. I'll have another look round the TT web site when I'm not so pushed for time.
What Tomtom version are you guys using? After a little play with mine I can say that with GPS setup as a bluetooth device. If bluetooth is on when I start Tomtom it stays on after I exit.
I use version 5.2 for Pocket PC
Well, small update - after having TomTom pop up the Bluetooth Manager box every time it starts up, and asking me which device I'd like to use as default, I managed to select the Qstarz Serial Port Connection shortcut which I created (had to manually create the link after setting up the device pairing) - I checked the option to Use this connetion by default, and now TomTom leaves the Bluetooth turned on after it exits!
Smashing stuff, means I can now use my headset and TomTom simultaneously in the car.
This is with TomTom 5.000 (4890) with GPS driver v1.20 and using the Great Britain Plus Map (v571). Bosh!
I get something different on my QTEK S100. When the QTek starts receiving the GPS signal (via bluetooth), TomTom freezes the screen for about 2 seconds and then closes TomTom.
Any ideas about this problem?
Is it because I had "MagicButton" installed? I uninstalled it, did soft reset... but the problem is still there. I can I know if it is MAgicButton doing that?
Thanks
DoubleW