Calls switching to speakerphone

[gtmethod3]

Originally Posted by binht611

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

What does this mean??

Also any updates on this issue?

[arrrghhh]

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]

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]

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]

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?

[arrrghhh]

Originally Posted by JWise1203

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?

Basically, yes. With these types of issues it's not easy to sort out, and the only way devs are going to be able to even dream of starting to fix the issue is with logs. So a dmesg, an adb logcat and adb logcat -b radio will all probably be in order. The more logs w/issues the better, y'know?

My problem is, I haven't figured out how to recreate the issue. It only seems to happen when I _don't_ want it to happen, which I guess is Murphy's law. Like I said, sometime I probably just need to make a hundred phone calls when I have unlimited minutes at night hahaha!

[JWise1203]

Originally Posted by arrrghhh

Basically, yes. With these types of issues it's not easy to sort out, and the only way devs are going to be able to even dream of starting to fix the issue is with logs. So a dmesg, an adb logcat and adb logcat -b radio will all probably be in order. The more logs w/issues the better, y'know?

My problem is, I haven't figured out how to recreate the issue. It only seems to happen when I _don't_ want it to happen, which I guess is Murphy's law. Like I said, sometime I probably just need to make a hundred phone calls when I have unlimited minutes at night hahaha!

Great thanks.

I am not sure what's going on but I have the USB drivers installed and had my phone working in DroidExplorer a few weeks ago. Now my phone will charge but not sync with my computer. I double-checked that USB debugging is turned on.

Ah, the problems never end.

[gtmethod3]

Originally Posted by arrrghhh

Basically, yes. With these types of issues it's not easy to sort out, and the only way devs are going to be able to even dream of starting to fix the issue is with logs. So a dmesg, an adb logcat and adb logcat -b radio will all probably be in order. The more logs w/issues the better, y'know?

My problem is, I haven't figured out how to recreate the issue. It only seems to happen when I _don't_ want it to happen, which I guess is Murphy's law. Like I said, sometime I probably just need to make a hundred phone calls when I have unlimited minutes at night hahaha!

I have noticed things go a bit haywire when call waiting kicks in.