Iphone 3G Baseband Logs

Question

Level 1

0 points

Iphone 3G Baseband Logs

Hi,
I've noticed that when connecting my Iphone 3G to Itunes
that Itunes asks to send diagnostic information to apple.
I've always deselected the checkbox that says to not as again and I've been keeping a backup of every log.
I've been getting baseband errors every day like this:

Date=2008-07-20;AP=5A345;BB=01.45.00;Model=N82AP;Machine=iPhone1,2
0:11:10 [clm] disconnect: duration=0;cause=kNoError;ceer=31;txPower=-199;maxTxPower=32;rat=1;cgi=268:3:60 01:8012
0:11:52 [clm] disconnect: duration=0;cause=kNoError;ceer=31;txPower=-199;maxTxPower=32;rat=1;cgi=268:3:60 01:8012
0:12:33 [clm] disconnect: duration=0;cause=kNoError;ceer=31;txPower=-199;maxTxPower=32;rat=1;cgi=268:3:60 01:8012
0:13:17 [clm] disconnect: duration=0;cause=kNoError;ceer=31;txPower=-199;maxTxPower=32;rat=1;cgi=268:3:60 01:8012
13:20:13 [clm] disconnect: duration=0;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=1;cgi=268:3:600 1:8413

The logs usually are at:
(Vista)
C:\Users\<user>\AppData\Local\Apple Computer\SyncNotifier\SyncNotifier\Logs

or

C:\Users\<user>\AppData\Roaming\Apple Computer\SyncNotifier\SyncNotifier\Logs

or XP:

C:\Documents and Settings\<user>\Application Data\Local\Apple Computer\SyncNotifier\SyncNotifier\Logs

Does anyone have the same?

The logs are named: log-bb-<date>-stats.txt.submitted i.e log-bb-2008-07-19-stats.txt.submitted

PC, AMD64 3200+

Posted on Jul 26, 2008 3:10 PM

Reply

Answer 1

sjds Author

Level 1

0 points

Jul 26, 2008 4:00 PM in response to sjds

Sorry the logs location should be:

Vista
C:\Users\<user>\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice

XP
C:\Documents and Settings\<user>\Application Data\<Local or Roaming>\Logs\CrashReporter\MobileDevice

Reply

Answer 2

sjbale

Level 1

0 points

Jul 31, 2008 8:33 AM in response to sjds

I get these as well, does any one else? Do these indicate a faulty baseband?

Reply

Answer 3

sjds Author

Level 1

0 points

Jul 31, 2008 8:36 AM in response to sjbale

I think that the problem might be the sim card. Mine stopped complaining with another sim.

Reply

Answer 4

sjbale

Level 1

0 points

Jul 31, 2008 8:40 AM in response to sjds

This is possibly slightly off topic but I'd be interested to know if you've had any crashes of mediaserverd, these seem quite frequent as well.

Best Regards, Simon.

Reply

Answer 5

sjds Author

Level 1

0 points

Jul 31, 2008 8:42 AM in response to sjbale

Just one-two over a 2 week period.

Reply

Answer 6

sjds Author

Level 1

0 points

Jul 31, 2008 8:43 AM in response to sjds

You should also post an excerpt of your baseband logs to see if they are the same.

Message was edited by: sjds

Reply

Answer 7

sjbale

Level 1

0 points

Jul 31, 2008 8:49 AM in response to sjds

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>SysInfoCrashReporterKey</key>
<string>c983903040244989039dfd338563be48753789690</string>
<key>SysInfoMachineConfigKey</key>
<string>iPhone1,2</string>
<key>SysInfoOSVersionKey</key>
<string>2.0:5A347</string>
<key>SysInfoSystemProfileKey</key>
<string></string>
<key>bug_type</key>
<string>195</string>
<key>description</key>
<string>Date=2008-07-30;AP=5A347;BB=01.45.00;Model=N82AP;Machine=iPhone1,2
18:59:04 [clm] disconnect: duration=21;cause=kNoError;ceer=0;txPower=-9;maxTxPower=32;rat=3;cgi=224:60:641 40:38727
20:48:04 [clm] disconnect: duration=224;cause=kNoError;ceer=0;txPower=-7;maxTxPower=32;rat=3;cgi=224:60:64 140:38727
</string>
<key>host osversion</key>
<string>OS:Windows;OSBuild:2600;OSMajorVersion:5;OSMinorVersion:1;</string>
<key>system_ID</key>
<string></string>
</dict>
</plist>

Reply

Answer 8

sjds Author

Level 1

0 points

Jul 31, 2008 8:52 AM in response to sjbale

Its the same that I was having. Try another sim card.

Reply

Answer 9

sjbale

Level 1

0 points

Jul 31, 2008 9:10 AM in response to sjds

Just ordered one, thanks for the help. I'll reply to this thread if it works.

Reply

Answer 10

Aug 6, 2008 8:40 AM in response to sjbale

Did your new SIMCARD finally solve your problem ?

Reply

Answer 11

sjds Author

Level 1

0 points

Aug 6, 2008 1:54 PM in response to Nicolas Dorfsman

I've discovered that its not sim card neither phone related (I've changed both).
I've cross checked the log's timestamp with my call log and it matches perfectly. It seams apple is collecting stats on every call.
The reason why you don't see others reporting the same is that the dialog that asks you to send the log as a checkbox ticked by default not to ask again so it takes only one dismissal without unticking the box to it never ask again.

Reply

Answer 12

Sep 11, 2008 2:37 PM in response to sjds

I have about a hundred crash reports from various things. They are normal and several are used just for information purposes. ie: Apple keeps track of when your battery gets so low the phone must shutdown. They want to make sure the batteries are good enough or holding up I suppose.
baseband crashes have happened occasionally even in the original iPhone. There was a weird lockup with 1.0-1.0.3 that caused the transmitter to lock-up entirely and be unable to receive or place calls if the call was dropped by stepping into an elevator or tunnel. The things you guys are seeing is likely a result of the 3G glitches with the transmitter power negotiation algorithm. There has been some talk that iPhone requests a lot of power for from the transmitter causing AT&T transmitters to exceed their limits when there are a large number of iPhones around. 2.0.2 was supposed to address this issue, but seems to have issues with dropped calls, likely as a result of going too far the other way. Hopefully tomorrow 2.1 will solve our problems as Steve has promised!

There also should be an important distinction as far as a baseband crash, and baseband statistics being collected to improve call and data handling.
Here is a crash. The log file is dozens of pages long but here is the last bit:
70611203 reg: fOperatorListFetched=0 fCurrentOperation=1 fSelectionMode=0 fBrickMode=0
70611232 reg: fManuallySelectedNetwork="" fDataAttached=1 fActingHplmn=310380 fServingPlmn=310410
70611232 reg: fLastKnownServingPlmn=310410 fHomePlmn=310410 fRequestedAlphaTag=-1, fFinalAlphaTag=9
70611232 reg: fAirplaneMode=0 fRadioOn=1
70611232 reg: fEnableAutomaticTimeUpdate=true fLastTimeUpdateValid=true fLastTimeUpdateTimestamp=66273
70611232 reg: fLastTimeUpdateTime=00:18:47 07/10/2008 -420 DST
70611233 sim: fSimInserted=true fNewSim=false fSimStatus=8
70611233 sim: fNetworkPersonalizationUnlockable=true fInitializing=false fImsi=31041...........fIccid=8901410.............
70611233 sim: fRemainingPinAttempts=3 fRemainingPukAttempts=10 fActivePin....................
70611233 sim: fSimRetryCounter=0 fSuppressPinRequest=false fNetworkSelectionMenuEnabled=false
70611233 rm: fPingCount=0 fPowerUpCount=0 fWantCrashLog=0 fRadioInitialized=1
70611233 rm: ...................................
70611233 rm: fInLowPowerMode=0 fInAirplaneMode=0
70611233 mux: fPowerState=0
70611233 mux: DLCI 0 fStatus=0 fLocalModemBits=0 fRemoteModemBits=4
70611233 mux: DLCI 1 fStatus=0 fLocalModemBits=6 fRemoteModemBits=4
70611233 mux: DLCI 2 fStatus=0 fLocalModemBits=6 fRemoteModemBits=4
70611233 mux: DLCI 3 fStatus=0 fLocalModemBits=6 fRemoteModemBits=4
70611233 mux: DLCI 4 fStatus=0 fLocalModemBits=6 fRemoteModemBits=4
70611233 mux: DLCI 5 fStatus=0 fLocalModemBits=6 fRemoteModemBits=4
70611233 mux: DLCI 6 fStatus=0 fLocalModemBits=6 fRemoteModemBits=4
70611233 mux: DLCI 7 fStatus=0 fLocalModemBits=6 fRemoteModemBits=6
70611233 mux: DLCI 8 fStatus=0 fLocalModemBits=6 fRemoteModemBits=6
70611314 rm: writing logs to: /Library/Logs/Baseband/log-2008-07-09-18-31-07.txt

User-requested log explanation: kTemporaryFailure

----
Here is the statistics:
Date=2008-09-10;AP=5C1;BB=02.08.01;Model=N82AP;Machine=iPhone1,2
9:57:27 [clm] disconnect: duration=319;cause=kNoError;ceer=16;txPower=-199;maxTxPower=32;rat=2;cgi=310:41 0:31005:20805
10:47:18 [clm] disconnect: duration=235;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410 :31005:235
11:09:01 [clm] disconnect: duration=292;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410 :31005:235
11:32:42 [clm] disconnect: duration=226;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410 :31005:235
12:32:25 [clm] disconnect: duration=3185;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:41 0:31005:20805
15:33:22 [clm] disconnect: duration=32;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410: 31005:4916
22:01:04 [clm] disconnect: duration=0;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410:3 1005:4055
22:02:01 [clm] disconnect: duration=20;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410: 31005:4055
22:02:01 [clm] disconnect: duration=20;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410: 31005:4055
22:08:28 [clm] disconnect: duration=2;cause=kNoError;ceer=0;txPower=-199;maxTxPower=32;rat=2;cgi=310:410:3 1005:4055
23:49:59 [clm] disconnect: duration=1052;cause=kNoError;ceer=16;txPower=-8;maxTxPower=32;rat=3;cgi=310:410 :31999:237

These are simply keeping track of your dropped calls, where you got "No Service" etc. Maybe someone might use these to improve the network!

Reply