What I mean is, if it's a compatibility issue then switching to another unit might not help. Having said that I’ve never had any issues with my w11 laptop.

I’d recommend trying with several sources first. (HiRes) connection stability is very source-dependent, Snapdragon Sound greatly improves it, or if missing try different quality settings.

@iFi audio worth notifying your peers perhaps that, unless Ifi Audio is radically changing its line of business, FB page was taken over last night.

It means they haven’t paired with each other yet. Take them out of the box, put close to each other, eventually they’ll go into pairing mode themselves.

I suggest to correct information on the product homepage, to avoid wrong expectations - it states "LDAC and LHDC (HWA) are both supported to their maximum”.

Ifi-gaia app version should be 1.2.7 and you need to be on the latest FW of course to disable touch.

In case someone hasn’t noticed - iOS Gaia app has been finally bumped to the feature level on par with its Android counterpart. You’ll have the same controls. @iFi audio cheers!

does it happen only when you turn your head to the right or both directions?

There are no shortcuts,Ifi should pick one option out of three: 1. Provide a convenient (for consumer) way to fix issues when they are encountered. 2. Invest a whole lot more into QA prior to releasing the product and then preach about seamless UX. It will never work though, there are always...

Not challenging the concept in the least bit, just - 1. The full set of even those basic settings is available on just one mobile platform out of the two mainstream ones. iOS users are limited to an app version released more than a year ago and by the looks of it not receiving any further...

What I’m saying is - if they don’t improve on current iteration, there’s absolutely no reason to believe the next one will be any better.

There’s nothing preventing Ifi giving current iteration at least a decent app support with controls configuration. All down to priorities and team capabilities.

Hey, question to those who's had some experience with connecting Go Pods to LHDC One - how did you achieve consistency in pairing across different sources (aindroid, win)? For me it's been kind of a hit and miss - sometimes it connects with no issues, sometimes have to try several times, switch...

Or if what you’re asking is does it support multipoint - no, it doesn’t.

You can just disconnect the pods first ( long press until short beep) and then connect from other device.

I for one prefer to adjust either individually, but to each his/her own.

You're making a bit farfetched assumption that s20+ with LDAC behave exactly the same as LHDC One with LHDC. Why not just test it with different sources instead of making assumptions?

If you have any old android dap which can output usb audio it should be giving a reliable true to the content output.

What sample rate is your source using for usb output? Perhaps the dongle adapts to it as it doesn’t make much of a sense to upsample BT signal?

Thrive towards ultimate fidelity is what this hobby is about, fully understand. Yet I dare say its nigh impossible to tell the difference between 96 and 192 on a lossless wired connection, let alone via a lossy BT codec. From a certain point it becomes just a number in specs.

Out of curiosity - how much 192Khz content do you have?

What does it mean "what it should be”? v1.2.5 is 11 months old and not compatible with some of the latest fw features.

Don’t believe the FW update procedure is any different between the two versions. App functionality is limited in 1.2.5.

Would that be the right moment to mention that iOS update 1.2.7 is still to no avail?

Very much execution dependent, pretty hard to get such cocktail to be balanced and not overly source-sensitive.