[xyrcncp]

You would think it would work similar to connecting an 8100 to a laptop over bluetooth.

[dale52]

hi my blkberry 7310e recognizes the TT910 but the 910 does not recognize the blkberry both devices have bluetoothe enabled. however i cannot pair them up any suggestions
Dale

Originally Posted by Wavshrdr

Hi,

Just thought I’d post my experience to help others that might have a similar situation. I purchased a Pearl and I have a TomTom 910 (aka TT 910) navigation system. As some of you who have the TomTom’s might know they don’t support many phones and I knew there was little chance of the Pearl pairing with the TT 910.

I was able to get my 7100 to pair up with it but it doesn’t support DUN so I couldn’t use any of the TT Plus services with it. That was the one reason I was looking at upgrading to the Pearl. I figured I’d have 14 days to make it work and if not return it to T-mobile.

I must have set like an idiot for an hour or better trying to pair the two devices. Neither one would see each other. I paired it just like I did with the BB 7100. Finally I decided to take a different approach. I made sure that even that discoverable was enabled in the Pearl (even though I didn’t need it on my 7100 during the pairing process).

I then started the Pearl’s search first before starting the TT’s search for other BT devices. I had a hunch that somehow the timeouts were occurring before I could actually pick up something that each device could work with. Finally a glimmer of success, the Pearl said it saw and “audio device”. I told it to search again and promptly lost it. I went on like this for about 15 minutes or so before I had another idea. I was pretty sure the “audio device” the Pearl was seeing was the TT 910 but I couldn’t be certain. I knew I wasn’t running any other BT devices but I turned off a BT headset downstairs that was with another phone just in case.

The next time the Pearl saw the audio device I did nothing with the Pearl. I restarted the search on the TT 910 and left the Pearl in the same mode where it had “captured” the signal from the audio device. About half way through the TT’s discovery process the Pearl’s message changed from audio device to TomTom 910. Paydirt at last!!!!

From that point on it was a simple matter to pair the phone with the TT 910. The TT 910 said it would work with their Plus services BUT I didn’t have the profiles of exactly how to set that up. They have specific files for the DUN settings for some phones like the Razr and with Tmo. I didn’t know what settings to make that part of it work at the time so now I am trying to track that down. I think they are generic Tmo DUN settings such as the access point as you can manually input some of the info but I didn’t have time to mess with it too much yet. So far though the phone pairs perfectly each time with the 910 and sound quality is excellent. The TT 910 acts as BT speakerphone and does a great job with the Pearl.

I have searched to try and find the Tmo DUN info on the forums here but there are so many posts when I search that I have spent a long time looking without success. I have tried a few different keyword searches for this info. Is there a sticky or a FAQ that covers this that I should be looking at? If I can get the DUN setup it would be awesome.

Hopefully my experience will help someone out. So far I am loving the Pearl and it is almost the perfect device for my needs. I can live with the smudges but so far the screen is tougher than an iPod in my experience. Battery life has surprised me but I’d still like a higher capacity one.

[kitbaldwin]

Here is what I had to do to get this working.

1) Put version 4.2.1.66 on my T-Mobile 8100 (Instructions here)
2) Set the TCP options on the 8100 to blank username and password and wap.voicestream.com as the APN
3) On my TomTom 510 go to traffic, which starts the Plus setup wizard. (This assumes it was already paired for voice.)
4) I chose T-Mobile US IV and walked through choosing the defaul options (This will fail.)
5) Once the setup fails select manual and replace internet3.voicestream.com with wap.voicestream.com in both places that it appears. Don't forget the "

It successfully connected!!!

[chadmd23]

Originally Posted by kitbaldwin

Here is what I had to do to get this working.

1) Put version 4.2.1.66 on my T-Mobile 8100 (Instructions here)
2) Set the TCP options on the 8100 to blank username and password and wap.voicestream.com as the APN
3) On my TomTom 510 go to traffic, which starts the Plus setup wizard. (This assumes it was already paired for voice.)
4) I chose T-Mobile US IV and walked through choosing the defaul options (This will fail.)
5) Once the setup fails select manual and replace internet3.voicestream.com with wap.voicestream.com in both places that it appears. Don't forget the "

It successfully connected!!!

Not working for me with a TomTom One. This sucks, I wanted traffic.

[BBUser7100t]

I have been able to pair the two and access the traffic info with a TomTom one and 8100. However, each time I turn off my TomTom One, I have to reenter all the info for the wireless data connection. As you can imagine, its a tedious process. Anyone have an idea of what I need to do to keep the connection and not have to type in all that info. each time?

Thanks.

[verbal11]

Originally Posted by BBUser7100t

I have been able to pair the two and access the traffic info with a TomTom one and 8100. However, each time I turn off my TomTom One, I have to reenter all the info for the wireless data connection. As you can imagine, its a tedious process. Anyone have an idea of what I need to do to keep the connection and not have to type in all that info. each time?

Thanks.

What settings did you use?

[billclark]

Originally Posted by kitbaldwin

Is that really true? I thought a number of people were using the 8100 as a modem on their PC. I assume mostly through USB. Is anyone using it via bluetooth with a PC?

Did you happen to look at the date of my original post? It was before 4.2.1.66 was available. Currently, the only known working version that will work with TomTom is 4.2.1.66. Later versions of 4.2.1 seem to not allow "tethering" of a TomTom Device.

[chadmd23]

Originally Posted by billclark

Did you happen to look at the date of my original post? It was before 4.2.1.66 was available. Currently, the only known working version that will work with TomTom is 4.2.1.66. Later versions of 4.2.1 seem to not allow "tethering" of a TomTom Device.

66 is TIM? (If it is, that version sucked.)

This reminds me of my 7200 from Verizon, the first EVDO upgrade allowed for free tethering, but tons of bugs. Once the clean version of the OS came out, Verizon was charging $15/month for tethering.

I'm keeping my fingers crossed for for a TMO version of the Pearl OS that allows TomTom tethering.

[zeros360]

Thanks to everyone who has posted on this subject! I was running Cingular's latest version 4.2.1.99 (somehting like that) and couldn't get the plus services to work. I then went down a version to the TIM release and the sucker worked and continues to work perfectly.

[sam hejja]

i was able to pair bb8100 to tt510. i can use the hands free with no problem. As soon as try to setup the plus services i loose the blue tooth connection. please help

[dandrzejewski]

Same here. I just downgraded to 4.2.1.66 and the wireless data works perfectly.

It's too bad that this version has that double-letter bug when dialing letters in phone numbers.

[IbSta]

downgrading eh :( just for the stupid devices to work :( I have a TomTom Go 720 and a Blackberry 8100 do think think it will work if I goto .66?

[IbSta]

Originally Posted by kitbaldwin

Here is what I had to do to get this working.

1) Put version 4.2.1.66 on my T-Mobile 8100 (Instructions here)
2) Set the TCP options on the 8100 to blank username and password and wap.voicestream.com as the APN
3) On my TomTom 510 go to traffic, which starts the Plus setup wizard. (This assumes it was already paired for voice.)
4) I chose T-Mobile US IV and walked through choosing the defaul options (This will fail.)
5) Once the setup fails select manual and replace internet3.voicestream.com with wap.voicestream.com in both places that it appears. Don't forget the "

It successfully connected!!!

Thanks for the tip. After I went back to .66 it picked up my phone and even with the defualts it connected!!!!!

[dandrzejewski]

Originally Posted by IbSta

downgrading eh :( just for the stupid devices to work :( I have a TomTom Go 720 and a Blackberry 8100 do think think it will work if I goto .66?

I bet it would. I don't think it's a restriction of the TomTom, I think it's a restriction placed on newer RIM device software.