Call Issues...

**arrrghhh** · #1 (**permalink**) 12-16-2010, 09:49 PM

So I'm on Sprint. I've had some issues with calls, sometimes the radio goes into airplane mode and the call just drops. I've had a few entertaining ones where Android resets itself, and the speakerphone flips on. The call will continue for a little while during the reboot, then disconnect.

I can't remember any other unique situations, but I have had both of these things happen when receiving a call. I can't remember of it ever occurring when I initiated the call, but I avoid calls like the plague in Android because of this issue.

Now you may be wondering - why the heck did this guy create a thread about this issue? It's been reported before, who cares? Well, I just always blamed it on the RIL for CDMA being scant... however, in another thread (that went WAY OT with this topic) a Sprint user said they did not experience any issues with calls...

Anyhoo, that user and I are trying to track down why this is occurring. I'll document some of the things we have investigated, and hopefully ruled out.

Radio firmware version (both on the same radio, 2.32.00WF)
WinMo ROM (he uses Sharkie, his associate uses stock... I'm on Energy. It's also been proven fairly consistently that WinMo ROM has no real effect on Android.)
Phone hardware (both RHOD400's)
Cell network tech (CDMA and Sprint)

So now we're comparing what build he's running and what I run.

I usually stick to vanilla system images, and what is on the autobuild if I'm doing baseline testing. Obviously I do a lot of test work as well with different developers, but that's kinda outside the scope of this discussion - as I typically don't run test stuff for several days, and since I try to avoid calls in general, it makes it rather difficult to run it at any great length of time

He PM'd me what was unique to what he was using, which I need to figure out where his system image came from. It appears to be FRX03, but the build number says "eng.neopeek.20101104.165551 test-keys"... Not a signed FRX03 image from stine's repo (files.xdandroid.com)

So he gave me a bunch of files, I'm using all of them just to be sure. I think the system image is the most interesting aspect of this, because it appears to be a neopeek build of FRX03...

steveholtam · #2 (**permalink**) 12-17-2010, 12:14 AM

Let us know how things are looking.

**arrrghhh** · #3 (**permalink**) 12-17-2010, 01:30 AM

Just happened. I was going thru the logcat... and this system image has JIT enabled. So that's what caused the reboot. I'm going to double-check my damned system image from my supposed clean folder here. I'm wondering if that build.prop that I'm mounting is enabling jit and superseding the system image...

Either way steveholtam, you do not have a clean FRX03 image... Where did you get it? It has neopeek in the name...

Update - just confirmed, that would make sense as well - the mounted build.prop file with jit enabled would take precedence over the system image file. So if I go back to a clean FRX03 system image the issue with reboots and speakerphone turning on etc should go away, but I still have the problem of the radio flaking and deciding to drop in the middle of a call - and I don't mean from a dead cell spot, I mean the radio has an x on it next to the signal bars. Then it'll go back to full service...

docnas · #4 (**permalink**) 12-17-2010, 01:36 AM

But the question is does it work for u? ie phone call issues?

**arrrghhh** · #5 (**permalink**) 12-17-2010, 01:49 AM

Quote:

Originally Posted by docnas

But the question is does it work for u? ie phone call issues?

Ok, these build.prop's floating around are bad news. They re-enable JIT, when JIT should be disabled. That was one of the stables of FRX03 believe it or not...

At any rate, if I go back to a system image/build.prop with JIT disabled, I won't experience the speakerphone turn on and reboot to the XDAndroid animation.

The radio disabling itself.... that's something completely different.

manekineko · #6 (**permalink**) 12-17-2010, 02:22 AM

Radio firmware version: I'll check if you think it'd be useful
WinMo ROM: Plutonium
Phone hardware: Rhod400
Cell network tech: Sprint CDMA

I have been running Android fulltime for months now, have never had an encounter with the infamous flip to speaker phone and reboot glitch.

The call/radio related bugs I have seen are:
-The calibration on the microphone in Android seems to be very different from optimal settings in Windows Mobile. If I do not hold the phone right next to my mouth while I talk on a call (which is kinda hard given the shape of the TP2 and the natural desire to keep it right next to my ear as well), people consistently report that my voice is really, really quiet and they can barely hear me.
-I will occasionally lose data connection even though it shows as connected (maybe once every few days) at which point I'll need to reboot to fix it. Not 100% sure whether voice continues to work after this.

steveholtam · #7 (**permalink**) 12-17-2010, 01:13 PM

Quote:

Originally Posted by manekineko

-I will occasionally lose data connection even though it shows as connected (maybe once every few days) at which point I'll need to reboot to fix it. Not 100% sure whether voice continues to work after this.

I have this problem every couple of days as well. It shows 3g, but no data transfers. Rebooting is the only way I have found to fix also. And I do think phone calls work after the data breaks. For me, I can have all sorts of issues going on, but the phone part always seems to work during crashes and such.

Also, I don't have your mic issues, or at least nobody has told me I sound quite or far away.

Arrgh, my phone portion worked before the build.props came out and after. The latest build.prop, which I am not using, caused games to not load, but the phone still worked. Not sure if that helps you or not.

**fishingmedic** · #8 (**permalink**) 12-17-2010, 05:28 PM

Quote:

Originally Posted by steveholtam

Arrgh, my phone portion worked before the build.props came out and after. The latest build.prop, which I am not using, caused games to not load, but the phone still worked. Not sure if that helps you or not.

I told him the same thing, I use my phone constantly on android and never had an issue, using the 12/2 build.prop, etc, and lo and behold, it freaking happened about an hour ago... speaker suddenly turned on, abdroid rebooted, could still hear the other person but they couldn't hear me. I just removed the build.prop from the root of the sd, I'll have to wait and see if it happens again, but I haven't had a call issue in months prior to this.

**arrrghhh** · #9 (**permalink**) 12-19-2010, 01:21 AM

Quote:

Originally Posted by fishingmedic

I told him the same thing, I use my phone constantly on android and never had an issue, using the 12/2 build.prop, etc, and lo and behold, it freaking happened about an hour ago... speaker suddenly turned on, abdroid rebooted, could still hear the other person but they couldn't hear me. I just removed the build.prop from the root of the sd, I'll have to wait and see if it happens again, but I haven't had a call issue in months prior to this.

Ha, that's awesome. I was able to recreate this bug consistently by basically abusing the volume control during a call. With JIT disabled, didn't matter how much I abused the volume control, I couldn't get the bug to rear its ugly head.

Either way, I try to test as thoroughly as I possibly can... for a reason, I want to know what works, what doesn't....

The 3g data failure I've usually be able to resolve by airplane mode on/off cycle. I've had it plague the phone repeatedly in a short time span tho.... which is odd. Other times I won't see it for quite some time - although I haven't tried to get logcats or really anything from when these issues occur. Only way we're going to fix the issue!

manekineko · #10 (**permalink**) 12-19-2010, 03:50 AM

Quote:

Originally Posted by arrrghhh

The 3g data failure I've usually be able to resolve by airplane mode on/off cycle. I've had it plague the phone repeatedly in a short time span tho.... which is odd. Other times I won't see it for quite some time - although I haven't tried to get logcats or really anything from when these issues occur. Only way we're going to fix the issue!

Interestingly enough, I just encountered this error while on wifi, which I've never observed before. Wifi was connected, but unable to access data. Cycled airplane mode and everything went back to normal. Wonder if it could be something higher level than the 3G data connection that's having issues.