Hi,
I got a Note 4 with stock Lollipop (no root, 100% stock) and I'm experiencing horrible wakelocks. As you can see on the screenshot my Note 4 is permanently awake...
Is there any way to find out, which app is causing these wakelocks without rooting the phone? (I don't want to trigger Knox count because of warranty)
Thanks
Restore factory settings. 100% awake is not normal
Related
Hi all,
So I recently took my trusty N4 running CM 10.1 w/Matr1x 9.5 all the way back to stock.
Used Wug's root toolkit app (great stuff), downloaded the 4.3 factory image from Google and took the phone to a completely stock version -- lost root and custom recovery in the process (as expected).
I have since rooted and added TWRP. The only apps using root at the moment are Auto Hide Soft Keys, Better Battery Stats (XDA ver), Busybox free, Greenify, and Quick Boot.
TLDR: N4 is Stock + Root, running 4.3
With the phone all set up now, am facing a weird battery drain issue.
The app that takes up the most battery is the DIALER app. I've attached screenshots from right now showing how the dialer is #1 draining battery (ignore the high battery life, this is from overnight when the phone was barely used).
Over the past week the general trend I'm noticing is ~12-14 hr of usage (normal usage of calls, browsing, email, all sync enabled; phone dies at this point), dialer shows CPU total 1h30m+, with very little actual foreground time. This is a far cry from the 15-20h I've generally gotten from this phone (whether stock, AOKP, CM etc, same usage pattern).
A friend of mine suggested that maybe the proximity sensor is keeping the phone and dialer app awake constantly. I used the Proximity Sensor Finder app which showed me that the proximity sensor was working. Playing with the proximity sensor in this way seems to reduce the CPU usage of the dialer, and improve the battery life.
Questions: Hardware or software issue? Any other way to debug/test what is broken?
Any thoughts, ideas, suggestions are welcome.
Any one have any ideas?
My battery stats today morning: Phone at 80% battery level after 1h 35m, with dialer at 51m 6s usage.
Seriously wondering if this is RMA material.
Have the same problem with my n4. Stock rom 4.4, rooted. Drives me nuts. All of a sudden dialer sucks my battery empty.
I'm not sure but I think you may use Greenify Xposed Module (donation pack) which makes you can hybernate system apps.
You could use it to hybernate the dialer.
Hi Guys,
i am currently using a Samsung note 3 and my battery only last for about 10 hours.. i tried all method but still did not get back to it original state... it lost about 30-40% over night... there is an ads on Kijji stating that
"We provide rooting and Custom ROM installation services.
Have you been experiencing excess battery drain after the Android 4.4.2 update?
Is your phone barely able to get a single day on a full charge?
If so, we can resolve these issues by rooting and loading performance optimized ROMs.
The Galaxy Note 3 CPU supports overclocking after rooting and allows your phone to exceed the performance of the current Galaxy S5.
The overclock is load dependant meaning it will only scale up as needed providing you with the improved battery life & performance you seek.
For current stock Canadian model Note 3's SM-N900W8 we will keep your Knox counter at 0x0.
What this means is if you are still under warranty this will keep your phones warranty valid.
Many customers have seen battery life extended from less than a single day to more than one and a half days on average.
[/B]
I wonder if anyone can show it to me step by step of doing what he mentioned above ? i would be very appreciate it.
If you are sure that your battery is in order, at first, сheck that files on microSD in phone were available and visible in phone. If files on microSD aren't available, remove micoSD. It will restore normal consumption from the battery.
thank you for the reply.. how do i do tht ? how to check and remove files from sd ???
btw i dont hae any microsd card installed ...
Since you stated "how do I get it to original state", I would assume it was working fine until some time recently. So the obvious question would be what did you do right before excessive batt. drainage started: did you updated from 4.3 to 4.4, loaded some new program or change some settings? You stated the battery drain is 30-40% overnight, the only time I had anywhere near that was when switched Wifi power save to off in one of secret menus.
If there is nothing obvious you did, look at detailed battery usage and see what's running, especially during night. If you just updated to KitKat, some people suggested full factory reset helped them with excessive battery drain, but you will need to restore all your programs and settings. You could also root and "freeze" unused programs.
Personally I stay away from custom ROM's, since quiet often some things in those ROMs don't work properly and prefer to root and customize settings manually myself, by following many guides here, but it is time consuming and requires good deal of learning, so for somebody who doesn't want to bother, this type of service could work, maybe.
One thing for sure, 30 to 40% battery drain overnight means something is wrong and needs to be fixed.
Try battery calibration app
Hi!
I'm facing an issue with my Note 4 N910C. I upgraded to Lollipop a few days ago. Malaysia. And since then experienced very fast battery discharge.
I also realized my dataplan is almost completed, so I checked my usage via My Data Manager. I was surprised that Knox was consuming the most data. Almost 800MB!
Any advice to shut it down or turn it off?
I can't even find the app?!
Thanks!
Willing
I have a Galaxy S6 Edge+. It's a second hand phone and I have only been using it for a couple of days. But I think it uses way too much battery doing nothing.
Last night I charged it to 100% and then unplugged. It had used 51% from just idle. I see that AndroidOS is using 46%... The phone is not rooted. Is my battery broken or is this something I can find out? How can I find out what part of Android drained half my battery overnight?
Deep sleep is probably not working and the person who had the phone before you might have tripped Knox. Go into download mode and check if Knox is tripped if it is, flash a custom kernel with deep sleep fix.
Thank you for replying. Knox has not been tripped. Just checked. How can I see if the phone reaches deep sleep or not?
This happens to me very seldom, otherwise I don't have this deep sleep problem.
When it happens I restart phone.
I am not rooted and Knox is OK, but I have 190 apps/services disabled with Package Disabled Pro.
I'm having some issues with my phone being awake when it is charging. I've checked the most obvious causes such as daydream, and the keep awake setting, but neither were active.
I'm not sure what actually keeps it awake as battery stats end up being erased at 100%. I have Wakelock Detector installed but that doesn't give me any conclusive evidence either since again, the stats are gone once the phone is fully charged. This is mostly an inconvenience as after disconnecting the charger, the battery use is about normal and I can control the wakelocks through Greenify, Amplify and the Privacy Guard's keep awake function.
Has anyone else experienced/solved this issue before and what did you do?
My current setup is:
Android 6.0.1
Resurrection Remix ROM
Nevermore Kernel
I have noticed that most ROMs above 4.4 seem to have an adverse effect on battery life on my S4 and my Galaxy Tab 2. 6.0 seems to be giving me the same standby time of 4.4 however on my tab, so I was hoping that it'd do the same for my S4 as I want to move away from using the Davlik runtime.
Always awake on charging is normal habit, you don't need to worry such thing.
Sent from my HUAWEI SCL-U31 using XDA Labs
Not for Samsung it's not .....at least not on the 4 Samsung devices I own (the AMOLED screens on them would get horrendous burn in if the screen remained on for long periods of time).
There is an option in
Settings>>developer options
that will prevent the screen from sleeping while the charger is plugged in, but the default setting for this option is disabled. Just double check to see if it has been enabled......
It wasn't normal in 4.4 nor 5.1, so either this was changed in 6.0 or my kernel is forcing this behavior, I may try switching kernels. As I mentioned previously, the dev options don't have anything enabled that would cause it to keep awake.