Given the types of products that are made with BT support, the hostile environments that they're developed within, and the common after-sales abandonment of support, BT should be a simpler protocol that is a LOT more resilient to implementation mistakes. But I don't think that anyone designs protocols to withstand institutional failure :-)
When you combine randChip with randBtStack, the end result is not necessarily a quality product. The poor engineers who have to work with this combination end up resorting to sending reset commands to their chip in an attempt to get the damn thing working.
The two issues I saw were Bluetooth is based on a frequency hopping radio using a dated low performance modulation scheme. The only nice thing you could say is potentially you can build really low power radio's using that design. However that brings up the second issues, a very complicated kitchen sink base band which requires a complex software stack and power hungry processor to support it. There goes your low power, out the window. (I think there were about 20 companies trying to design low power Bluetooth transceivers circa 2000-2003, most of them never could get the power low enough or a working stack)
Hardware design issues aside, frequency hoppers have insurmountable quality of service issues for most applications. Professionally I don't think this is fixable.
They would have been better off doing the following three things.
1. Define a low speed point to point oriented modulation scheme that can be supported by 802.11 radio front ends. Probably could have implemented this as a sub-band of some sort.
2. A direct sequence spread spectrum physical layer for USB. Advantage of that is the USB stack mostly works as USB had a 10 year head start and more resources than the Bluetooth alliance ever had, or will have. If one thinks a stack like USB is 'easy' consider Microsoft had to redesign theirs three or four times.
3. Dedicated DSSS wireless headphone spec. Seriously this was the original design goal and was totally achievable until the committee responsible for the spec lost their minds.
Don't get me started on security. BT is probably a festering pit of remote exploits and vendor backdoors.
I don't blame the Bluetooth standard though, messy as it might be. That's clearly terrible implementation on the car manufacturer's part.