Closed GoogleCodeExporter closed 9 years ago
First, sorry for the delayed response. I was out of town since Sunday.
The main reason I gave the 3 stream options is because of the issues with
Android using those during a Bluetooth connection. It seems that every phone
and every Bluetooth device is different. I was able to make it all work well
on Droid 1, 2, and 3 with Motorola T605 and HF850 car kits. I don't have the
other equipment to develop on to ensure it would work with them. One of the
other developers on this project can't get the voice call stream to work on his
devices either. Is the Bluetooth a factory Seat feature or aftermarket? It
seems the factory Bluetooth car systems are way behind the aftermarket. Most
are just now starting to support A2DP. Many don't support voice features from
the phone but rather implement their own (for big money). I don't understand
why the auto companies are so behind on this.
I guess I could make a whole bunch of configurable options for Bluetooth so the
user can try them all in hopes of getting one to actually work. I am partially
there with the 3 streams and the delay. If I had the devices to develop on, I
would set these by device. The problem is that is really depends on the phone
and Bluetooth device pair. I could end up with a massive database of supported
devices.
The Droid 2 I develop with has 2.3.3 and it works fine on all 3 streams. Each
phone maker implements their own UI changes and many of those impact hands-free
operation and other things. Then there is also the hardware differences and
implementations.
I will say that Android has come a very long way since I bought my Droid 1 with
Android 2.0, 2 years ago. Back then, hands free only worked to receive calls,
sometimes. It would go into a connect/disconnect gyration of the HF850 so it
was not usable at all. Even on the T605 it would not accept any voice
commands. That has since all been fixed. Now all my devices are working well.
Android 4.0 is right around the corner and it promises more big improvements.
Android started out rather crude but it improving rapidly.
Original comment by JimR...@gmail.com
on 30 Sep 2011 at 1:00
This is often a compatibility issue with the devices used. It is not fixable
in the application. Hoping for changes in Android 4.0 that may help.
Original comment by JimR...@gmail.com
on 30 Oct 2011 at 7:59
[deleted comment]
Original comment by JimR...@gmail.com
on 4 Aug 2012 at 1:42
Original issue reported on code.google.com by
eleanor....@gmail.com
on 26 Sep 2011 at 3:15