Tread 2 Firmware 3.50

Discussion related to the Garmin Tread, Tread SxS, Tread Overland, Tread Overland XL, Tread Baja, and Tread 2 Powersport/Overland/SxS Navigators
Post Reply
User avatar
GPSrChive
Site Admin
Posts: 4249
Joined: Fri Jan 20, 2017 11:29 pm

Tread 2 Firmware 3.50

Unread post by GPSrChive »

Tread 2 Firmware Update 3.50 released 21JAN25:

Changes made from version 2.50 to 3.50:
  • General bug fixes and improvements.
  • Added support for the new zümo R1 Radar.
  • Improved support for Outdoor Maps+.
Please share your observations here!
bananachunks
Posts: 7
Joined: Sun May 16, 2021 2:58 am

Re: Tread 2 Firmware 3.50

Unread post by bananachunks »

After having another loss-of-touch episode this past weekend, as well as my first loss of charging (hopefully due to whatever was causing the loss of touch), I was able to once again reset the device while plugged in to a high power [Click to connect to PC - enabled] power source. I got touch back. Figured I might as well enable wifi and update while I could - maybe an update would fix things? I have yet to see if the loss of power issues were taken care of (or if, as per usual, it's the cable) - I guess I'll find out this weekend. What I did notice right away was that I can no longer hit one of the 4 handlebar remote buttons to get into the map display. Previous to the 3.50 update, after hitting [+] to accept the always after bootup Agreement button, I could then hit any of the remote buttons to take me from the main device screen to the map screen. Now it just gives me a popup of something along the lines of "Zoom In [+] (or insert whatever function is programmed to the button, here) is not available". Once I touch the screen to go into map view (not easy if, say, the device isn't accepting touch) the remote buttons then act as expected. I'm guessing this was a "feature" added by the new update...? Anyone else seeing this and/or know of a way to put things back the way they were?

I also noticed this weekend while my device was not allowing touch and not charging (and of course, not accepting input from the remote), that "Send location to device" from the Tread app was not actually doing anything, even though the app would respond with "Location sent to device!" This was the only way I could use the device the first time it lost touch and I didn't yet have the remote. Hopefully this is fixed with update 3.50 - again, I guess I'll find out this weekend.

Just a reminder that this is my second device after the first one permanently lost touch less than two weeks after getting it.

So far it appears that Garmin is indeed keeping up the "good" work 🙄 *eyeroll
Post Reply

Return to “Tread”