Database Info

[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.

[Q] Trying to boot without battery (reward for solution)

Ok, so I am a hardware guy not software.
I have all the hardware put together to run a I777 without a battery.
I can get the phone to boot all the way to the home screen, Then within a couple seconds I get the 0% battery warning after which the phone shuts itself back off.
After some research I found someone reference:
services/java/com/android/server/BatteryService.java in android_frameworks_base
I attempted to do a adb pull of systemui.apk
After much frustration of adb not working correctly I could open the adb shell if the phone was connected, I could type the su command and the phone displayed the confirmation that shell had been granted su, but then I could go no further adb devices showed nothing connected, 1 billion driver reinstalls, computer and phone restarts later, I finally got the phone to connect using MyPhoneExplorer program.......
So I get the sustemui.apk and attempt to use a couple different windows based decompilers (again I am hardware not software) and that is where I am currently stuck.
I have spent countless hours on this now and would much rather just offer a reward to someone to get this fixed.
So here is the offer.
$25 if you can change whatever needs to be changed so the phone will not shut off even though no battery is connected, thus the battery level will always report 0%
As noted above, I think it is just the one small piece of code needs to be changed, recompiled and put back on my phone. However, it may go deeper than that as I have found nobody that has actually done this complete, several threads here and elsewhere of people asking but they are usually only a couple posts in a thread then nothing.
I can pull and send whatever files are needed to be changed, if it becomes massively time consuming I may be willing to renegotiate payment, but I think for someone who knows what they are doing this should be fairly quick.
Hit me up with a PM and we will get some direct communication going, skype, google talk etc lets get this going.......
PS, I can pay with either paypal, or if you prefer something else like a amazon gift card, google play credit etc.

I saw on YouTube that you successfully got this to work.
What ROM and power supply did you use?

I think "ADB shell halt" bricked my tablet

I have a samsung galaxy tab 2 7inch that is rooted and running a cyanogenmod 11(i think) nightly. So here's the story:
I was looking on google for a way to shut down my tablet through adb and came across "adb shell halt". After typing this, the screen immediately turned off and would not turn back on. After google searching I only found one person with the same problem. Looking into the "halt" command a bit more, I've learned that apparently it forcefully shuts down the Zygote which causes the Android system to forcefully close everything without giving anything a chance to save. Apparently the only thing left active is the Linux kernel, or at least that's what I've read. It's said that a battery pull can fix this, however I've repeatedly removed the battery, waited 15 minutes (and once overnight) and put the battery back in, only to constantly have the same result; it simply won't turn on, or at least show any signs that it is on. I've seen people saying that "adb shell start" will restart it, but I can't reconnect it to adb, I've tried several times. The only other thing I have seen is to mod the board and solder a chip to test pads that will allow me to communicate with the Linux kernel, but I'm hoping that there is another thing I can try first. If anyone can help me, I would REALLY appreciate it.

the100guy said:
I have a samsung galaxy tab 2 7inch that is rooted and running a cyanogenmod 11(i think) nightly. So here's the story:
I was looking on google for a way to shut down my tablet through adb and came across "adb shell halt". After typing this, the screen immediately turned off and would not turn back on. After google searching I only found one person with the same problem. Looking into the "halt" command a bit more, I've learned that apparently it forcefully shuts down the Zygote which causes the Android system to forcefully close everything without giving anything a chance to save. Apparently the only thing left active is the Linux kernel, or at least that's what I've read. It's said that a battery pull can fix this, however I've repeatedly removed the battery, waited 15 minutes (and once overnight) and put the battery back in, only to constantly have the same result; it simply won't turn on, or at least show any signs that it is on. I've seen people saying that "adb shell start" will restart it, but I can't reconnect it to adb, I've tried several times. The only other thing I have seen is to mod the board and solder a chip to test pads that will allow me to communicate with the Linux kernel, but I'm hoping that there is another thing I can try first. If anyone can help me, I would REALLY appreciate it.
Click to expand...
Click to collapse
Can you get into recovery or download mode? can you get your device to connected to pc via adb? if none of these, then that's the only way my friend.

Seems like i have same problem.I also had cyanogenmod11 runing for like 3-4 months before it simply...died 2 days ago.It does not respond to any charger/usb/ car charger/ battery pull. Even tried to power the motherboard on without any daughterboard connected.Still dead.
It's a P3110 (wifi).Any suggestions?Thanks alot, i can and i'm willing to try anything that does not include desoldering/soldering chips.Thanks alot

How to determine the cause for unexpected phone shutdown?

Hi all. I have Nokia 8.1 for a few months now. Updated to Android 10 immediately and it has been rock stable. Until today.
At about 11am I heard an incoming message notification but was busy and decided to look at it later.
At 11:55am I picked the phone but could not wake it up - tapping didn't work, fingerprint didn't work. Black screen. So I long-pressed the power button and it booted up.
It is working fine since but I'm somewhat concerned about the issue.
I collected a zip log file through "adb bugreport" command.
As I understand, it's tricky to find the cause after the reboot because all log files are generated fresh after boot. I looked in \FS\data\tombstones folders and found three records there, all complaining about the following issue:
Code:
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'FORTIFY: %n not allowed on Android'
But they are almost a month old and I don't remember anything weird happening at that time; except maybe some Android system update and manual reboot.
Is there any place in that log zip or somewhere else on the device (without root) where I could find some info about what happened right before the unexpected shutdown? Kernel panics? Crashes?

Hmm, nobody? Does it mean that everybody else is just ignoring random shutdowns and have never attempted to debug the problem?

AFAIK logcat output isn't persisted over reboot, and maybe that's one reason nobody replied to this thread. But you can always write log to a file every time your phone boots (via shell commands etc) and just check out that file once phone rebooted.
Regarding kernel log, /proc/last_kmsg or /sys/fs/pstore/console-ramoops might be helpful.

Problems about "dev/block/loop", I/O error, and iosetup failed 1 Android-x86

Problems about "dev/block/loop", I/O error, and iosetup failed 1 Android-x86
So, I've been using Android-x86 for years without any problems, until recently.
A while ago, while I was playing some games on my previous Android-x86, my wifi died all of a sudden, and since I don't have anything else to do without an internet connection to it, I turned off my laptop and reboot when the wifi is back up.
While rebooting, I was then stuck in an infinite loop on the splash screen (which had happened a few times already), prompting me to reinstall Android-x86 (as per usual) because I can't think of any other method to fix it.
Normally, everything would be just fine, I just need to enable native bridge to be able to play the games I usually play, but this time something was off, and almost every games I used to play crash right away as if native bridge hadn't been enabled (which it was).
So I looked up to try finding a solution, and came across a guide to manually install houdini.sfs through terminal console, and the following kept happening:
mount: dev/block/loop(xx) I/O error
or
mount: iosetup failed 1
I absolutely have no idea what's causing this, and I can't find anything that talks about this error, and I hope I can find an answer here
Thank you for your time in advance