Develop Bugs

Generic BT GPS & TomTom 5

I have just bought a Generic BlueTooth GPS for use with TomTom 5. I successfully paired the GPS with the XDA IIs, then the problem came of getting tomtom to find it. It will not see it as a Bluetooth GPS so I have to select "Other Cable NMEA GPS", set the baud rate to 38400 and set it to COM 6.
This will work for approx 40mins before TomTom5 crashes. It then takes a soft reboot to get it working again.
Is anyone else having similar problems?
I might have to go back to TomTom3.
My device info:
ROM Version: 1.40.00 WWE (i-mate ROM)
Radio Version: 1.12.00
ExtROM Version: 1.40.176 WWE

Well after struggling with TomTom 5 for the last time, I'm going back to TomTom 3. I believe there is a patch out there to get the TomTom 5 maps to work with 3.

I use my pda2k with tomtom 5.1 and both the Tomtom 3 bluetooth gps and a BT-338 Globalsat GPS Bluetooth Receiver .
In order to get it to work, I have to switch on bluetooth and connect to the gps manually, and then start Tomtom. Occaisonally the gps wont connect or Tomtom just wont detect the gps. I then to a soft reset, try again and it works.
I have not had to do anything clever with the Tomtom settings, in fact I think I just use the Tomtom bluetooth setting for both receivers.
If someone phones me whilst using Tomtom, after the call, tomtom does not detect the gps and I have to quit and restart.

Well I'm back on TomTom 3 now, it's lovely and stable, the BT connect first time everytime and I can make/accept calls on my BT headset.
Perfect!
If only the boys at TomTom had put some effort in and tested 5 before releasing it.

Hello Porkspeare,
can you tell me which version of TomTom 3 you are using and what bluetooth stack? I have the problem that I cannot use my BT headset Bluetrek G2 after installing TomTom 3.01 , even though before the TomTom install it works fine. Would be interesting to know what combination works on your machine.
Thanks

ROM Version: 1.40.00 WWE (i-mate ROM)
BlueTooth Version: 1.0.0 Build 3900
TomTom Version: 3.03 (427)
BT Headset Ver: Blue Trek G2
Hope this helps.

Vavavoom, are you using the very latest bluetooth driver from tomtom for version 3..

tomtom 5 hangs
I have same problem...
The problem goes away if you turn off all POIs
some say copying poi.dat from tomtom3 maps will solve it..
also seen something about a vga registry hack, havent tried any - i have just turned off poi until some solution pops up...
Jan

Hi cruising-thru,
I don't know what you mean by "bluetooth driver for TomTom3" - can you get a seperate update for just the bluetooth driver? The only update I found was for the Navigator (3.07) and GPS (3.07). Unfortunately I can only install the GPS update. If I try to install a Navigator update higher than 3.01 TomTom tells me it cannot find a map even though it's installed and activated. My current combination is therefore Navigator 3.01 and GPS 3.07.
If there is a sperate BT update could you please tell me where to find it?
Thanx

Thanx porkspeare,
I have the same combination except I only managed to install TomTom up to version 3.01. Maybe if I somehow manage to update to 3.03 it solves my problem. Will keep trying
Cheers

PDA2K - Car Kit / In-Built GPS Comms

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..

TomTom & AX3L_OS_v3.1.2_LITE_fixed

Hello,
I am wondering if AX3L_OS_v3.1.2_LITE_fixed.rar is a GPS enabled rom. I cannot seem to connect using TomTom version 6.010. If it matters, my radio version is 1.50.08.11 and I am in the US.
TomTom Settings :
GPS receiver : Other NMEA Receiver
baud rate : 9600
GPS to com9
Thank you in advance!

Palermitano said:
Hello,
I am wondering if AX3L_OS_v3.1.2_LITE_fixed.rar is a GPS enabled rom. I cannot seem to connect using TomTom version 6.010. If it matters, my radio version is 1.50.08.11 and I am in the US.
TomTom Settings :
GPS receiver : Other NMEA Receiver
baud rate : 9600
GPS to com9
Thank you in advance!
Click to expand...
Click to collapse
But why don't ask this in the AX3L ROM Thread???
Don't you think AX3L will help you better?

Oh Yea it works!
Palermitano
AX3L 's AX3L_OS_v3.1.2_LITE_fixed.rar works the GPS great! I have less than 50% memory usage before kicking off the TomTom 6. It's been the fasted operation I have seen on the Trinity.
I'm using the TomTom 6 from HTC and maps from everywhere. It's a lot more stable than WM5 and I'm seeing a lot less memory card corruption. (4gig SD from TopRam)
What you might try is VITO Navigator II v1.3 to trouble shoot the problem. This little app can auto find the GPS module in the Trinity and give a display of all viewable sat's in about 5 seconds. There is no enable or disable needed, that app will turn on the gps and start working. It can even show you the raw data stream coming down.
TomTom has too much over head to trouble shoot with.
Been playing with GPS units for 8 years now, Palm3 to Sony N70 to HP 5450 and now Trinity.

Windows mobile 6 and tomtom 6.0.20,

hi i got tom tom 6.0.20 for mda compact 3 from t-mobile now i have windows mobile 6.
but the gps is not working.
i have gps settings to com4 on the first tab on the second none automatic on the third tab.
and in tomtom i got internal gps selected.
please help.
greats antonius
Edit: got 1 signal now but still no connection and map only 17 is gray and standing out.

Try newer Version of TomTom. The last Version working for the Artemis is TomTom 6.032.8351. On the HTC Support Page you can find TomTom 6.032.8320 under the P3600 Section.
Regards
Jabami

works for me, try 'other nmea receiver', 9600 baud rate, and com4
hope it helps

Ive used all sorts of roms including the now official Tmob uk one and never had probs. I always use tomtom 6.0.30 from HTC's website. I use an external bluetooth GPS (as its wired into the car) and also the Build in GPS all without problems.
When in doubt, get the stylus out (and had reset)

Deluo Bluetooth GPS problems with WM 6

Hello everybody,
I don't know if this is the right forum to post this question but here we go...
I have a Wizard (HTC Qtek A9100) Smartphone with ROM Hornet Manilla 4.5 upgraded on December 2008.
Everything is working well except my Deluo Bluetooth GPS.
I already tested other bluetooth assessories that are working 100%.
The Smartphone can find the GPS receiver on Bluetooth tab, but they can't stabilish a full comunication. (Bluetooth comunication ok means the blue lamp doesn't flashing and it is flashing...)
The Navigator software I'm using is Destinator 7.
Everytime I turn on the bluetooth on smartphone and turn on the GPS, they start working for 2 or 3 sec, which means blue lamp doesn't flashing and comunication stablished. After that, they loose the connection each other and the light become flashing.
There are a lot os sets to be done and it is not clear for me:
COM port #2 for the navigator software;
COM port #7 for the hardware;
NMEA protocol for the GPS;
Bound Rate for GPS;
Serial Port for service.
Why two COM ports ? Why serial port ?
A lot os things that I don't understand.
I really would like to have the GPS working again and for me there isn't a hardware problem (Smartphone or GPS) but a configuration problem (comunication or connection) and not the partnership between both equipments which is OK.
Is there anything that can be done in order to solve this problem ?
Tks in advance.
Regards,
Cássio

No sugestions ?
I'm still facing the GPS problem.
Regards,
Cássio