Tomtom Go 520 - Phone book entries

[Stocky69]

Guys,

I've been monitoring the posts regarding handsfree for a few days. Guessing this is the best thread to post this on?

I have a TT920 and a Nokia 6233 phone. A couple of posters claim that this phone works fine...perhaps apart from SMS. (I'm not bothered about that bit).

Despite messing around with the set up for the last couple of months off and on, I can't get the b****y thing to work!!! My missus my coincidence has the same handset and can't get that one to work in the same way also.

It seems to connect to bluetooth and then drop off straight away. It then carries on running through the set up and it looks like it's going to work but never seems to have paired up successfully. It freezes up when I try and sync my phone book saying there's a sync error.

Any thoughts about how I can set it up differently or anyone else had the same phone/TT problem?

Thks,

[shadamehr]

Ok all - a couple of things.

Firstly an apology. I posted earlier, in a hurry heading out to work, and never realised the catalogue of typing transpositions and errors it contained.

This was compounded by the fact that being at work all evening, it has sat there all this time confusing everyone without me even knowing.

Suffice to say, DYN was meant to mean DUN, which in turn stands for Dial Up Networking.

Now, if I haven't made you suicidally bored reading that bit, I will now, in saying that Dial Up Networking is a Bluetooth Protocol (a certain feature of Bluetooth), that some devices have, and others don't.

An example of bluetooth protocols that you might understand, would be "Handsfree" which is the protocol that allows our beloved TomTom's to 'talk' to (some of) our mobile phones.

DUN (if I can now use the abbreviation), is the protocol that allows devices to connect to our phones, AND then to make a data call/connection, and thus allow us to do things like get Traffic Updates if we subscribe etc.

And as such, most (but I am not sure if all) Windows Mobile Devices - that is Pocket PC type hand-held phones that run the Windows Mobile operating system, do not include DUN Protocol, unlike most normal types of standard phones.

That is why common advice for people on here using such types of phone and not getting Wireless Traffic to work, is to advise them to download a stand-alone .cab file (a bit like a zip file, if you know what one of those is), to their phone, that adds DUN protocol.

Wow, there you go - how geekie technical.


Moving on, whilst you all still just about have the will to live...

In reply to the question by the user with the Nokia 6233, suffice to say, following my long post on previous page, this type of Nokia is a Series 40 Nokia - the same more 'basic' sort as Dennis's 6230i, albeit the 6233 is a newer and slightly more advanced/updated handset.

But as it is the same base Series 40 type of Nokia, it is "meant" to work fine with a 920.

So I am unsure why yours is not working, or keeps disconnecting alas mate.

Wish I could add more, but the short answer (for that question at least) is that it should indeed work though!

[DennisN]

[shadamehr]

For a more helpful attempt however, let me suggest this...

Remove the current pairing from your phone (Go into something like Settings, - Connectivity, or Settings - Bluetooth, or similar, then Paired Devices, then delete the pairing with the TomTom).

Then on the TomTom Manage Phones menu, delete the phone.

Then before anything else, switch both devices off then back on.

Now, make sure bluetooth is on in your phone, and set to "Discoverable" or NOT Hidden.

Go into your TomTom menu, and go to Plus Services, and try Plus Weather.

It should then ask you to start searching for phones at that point, as you have likely tried before.

When it finds your Nokia 6233, follow the instructions on the TomTom, but with a key difference...

Instead of actually choosing your model of phone, if shown, choose "Other" instead.

Then follow the steps as normal to set it up.

At a certain point, your TomTom will suggest something about making sure you set the device to "Authorised" on your phone - heed this advice indeed! Go into your Bluetooth settings on your phone, to the paired TomTom device, and choose something like Options - Set as authorised

Do this at a convenient point during the TomTom setup where it kind of pauses for you, or asks if you want to continue with setup - do the "set as authorised" thing on the phone before continuing with the setup.

Now, somewhere along the setup process, you will get a progress bar that is well known for appearing to hang at around 65%

IT HASN'T - trust us (or rather 99% of the time, it hasn't actually hung - there are sure to be exceptions to make me look a fool).

When it appears to have froze at 65%, go and make a cup of tea, run the bath, do whatever, as long as you can occupy yourself for over 30 minutes.

As it has actually been known to take well over this long before it either:

a) WORKS, and finishes the setup fine (rare, but great if so), or:

b) Fails, but with an error message that asks if you want to try MANUAL settings. If so, this is the key...

Say yes to Manual setup, and just accept the suggestions it gives you each time, being careful NOT to accidentally delete any characters. When asked about Automatic IP address or manual, as well as DNS etc, choose Automatic for each of those questions.

Eventually you will finish the questions off.

And if there is any luck, you MAY, just may, have managed to get connected.

But the final point I wish to make - this is nothing more than one last gap attempt to try, before giving up the ghost. As your phone is meant to work anyway, this advice here, might not make any difference at all.

It's worth a try however, if nothing else.

One final note - if your setup already used to appear to freeze at 65% when choosing your actual model of handset, then carry out my instructions above, but actually choosing the correct sort of handset first, but again, leaving it at least 35 minutes if it appears to freeze at 65%.

Finally, you have made sure your phone is running the latest Firmware yes, as this can make a major difference?

If that means nothing to you, mention it here or drop me a PM, and I will try and give you some pointers. But updating your firmware will mean losing loads of stuff off your phone, so not really something to do lightly, unless you really really have to.

Good luck, no matter what!

[shadamehr]

[Stocky69]

Thanks Shadamehr,

Thinks I need a bit of time to sit down and go through the whole process but really helpful.

I'll let you know how I get on......eventually....

I was aware of the non compatability on the TT website but I was going by the couple of posters who have mentioned successfully using the 6233 with x20 TT's.

I also believe my phone firmware is the latest as I had a previous bluetooth headset problem and they swapped out the phone to a newer firmware version....or so they told me. Perhaps that's the base of the problem

Nokia 6233 going cheap anyone???????

[shadamehr]

If you didn't already know, if you type:

*#0000#

On your phone's standby screen, it will tell you the current firmware, model no., issue date etc.

This applies to all Nokias, and indeed most other handsets too, so you can try it too if you so wish Dennis.

Then you can Google to see what the latest reported Firmware for your own model of phone is meant to be.

For the Nokia 6233, most results say 5.43 is the latest.

But the wiki entry at:

http://en.wikipedia.org/wiki/Nokia_6233

Indicates it is actually 5.60

Also for ALL of you reading this, one caveat...

The latest firmware versions are often only possible for UNBRANDED/None-operator versions of the handsets. Often each Network has their own CUSTOM Firmware versions on these phones, and these often have different numbers, and certainly can't be upgraded to a newer released firmware the day it comes out, as this is invariably always for the network free versions first. You usually have to wait for your network to customise their own version of a new firmware, before they release it for your handset.

This is not usually a problem for older handsets however, whereby the latest firmware has usually been out so long by now, that even the networks have updated their own version.

But please bear this warning in mind when comparing version numbers etc.

[Stocky69]

Shadamehr,

Thanks for all your efforts in that post.....and.......success. Yippee

By going into the wireless connection and disabling the Plus services I think that was enough to do the trick. (well that was the only thing I really did differently).

The other set up took barely 60 secs. Even though by phone claimed it couldn't syncronise the contacts, my 300+ have been copied almost instantly.

SMS is also working too.

Will try it out in the car tomorrow for a proper test.

For info, my firmware on the phone is version 5.43 on Orange.

V V happy now.

[DennisN]

[shadamehr]

[richard345]

Found a couple of things when uploading my Phonebook from a Nokia N73 to my TT 520 in that if you have multiple numbers for an entry, for example, Home, Business and Mobile, then only the default number which is selected in the phone's Contacts is brought over with the name and secondly, if you only add a Company Name, instead of Firstname, Lastname to a Contact, then these numbers are brought over as orphaned entries, at the top of the list, in numerical order, without any Alphabetical details at all. This is pretty useless, as I had to scroll thoough over 100 entries, before coming across the first name! This is probably because all my Contacts are downloaded from Outlook Contacts to the phone.

I guess I'll have to extract the Contacts fro Outlook to .csv format, edit them and then imort to the 520 - unless anyone knows an easier way?
_________________
Ric - TomTom 520 DEAD - Passed to the great traffic jam in the sky. Now using Maps & Waze on Samsung Galaxy S4 + CamerAlert of course!

[mikealder]

Richard, if you use Excel on the PC have a look at using the pre-formatted spreadsheet from THIS Page, it might make life a little easier - Mike

[richard345]

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!