Originally Posted by CodaHighland

Whatever happened to needing 10 posts to even post in this section?

He joined before that requirement was laid down. Users who joined before that date are grandfathered.

Since the Bing app no longer does navigation, I've decided to try and use my phone solely as Android so I can use Google Navigation. Everything seems to be working fine, except I am getting issues with the phone not ringing when people call me.

Data switches from 3G to 1X when the phone should be ringing.

I have found that if I first call out, then my phone is much more likely to ring when someone calls me.

I am using the Sprint CDMA version.

I searched the thread, and there was mention that this was caused by a bug in RIL, and there was a fix to get the phone to mount an older version of RIL.

But I didn't see any follow up. Is that still the only fix, or is there a newer kernel somewhere they I should install that solves this? I used the "full bundle" download dated Sept 1 for my install.

AFAIK problems with incoming calls tends to just be your phone being busy. Try running fewer background apps.

Originally Posted by CodaHighland

AFAIK problems with incoming calls tends to just be your phone being busy. Try running fewer background apps.

I have none running besides the default. At its pretty flawless, you can watch the phone switch from 3G to 1X, which shows the phone is noticing the call, but it never rings. Make an outbound call, and then inbound calls ring like normal. The phone is not laggy or non-responsive when it is failing to ring.

Earlier in the thread (from Sep 21st) there were several people with this problem, and the work around mentioned above was used to solve the problem.

I'm just looking to see if this is solved in one of the newer kernels or if there's a better solution.

Ok, after upgrading the kernel and it not solving things, I dug back through the thread and found the solution here:
http://forum.xda-developers.com/show...postcount=1269

Now that I've set my WinMo side to airplane mode, it seems to have solved the issue, and it explains why it would start working after I would make an outbound call.

Originally Posted by shawndoc

Ok, after upgrading the kernel and it not solving things, I dug back through the thread and found the solution here:
http://forum.xda-developers.com/show...postcount=1269

Now that I've set my WinMo side to airplane mode, it seems to have solved the issue, and it explains why it would start working after I would make an outbound call.

I was going to suggest this . Always, always, always boot Android with WinMo in Airplane Mode!

I... have never had problems with that and my WinMo isn't in airplane mode. >.> Am I just getting lucky? Or is this something fixed in GBX?

Originally Posted by CodaHighland

I... have never had problems with that and my WinMo isn't in airplane mode. >.> Am I just getting lucky? Or is this something fixed in GBX?

Depends on the radio firmware it seems. Never a bad idea to boot with WinMo in Airplane Mode - that ensures that the radio is completely shut down before booting Android.

Hey Arrrghhh, is there a major reason to upgrade my rootfs or initrd beyond what is in the 7.1 complete package?

Originally Posted by shawndoc

Hey Arrrghhh, is there a major reason to upgrade my rootfs or initrd beyond what is in the 7.1 complete package?

Not that I can think of. If you're playing with newer kernels, there's a slight reason to upgrade the rootfs. Hasn't been an initrd update in ages .