Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
typci said:
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
Click to expand...
Click to collapse
Turn OFF wifi when you're not using the phone. problem solved
If not work try this :
Goto CPU menu -> smartass v2 and make low and high cpu speed settings to 1 ghz.
This will also increase Battery life and must fix random rebooting.
Other way is clear caches and install rom again.
Loureiro:
I'll try turning off the wifi. It sounds like a highly likely solution since: 1) I've only seen my phone at home 2) I always turn wifi on at home.
Is there a specific reason why wifi is causing reboots? Maybe something I can find a fix for?
technogod:
Don't have custom kernal installed, so I can't alter the CPU parameters. Wanted to make sure the phone was stable at stock before changing the kernal.
Speaking of which, what's the most stable kernal for overclocking the 2.3 stock rom?
I'll try clearing the caches as well.
Thanks.
The wifi bug is known fault with the .35 kernel found in the official upgrade. hopefully it will be fixed next week fingers and toes crossed. I am not sure if any of the kernel dev's have found a fix yet.
Without cpu parameters, only way i am found that : clear three caches with clockwork and reinstall your rom. It's working on stock roms or custom roms. I think, this is not rom problem. There is different something. Cache clearing solves problem. Resetting problem started on my phone when i start to try other roms.
I am using miui 2.2.3 now and i will setup 2.2.10 version today. While using stock rom, i have some resetting problem. But now, my phone working without self-reset.
Hi everyone
I have an international version of Note 3. The problem I'm facing is, after rooting my phone and installing Lidroid Custom ROM, the battery on my phone started draining badly. To get rid of the problem I reinstalled Stock ROM on it and also unrooted the phone. But the problem is still there.
Even without using the phone, the percentage drainage is about 1% every 10-15mns. Have removed all third party application from the phone, but to no avail.
Can something be done about this? I'm at wits end and need a solution badly. Please respond ASAP.
Thanks in advance.
anirmj said:
Hi everyone
I have an international version of Note 3. The problem I'm facing is, after rooting my phone and installing Lidroid Custom ROM, the battery on my phone started draining badly. To get rid of the problem I reinstalled Stock ROM on it and also unrooted the phone. But the problem is still there.
Even without using the phone, the percentage drainage is about 1% every 10-15mns. Have removed all third party application from the phone, but to no avail.
Can something be done about this? I'm at wits end and need a solution badly. Please respond ASAP.
Thanks in advance.
Click to expand...
Click to collapse
Get wakelock detector from Google play see if it's a app draining the battery
Get into recovery mode and clean your cache, whatever bad bug went on with the custom ROM flash is still there. Once you clear it you should be OK.
Hello!
I've made everything possible, to reset my phone, i flashed a newly fresh Stock ROM with ODIN and deleted everything on my intern SD-Card. So actually it should be clean and fresh.
But my Wifi-Module still doesn't let my phone sleep. It wakelocks the whole phone to 95%!
I use Wakelock Detector, to see what's happend and I can see that wlan_rx_wake and wlan_wd_wake are the problem. When I shut wifi off, everything works fine and my battery doesn't drain so fast.
Can I replace the Wi-Fi-Module? Or do you know any solution?
Thanks,
Jan
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
[Q] "Dream Manager Service" keeps waking the screen up, how do I disable it?
I've looked for other posts on this issue, but none helped me very much. I have a Samsung S5 (international, sim-free), I recently flashed Phoenix Rom, version 6.3, build BOC7. Was on Omega Rom BOB7 previously. I'm also on BOB7 bootloader and modem. Don't know if it's relevant, but I'll mention it anyway. I don't have a PC, so it's difficult for me to use Odin, it's something I have to arrange days in advance. That's why I haven't updated bootloader or modem to BOC7 yet. And before anyone tells me to just go back to Omega Rom, Phoenix Rom is my absolute favourite Rom, it was my daily driver on KitKat, and I just discovered today that it had been updated to Lollipop, so I flashed it immediately.
Using Wakelock Detector immediately after booting, I find Android System, specifically "Dream Manager Service" the only thing which has woken the screen. So that seems to be the culprit, but I don't know how to kill it. It was never an issue before. Basic Daydreams (a Samsung process) is frozen via Titanium Backup. I don't use any other sort of daydream app or service.
It is clearly an issue with Phoenix Rom, but it didn't start until a few hours after I'd flashed it. So in the meantime something has happened, but I don't know what, and before I go through the hassle of reflashing it, I'd like to see how I could disable it. Things I've tried:
- Turning off ambient display - was not on when the problem started, I've tried turning it on and off, but doesn't help. I don't use it or want it, so I don't mind killing it somehow.
- Booting into safe mode. This helped, the problem did not appear when in safe mode. As far as I know though, it just doesn't allow "Dream Manager Service" to run. Not so helpful for finding out how to disable it.
- Revoking permission to "keep screen on" in App Ops for Android System. It seems to just ignore this, which seems to make the whole permission management thing a bit pointless.
When the screen does turn on, it looks different. The wallpaper is not displayed, and it's all in black and white.
Does anyone know why "Dream Manager Service" is doing this? And more importantly, how I can stop it? If you need any more information from me, just ask.
EDIT: Found reason: Ambient Display in Phoenix v6.3 was causing this bug, even after I turned it off. Downgraded back to 6.0, will skip 6.3 and wait for fix, hope it will be an option in the Aroma Installer next time.
Thank you! I found this information useful 2 years later in my Galaxy S7 running Ambasadii Nougat 7.0.