Related
Does anybody have experience of Navman GPS software on the XDA II. I loaded the newest operating system as per instructions and then loaded the software. Now whenever the software is run, the whole phone runs at about a 1/50th of the speed.
Any suggestions as desperate. :?
spottrader said:
Does anybody have experience of Navman GPS software on the XDA II. I loaded the newest operating system as per instructions and then loaded the software. Now whenever the software is run, the whole phone runs at about a 1/50th of the speed.
Any suggestions as desperate. :?
Click to expand...
Click to collapse
Turn off incomming beams in control panel and try again!
Let us know how that goes? 8)
Thanks.
I tried turning off all beams but to no avail. Still painfully slow
What SD Card have you got the maps on? Make, Size etc
i have a SanDisk 1Gb SD card. Made in china
I was struggling setting up my Navman 4100 and also experienced a major reduction in the speed of the mapping software. It turned out I had the wrong com port setting in the GPS Status screen. I had no idea which com port it should've been until I followed the instructions here http://www.navman-europe.com/support.php?id=AA005410&faq=56
The EnableCharPin hack finally allowed my gadgets to talk to each other properly, thereby informing me of the correct com port to use.
Stick with it Spottrader, it's a pain to set up, but I can vouch for the fact that driving around being guided by 5 satellites is probably the coolest thing you'll ever do on a mobile phone ! 8)
(By the way, my incoming beams box IS ticked.)
Same thing here
Installed tomtom on my xda, an ipaq and a mitac mio. Same thing happened till I changed the gps over to tomtom gps on sp2.
All work fine, (even the bluetooth one on the ipaq)
Go figure.
just got myself tomtom 5. unfortunately cant hook up my gps which is Altina GBT708. It is a bluetooth gps which i could use successfully with previous versions of tomtom on com port 6 now it dosent work. any tips. tried using com port 5 patch in other forums still no result. tried installing previous version of gps driver over current still nothing.
TomTom5 is a pain in the butt to configure your GPS. I have the NavMan GPS sleeve for the IPAQ and just sleecting NavMan GPS from the settings screen doesn't work. I had to configure a standard NMEA GPS unit and set the baud rate to 38400 and then it worked. Play about with the settings, one will work eventually!
how do you go about doing that.i have been trying to select various options dosent seem to work
I am having the same problems with a Fortuna Clip-on Bluetooth GPS. Worked fine with previous TT3 and works fine with Memory-Map software.
The only thing I noticed is that you can pick com port but not the baud rate.
Any help on this would be appreciated. :?:
Just select standard wired GPS or standard bluetooch GPS (wired in my case). It then asked for baud rate. I searched the web to find the right baud rate to set for my device.
i chose the standard bluetooth gps. then it asked me to selected the port. so i selected com port 6. after that it just doesnt do anything. for tomtom 4.44 it goes to bluetooth manager automatically and asks to confirm the gps device
After selecting Standard bluetooth the next screen asks what the unit is connected too and after selecting com6 nothing happens?
If I select TomTom bluetooth I get some blue light flashes from the GPS unit and that is it.
Mine is wires, not bluetooth so I can't help I'm afraid.
I have Orange SPVm2000, TT5, Fortuna Clip-on Bluetooth GPS, Motorola HS850 Bluetooth Headset and have them all working together.
I had the same problem as reported hear of not being able to setup GPS on com 6, TT5 would either freeze when selecting com 6 or no communication would start between GPS and PDA.
First my observations:-
Always start to configure GPS with a soft reset this is a must as this is the only way I can guarantee a connection now that I have it working.
The only time I could get the blue light to flicker on my GPS was when I selected TomTom GPS receiver
When I select Com6 I am not given the option to select baud rate?
The sequence of events that made the final connecton:-
Do a soft rest.
I selected TomTom Bluetooth GPS and left the PDA and GPS trying to communicate for 5mins. During this time the blue light on the GPS flashes at different rates.
I then selected "Other Bluetooth GPS" then Com6 and it sprang into life.
This is not a guaranteed solution, but it worked for me. Why?
The problem is clearly with TT5, as I have no problems with this setup with other navigation software.
Remember in TT5 if it fails to connect once it will not connect at all until you do a soft reset of your PDA.
Hope this helps.
Daron at Tekguru seems to have solved this problem:
http://www.tekguru.co.uk/phpBB2/viewtopic.php?t=6291
"...I've resolved the issue, which stems I think from the BT GPS unit I use (Emtec as supplied with CoPilot Live).
It seems that TTN5 has decided it is not a valid BT unit, which is a major grr.....
But in the end after a good hour of hard resetting the machine to give me a clean platform I've found the following works (assuming BT is on and the GPS already paired):
- Tap on the screen and select Change Preferences (big spanner)
- Tap the black triangle until it says Preferences 4 of 6
- Select Configure
- Select 'Another cabled NMEA GPS' set the GPS Baud Rate at 38400 and select DONE.
The BT wizard will then allow you to select the correct bluetooth port, for my machine it was the top of the two BT ports (COM 8 - if you tap and hold).
You will notice a small orange and black circle at the top right of the screen this will start to spin if you are connected to the GPS if it does not spin then soft reset the PDA and try again.
This did take three tries before it connected for me but it worked beautifully.
TTN5 uses a superb VGA graphics set and it looks damned beautiful! Worth the effort but by God TT could have made it less painful!"
Hi, might be worht giving my post here a look http://forum.xda-developers.com/viewtopic.php?p=125995#125995
Might be able to help you.... James
:wink:
IT WORKS....
I was a bit sceptical at first but xda-rocks found the solution from us. he might not be the one to find it but atleast brought it to our attention. im sure a lot of people were suffering with this problem and will be pleased that they can use their tt5 at last. i had almost given up hope at one point and move back to tt4.44 as i find tt3.07 utterly rubbish, slow and without features.
i can now start playing round with the gps once again like when i first got my m2000...
THANZ AGAIN
TT5 & Blutooth
Hi Guys
I thought I would post this. I had the same problem with TT5 and it not connecting to my BT gps until I installed 5.10 . The only problem is that I already got my refund from TT due to lack of functionality. I had to install a cracked ver off of the net and Piratebay has a 5.10 hack on there now. I think I will reorder my TT5 as it seems to work great now.
THanks
Coupegbr
OK here's a strange one. Orange SPV M2000 with Navman Smart ST V3 amd a Holux GPS cradle (which uses the com port on bottom of the phone so its hard wired).
Since installing I have been through a process of elimination to find out why the software reports NO GPS DATA occasionally, especially when it had to do anything that involves loading something, i.e. a speedcam warning or voice command approaching a roundabout. Tried the lot. Disabling ports/activesync etc.
Then one day it dawned on me that it wasn't happening on a long drive North from London. The only thing that was different was I didn't have the headset plugged in!
I've tested this over the last few weeks or so, and yes, headset plugged in means loss of data from the GPS intermittently.
I installed TOM TOM 5 from a friend and low and behold it seems to be doing the same. In TOM TOM you get the signal bars at the right and they go to zero every couple of minutes then spring back up. So its not software specific.
I would have thought the supplied headset was just a good old-fashioned 'feed to the speaker or feed to the earpiece' hard connection but it would appear not to be so.
So the question is, what is the Blue Angel doing when the headset is plugged in that it isn't doing when its not?!!!
....... tumbleweed rolls by........ signs creak...... saloon doors swing......
OK, ....I know, ...I know, ....if no one has posted it probably means no one knows the answer So I'll ask, does anyone use their Blue Angel with Navman SmartST V3 who could try this with the headphones to see if its a one off or a real issue?
As a test I installed TomTom Navigator and it does the same thing.
Any thoughts appreciated.
OK guys. I know I can't force a response so I'll post findings to date. For one reason or another, I have used Navman Smart ST V3 (now returned) a 'borrowed' version of Tom Tom navigator 5 and, in an effort to remain 'legit' a version of Destinator PN. All these exhibit the same problem so I can only presume that there is a hardware issue with the Blue Angel and my GPS port (port 1). Does anyone have a clue what the BA does when you plug in the headset that could cause such a problem or pehaps even a fix?
I have an XDA IIs with TomTom 5 and a wired GPS unit.
It doesn't exhibit this fault.
The headset (wired) works just fine. I have disabled BlueTooth to get reliable telephone performance, so I can't tell what that would work like.
HTH
Steve
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..
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
Try a search on the Hermes forum. I found lots of stuff.
I found THIS ONE . But there were MANY others. Some users reported success with some ROMs.
Don't fret, it works fine on mine... Are you running a WM6 image - you may wish to upgrade to wm6 if you're not. (or downgrade to TT5.....)
Treat the issue as 2 separate problems, bluetooth related loss of GPS unit, and the stability of the TT6 software.
There are any number of other applications that will let you connect and read signals from the GPS unit, try these to see if you have a faulty gps unit or if its TT playing up.
Once you're happy with this look at the TT issue.....
I have 2 Varios II and I can admit that I had some issues with TT6 with WM5. TT liked to freeze when I was typing in the address or browsing through menus. When I changed to WM5 AKU3.2 it was better, but still not perfect. Eventually, it was WM6 that helped me. Now TT6 is running without any issues (of course it can freeze from time to time when I have too many programmes running in the background). Just try any of new WM6 and everything should be fine.
I had TT5.21 which people said run fine which didnt on wm6 but TT6.1 works fine
Long time since i've been on here but while i was browsing about, i saw this problem. All i can suggest is using the inbuilt GPS and see how that works? I have TT6 as well and i have used it perfectly well on an XDA Mini, XDA Orbit, SPV M700, HTC Touch, HTC TyTn II... seems a bit odd that you're having these problems. Have you since cured the fault or is it still being a bit of a ****bag?!
While i'm here... anyone got the latest maps at all for TT6? Shout me on [email protected] if you have any info on TT6 or need any PDA / Pocket PC help.
Griz
ibanyard said:
Don't fret, it works fine on mine... Are you running a WM6 image - you may wish to upgrade to wm6 if you're not. (or downgrade to TT5.....)
Treat the issue as 2 separate problems, bluetooth related loss of GPS unit, and the stability of the TT6 software.
There are any number of other applications that will let you connect and read signals from the GPS unit, try these to see if you have a faulty gps unit or if its TT playing up.
Once you're happy with this look at the TT issue.....
Click to expand...
Click to collapse
Yeah, I had established that the gps was working fine, I've been happily using it on my ipaq 2210 for ages. Then with the Hermes testing with gpsgate and some other stuff showed no problems.
The problem I had was that my TT6 was a 2GB SD card version and I didn't have micro SD big enough to test it. I had about 1hour to play with my friend's one and that's when I discovered the two problems.
He lent me the card to play with this evening and I've made a little progress now. I've sorted the flakey GPS operation, primarily by changing the com port, deleting the pairing and pairing again. So far that's not dropped out since.
Tomtom runs but freezes, this appears to be a confirmed problem which I hope that WM6 will solve as (mean-machine) suggests.
I feel a lot happier that the damn thing runs at least. The freezing appears to be related to cpu usage as I find that that zooming right out on a map is a good way to cause this to happen. The menu screens can be a problem too and the rest appear intermittent. As others have stated in other threads, hitting the red button and then switching back to TT will free it up.
I guess the next thing is to study the Wiki and try an make sense of the order things need to be done to put WM6 in, which Rom if any, which version of WM6. ... Information overload, so I think I need to take it slow and ingest the data .
Thanks for all the replys guys, it amazes me how much support HTC has and how many of you are passionate about them. Up till a few months ago I had never heard of HTC, now I doubt I'd consider anything else.
TomTom6
louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
I have been using TomTom 6 on my Imate Jasjam (TyTn) both with WM5 and many versions of WM6. It works flawlessly never missing a beat. What com port are you using? Have you turned off secure connection?
@louiscar: a good place to start with upgrading info (to avoid the overload) is THIS SITE . Great guides that make it simple.
rbin said:
I have been using TomTom 6 on my Imate Jasjam (TyTn) both with WM5 and many versions of WM6. It works flawlessly never missing a beat. What com port are you using? Have you turned off secure connection?
Click to expand...
Click to collapse
Hi rbin,
I've currently got the GPS panel set to 'program port = com2', 'hardware port = com0' and my bluetooth gps is set to 'outgoing = com0'
Currently this works well so the GPS issue has been resolved.
Tomtom on the other hand freezes pretty much as described here:
http://forum.xda-developers.com/showthread.php?t=299892&highlight=tomtom+freezes
and in a number of other threads.
todd_jg said:
@louiscar: a good place to start with upgrading info (to avoid the overload) is THIS SITE . Great guides that make it simple.
Click to expand...
Click to collapse
Great link, thanks Todd. Reading glasses are on already.
TT6 w/Pharos and Holux recievers work great
I've an AT&T Tytn upgraded to WM6 and have no troubles with my Holux or Pharos receivers and TT6.
Everything works great EXCEPT issues with data connections such as TT Buddies or traffic. This isn't unique to the PDA version of the software though, as I also have a standalone TomTom GO 910 paired with the phone and it works almost okay as a bluetooth speaker phone, but constantly has trouble getting a good data connection.
My $0.02
louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
I have used TT6 on my MDA VArio II (TyTn) for almost a year...no problem. Now I have the TyTn II
Same here.. been using Tom tom 6 on my Tytn since the day i installed wm6, no problems here, works like a charm!
HEAT???
I have been using TT6 on my Imate JASJAM running the DOPOD WM6 ROM without much trouble (no hanging etc). The only problem I am experiencing is huge power drain and the unit being physically hot when running TT. Maybe this power drain and potential overheating can cause some units to hang and playup, or potentially any unit given the right environment!
Anyone else finding their units getting a bit hot?
I've been using TT6 on my Tytn (MDA Vario II) almost one year now. No problems. Started using TT6 while running WM5, upgraded to WM6 (schaps rom), reinstalled TT6 and it just continued as before. No problems, no hangups no freezing. I've been using all kinds of different charts with TT6, so I don't think the problem is with TT.
louiscar said:
Hi rbin,
I've currently got the GPS panel set to 'program port = com2', 'hardware port = com0' and my bluetooth gps is set to 'outgoing = com0'
Currently this works well so the GPS issue has been resolved.
Tomtom on the other hand freezes pretty much as described here:
http://forum.xda-developers.com/showthread.php?t=299892&highlight=tomtom+freezes
and in a number of other threads.
Click to expand...
Click to collapse
Going to try your settings too, cause on all WM6 roms I tried I keep losing my GPS BT connection. I'm not damn sure it got nothing to do with TT6. But when I delete my gps and reconnect it while TT6 is up and running, TT will find the gps straight away. So imho it's the BT connection that fails and not TT.
It's really annoying though.
Cheers, M
I have been running TomTom Navigator 6 on my JASJAM for some time. The hanging problem described is probably caused by having all the Points Of Interest (POI) active.
Go into the TomTom settings menu and de-activate ALL the POIs. Try it, then only turn on the ones you actually require.
oltp said:
Going to try your settings too, cause on all WM6 roms I tried I keep losing my GPS BT connection. I'm not damn sure it got nothing to do with TT6. But when I delete my gps and reconnect it while TT6 is up and running, TT will find the gps straight away. So imho it's the BT connection that fails and not TT.
It's really annoying though.
Cheers, M
Click to expand...
Click to collapse
Doesn't work either. Seems that after a soft-reset the BT connection with my GPS is f*d. Very strange because the BT headset doesn't suffer any of this. Maybe time to buy a new GPS, but with WM5 I never experienced this behaviour.
I found that with tt6 you need to have the WM6 internal gps settings set to "None" for both program and hardware port. Then make sure the box is checked in the last tab so it autodetects the com ports. Once all this is set and you goto add a bluetooth gps device in tt6 it gives you the option to use com port 0. select this port and it should detect your gps unit with no probs. Been running tt6 on my 8525 with tnt's latest cooked rom and things couldn't be running smoother.
Edit: On another note. I used to use Telenav with my 8525 with the original at&t rom. I had the worst luck with that application. I would constantly lose my gps connect and I almost always had to do a soft-reset to get it working again. It is quite possible that Telenav was not the issue and that the particular rom I was using had bluetooth connection issues that were resolved when I switched to a cooked rom such as the tnt one. So for those using tt6 with BT connection problems you may want to try a different rom and see how your luck goes.