A small number of handsets are known to be affected by the "call muting bug" (model list at bottom of this article). For affected users, when making or receiving a phone call, the person on the other end of the call will hear what the Forcite user is saying, but the Forcite user can not hear what the other person is saying.
On Android devices, this can occur when the Forcite app attempts to push an audio notification, such as a navigation instruction or an incoming road event alert, whilst you are on a call.
On iOS devices, this can occur if you use Spotify (not iTunes) and start a song while you are on a call.
The best workaround until the bug fix update arrives is to not take calls while navigating, or turn off alerting inside your Forcite app if you expect to be taking a call on your ride. Or on iOS, don't play music from Spotify while on a call.
We apologize for this inconvenience, and we are working hard to solve this issue in a firmware update to be released in the near future. Because the update effects low-level, general Bluetooth behaviour, the solution needs significant development and testing before it is safe to release.
In the meantime, if you do experience the call muting bug, the Forcite development team would appreciate it if you could report the bug along with your phone make and model, as well as your Android version (usually found in settings under "phone info" or "About phone") using "Submit a request" above.
So far, this bug has been discovered on the following Android handsets:
Samsung S20
Samsung S20 Ultra
Samsung A21s
Pixel 3
Pixel 5
Pixel 4a