• State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 5 subscribers
  • Views 3080 views
  • Users 0 members are here
Options
Related
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

Need to restart to connect to sensors

meste7
over 5 years ago

I wonder if anyone else has this behaviour. Sometimes I have to restart the watch Expedition to regain connection to my sensors. The same on stable and beta FW.

  • 0 over 5 years ago

    Are you using the default watch face?  That used to happen with my F5 using 3rd party faces.

  • 0 over 5 years ago in reply to bjrmd

    yes, default watch face

  • 0 over 5 years ago

    Sensors do only work during an activity is known?!

    Don't have this problem on mine ... running Beta 3.31

  • 0 over 5 years ago

    Let me explain it more clear - I run, all fine, then next day when I want to run again, I start the app but HR belt is not connected. I have to restart the watch and then HR belt is connected. The same happens with my FP.

  • 0 over 5 years ago

    I’m assuming, like me, you have the RunScribe Plus CIQ data field installed ( @meste7 and I are active on the RunScribe community forums too). I have seen this same behaviour, but I think it may be some clash caused by the RunScribe CIQ data field trying to open ANT channels to search for the pods and somehow that’s causing all ANT to fail on the MARQ. My Fenix 5+ doesn’t have this issue with the exact same setup, which I’m still using alongside the MARQ for comparison, so it’s some unique to the MARQ.

    @meste7, given you’re on 2.31 beta, it might be useful to pass on your observations to [email protected] if you have time.

  • 0 over 5 years ago

    Have exact same problem. Every now and then MARQ Athlete would refuse to connect to one of the sensors or all of the sensors, whether BLE or ANT+. A few days ago it was Polar H10 (via ANT+). Yesterday it was Stryd. In both cases, restart fixed the issue.

    Possibly related to that is the battery drain: the watch uses almost no battery upon restart after being charged up -- like less than 7% in 24 hours with full BLE connectivity to phone. But as soon as an external sensors is used, or GPS, or headphones when activity is started, the watch starts gobbling up battery like there's no tomorrow. I did 1.5 hours run with GPS, external heart rate, and music yesterday and about an hour more of spin bike with music and external heart rate, I'm down to 50% having been about 92% in the morning of that day.

  • 0 over 5 years ago in reply to Crispin_Ellisdon

    I'm on stock F/W and I have a very similar issue. Sometimes the watch simply refuses to connect, sometimes something else freezes up like showing some internal step ids in structured workouts as opposed to names/exercise names. In all cases there's always increased battery drain.

  • 0 over 5 years ago in reply to nickk

    The same with me (I have Runscribe Plus datafield installed).

  • 0 over 5 years ago

    I am on the latest FW and still have this issue quite frequent. I wonder if Garmin is aware of this issue...