Thanks! That was informative on several key points:
- That you talked to a “Lab tech” is great news, in that even if he was just tech support, he sounds as if he gets to at least influence, or talk to the engineers. I know that in my company, we “forced” engineers to do first line tech support for at least an hour a day. That led to customers driving engineering that no manager could ever match. They could see first hand, the implications of their decisions, and that drove engineering much better products.
- I’m not at all sure I buy that BT is different on PCs, vs phones. Generally, a spec like BT is a spec, regardless of which OS or device it is on. We pioneered SCSI devices for all OS’s, all SCSI devices, and all hardware hosting. So, I have a bit of experience with device drivers, OEMs and software distribution. They could have “done it wrong”, but I doubt it. To maintain as much compatibility as possible, they should have only supported what they had to. Once you try to do exotic functions that only exist in x hardware, or x OS, then you not only limit your market, but you generally will break and make fragile what you do “support” i.e., it becomes unreliable.
- Again, if someone talks to support or engineering:
----- >> Please lobby for more than TWO BT pairings that can be saved.
That alone would clear up most of our problems. The alternative of requiring a dongle is not good. They then cannot “talk to the HA” from any app or application. Think of “programming” your HA — think you are going to do that through an ANALOG audio port?? I don’t think that’s possible. (Or, it hasn’t been since TRS-80 Radio shack days when you stored programs on audio cassette tapes!!) - Eventually, they, or someone else, will open up an API that we can control our HA with our devices. That can’t happen unless and until we can always have a DIGITAL wireless connection from our PCs and phones.