AVRCP is quite eloquent. I get the feeling that whoever designed it is upset that it never got properly implemented or used. BTLE in its entirety is just simpl

AVRCP is quite eloquent. I get the feeling that whoever designed it is upset that it never got properly implemented or used. BTLE in its entirety is just simple. It is possible to read over the BTLE spec in a couple hours and understand it. (AVRCP can be read in half an hour tops, 15 minutes if you skim the same-y diagrams) BT SPP is, well, a glorified serial port, with all the advantages and disadvantages that entails. If you want a glorified pipe, BT SPP is where you go. You can actually use BT LE to do the same thing, at a much slower transfer rate. > wifi and ethernet and usb drivers tend to work reasonably well WiFi and USB drivers are also flaming piles of trash. Since 90% of USB use cases consist of either USB-HID or Mass Storage, there is less to get wrong. Do anything beyond that and you can easily find yourself SOL. And Wi-Fi drivers are complete crap. Power management sucks, Wi-Fi chips hard lock and somehow a watch dog timer never kicks in (how?), and they rarely give the speeds that they are supposed to. Intel had some Wi-Fi chip a few years back that, for a good 2 years after its release, it would randomly stop deciding to finding networks to connect to, until it was power cycled. After a couple of years on the market they finally released a firmware update. Don't get me wrong, Chipset BT Firmware is horrible. I've worked with vendors who obviously weren't using version control, subsequent patches would have regressions that made it apparent they had built today's patch off of old source code that predated the last patch they had sent us. Hilarity like that. But the OS side BT stacks also tend to suck. Then there is the driver for the BT chip, which can also suck. The actual BT standard itself, I would argue, isn't the largest part of what is wrong.