As the title suggest my phone redmi 3s drains 10% battery in just 8 hours of night. When i see cpu states it shows that it only goes 1 hour deep sleep in night. Using Havoc oreo. I think the Problem is with stock kernal so i tried chimera kernal. But the problem still there. Tried greenify but still deep sleep problem. Now how to detect which wakelock wake the device ? And how to block it. Yes remember i have magisk root as well as exposed installed.
Please help!!!
*removed*
krishna_jm said:
flash this deep sleep zip file from twrp. if it doesnt help, flash emperor tweaks next. good luck
Click to expand...
Click to collapse
Is there any chance of that these zips can brick my device ?
Related
Hi all
I'm kinda frustrated and this is my story.
I have Edge + for less than an month (this is my firs Samsung device). I feel pretty familiar with the rooting and other installation, so after I got this device I installed PhilZ Recovery and the Arter kernel.
The device was kinda laggy and after I've tried to restart the device it stock on FRP lock and I flashed the original firmware and decided to let it chance. After that no matter what I did including reflashing
the original firmware, Android System keeps draining the battery, in one night it lose 30% with doing nothing (I guess it is some deep sleep bug). It's like CPU works half of the time while the device is turned on
(with or without Screen is ON).
My question is why actually this happen? Is it common issue with the original firmware? What can I do?
All advises will be welcomed.
Thanks!
stas-ta said:
Hi all
I'm kinda frustrated and this is my story.
I have Edge + for less than an month (this is my firs Samsung device). I feel pretty familiar with the rooting and other installation, so after I got this device I installed PhilZ Recovery and the Arter kernel.
The device was kinda laggy and after I've tried to restart the device it stock on FRP lock and I flashed the original firmware and decided to let it chance. After that no matter what I did including reflashing
the original firmware, Android System keeps draining the battery, in one night it lose 30% with doing nothing (I guess it is some deep sleep bug).
My question is why actually this happen? Is it common issue with the original firmware? What can I do?
All advises will be welcomed.
Thanks!
Click to expand...
Click to collapse
I would suggest finding the stock firmware and kernel and re flashing both clean. I have the Edge+ international version and I also rooted and flashed the Arter kernel... But i do not have deep sleep issues. I will loose probably 2-3% battery over night with sync and Wi-Fi off.
Sent from my SM-G928F using Tapatalk
Speedster_1 said:
I would suggest finding the stock firmware and kernel and re flashing both clean. I have the Edge+ international version and I also rooted and flashed the Arter kernel... But i do not have deep sleep issues. I will loose probably 2-3% battery over night with sync and Wi-Fi off.
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
That exactly what I did I flashed (even a few times) the original kernel and ROM via Odin but the issue is still there.
2-3% per night it's nothing comparing to my 30% So I guess you don't have any deep sleep issue
stas-ta said:
That exactly what I did I flashed (even a few times) the original kernel and ROM via Odin but the issue is still there.
2-3% per night it's nothing comparing to my 30% So I guess you don't have any deep sleep issue
Click to expand...
Click to collapse
True but my G3 used to sleep for 8 to 10 hrs straight with 0% drain.... But oh well.
Sent from my SM-G928F using Tapatalk
Speedster_1 said:
True but my G3 used to sleep for 8 to 10 hrs straight with 0% drain.... But oh well.
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
Hey. Yeah G3 is the best in deep sleep case. no drainage for a day for 6 days just %1,, but too much drainage while using tho
I'm not sure if my problem is the same as yours. But my phone was facing the same battery issue on stock firmware. I turn off everything, even with flight mode on, the battery drain was like 30-40% overnight.
After I installed gsam battery monitor, I found out that the android system was the main culprit. The android system drain amount was like 7-10 times to kernel (android os), and the apps also showed that my phone was kept awake all the time. No matter what firmware I used, the problem still persists. Fortunately, the problem was then solved when I installed arter97 kernel, or any kernels other than the stock one.
fenrir_ac said:
I'm not sure if my problem is the same as yours. But my phone was facing the same battery issue on stock firmware. I turn off everything, even with flight mode on, the battery drain was like 30-40% overnight.
After I installed gsam battery monitor, I found out that the android system was the main culprit. The android system drain amount was like 7-10 times to kernel (android os), and the apps also showed that my phone was kept awake all the time. No matter what firmware I used, the problem still persists. Fortunately, the problem was then solved when I installed arter97 kernel, or any kernels other than the stock one.
Click to expand...
Click to collapse
Yea, this is the exact my problem. Eventually I flashed Arter97 kernel and seems like the issue actually disappeared.
Thanks!
I have the same problem. No deep sleep on stock rom ! Any help ?
Thnks a lot
L
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
CoinCoin88 said:
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Click to expand...
Click to collapse
looks like you are having weak or no signal. this is likely to cause this issue!
Bac0nator said:
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
hellcat50 said:
looks like you are having weak or no signal. this is likely to cause this issue!
Click to expand...
Click to collapse
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
CoinCoin88 said:
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
Click to expand...
Click to collapse
sultan's rom is cm13 with caf kernel. it is known to be very battery friendly.
Here is the link: http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Sultan's builds are optimized for battery on the one plus one. They tend to be better than official cm13 builds, most of the time.
Another option is downloading an app called nap time on the play store, which forces your phone to go into deep sleep the moment the screen shuts off.
CoinCoin88 said:
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Click to expand...
Click to collapse
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
I have the same issue on Sultan's Rom. First 20 days battery life was awesome and now all the time phone is awake. I am reflashing sulatn build again
Thanks for this info, this is going in the same direction I observed and somewhat reassuring. Are you talking about CM nightlies then ?
edit: that was inteded for @tiny4579
Sent from my A0001 using XDA Free mobile app
tiny4579 said:
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
Click to expand...
Click to collapse
By any chance, would you happen to have SuoerSU as root binary/manager? I recall it patches boot.img which prevented encryption from being run in the first place (to encrypt, I had to reflash the stock boot.img, encrypt, then reflash SuoerSU). I'm wondering if the altered boot.img couldn't be part of the problem.
Sent from my A0001 using XDA Free mobile app
Some heads up: there was indeed a wakelock issue that has been fixed by a commit on the 4th of June.
See associated bug on JIRA: https://jira.cyanogenmod.org/browse/BACON-4987 (and appreciate how it's easier to blame the user than to try to replicate a bug). Hopefully we'll have a 'future OTA' before the end of the year...
I still have this wakelocks issues right now...
Hi,
I am having battery issues on stock. So I rooted, all fine no problem. Got over it went back to stock... have huge battery drain issues and I have confirmed device does not enter deep sleep and always has cpu awake.
How can this be fixed? I flashed stock standard ROM back but that is the problem... apply root and all is well.
Anyone else had this?
Flash arter97 kernel deep sleep fix
Thanks but how would I do that being on stock no root
Hi,
After I root my phone (sc02h, cook rom nougat 7.0) with supersu 2.82, I noticed that I could not on/off the phone display with the clear view cover. A message asking me to use nfc but I can not turn it on (it does not turn to blue and always off when I go back). The beam feature also does not work (cant choise, its gray), tap & pay feature gray too..
Also when I use spy cpu, deep sleep does not working.
All these features are fine before I root my phone.
Please help. And thanks for read...
Same here. No deep sleep, no Nfc.
I have root, twrp 3.1.1.0, supersu 2.82 sr1.
Will try full stock restore and Cf autoroot (CWM recovery). Seems Cf has not these issues.
gigies said:
Same here. No deep sleep, no Nfc.
I have root, twrp 3.1.1.0, supersu 2.82 sr1.
Will try full stock restore and Cf autoroot (CWM recovery). Seems Cf has not these issues.
Click to expand...
Click to collapse
And what now? My friend
OFz said:
And what now? My friend
Click to expand...
Click to collapse
At least, the problem was Nfc. With root and Twrp, Nfc won't no more turn on and generates constant wakelock (no deep sleep at all).
I flashed CWM recovery and then phone goes in deep sleep sometimes (rarely), but Nfc wakelocks were still the problem.
So, I manually renamed Nfc, Tag and Beam apks from /app and /priv-app [.apk -> .bak] (since I don't use Nfc, that is not a big problem for me).
Now no more wakelocks and phone enters deepsleep normally
Probably flashing Cwm (via Cf autoroot) directly on clean stock rom would not have caused the "Nfc not working" and wakelocks issues. I did not try this because the workaround I've described is time saving, and good enough for my needs
gigies said:
At least, the problem was Nfc. With root and Twrp, Nfc won't no more turn on and generates constant wakelock (no deep sleep at all).
I flashed CWM recovery and then phone goes in deep sleep sometimes (rarely), but Nfc wakelocks were still the problem.
So, I manually renamed Nfc, Tag and Beam apks from /app and /priv-app [.apk -> .bak] (since I don't use Nfc, that is not a big problem for me).
Now no more wakelocks and phone enters deepsleep normally
Probably flashing Cwm (via Cf autoroot) directly on clean stock rom would not have caused the "Nfc not working" and wakelocks issues. I did not try this because the workaround I've described is time saving, and good enough for my needs
Click to expand...
Click to collapse
I dont know why but recent, my phone can go to deep sleep, now big problem for me is cant turn off display when i close clear view cover, may be problem is nfc or tag or beam..
Any help @@ i dont using nfc but i get mad bc i cant turn off display when i close my flip cover :laugh:
I'm posting this once again hoping one of you is experiencing the same problem.
The gist of the story is, when I root my phone, it drains battery quick leaving me with 2-2.5h SOT. When it's not rooted, it goes back up to 6h SOT.
This is not a rogue app problem, it's not a kernel problem, it's not a media scanner problem, it's a ROOT problem. And it stems from the days of Oreo, all the way to now where I'm on the latest OneUI build (February patch).
Somehow, when magisk or SuperSU is installed, it just drains battery quick. Does anyone have the same problem?
For clarification: tried safe mode, both rooted and u rooted with the same outcome: more drain on root than on non-root. Also tried COMPLETELY formatting the phone, and go from there with absolutely no third party apps installed; same outcome.
Thanks.