Works perfectly for me
Works perfectly for me
You can add your own POI * (like radars) but you can't set up a warning sound (yet) in TT for your own POI.
An option is to have another radar app running in the background.
I have [Only registered and activated users can see links. ] running simultaneously , this app is using the SCDB radar database and gives a warning sound, while you have the TT screen up for navigating.
BTW [Only registered and activated users can see links. ] is exactly the same app as CamSam, but with a different name.
* to add POI, copy the POI file with *.ov2 extension to \Android\data\com.tomtom.gplay.navapp\files\files\personal\pois\
Last edited by pietpisvlek; 4th February 2016 at 11:03.
Got this working on a Nexus 7 (2013) wi-fi without any problems with installation, as well as on a Galaxy S.
My problems starts after about 30 mins when I come to a stop at traffic lights or round abouts etc. the map starts turning through either 90 or 180 degrees, then can take up to 20 seconds to re orientate itself after the car starts moving again. This happens on both units with the Nexus 7 running marshmallow 6.01 and the Galaxy S running a custom rom of lollipop 5.1.1 with uk & ireland map.
Anyone else experienced this occurrence?
Yes, I have the same problem with my Huawei Ascend. Not really a problem for me because if I start driving again it is back on position again instantly.
Maybe heat-insulating glass or not a very good GPS receiver like mine. Put in in a different place in your car and see if this gives better reception.
Last edited by duur1duur; 5th February 2016 at 18:27. Reason: text correction
I appreciate your reply, but, in my case, there are 2 different units running different versions of Android which have been placed on the windscreen, on a designated vent mount as well as the car seat and hanging from a sun visor, in every case the same problem shows itself. I am going to try it tomorrow on a Galaxy S4 to see what happens, it may be a common problem due to a bug in the software.
It seems that this problem does not occur everywhere. I went up to Manchester airport Saturday, a round trip of 364 miles, without any problems with my galaxy S4 running stock lollipop 5.01.
I think I will put lollipop 5.01 on both the Nexus 7 and the galaxy S out of curiosity to see what happens and let you know, although it will probably be Thursday before I do them.
For those that are interested and don't mind experimenting, I have now tried this version of of TomTom under Lollipop 5.01 & 5.1.1 on my Nexus 7 (2013) wi-fi tablet and it run's fully stable under both Lollipop 5.01 and 5.1.1 with no drifting when stopped. I had no success on the Galaxy S and I have tried custom roms based on 4.4.4, 5.01 and 5.1.1 so will stick with TomTom 1.4 on that one, it's only a plaything anyway.
I needed to re-download the map each time as each install would not recognize the map from a previous installation, backing up the application itself using both Airdroid and Titanium backup was immediately recognized without needing to install from the playstore first.
I hope this information helps someone as having the map drift when stopped certainly caused me to get kranky and swear a lot.
Now to try and stop the Marsh Mallow software update on my Nexus