Closed GoogleCodeExporter closed 8 years ago
Hmmm not sure how this could happen. Do I understand that you have rebooted
without
the headset connected and still see this issue? If you didn't connect a
headset and
didn't tap the icon the widget should not have ever been executed by the OS so
it's
hard to imagine how it could be involved.
Have you tried to turn the speakerphone on and off during the call through the
dialer
ap? Does this do anything?
Original comment by danwal...@gmail.com
on 13 Nov 2009 at 4:20
I tried turning on anf off speakerphone, but it remains the same. I am thinking
in doing a hard reset, to se if it
fixes the problem, But I am first backing everything up... with the hope there
is a way of solving it in the
meantime!
Thanks
Guido
Original comment by ggavila...@gmail.com
on 14 Nov 2009 at 9:25
I mean, it turns on and off speakerphone, but it does not turn back to phone
normal speaker...
Original comment by ggavila...@gmail.com
on 14 Nov 2009 at 9:26
I assume you've removed the widget completely by now as well?
If you have the SDK installed you can use logcat (see
http://developer.android.com/guide/developing/tools/adb.html) to capture
logging when
switching between speaker and headset. This would let you verify hardware is
actually toggling the output and indicate there is probably some type of
hardware
problem happening
The logs from the android OS I see with my G1 when switching from dialer
speakerphone
to headset are:
11-14 10:16:44.549 I/AudioHardwareMSM72XX( 51): Routing audio to Handset
11-14 10:16:44.549 D/HTC Acoustic( 51): msm72xx_enable_audpp: 0x0000
11-14 10:16:44.559 D/AudioHardwareMSM72XX( 51): setVoiceVolume(1.000000)
Hope this helps, good luck.
Original comment by danwal...@gmail.com
on 14 Nov 2009 at 5:18
I don't believe this could be related to the application, therefore I'm moving
to
invalid status.
Original comment by danwal...@gmail.com
on 3 Jan 2010 at 3:27
Original issue reported on code.google.com by
ggavila...@gmail.com
on 13 Nov 2009 at 1:24