Another "Home" triumph

mikealder · Posted: Fri Nov 14, 2008 7:27 pm Post subject:

I don't use Home unless absolutely necessary so operating the Go via Home isn't something I do at all - the extra numbers are found when you tap the sat strength meter then tap the version box on the right hand side of the screen - Mike

MrT · Posted: Fri Nov 14, 2008 7:30 pm Post subject:

Just typing faster than thinking, it is 8.204/9718/081105 but that update a few days ago caused Home to stop "operating my device". Oddly enough Home does not seem to cache whatever it downloads and installs for this function.

mikealder · Posted: Fri Nov 14, 2008 7:35 pm Post subject:

TomTom Home will require a new file which it should download automatically to allow operation via the PC interface, if this isn't available as yet all you can do is either complain or wait for it to be made available, we have seen this behaviour in the past with the x20 and x30 devices when new software versions are released, Home catches up with the plot a few days later - Mike

adam45 · Occasional Visitor Joined: May 30, 2007 Posts: 5

Does anyone have any idea when (if?) this bug (and the others) might be fixed? Somebody confidently stated above that TomTom were aware of the issue. How do we know this?

A sampling of the horrendous outstanding bugs that I know of on the x40 series:

1. Home Bug: Home cannot "Operate My Go"

2. Volume Bug 1: The lowest possible volume setting, 10%, is just about bearable. anything higher is unbearably loud and distorted.

3. Volume Bug 2: With the automatic volume adjustment selected to "on" it will then be even worse. It'll whisper at you when its noisy and shriek at you like a banshee when it's nice and quiet.

4. Camera Database Inacuracies: The new speed camera database is missing about 10-20% of the cameras as compared to the normal (non-premium) version.

5. Day/Night Switching Bug: Automatic switch-over to night/day mode does not work on the 940.

Do TomTom test these things at all? Surely these basics should be based on mature and common code by now? WHy do they keep breaking these things on their new models?

Moan over.

DennisN · Posted: Tue Nov 18, 2008 9:06 pm Post subject:

dhn · Posted: Tue Nov 18, 2008 10:04 pm Post subject:

Another theory here.........I state this as a software tester for a living. And I speak from the frame of reference that I know.

Anyway, when develops change code, they do what is known as 'unit testing' or, in other words, 'quick and dirty' with a small sampling of data. The code is then passed on to Q/A (me, for example) to do rigourous testing with the changed code using a much wider sampling of data and, as well, push the envelope, so to speak, to see if existing functionality has gotten broken as a result of the code change ('regression errors' is the proper term).

My theory?

Coding changes at TomTom regarding any firmware for units or for Home is subject to 'unit testing' only. NO testing done by any dedicated QA team at all.

I cannot believe than any competent tester would sign off on the junk that comes out of TomTom.
_________________
David

Darren · Posted: Tue Nov 18, 2008 10:08 pm Post subject:

MrT · Posted: Thu Nov 20, 2008 12:20 pm Post subject:

I have my suspicions about the emulation of the x40 range under Home.

When first I tried my first (faulty) unit out, the SIM card emulation in Home was for a Netherlands SIM rather than the installed UK (44) SIM which my TT account rejected as being not for use in this country.

I suspect this emulation then locked the Live Services out for this unit as it had registered the Live Services for use in the Netherlands.

If my suspicions are true, this may be why a new emulation dll has not yet appeared for Home with the x40 range as they are trying to correct the error.

Of course it may be that my faulty unit caused the SIM to show as a Netherlands SIM in Home "Operate my Unit" but it showed as a UK SIM when running standalone on the unit.

SunnyUK · Occasional Visitor Joined: Nov 02, 2008 Posts: 52

	PocketGPS
	Web