I'm seeing a small number of logcat entries from my apps since Android 13. I can only see a a couple of minutes before plugging the phone in to check the logcat. It's as if something is clearing the logcat. If I leave it plugged in it doesn't clear and I can see as far back as I could when I first plugged it in. I have increased the log buffer size in Developer Options to 4M and then 8M and it's still the same. I should be able to see logcat entries from the previous day with such big log buffers! It's also the same whether checking the logcat from Android Studio or from the phone itself with a logcat reader app (if I don't leave it open).
What should I check to solve this?
Anyone? Please help. This makes it very difficult to debug overnight.
Related
Okay, any ideas on why when i plug my Evo into any computer USB it charges, but it doesn't give me the menu to connect to it, it use to.
USB Debugging mode enabled, no there are no alerts in the notification menu. I have even tried changing the default preference on what to do.
Handheld is 100% charged. I have tried powering off and on, pulling the battery, went into fastboot and can get there....but i can't connect from pc...so SDK and access evo-recovery for nandroid options are a no go.
I am realitively new to this, and am hoping the experts and the community will be able to pull through for me.
Thanks
rooted and running 3.1.2 RvU with radio fix patch applied.
oh, and just to make it further clear, the handheld is working great aside from that...
(i also tried different cables)
Anybody??
Anybody else ever see this before?
Identical problem. It started after the phone crashed while on a call. Don't know how to fix it, but I'll let you know if I find out.
So, the problem appears to have fixed itself (since I can now select my connection type again). I read on another thread that removing the battery for about a minute could be a potential fix. For me, trying again after more than 24 hours of up time seemed to be enough.
Hope this helps you out...
So for the second day straight my phone battery has dropped to half in about 4 hours screen off in my pocket... After closing every program and turning off data sync, the 3G connection is still constantly in use. I downloaded a network traffic program to check usage, and to my surprise my phone had downloaded over 60MB in just 1 hour. I restarted the phone and the problem seemed to be fixed, however it's started back up again, even after restarts and switch from airplane mode and back.
I'm already using SwitchPro, I have all sync options turned off already. The problem didn't come up until a few days ago.
I haven't installed any new programs or widgets in the last couple of daysIs anyone else having a similar issue? Have you been able to solve it?
I had the same issue then I flashed Fresh. Now it is working proper. I would suggest flashing a dif ROM or factory reset.
Load aLogcat or Quicksysteminfo , from market and look at your logcat file. The cause will be obvious from there. If the phone is "idle" and the logcat is recording what's doing the data moving, you can then kill it.
Is it me or is the hands free Bluetooth constantly running even when unchecked.Maybe im looking at the log cat wrong but it appears that way
It looks like location services was using all that data. I think anyway, I'm not sure If read the logcat right, but a lot of that information dealt with location stuff. I went to settings, privacy, and disable google services from using my location and the constant 3g seems to have stopped.
Why would it just go ape **** like that after having the phone for 3 weeks?
I just noticed the same problem, turns out it was the people app that was causing it. I killed it and data traffic stopped. You can launch it from the menu and it loads back up and is fine. Just seems to be when it starts by itself when you first boot up the phone.
Hi, yesterday I had my nexus 7 charging, when I checked after a couple of hours, I noticed it was fully charged, but the wifi icon was white and "empty" instead of blue and "full", so I went to disable the wifi and enable it again, but it got stucked at "turning on wifi".
Mine is on 4.2.1 and it's rooted, but with the google factory rom, and clockwork recovery. I reset the nexus, same issue, so I reset the nexus again and went to the bootloader and wiped the cache, got the same, so I did a factory reset and got to the setup screen, chose the language and it goes to select wifi and it's still stuck at turning wifi on, and I can pass that screen, is there a way to fix it? is my wifi radio toasted? I need help and I searched on the forums for something like this and I could not find anything, any help will be appreciated.
anyone? I need help with this.
Sounds more like a hardware problem than a software problem, although on a different device (android phone) I could get similar symptoms to appear after fooling around with certain WiFi tether apps. At least one difference between that case and this one though, was that I was able to always clear the problem up with a reboot.
You might be able to get more insight by looking at "dmesg" output or possibly a dumpstate report.
Turn WiFi off, reboot, capture dmesg output, turn WiFi on (fails), capture dmesg output again. (Point of the first capture is only to get approximate starting time of the WiFi fail time - the dmesg timestamps are in seconds since boot, not UTC or local TZ)
good luck
I had my phone on today and after about 13 hours of being on with less than 15 mins of screen time, I noticed it was awake for all 13 hours. Also, I don't know why, but even being rooted I am unable to view Alarms in BetterBatteryStats.
If anyone could look at my log and offer any insight on the problem, it would be highly appreciated.
jsilvermist said:
I had my phone on today and after about 13 hours of being on with less than 15 mins of screen time, I noticed it was awake for all 13 hours. Also, I don't know why, but even being rooted I am unable to view Alarms in BetterBatteryStats.
If anyone could look at my log and offer any insight on the problem, it would be highly appreciated.
Click to expand...
Click to collapse
Some service is holding a wakelock while accessing the modem. Either that service crashed/hung without releasing the wakelock, the modem didn't respond, or there's simply a bug in the code. I would reboot and see if it happens again. If so, think about which apps you installed directly before this started happening. If you're running a custom ROM/kernel, this could be the root of the problem. With the BetterBatteryStats log alone, there if no way of telling this
XDA_Bam said:
Some service is holding a wakelock while accessing the modem. Either that service crashed/hung without releasing the wakelock, the modem didn't respond, or there's simply a bug in the code. I would reboot and see if it happens again. If so, think about which apps you installed directly before this started happening. If you're running a custom ROM/kernel, this could be the root of the problem. With the BetterBatteryStats log alone, there if no way of telling this
Click to expand...
Click to collapse
Thank you for the response, as far as I can tell it was caused by an edit to the hosts file, since reverting the hosts file back to default (only localhost) seems to have fixed the problem.
Has anyone else noticed that notifications seem to be super slow in coming after the Pie update? Line and Email can take up to two hours to exhibit a notification. I've looked at the notifications area of the apps, and nothing appears to have changed that I can see, and I can't find anywhere in Pie to tell it to allow more background time for these apps. I've tried force stopping and restarting with no change.
If anyone has any idea on what is going on, and how to fix it, your help would be most appreciated. Being told your wife left you a Line message 2 hours after she did so, or that your kid sent an email 2 hours earlier, is NOT conducive to a happy home life.
Nobody else has this issue? It appears to be connected to the fact that the phone is sitting undisturbed for a long period of time. If I am carrying the phone around with me, the notifications seem to come as expected, but if the phone is just sitting on my desk for a while, they seem to come from minutes to hours later.
You could try to whitelist those apps on Battery Optimization
I'm no expert, but from what you describe sounds like the phone is entering into Doze and notifications cannot come until the next maintenance window
If a user leaves a device unplugged and stationary for a period of time, with the screen off, the device enters Doze mode. In Doze mode, the system attempts to conserve battery by restricting apps' access to network and CPU-intensive services. It also prevents apps from accessing the network and defers their jobs, syncs, and standard alarms.
Click to expand...
Click to collapse
https://developer.android.com/training/monitoring-device-state/doze-standby
I think white listing the app prevents this behaviour
It does sound like you are correct and the phone is entering Doze mode, delaying the notifications. Thanks for that!
I will check into how to add the email and Line app to a whitelist for Doze. Hopefully it's a simple task, but I don't see anything under Battery doing a quick scan.
Just a follow up. After much searching and reading, I finally found where to turn off battery optimization for the two apps I needed notifications from. FYI:
Most things on the web say to go to Settings->Battery, then hit the three dot menu and select Battery Optimization. This does not appear on my phone. (see screenshot) To get to the list of optimized apps, you need to Search->Battery Optimization, select Battery Optimization from the results (it will take a few seconds to load), then tap Not Optimized and select All Apps. Find the app you want, tap it, then select Don't Optimize. You can also go to Apps and Notifications->Advanced->Special app access->battery optimization.
Whether this will actually fix the problem is another question entirely as most posts say that Doze continues to work. I guess we shall see.
I hope this saves someone the aggravation of trying to find something directly relating to Pie. Most things out there are for older builds.
Also, I turned off Adaptive Battery to see what the actual difference is in my light usage use case. If you are interested in the results of this test, let me know and I will post here.
Glad you were able to whitelist those apps.
I think it's weird anyway, as far as I know deep doze takes hours to trigger and the device has to be completely still. Any movement would take the device off deep sleep and enter a less aggressive doze (where notifications would be checked more often)
You did mention this is your case (you were leaving your device on your desk) but just for curiosity, how long approx would you leave your phone unattended?
Thanks and I hope this solves your issue.
Tepig said:
Glad you were able to whitelist those apps.
I think it's weird anyway, as far as I know deep doze takes hours to trigger and the device has to be completely still. Any movement would take the device off deep sleep and enter a less aggressive doze (where notifications would be checked more often)
You did mention this is your case (you were leaving your device on your desk) but just for curiosity, how long approx would you leave your phone unattended?
Thanks and I hope this solves your issue.
Click to expand...
Click to collapse
Unlike some folks, I am not tied to my phone. It often sits on the desk undisturbed for 3 or 4 hours during the day unless a notification comes in and I pick it up to look at it. Most of my screen time is on my computer, so the phone is the external brain when out and about, but not used much otherwise. At night, I turn on airplane mode until I get up the next day, then turn it off. I'm a retired software engineer, so have no real need for constant communication anymore, and I like it that way.