This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New 2018.10 map routing not working properly

Yesterday I updated the maps and went for a drive with navigation routing set to Automobile Driving with lock on road ON (see screenshot for GPS settings), the result is that the device now gets confused and will usually recalculate and lock on adjacent roads that run parallel or near the road you are driving on making navigation unusable.

For example on a 2 km stretch of straight road segment where I am proceeding on, it would think that I have deviated several times off the route sometimes on roads that are as much as over 50 metres away from the one the car is on. As a result on this 2 km stretch it recalculated about 7 times despite no change of direction.

I will post a link to a youtube video when I get the chance to show the flawed behaviour of my updated unit side by side with the proper behaviour on my other unit. My other unit has the old maps and old GPS chipset firmware and is rock solid in navigation.

I really think there is something seriously wrong with these new maps (I also already posted about the thin graphics style earlier on) or possibly GPS chip firmware.

Please let me know if you can also reproduce this (please see screenshot for routing settings). ciq.forums.garmin.com/.../1340645.jpg
  • You may want to keep you existing Gecode map as this is the only map that is locked. The unl file from the other unit will not unlock it on your device as they are key off the units serial number.. All the other maps are unlocked.


    Alan,

    I followed rob-tech's instructions and it seems to work. The only files that I copied from the other unit are the 3 img files.

    What should I do to verify that the new Gecode map is unlocked.


  • You know that the maps work because you can enter street addresses and search POI's. Also there in no error about failing to unlock maps when the unit boots from a powered off state.

    Do not worry about this, I based my steps on the file structure of an un-updated 1030 from a riding partner, new units only have one .gma file which is named using a series of numbers that is unique to that unit. Since these happen to be the same maps as the 1030 originally shipped with, unlock files are not required. If you follow my steps the file structure will be identical to a unit bought on launch day.
  • rob-tech,

    Thanks for your help. I now have usable navigation and maps with thicker lines which I really like. I don't get any error messages on boot up and I can search for a street address and POI. All is good! Your instructions worked perfectly.

    I have attached a screen snag of my downgraded 1030. Is the GMA file, highlighted in green, the one linked to the serial number of the unit which then unlocks the downgraded Gecode maps?

    I also downgraded my firmware form the 4.0 disaster to 3.9. Should I stay on 3.9 for now or is 5.0 worth the risk?ciq.forums.garmin.com/.../1371012.png
  • Second try for GMA screen snag image. Hopefully it is higher resolution this time.ciq.forums.garmin.com/.../1371016.jpg
  • rob-tech,

    Thanks for your help. I now have usable navigation and maps with thicker lines which I really like. I don't get any error messages on boot up and I can search for a street address and POI. All is good! Your instructions worked perfectly.

    I have attached a screen snag of my downgraded 1030. Is the GMA file, highlighted in green, the one linked to the serial number of the unit which then unlocks the downgraded Gecode maps?

    I also downgraded my firmware form the 4.0 disaster to 3.9. Should I stay on 3.9 for now or is 5.0 worth the risk?


    Yes, that's the one, this file should never be touched as it is unique to each unit, and is probably required for future map updates.

    Firmware 5.0 seems to work quite well for me with several rides of 40 to 100 km in length. The only thing that is not working correctly but used to work in 3.9 is bluetooth le phone auto pairing. Auto upload and tracking is reliable so far however, I didn't get a chance to use group track or live track yet.

    I use all the core sensors from the bundle but no power meter yet.

  • rob-tech,

    Thanks for your help in getting the 2017 maps working and for answering my questions. Really appreciate it!
  • I'll see if the next stable firmware release fixes these routing problems (but it's unlikely since the map seems to be the problem), if not I'll have to contact Garmin as this is not really acceptable. It shouldn't take them many months to fix something like this, as it's basic functionality.

    The issue has been acknowledged but there is nothing to show for it. It broke after the 2018 map update and works with other maps, therefore logically a new map update should be released that reverts whatever change is responsible.

    We should not have to wait an entire year for a working map that supports basic GPS features.

    This mishandling of these issues is really souring my perception of the brand.
  • Former Member
    0 Former Member over 6 years ago
    For info - I am in Western Australia and using a 276Cx (updated from a 276C). Since purchase in Dec 2016 I have been in constant contact with Garmin Support Australia regarding inaccurate & false routing issues with the 276Cx (and other "bugs"). I had never had any issues with the old 276C using map set 2017.1, but was not able to load this map set into the 276Cx as a test .. The 276Cx was initially loaded with 2017.3 CN Aus & NZ Mapset & Topo Aust Full v5; later upgraded to 2018.3 CN....

    As I regularly travel the Remote Outback areas of West Aust it was obvious that consistent Routing errors were calculated and no manipulation of avoidance parameters would correct these anomalies. At Garmins request I have forwarded, over the last year, Screen Shots, Mp4 videos, complete 276Cx File System, in an effort to help resolve the issue. Other Routing systems used ie iMaps & Google maps displayed the correct "Shortest Distance" but the 276Cx sometimes added 100's of Km, via totally obscure Routes - not good in Outback where fuel & water is an issue....

    Recently, I sourced the Open Street Routable Generic map set for Garmin and confirmed that it behaves correctly with Routing Calculations accurate and comparing favourable with my old 276C (using 2017.1) and iMaps; Google maps.... ie It confirmed that the issue was NOT related to the 276Cx ....

    Upon informing Garmin Australia they promptly offered and have immediately refunded me the 3 x map sets purchased for the 276Cx. Obviously, what concerns me is that, this forum post identified the Routing Issues with map sets later than 2017.1 back in March 2018 but, it would appear that the issue has been kept "under the raps" and not acknowledge .... possibly because of the huge financial ramifications relating to "Consumer Laws / Fit for Purpose" in various Countries ....

    It would appear that after Mapset 2017.1 Garmin maps have gone "astray" and unfortunately with these Maps used in many different Garmin Devices we all are left with "Sub Standard Routing" ..

    At this point I will still continue to use the 276Cx, but will stick to Open Street Maps ......

  • The new maps have heat profiles (popularity routing). Did you have that switched off under the routing options.


    aweatherall what do you mean , if the old map are installed , you cannot use round trip? because I sow that is working

    @rob-tech , is this issue fixed?
    I have bought an 1030 and I don't know


  • No, this is absolutely not fixed and what makes it more disappointing is that the issue exists for half a year, it was acknowledged and then complete silence.

    How difficult is it to fix the map which is unsuitable for purpose and release a new one. Maybe I should get a discount on the unit because part of it is unfit for use (I should pursue something like this and I might), unbelievable really and a complete joke for a company with Garmin's resources that claims to be the leader in navigation solutions.

    Shawn-Garmin, any updates on when we can expect a resolution or will this go on in complete silence until 2019 maps are released which are still broken?