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

Watch freezes when external TEMPE sensor is connected

Today it happened to me the second time. I was using my watch on a hike. Course navigation was turned on and after about 2-3 hours of recording, when I scrolled to the temperature datafield, the device got completely frozen. I had to do a soft reset to get it work again.

In fact, at the first time I was also experiencing extremely slow or even completely not responding navigation. I mean, the arrow that shows the current position didn't follow me on the map and after the first turn the watch didn't give me more instructions about turns. I think this behavior was also related to the TEMPE sensor because I didn't experience the same when I was not using my TEMPE sensor. 

Have you seen similar problems with or without TEMPE sensor?

  • I always use my Tempe and have had no issues.  I don't have the temperature on a screen by itself.  It sits on a screen with two other data fields. I also have not yet used my 945 for course navigation. Does it only happen with course navigation or on any run?

  • I've not seen this issue with the tempe sensor and I've used the 945 12/hrs/day for 2*2 week hikes. However I have seen the extremely slow watch response at the beginning of my hikes but that has always sorted itself out after 30 mins or so. I have routing set to ”Follow Courses” rather than ”Use Map” which i think is the same as you? I have a watch screen set up with current temp and min temp displayed. I guess the next thing for you to try is a hike without the tempe sensor.