My findings were the same as crazyjlondon but it did work for about 40 minutes and then 10 minutes after a reboot. Deleting the files restored it to reliable use.
Tom Tom Mobile 5 FIXED on N70!!
I have installed both the individual zoned POIs as well as the Single file version. I have tomtom alert me about both off and on route zoned POIs but I have only enabled the single POI and I have told tomtom to display POIs. This leaves me with all speed cameras visible on the map albeit only the generic camera image. However when in close proximity to a camera it warns me both with the appropriate "zoned" audio and visual indication. Tomtom seems totally stable and the slowdown due to the POI being enabled is barely noticeable.
Cheers for everyone that contacted me to try them, but they dont appear to be any better 😞
I suffered the same fate, it worked for about 45 mins fine but has gradually got worse, yesterday I had one single bomb out (the first) then today it bombed out about 4 times on the way home (30 min drive), although Im still yet to need a reboot to reconnect unlike some need to.
At least this proves one thing, that its not 3rd party POIs that it doesnt like, its ANY added on POIs regardless of how they were generated, even ones generated with TomTom's own app. The fact that it still bombs out with TomTom generated POIs should give those that have a support call open with TomTom some additional ammunition to get them to fix it though.
Another point on this thread, I have had all the problems you are experiencing too, runs a lot better with just the single file speed camera file and seems much more stable if you disable all the info in the status bar ie the remaining time, distance,arrival time,current time, street name, speed. access it by menu-change preferences-status bar preferences
Seems like the less tomtom has to do in the N70 the better it is.
Give it a try and let us know your results
I'm still on version 2 by the way not version 3
Ive had it running fine with everything else switched on (10 other inbuilt POIs etc) plus the single PocketGPS POI file, so I'm just going to stick with that for now I think. Its not really the point though is it, if TT say its fully compatible then you should be able to run it to its full capacity with everything switched on and multiple ov2 POI files added, you shouldnt need to tweak and turn bits off etc just to get it to work half reliably.
Chris
Locoblade wrote: if TT say its fully compatible then you should be able to run it to its full capacity with everything switched on and multiple ov2 POI files added, you shouldnt need to tweak and turn bits off etc just to get it to work half reliably.Chris
I agree 100% but as it sems its not "really" compatible we have to do these things to get it to work at all 😊
Hello.
First of all, sorry for my bad english, i m french ...
So i m a pretty new user of the N70 😛
I'would like to know if some one can resume this thread, in order to tell what i have to do to have a working TomTom on my phone please ?
So, which firmware ? which version of TomTom ? What do i have exactly to activate / or not in tomtom software ? Does any Gps receiver works correctly ?
Thanks for all :redface:
Resume of my configuration.
Nokia N70
SFR operator
v 2.0539.1.2 RM - 84 19-10-05
I just try tomtom mobile v5.00 (not a really legal version 😛) it seems to work, even if the soft seems to works, the screen is really "trouble"
Hi Pitiyo
There's probably no clear answer because most of us seem to have had varying results.
Personally, Ive found that TomTom works fine as long as you don't add any 3rd party POIs. It also seems to work fine if you only add one 3rd party POI file but gets upset when you start adding multiple ones.
This is with the latest firmware v3.xxx and a Holux GPSlim 236 GPS unit.
However, I now don't actually believe that TomTom is at fault though. I installed GPS Cyclemaster (as discussed in another thread "Free Mapping Software"😉 and downloaded some maps directly from the OS website (the UK's official mapping agency), and when you put the app into map mode it scrolls the jpg maps to show you your location. Suprise suprise after about 10 minutes of this in the car, it drops the bluetooth connection. I also seem to recall someone mentioning similar things happen with Route66?
So, the conclusion Im rapidly coming to is that its Nokia at fault after all. I dont think it can be the actual processor load issue that some have mentioned as a possibility because the N70 is at least twice as powerful as some other S60 phones that run these apps fine, but what Im thinking maybe is that the phone doesnt give the bluetooth threads / processes a high enough priority, so when the going gets tough for the CPU, the bluetooth processes get shoved to the bottom of the processing list and so it causes an issue.
If this theory is correct (and it probably isnt :tongue: ) I was wondering if anyone knew if / how you can up the priority on certain processes like you can with windows processes? Ive looked using taskpsy and can't see anything, but I guess there may be a way?
Chris
Hi Pitiyo / all
sounds like Locoblade is right - different people are getting different results.
I would say though do not get a BT-77 GPS reciever - I have this and the same firmware as yourself (2.0539.1.2 RM - 84 19-10-05) and the drop out's are shocking. Lots of people are talking about 10 / 20 minutes or more of working fine - I am lucky if I get 2 streets without the bluetooth dropping.
I have removed all my pocketgps poi files and at least the phone does not crash / hang all the time now but TOM TOM is unuseable. It does re-establish the connection on it's own but that takes about 20 seconds or so - probably meaning you've alreay missed your turn!
My brother has an N70 with v3.xx firware and when a I get a mo I will test my reciever with his phone and vica versa - his is an X50 GPS (or something like that). I hope a firmware update alone will improve things on my phone.
Has anyone got the BT-77 reciever working with N70 and new / old firware?
Nig
Locoblade wrote:Hi PitiyoThere's probably no clear answer because most of us seem to have had varying results.
Personally, Ive found that TomTom works fine as long as you don't add any 3rd party POIs. It also seems to work fine if you only add one 3rd party POI file but gets upset when you start adding multiple ones.
This is with the latest firmware v3.xxx and a Holux GPSlim 236 GPS unit.
However, I now don't actually believe that TomTom is at fault though. I installed GPS Cyclemaster (as discussed in another thread "Free Mapping Software"😉 and downloaded some maps directly from the OS website (the UK's official mapping agency), and when you put the app into map mode it scrolls the jpg maps to show you your location. Suprise suprise after about 10 minutes of this in the car, it drops the bluetooth connection. I also seem to recall someone mentioning similar things happen with Route66?
So, the conclusion Im rapidly coming to is that its Nokia at fault after all. I dont think it can be the actual processor load issue that some have mentioned as a possibility because the N70 is at least twice as powerful as some other S60 phones that run these apps fine, but what Im thinking maybe is that the phone doesnt give the bluetooth threads / processes a high enough priority, so when the going gets tough for the CPU, the bluetooth processes get shoved to the bottom of the processing list and so it causes an issue.
If this theory is correct (and it probably isnt :tongue: ) I was wondering if anyone knew if / how you can up the priority on certain processes like you can with windows processes? Ive looked using taskpsy and can't see anything, but I guess there may be a way?
Chris
Interesting... I had my N70 working fine for at least 2 hours with GPSCyclemaster and an old tomtom GPS unit when walking in the lake district recently ... was very impressed !!!
That was b4 I updated my firmware... not one drop worked flawlessly...
Locoblade wrote:
So, the conclusion Im rapidly coming to is that its Nokia at fault after all. I dont think it can be the actual processor load issue that some have mentioned as a possibility because the N70 is at least twice as powerful as some other S60 phones that run these apps fine, but what Im thinking maybe is that the phone doesnt give the bluetooth threads / processes a high enough priority, so when the going gets tough for the CPU, the bluetooth processes get shoved to the bottom of the processing list and so it causes an issue.If this theory is correct (and it probably isnt :tongue: ) I was wondering if anyone knew if / how you can up the priority on certain processes like you can with windows processes? Ive looked using taskpsy and can't see anything, but I guess there may be a way?
Chris
I fully agree with you Locoblade, and in fact I have been able to test that during the last 3 weeks with my N70 upgraded to an internal Nokia beta firmware relase v4.0603.2.0.3
The TT behaviour is now better since for example allows me to switch the voice orders to a Blutooth handsfree in my car whereas with V3 or V2 FW it was impossible (TT crashed after minutes working in such mode).
Regarding the usage of tT with single files of speed cameras activated, I've seen also an improvement but still works not perfectly. Now the TT doesn't crash and blocks the N70, but it when I am near a PoI (not all, only some of them) I see like a delay in the TT position, whcih returns to normality after a few seconds. I need to check if the behaviour is the same with the common files of the speed cameras but definitely thN70 is much better than before.
On top of these BT enhancements I have seen others specially regarding the videocalls. Now it is possible to videocall directly when dialing using the right sof key which now is enabled as Videocall.
Summarising, I fully support the idea that Nokia has something to do with all those issues we all have experienced when wotking with TomTom 5.20
Hey guyz i got n70 on 3g want to send it abroad. any one plz plz plz plz plz plz plz plz plz plzzzzzzzzzzzzzzz help me to unlock it. it does not accept any other sim in abroad. plz help me alot of tnQs in advance.
mail me :
[email][email protected][/email]
Hi Everyone :icon14:
I'm having the same trouble With Nokia N70 v3.xxx & TT5 v5.20
My bluetooth connection cuts out after about 15 to 20 mins with the multi pocketgps poi :frown:
I'm going to try the single file pocketgps poi & see how that goes (Thanks to you all) 😊
I don't know if this is of any help, but i have noticed that my bluetooth connection to the gps dose seam to go down my when my N70 goes onto 3G off GSM 😡
I'll try setting it to just GSM, & get back to you :icon14:
I found I could get an hour out of tomtom 5.20 with the latest firmware. Once the bluetooth dropped (headset and gps) I could start it off again by switching bluetooth off and on on the N70 however it would only then be a few mins before losing it again whereas a reboot would earn me another hour.
I use the speed categorised camera dbase from pocketgpsworld although I have all POIs disabled execept warnings for cameras.
I have always been convinced that this is a bluetooth issue for Nokia as musch as a TomTom problem.
Hi all,
Dont mean to p*ss anyone off but i am using tt5 with speed camaras and all poi activated with a Globsat BT-338 and once connected it stays that way until i switch it off, only posted this cause i cant see anyone else mentioning the BT_338. TT5.000 (419), GPS Driver v1.20, Great Britain Map v605, BT-338 s/w v3.11:icon14:
handsome_ilyas - try and ask your question somewhere else - you may get a better response!
Tested tonight with genuine TomTom silver GPS (9821x) reciever and had much better results. Seemed fairly stable on first trip but needed a reboot of phone to re-establish bluetooth connection.
In summary...
N70 + BT77 GPS + FW - 2.0539.1.2 RM - 84 19-10-05 = dropouts every minute or so :frown: - unusable
N70 + Silver TomTom GPS (9821x) + FW - 2.0539.1.2 RM - 84 19-10-05 = stable (ish) 🙄 but required restart of phone to re-establish bluetooth.
I know people have different opinions of what is wrong but it seems to me that there is more than one problem. If my phone phone works much better with one GPS than the other then something other than TomTom or Nokia alone is at fault! FYI -tried my GPS receiver (BT-77) with 6600 and worked fine!
And going back somewhat to a post about bad performance with voice recognition docrob stated he had bad voice recognition problems. I totally agree with crazyjlondon saying TomTom or sat nav is more important than silly voice recognition (who uses that anyway?) BUT the point I think was that the phone handled voice recognition fine when not in TomTom but faled badly when in TomTom - leading one to think there could be a resourse hog within the TomTom software - or maybe within the way the N70 allocates stuff.
Sorry - kind of ranting now - beer has been consumed (but doesn't change the facts!)
Nig
Hi all, just thought I'd add my experience from testing Tom Tom on my own very new (last week) N70.
Having ordered an upgrade to N70, one of the major factors was being able to run Tom Tom, so imagine my horror once I had commited to another 12month contract, got the phone THEN AND ONLY THEN did I chance upon this well informed forum...
After a few days of testing my experiences are list this:
Kit:
NOKIA N70 running latest o2 firmware
TOM TOM 5.2 Mobile
SilverShield bluetooth 16 channel GPS Receiver (�40 on eBay)
Test 1)
Running all POI's, paired through Bluetooth, 15 minute journey around Leeds.
Result)
Took a long, long time to acquire satelites, once running all was well for about 10mins when after hitting a few Speed Camera's etc. phone loses GPS Receiver and refuses to re-connect... not good.
Test 2)
A full run from Leeds to Liverpool & back (damn passport renewal, good way of testing sat nav) I now let Tom Tom pair itself having deleted any previous bluetooth pairings. Disable all POI's, using only the ALERT if Speed Camera POI is on route method, ensure I reboot phone prior to launching Tom Tom.
Result)
Not once did it lose the Receiver (in over 4hours) well actually it did my return journey under a tunnel on Leeds ringroad (which you would expect) on emerging at the otherside it reconnected itself with no problem at all. Also received several phone calls & texts, all answered while Tom Tom was running with NO problems at all.
Conclusion)
Run latest firmware... Reboot Phone BEFORE launching Tom Tom... Disable POI's (apart from Speed Cam on route)... Update to Tom Tom 5.20... Let Tom Tom pair itself with the receiver... Interestingly I found that it acquired a signal much faster if I actually had Bluetooth switched off on the Phone before lauching Tom Tom, which once open will ask if you want to switch on Bluetooth.
As agreed with everyone else its a shame you can have all the POI's running but frankly I can live without knowing where the nearest McDonalds etc is - if it means I can have reliable Sat Nav.
Not entirely sure what is at fault, my thinking being its either a software memory leak from the application, which it can't recorrect when the POI's are running or some kind of odd conflict between the POI's and Bluetooth.
not conclusive but just my two'penneth worth.
nickgun wrote:Test 2)
A full run from Leeds to Liverpool & back (damn passport renewal, good way of testing sat nav) I now let Tom Tom pair itself having deleted any previous bluetooth pairings. Disable all POI's, using only the ALERT if Speed Camera POI is on route method, ensure I reboot phone prior to launching Tom Tom.Result)
Not once did it lose the Receiver (in over 4hours) well actually it did my return journey under a tunnel on Leeds ringroad (which you would expect) on emerging at the otherside it reconnected itself with no problem at all. Also received several phone calls & texts, all answered while Tom Tom was running with NO problems at all.Conclusion)
Run latest firmware... Reboot Phone BEFORE launching Tom Tom... Disable POI's (apart from Speed Cam on route)... Update to Tom Tom 5.20... Let Tom Tom pair itself with the receiver...
Hi,
Glad to hear you are using the same settings and conditions as me, and with the same results. I have not had a bluetooth error for several months using the above method. I assume you also got your passport successfully?
Cheers,
Dez
dez_borders wrote:Hi,Glad to hear you are using the same settings and conditions as me, and with the same results. I have not had a bluetooth error for several months using the above method. I assume you also got your passport successfully?
Cheers,
Dez
Hi Dez,
yes new passport in pocket thanks (only after a 4hour wait though)... off to Barcelona tomorrow for a 5 day break, me'thinks it might just be time to test out Tom Tom 5's European Maps (Much to my girlfriends annoyance no doubt.)
I know my way around the city well - so it'll be interesting to see how it works in Espanol.
Will report end of next week.
Cheers
Nick
crneo wrote:Interesting... I had my N70 working fine for at least 2 hours with GPSCyclemaster and an old tomtom GPS unit when walking in the lake district recently ... was very impressed !!!That was b4 I updated my firmware... not one drop worked flawlessly...
I have a feeling it is to do with the speed that the phone has to update the screen amongst other things, because I used GPS Cyclemaster for a couple of hours when on a bike ride and it ran fine, and likewise when snowboarding last week albeit without any maps loaded (GPS verified 38.1mph 😮 ), but when I ran it in the car with the maps showing so its having to scroll the maps quickly, it dropped. It only did it once so I can't verify, but the drop did happen at about 60mph so the maps were having to scroll quite quickly at the large scale setting.
Try loading up some maps that will cover a reasonable car journey and see if its still stable when you're doing car speeds.
Chris
Does anyone have Tomtom5.2 working with a N70 and 3.0xxxx firmware? I can't get it working. Route66 has also the same problem of losing the BT conncection every couple of minutes. So it seems to be a Nokia problem.
I just called Nokia (holland) and explained the problem. But all they say is to get in contact with my the gps receivers helpdesk. They have to fix it. They say that this is not a Nokia problem. But when I say that this is strange because nobody (all different GPS receivers) can get it working they say they only support the Nokia GPS device (LD-1W) GPS BT Receiver. Arggghhhh....
Does anyone confirm that Tomtom is working with the LD-1W GPS device?
I've just replaced my ADAPT AD-300 GPS receiver for a Tomtom Sirf III receiver. And now is everything working fine (till now).
OK i have just purchased a N70 Vodafone with FW V 2.0539.1.2 19-10-05 RM-84.
I have a gps receiver, and just waiting for my memory card to arrive, so i can install tom tom 5. I have version 5.20
But after reading this thread, do i beleive i am in for a load of serious hassle with this. Is it worth even trying or bothering to get this thing working?
Roden wrote:OK i have just purchased a N70 Vodafone with FW V 2.0539.1.2 19-10-05 RM-84.I have a gps receiver, and just waiting for my memory card to arrive, so i can install tom tom 5. I have version 5.20
But after reading this thread, do i beleive i am in for a load of serious hassle with this. Is it worth even trying or bothering to get this thing working?
Yes it works well as long as you don't use the free gatso database. Mine was excellent yesterday when the M4 was closed so I got tomtom to plot a route around it avoiding Reading town centre at rush hour.
Just to update that my N70, latest o2 firmware, Tom Tom 5.2 and Silvershield 16channel GPS Receiver is pretty much 100% reliable as long as its rebooted before opening Tom Tom and I let Tom Tom pair itself with the receiver.
As previous discussions diasabling the POI aside from Speed Camera warning is a good idea.
Didn't get to check Barcelona function as stupidly left the GPS in the car at the Airport but its worked a treat on half a dozen journeys since, long (200 miles+) or short (10miles+ below) and even taking a call or losing signal from being in a tunnel has caused no problems.
In my experience I have to disagree with the user thinking its speed of the vehicle which causes any connection issues either as mine has worked perfectly at 3mph walking pace and at very much the wrongside of the UK speedlimit.
In summary with a few careful tweaks I have reliable SAT NAV running without any problems at all, and thats using a �40 eBay Bluetooth Receiver NOT the much more expensive Tom Tom or Nokia one.
Ok guys well i just done a short test about 15 mile journey, all pois of, except warn on speed cameras, first 15 miles, lost the receiver, on the way back, i rebooted the phone, and it seemed much more stable.
About the POI`s though, how do you know if you have the tom tom data base, or the free one, mine says pocket.gps i think.
Also i have a question, my GB map is 5.62, what is the version 6?
Well, having had TomTom running perfectly on my N70 for the last 3-4 weeks without a single reboot, I thought I'd share how my setup works.
First, TomTom 5.62, and BT-77 GPS.
I don't use any POIs (lucky if I'm able to even get to 70 on my journeys, and anyway, I rarely speed anymore - either getting old or my licence is too valuble) which probably makes a big difference.
When I power the GPS on, I leave my N70 in locked mode (bluetooth enabled) until the GPS has finished its initial flickering.
Then, unlock the phone and start TomTom. Sometimes it asks to accept a connection from the GPS device, othertimes it doesn't but I've not yet had it not get a connection within 20 seconds.
Then use as normal (this has been on various length journeys ranging from 10 mins to 3 1/2 hours).
Then, when time to shut down, switch off GPS first, then close TomTom. At this point I usually get a blank screen but pressing the hangup button returns back to the home page.
Now I'm sure that some of the above isn't totally necessary however I'm now into a nice routine which takes very little time and most importantly works consistently.
Anyway, hope it helps.
In my experience I have to disagree with the user thinking its speed of the vehicle which causes any connection issues either as mine has worked perfectly at 3mph walking pace and at very much the wrongside of the UK speedlimit.
If thats in reference to what I said, then that was mainly aimed at using GPS Cyclemaster. The disconnections Ive had with Tom Tom havent shown any real pattern over certain speeds, and with only the single PocketGPS database ive not had a single disconnection regardless of speed (in over 24hrs use), although it could be a combination of speed and additional POIs because I noticed when it did disconnect the refresh rate of the map is slower with more POIs.
In summary I think if people want a reliable Tom Tom then most seem to be able to do this without any 3rd party POIs added.
Hi,
Has anyone heard of V5.0606.2.0.6
11-02-06
AM-84
for N70. Apparently it's available for some N70 handsets. Depends on network.
Rob
docrob wrote:Hi,
Has anyone heard of V5.0606.2.0.6
11-02-06
AM-84
for N70. Apparently it's available for some N70 handsets. Depends on network.
Rob
I'm intrigued, where did you hear about that?