[Q] Constant "E/TrafficStats" in logcat

---

I've looked around, but can't really find much information about this. When viewing logcat logs(via an app called aLogcat), every 5 to 10 seconds, i get the three errors listed below:

08-24 17:32:14.605 E/TrafficStats( 2906): Tx(pdpbr0) 72
08-24 17:32:14.608 E/TrafficStats( 2906): Rx(pdpbr0) 100
08-24 17:32:14.608 E/TrafficStats( 2906): dpram_stat: pending UL 0 (@4926) pending DL 0 (@5360)

For what it's worth, pid 2906 in the log above points to: com.android.phone

I am currently running on Humble 1.51, with CWM from 08-17(Orange, with restore capability). However, i've noticed this on previous versions of humble/cwm as well. I just did a factory EE4 install via Odin with .pit file, then installed an old humble (1.33) with the same results. I've tried removing the SD card completely, and it still pops up.

If I look at the network usage in Spare Parts, I see that 'Dialer' is always at the top. It sounds like it may be related, as there was a similar discussion in this thread.

Does anyone have ANY idea why the constant "E/TrafficStats" messages might be happening? If not, any idea what I can do to get more information on what is causing it?

I to noticed this and am very curious as to what it is?

I'm not sure what is causing it, unless it is some sort of hardware defect? It makes me feel better that it isn't just me though :)

Sent from my SCH-I510 using XDA Premium App

it's mainly debugging stuff from what i can tell, and it isn't breaking anything, just annoying when looking through logcats.

The thing is that not everybody gets those messages though. I've seen other charge users' logcats, and they aren't in there, at least not nearly as often. I've noticed that it does seem to be greatly diminished when the phone hasn't recently been used, but not consistently. For example, last night it ran from 11:30 to 2:30 without a single message. Then, it started occurring every 2 to 5 minutes. When the phone is being used though, it is consistently every 5 seconds.

The only way i've found to prevent it is to turn on airplane mode, then restart, as the numbers after pdpbr0 or pdpbr1 are like some sort of counter(they never go down, only up). Obviously, that isn't ideal.

If you have logcat look at the radio buffer instead, you will see messages that coincide in frequency with the trafficstats for "[GsmMultiDCT]NetPollStartTimer: posting again for netStatPollPeriod", with the same UID as the trafficstats.

imnuts, do you know of any tools/apps for me to investigate this further than just looking logs?

You could start decompiling framework .jar files and searching through the resulting smali output for TrafficStats to see what is creating the lines and potentially how to stop them.