Earbud/headphone database for Venu 2?

Works fine with my Buds+ and Buds Pro,also fine my wife's Buds+ on her Venu 2S..Both on left wrist.I only heard once a little interruption on my Buds Pro,but the watch battery was very low..

Gabriel, can you confirm that your usage was during running?  My buds+/live also work fine until I start running, that's when the cut-outs start.  The earbuds were at 100% when I started the run and watch was >50%.  I thought it may have been due to local interference but yesterday I went in-line skating in a rural park still had cut-outs.  I also notices that they happen much more often when I'm listening to music versus something that requires lower bandwidth, like a podcast.

Gabriel, can you confirm that your usage was during running?  My buds+/live also work fine until I start running, that's when the cut-outs start.  The earbuds were at 100% when I started the run and watch was >50%.  I thought it may have been due to local interference but yesterday I went in-line skating in a rural park still had cut-outs.  I also notices that they happen much more often when I'm listening to music versus something that requires lower bandwidth, like a podcast.

No,I'm not running..I'm doing "fast walking" at 6.5 - 7.5km/h speed..I'm doing 7Km and 10Km sessions and I'm not having this problem with the buds..To be honest I'm not taking the buds every day,I do it mostly when I'm tired to give me some rhythm..

8297442 said:

My buds+/live also work fine until I start running, that's when the cut-outs start

You may be affected by cross-body interference.  The majority of the population is right handed and wear their watch on their left wrist.  For reasons unknown to me, most wireless earbud/earphones have the main receiver on the right unit.  When running, your natural arm swing is more exaggerated compared to walking and when your left arm swings towards the back of your body, the signal is blocked by your body and you can experience cut outs.  You can test this standing still by moving your left arm towards the back of your body, or by turning your head to the right.  I don't own the V2 or Samsung buds, but I have experienced this with my Bose Soundsport Free's on my F6 and 945, but I have to deliberately try to interrupt the signal.  Some receivers will just work better than others. 

All of the earbuds that I have used have receivers in both buds (they can be used independently).  I performed some limited testing and here are my findings.  For the cut outs to occur GPS has be recording (though I didn't try to actually run w/o GPS logging so that's for next time).  In-house w/o GPS logging I get no cut outs.  With GPS logging I was able to induce the cut outs with high probability when my arm was bent in such a way that it was high and close to my body with my palms pointing up.  The watch at this point is approximately 20cm / 8 inches below my armpit.  The closer to the body the worse the cut-outs.  I switched the watch to my left hand and was able to induce the cut-outs in the same position but the severity was not as bad.  I'll do more testing next time I actually go for a run.

A bit off topic but is it necessary to change which arm the watch is on in the app (I remember it's in the settings somewhere) if I do decide to run with it that way or do the algorithms compensate?  I guess I could easily test this but there has to be some reason why Garmin asks for this info...

Soundpeats TrueEngine SE don't work on Venu 2s. Stays in a constant loop of connecting and disconnecting.

Sony WF-1000XM4 and Jabra Elite 85T work perfect with this watch on the left wrist.