Not working with Android 2.1

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Not working with Android 2.1 (Cyanogen 5.0.7 for Magic)

What is the expected output? What do you see instead?
The widget does not respond (does nothing) when I press it.

Original issue reported on code.google.com by sdepab...@gmail.com on 1 May 2010 at 12:16

[GoogleCodeExporter]

Hi
I'm not surprised that the ap doesn't work on 2.1 since it uses deprecated 
API's to 
force headset routing.  I am surprised that you need it since I thought the bug 
was 
fixed with 2.0.  
https://review.source.android.com/#change,9780

Are you using the HTC muti adapter?  Does the audio not route to the headset 
when you 
plug in the adapter?

I don't have access to a 2.1 phone right now to test this but if you want to 
run adb 
logcat and attach the output I will take a look.

http://developer.android.com/guide/developing/tools/adb.html

Original comment by danwal...@gmail.com on 1 May 2010 at 4:58

[GoogleCodeExporter]

Hi,

The thing is that I'm not running toggleheadset2 for the intended use - a bug 
with 
the OS - but because my connector is not working properly. I suppose there's 
something wrong with it because of the heavy use, and it detects the headset or 
the 
headphones when there's NOTHING plugged in, so when I receive or put a call I 
don't 
listen anything (the phone is routing the sound to the headset). What I was 
doing up 
until know was - before upgrading to 2.1 - in the event of no sound going to 
the 
launcher and hit toggleheadset2 so the sound got routed to the speaker.

Do you know of any application doing the same as toggleheadset2 and working in 
2.1?

I attach you the logcat output.

Best regards,

Sergi

Original comment by sdepab...@gmail.com on 1 May 2010 at 12:24

Attachments:

• logcat

[GoogleCodeExporter]

I suppose that the problem is that it's using deprecated methods of the 
AudioManager 
class, isn't it?
http://developer.android.com/reference/android/media/AudioManager.html

Original comment by sdepab...@gmail.com on 1 May 2010 at 6:57

[GoogleCodeExporter]

Yes.  From the trace it looks like getRouting no longer returns actual routing 
information, and setRouting() does not actually change the routing to headset 
as it 
did in 1.6  You could try experimenting with setSpeakerphoneOn to see if 
forcing the 
speakerphone off has any impact.  I doubt it will though.

Moving to WontFix as I don't plan to incorporate this into the current ap as it 
is 
intended for 1.6 and specific problems with the HTC multi adapters.

Original comment by danwal...@gmail.com on 4 May 2010 at 3:36

• Changed state: WontFix
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Thanks to Adam King I believe this issue is solved with the most recent 
check-in.  See the version attached to 
http://code.google.com/p/toggleheadset2/issues/detail?id=8 and please update 
with test success/fail status.

Original comment by danwal...@gmail.com on 5 Apr 2011 at 4:37

[GoogleCodeExporter]

Moved to fixed status

Original comment by danwal...@gmail.com on 5 Apr 2011 at 4:38

• Changed state: Fixed