So I went for my first medium-long run with the 645M that I got in the mail yesterday. I was so excited.
About 2 miles in my music cut off. I thought it was just a long pause between songs, but after a bit, I stopped and looked at the watch face. Big triangle of death. Thought it was resetting so I gave it a minute or two. After that I did a soft restart but it seemed to get hung up and still had the triangle. I waited around for like 5 minutes to see if it would resolve itself. I restarted it again. Same thing. Having wasted 7-8 mins just standing on the side of the road, I just continued the run. After about a 1/2 mile, I noticed the watch went back to the run screen. After a few more minutes the music came back on. ANNOYING.
Seems like there are some software kinks that need to be resolved. One other odd bit I should mention--when using Garmin Express to sync it to my PC, it hung on the initial setup screen for literally *hours*--you know the part where it says it's uploading data? I have a lot of runs but it really shouldn't take *hours*. I used GE to connect it to my Mac & it synced within minutes. I'm not sure what's that's about. Still can't get it to work on my PC.
Also, I find the blutooth range is suspect. Using a pair of "approved" headphones (Jaybird x3), I get repeated--I mean like easily replicated--dropouts if I put my arm to my side (yes, both watch & blutooth dongle on headphones is on same side). While running, and my arm is in a 90 degree angle, it's perfect. It's just a walk where I get intermittant cutoffs. Really disappointing. My Apple Watch 3 paired with Jaybird x3s experience some cutoffs too (as do all blutooth) but not like this--having my arm extended normally with normal walking arm swing.
Gonna give it a few more runs before I RMA it back to Amazon; hopefully a patch or something is in the works because the current software doesn't seem like it should be out of beta.
Software Version: 2.40 (226df85)
