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

Weird interaction

OK, this happened on Sunday. I fixed it, so I thought I'd report it here in case anyone else runs into the same problem.

I have a Forerunner 945 (obviously), connected to a Samsung Galaxy Note 9 and AfterShokz Titanium headset. I've loaded several albums of music onto my watch. (Basically, the first sixteen albums of the Progarchives top 100 studio albums.) So I set it to play songs randomly while I was running.

Nothing. No sound. No music. (I did hear the headset turn on and announce that it was connected.)

This was the first time I had used this setup, and I couldn't figure out what was going wrong. Max volume on the watch. Max volume on the headset. Nothing.

What I didn't think about was that the phone was set to silent. No announcements and no media. That overrode the settings of my watch and my headset.

Today it works fine after I unmuted my phone. Maybe I'll finally be able to run with music tomorrow morning.

0 ericgottlieb over 5 years ago

I have not encountered this, but was the headset connected to both the watch and the phone at the same time? I usually go out of my way to ensure that my Trekz Air are only paired to one device because they do a pretty poor job of handling being connected to two devices at once. So... I’m not too surprised you ran in to this issue.

0 winfij over 5 years ago in reply to ericgottlieb

I have the same with the AfterShokz Titanium - I wait until I have run far enough from the phone left in the car that they won't connect before turning them on and starting music from the FR945, no problems that way.

If they connect to the phone first on powerup it's a bit hit and miss whether they work with the 945.