Quote:
Originally Posted by jnewkirk5
I can tell you for a fact that the right developer could solve this problem rather quickly and this is how I know. First off I got a moment after being with windows mobile phones for years. They have been doing it for years and well. I mean it worked every time. I never had a problem not once with three different phones and countless (probably 10) headsets. I could not believe when I got the moment and bluetooth support was so shoddy. I mean bluetooth has been out for ever and the phone couldnt even transfer files. Secondly, on more than one occasion my moment has messed up and stuck after a call and ALL of the system audio WAS routed through my mono bluetooth headset (Moto H710). It has actually worked, just did not stay that way, so it is strictly a programming issue. I have now purchased a Jabbra headset that supports A2DP and it will work but still plays audio through the speaker as well. Why is this so hard? Because it's not important to Google. I have created instances in Google codesite here: Issue 7906 - android - Audio routing to mono bluetooth headsets - Project Hosting on Google Code and still no love. It's stupid! |
It is more of a programming issue but if you know for a 'fact' then program it yourself or go back to winmo. BT sucks in general but the worse part is that it is a proprietary licensed protocol. This means that unless you pay the fee you can't use it unless you reverse engineer it which is what linux has had to do for years. Android is open source so they can't pay the license and then include the code for all to see and use. Winmo doesn't give you the source code for anything so they can use the code since you won't see it.
All those winmo toys paid the bt tax so that is why they work, nothing to do about caring.