Slow Install (GE on Mac to nuvi 3597)

 

Is it me/operator error, or something else? My 3597 seems to just stall and shows 30 or so hours to install using GE. This is my third time installing. First time I had to leave it to install overnite. The map is already installed to the computer, so download went pretty quick. When the stall happens is when install starts.

Second time I used the clone method, but I lost one of the installed maps. (I know that was operator error!)

Third time I'm showing 30 hours again. I'm on a MAC, but that shouldn't make any difference.

My DS55 took a longer time loading over WIFI. Almost three hours instead of 30-45 minutes. Is this map that much larger?

--
Frank DriveSmart55 37.322760, -79.511267

3597 map update.

I didn't have any issues installing 2022.25 on my two 3597's. My DriveLuxe 51 gave me some grief ... not during the install, but when I rebooted afterwards. The screen went all wonky and it eventually crashed. It continued to happen after several reboots. Then all of a sudden it straitened out on its own and has been OK since (fingers still crossed).

--
Alan - Android Auto, DriveLuxe 51LMT-S, DriveLuxe 50LMTHD, Nuvi 3597LMTHD, Oregon 550T, Nuvi 855, Nuvi 755T, Lowrance Endura Sierra, Bosch Nyon

mac?!

I don't know Mac, but the basics are:

Restart the computer. Restart the 3597. (not just sleep)

Remove all other USB devices from the computer. Plug the Garmin USB cable directly into the computer.

In Garmin Express, delete the 3597 and re-detect it. In Windows, that would install a Garmin USB driver.

For the 3597, half the time, Garmin Express says the map update installed correctly, when it really hasn't. It installs properly the second time.

When the 3597 firmware is updated, Garmin Express is supposed to restart the nuvi to install it in memory, but that never happens. I always have to restart the nuvi and then popups show the firmware install.

Several of the above are 3597 issues, not Mac or Windows issues.

I've done all those things.

I've done all those things. I jsut don't. know what's wrong. It looks as if Garming has throttled the download speed some, but the install is just agonizingly slow. And I don't want to interrupt it in the middle of the install.

--
Frank DriveSmart55 37.322760, -79.511267

Some things to try

phranc wrote:

I've done all those things. I jsut don't. know what's wrong. It looks as if Garming has throttled the download speed some, but the install is just agonizingly slow. And I don't want to interrupt it in the middle of the install.

Not a Mac expert by any means but I would start with

1. Optimize your system first with the Mac repair app just to be sure there aren't any issues.

2. Check your various USB Ports and make sure you are using something compatible with USB 3.0. In addition, once the best port is found, do not go through any form of hub.

3. Locate and disable Spotlighting on the which is an indexing utility that is part of the Mac OS. Normally Spotlighting indexes a USB drive, but it may very well index the Garmin

Follow the steps below to do this:

Open System Preferences and select Spotlight.

From the window, click on the Privacy tab.

Click + button at the bottom to add your USB drive.

The next time you plug your USB drive, Spotlight will ignore the storage device and you can transfer files normally.

--
John from PA

If there is another map

If there is another map update failure:

If the map data is going to a memory card in the 3597, what you are describing sounds indicative that the memory card is reaching the end of its useful life. The card will be recognized (in Garmin device or computer) and data can be read from it easily, but attempts to write data is where the failure happens. If you have one, pop in a different 16GB or 32GB card into the 3597 and try that.

PCs in general (Windows, Mac, Linux, doesn't matter) don't really know how to recognize a failing memory card, much less tell you about it. In Windows there is the H2testw program download to test for write errors on a card, but you're on Mac, so the easy thing to do is try another card.

I fixed it. I had to

I fixed it. I had to reformat the SD card. It took the lower 49 without the SD card in less than an hour. After formatting the SD card, it installed the full map in about an hour.

--
Frank DriveSmart55 37.322760, -79.511267

incipient card failure

frostedside wrote:

...
PCs in general (Windows, Mac, Linux, doesn't matter) don't really know how to recognize a failing memory card, much less tell you about it.
...

On my DashCam 56 I once got a message indicating an incipient card failure. IIRC it recommended formatting the card.

Good to know the DC56 has

Good to know the DC56 has that kind of write failure detection programmed into it. On my Viofo dashcam, all I have is an option to auto-format the card every X number of days. That's not a warning system, but better than nothing.

High Endurance μSD cards.

frostedside wrote:

...
PCs in general (Windows, Mac, Linux, doesn't matter) don't really know how to recognize a failing memory card, much less tell you about it. In Windows there is the H2testw program download to test for write errors on a card, but you're on Mac, so the easy thing to do is try another card.

If there is a concern about wearing out the μSD card, SanDisk manufactures 32GB "High Endurance" and "Max Endurance" μSD cards priced around $9-$13. I haven't used them in a Garmin, but have used them extensively in a Raspberry Pi (running Linux) without issue. Samsung has a "Pro Endurance" μSD card with similar specifications to the SanDisk.
Mark