Calls switching to speakerphone

JWise1203 · #1 (**permalink**) 11-07-2010, 12:43 PM

I am having a problem when making calls where the audio switches from the headset to the speakerphone (I am not changing it). I would prefer that everyone around me not hear my conversations

. Has anyone else run into this? I also hear some static over the speakerphone as well. I know static has been an issue in the past, what's going on here? This has happened in the last few builds, I am running 11/1 Reference currently.

**arrrghhh** · #2 (**permalink**) 11-07-2010, 01:50 PM

Yea, the cell radio doesn't seem too stable. I always blamed it on CDMA not being optimized, but I've seen some GSM guys report radio issues as well. So there may be hope it'll get fixed eventually, but I don't know of anyone looking into it currently.

We'd probably need a logcat or something from when this happens. I've only had the speakerphone issue happen once to me, but I've had reboots and radio cycles galore with calls. I just avoid calls like the plague in Android.

kcwebmonkey · #3 (**permalink**) 11-07-2010, 02:15 PM

I've had that issue as well before... i'll be on a call and can hear it coming from the speakerphone but it's not full volume. it's always quieter and staticy. It always goes away if i turn speakerphone on and off.

**arrrghhh** · #4 (**permalink**) 11-07-2010, 05:45 PM

LOL mine wasn't so easy. As soon as the speaker phone flipped on, the Android boot animation started playing again - a reboot within Android basically. But the call was still going, on speakerphone. I just soft reset it back to winmo...

binht611 · #5 (**permalink**) 11-08-2010, 02:19 AM

that also is my probleams!
1. phone automatic turn on speaker and reset
2. after some call, my phone can't make or receive any call but 3g still working

i just install 28/9 blazn and update 03/11 kernel manually and the probleam maybe fixed! (must disable "post automatic brightness" in the xdandroid start)

gtmethod3 · #6 (**permalink**) 11-09-2010, 10:15 PM

Quote:

Originally Posted by binht611

(must disable "post automatic brightness" in the xdandroid start)

What does this mean??

Also any updates on this issue?

**arrrghhh** · #7 (**permalink**) 11-10-2010, 12:03 AM

Quote:

Originally Posted by gtmethod3

What does this mean??

Also any updates on this issue?

He's talking about the auto-backlight setting in WinMo. Shouldn't need it anymore, as there's some new code that initiates the backlight brightness in Android now. Just need to be up to date on the kernel (zImage).

No updates on the issue. Don't really have a good grasp on what's causing it, we'd probably need a logcat -b radio when the issue is happening... fun fun.

JWise1203 · #8 (**permalink**) 11-10-2010, 12:36 AM

Quote:

Originally Posted by arrrghhh

He's talking about the auto-backlight setting in WinMo. Shouldn't need it anymore, as there's some new code that initiates the backlight brightness in Android now. Just need to be up to date on the kernel (zImage).

No updates on the issue. Don't really have a good grasp on what's causing it, we'd probably need a logcat -b radio when the issue is happening... fun fun.

I was running Android yesterday I took a call and changed the in call volume. My phone then transfered the call to the speakerphone and Android proceeded to reboot. Needless to say, I disrupted a meeting that was going on, on my floor. I had to pull the battery out to get things to stop. I can't use Android full time until the radio is a more stable.

Excuse me for my ignorance, I would be happy to grab the log file, but I am not sure how to execute the logcat command when I reproduce the issue. Can you explain how to do that?

**arrrghhh** · #9 (**permalink**) 11-10-2010, 12:48 AM

Quote:

Originally Posted by JWise1203

I was running Android yesterday I took a call and changed the in call volume. My phone then transfered the call to the speakerphone and Android proceeded to reboot. Needless to say, I disrupted a meeting that was going on, on my floor. I had to pull the battery out to get things to stop. I can't use Android full time until the radio is a more stable.

Excuse me for my ignorance, I would be happy to grab the log file, but I am not sure how to execute the logcat command when I reproduce the issue. Can you explain how to do that?

Well since the phone reboots, it's a little complex. First, you must setup adb. Once that is setup, run adb logcat > output.txt - it'll run constantly, outputting to that file. Then the fun begins. You'll have to reproduce the error with this running. Devs may also need a logcat -b radio as well... I guess I should just make a bunch of phone calls to try and recreate the issue.

This project is still very much in testing - not meant for daily use around office meetings

JWise1203 · #10 (**permalink**) 11-10-2010, 12:56 AM

Quote:

Originally Posted by arrrghhh

Well since the phone reboots, it's a little complex. First, you must setup adb. Once that is setup, run adb logcat > output.txt - it'll run constantly, outputting to that file. Then the fun begins. You'll have to reproduce the error with this running. Devs may also need a logcat -b radio as well... I guess I should just make a bunch of phone calls to try and recreate the issue.

This project is still very much in testing - not meant for daily use around office meetings

Haha ... good point! I wasn't actually in a meeting. But those who were heard my speakerphone at full blast

. I assume I run the adb commands using my PC with DroidExplorer installed? If so I guess I should reproduce the issue with the phone connected to my PC?