Hi Guys,
I flashed the latest 5.0.1 Lollipop firmware (N910FXXU1BOC3) last week to my N910F Note 4.
Everything has been working okay. Until yesterday where the phone is constantly awake.
I have uninstalled all 3rd party apps and booted into safe mode yet it still shows as constantly awake in the power saving settings section.
I have tried using airplane mode, removing the battery for 10 minutes . Restarting multiple times to no avail......
Does Anyone have any suggestions?
BNerd89 said:
Hi Guys,
I flashed the latest 5.0.1 Lollipop firmware (N910FXXU1BOC3) last week to my N910F Note 4.
Everything has been working okay. Until yesterday where the phone is constantly awake.
I have uninstalled all 3rd party apps and booted into safe mode yet it still shows as constantly awake in the power saving settings section.
I have tried using airplane mode, removing the battery for 10 minutes . Restarting multiple times to no avail......
Does Anyone have any suggestions?
Click to expand...
Click to collapse
Reflash the firmware again and do a full set up as if it was a brand new device.
radicalisto said:
Reflash the firmware again and do a full set up as if it was a brand new device.
Click to expand...
Click to collapse
I shall try that when I get home. I restored my phone from a backup after I originally flashed 5.0.1.
This time I shall keep it as a fresh firmware flash.
BNerd89 said:
Hi Guys,
I flashed the latest 5.0.1 Lollipop firmware (N910FXXU1BOC3) last week to my N910F Note 4.
Everything has been working okay. Until yesterday where the phone is constantly awake.
I have uninstalled all 3rd party apps and booted into safe mode yet it still shows as constantly awake in the power saving settings section.
I have tried using airplane mode, removing the battery for 10 minutes . Restarting multiple times to no avail......
Does Anyone have any suggestions?
Click to expand...
Click to collapse
hi ,
your above post reminds me of my experience recently,with........BOC3
i upgraded from Android v 4.4.4 to BOB4 lollipop ( dirty flash ,no wipe, no factory reset ,
no problems at all .My device was running smooth ,no errors etc. battery ok .)
Flashed fom BOB4 to BOC3, i resetted my device etc .root recovery etc .
for a while everything was running fine,after a few days ,i started to have a bad wakelock .
Device was awake most of the time .
Lucky i was able to id/pinpoint culprit with" BetterBatteryStats " and Gsam battery monitor .
It was a system process something with....... Samsung security Filezip log..?
As i had an old app on hand "DisableService"( root ) and traced the process and unticked 3 relevant processes ( lucky guess ? ) and my wakelock is solved .Battery usage much better etc
BOC3 is just as good and stable as my previous v4.4.4 and BOB4...!!
So sometimes dirty flash works ok and sometimes flashing,then an factory reset..etc etc does not help.!
good luck
willcor said:
hi ,
your above post reminds me of my experience recently,with........BOC3
i upgraded from Android v 4.4.4 to BOB4 lollipop ( dirty flash ,no wipe, no factory reset ,
no problems at all .My device was running smooth ,no errors etc. battery ok .)
Flashed fom BOB4 to BOC3, i resetted my device etc .root recovery etc .
for a while everything was running fine,after a few days ,i started to have a bad wakelock .
Device was awake most of the time .
Lucky i was able to id/pinpoint culprit with" BetterBatteryStats " and Gsam battery monitor .
It was a system process something with....... Samsung security Filezip log..?
As i had an old app on hand "DisableService"( root ) and traced the process and unticked 3 relevant processes ( lucky guess ? ) and my wakelock is solved .Battery usage much better etc
BOC3 is just as good and stable as my previous v4.4.4 and BOB4...!!
So sometimes dirty flash works ok and sometimes flashing,then an factory reset..etc etc does not help.!
good luck
Click to expand...
Click to collapse
IS there a ROOT for BOC3 then? I'd love to root it and find the culprit of the constant wakelock....
BNerd89 said:
IS there a ROOT for BOC3 then? I'd love to root it and find the culprit of the constant wakelock....
Click to expand...
Click to collapse
hi ,
i used the same CFauto root + CWM recovery , i used for Android v 4.4.4 ,..BOB4 and again on BOC3..
no problems for me(however, i did see some members saying they are
struggling to root and some members have no problems at all ? )
i had no problems rooting ..N910F SNAP ,rooted and custom recovery
good luck
willcor said:
hi ,
i used the same CFauto root + CWM recovery , i used for Android v 4.4.4 ,..BOB4 and again on BOC3..
no problems for me(however, i did see some members saying they are
struggling to root and some members have no problems at all ? )
i had no problems rooting ..N910F SNAP ,rooted and custom recovery
good luck
Click to expand...
Click to collapse
Do you possibly have any links to the CFauto root and CWM please?
BNerd89 said:
Do you possibly have any links to the CFauto root and CWM please?
Click to expand...
Click to collapse
hi ,
i had both on my laptop since i got my Note 4 N910f in oct 2014 (?)
had Note for a few hours and rooted...........and still .
i have only "quickly " check " this link ..see @ chainfire post #3..( sorry )
http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
Just make sure you download correct version !
Cwm recovery i used .... N910F vers 6.0.5.1 (1022)( see snip )
i have'nt correct link ..sorry
good luck
Have this issue myself with a N910F on 5.0.1 BOC3 (N910FXXU1BOC3 - CSC TDP). Without much Screen on time i get about 50% battery usage after 9h (usually when I get home from the office). It's not bad, but I would still wonder what the battery life would be like if I did not have the device constantly awake.
I would not want to root the device in order to avoid tripping the KNOX counter.
Is there any way to find and remove the wakelock culprit without rooting the device ?
I updated to 5.0.1 BOC3 from 4.4.4 ANK4 from Odin, wiping the device before and after.
Any ideas on how to proceed without tripping KNOX ?
I had the same problem and I fixed it when I disabled google backup from settings...
Maybe you could try this!
talexop said:
I had the same problem and I fixed it when I disabled google backup from settings...
Maybe you could try this!
Click to expand...
Click to collapse
Thanks for the reply, but wanted to know what are you reffering to as google backup. Are you talking about the google sync for contacts, gmail, calendar, drive etc ?
Because on the device i have 2 google accounts that have gmail sync and another google account with gmail, contacts, drive and calendar.
I have disabled google+ photo backup.
lolozaur said:
Thanks for the reply, but wanted to know what are you reffering to as google backup. Are you talking about the google sync for contacts, gmail, calendar, drive etc ?
Because on the device i have 2 google accounts that have gmail sync and another google account with gmail, contacts, drive and calendar.
I have disabled google+ photo backup.
Click to expand...
Click to collapse
There is a menu backup inside settings. Where it syncs wifi passwords etc with Google... I do not know how it is called in English because I use it with Greek names... But I think you can find it easily..
lolozaur said:
Thanks for the reply, but wanted to know what are you reffering to as google backup. Are you talking about the google sync for contacts, gmail, calendar, drive etc ?
Because on the device i have 2 google accounts that have gmail sync and another google account with gmail, contacts, drive and calendar.
I have disabled google+ photo backup.
Click to expand...
Click to collapse
There is a menu "backup and reset" inside settings. Where it syncs wifi passwords etc with Google...
Seems that the wakelock issue is a thing of luck.
I have disabled some more sync options and additional stuff like Multi Window and On-Body Detection SmartLock but i had the same issue with the phone being constantly awake.
Every time i disabled a new feature, did a phone restart. What i noticed is that sometimes after the restart, the wakelock problem goes away, sometime the phone is still constantly awake. So from my point of view, without rooting the Note 4, i can say it's pure luck after a phone restart.
I'm loving that now i see 23% battery consumption after 12h with an estimated of 2 Days left - without power saver. It sure beats the 50% consumption after 8h with 8h left. But i still have to admin, with a constant wakelock on the device, the resolution of the screen, the battery life is .. WOW
lolozaur said:
Seems that the wakelock issue is a thing of luck.
I have disabled some more sync options and additional stuff like Multi Window and On-Body Detection SmartLock but i had the same issue with the phone being constantly awake.
Every time i disabled a new feature, did a phone restart. What i noticed is that sometimes after the restart, the wakelock problem goes away, sometime the phone is still constantly awake. So from my point of view, without rooting the Note 4, i can say it's pure luck after a phone restart.
I'm loving that now i see 23% battery consumption after 12h with an estimated of 2 Days left - without power saver. It sure beats the 50% consumption after 8h with 8h left. But i still have to admin, with a constant wakelock on the device, the resolution of the screen, the battery life is .. WOW
Click to expand...
Click to collapse
Signing out of Google in the settings page then rebooting and signing back in stops the device being always awake. However, it seems Google Services is very buggy and for me the wake happens again after a few days randomly.
Happens with 5.1.1 too. Not rooted
Hi all,
I'm running the official 6.0 ROM from this thread and the latest baseband/modem/bootloader from this thread. The ROM is working smoothly apart from 1 crucial issue: whenever the devices goes into deep sleep it reboots itself.
- This doesn't happen when the screen is on or the device is otherwise active (e.g. it didn't reboot when I was moving data off of it to a PC)
- This doesn't happen when the SIM is locked / when the device does a reboot and I don't touch it (e.g. it reboots when I go to sleep and it will be up and running the next morning - battery log shows it has been on without interruptions throughout the night)
Obviously a quite frustrating issue and I don't know where the problem lies. Any help or ideas much appreciated.
1. Backup what you want to save.
2. Wipe /system and /data
3. Start from scratch
Use the phone without installing any apps. If it works then the rom is fine. Then try installingen the apps you want to use and keep testing.
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...
My S5 doesn't enter deep sleep after having used mobile hotspot. There's no wakelock though when it occurs, the cpu simply stays awake all the time. Only a full reboot fixes the problem
Already tried:
Toggling airplane mode on and off
Closing every open app
Flashing a new baseband
What I won't try
Factory reset
Reflashing the entire firmware through Odin
Anyone else had the same problem? I only have xposed, greenify, amplify, some apps frozen and a bunch of other stuff with zero problems apart this hotspot thing.
Bump
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 ?