My friend and I both have Tilts running the following:
HardSPL 3.56
Death V4.1
Radio 1.58.16.24
The only difference between the two phones, is that I used the cab widely available here for TomTom and he bought a full fledged copy on DVD.
When I go to use my phone for navigation everything is choppy like so many others, but he showed me a route demo and it's smooth as the Magician in the htcclassaction.org demonstration video. I can't figure out how it's so smooth though. He's not using the "D3D drivers", either, so I'm at a loss.
His TomTom is 6.01 with 6.01 USA and Canada
Any ideas as to why / how TomTom got around the choppyness of DirectDraw?
Nothing at all?
I think this could be very important for DirectDraw and 2D acceleration if someone could figure this out
What I found when running TomTom on my Tytn II is that if you disable all the POIs from showing on the map while you are navigating then the software runs very smoothly.
If you use any speed cam warnings etc these still show up on the map as you navigate but it has no impact on the speed etc.
Let me know how that works.
Paul.
What about differences in the speeds of the SD cards? What do you have and what does he have? There have been reports that the 4GB and higher capacity cards cause Tom Tom to run slow.
how is it laggy?
Err...could this be the old Windoze analogy???
Increase of version = extra stuff to do???
Like early version just drew maps,,,new version waits for you to talk to it, checks traffic draws more items and still wants to work on same memory and processor???
you disable all the POIs from showing on the map while you are navigating then the software runs very smoothly.
Click to expand...
Click to collapse
I'm sure glad to have seen this post. I've posted on 2-3 different forums, including teh TomTom support forum here; I've Called TomTom support...all to no avail.
This fixed my problem.
how is it laggy?
Click to expand...
Click to collapse
Go in and check a dozen or so POIs to display while driving, and I suspect you'll find out. Map was jerky; I could make a turn, and be a half block down the road before it know I had turned.
I have an 8GB Sandisk MicroSDHC card and he has a 4GB Sandisk MicroSD card. I'm going to try disabling POIs, but I don't think that's it.
NerdsMcGee said:
I have an 8GB Sandisk MicroSDHC card and he has a 4GB Sandisk MicroSD card. I'm going to try disabling POIs, but I don't think that's it.
Click to expand...
Click to collapse
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
NerdsMcGee said:
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
Click to expand...
Click to collapse
You're welcome.
I have a 4gb micro sd card and the speed has nothing to do with the size or speed of the card.
I wonder if the video of the 2 machines on the class action lawsuit website had the Tytn II displaying all the POIs.
I think they would be a bit embarrassed if that turns out to be the case
I think the problem is just TomToms laggy software rather than the PDA
Paul.
firstandlast said:
You're welcome.
I have a 4gb micro sd card and the speed has nothing to do with the size or speed of the card.
I wonder if the video of the 2 machines on the class action lawsuit website had the Tytn II displaying all the POIs.
I think they would be a bit embarrassed if that turns out to be the case
I think the problem is just TomToms laggy software rather than the PDA
Paul.
Click to expand...
Click to collapse
I wouldn't be surprised. TomTom has always been smooth and lag-free for me, even with the stock HTC shipped ROM.
I forget which versions I've used, but I think it was:
6.02?
6.030 (or 6.032? I can't remember)
7.450 (the latest TTN7)
Well, at least video is smooth. I had sound issues with 6.030/32 and TTN7 that did not occur with the first version I used.
As you can see by my current sig (although soon to change) I'm using the latest HTC WM 6.1 ROM and 1.65.17.56 Radio with the correct 3.28.0000 SPL and I get very laggy GPS performance full-stop. It's not necessarily jerky (although on occasion where lots of movement such as going around a roundabout occurs, it can be) but it is very laggy. By this I mean I can be sitting in the train stationary and from the train starting to move and Tomtom Navigator actually registering movement/speed, it can take up to 25 seconds - and this is with a reasonable signal reception averaging 3 or more bars the whole time. I put this down to the actual GPS perfomance of the Radio module driver. Tomtoms call centre in the UK advised me that TTN Version 6.032 (the HTC official version) isn't actually supported under WM 6.1, only the original WM 6.0 O/S so guess what's happening to my TyTN II later this week at the HTC repair centre.... I'll be so pleased not to have to put up with rubbish GPS performance anymore. Next time I'll only upgrade to WM 6.1 once I get the all clear that they've fixed their WM 6.1 ROM/Radio combination.
Oh and I have tried TT 6.10 when Tomtom were first attempting to work out why their software was playing up after the WM 6.1 upgrade (they provided me with a free 'crossgrade' for faultfinding purposes) and I fould in terms of smoothness, it was identical to 6.032. I went back to 6.032 because 6.10 didn't have fully working customised things like jog button volume control, volume change screen indication and native inbuilt 'internal' GPS setting. The start menu also misbehaved or the physical Windows button on the phone wouldn't work properly when TTN was running, something like that - altogether not as 'Kaiser friendly'.
NerdsMcGee said:
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
Click to expand...
Click to collapse
Perhaps this works with Navigon, too. Gonna try that later
I am using TTN 6.032 on the latest WM 6.1 with a maximum of POIs enabled and it runs smoothly.
I've tried a version lower than 6.032, and based on my personal experience it didn't really make a difference. As long as you turn off the POI the TT will run like crazy, and plus the lower version is not as user friendly as the 6.032, or even better V.7, that's if V.7 will accept the maps from V.6, just my 2 cents.
Flying Kiwi said:
As you can see by my current sig (although soon to change) I'm using the latest HTC WM 6.1 ROM and 1.65.17.56 Radio with the correct 3.28.0000 SPL and I get very laggy GPS performance full-stop. It's not necessarily jerky (although on occasion where lots of movement such as going around a roundabout occurs, it can be) but it is very laggy. By this I mean I can be sitting in the train stationary and from the train starting to move and Tomtom Navigator actually registering movement/speed, it can take up to 25 seconds - and this is with a reasonable signal reception averaging 3 or more bars the whole time. I put this down to the actual GPS perfomance of the Radio module driver. Tomtoms call centre in the UK advised me that TTN Version 6.032 (the HTC official version) isn't actually supported under WM 6.1, only the original WM 6.0 O/S so guess what's happening to my TyTN II later this week at the HTC repair centre.... I'll be so pleased not to have to put up with rubbish GPS performance anymore. Next time I'll only upgrade to WM 6.1 once I get the all clear that they've fixed their WM 6.1 ROM/Radio combination.
Oh and I have tried TT 6.10 when Tomtom were first attempting to work out why their software was playing up after the WM 6.1 upgrade (they provided me with a free 'crossgrade' for faultfinding purposes) and I fould in terms of smoothness, it was identical to 6.032. I went back to 6.032 because 6.10 didn't have fully working customised things like jog button volume control, volume change screen indication and native inbuilt 'internal' GPS setting. The start menu also misbehaved or the physical Windows button on the phone wouldn't work properly when TTN was running, something like that - altogether not as 'Kaiser friendly'.
Click to expand...
Click to collapse
Google "static navigation". The oddball performance at low speeds (such as lag from a stop) is not TomTom's fault. It's a setting in the GPS receiver that (unfortunately) can't be disabled on the Kaiser.
Related
I've been asked whether it's working OK on the Kaiser (and its rebranded versions). As I've run into diametrically opposing reports, I've found it the best to start a new thread so that I can see whether it works or not.
Yes it does work, well on the Vario III incarnation it does. I have had 6.0 running and now I've installed 6.030 which is also running perfectly
Works fine on my HTC branded phone, running 6.032 now
Version 6.032 ships with the TyTN II and works fantastic as it directly supports the internal GPS!
Works great for me out of the box. Vodafone v1615 and V6.032.
Had to buy a full UK map and that installed OK.
Hope this helps
Works perfect on my unbranded HTC Tytn II... no configuration and stuff needed...
The only thing I've found is that it won't work with some of the newer maps.
I am running a v660 map but I couldn't get a newer (675) version to work.
Anyone able to use newer than 660 on a TyTn II?
Thanks guys and gals; highly appreciated
i have maps 675 working uk n ireland map.
TomTom Navigator 6.030 (8320) + UK and IE Plus Major Roads of WE 1409 v675.1409
works fine
mbriody said:
The only thing I've found is that it won't work with some of the newer maps.
I am running a v660 map but I couldn't get a newer (675) version to work.
Anyone able to use newer than 660 on a TyTn II?
Click to expand...
Click to collapse
I'm running the TomTom 6.032 with USA_Canada map (version 6.75).
Guess it must be just me then!
I'll give 675 a try again.
I'm running 6.010 on my Tilt with no issues. I just chose 'other nema gps' for my adapter and set the com4 and 4800 baud.
Works like a champ.
laakness said:
I'm running 6.010 on my Tilt with no issues. I just chose 'other nema gps' for my adapter and set the com4 and 4800 baud.
Works like a champ.
Click to expand...
Click to collapse
Why do you use an adapter and not the internal GPS radio built into the Tilt?
I have TomTom working on my Tilt (still evaluating with freebie map) using the internal radio. Works good but certain features are turned off (i.e., sound) in the evaluation version. TomTom looks to be much better and more user friendly than Telenav.
BillMc said:
Why do you use an adapter and not the internal GPS radio built into the Tilt?
I have TomTom working on my Tilt (still evaluating with freebie map) using the internal radio. Works good but certain features are turned off (i.e., sound) in the evaluation version. TomTom looks to be much better and more user friendly than Telenav.
Click to expand...
Click to collapse
I never said I was using an external adapter. I said "other nema gps" SETTING which is in the options. That is because the 6.010 version does not have Internal GPS as an option so I have to specify the comm settings for my device.
v6.030 with v675 maps works flawlessly on my Orange TyTn II.
TomTom Maps 50% Off
For anyone who doesn't yet have the TomTom maps, it appears they are 50% off today. Not sure how long this sale price will last.
Question for you guys..... I purchasing a Tytn II on the internet, and i asuming it will come with TomTom, but mind dose not.
Just want to know where did you guys purchasing your TytnII??? I live in USA, and using Tmobile...it is suck they do not have the 3G ...... I wish it will have it soon.....
I only have a couple of problems.
1. If I minimize TT by pressing the side OK button then try to click on something in the corners (volume, start menu) then TT comes back forward.
2. Sometimes it takes quite a few minutes for TT to connect to the GPS.
Besides these minimal problems, I love not having to carry around a separate GPS unit.
My Tilt did not come with TomTom but after a a great deal of searching and reading the forums here, I ordered it from Amazon. I wanted a GPS solution that was independent of a data feed (I have no data plan since most all of my stops have wi-fi access.....and I'm cheap).
Installation to the computer was very simple. Setting up the device worked the first attempt (likely because I had read about which settings to chose here on the forum). Registering the software was not exactly intuitive (I attempted to use the product number provided in the box.....which it turned out to be only used online to get the actual activation number from tomtom).
Running TomTom Home 1.5v106 on the computer and 6.010 on my Tilt.
I can pull a good signal even indoors at home. In-car performace in poor (without an external antena). But all works like a charm on my Harley, where the driving instructions are played thru the stereo speakers.
The only thing that appears to be lacking (or I just haven't found it yet) is the ability to plan routes on the computer and upload them to the Tilt. But I've had no problems planning routes directly on the device itself.
inkspot said:
I only have a couple of problems.
1. If I minimize TT by pressing the side OK button then try to click on something in the corners (volume, start menu) then TT comes back forward.
2. Sometimes it takes quite a few minutes for TT to connect to the GPS.
Besides these minimal problems, I love not having to carry around a separate GPS unit.
Click to expand...
Click to collapse
Same problem here- if I have the phone on mute, I can't minimize TomTom to turn up the volume, as TT seems to hog control of the touchscreen in WM6. This wasn't a problem in WM5. I'm eagerly awaiting the next release of TomTom.
SYMPTOM:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
SOLUTION:
http://forum.xda-developers.com/showpost.php?p=2114969&postcount=25
http://forum.xda-developers.com/showpost.php?p=2120352&postcount=35
http://forum.xda-developers.com/showpost.php?p=2114969&postcount=40
Click to expand...
Click to collapse
I had this as well with Sleuth's v3 (WM6.1) rom as well, I went back to Sleuth's v1.2 (WM6) and all is good again with iGuidance.
vip_snoopy said:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
My Tilt with DCS's 1.5 cannot run iGuidance 4 totally.
vip_snoopy said:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
Try baud rate at 4800. See if that helps.
I think v4 is far inferior to v3. I have both and v4 is uninstalled. No map generation and compatibility problems.
J
I've found v4 to be OK on Hermes and Kaiser with WM6.0. I've played with baud and it doesn't matter, from 4800-38400 same refresh rate seen.
so, set it to 4800? will try tomorrow when I drive
vip_snoopy:
Don't bother. It won't help. It has something to do with the internal GPS on the Kaiser and WM 6.1 that iGuidance 4 doesn't like. I had the same issue as you (and others). As a test, I paired my bluetooth GPS to the phone and iG4 worked great.
However, other GPS based software (ie Live Search) works fine in WM 6.1.
I cooked my own ROM from Alex's 3.02 package...
shadee
slimshadee said:
vip_snoopy:
Don't bother. It won't help. It has something to do with the internal GPS on the Kaiser and WM 6.1 that iGuidance 4 doesn't like. I had the same issue as you (and others). As a test, I paired my bluetooth GPS to the phone and iG4 worked great.
However, other GPS based software (ie Live Search) works fine in WM 6.1.
I cooked my own ROM from Alex's 3.02 package...
shadee
Click to expand...
Click to collapse
so you said you cooked your own ROM from Alex's 3.02 package, is that WM6.1? could you provide some more details about it?
Yes. 3.02.405.0 ROM base (WM 6.1). It is Alex's v5 Kitchen.
I just got iG4, so I never tested it with any of the ROMS I cooked from WM 6.0. I did however, use iG3.01 sucessfully on all of those WM6.0 ROMs.
I was fortunate to have a bluetooth GPS from my old Hermes and Wizard PPC's, and used it to confirm the problem with iG4 / WM6.1 (3.02 ROM) was related to the internal GPS on the Tilt / Kaiser. iG4 works like a champ with the BT GPS, but craps out constantly when using the built-in GPS.
IMO, the built-in GPS is significantly inferior to a paired BT GPS.
And, BTW, iG4 is slower than iG3.01, probably because of the added POI's and the fact the entire map must be loaded on your storage card. I really miss the maploader program from version 3.
Get a BT GPS and enjoy iG4...it's still the best nav software in my book.
shadee
My two cents worth... I have Handymap (South African Version of Papago) and it also was very sluggish, used to update every 300m or so when going at 100kmph. I complained to the vendor, and since then they have released a cab install specifically for the Tytn II.
So it seems to me that the way the internal GPS chats to the software is different than the way an external BT GPS does.
Just to get this thread back on track and see if anyone can help us find a solution. I am also having the same issues that you describe with iGuidance 4. I am able to get a satellite lock quickly, but while driving, the map does not refresh or update unless you tap the screen. The interesting thing about this problem is that the same version iGuidance works incredibly when using a WM6 rom. This problem only occurs when using WM6.1. Additionally, using the 6.1 rom only seems to impact iGuidance and not TomTom.
I did some research on other devices and saw that some people had success using Franson GPSGate, but I am looking for a solution that doesn't require it as it was not required in wm6.
Please do not turn this thread into a debate over which gps application is better or which version of iGuidance is better. Any suggestions as to what may solve this issue would be appreciated.
I found two issued with iG4 and WM6.1
1 - the map gets a fix but doesn't update unless the screen is touched
2 - the TTS in iG4 uses "canned" speech for most commands, and TTS to just say the street names. With 6.1, the TTS engine seems disabled as well.
3 - Just an FYI, there is a reg setting to force iG4 to only use canned speech like the previous versions like iG3 which does speed up the prog. You can also force full TTS which slows the prog more, so the current hi-brid method is a performance balance.
If GPS Gate fixes this, I'd be OK with that for now till a better fix comes along. Anyone have solid information about this? I'm on Sleuth's v1.2 WM6 rom till then, which is a solid rom, snappier than the stock Kaiser which was very good.
My experience with tech support with iNav will be that they will deny the existance of WM6.1 and any issues, then fix it in the next release. That's what they've done year over year. But I still love the prog.
slimshadee said:
Yes. 3.02.405.0 ROM base (WM 6.1). It is Alex's v5 Kitchen.
I just got iG4, so I never tested it with any of the ROMS I cooked from WM 6.0. I did however, use iG3.01 sucessfully on all of those WM6.0 ROMs.
I was fortunate to have a bluetooth GPS from my old Hermes and Wizard PPC's, and used it to confirm the problem with iG4 / WM6.1 (3.02 ROM) was related to the internal GPS on the Tilt / Kaiser. iG4 works like a champ with the BT GPS, but craps out constantly when using the built-in GPS.
IMO, the built-in GPS is significantly inferior to a paired BT GPS.
And, BTW, iG4 is slower than iG3.01, probably because of the added POI's and the fact the entire map must be loaded on your storage card. I really miss the maploader program from version 3.
Get a BT GPS and enjoy iG4...it's still the best nav software in my book.
shadee
Click to expand...
Click to collapse
well, although I do have a BT GPS, I'm just lazy to carry another one around since I have an "Internal GPS" for the Tilt. So for the meantime I'll be using TomTom until someone figures how it works out. - Hopefully by then iGuidance 5 will be out
I have seen this as an issue as well...But i actually saw it in one of Dutty's WM6.0 ROMs. I then updated to Schaps 6.0 rom and the problem went away. I've since installed only one WM6.1 rom, the udK 7.0 R1 Vega - WWE | WM6.1 CE OS 5.2.19199 (Build 19199.1.0.0). I was going to try a different rom, but i'm not sure that it will solve my issue after reading this thread.
Rom Doesn't Matter
I've had this exact problem ever since the first cooked WM6.1 ROMs have been made available. I have tried every radio and almost every WM6.1 ROM and all have the exact same problem as mentioned in this thread.
But a Bluetooth GPS reciever does work so I'm just going to go with that for now since I only use GPS in my car anyway.
Also I registered my program with iNav and there are no updates to the software yet. opefully when there is it will fix the problem.
temporary work around
Ok, I've given up searching for now and believe that the only solution is to use GPSGate as discussed in this post
http://forum.xda-developers.com/showpost.php?p=1862272&postcount=4
GPSGate is not free, but there are alternatives to it out there that haven't been tested yet. I did download the trial of GPSGate and can verify that it does work. It's not too expensive either for just the ppc license.
To use the mortscript script that is discussed in this thread, you do also need to download AstroGPSLauncher which can be found here:
http://forum.xda-developers.com/showpost.php?p=1870976&postcount=1
It seems as if we are stuck with this until iGuidance can resolve it. The more users that contact them, the better chance we have of getting a fix. However since 6.1 isn't officially released yet, they will more than likely deny the issue.
Heres what iNav support had to say in response to my e-mail
I don't think any of these options will fix the 6.1 compatibility issue...what do you all think?
MY SUPPORT REQUEST...
Hello,
I have Windows Mobile 6.1 on my AT&T Tilt Pocket PC. iGuidance recognizes my internal GPS, but does not automatically refresh the screen. I have to zoom in/out or change something with the screen to get it to refresh. Do you know how I can fix this problem?
THEIR RESPONSE...
There are several possibilities:
1) GPS connection issue : the program is not connected to your GPS and thus unable to update your current position. If it's connected, the arrow/cursor in iGuidance map screen should be in yellow or green. And when you click on view > gpsinfo, you should see the screen w/ NMEA data being updated continuously. If the cursor continues to stay at grey color, this means iGuidance has not been connected to your GPS. If the cursor is red, then this means it has found your GPS but is in the process of locking and searching for satellite signals. The GPS connection indicator information can be found under Section IX step #6 of the iGuidance Installation Guide, and the step-by-step instruction on how to configure and connect iGuidance to your GPS is available under Section VIII step #4 of your iGuidance Installation Guide.
2) Normal program operation: whenever you've just entered an address and click on "nav", the program will automatically enable panning mode. You will need to click on the "X" button at the lower right hand corner to exit the panning mode to see the screen refresh. If you don't manually exit, it will self auto-exit after 40-45 seconds. So if you didn't know how to operate the program and didn't wait for 40-45 seconds, it's likely you will think that the screen is not updating.
3) Program installation: it is also possible that some files were corrupted during installation. You might want to following the uninstall/reinstall instruction in Section II of your iGuidance Installation Guide and reinstall the PPC version.
Tilt is the most popular pocket pc phone used by our customers, so there's no compatibility issue w/ the hardware nor the internal GPS. Most likely, scenario #2 or 3 is the problem.
Has anyone figured out how to get iGuidance 4.0 to work on Windows Mobile 6.1 without spending more money? I know about the GPS Gate trick, but would rather not spend another $20 when iGuidance worked flawlessly by itself on WM6.0.
afgoody said:
Has anyone figured out how to get iGuidance 4.0 to work on Windows Mobile 6.1 without spending more money? I know about the GPS Gate trick, but would rather not spend another $20 when iGuidance worked flawlessly by itself on WM6.0.
Click to expand...
Click to collapse
If you click on my link from two posts above, you'll see that they mention a free alternative called GPSProxy
Just wondering if anyone's TomTom 6 or 7 is as slow as the one as this video I made or is yours running smoothly. Would have though TomTom would have ran much better than this due the the GPU acceleration
Even though it's a VGA screen my Tytn 2 was running this much, much faster, not far off silky smooth . The TomTom in the video is v7 VGA running the latest v7.20 maps (tested also with TomTom 6 QVGA running v6 maps and was just as slow).
Am posting this as reading some posts here and people are saying my TomTom is running smoothly, mines running perfectly, no lag etc.
Look forward to your feedback
Excuse the background noise, forgot to remove it
http://smg.photobucket.com/albums/v604/Radeon/?action=view¤t=MOV04324.flv
im using tomtom7 that came with some of the original diamond roms and the free map that you get for one city from tomtom's site and it runs flawlessly.
Smartstradamus said:
im using tomtom7 that came with some of the original diamond roms and the free map that you get for one city from tomtom's site and it runs flawlessly.
Click to expand...
Click to collapse
What rom version are you running?
Wouldn't mind trying it.
i've run tomtom (both 6 and 7 with your same map) on ALL the ROM that we have at this moment for ours diamond , always smoothly.
neither my polaris have problem like that in your video , my be you have too many POI activated.
Radeon123 said:
Just wondering if anyone's TomTom 6 or 7 is as slow as the one as this video
Click to expand...
Click to collapse
Yep, mine is as ****ty as yours. That is the reason I liked Tomtom is it's smooth movement..... not on the Diamond though, might as well run a slideshow, could possibly be faster.
hi radeon, it seems that i have the same problem as you.
till now i'm thinking it's because of the gps refresh rate, but i'm not really sure
because this should offend all diamond users...
but for me the major problem of using any gps software at the moment is the
enormous lag at low speeds. when i'm in a traffic jam the position updates approx.
only every 100m, and the actual speed is also very slow in changing it's values (i'm
standing still and the tachymetre shows still ~10km/h for a few seconds...
i guess this is because the static navigation of the chipset.
regards,
markus
Hi
I had the same problem on my first tomtom, you display too much POIs, try to disable a lot of POI and retest.
POI's Rubbish
It has nothing to do with the number of POI's. I have run the exact same version of TTN and the exact same map on a Treo 750 with ALL POI's activated and it was as smooth as my Tomtom GO720.
I just find it hard to beleive that my old Palm ran faster??????
Dont know why but it isnt POI's.
thorin31 said:
Hi
I had the same problem on my first tomtom, you display too much POIs, try to disable a lot of POI and retest.
Click to expand...
Click to collapse
I always make sure my POI's are disabled otherwise TomTom would run a lot slower than that video .
Smartstradamus said:
im using tomtom7 that came with some of the original diamond roms and the free map that you get for one city from tomtom's site and it runs flawlessly.
Click to expand...
Click to collapse
Well I would like to see that "flawlessly" on a video!
I just can't believe the current TomToms run flawlessly on the current Diamond ROMs. Till I see it myself.
pietrucci said:
Well I would like to see that "flawlessly" on a video!
I just can't believe the current TomToms run flawlessly on the current Diamond ROMs. Till I see it myself.
Click to expand...
Click to collapse
Would love to see this to
Just as a test, I removed all my POI's and voices from the map folder and ran TomTom with as little on screen as possible, also disabled all street names etc, did a demo run and it ran at exactly the same speed as that video.
I'm running the TLR 1.37.405.1 rom at the moment, so hopefully this maybe a rom issue because the GPU is doing bugger all to help run TomTom, seems the CPU is doing everything, and being a VGA screen that's why it's a lot slower than my old Tytn 2 which the CPU did everything there to.
This is the only issue I have with the Diamond and it's an annoying one
pietrucci said:
Well I would like to see that "flawlessly" on a video!
I just can't believe the current TomToms run flawlessly on the current Diamond ROMs. Till I see it myself.
Click to expand...
Click to collapse
Trust me when i say that you need the tomtom version that was shipped on certain roms.
I would give you a link but im sure the xda guys would class it as warez!
I have a uk diamond that didnt come with tomtom7 but i have a license for tomtom so i found the optimized version for the diamond.
Hi,
Like most people here, I've experience TomTom's lag. From my stock Touch Pro, I notice a 3-4 second lag whilst driving around 60km/h. I read the previously mentioned GPS tweaks for the Touch Pro and initially applied the tweaks, but only dividing the original values by 4 (eg. PollInterval went from 1024 to 256, etc.). This reduced the lag to 1-2 seconds whilst driving. After applying the tweaks by dividing by 8 (eg. PollInterval to 128) resulted in the same 1-2 second lag in TomTom whilst driving. Clearly, the GPS is no longer the bottleneck now.
Next, I planned a route and watched the Demo at 200% speed to see how fast I can expect TomTom to appear. The display refreshed every 1-2 seconds! Coincidence?! I was in Harvey Norman (huge electronics retailer with lots of demo units) and watched a route Demo on a TomTom standalone device at 200% speed. The display refreshed 2-3 times per second.
Hence, is it possible to increase TomTom Navigator's refresh rate on the Touch Pro? For example, by applying some kind of graphics configuration changes or something? Perhaps tweaking the graphics driver somehow? Or is it that the standalone TomTom devices have much better hardware and the performance we are seeing on the Touch Pro is about as good as we can expect it?
Any help appreciated!
Cheers,
Ledg3.
Any ideas? Anyone?
Just wondering. have you tried one of the newer roms that have the gps driver cooked in? i am using provens 1.06 and it seems to not lag as much (only tried it for about 15 minutes earlier today)
Hi ajmoncrief,
Thank you for your reply.
I haven't tried any ROMs at this stage as I received my Touch Pro just recently.
Is it possible to load the new GPS driver without replacing the ROM?
Also, does your new GPS driver lag less than 1-2 seconds whilst driving?
At the moment, I would be surprised as TomTom only updates my display every 1-2 seconds, even just by running a demo (and not relying on the GPS for input).
I'm not sure about a driver cab...I would assume that theres one floating around. Check out Da G's rom thread and qsqa's PROven's thread. I tested tomtom again this morning and I'm getting much better results now. I'm not exactly sure how fast/slow the screen refreshes, but it does do so in a timely manner. Im confident that it does do better than once every 1-2 seconds. (I only live 3-6 miles from everywhere I need to go and I dont have any out of town trips within the next couple of days) Maybe someone else can chip in on their thoughts here.
TomTom 7.9 slow refresh
I am having the same problem on the AMEO (X7500) and TomTom 7.9 - screen refresh is quite slow, every 2 seconds. Version 6 was running realy smoothly. Any ideas? Soft reset, restart, speed camera warning on-off does not change the refresh rate.....
Luk
Your position on the map is always going to be a second or two behind your actual position. There is no bottleneck or slowdown even if you set the GPS at 4800 baud. The GPS only sends out a position update once a second. This will also make the screen a little jerky. Most programs smooth out the jerkiness by assuming there will not be a huge change in speed and smoothly move you to where they estimate the next GPS position will be.
Some programs also cheat and estimate your actual position on the map, so it is very close to your actual position. You can tell, because in the city you will be shown going through the intersection when you make a turn. It will then jump backwards and then show you making the turn. One of the GPS programs I use to have did this, but I do not remember which one.
TT7 on my Kaiser (ATT Tilt) moves smoothly along, and is near dead on for location. There's no refresh problems.
TT7 on my Raphael (ATT Fuze) repaints the screen every 1 - 4 seconds, and my position is off by at least 100 feet. Even with tweaks, it functions pitifully compared to the Kaiser.
is everyone here using the VGA version of TT7 or the QVGA version meant for the Tilt?
there are different versions (vga and qvga)??????????
Have you tried Franson GPS gate? DOwnload the trial and create a virtual com port 2 and map the Com4 GPS multiplexer to virtual com 2 and then have tom tom look to com 2 for the GPS. I bet the lag goes away. I was told that the commercial GPS softwares look for standardized GPS info in which the HTC phones' GPS use a variation which causes lag problems.
tomtom 7.910 screen redraw problem
Yes there are different versions of 7.910.9185 blue, black qvga and there is VGA version. I have the problem with the screen redraw, not the general speed, which is better than 7450 for example for route calculation. Screen redraw on 7.450 version was running smoothly, so it is not the question of the GPS, but the maps form 7.910 are not compatible with the 7.450. Screen redraw problem is visible even in demo mode, at 200% of speed instead of the smooth ride you have a "slideshow" in 7.910 version
lukasz said:
Yes there are different versions of 7.910.9185 blue, black qvga and there is VGA version. I have the problem with the screen redraw, not the general speed, which is better than 7450 for example for route calculation. Screen redraw on 7.450 version was running smoothly, so it is not the question of the GPS, but the maps form 7.910 are not compatible with the 7.450. Screen redraw problem is visible even in demo mode, at 200% of speed instead of the smooth ride you have a "slideshow" in 7.910 version
Click to expand...
Click to collapse
I was using 7.450 but i read that version was for qvga devices so i upgraded to 7.451 i know it seems stupid for a .001 update but that is vga not sure about 7.910 as i read that it was vga to and for the diamond if im not mistaken but you can try 7.451 if you want. look around for it also if the map works for 7.450 i don't think it will work for 7.451 or at least it did not work for me. so look for the files if you can't find them drop me a pm and i can tell you where to "BUY" them also i tried the gps reg tweaks and it did not seem to make it any better but i did not have a problem with the gps in the first place. hope this info helps
I've also experienced lag like what you guys are talking about... what I did was I disable all POI in preference so that nothing will show up and it seemed to be a lot faster... still has that choppyness... but much better than before... i hope this helps...
Anyone has this 7.450 Tom Tom VGA Cab? Thnx in advance
bruceo said:
Have you tried Franson GPS gate? DOwnload the trial and create a virtual com port 2 and map the Com4 GPS multiplexer to virtual com 2 and then have tom tom look to com 2 for the GPS. I bet the lag goes away. I was told that the commercial GPS softwares look for standardized GPS info in which the HTC phones' GPS use a variation which causes lag problems.
Click to expand...
Click to collapse
How sure are you about this solution? Have u tried?
If it works, it means TomTom is at fault here, and not HTC
But it also lags in Google maps....how would you explain that?
I am very curious if anyone has really tried this and can confirm the lag going away (and most important; make pedestrian mode usable)
Moaske said:
How sure are you about this solution? Have u tried?
If it works, it means TomTom is at fault here, and not HTC
But it also lags in Google maps....how would you explain that?
I am very curious if anyone has really tried this and can confirm the lag going away (and most important; make pedestrian mode usable)
Click to expand...
Click to collapse
Sadly the HTC really is fault here, not TomTom. I have a external SirfIII GPS module, and while TOmTOm still appears to redraw 2-3times a second, the lag goes away. And TomTom is very very accurate then. The Franson GPS gate doesnt solve anything with the lag. It might make GPS lokc quicker, but tbh it didnt help me much (using QuickGPS data). I get fast locks with both the built-in and the external GPS. The problem is between the data output and the chipset. Drivers should / or could solve it.
Problem solved!
Hello,
Yes I have been experimenting A LOT with TomTom. I have found out that what really slowes down the map redraw is the RADARS if they are inserted into the map directory as a POI. Without radars it runs very nice both in version 7.45 and 7.9.
TT redraws screen very slow even if you switch off the warning for getting close to the radars as POI categories, I think that it is much too many of them for the whole Europe and POI mechanism is not the proper one for radars. Changing the radars into the official "with serial" solved the situation. I hope it helps to the others!
Tom Tom Lag
Aside from the initial startup (I wait about 30 sec) everything seems to work well. Refreshes good, etc.
I use the following settings:
Ver: TTN_7.450.9028
Map Pack: USA_and_Canada_v.675.1409
Other NMEA Device
Baud 19200
COM 4
HTC Radio: Raphael Radio 1.08.25.20M1
I have the AGPS UN-Checked
pabent said:
Aside from the initial startup (I wait about 30 sec) everything seems to work well. Refreshes good, etc.
I use the following settings:
Ver: TTN_7.450.9028
Map Pack: USA_and_Canada_v.675.1409
Other NMEA Device
Baud 19200
COM 4
HTC Radio: Raphael Radio 1.08.25.20M1
I have the AGPS UN-Checked
Click to expand...
Click to collapse
Thanks for the tip, I just updated to this radio from 1.02.25.28 and my GPS seems to be working much much better!
Hi
Can anyone tell me how to work out if TomTom is actually using QuickGPS data?
On my old phone (which also had QuickGPS) when I went into the GPS details immediately after loading TomTom I'd see loads of satalites listed on the histogram before I actually got a lock. Now when I do a cold start they don't show until I've got a lock. For a warm start they do show and I get a very quick lock, but I'm guessing the QuickGPS data is more for speeding up the cold starts.
Also does anyone know if it makes a difference whether I choose "Internal GPS Device" or "Othe NMEA Device"? Either seems to work
Thanks
Dan
Timed testing?
dancj said:
Can anyone tell me how to work out if TomTom is actually using QuickGPS data?
Click to expand...
Click to collapse
When the HTC TyTN II WWE WM 6.1 upgrade that wasn't first came out and GPS performance fell through the floor, there was speculation that QuickGPS wasn't doing its thing and that this was (at least part of) the reason for the very poor GPS performance and extended times to get a lock. Short of timed testing to achieve a satelite lock which isn't conclusive, I'm not aware of a way to prove that the data is being used by Tomtom or any other navigation software but it might be worth reviewing/searching among some of those past threads on the topic. Theres also alot of discussion in the Raphael forum about poor GPS performance on some Touch Pro devices and some of that is at 'nuts and bolts' level.
On my old phone (which also had QuickGPS) when I went into the GPS details immediately after loading TomTom I'd see loads of satalites listed on the histogram before I actually got a lock. Now when I do a cold start they don't show until I've got a lock. For a warm start they do show and I get a very quick lock, but I'm guessing the QuickGPS data is more for speeding up the cold starts.
Click to expand...
Click to collapse
Yes it is. Have a read of the Kaiser GPS Enhancement Guide for some general information in this field but a seach should also yield LOTS on the topic.
Also does anyone know if it makes a difference whether I choose "Internal GPS Device" or "Othe NMEA Device"? Either seems to work
Click to expand...
Click to collapse
I had it suggested to me (by HTC) to use the latter and configure the port manually but after much trialling this, I found it didn't fix the problem of poor GPS performance and as far as I was concerned was a waste of time. Given the version of Tomtom Navigator 6.032 was a special one co-developed with HTCs assistance for their devices, I cant see why changing away from 'Internal' should be benificial. In the end my slow fix fix only came with reverting to WM 6.0 for me. I believe some later WM 6.1 ROM/Radio/SPL combinations now offer GPS performance which is much better than earlier WM 6.1 implementations but as these aren't (yet) available through HTCs UK website for my device and I know what I currently have works very well, I'm staying with the official WM 6.0 setup for now. My device is out of warranty, so one day I may try another setup for comparison (say the latest Hong Kong WWE ROM/Radio/SPL).
Thanks - I'm experimenting with radio at the moment and I have managed to get some improvement, but it's annoying not being sure if QuickGPS is really working
dancj said:
Thanks - I'm experimenting with radio at the moment and I have managed to get some improvement, but it's annoying not being sure if QuickGPS is really working
Click to expand...
Click to collapse
Have you seen this thread about Hopeless GPS after WM 6.1 update yet? Since you're in the UK I'm interested to know how your GPS under WM 6.1 with your fairly new Radio is performing. What sort of times do you get standing still out in the open to get a 'cold' satelite lock? Have you tested with that 1.71xxxx eMO Radio as well? I believe the SPL version can also make a difference to GPS performance but I don't know any more about why that is.
In the last couple of days I've tried the 1.70.19.09 and 1.70.18.02 radios. They seem to have a much better GPS performance than 1.58.25.17 which I was on before. It's only been a couple of days though so I can't be 100%