Help Help?!

[jp10003]

Can anyone tell me if there's anything wrong with the contents of this log. I'll keep it short. I'm just confused because I have no bluetooth handset, no tethering and no ISync. Sorry if this is a newbie question, but I just had my Inc replaced and I'd rather fix a potential problem than a definite one.

jp
------
[ 02-02 17:20:28.850 93:0x96e E/lights ]
write ok string=0,len=1
[ 02-02 17:20:28.859 93:0x96e E/lights ]
write ok string=0,len=1
[ 02-02 17:20:28.859 93:0x96e E/lights ]
write ok string=0 0,len=3
[ 02-02 17:20:28.869 93:0x971 D/WindowManager ]
setShowKeyguard(false)
[ 02-02 17:20:28.869 195:0xc3 E/IncallScreen ]
setPowerKeyFlag(false)...
[ 02-02 17:20:28.889 70:0x46 D/AudioPolicyManagerBase ]
startOutput() output 1, stream 0
[ 02-02 17:20:28.899 93:0x69 I/LSState ]
EventReceiver:android.intent.action.NOTIFICATION_REMOVE
[ 02-02 17:20:28.899 70:0x5b D/AudioHardwareQSD ]
Enable ALT for speaker
[ 02-02 17:20:28.899 70:0x5b D/AudioHardwareQSD ]
ALT batt temp = 298
[ 02-02 17:20:28.910 195:0xc3 I/CallCard ]
setPhotoImageDrawableuplicated drawable
[ 02-02 17:20:28.910 195:0xc3 D/BluetoothHandsfree ]
updatePhoneState()
[ 02-02 17:20:28.910 195:0xc3 E/BluetoothHandsfree ]
prevCdma state: IDLE, currCdma state: IDLE
[ 02-02 17:20:28.910 195:0xc3 E/BluetoothHandsfree ]
cdma: callheld: 0
[ 02-02 17:20:28.910 195:0xc3 D/BluetoothHandsfree ]
cdmaSetSecondCallState: Setting mCdmaIsSecondCallActive to false
[ 02-02 17:20:28.910 195:0xc3 E/IncallScreen ]
setPowerKeyFlag(false)...
[ 02-02 17:20:28.929 195:0xc3 I/CallCard ]
setPhotoImageDrawableuplicated drawable
[ 02-02 17:20:29.179 545:0x3f3 D/ContactNameCache ]
Contact onChange: false
[ 02-02 17:20:29.289 70:0x5b I/AudioHardwareQSD ]
AUDIO_START: start kernel pcm_out driver.
[ 02-02 17:20:29.289 70:0x5b W/AudioFlinger ]
write blocked for 385 msecs, 11 delayed writes, thread 0x155c0
[ 02-02 17:20:29.299 195:0x1007 D/PhoneUtils ]
setAudioMode(MODE_NORMAL)...
[ 02-02 17:20:29.309 93:0x9ec D/AudioService ]
setMode = 0
[ 02-02 17:20:29.419 195:0xc3 D/BluetoothHandsfree ]
updatePhoneState()
[ 02-02 17:20:29.419 195:0xc3 E/BluetoothHandsfree ]
prevCdma state: IDLE, currCdma state: IDLE
[ 02-02 17:20:29.419 195:0xc3 E/BluetoothHandsfree ]
cdma: callheld: 0
[ 02-02 17:20:29.419 195:0xc3 E/IncallScreen ]
setPowerKeyFlag(false)...
[ 02-02 17:20:29.429 195:0xc3 E/PhoneApp ]
mStatusBarDisableCount is already zero
[ 02-02 17:20:30.609 93:0x69 I/BluetoothA2dpService ]
RESUME_PHONE_STATE
[ 02-02 17:20:30.915 195:0xc3 D/DataConnectionTracker ]
netshare is outdated
[ 02-02 17:20:30.939 93:0x7e D/MobileDataStateTracker ]
watch=admin, mtype=admin dropped - wrong Apn
[ 02-02 17:20:30.949 93:0x7e D/MobileDataStateTracker ]
replacing old mInterfaceName (rmnet0) with rmnet0 for hipri
[ 02-02 17:20:30.949 93:0x7e D/MobileDataStateTracker ]
watch=default, mtype=hipri dropped - mEnabled = false
[ 02-02 17:20:30.969 93:0x116 D/NetworkLocationProvider ]
onDataConnectionStateChanged 2
[ 02-02 17:20:30.969 93:0x7e D/MobileDataStateTracker ]
watch=fota, mtype=fota dropped - wrong Apn
[ 02-02 17:20:30.969 93:0x7e D/MobileDataStateTracker ]
watch=httpproxy, mtype=httpproxy dropped - wrong Apn
[ 02-02 17:20:30.979 545:0x221 V/MmsSystemEventReceiver ]
Intent received: Intent { act=android.intent.action.ANY_DATA_STATE flg=0x20000000 cmp=com.android.mms/.transaction.MmsSystemEventReceiver (has extras) }
[ 02-02 17:20:30.979 93:0x7e D/MobileDataStateTracker ]
watch=wapgateway, mtype=wapgateway dropped - wrong Apn
[ 02-02 17:20:30.990 93:0x7e D/MobileDataStateTracker ]
replacing old mInterfaceName (rmnet0) with rmnet0 for supl
[ 02-02 17:20:30.990 93:0x7e D/MobileDataStateTracker ]
watch=supl, mtype=supl dropped - mEnabled = false
[ 02-02 17:20:30.990 93:0x7e D/MobileDataStateTracker ]
watch=mms, mtype=mms dropped - wrong Apn
[ 02-02 17:20:30.990 93:0x7e D/MobileDataStateTracker ]
watch=dun, mtype=dun dropped - wrong Apn
[ 02-02 17:20:30.990 93:0x7e D/MobileDataStateTracker ]
watch=default, mtype=default Received state= CONNECTED, old= SUSPENDED, reason= 2GVoiceCallEndedapn=null apnTypeList=default,supl mInterfaceName=rmnet0
[ 02-02 17:20:30.999 568:0x238 V/com.fusionone.android.sync.service.SyncService ]
onStart() invoked
[ 02-02 17:20:30.999 568:0x238 V/com.fusionone.android.sync.service.SyncService ]
handleNotification invoked: Intent { act=com.fusionone.android.sync.rpc.ISyncManager (has extras) }
[ 02-02 17:20:30.999 568:0x238 V/ba ]
aj
[ 02-02 17:20:31.009 568:0x24e V/ba ]
firing COMMUNICATING event
[ 02-02 17:20:31.009 568:0x24e E/ba ]
fResult.getData() : null
[ 02-02 17:20:31.019 568:0x24e V/ba ]
firing COMPLETED event
[ 02-02 17:20:31.019 93:0x7e E/NetworkStateTracker ]
net.tcp.buffersize.evdo not found in system properties. Using defaults
[ 02-02 17:20:31.019 93:0x7e V/NetworkStateTracker ]
Setting TCP values: [4096,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.default]
[ 02-02 17:20:31.049 545:0x228 V/MmsSystemEventReceiver ]
ANY_DATA_STATE event received: CONNECTED
[ 02-02 17:20:31.049 93:0x80 D/Tethering ]
Tethering got CONNECTIVITY_ACTION
[ 02-02 17:20:31.049 93:0x80 E/Tethering ]
>>>>>connectivity changed<<<<<
[ 02-02 17:20:31.049 93:0x80 E/Tethering ]
type: mobile, connected: true
[ 02-02 17:20:31.049 93:0x80 D/Tethering ]
MasterInitialState.processMessage what=3
[ 02-02 17:20:31.049 93:0x80 E/HierarchicalStateMachine ]
TetherMaster - unhandledMessage: msg.what=3

 

[sdrawkcab25]

What issue are you trying to troubleshoot?

 

[jp10003]

I just don't understand why/what the bluetooth activity is; The Tethering activity; and the ISync..
I'm guessing the sync is a standard system process, but flags go up when words like TETHER and BLUETOOTH come up in my log as I don't use either. Also when they pop somewhat randomly.. I'm just trying to figure out if it's out of the ordinary, or if it is something I should ignore.. I want to understand the functionality of my phone and to not worry about stupid things, or bother nice people with insignificant issues.

 

[jp10003]

So is this a normal function of a non rooted phone?

 

[sdrawkcab25]

The log does seem weird but, I'm sure there is a lot of background activity that goes on that has zero effect on anything. All of that happened in a span of 3 seconds. I wouldn't worry about it unless the phone starts acting strange.

 

[jp10003]

Well, it did, so I had it reset, then all this bluetooth OPP, and dun, bcm2549 or something was installed. It just seems odd.

 

[sdrawkcab25]

As I posted in your other thread, that is the broadcom chip in the phone.

 

[jp10003]

Thank you so much.. As long as it's not a security risk, I'm a happy man. (I just wonder why it would list attaching to things.. unless it considers the actual phone (headset) a bt connection.device