Related
After reading may threads on here about people not being able to get TomTom working with US maps once they have upgraded to v5.21 I thought I would look in to a way around the troubles.
Here is what I think peoples problems are:
1. Bluetooth GPS could not be paired under TomTom v5.00
2. Cracked versions of maps or even maybe real v5 maps of the US don’t work under v5.21
People want US maps AND Bluetooth GPS i.e. numbers 1 AND 2, but can't find a way to have their cake and eat it.
After many installs and trials of TomTom v5 and v5.21, I think I have just hit upon a solution. The basis of the problem is that TomTom v5 does not let you use a COM port that your Wizard lets you set, so how do you fix this.....
- I installed TomTom v5 as per the many sets of instructions on the forums, ie copy CAB files to your SD card and install.
- Next pair your BT GPS to COM port 8.
- Run TomTom and set up as normal, when you get to the GPS setup, select COM port 2
- Close TomTom
- Copy navigator.cfg (installed in /Program Files/Navigator) to your PC
- Using a hex editor edit navigator.cfg
- Change ONLY the entry for the number after the work COM to 8 (or what you set the COM port to above)
- Copy the file back to the original location
- start TomTom
You should see that the BT GPS is now recognised; also you should see that you can select all the maps that you have installed.
I have not tested that the BT GPS works in the UK and the US ‘cos I can’t be in 2 places at once, but I hope that some of the US users can verify this before I move out mext month.
Let’s hope this is the final answer I have been looking for
Wow. That's great, thanks for that.
i've just spent the last week with the Bluetooth problem, only to realise about an hour ago that I had the answer all along and I was just too stupid to realise.
In case anyone out there has been battering their head on their laptop in frustration (and is similarly mentally challenged as myself), I have a hint for those using the not entirely legal version of TT.
If you have the one marked 5.21 or have one which has 5.00 and 5.21 exe files in the zip somewhere, you need to copy across the cabs (as described on many forums - I have messed about so much I can't describe a full process to get to where I am now but I'll try to summarise below)
Once the cabs are copied, version 5.00 will work OK but will have the BT COM port problem.
Then stick the 5.21 cracked exe into the Program Files\Navigator folder ( i did not delete the old one, just renamed it incase it went wrong) and then when you run the new one it runs as before but with the COM port options.
My mistake was when I first got the files, I tried running the exe on my PC and in the phone. It doesn't work until you have the cracked 5.00 app already working and only then if you stick it into the Navigator folder.
Sorry if this is just stupid but I have browsed god knows how many forums over the past 2 weeks and so many people seem to be having similar problems (some with genuine tomtom and some not saying but hey, if they had paid for it in the first place the upgrade would be easy, right??).
I'll try to summarise the steps I took to get mine working (these are my best guess of the basics to get it working, skipping the hundred other things i have tried which failed to help.
1. installed cabs (WZD, GPS, PINAddIn & my desired Voice) from pocketpc and voice folder BUT had problem with ttn cab as just gave 'unsuccessful' message
2. Copied maps into storage card in their respective folders (NB apparently need to have at least 2 maps to get it to recognise them, if you only have one just copy the folder and rename one of them)
3. Downloaded WinCE Cab Manager (freeware for first 15 uses) from OCP
4. Opened ttn.cab in WinCE Cab Manager and extracted exe and data.chk file and put into Navigator folder in Program Files
at this point the 5.00 version should load, set up maps and voice and works fine apart from GPS
5. Rename (or delete) the TomTom Navigator.exe and replace it with the 5.21 one from the cracked folder.
all the GPS stuff should be easy from there as COM port 6 should show up (and is covered elsewhere anyway)
I think that's the essential points. There is a lot of superflouous stuff that comes with TomTom that you don't need to get the main function working so that's why there is a minimum of installs.
If there's anything I missed, please correct me.
Anyway, I am now only 1 step away from being able to us the darn thing after 2 weeks of trying.
The main reason I got it was to navigate in Germany when I go on holiday in June as I have a few serious days of driving and want to be able to navigate easily.
I have been able to get my Germany and Great Britain maps working fine but as I live in Australia, I want to get used to using TomTom now with my Australia maps...BUT THEY WILL NOT LOAD!!!
They show up on the screen when I pick my maps but the screen just freezes when i select Australia.
Any ideas???
Heres a navigator.cfg already set to use com port 7.
Anyone with v5 can set their outgoing port on the BT device to port 7 and replace their .cfg file with this one and it should work - I just tried it.
Bilbo...you are my new hero.
I'm really glad to know that my $100 and 4 hours of hacking around with this thing weren't all in vain. Thank you SO much.
<3 <3 <3 8)
hi pewe,
thanks for the post. have got the same com port problems and breaking my head over it trying to get a rikaline gps work. could please please post a detailed answer on what to do with the file u have posted. i copied the file over the one i had in the pda but now have lost com port 4 and no 7 has appeared. please help
cheers, many many thanks.
pewe said:
Heres a navigator.cfg already set to use com port 7.
Anyone with v5 can set their outgoing port on the BT device to port 7 and replace their .cfg file with this one and it should work - I just tried it.
Click to expand...
Click to collapse
hi weevel,
looked at your post. have the same problem. would have a copy of the cracked 5.21 exe. cant seem to find one and unable to work my tomtom. have got the cracked 5.0 working properly but no gps. pleeeeeeease help.
cheers.
weevel said:
Wow. That's great, thanks for that.
i've just spent the last week with the Bluetooth problem, only to realise about an hour ago that I had the answer all along and I was just too stupid to realise.
In case anyone out there has been battering their head on their laptop in frustration (and is similarly mentally challenged as myself), I have a hint for those using the not entirely legal version of TT.
If you have the one marked 5.21 or have one which has 5.00 and 5.21 exe files in the zip somewhere, you need to copy across the cabs (as described on many forums - I have messed about so much I can't describe a full process to get to where I am now but I'll try to summarise below)
Once the cabs are copied, version 5.00 will work OK but will have the BT COM port problem.
Then stick the 5.21 cracked exe into the Program Files\Navigator folder ( i did not delete the old one, just renamed it incase it went wrong) and then when you run the new one it runs as before but with the COM port options.
My mistake was when I first got the files, I tried running the exe on my PC and in the phone. It doesn't work until you have the cracked 5.00 app already working and only then if you stick it into the Navigator folder.
Sorry if this is just stupid but I have browsed god knows how many forums over the past 2 weeks and so many people seem to be having similar problems (some with genuine tomtom and some not saying but hey, if they had paid for it in the first place the upgrade would be easy, right??).
I'll try to summarise the steps I took to get mine working (these are my best guess of the basics to get it working, skipping the hundred other things i have tried which failed to help.
1. installed cabs (WZD, GPS, PINAddIn & my desired Voice) from pocketpc and voice folder BUT had problem with ttn cab as just gave 'unsuccessful' message
2. Copied maps into storage card in their respective folders (NB apparently need to have at least 2 maps to get it to recognise them, if you only have one just copy the folder and rename one of them)
3. Downloaded WinCE Cab Manager (freeware for first 15 uses) from OCP
4. Opened ttn.cab in WinCE Cab Manager and extracted exe and data.chk file and put into Navigator folder in Program Files
at this point the 5.00 version should load, set up maps and voice and works fine apart from GPS
5. Rename (or delete) the TomTom Navigator.exe and replace it with the 5.21 one from the cracked folder.
all the GPS stuff should be easy from there as COM port 6 should show up (and is covered elsewhere anyway)
I think that's the essential points. There is a lot of superflouous stuff that comes with TomTom that you don't need to get the main function working so that's why there is a minimum of installs.
If there's anything I missed, please correct me.
Anyway, I am now only 1 step away from being able to us the darn thing after 2 weeks of trying.
The main reason I got it was to navigate in Germany when I go on holiday in June as I have a few serious days of driving and want to be able to navigate easily.
I have been able to get my Germany and Great Britain maps working fine but as I live in Australia, I want to get used to using TomTom now with my Australia maps...BUT THEY WILL NOT LOAD!!!
They show up on the screen when I pick my maps but the screen just freezes when i select Australia.
Any ideas???
Click to expand...
Click to collapse
but no gps
Click to expand...
Click to collapse
Have you tried V5 with the navigator.cfg fix discussed here
http://forum.xda-developers.com/viewtopic.php?t=46828&postdays=0&postorder=asc&start=0
hi pewe,
is it the reg editing u are reffering to in that forum. please let me know.
cheers
pewe said:
but no gps
Click to expand...
Click to collapse
Have you tried V5 with the navigator.cfg fix discussed here
http://forum.xda-developers.com/viewtopic.php?t=46828&postdays=0&postorder=asc&start=0
Click to expand...
Click to collapse
You can try that - but the easiest solution to try first is the one where you set the GPS in TT to any port, setup the BT device config to outgoing port 7 then replace the navigator.cfg. That seems to work for most people.
hi pewe,
another small issue. us maps dont work with 5.21 upgrade. is it a question of downgrading to v5 before a trip and borrowing a friends tomtom reciever to work there and come back change again or is there anither way.
cheers
I have tried that with my Cinular 8125 (WM5), in TOMTOM set the gps to com 2 then switch the cfg file adn it still doesnt work, i have MS streets and maps working fine, so i know the GPS is good.
I have a new idea lets work with 5.21 and see see what version map it reads then edit our usa maps and change the version. Has anyone tried this, ive been looking all over for a TOMTOM map editior, but no luck. I have all the USA maps so if you need one let me know
pewe said:
Heres a navigator.cfg already set to use com port 7.
Anyone with v5 can set their outgoing port on the BT device to port 7 and replace their .cfg file with this one and it should work - I just tried it.
Click to expand...
Click to collapse
Hi,
Have tried replacing my cfig file with the one you supplied but this hasnt worked...my version of tomtom however appears to be 5.1
Do I need a different Cfig file for this version ?
Many thanks
Steve
Do I need a different Cfig file for this version
Click to expand...
Click to collapse
Not sure - I've never used V5.1.
What com ports does TomTom offer you when you try to configure the BT device?
pewe said:
Do I need a different Cfig file for this version
Click to expand...
Click to collapse
Not sure - I've never used V5.1.
What com ports does TomTom offer you when you try to configure the BT device?
Click to expand...
Click to collapse
Config within Tomtom offers -
COM9:
Infrared Port
COM3:
COM0:
COM2:
Serial Port
These are the 'normal' options - so I can't understand why it doesnt work.
Are you sure that the BT is setup on your device as com port 7?
If it is and it doesn't work, try setting it to com port 6 and try this config file.
pewe said:
These are the 'normal' options - so I can't understand why it doesnt work.
Are you sure that the BT is setup on your device as com port 7?
If it is and it doesn't work, try setting it to com port 6 and try this config file.
Click to expand...
Click to collapse
Certain my BT device was set to Com port 7, still tried this alternative Cfg. file and changed port to 6 with the same result in that options within tomtom remain unchanged as stated before (assume the expected result should be to provide additional Com ports within tomtom Configure screen to enable selection of Com port 6 ?)
Not sure then.
Maybe V5.1 has some differences about it.
pewe said:
Not sure then.
Maybe V5.1 has some differences about it.
Click to expand...
Click to collapse
Cheers anyway...
Other forums suggest that installing the V5.2 update from tomtom will fix the comm port bug....not sure however if this will wreck all the files I have so painstakingly installed. Any ideas if running the tomtom update is safe ?
Not sure - it depends what you have installed. Some have reported problems with Maps from V5/V5.1, but mainly in the US. Mine went from V5 to V5.2 without a problem.
If you backup everything before you upgrade you can always re-install..
How to get TOMTOM Working with UK and USA Maps
I have TOMTOM 5.21 on IPAQ in the UK and wanted to load the Michigan Map for a business trip that I have next month.
Having downloaded the USA Maps I spent all day trying to get TOMTOM to recognise the USA Map with no luck.
Read all the forums and tried one or two tips but to no avail. Then I tried something quite simple.
1. Install all the way to 5.21 in order to get Bluetooth GPS working. Once done this makes the correct .CFG file.
2. Simple back up the 5.21 executable or rename.
3. Copy the cracked 5.0 executable into the navigator directory. Voila ! It retains the Bluetooth settings AND it allows me to load the USA maps.
Wont be able to properly confirm the USA maps work 100% till next month but UK map work just fine and when I load the michigan map it lets me browse but cannot plan a trip cos GPS says I am out of the scope of the map.
So looking good.
Hi all,
For everyone with the problem with TomTom Navigator whereby it only announces part of the directions, attached is a small application which provides a workaround.
It works by playing a short silent WAV file in a loop in the background, starting TomTom then shutting itself down automatically once TomTom is closed. This is basically the same mechanism as mentioned on another thread whereby a silent MP3 is played through a script in an external MP3 player but written as a self-contained program.
To run TomTom with the fix:
If you don't already have it, first install the Microsoft .NET 3.5 Compact Framework. Available as a cab here: http://www.megaupload.com/?d=2ZGV1DNJ.
Unzip the attached TomTom Audio Fix.zip and copy TomTom Audio Fix.exe into your TomTom Navigator directory e.g. "\Program Files\Navigator". You can then just run TomTom Audio Fix.exe which will automatically start TomTom.
This has been tested on TT 7.910 (9185) and 7.915 (9196), please post here if you try it out with whether it's working ok or you run into any problems!
Updates
v1.10:
- Icon refreshed, now displaying correctly.
- When run, TomTom Audio Fix.exe will now automatically generate a "TomTom Navigator.lnk" shortcut in the current directory. This can be copied directly over the installed TomTom shortcut in the start menu; saving the need to manually create a shortcut to the fix.
v1.11:
- Thanks to Mr_Q, this is now provided as a .cab file:
º Automatically copies file to TomTom Navigator directory and overwrites the shortcut in the start menu.
º Install the cab in the same location as you installed TomTom (eg. Storage Card), else it won't work.- Removed redundant change from 1.10 which created the TomTom Navigator shortcut.
Regards,
JDH
Brilliant. Thanks very much to you and those who figured out what the workaround was. Just goes to show what a marvellous place this Internet can be!
Filbert
Good work! Thanx a lot! I'll try it immediately.
Works really good on TT 7.915.9196
Thanx again.
What´s .NET 3.5 Compact Framework?
@JohnnyDH
Do I understand it right, after installing the fix I have to start the fix from explorer and TT will start automatically??
In that case is there a chance for a shortcut in programm directory? That would make it more easy than starting the programm everytime from explorer.
Thanks for the answer.
Rodgauman
Beside my question one post before, the fix worked fine. Only a shortcut would be fine.
I tried to copied the fix into windows\startmenue folder, but then the correct path will not be found.
I have navigator on my storage card installed. Path is in german:
Mein Gerät\Speicherkarte\Programme\Navigator
When I start the fix from there it works fine.
Thanks a lot JohnnyDH! This really does work great. Can I make a request? Would it be possible to change the icon of the file as it is of pretty bad quality now. I'd appreciate it very much.
@rodgauman
You will need to manually edit the TomTom shortcut in your windows\startmenue folder. Copy the TomTom Navigator.lnk file from the start menu to your PC, open it with a text editor, and change where it says "TomTom Navigator.exe" to "TomTom Audio Fix.exe" e.g. I changed mine from:
47#"\Program Files\Navigator\TomTom Navigator.exe"
to:
47#"\Program Files\Navigator\TomTom Audio Fix.exe"
Save the changes and copy it back replacing the original file. Unfortunately there are too many installation locations / languages etc for me to automate this!
@daffie
Not a problem, glad it is working for you! Good spot on the icon, it was extracted directly from TomTom Navigator.exe and I hadn't noticed. I will upload an updated version at some point in the next couple of days to give a few more people a chance to test it in case any fixes are required.
thank you man.
it worked for me too...tomtom 7.915.9196
@JohnnyDH
Thanks again, editing of shortcut worked fine!
Beside that I learned how to create a shortcut for other programms.
Great Job!
Thanks JohnnyDH
Work fine version 7.915.
JohnnyDH said:
@rodgauman
@daffie
Not a problem, glad it is working for you! Good spot on the icon, it was extracted directly from TomTom Navigator.exe and I hadn't noticed. I will upload an updated version at some point in the next couple of days to give a few more people a chance to test it in case any fixes are required.
Click to expand...
Click to collapse
Thanks a lot, I really appreciate it! Today I did a testrun using TT7 and the voice now works like a charm...very happy about this fix!
Its working like a charm. Theres only one thing I noticed. When TomTom is started, it starts muted. Is this how its supposed to be?
have been waiting so anxiously for a TT voice patch! Many many thanks!!!
ps creating a high resolution icon would be nice, since it looks so ugly on new HTC program menu
Thanks a lot....this bug has been driving me crazy...works on TomTom7.450
Thank you JohnnyDH,
i use it with TTN7.915.9196 vga black. You save my Life
Awesome.
Thanks a lot man !
@ Johnny DH
thanke u very much ... i already fix it... Finayly...i really appreciated..
TomTom Audio Fix v1.10 works like a charm!
Kudoos to you
Thankyou! this worked perfectly
In order to have both TTS and Contact POI's working in iGO8 you're going to need two different versions of iGO8.
FIRST VERSION NEEDED: iGO8 v8.32.64029 (Nov 7 2008)
This version is designed for the PDA, and as such is able to geocode contact information. Install this version with the attached 64029sys.txt
At this point if everything is done correctly, iGO8 should boot normally BUT be VERY slow and unresponsive. This is GOOD! This is iGO8 Geocoding your contacts. Depending on the quantity of contacts with addresses you have, this could take a VERY long time. When it is done you will get a message similar to the following:
Geocoding finished with errors. 38 of 110 addresses found, 72 failed. Do you want to see the details?
At this point you could see the details of the errors, which will show you all of the addresses that are not entered into Outlook in a iGO8 palatable way. You could just ignore them and be happy with what you have (unlikely), or go back into Outlook, correct the formatting errors, and try again (and continue your suffering).
This can be VERY tedious... iGO is one picky bastard. You might even have to input the addresses into iGO as destinations, see how iGO formats the addresses, and then change the Outlook contacts to match the format iGO uses for a particular address.
I have even heard that contact need to be deleted and reentered into Outlook in the proper iGO8 fashion or you will continue to get errors for particular contacts.
SYNTAX ADVICE:
not Blvd. --> Blvd (The little "." will throw an error every time)
not Blvd --> Boulevard ("Usually" iGO dislikes abbreviations)
not N. --> N --> North (This is hit or miss)
NEVER use apt# (just give up and don't try)
NO Suite # (same as above)
If you have to have apt or suite #'s AND you want iGO to geocode, then the only way to get it both ways is to use the "OTHER" address in Outlook to place the iGO friendly address and the correct address in the "Business" or "Home" Outlook address. The ones with apt or suite # will error, but the second addresses in the "Other" address without the apt or suite # will geocode as POI's fine.
When you are done, you will be left with this little piece of GOLD... YOUR CONTACT POI's FILE ! ! !
\iGO8\save\gccache.dat
You'll want to back this file up somewhere else for safe keeping. We don't want all this hard work to go to waste.
SECOND VERSION NEEDED: iGO8_v8.3.4.102680 (Aug 13 2009)
This is the newest PNA version that does not have the ability to geopcode contact POI's, but it is able to read the gccache.dat file created by the PDA version above AND it is capable of TTS. Install this version with the attached 102680sys.txt
You will need to install this version and simply place the gccache.dat into the iGO/save folder and iGO will do the rest for you.
Now getting iGO8 to reliably run TTS is a different story. TTS requires ALOT of RAM to run. If there is not enough RAM available (~115-120mb), then it will simply refuse to play TTS voice prompts and you will be stuck with standard voice prompts. To free up a good chunk of the necessary RAM install both NOPushInternet_v2.cab and SSK TP2 Dynamic Resource Proxy.cab. To get the rest your available RAM to acceptable levels you will need to disable TF3D, run CleanRAM, and then start iGO.
Sounds complicated? Well, fortunately itsachirpthing over at PPCGeeks has created a nice little script that does just this. The original post can be found HERE. And the original thread can be found HERE. I recommend reading both these original threads. They have additional information to get iGO8 working properly on TP2.
itsachirpthing @ PPCGeeks said:
I have a custom mort script that will turn off TF3D, run CleanRam (I have custom process enabled to exit Opera and Tmail within CleanRam), then run Igo8. Once you are finished with Igo and you exit, TF3D will restart. This took some testing, but this works everytime with the high quality TTS voices. I have had no issues. I have posted the code below, this will work on your device providing that you install CleanRam to your "device" and your IGo program is listed as "\storage card\iGO8\igo8.exe". These HQ TTS voice issues baffled me for months, but now they work consistently without a soft reset.
Again this code will stop TF3D, Run CleanRam, Start Igo... then when you exit iGo it will restart TF3D.
manilastate=ProcExists("manila.exe")
If (manilastate)
Kill("biotouch.exe")
RegWriteDword ("HKLM","Software\Microsoft\Today\Items\TouchFLO 3D","Enabled",0)
RedrawToday
endif
RunWait("\program files\htcaddicts cleanram\htcaddicts_cleanram.exe")
RunWait("\storage card\iGO8\igo8.exe")
Sleep(5000)
Kill("Repllog.exe")
While ( ProcExists("igo8.exe") )
IdleTimerReset
Sleep(500)
EndWhile
If (manilastate)
RegWriteDword ("HKLM","Software\Microsoft\Today\Items\TouchFLO 3D","Enabled",1)
RedrawToday
Run("\windows\biotouch.exe")
endif
I have attached the script to run with mort script. I hope others can benfit as well. Good luck and enjoy!
Click to expand...
Click to collapse
I have added this iGO script to the MortScript.cab posted here. You need it and CleanRAM.cab. Install both to the device, not the SD Card. Then just click on the Plain iGO Scipt icon in the Start Menu. The script will close TF3D, run CleanRAm, start iGO8, and when iGO8 is exited, it will start TF3D again
Inaddition to the above Script, you will need to install both NOPushInternet_v2.cab AND SSK TP2 Dynamic Resource Proxy.cab
in order to free up enough RAM. But with the above script, CleanRAM, and these two cabs, you should have enough RAM to run TTS of TP2. These CAB's are attached.
The sys.txt files attached are what works for my ATT TP2. It took many hours to find the correct setting for each iGO8 version and I am providing them to make your process easier. If they don't work or you get some other error for what ever reason... I AM PROVIDING NO TECH SUPPORT. This is simply information for your use.
Good Luck!
PS. This works best if you have two micro SD cards. One for each version of iGO. That way if you add new contact address, you can simply pop out one card, geocode the data, and transfer the new gccache.dat file to the other card.
PPS. Once you do get everything working in iGO 8 properly.... DO NOT MESS WITH ANYTHING ANYMORE!!! iGO8 is one finicky bastard and will throw a TTS temper tantrum (refuse to load TTS) if you do... I know ALL TOO WELL!
DONT ASK ME FOR COPIES OR WHERE TO GET THE ABOVE PROGRAMS....
BUY THEM or USE SOME CREATIVITY.... like GOOGLE!
Hi:
Thanks for the great info. I have a few questions. The Mortscript seems to run clean RAM, and disable TF3D, but then TF3D starts back up on its own. Is this normal?
Also, is the script supposed to also start iGo, or must this be done manually; script did not start iGo for me.
Thanks again!!
The script is as written above. If the location of iGO8.exe is not where the script is pointed you 'll have issues.
RunWait("\storage card\iGO8\igo8.exe")
If you do not have a iGO8.exe in the above folder, you'll need to just make a second copy of application.dat in the same folder and rename it iGO8.exe. They are the same file, just different names.
Hi:
Thanks so much for your help. You were absolutely right, my .exe was in Storage Card/Program Files.
It is working well now.
Unfortunately it didn't make TTS work for me, but I have had problems with it for a LONG time, and never been able to find a fix.
Thanks anyway for everything
cincy1020 said:
Hi:
Thanks so much for your help. You were absolutely right, my .exe was in Storage Card/Program Files.
It is working well now.
Unfortunately it didn't make TTS work for me, but I have had problems with it for a LONG time, and never been able to find a fix.
Thanks anyway for everything
Click to expand...
Click to collapse
Were you using the above mentioned iGO versions? If not... I wouldn't know.
lokmeup said:
In order to have both TTS and Contact POI's working in iGO8 you're going to need two different versions of iGO8.
FIRST VERSION NEEDED: iGO8 v8.32.64029 (Nov 7 2008)
This version is designed for the PDA, and as such is able to geocode contact information. Install this version with the attached 64029sys.txt
At this point if everything is done correctly, iGO8 should boot normally BUT be VERY slow and unresponsive. This is GOOD! This is iGO8 Geocoding your contacts. Depending on the quantity of contacts with addresses you have, this could take a VERY long time. When it is done you will get a message similar to the following:
Geocoding finished with errors. 38 of 110 addresses found, 72 failed. Do you want to see the details?
At this point you could see the details of the errors, which will show you all of the addresses that are not entered into Outlook in a iGO8 palatable way. You could just ignore them and be happy with what you have (unlikely), or go back into Outlook, correct the formatting errors, and try again (and continue your suffering).
This can be VERY tedious... iGO is one picky bastard. You might even have to input the addresses into iGO as destinations, see how iGO formats the addresses, and then change the Outlook contacts to match the format iGO uses for a particular address.
I have even heard that contact need to be deleted and reentered into Outlook in the proper iGO8 fashion or you will continue to get errors for particular contacts.
SYNTAX ADVICE:
not Blvd. --> Blvd (The little "." will throw an error every time)
not Blvd --> Boulevard ("Usually" iGO dislikes abbreviations)
not N. --> N --> North (This is hit or miss)
NEVER use apt# (just give up and don't try)
NO Suite # (same as above)
If you have to have apt or suite #'s AND you want iGO to geocode, then the only way to get it both ways is to use the "OTHER" address in Outlook to place the iGO friendly address and the correct address in the "Business" or "Home" Outlook address. The ones with apt or suite # will error, but the second addresses in the "Other" address without the apt or suite # will geocode as POI's fine.
When you are done, you will be left with this little piece of GOLD... YOUR CONTACT POI's FILE ! ! !
\iGO8\save\gccache.dat
You'll want to back this file up somewhere else for safe keeping. We don't want all this hard work to go to waste.
SECOND VERSION NEEDED: iGO8_v8.3.4.102680 (Aug 13 2009)
This is the newest PNA version that does not have the ability to geopcode contact POI's, but it is able to read the gccache.dat file created by the PDA version above AND it is capable of TTS. Install this version with the attached 102680sys.txt
You will need to install this version and simply place the gccache.dat into the iGO/save folder and iGO will do the rest for you.
Now getting iGO8 to reliably run TTS is a different story. TTS requires ALOT of RAM to run. If there is not enough RAM available (~115-120mb), then it will simply refuse to play TTS voice prompts and you will be stuck with standard voice prompts. To get your available RAM to acceptable levels you will need to disable TF3D, run CleanRAM, and then start iGO.
Sounds complicated? Well, fortunately itsachirpthing over at PPCGeeks has created a nice little script that does just this. The original post can be found HERE. And the original thread can be found HERE. I recommend reading both these original threads. They have additional information to get iGO8 working properly on TP2.
I have added this iGO script to the MortScript.cab posted here. You need it and CleanRAM.cab. Install both to the device, not the SD Card. Then just click on the Plain iGO Scipt icon in the Start Menu. The script will close TF3D, run CleanRAm, start iGO8, and when iGO8 is exited, it will start TF3D again
The sys.txt files attached are what works for my ATT TP2. It took many hours to find the correct setting for each iGO8 version and I am providing them to make your process easier. If they don't work or you get some other error for what ever reason... I AM PROVIDING NO TECH SUPPORT. This is simply information for your use.
Good Luck!
PS. This works best if you have two micro SD cards. One for each version of iGO. That way if you add new contact address, you can simply pop out one card, geocode the data, and transfer the new gccache.dat file to the other card.
Click to expand...
Click to collapse
i tried this and all i have to say is ............THANKS!!!! this is the missing piece to my tilt2...i have asked around and no one seemed competent enough to know what i was talking about until now...the 64029 sys text fixed my intial boot up problem and now IGO is good to go...thanks again. God Bless
thesilentnight said:
i tried this and all i have to say is ............THANKS!!!! this is the missing piece to my tilt2...i have asked around and no one seemed competent enough to know what i was talking about until now...the 64029 sys text fixed my intial boot up problem and now IGO is good to go...thanks again. God Bless
Click to expand...
Click to collapse
Your welcome. I am glad my searching, suffering, trial and error have been helpful to others. I felt it would have been a waste of effort, if only my phone was to benefit from the knowledge.
Added both NOPushInternet_v2 and SSK TP2 Dynamic Resource Proxy CAB's...
Need for maximum available free RAM.
lokmeup said:
Were you using the above mentioned iGO versions? If not... I wouldn't know.
Click to expand...
Click to collapse
Hi:
Yes I am using the above mentioned Aug 13th version, but to be honest I have had this same problem since I switches to the R3 versions. Oddly enough, I only get TTS from "Amy", which isn't even a TTS voice, but her voice is limited, and doesn't include things like street names etc... When I try to use "Susan" or "Dave" which are TTS voices, they do not work at all. I have tried a million different TTS packages, as well as sys.txt edits, and still no luck.
I have searched and searched and never been able to fix it.
But anyway, thanks so much for posting your info, I am sure it will help others.
cincy1020 said:
Hi:
Yes I am using the above mentioned Aug 13th version, but to be honest I have had this same problem since I switches to the R3 versions. Oddly enough, I only get TTS from "Amy", which isn't even a TTS voice, but her voice is limited, and doesn't include things like street names etc... When I try to use "Susan" or "Dave" which are TTS voices, they do not work at all. I have tried a million different TTS packages, as well as sys.txt edits, and still no luck.
I have searched and searched and never been able to fix it.
But anyway, thanks so much for posting your info, I am sure it will help others.
Click to expand...
Click to collapse
I recommend reading the threads on PPCGeeks. You might need their recommended BRANDING.ZIP and DATA.ZIP files.
I know it is a pain in the ass... but it can work
but then again it can also stop working right after
Good Luck!
Lokmeup, thanks for the post. I found this by googling Igo8 and contacts... I'm running iGo8 (the most recent pna version) on my Imagio and of course it won't input the contacts.
I plan on following your directions but was wondering if I'll need to keep both versions available and run the PDA version every time I enter a new contact as the PNA version won't import contacts?
I miss the 'navigate to contact' from Tomtom but Tomtom doesn't seem to like the Imagio as it lags out while iGo8 runs fine.
Thanks in advance!
lokmeup said:
PS. This works best if you have two micro SD cards. One for each version of iGO. That way if you add new contact address, you can simply pop out one card, geocode the data, and transfer the new gccache.dat file to the other card.
Click to expand...
Click to collapse
Yes, It is best to keep both versions.
lokmeup said:
Yes, It is best to keep both versions.
Click to expand...
Click to collapse
Thanks and DOH! Didn't see that part about the other card. The damn SD card on the Imagio is behind the back cover and the cover is a beast to remove. I'll try to keep one internal and one external and see if that works. Thanks again!
Update: iGO 8 v8.3.2.97313 (Jul 3 2009) also works for geocoding. You can have one in main memory and one on your SD card and the one in main memory will geocode for the one on the card.
Thanks again Lokmeup, you gave me back the one function iGO was missing over TT!
Not to be a nay sayer, but why in the world do you need to jump through all these hoops to get TTS to work? My TTS works fine on 102680 with Igo as installed, I'm using the Energy 6.5.1 ROM but it's worked with every ROM I've tried it on?
For all of us obsessed with flashing, a lot of chefs are adding Sense instead of just TF3D. Sense will also cause TTS not to work. I have edited the mscr to disable HTC Sense before launching igo8 (and of course renenabling it upon exiting the program)
Two versions:
One that closes Sense then launches igo
The second closes sense, runs clean ram then launces igo
Personally i hate havng to confirm the cleanup, but your choice. Either one works out for me
IMPORTANT: RENAME file extention .txt -> .mscr (xda does not permit me to upoad mscr files)
marscandybars said:
For all of us obsessed with flashing, a lot of chefs are adding Sense instead of just TF3D. Sense will also cause TTS not to work.
Click to expand...
Click to collapse
Unless I'm really confused Energy ROM Phoenix has Sense in it, and it works fine with TTS on my phone without any scripts.
marscandybars said:
For all of us obsessed with flashing, a lot of chefs are adding Sense instead of just TF3D. Sense will also cause TTS not to work. I have edited the mscr to disable HTC Sense before launching igo8 (and of course renenabling it upon exiting the program)
Two versions:
One that closes Sense then launches igo
The second closes sense, runs clean ram then launces igo
Personally i hate havng to confirm the cleanup, but your choice. Either one works out for me
IMPORTANT: RENAME file extention .txt -> .mscr (xda does not permit me to upoad mscr files)
Click to expand...
Click to collapse
rename this file and just run it like the cab file I presume ??
Its working with the Sense file. I just went out and try it out. Would you be able to create a Sense file you created for igo mortcript and the htc addicts clean ram v1.8. ? I can see the other file as a shortcut in the start menu? Would you be able to create the same one for the sense version ?
Thanks.
Hi!
I’ve spent a lot of time trying to get voices to work on tomtom, but everything i do ends up with "There are no voices available. You will no hear any spoken instructions"
I’ve installed 7.916.9189 , 7.916.9189 Blue, qvga.7.916.9189.blue and others and they are all the same.
Just now I have on qvga 7.916.9189
Western_Europe_1GB_840_2561 - maps
USA_and_Canada_840_2561 – maps
And a mega pack of 137 voices
The root of the 16gig SD card is
Map – USA
Map – Euro
TOMTOM – with folders for .exe etc
VOICES >> folder with name of voice >> 3 files (.bmp, .chk, .vif) the numbers of the file are the same as the folders
ZIP – for Uk post codes
I’ve edited the registry for auto rotate and also removed the 2 files to get Bluetooth working.
Can someone please suggest how to get the voices working
Thanks!
Dan
The voices folder shouldn't have any other folders inside it just the data chk,vif and bpm (if there is one) for each voice you want....eg:
Voices........data61,data61.chk,data61.vif,etc
My HKLM/Software/HTC/NaviSW only has (Default), BTMsgState, BTName, MovieState, TaskBarShift and TwoFingerEvent as strings.
I can't see anything in this lot that could possibly load and run any navigation software and my NaviPanel certainly won't load my TomTom navigator software (ApplicationVersion 7917).
TomTom runs just fine normally on my HD2 but won't load through NaviPanel which has only 'Make a Call' available - all the other icons are grayed out...
Any idea on how I get NaviPanel to load and use TomTom?
Thanks.
KennyD
your first post not searched the forum? the answer is around
type tomtom and navipanel in the search and it comes up just like it did for me.
Yep, I've spent a chunk of today searching through this entire forum - but just can't figure out how to get NaviPanel to run my TomTom.
I found a copy of the dll "NaviSWMiddle_TomTom.dll" and dumped that into my \Windows folder (I didn't have any NaviSW dlls there at all) and I created a new registry string named "MiddleLayerDLL" and gave it the value "NaviSWMiddle_TomTom.dll" and soft-reset my HD 2 twice for good measure.
Still nudda. Zip. Zilch. I load NaviPanel and still just get the Phone icon available and all the others are grayed out. No error messages, nothing. Just grayed icons for all the rest. My TomTom is loaded onto my SD card and works perfectly from its own .lnk...
Is there a particular version of the "NaviSWMiddle_TomTom.dll" file I need? I just located the only one I could find on the web and downloaded that.
While I can happily registry edit, editing dll files is a little beyond me.
What am I missing that prevents NaviPanel from loading TomTom?
KennyD
think the problem is the same for any navi program other then copilot.
look e.g. here
http://forum.xda-developers.com/showthread.php?t=641756
this is about iGO but idea is the same it gives a complete solition for TomTom also
I has asked HTC Tech Support and they told me that Navipanel would work ONLY with CoPilot. So this is it unless someone comes with a work-around solution
Fabulous, fabulous, fabulous!
Finally got cooperation out of NaviPanel!
For those still searching -> try the link at //forum.xda-developers.com/showpost.php?p=5789366&postcount=9
I edited the new Config.ini file sitting in the new CoPilot folder to include "Storage Card/" in the pathway before "Program Files/Navigator/TomTom Navigator.exe" and it is now happily functional! (This cured the "-2147479552" error...)
You can have TomTom installed on an SD card and this CoPilot work-around will get NaviPanel to cooperate!
Finally got there! Phew!
KennyD