[MTCD Android Head Units General] SkyBeam2048:
Which is true. Even the thread title says MD725: [PX5][MD725] Solution for the bluetooth echo v2

Be fair please. [MENTION=7621504]f1x[/MENTION] even tried to help by analyzing the SD968 driver and spent time on this. Unfortunately he discovered he can't do much at the moment. End of story, he can't help you right now. No matter how often you ask in different threads.

You're asking in threads which are either general purpose or not Bluetooth related. A general thread is fair enough to ask again. People here have been so kind to point you to the most appropriate thread about Bluetooth driver issues. Also [MENTION=7621504]f1x[/MENTION] is by far the most person with most knowledge about MTCD Bluetooth infrastructure and drivers by now. He stated not to be able to help currently.

As you are sure SD968 is affected but not handled in any of those threads. I ask you to open a new thread. Perhaps also others will join you and discuss potential impacts and work-arounds. As of my knowledge there is no specific SD968 thread yet. So even if others have the same problem it's hard to find those reports in all general threads and off-topic discussions in there.

What is interesting is that there are some reports about SD968 to work just fine in Bluetooth calls. So the problem there might be a completely different one like interferences, hardware issues (antenna etc.) or incompatibilities between certain mobile phones. It's also within the nature of people to believe that others might have exactly the same problem and somebody should do something to help them all while in fact all of them have problems with different source. Like some are unable to set the proper pairing code, some have broken unit, some have bad antenna, some have issues with their phone.... all of them complaining "Bluetooth not working, we all suffer from the exact same problem!".

So first attempt usually is to try getting the problem resolved. Update to different ROM or even try multiple ones as already suggested. Try different phones, check the antenna of your unit, try to pair various different devices, turn of WiFi during Bluetooth use etc.

If you can't find a solution you can try to contact your vendor or the unit manufacturer. Although it's unlikely they send you a fix right away they might start investigating if many people complain. In best case they would release the sources so we can fix it (assuming it's a software issue).

Last options are to start investigating yourelf. Root the unit, check the logs, analyze code (although in case of SD968 this is difficult as mentioned). If you are not skilled to do it yourself then hire somebody doing it, or if you trust a developer, feel free to buy a unit and send it to [MENTION=264886]FIX[/MENTION]. He might be willing and able to help if he has such a unit. It would not be the first time things get solved this way.

And, as a last resort: Give up and declare your unit with SD968 as unusable. Sell it and get something different. Or just live with the limitations.

OK; I think these are all the options you have. I think people here really tried to help you and others but there are limits and we are not producers (neither manufacturer not seller) of those units and there is limits what we can do and we have to be realistic about. Sorry to say. But you still got a couple of options to chose from :)