Tom Tom Mobile 5 FIXED on N70!!

Johnny Hormone wrote:Summary - In my experience you dont need the latest firmware on the N70, you dont need the latest 5.2 release for TomTom mobile 5, and you dont need the latest TomTom GPS receiver... Just dont use a speed cam POI database :icon13: .

Hi Johnny,

Looks like different results work for different people. However, if you did upgrade your firmware to V3.xxxx you might well find you CAN have the SpeedCam warning enabled without loss of signal. I never experienced a single loss of GPS signal when I tested with FW3 and the SpeedCam DB only set to 'warn only when on route' and all POI's hidden. I drove for 4 hours, passing about a dozen speedcams - in both directions - perfect operation.

FW upgrades should be free, what have you got to lose? 😉

P.S. I am interested to learn of your experiences with the new Maps, but I agree with your expectation that there should be no difference.

Dez

Just wondering what memory cards are the ones that seem to working with points of interest speed cameras?

Just to add to the database of user experience, I installed a friend's Tom Tom onto my N70 as a test after he had the usual issues with it after 5-30 mins and today we did a two hour journey from Hants up to the NEC in Birmingham and never had a single lockup or loss of signal, it even coped with me walking into the services (so dropping the bluetooth connection) and then returning to carry on where we left off, without needing to reboot or re-pair the bluetooth. This was with the phone in onlne mode so able to receive calls (although didnt actually take any), using an old style (silver) Tom Tom receiver, no speed camera location data and my 02 supplied phone with v3.0546.2.3 firmware.

Oddly enough though it didnt provide any real conclusive evidence because we plugged his phone in for the return journey (a Vodafone N70 with v2.xx firmware) and that didnt lock up or drop signal either, despite doing it several times before within a few minutes when he'd tested it previously!

WOW THANKS GUYS...... After deleting ALL of my POI's my TomTom worked perfectly and it even improved the frame rate to that of a proper tom tom go system! Smoooooooth! Anyway.... I downloaded the safety cam POIs from pocketgps (the ones that say which speed) and added them to my card, I put the audio warnings on each one (on route only) and then Hid the POI's on the tom tom menu. My tom tom is very stable, and the audio warnings come on and the pictures of the cams do aswell when im however close i set the warning to come on! Im still testing.... but this is the most stable ive ever had it! The only problems ive had is, ive had to restart my phone once in a while, as tom tom wont find my gps unit on initialisation of tom tom.

Well done! Good work guys!

It must be a memory/cpu problem with the app or phone. If enough of us complain to the right people, we will get something done!!!!!!!!!!!!!

Locoblade wrote: This was with the phone in onlne mode so able to receive calls (although didnt actually take any), using an old style (silver) Tom Tom receiver, no speed camera location data and my 02 supplied phone with v3.0546.2.3 firmware.

For me the significant facts above are V3 FW and no POI's enabled. I am also on O2 with V3 and can confirm your results on a friends borrowed TT GPS Receiver.

Locoblade wrote: Oddly enough though it didnt provide any real conclusive evidence because we plugged his phone in for the return journey (a Vodafone N70 with v2.xx firmware) and that didnt lock up or drop signal either, despite doing it several times before within a few minutes when he'd tested it previously!

Thanks for the info.

P.S. Is the disabled POI workaroud working for owners of other brands of GPS receiver?

Dez

swat47 wrote:WOW THANKS GUYS...... After deleting ALL of my POI's my TomTom worked perfectly and it even improved the frame rate to that of a proper tom tom go system! Smoooooooth! Anyway.... I downloaded the safety cam POIs from pocketgps (the ones that say which speed) and added them to my card, I put the audio warnings on each one (on route only) and then Hid the POI's on the tom tom menu. My tom tom is very stable, and the audio warnings come on and the pictures of the cams do aswell when im however close i set the warning to come on! Im still testing.... but this is the most stable ive ever had it! The only problems ive had is, ive had to restart my phone once in a while, as tom tom wont find my gps unit on initialisation of tom tom.

Well done! Good work guys!

It must be a memory/cpu problem with the app or phone. If enough of us complain to the right people, we will get something done!!!!!!!!!!!!!

Glad to hear yet another TT Mobile user has found the POI solution works for them! It's been a long time coming for many of us.

The latest theory on the cause of the problem is the read/write speed of MMC's in N70 owner's phones. Some are as low as 2.5Mb/sec, some are over 9Mb/sec. The idea is that on the slow cards, TomTom cannot read the main maps and multiple POI databases all at the same time. This might explain why some users experience no problems with TT, where others found it completely unusable.

It MIGHT also explain why some users reported TT would lose GPS signal at the same location on a route every time (often only in one direction!). I wonder if there were a lot of POI's nearby the location where TT failed? When I first owned TT, I fell into the temptation to enable almost every POI available, which resulted in too slow read performance for TT from my 512Mb 2.5Mb/sec MMC.

By the way, I also share your problem of needing to reboot the phone after closing the TT app, otherwise the GPS Receiver cannot be found next time. At the moment you'll just have to get used this - at least it cures the annoying problem.

Dez

I've found that TomTom doesn't always connect to my TT MK2 GPS receiver, The easiest way I've found to get it working is to go into the GPS Status, Then it finds it fairly quickly,

It is annoying,

Carl,

Hi all just got this reply from Tomtom...
First of all, the card you have there is not fast enough. Please read the following regarding SD cards and their performance, which explains a bit closer:

With regards to memory speed, there are a few things to keep in mind. The Tomtom application, demands a READ speed of at least 10mb/second. This is very important, as a lower specced card will almost certainly experience big issues with both starting and using the software. Most cards on the market are not made with this in mind. Most cards are designed to be used with other type of devices in mind, devices where WRITE performance is more important (like with cameras for instance).

Another problem is that SD cards will not tell you how many MB they can transfer per second. They rather give you a cryptic 40x or 50x or 60x specification, which can be hard to translate into real world numbers. There is however a logic behind it, and a way to calculate ecxactly what this means. I'll do the math for the 10mb limit here, so we can find out what that becomes in the 40x, 50x, 60x system. This system is a survivor from the early years of the CDROM age, where the original CDROM players were capable of 150kb/second read access. Later, this was doubled (2x) using updated technologies, and like this the 2x, 4x, 8x, 16x system was born.

First we need a few definitions:
1mb = 1024kb
1x = 150kb/sec

Now, it becomes fairly simple:

First, how many kb are there is 10mb?
10 * 1024 = 10240

Now we can calculate the "x" specification of a 10mb/sec card:
10240kb / 150 = 68,27

With this calculation, we find that 68,27x is the minimum READ specification for SD cards used with our software. This means that you need a card with at least 70x specification to work with our software.

What you will find, is that typically cards with a high storage capacity have a slower READ speed, while lower capacity cards might have better access times.

I see you refer to other users using 56mb/sec cards? As far as I know, the fastest cards currently on the market have a read access of 150x (equivalent to about 22mb/sec). Are you sure you're not confusing the two different ways of giving read speed specifications as explained earlier in this email?

I also have to ask you to remove any 3. party POIs you have on the device (such as the PocketGPSWorld database you refer to). We can only guarantee functionality with our software. Software from 3. party suppliers such as Pocket GPS World can seriously damage the equipment, we can not guarantee error free operation with our devices/software as long as they are used with such 3. party software.

With best regards,

The TomTom Customer Support Team

Hi, I just need some help from people who kno more than i do bout the n80

I went on ebay and i found this person who is selling the n80 for 300usd
To my knowledge, the fone isnt even out yet, and if it is, y is it so cheap.
the person sed they bought it from the finalnd factory.

can anyone tell me if this is legit or if its a scam?

if so, where can i buy this fone besides ebay? anyone kno any trusting online cell phone sites where i can buy fones that will ship to Toronto.

Thank you

Kinda think you have posted that n80 question in the wrong place chap, I would try a separate thread for it rather than one dealing with the TomTom app on an n70.

More people will see it if it is on its own thread. 😊

Regarding the speed of the card, am I right in thinking that Tomtom works flawlessly with a low speed card when used in conjunction with a different phone for example 6630 or 6680? Therefore surely it has absolutely nothing to do with read speed? I cant imagine that enabling a POI or two would use much more than extra MB per second in read speed required/

Densil

densil wrote:Regarding the speed of the card, am I right in thinking that Tomtom works flawlessly with a low speed card when used in conjunction with a different phone for example 6630 or 6680? Therefore surely it has absolutely nothing to do with read speed? I cant imagine that enabling a POI or two would use much more than extra MB per second in read speed required/

Densil

Yep, spot on....
My mates got TT5 on a 6630. He has got the cheapest card he could find (256mb for �9.99) in his phone (he says its read time is 2x) and he borrows my GPS receiver (must start charging him for this!!) and he regularly does a four drive to his mums at weekends without so much as a blink! He has got the speedcams from Pocket GPS World loaded, visible and functioning flawlessly!!

I'm starting to think that the phone is the issue in it's processing power, not the card. But I'm no techie and am probably wrong!!!

gadget_sa wrote:Yep, spot on....
My mates got TT5 on a 6630. He has got the cheapest card he could find (256mb for £9.99) in his phone (he says its read time is 2x) and he borrows my GPS receiver (must start charging him for this!!) and he regularly does a four drive to his mums at weekends without so much as a blink! He has got the speedcams from Pocket GPS World loaded, visible and functioning flawlessly!!

I'm starting to think that the phone is the issue in it's processing power, not the card. But I'm no techie and am probably wrong!!!

Hi,

I agree with you both, and it's worth pointing out that the 6630/6680 phones have CPU's approximately half the speed of the CPU in the N70, and the 66xx range also had less onboard memory. Perhaps TomTom on 66xx runs so slowly that the MMC card's read speed is much less important?

I also used TT with a 2Mb/sec MMC card on the 6680 with no problems but the problems are apparent when the same card is used on the N70...

...I am now going to buy one of these 15Mb/Sec cards at £27 inc VAT and P&P... (see below)

Once I have the card installed, I will SHOW POI's, borrow a m8s GPS receiver, and perform some tests in Edinburgh where there's loads of POI's to display.
I will let you all know how I get on, probably early next week.

http://www.techfever.co.uk/products....&source=affwin

PEAK 512MB RS-MMC MOBILE XTREME 100x
Flash Memory>>SD/MMC
Type : Mobile Multimedia Memory Card
Size : 512MB
Model number: 2983ADPK
Weight: 0.01Kg

Special Features :
The Peak MMCmobile 4.0 Card is Based on an Advanced 13-pin Interface with Dual Voltage and is Designed to Meet the Requirements of Different Portable Audio & Video Consumer Devices. It can Operate at Voltages of 2.7V - 3.6V as Standard. It can also Operate at Voltages of 1.65V - 1.95V Which Most Cellular Phones Require.

Specifications:
Package Type : Retail
Capacity : 512MB
Interface : MMCmobile
Read Speed : 15MB/s
Write Speed : 8MB/s
Operation Voltage : 2.7V to 3.6V, 1.65V to 1.95V
Insertions : 10,000
Width : 18mm
Height : 24mm
Depth : 1.4mm

Package Contents:

MMC Adapter
Warranty: 5 Years

crazyjlondon wrote:
First we need a few definitions:
1mb = 1024kb
1x = 150kb/sec

Now, it becomes fairly simple:

First, how many kb are there is 10mb?
10 * 1024 = 10240

Now we can calculate the "x" specification of a 10mb/sec card:
10240kb / 150 = 68,27

With this calculation, we find that 68,27x is the minimum READ specification for SD cards used with our software. This means that you need a card with at least 70x specification to work with our software.

My card is an Adata 512mb 100x quite a bit more than 70x! and it crashes with POI Enabled (just the POIs that come with tomtom)

If you run a test on the large size mmc that tomtom mobile came with a year ago you find their stock cards runs at this

SiSoftware Sandra

Benchmark Results
Combined Index : 114364 operation(s)/min
Endurance Factor : 5.0
512B Files Test : 230908 operation(s)/min
32kB Files Test : 46429 operation(s)/min
256kB Files Test : 4940 operation(s)/min
2MB Files Test : 757 operation(s)/min
64MB Files Test : 47 operation(s)/min

Performance Test Status
Run ID : CRAZYSCOMP on 10 January 2006 at 04:20:21
SMP Test : No
Total Test Threads : 1
SMT Test : No
Dynamic MP/MT Load Balance : No
Processor Affinity : No

512B Files Test
Read Performance : 1379888 operation(s)/min (11499 kB/sec, 65x)
Write Performance : 79605 operation(s)/min (663 kB/sec, 3x)
Delete Performance : 785605 operation(s)/min
Combined Index : 230908 operation(s)/min

32kB Files Test
Read Performance : 188979 operation(s)/min (100789 kB/sec, 572x)
Write Performance : 16481 operation(s)/min (8790 kB/sec, 49x)
Delete Performance : 622205 operation(s)/min
File Fragments : 1.0
Combined Index : 46429 operation(s)/min

256kB Files Test
Read Performance : 4362 operation(s)/min (18611 kB/sec, 105x)
Write Performance : 4635 operation(s)/min (19776 kB/sec, 112x)
Delete Performance : 715289 operation(s)/min
File Fragments : 1.0
Combined Index : 4940 operation(s)/min

2MB Files Test
Read Performance : 701 operation(s)/min (23927 kB/sec, 135x)
Write Performance : 645 operation(s)/min (22016 kB/sec, 125x)
Delete Performance : 894141 operation(s)/min
File Fragments : 1.0
Combined Index : 757 operation(s)/min

64MB Files Test
Read Performance : 48 operation(s)/min (52429 kB/sec, 297x)
Write Performance : 34 operation(s)/min (37137 kB/sec, 211x)
Delete Performance : 380129 operation(s)/min
File Fragments : 1.0
Combined Index : 47 operation(s)/min

Endurance Test Status
Operating System Disk Cache Used : No
Use Overlapped I/O : No
Test File Size : 32MB
Block Size : 512 byte(s)
File Fragments : 1

Endurance Benchmark Breakdown
Repeated Sector ReWrite : 5 MB/s
Sequential Sector Write : 5 MB/s
Random Sector Write : 766 kB/s

Drive
Total Size : 190GB
Free Space : 37GB, 19%
Cluster Size : 4kB

Your see that our cards are way slower and combined with a n70 running at 230mghz its trying to read much more data as the frame rate of the maps much faster than other phone like 7610 6830 etc ..
i found these 150x and 132x cards on this site ATP are 150x goldflash are132x

http://www.pc-memory-upgrade.co.uk/memory/dual-voltage-rsmmc.asp

dez_borders wrote:Hi,

I agree with you both, and it's worth pointing out that the 6630/6680 phones have CPU's approximately half the speed of the CPU in the N70, and the 66xx range also had less onboard memory. Perhaps TomTom on 66xx runs so slowly that the MMC card's read speed is much less important?

I also used TT with a 2Mb/sec MMC card on the 6680 with no problems but the problems are apparent when the same card is used on the N70...

...I am now going to buy one of these 15Mb/Sec cards at �27 inc VAT and P&P... (see below)

Once I have the card installed, I will SHOW POI's, borrow a m8s GPS receiver, and perform some tests in Edinburgh where there's loads of POI's to display.
I will let you all know how I get on, probably early next week.

http://www.techfever.co.uk/products....&source=affwin

PEAK 512MB RS-MMC MOBILE XTREME 100x
Flash Memory>>SD/MMC
Type : Mobile Multimedia Memory Card
Size : 512MB
Model number: 2983ADPK
Weight: 0.01Kg

Special Features :
The Peak MMCmobile 4.0 Card is Based on an Advanced 13-pin Interface with Dual Voltage and is Designed to Meet the Requirements of Different Portable Audio & Video Consumer Devices. It can Operate at Voltages of 2.7V - 3.6V as Standard. It can also Operate at Voltages of 1.65V - 1.95V Which Most Cellular Phones Require.

Specifications:
Package Type : Retail
Capacity : 512MB
Interface : MMCmobile
Read Speed : 15MB/s
Write Speed : 8MB/s
Operation Voltage : 2.7V to 3.6V, 1.65V to 1.95V
Insertions : 10,000
Width : 18mm
Height : 24mm
Depth : 1.4mm

Package Contents:

MMC Adapter
Warranty: 5 Years

Hi Guys,

I've just read the response from TT Customer services with regards to the Speed of the Memory Card and all that I can say is "what a stupid Pr*ck this guy is"

Are TomTom just pathetic or what ?

The Speed of the memory card will have absolutely nothing to do with the problem. There isn't any applications on the Pocket PC or Symbian phones that would use the full bandwith to communicate with the memory card. If that was the case, why wouldn't a 200k game start instantly or TT application start in approx 0.2 of a second ?

If there is a BIG ISSUE about the memory card working on a super fast Mobile with over 200Mhz of speed, How the hell would it work on a Pocket PC running at 624Mhz ?

In the world of programming when you read data, the program has to wait for the data to get read and then executes the next instruction, it doesn't usually matter how long the read takes i.e. if theres a few Milliseconds difference it isn't going to matter.

Theres prob a million other reasons for the Memory Card not to make any difference and I would be gob smacked if it turned out to be the problem.

I think TT have run out of idea and are now clutching at straws.

TT, WHAT A STUPID COMPANY !!!!

Ash_99 wrote:
The Speed of the memory card will have absolutely nothing to do with the problem. There isn't any applications on the Pocket PC or Symbian phones that would use the full bandwith to communicate with the memory card. If that was the case, why wouldn't a 200k game start instantly or TT application start in approx 0.2 of a second ?

If there is a BIG ISSUE about the memory card working on a super fast Mobile with over 200Mhz of speed, How the hell would it work on a Pocket PC running at 624Mhz ?

In the world of programming when you read data, the program has to wait for the data to get read and then executes the next instruction, it doesn't usually matter how long the read takes i.e. if theres a few Milliseconds difference it isn't going to matter.

Theres prob a million other reasons for the Memory Card not to make any difference and I would be gob smacked if it turned out to be the problem.

Hi Ash,

Harsh words, lol! Perhaps partly justified considering how long TT have let this problem go on.

However, as an I.T. professional, 10 years of which was in programming, I have to say that the Memory Card read speed is the most reasonable explanation so far put forward by TT support for a problem which affects some N70 owners so badly and others not at all.

We all share the same handset hardware, and all network branded phones seem affected by the problem. Whilst I would highly recommend the FW 3.xxxx upgrade to all N70 owners, there do appear to be some FW 2.xxxx owners who have no major problems with TT.

The only 2 items of hardware which differ between users are the MMC and GPS receivers. Considering that TT's own GPS Receiver did not work any better with TT on the N70 than 3rd party GPS receivers, then all that remains is the MMC.

Whilst I agree in I.T. best-practice, that programmers SHOULD always check the status of read requests and check buffer levels on EVERY I/O operation, typically they do not do so - partly through laziness, partly through the assumption that I/O operations will always complete successfully and on-time, and also in an aim to produce smaller, faster and more efficient executables.

I have seen some amazing and unexpected issues over the years on relatively simple COBOL batch programs which did not check I/O status, and modern event-driven programs like TomTom are arguably far more complex in nature. Microsoft themselves release patches to fix buffer overflow problems almost every month, so we should not be too harsh on TT.

However, and in an attempt to prove or disprove the MMC query, I am upgrading from a 2Mb/sec MMC to a 15Mb/sec card and will do some tests with POI enabled.

Also, is there anyone out there experiencing the problems with POI's who has the following hardware...
1. N70 with FW 3.xxxx
2. Original TomTom Supplied MMC Card (which TT claim has read speed of 10Mb/sec)
3. Original TomTom GPS Receiver.
If anyone has all 3 of the above and still gets random 'No GPS RECEIVER' errors when using TomTom on the N70, then the MMC is unlikely to be the cause.

Cheers,
Dez

LOL, Sorry for the Harsh words Dez, it was late, and I just didn't like that answer from TT. To me it just seems that TT are looking for anyway out of this problem without addressing it.

From your explanation, it might seem that TT are lazy programmers, I can only hope they change there Coffee and step upto the challenge.

I look forward to seeing your results.

Cheers

Ash.

Ash_99 wrote:LOL, Sorry for the Harsh words Dez, it was late, and I just didn't like that answer from TT. To me it just seems that TT are looking for anyway out of this problem without addressing it.

Hi Ash,

I don't work for TT, so be as harsh as you feel neccessary, lol!
I was just trying to put forward a balanced view of their latest explanation.

My new MMC is in the mail, so hopefully this weekend I can borrow my m8's TT GPS Receiver and conduct some tests with lots of POI enabled.

Did some tests a few days ago (on slow MMC) with the Speed Camera set to 'Warn only when on route' and with my Motorola HS810 Headset in use. Did 2 hours driving, answered one call and not a single 'no GPS Device' error.

I still have to reboot the phone after closing TT if I want it to detect next time.

Dez

My findings are similar to the ones above - it is the POIs that cause the problem. My N70 (Orange) with tomtom 5.2 ran for only about 10 minutes with POIs enabled. With them disabled it ran for over an hour and I took several calls during that time.

I managed to break the screen on my nokia N70 so have to temporarily go back to my old SP-C500.

Im trying to get my TomTom from the MMC card onto the MiniSD card that the C500 uses.

Tomtom starts up fine but says "No Maps Found"

The map is in the correct place on the card, so have i missed something?

Probably a long shot but if anyone does know i would be grateful..

After searching many forums on this can anyone else confirm if when updating TomTom to v5.20 they have tried installing the N90 update?
This worked fine for a whole day but then when pear shaped.....
Im using N70 firmware V2.0539.1.2 19-10-05 RM-84..
Does anyone know what the lastest version is and if it resolved any issues..
Also problems connecting to other phones 6680 6630 6230i...
Thanks..............

Just to add my experiences to this, I received my Holux GPS receiver on Thursday (GPSlim 236) and having been running Tom Tom on every journey since.

I feel that there may be two seperate issues, one relating to losing GPS connectivity when the PocketGPS POI's are loaded and the other when coming back withing bluetooth range and creating the connection to the GPS - Im not sure these two are related.

In total Ive done about 6 hours of driving without the PocketGPS POI's installed (inc about 3 hours with a mate's original Tom Tom GPS receiver) and I never had a loss of GPS connection. This morning I installed the PocketGPS POI's (the seperate ones) and set them to warn only when on route yet within 10 minutes I had a dropped connection even though I was on a country road where Im fairly certain there would be no warnings anywhere close. I then disabled all POIs and immediately the connection came back without even exiting Tom Tom, but another 10 mins or so went past and it lost connection again. I then manually deleted all the pocketgps files and it ran fine for the reast of the journey, which in total was well over an hour. To me thats fairly conclusive that in my case at least, its the presence of the pocketgps files in the Tom Tom folder that causes issue, regardless of whether POIs are on or not. Next I'll try the single file version and see how it goes.

The other issue I had was one thats been experienced here before too, whereby when coming back to the car, it wouldnt reconnect to the GPS unit until I'd rebooted the phone. However, I think this only happened when the GPS unit was switched off manually (possibly before exiting Tom Tom), as most of the time it will say "No GPS Device" but as soon as I ask it to plan a route, within a few seconds it finds the GPS device and calculates the route, although on a couple of occasions I had to go into the GPS setup section of Tom Tom before it found the device. Im not sure if its coincidence or not, but all the niggles I had with connecting like this were in my girlfriends car (new Focus), Ive not experienced any of these connection issues in my Leon so is it possible its car specific somehow?

For info Im running the latest v3.0546.2.3 firmware and a Kingston 1Gb MMC.

Chris

hi,

i have followed this thread for while now. i have same sort of problems. i have latest v3 firmware. and as well as GPS drops and phone occasionally rebooting (sometime when receviing call) it also has problem when using speech recognition on the N70 (which i haven't seen posted before).
.
if you have TTM application running and you navigate to the main telephone menu then hold down the right selection key (which activates speech recognition), it should make sound and then you will see progress bar with "speak now". BUT with TTM running, if you try and activate speech recognition the phone is very slow to respond with both the tone and "speak time" progress bar. Well it does for me anyway. i originally noticed this problem using my BT headset and activating speech recognition via BT, but you don't even need the BT headset attached - just activating the speech recognition via the phone causes problems.
As soon as you exit TTM the phone springs to life and speech recognition commands appear on screen.

i'd be interested if anyone else has this specific problem. TT are currently investigating it for me. i'd be greatful for any test results back which i can pass to TT.

rob

ps: just got TTM 5.202 off TT and will test this with GPS this week. this 5.202 version still causes problems with voice recognition though so it definately doesn't sort everything out for me. anyone else have this voice recognition problem??

I've just changed my Kingston 512Mb MMC (8Mb/s) for a Peak 512Mb MMC (15Mb/s) and there was no difference in the reliability with POI's switched on so i think that the card speed issue is not a cause of the problem, once you are approching the TomTom recomedned speed of 10Mb/s

Just to add, Ive tried it for about an hour and a half today with the single file PocketGPS camera database and it worked fine, no hangs etc. Is it possible that when there's 4 or 5 seperate ov2 files in the map folder, that Tom Tom for some reason can't read all of them quickly enough and so causes a wobbly? Ovbiously this is an N70 specific thing though, so possibly the way the N70 pulls data off the memory card?

Im not sure its worth looking too far into the card read speed issue because I assume Tom Tom are suggesting this as a potential fix for when people have issues with straight out the box vanilla Tom Tom (without PocketGPS databases etc which the'll never warrant it working with). In most cases on here it appears that without the PocketGPS data, there's very few problems anyway. I doubt Tom Tom would have tested and troubleshooted adding 3rd party add-ons, so are unlikely to know the fix, but even if they do they are unlikely to tell anyone seeing as they have a chargeable rival product they would prefer you to use!

Chris

patrickmurphy19 wrote:After searching many forums on this can anyone else confirm if when updating TomTom to v5.20 they have tried installing the N90 update?
This worked fine for a whole day but then when pear shaped.....
Im using N70 firmware V2.0539.1.2 19-10-05 RM-84..
Does anyone know what the lastest version is and if it resolved any issues..
Also problems connecting to other phones 6680 6630 6230i...
Thanks..............

Hi,

TomTom Support informed me the N90 install routine is compatible with the N70.
You could do with a Fiurmware upgrade to V3.xxxx which should be free.

You will also find TomTom more stable on the N70 if you HIDE POI's.

Cheers,
Dez

Locoblade wrote:Just to add, Ive tried it for about an hour and a half today with the single file PocketGPS camera database and it worked fine, no hangs etc. Is it possible that when there's 4 or 5 seperate ov2 files in the map folder, that Tom Tom for some reason can't read all of them quickly enough and so causes a wobbly? Ovbiously this is an N70 specific thing though, so possibly the way the N70 pulls data off the memory card?
Chris

Hi Chris,

As per my postings earlier in the week, I replaced my old 2.5Mb/sec MMC card with a 15Mb/sec one and did some more testing relating to the POI question.

Test 1
--------
With all POI disabled and only the SINGLE PocketGPS (large file) set to 'Warn only on Route', Tom Tom is 100% stable for me - (3 hours driving, city/country)

Test 2
--------
With 13 (!) POI's selected and SHOW POI enabled, TomTom's 3D screen updates dropped to approximately 1/2 their normal speed, and the entire phone locked up within 5-10 minutes, then a few minutes later the N70 rebooted itself.

Test 3
--------
With 1 POI selected ('Petrol Stations ALL'😉, SHOW POI enabled, and the Large PocketGPS POI set to 'Warn only on route', TomTom was again stable on my system. (same 3hr route as used in Test 1)

So far, the theory holds true that too many POI's enabled will make TT and/or N70 unstable by using up too high CPU or Memory bandwidth.
The principle is that the slower your MMC card's read/write speed, the less POI's can be in use before TomTom crashes. N70 Firmware 3.xxxx is also advisable.

More testing next weekend. 😉

Dez

dez, locoblade, gary cat,

can any of you see if you can activate speech recognition on your N70 with TTM running. you don't have to connect it to GPS, just start TTM application.
i surely can't be the only person with this additional problem?

cheers,
rob