I'm getting a lot of these errors in my log, and suspect it's may be the cause of my battery draining quickly just on standby.
Are others getting this error, or might it be just a stray app?
Getting them too!
Related
Firstly, please don't bombard me with the check apps responses and the like. I've been running down apps and processes for 2 weeks. I went from being able to use my phone all day with gps on, wifi on, email syncing, and all that good stuff, and still have plenty of juice left after a full day. All of the sudden my phone is draining so fast that it will barely make it overnight (unused). From around 12:30am- 6:30am my phone went from 78% - 2% and was in deep sleep for around 5hr45min of that time. There were no changes or new installs during the period when this started happening. I actually have two Bionics (hwd A & hwd C versions) that were RDlite back to stock ICS within one day of each other (months ago), with not much done to them other than root and unlocking sim. Both started exhibiting this behavior around the same time. Killing apps and background processes and services make no difference at all. The excessively quick drain continues even when in deep sleep. I haven't done another reset, but from what I've read up on the issue, that procedure hasn't helped anyone else who've started experiencing this same problem?
Any suggestions beyond the same ol' 'check your running apps and cpu use'. Something is wrong beyond apps keeping the phone awake or active when the issue continues while in deep sleep.
Your phone is obviously not in deep sleep if it goes from 78-2% unused overnight. Either that or both your batteries are failing at the same time.
Betterbatterystats is telling me it's going into deep sleep. I didn't think so either, for the obvious reasons, but it does without any excessive delay when the phone is left alone. Andriod.os battery use is always in the 60-80% range unless I'm playing a game or something that you would expect to eat up an appreciable amount of cpu cycles. I have 10 instances of kworker/u, is that many normal? 6 of those seem to dominate the energy consumption by android.os. This is the only thing that I've found that stands out. I may be wrong, I don't know much about linux, but I thought that I should also see some type of activity from an app associated with higher kworker activity and/or that many instances running. I admit I'm assuming more than anything else there though.
I find it more plausible that my issue is more related to an issue which seems to be common across a broad range of users, than 3 batteries tested in 2 different phones suddenly acting abnormally, but all in an identical fashion. I don't think it's hardware related either. Two different hardware revisions! Highly unlikely to phones manufactured so far apart would start to exhibit the same hardware related issue at the same time. It would be more likely to occur over a similar period of operation or age in that case. The only common factor, other than when the phones started exhibiting this problem, is that they were flashed back to stock ICS within a day of each other around Feb or March.
I suppose it'd be really rare that this would happen on both phones but is it possible the batteries are just trashed? Try a new one?
I'll preface this by saying, this is kind of a stupid question, kind of just common sense...
Here is my scenario though:
I have disabled certain apps push notifications for the sake of saving battery and partly for data consumption. Instead i just end up checking the app manually several times a day.
I am wondering if turning my phone on and opening the app may actually be more of a drain on battery and network than just having push notification on, especially if there are no new notifications most of the time i check manually.
I'm thinking there are probably ways to scientifically approach this, by checking the battery or data stats for each scenario (push on/off) but I'm curious if anybody has first hand knowledge already they could share.
steelcity said:
I'll preface this by saying, this is kind of a stupid question, kind of just common sense...
Here is my scenario though:
I have disabled certain apps push notifications for the sake of saving battery and partly for data consumption. Instead i just end up checking the app manually several times a day.
I am wondering if turning my phone on and opening the app may actually be more of a drain on battery and network than just having push notification on, especially if there are no new notifications most of the time i check manually.
I'm thinking there are probably ways to scientifically approach this, by checking the battery or data stats for each scenario (push on/off) but I'm curious if anybody has first hand knowledge already they could share.
Click to expand...
Click to collapse
For the data consumption part, you can get detailed data on the power issues by using Application Resource Optimizer that AT&T offers (for everyone including non-AT&T users). It gathers detailed data (down to packet sniffs) on how the application makes radio requests and if there are issues with the requests and gives you list of issues, profiling, and power consumption of the app in joules. You can get a copy of their tool at ARO's website.
Recently I've been experiencing heavy background drain on oos unrooted 5.0. I'm only getting about 2-3 hours sot, and as a result I performed a factory reset yesterday. After the reset the battery life was pretty much the same. I used the adb command from this thread (https://forum.xda-developers.com/oneplus-3t/how-to/battery-life-heres-how-fixed-t3536456) to inspect the processes running in the background and using CPU. From the chart, I notice an entry labeled "logd" that is consistently running in the background and using anything from 1-5% of CPU. In my battery stats in settings, cell standby and Android system are both above screen battery usage. I think that cell standby is caused by the use of LTE, but I don't know that is causing the Android System drain. Android OS also shows up but it's farther down the list. Does anyone know a solution or a reason as to why or what "logd" is doing constantly running in the background? In addition to logd, there are also several other processes running while the screen is off/on, but I'm not sure if they're significant as they never really stay on the page for long, while logd does.
ps. from time to time, I get a "bug report captured" notification even though I didn't intentionally take a bug report. After "bug report #1 captured" I get a "bug report #2 captured" a few minutes or hours later and then a "bug report #3 captured" ...etc. This only happens sometimes, and at other times it doesn't occur at all.
Hello.
I use my Z8 as a daily driver about 3 months. I have a trouble with battery drain. Some screenshots:
Why does the system sometimes take 8% and sometimes not at all. "Android OS" and "Android System" in battery info are presents, battery drain is high. If these processes are invisible, battery drain is OK. Why?
Problem solved:
daemon /*bin*/sscrpcd is a mine problem. I delete this daemon from filesystem, battery OK and even proximity sensor alived!
Hey, what exactly you mean by this sscrpcd?
I simply deleted this program (sscrpcd) and battery drain stopped, proximity sensor alive.
sscrpcd is a daemon for sensors.
Topic
Hi,
where can i find this program sscrpcd so i can delete it.
# find / -name sscrpcd
/vendor/bin/sscrcpd
After clean installation
lineage-19.1-20230407-nightly-sake-signed.zip
pjk11 said:
/vendor/bin/sscrcpd
After clean installation
lineage-19.1-20230407-nightly-sake-signed.zip
View attachment 5884213
Click to expand...
Click to collapse
Well I am on stock OS and don't have RW on vendor so would need to change OS but will probably do that anyway. Last thing to give my zenfone 8 a chance before switching to other brand due to how bad battery is. Maybe on LineageOS it will magically resolve.
You need root.
i got this error "Problem Reading Your Battery Meter" and it didn't even charging the battery,,,i'm ****ed up!! anybody know what caused this and how to solve it??