Intro - skip if you want
When I first got my TomTom I was able to configure it for use with my Nextel iDEN phone for TomTom Services with no problems. DC calls really confused the hands-free feature on my TomTom, so I disabled that. Several months later I switched to Verizon, and configured that phone (with some issues), and somewhere along the line I deleted my iDEN phone from my TomTom configuration.
Jump ahead to last week, and I decided to reactivate my iDEN phone so I can use it instead of my Verizon phone and stop paying Verizon $30 a month for tethering. Much to my dismay, I discovered that the current device software (8.300) doesn't allow you to enter anything but numbers and a few special characters in the dial string. This is a problem because my iDEN phone uses a dial string of "s=2".
How did I overcome this problem? Read on...
The Fix
Before you get started, here's what you'll need:
For the purposes of this post, I'll assume some familiarity with configuring your TomTom, and that your main obstacle is the limitations of the 8.300 device software.
Once you've gathered the above items, here's what to do:
Now you're probably wondering why I would activate another phone instead of just paying Verizon $30 a month. I'll save that answer for another thread.
When I first got my TomTom I was able to configure it for use with my Nextel iDEN phone for TomTom Services with no problems. DC calls really confused the hands-free feature on my TomTom, so I disabled that. Several months later I switched to Verizon, and configured that phone (with some issues), and somewhere along the line I deleted my iDEN phone from my TomTom configuration.
Jump ahead to last week, and I decided to reactivate my iDEN phone so I can use it instead of my Verizon phone and stop paying Verizon $30 a month for tethering. Much to my dismay, I discovered that the current device software (8.300) doesn't allow you to enter anything but numbers and a few special characters in the dial string. This is a problem because my iDEN phone uses a dial string of "s=2".
How did I overcome this problem? Read on...
The Fix
Before you get started, here's what you'll need:
- Your TomTom (obviously)
- A blank SD card (I used a 2GB card, but a 1GB card will work fine)
- A copy of version 7.221 of the device software (download here - thanks Oldboy)
- A Guam map, compatible with version 7.221 of the device software (should already be on your device - I used map version 715)
- Your activated iDEN phone (make sure the globe icon appears at the top of the display)
For the purposes of this post, I'll assume some familiarity with configuring your TomTom, and that your main obstacle is the limitations of the 8.300 device software.
Once you've gathered the above items, here's what to do:
- Backup your TomTom using Windows Explorer, as described elsewhere in these forums
- Insert your SD into your TomTom device and connect your TomTom to your computer
- Copy the entire contents of your TomTom's internal memory to the SD card, excluding all map folders.
- Copy the Guam map folder from your TomTom's internal memory to your SD card (I don't think this step is necessary, but this is what I did)
- Unzip the 7.221 device software and copy it to your TomTom device, preserving the folder structure
- In Windows, safely remove the drives in your TomTom, turn off your TomTom and disconnect it from the computer
- Turn on your TomTom. You'll end up going through the setup as if it has been restored to factory defaults. Don't worry if only the Guam maps appear - only maps that are compatible with 7.221 will appear
- Pair your iDEN phone with your TomTom device, as described here
- If the data setup fails, try again... TomTom's servers are sometimes flaky
- Turn off your TomTom and remove the SD card
- Turn on your TomTom and verify that it's working by trying the weather service (it's free)
Now you're probably wondering why I would activate another phone instead of just paying Verizon $30 a month. I'll save that answer for another thread.
