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...