Open GoogleCodeExporter opened 8 years ago
I think you are right, I haven't actually tried this. I only cared about
getting the headphones to work and not the wired headset. That means this
application is essentially mis named which is unfortunate.
It's probably possible to switch the input audio routing as well but I'll need
to investigate. I will try to get to this in the next week.
Original comment by danwal...@gmail.com
on 5 Jun 2011 at 3:13
Thank you for responding! The only reason I bought the HTC adapter was to use
my headset for driving. After I downloaded the app and failed to get it to work
with my headset, I went out and bought other headsets thinking the issue was
with my headset. After all that, I would've saved money just buying a
bluetooth headset. Haha :-/
Original comment by yvette.l...@gmail.com
on 10 Jun 2011 at 10:43
I've investigated a bit this morning. Unfortunately I don't see a way to do
this easily. The output routing is the same between a headset or headphones.
I don't see a way to change the input routing on 1.6. I'm using setRouting()
in AudioManager with ROUTE_HEADSET - see
http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=media/jav
a/android/media/AudioSystem.java;hb=843ef36f7b96cc19ea7d2996b7c8661b41ec3452
I would expect if anything would alter input routing this would. It may be
possible to experiment with other values to setRouting, however I don't have my
1.6 platform right now.
I think you should return your headset and get a bluetooth headset... that way
it will be more likely to work with your next phone too :)
Sorry for the confusion, I will update the comments in the application to note
this.
Original comment by danwal...@gmail.com
on 11 Jun 2011 at 5:24
Original issue reported on code.google.com by
yvette.l...@gmail.com
on 5 Jun 2011 at 12:25