i ordered the comboard from ifixit.com

Regards,

Martijn

I've just checked and double checked the baseband logs and it MOST DEFINITELY ISN'T a hardware issue. At least in my case. The reason swapping a comm board helps is because you're swapping the NOR chip along with it and i suspect it's a software issue in the NOR...

Here's a dump from my baseband logs. First, with external power plugged in, the phone waking from sleep to ring normally:

27989 recv[low]: OK
27989 send[low]: at+xdrv=0,20,0
27996 recv[low]: +XDRV: 0,20,0,0
27998 recv[low]: OK
64998 recv[call]: RING
65000 recv[reg]: RING
65002 recv[sms]: RING
65003 recv[low]: RING
65005 recv[pdp_ctl]: RING
65007 recv[pdp_0]: RING
65009 recv[pdp_1]: RING
65013 recv[call]: +CLIP.........................
65013 evt: Sending internal notification kEventCallActive (0) params............
65013 evt: Sending event kCallStateChangeNotification (1)
65013 clm: Current caller id info ...............
65013 evt: Sending event kIncomingCallerIdNotification (9)
65027 recv[call]: +XCALLSTAT: 1,4


Then on battery, the phone NOT waking from sleep on an incoming call:

115459 mux: Enter low power mode.
115459 mux: Control channel sending PSC command (0 bytes).
115464 mux: Control channel received PSC response (0 bytes).
115515 reg: .................................................. .....
115691 rm: exit low power
115691 mux: Exit low power mode.
115691 evt: Sending internal notification kEventExitingLowPower (15) params............
160691 reg: .................................................. ....
160691 reg: elapsedSecs = 45, elapsedAbsSecs = 0, gLowPowerTotalElapsedSecs = 45
160913 recv[call]: RING
160913 recv[reg]: RING
160913 recv[sms]: RING
160913 recv[low]: RING
160913 recv[pdp_ctl]: RING
160913 recv[pdp_0]: RING
160913 recv[pdp_1]: RING
160913 recv[call]: +CLIP.........................
160913 evt: Sending internal notification kEventCallActive (0) params............
160914 evt: Sending event kCallStateChangeNotification (1)
160914 clm: Current caller id info ...............
160914 evt: Sending event kIncomingCallerIdNotification (9)
160914 recv[call]: +XCALLSTAT: 1,4

See? As far as the baseband's concerned, everything went out perfectly as planned:

1. it went to sleep (low power state)
2. an incoming call triggered wake up (exiting low power state)
3. then it sent RING response, got the caller ID and issued a system notification w/ caller ID

Just BTW, note it never goes to low power state when on external power!

Someone over at the iPhone Elite forum posted a potential fix for this. I haven't followed all the posts in this thread and I apologise if the suggested fix has already been attempted.

Turn on Airplane mode. Reboot. Turn off Airplane mode. Reboot.

See if that fixes your no-ring-while-sleeping problem?

Thanks!

Airplane mode switching not work for me

Originally Posted by Kohila

Airplane mode switching not work for me

Sorry to hear that.

I guess it's not the same for everyone.

Originally Posted by orcinus

I've just checked and double checked the baseband logs and it MOST DEFINITELY ISN'T a hardware issue.

How can I see the baseband logs (and other logs)? Thanks!

@Mauler:

Nope, that unfortunatel doesn't work for me either.

@dond:

1. Start Phone, tap on Keypad
2. Enter *#5005*78283#, tap Call, tap Reply, type in something ("Dump" will suffice)
3. Check /Library/Logs/Baseband/ or /Library/Logs/CrashReporter/Baseband

In other news, i've found another way of avoiding (not solving) the problem. It essentially does the same thing as leaving an MP3 file to play silently in the background, but without the added hassle of doing it every time the iPhone restarts and, well, having an MP3 file playing in the background

Here goes:

1. Access the iPhone's file system by a method of your choice (iPhoneList or other manzana.dll app, iPHUC, SCP)
2. Go to /System/Library/SystemConfiguration/PowerManagement.bundle/
3. Back up com.apple.SystemPowerProfileDefaults.plist somewhere safe
4. Delete or rename com.apple.SystemPowerProfileDefaults.plist
5. Reboot

You can check if it worked by going to Settings > Usage and checking the Usage and Standby values. If they stay the same no matter what you do, that's it

Same caveat applies as with the MP3 non-solution - your iPhone won't be able to go into sleep and, thus, the battery life will shorten greatly. The battery will die in <24 hours with the phone just sitting there.

here's my crash log: (can be found at /Library/Logs/CrashReporter/Baseband/)

752548 mux: Enter low power mode.
752548 mux: Control channel sending PSC command (0 bytes).
752552 mux: Control channel received PSC response (0 bytes).
752602 reg: .................................................. ......
752841 ipc: *** Baseband crash detected! ***
752841 rm: reset called with reason modem reset
752855 rm: Reset: modem reset
752923 rm: ENTER: resetCommon
752988 rm: start reset dispatcher state
752988 rm: end reset dispatcher state
752989 evt: Sending internal notification kEventRadioOff (6) params............
752989 clm: Clearing DTMF queue
752989 evt: Sending event kOperatorNameNotification (14)
752989 evt: Sending event kServiceProviderNameNotification (13)
752990 evt: Sending event kRegistrationStatusNotification (11)
752990 evt: Sending event kDataAttachStatusNotification (110)
752990 evt: Sending event kRegistrationStatusNotification (11)
752990 evt: Sending internal notification kEventNotRegistered (3) params............
752990 evt: Sending event kSimToolkitMenuNotification (97)
752990 evt: Sending event kSimToolkitSetUpIdleModeTextNotification (105)
752991 evt: Sending event kSimStatusChanged (138)
752991 rm: start reset dispatcher state
752991 rm: end reset dispatcher state
752999 ipc: read() failed: Resource busy (16)
753006 rm: exit low power
753006 evt: Sending event kRadioNotReadyError (75)
753079 stk: sessionResponse_nl: Out of turn response: 4,-1
755268 ipc: ThreadedIpcDriver::dumpState() : buffer (0 bytes):
755269 rm: fWriteDataAvailable=false, fBufferSize=2048, fReadFlush=false
755269 rm: fSupportsH5TransportMode=true, fInH5TransportMode=true
755269 ipc: closed reader fd, reopening...
755269 evt: Sending event kRadioResetNotification (84)
755269 rm: sendPing
755270 rm: EXIT: resetCommon
755270 send[default]: at

Was that crash triggered by an incoming call while the baseband was in the low power state, or...?