Hi,
Has anyone come across a fix to make WM6.1 bluetooth connect to the TomTom range of external Sat Nav devices?
It can pair with the phone but does not have the correct services to enable a data connection.
After a bit of research on the wen it appears that this is an issue with WM and not the phone hardware.
Any suggestions welcome.
Regards,
Simpic
Related
Hi All,
I have a i-Mate PDA2K-EVDO with the following specs:
ROM:2.03.00 WWE
Radio: HA01_140
Ex ROM: 2.03.11 WWE
Currently with eXpansys FSE9 Car Kit (Includes integrated GPS reciever) URL"http://www.expansys.com.au/product.asp?code=124312", with ALK (Travroute) CoPilot Live 5 for PPC.
The issue that I am having is that when the phone is docked in the car-kit all call functions work fine (except for volume being a little low, but that may be spk position), however I cannot get the GPS software to communicate with the reciever. I am not sure whether the com-port that is used to communicate with the reciever is only being half-opened (or not remaining open).
I have tried modifying the selected COM settings and am currently using (COM 1, 4800) which appears to have some communication with the device. When the unit first is powered-up the GPS recieving light is on (steady) and when GPS location is established the light starts flashing. I have installed GPSInfo (for WM5) and am able to scan ports to establish COM1, 4800 as the connected port. When I then press the "Cold Start" button the GPS reciever resets, and then goes through the re-establishment phase, but no GPS data is being parsed.
To top things off, I did manage to get the CoPilot software to work for all about 5 mins. So I am thinking that this may be a port issue (or something with the reciever).
Can anyone provide some help with the following:
1 - A utility that can check com port activity, and see what is happening at this level.
2 - Some insight as to what other programs may use the same ports as COM1 - As I believe that it is serially emulated as a COM.
3 - Any other insight would be greatly appreciated.
Thanks in advance.
pro-integrator said:
Hi All,
I have a i-Mate PDA2K-EVDO with the following specs:
ROM:2.03.00 WWE
Radio: HA01_140
Ex ROM: 2.03.11 WWE
Currently with eXpansys FSE9 Car Kit (Includes integrated GPS reciever) URL"http://www.expansys.com.au/product.asp?code=124312", with ALK (Travroute) CoPilot Live 5 for PPC.
The issue that I am having is that when the phone is docked in the car-kit all call functions work fine (except for volume being a little low, but that may be spk position), however I cannot get the GPS software to communicate with the reciever. I am not sure whether the com-port that is used to communicate with the reciever is only being half-opened (or not remaining open).
I have tried modifying the selected COM settings and am currently using (COM 1, 4800) which appears to have some communication with the device. When the unit first is powered-up the GPS recieving light is on (steady) and when GPS location is established the light starts flashing. I have installed GPSInfo (for WM5) and am able to scan ports to establish COM1, 4800 as the connected port. When I then press the "Cold Start" button the GPS reciever resets, and then goes through the re-establishment phase, but no GPS data is being parsed.
To top things off, I did manage to get the CoPilot software to work for all about 5 mins. So I am thinking that this may be a port issue (or something with the reciever).
Can anyone provide some help with the following:
1 - A utility that can check com port activity, and see what is happening at this level.
2 - Some insight as to what other programs may use the same ports as COM1 - As I believe that it is serially emulated as a COM.
3 - Any other insight would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
Not too sure if this'll help but with TomTom 5, you need to disable incoming beams on the Start\Settings\Connections\Beam to enable the Hard-Wired GPS to be read..
Try it and let us know the outcome..
Cheers!
Still No Good
Hey Mr Philly,
No luck with the Beam Settings. I even went as fas as Hard Resetting the device :x as Active Sync to Exchange stopped working this morning....
Any other ideas?
Thanks again for your response.
Paul.[/quote]
Paul, you mentioned specificaly that you loaded GPS Info (for WM5) is this the OS you have on the device? if so the GPS applet in the control panel / connections tab might need playing with - BTW I should have mentioned as its a wired GPS unit leave the Receive all beams OFF on this device - Mike
Interesting Point
Hi Mike,
Thanks for joining in on this thread.
I have disabled beams on the device.
THe GPSInfo app loaded was WM5 although I only have WM2003 SE. I have searched through multiple ng's to find a 2K3SE version, but all seem to point to the new version.
This was also the file provided my the distributor of the car-kit & cradle. The GPS unit is integrated into the Car Kit, so that is what i refer to as hard-wired (opposed to GPS).
As for the applet, I do not have a GPS applet in the connections section :?:
Can you provide any more informationon this point.
Thanks again,
Paul.
Disregard it then, I thought you might have loaded up a 2005 OS by chance , this has no bearing on the problem on your device - more thinking time required - Mike
Re: Still No Good
pro-integrator said:
Hey Mr Philly,
No luck with the Beam Settings. I even went as fas as Hard Resetting the device :x as Active Sync to Exchange stopped working this morning....
Any other ideas?
Thanks again for your response.
Paul.
Click to expand...
Click to collapse
Hi Paul..
Apologies.. I also need more thinking time.. :lol:
If I think of anything else, I'll get back to you..
Hi I have a mda compctII, I also have tomtom navigator 5. I am having problems setting up me I-blue gps reciever. I can get everything running and the test program supplied with the gpr reciever connects to the device and shows gps location. But... when I go to run tomtom I cannot get it to recognise the device. It is set up on bluetooth serial port 6 but tomtom does not have this selection availible... and Ideas?
I have no experience pairing a 3rd part BT GPS receiver since I use the original TomTom. I think what you need is to first install BT_COM_PORT.CAB (attached) so that you could select on which COM port to use.
Try upgrading TT to the latest version (5.21) too.
Good luck.
one step closer... in blutooth selection I am given the option for all the com ports... but it will only allow me to select com 6. This option is not shown in tomtom just com:0,2,3 and 9.
Sorry mate, I think I couldn't be of any further help since I have no experience with the I-Blue. If my memory serves me right, I think I saw some posts about the I-Blue in Howard Forum.
Hi, I'm having a problem with connection to my Bluetooth in the car. I've a car with integrated Bleutooth, not Parrot or any other extra device.
Since I upgraded my Artemis [P3300 in Holland] to WM6 I came across this problem. The Artemis does connect to the Bluetooth car system, but I can't phone 'out' en I can't answer my connections !?
Has anyone come across this same problem and what more...I'd like to hear a solution?! HTC gives the advice to 'hard reset' [what I already did!] or downgrade to WM5. I think that is not a real problemsolver in WM6 !
Help Help
Can someone give a definitive answer to this, I am using an Orange SPV M700 which I have flashed with the generic Dopod WM5 rom Version 1.23.405.2.
I have tried various WM6 roms and have had the same issues with them all, I loose bluetooth pairing authority, the wirless keys are lost and Tomtom map activations are lost too.
Is there a way to resolve this issue as I see there are a lot of users with the Trinity and WM6 in signatures, so someone must be doing something right.
After having flashed my phone from WM5 to WM6, the tomtom ID of my phone changed too... Perhaps Tomtom's support will help you with that?
I have no problem with bluetooth...
It's not that, perhaps I should have been a bit clearer.
After flashing to WM6 & pairing across bluetooth for the activesync, connecting it to my wireless & activating the tomtom maps, give it 24hours or so and these details are lost. Although the bluetooth PC is still in the paired devices, the pairing code needs to be re-entered as does the wireless key if I try to connect to that.
The Tomtom map needs reactivating again also.
peterelliott11 said:
The Tomtom map needs reactivating again also.
Click to expand...
Click to collapse
I already read somewhere about this.
When you do some pairing with bluetooth and PC sometimes you lose the maps!!
Don't have further details though
Hi,
I upgraded my ROM from WM6 to WM6.1 (Kavana's ROM) a couple of days ago, but my Route 66 N7 software can't work with my Adapt AD-300 GPS receiver anymore.
It's quite weird: my phone finds the receiver, I can add it as device and the connection looks OK. Only Route 66 keeps complaining it can't find a receiver. There is no GPS signal on the receiver, but before the upgrade the software could see the receiver with just a good BT signal. Now: nothing.
I have tried everything: serial connection yes/no, secure connection yes/no, COM6/COM7, enable incoming beams/BT to my phone. Nothing helps.
Anyone know about issues between Bluetooth devices, maybe Adapt specifically, and WM 6.1?
Otherwise, is there any software with which I can check the BT connection on my phone itself?
Only thing I haven't tried yet is factory reset the GPS receiver itself (I removed the battery for a couple of minutes, but don't know if this is sufficient).
Bah, I like 6.1 too much to revert to 6.0
-mod-: oh right, my phone is an S620.