View Single Post
  #48 (permalink)  
Old 09-20-2010, 12:53 PM
arrrghhh's Avatar
arrrghhh
Testing Extraordinaire
Offline
 
Join Date: Mar 2007
Posts: 3,604
Reputation: 7360
arrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the community
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: Next for Android on TP2

Quote:
Originally Posted by Gilliland View Post
Yes, I've heard about both of those. I put "snd.force_headset=2" into my startup file, but it didn't make the headset work (though it DID prevent the speaker from working ). As for activating the headset in WinMo, that might work, but it's hardly a fix. And once you boot into Android in that mode, then the headset is the ONLY thing that will work. So it's not much of a workaround.

Anyway, good luck. Let me know if you come up with anything.
So yes, it does break the speakerphone... and basically you have to do both. Put that snd.force statement in your startup, and boot Android with a call to VM going & a set of headphones plugged into the 3.5mm jack. I now get audio thru the headphones... and only thru the headphones.

I guess I should've seen what happened on a call, if any sound would play thru either speaker... Haha testing that now.

I'll admit, not the best solution, but a workaround is a workaround... it does come with the risk of breaking other functionality

Bah, it completely borks sound for anything but the 3.5mm headphone jack... I even get that odd staticy feedback from the speaker when stuff is playing thru the headphones...

Last edited by arrrghhh; 09-20-2010 at 01:16 PM.
Reply With Quote
This post has been thanked 3 times.