2 June 2022
If you use an iPad, and other people have started complaining about hearing an echo: the problem is probably caused by your iPad. There is a solution. The solution has to be applied to your iPad.
If you have recently started hearing an echo of your own voice: the problem is probably caused by somebody else’s iPad. If it happens all evening, it is probably your partner’s iPad. If it only happens at some tables, it is probably an opponent’s iPad. There is a solution. The solution has to be applied to the iPad. Please ask the iPad user to look at this page, or to contact RealBridge via support@realbridge.online
This problem occurs when the iPad has been upgraded to iOS 15.4 or iOS 15.5, and the iPad is one of:
If your iPad is newer than that, your iPad is not causing the echo problem.
If you don’t know which iPad model you have, look in the iPad's Settings: General on the left, About on the right, Model Name on the right.
Note: the iPad Pro 11-in doesn not have the echo problem.
This may seem strange, but it does work.
You will need a headset that has a standard 3.5mm audio jack (or anything else that has one of these jacks). That is, the type of plug that has a single circular pin, with a few black stripes on it, like this:
It can be headphones, or earbuds, or a hands-free kit for a mobile phone, or a cable. It can even be just the plug, without anything attached to it.
It doesn’t matter how many black stripes it has. It doesn’t matter how good it is. It doesn’t matter if it actually works or not. All it needs is the plug.
If you don’t have anything with this type of plug, you can buy a headset or cable with a 3.5mm plug very cheaply. If you can’t find one, email support@realbridge.online and we will post one to you.
This is what you have to do:
This works because the physical action of plugging in and unplugging the audio jack resets the echo-cancellation on the iPad.
If you can't find your a headphone socket on your iPad, please contact support@realbridge.online for advice.
The solution above is just a workaround – in the medium term we expect Apple to fix this in their software.
The problem has been reported to Apple on their defect-tracking system: https://bugs.webkit.org/show_bug.cgi?id=239285