4f170 Bridge active map

[pobelka.potolkov]

Does anyone know how to change the active map on this device? (Bridge)
The Europe map with all countries is currently installed. In the list of other countries it is impossible to make a choice, they are all inactive.

I only want to use a few countries. And I'll free up some storage space

I realize that this navigator is not intended for the casual car user. I bought it for myself due to my employment as a truck driver.

 

[canderson]

It is not possible to reduce the map if the device is now connected to Webfleet. Any edit (see below) will cause the application to fail a special version of a checksum.

If it is still connected to TomTom, there is a way to do it, but it requires the editing of the update-locations file with a bunch of 'excludes' statements. You must first determine the names of the map segments that are normally included in your map build, and then exclude them.

If you wish to risk it, here is a snippet of what 'excludes' look like in the update-locations file. Just be SURE that you keep a safe copy of your original update-locations file somewhere before you try this:

{
"schema": "2",
"uris": [
{ "uri": "https://bridge-files.tomtom.com/betatest/build/device.production.m/package-list.system" },
{ "uri": "https://bridge-files.tomtom.com/betatest/content/package-list.content.north-america.nds" },
{ "uri": "https://download-tls.tomtom.com/bri...ge-list.content.north-america.alabama.exclude" },
{ "uri": "https://download-tls.tomtom.com/bri...list.content.north-america.alabama-3d.exclude" },
{ "uri": "https://download-tls.tomtom.com/bri...age-list.content.north-america.alaska.exclude" },
{ "uri": "https://download-tls.tomtom.com/bri...ge-list.content.north-america.alberta.exclude" },

 

[Jamal_013]

Hi, I have found this configuration while searching the forum for some information about TomTom Bridge.
It points to an exciting software build. It looks great, very modern and comparable to current TomTom devices. Unfortunately, it is very unstable and poorly optimized. Do you know if there is any way to make it run smoothly on out trusty TomTom Bridge?

Regards,

 

[canderson]

Hi, I have found this configuration while searching the forum for some information about TomTom Bridge.
It points to an exciting software build. It looks great, very modern and comparable to current TomTom devices. Unfortunately, it is very unstable and poorly optimized. Do you know if there is any way to make it run smoothly on out trusty TomTom Bridge?

Regards,

I am unclear about what you are asking.

What app are you talking about, and where would one find it?

What build are you talking about that is "unstable and poorly optimized"?

There are only two sources that I know about for the primary app for a TomTom Bridge - TomTom's dev site and the Bridgestone site. Further, once you've switched to Bridgestone, there's no going back to the TomTom builds.

 

[Jamal_013]

I am unclear about what you are asking.

What app are you talking about, and where would one find it?

What build are you talking about that is "unstable and poorly optimized"?

There are only two sources that I know about for the primary app for a TomTom Bridge - TomTom's dev site and the Bridgestone site. Further, once you've switched to Bridgestone, there's no going back to the TomTom builds.

If you create an update location file that directs to : { "uri": "https://bridge-files.tomtom.com/betatest/build/device.production.m/package-list.system" }, system will update to build ver. 19.121.1534.ce7f7f7.136.

 

[Jamal_013]

19.121 - That's the version I was referring to.It is great looking but very slow and crashing a lot. Is this the latest version available? I also own Webfleet 8475 - any idea if it will receive NDS maps?

 

[canderson]

By using the update-location file you have there, you get whatever is currently in the queue for testing. It calls it device.production.m in the filename, but what that refers to are devices that run 'production' (vs. custom) code, not something that would necessarily pass as production level code.

The version I'm presently running on my TomTom version unit (vs. Webfleet unit) is 18.623.1637.136
It has been very stable for me.

Your device is using 'Classic' maps. You'd need to switch the device firmware over to NDS along with a new map set. Your firmware wouldn't know how to interpret the NDS maps.