I'm on the US NG1 firmware on the Tab Pro 8.4 (all stock) and I seem to have this situation where CPU Cores #2 and #3 are always on, and always running at least 1.5GHz. In fact they seem locked at 1.5GHz (they don't seem to go faster or slower) which is very strange. Both CPU-Z and the "device info" screen of AnTuTu show evidence of this.
Any ideas?
I've already tried killing all programs/tasks/recent apps ... no change.
( A few days ago I had the issue where even when the tablet was idle (screen turned off) for several hours it was basically almost fully awake, and the main culprit was "Google Play Services" which used way more battery than even the SCREEN. Very weird. But after 2 days of this weird behaviour, it stopped and the tablet was able to stay in deep sleep most of the time in Idle )
Strange behaviour indeed...I have troubles with deep sleep to, but not related to the cores locked to max freq.
Try hard reset, and if it doesn't work, go for replacement. ..
I cleared Cache from Settings->Storage and did a cold boot (turn off, wait, then turn on)
The issue seems to be gone. I quickly opened each of my most-freq-used apps at least once ... then checked CPU-Z again, and it's still fine (CPU cores are sleeping).
So it's not one of my frequently used apps.
I'll probably check my Battery specs on a daily basis for the next little while to ensure it doesn't come back.
BTW are there any apps for unrooted phones which can detect wakelocks? All the ones I saw on the Play Store require Root to detect wakelocks
Related
This morning i have unplugged my phone from charger. After 3 hours of not using it, my battery went down for 6-7% and when i entered battery history i saw that my phone processor was awake for 3 hours!!!
I have posted dump file several times (from betterbatterystats) on the thread about betterbatterystats but no one is answering.
Can any one please help me ?
Dumpfile
Strange...
BTLowPower (a kernel wakelock) kept the phone awake this whole time.
I've never seen a kernel wakelock like that before.
If it wasn't just a mishap (reboot and see if she's sleeping) try turning off bluetooth or flashing a new kernel.
Edit:
It's also saying no signal...which is incorrect...as I'm looking at your screenshots.
I'm no expert on reading the logs...but that's odd.
You were not using it, but it was not asleep, in the way a laptop does a low power "sleep".
Possible sources of use: system, apps, radios, screen
a. system:
OS's have a lot of background processes, and I have to say 3.5% (56% x 6-7%) in 3 hrs does not seem unreasonable,
even if nothing else was running (eg lots of os scheduled processes to check stuff, eg updates)
(btw, I have written OS kernel schedulers in the old days)
b. Are any of your apps trying to get data, eg podcasts, news, weather...? Looking for or Getting Updates?
c. You have wifi connected - that will use battery. Turn it off.
d. The screen was on at least part of the time. That uses battery. 11% (of the usage) from your screen.
Apologies if I have misunderstood your question.
undecidable said:
You were not using it, but it was not asleep, in the way a laptop does a low power "sleep".
Possible sources of use: system, apps, radios, screen
a. system:
OS's have a lot of background processes, and I have to say 3.5% (56% x 6-7%) in 3 hrs does not seem unreasonable,
even if nothing else was running (eg lots of os scheduled processes to check stuff, eg updates)
(btw, I have written OS kernel schedulers in the old days)
b. Are any of your apps trying to get data, eg podcasts, news, weather...? Looking for or Getting Updates?
c. You have wifi connected - that will use battery. Turn it off.
d. The screen was on at least part of the time. That uses battery. 11% (of the usage) from your screen.
Apologies if I have misunderstood your question.
Click to expand...
Click to collapse
You've misread the log, for one.
His phone wasn't asleep the entire time.
And he seems to understand that this is a bad thing.
But it wasn't an app, it was a kernel wakelock.
And wifi is better than 3G/4G unless you're getting full signal...
The wifi was on when i was catching ss and saving logs..
The thing is that i have weather update on automatic. That might be a problem ? But phone was not connected to internet during that time..
Help me ?
Reboot the phone, because the kernel is thinking you have no signal, while you actually do. Then recharge, and see if it stays awake again.
Sent from my Galaxy Nexus using Tapatalk 2
Is it normal for this phone not to deep sleep? I installed CPU spy and it shows that it always stays at 300mhz when the phone is idling. I have all apps closed in the recent apps tray and my phone is stock. Just wondering if this is normal. Thanks
I've been wondering the same thing... battery seems fine and none of my apps or keeping the device away, so I'm assuming it's the whole dt2w feature they have on it. Plus, they mention a "sleep mode" on the HTC website, so maybe they got their own thing or something...
Any info would be nice.
EDIT: Apparently, while charging the device, it will rarely go into deep sleep mode. After I took it off the charger, it was going into deep sleep exactly like it should.
I'm on stock, rooted, s-off
my device is getting extremely hot during normal use.(i dont play games at all, just whatsapp, facebook, news etc..)
sync is off, auto brightness.no google location reporting and history, no google now or history.
and using bbs to see what is going on ,i have no wakelocks and looking at battery screen, screen on time and awake time are almost identical.so nothing is keeping my device awake.
but for some reason, when the device is idle, the cpu goes nuts!
i installed cpu status bar xposed module so i could monitor cpu on real time, and i see the device jumping allot from 300mhz to 960 and 1000+ for no reason.(without touching it, and no apps running).when i touch the screen it scales to maximum.
it drives me crazy because i dont understand why the cpu behave like that.there is no logical reason for cpu going to max when i'm typing text.
its unbearable, cause its getting really hot while i hold it.
i have tried various kernels(elementalx, skydragon, faux, ionx, hacker kernel, but all of them shows that behavior.
on my old i9100, i never got that behavior, ondemand governor was perfect and i could reach 4 hours of screen on time.with the m8, i can barley pass it , going for 4-5 hours, because its draing too fast.
any suggestions?
*EDIT*
tried a factory reset, and i just installed xposed with cpufreq status bar module, and the device is still going nuts.WTF?
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
thebobmannh said:
Can I ask... are you sure this is abnormal? I mean, are you seeing ill effects? Is the device laggy? Is your screen-off battery time awful?
All OS's do stuff in the background, and "idle" doesn't really mean anything at all to be honest -- even when you "don't have any apps running" there are apps running, and you'll always see the CPU cycle from idle to low speed to high speed if you're looking for it.
Click to expand...
Click to collapse
i know there are background process and apps, and i don't except the device to stay at 300mhz all the time, but its quite annoying to hold on to a device and feel its temperature rising to insane levels without doing anything fancy with it.just texting.and every touch ramp the cpu to the max frequency, its weird.and unnecessary.
i don't know if its normal behavior, as i mentioned, my old i9100(galaxy s2) would not act like this. and i could get 4 hours of screen on time, and here, i get 4-5 hours max.it dose not seem logical.
I'm not using lte of nfc or BT.my reception is full(both wifi and cell).
i just want to know if this a normal behavior? anyone else having this heat buildup on light use?
I have a similar problem there on M8S. I killed half the background tasks, disabled syncing, auto backups, and then I open FBreader(or any other app) at 30% brightness and all the cpu cores go to 50 degrees C, heat up my battery to 43 degrees C. It results in loss of 40% of battery charge in just an hour. With screen off my device usually consumes 1-2% an hour. Whatever I do, I have never seen at least one core sleeping, they always work at 600-900MHz.
So - I'm not sure if I have a problem or not yet, but I thought I'd see if others have noticed anything strange. I just happened to open CPU Spy and noticed my Pixel XL (unlocked, rooted with MAGISK v 16, stock) had a very low 7% deep sleep after about 4 hours off the charger. The lowest 307 mHz CPU level had about 45% and the remainder was sprinkled throughout the various ranges with another 20% or so at the highest speed. This seemed strange to me as whenever I have checked on this in the past, Deep Sleep was always a large portion of the total CPU time...I can't say for certain if I have checked this on 8.1 or not until now. A quick Google search yielded some reddit and XDA threads specific to Deep Sleep issues on the Essential device and they seem to have concluded the issue lies within their stock kernel on 8.1. (Some resolved by switching to the Elemental X kernel based on 8.0 base). Anyways, I have tweaked my app "Background Check" settings to turn off for most non-essential apps and am preparing to more fully test this. But wanted to see if anyone else was having similar issues on their OG Pixel XL. I should also note that I am running the MAGISK module that allows you to "Optimize Battery use" for Google Play Services. And it appears to be working as Google Play Services is no longer a top culprit within WakeLock Detector. When this did not yield improved battery performance, that is what started me digging into this further.
Thanks,
S
Long story short, I have been experiencing a severe battery drain with any ROM I try for the last month or so. Some ROMs seemed not to have it until first reboot, then the drain showed up.
Installing BetterBatteryStats showed me there was a "fingerprint wakelock" active 100% of the time. This was a bit strange, because my fingerprint sensor doesn't even work most of the time (sometimes it works after installing a ROM, sometimes after a few reboots, but it always stops working eventually for no apparent reason).
But searching around, I came across this page, where the following step is suggested:
mv "/vendor/bin/hw/[email protected]" "/vendor/bin/hw/[email protected]"
By renaming the corresponding file on my current ROM (/vendor/bin/hw/[email protected]) and restarting the device, I got rid of the battery drain and it now shows a healthy deep sleep time! I suppose that kills the fingerprint sensor, but since it wasn't working anyway, no harm done.
Just posting it for posterity and reference to whoever wants to try, I have no idea if anyone else has the same issue. (now I'll go hunt down PowerManagerService wakelocks, which seem to be the next big thing eating battery)
First, thank you for your guide. After updating from 7.1.2 to 9 i experienced a severe battery drain issue as well and this solved it. Actually, the fingerprint sensor never worked on android pie for me (crdroid 5.3). I would like to add some information that may be usefull to people.
This battery drain was caused by the fingerprint sensor and can be diagnosed by cpu spy where you will see your phone not going into deep sleep at all (interactive mode kernel, no idea for performance or gaming modes), and better battery stats showing finger print sensor being responsible for a big part of kernel wake lock when the screen is off.
Renaming the file can be done either if you are rooted on the phone or ( as i have noticed many apps like netflix refusing to work on rooted phones, making it inplactical to having your phone rooted ) using adb usb debugging to rename the files. if you are not allowed to rename the files, remount the phone and try again, remounting will automatically mount it in ReadWrite, while sometimes the first time will mount only as read.
If the problem is fixed the cpu spy app will show a much larger time spent in the lowest clock state in interactive mode and actually phone spending time in deep sleep.
PS: DO NOT hunt down the power wake locks as stated in your post, as those are active when your screen is on, and those should be on.