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

fēnix 7 - Wireless Earbuds Bluetooth Connectivity

Interested to hear from any fēnix 7 owners who've streamed music/podcasts during a GPS activity and can comment on the stability of the connection?

One of the major frustrations with my fēnix 6 is the constant dropping of connection with true wireless buds as soon as I commence a GPS activity. I'm wondering if this is solved in the fēnix 7 and whether there's a newer firmware or revisions to the BT chip?

  • I also leave the phone at home when I go running but still on Sunday the music stopped multiple times and I had to open Spotify and hit play to reconnect. Tomorrow before I go out I'll disable phone connect on the watch and see if I get any issues with playback then. I've tried that last night and today whilst just at home and the music played with no issues. The phone still had Bluetooth on but the watch had phone connect disabled. When I re enable the music then soon stops and the earbuds lose connection. For me on th 955 this is random and not related to a notification. 

  • +1 in this! I tried disabling phone connection of the watch before starting the music and kept it off during the time I listened to music and guess what? No disconnects or dropouts at all! I tried it twice at home for 15-20 minutes each the other day and today at a 60 minute run. All other bells and whistles turned on during the run. After one of the tests at home I tried again immediately after but with phone connection on and the headphones disconnected after a few minutes.

    It would be interesting to hhear if this works for more users. I’ll post again if I experience any connection problems even with phone connection off.

  • I literally just got back from a 5 miler - I did the same as I posted above and 100% no issues at all during the run. When I got back home I enabled phone connection again - the music stopped and bluetooth connection to earbuds was lost within about a minute or so. So for now I/we have a work around! But this is not acceptable on production devices costing this amount of money so it would be good to get Garmin's input here and an ETA of a fix.

  • Hey all! Just wanted to let you guys know that in my case the 9.33 update seems to have stabilised things. I have now been out in three activities with music through Bluetooth- one 33 minute run, one 65 minute walk and today a 2 hour run and I’ve had zero disconnects! This was with phone connection enabled and I had the phone with the on two of them and left it at home for one. So no workarounds needed. And I had severe problems before the update so I hope this means the problem was fixed with the update and won’t come back in the future!

  • This morning’s run was the worst ever for my headphones. After about 2 minutes they lost connection and I never could get them to reconnect. Please tell me there will be a fox for this. I spent a lot of money on this watch and I can’t believe I can’t listen to music consistently when I run 

  • I am still experiencing issues after the 9.33 update. Today I lost connection 2 minutes into my run and couldn’t even get it to connect back 

  • Just tested some headphones with my F7 Sapphire Solar, many of which did not work at all on F5+, F6 or F7 previously as you'll have seen from my other posts on this.

    Updated to 9.33 and I think you have fixed the core issue for "truly wireless earbuds", which most but not all on this thread are talking about. Only a very quick test so far as I wanted to check a few of them and report back. There are still some glitches, but these are different to before and less consistent so I would guess are a different issue, I'll test further and report back if I can find consistent behaviour but right now it's not consistent and could well be interference or weak signal.

    The ones I tested are all Sony, and I've tested and reported on all of these from Fenix 5+ through Fenix 6 and Fenix 7.

    Linkbuds - ok (as before, never any issues)
    WF-1000xm4 ok (as before, never any issues)
    WF-SP700n - ok (as before, never any issues)
    WF-1000xm3 - small occasional glitches but better than before
    WF-SP800N - glitch when GPS locked then occasional small glitches but seems better than before
    WF-SP900 - Seem OK, no glitches so far (previously VERY bad)

    All tested by starting Spotify, playing music, left playing for 20 seconds then back to main screen and start running activity with GPS. Waited for GPS lock and then start activity, listen for 1 minute. Previously the first three all just worked as expected, while the last three would consistently glitch badly upon activity start. Hopefully whatever you did can and will be backported to F5+ and F6 as it seems way better than before.

    I will add that system sounds now seem weirdly high pitch (e.g. lap noise). Is that on purpose?

    Thanks for the effort on this case, it's been going on for years so good to see some hope and progress. Hopefully everyone else is seeing improvement.

  • I just did about a 40 minute run with my fenix 7. I use beats pro headphones. This is the first time I didn’t lose connection. I did turn off Bluetooth on my phone before I started. I don’t understand why this would matter since I don’t run with my phone ever. Can someone tell me why this would matter ?  I ran yesterday for about 30 minutes and didn’t turn off Bluetooth on my phone before I started and lost connection in about two minutes. 

  • I am still experiencing issues after the 9.33 update. Today I lost connection 2 minutes into my run and couldn’t even get it to connect back 

    I am sorry issues continue.

    - What Bluetooth headphones are you using? (Name and Model)

    - Turn off Bluetooth on your smartphone prior to starting your activity. Any difference in Bluetooth connectivity behavior between your watch and Bluetooth headphones?

  • My head phones are beats fit pro. I did turnoff Bluetooth on my phone prior to my run this morning. I didn’t lose connection during my 40 minute run. I didn’t have my phone with me