Database Users

[Q] Phone does not sleep after Reboot?

hello, I've been trying to find out what causes this... but I've pretty much hit a dead end.
on occasional reboots, the phone reaches the homescreen and does NOT sleep.
it will stay there until I open any app
at that point
- it will vibrate
- activate wifi
- activate power-savings
- activate color setting (Professional Photo)
when the phone reboots properly (and sleeps after reaching the homescreen)
it will automatically
- vibrate
- activate wifi (I reboot with WiFi ON)
- activate power-savings
- activate color settings (Professional Photo)
hope someone can chime in on this

wilflare said:
hello, I've been trying to find out what causes this... but I've pretty much hit a dead end.
on occasional reboots, the phone reaches the homescreen and does NOT sleep.
it will stay there until I open any app
at that point
- it will vibrate
- activate wifi
- activate power-savings
- activate color setting (Professional Photo)
when the phone reboots properly (and sleeps after reaching the homescreen)
it will automatically
- vibrate
- activate wifi (I reboot with WiFi ON)
- activate power-savings
- activate color settings (Professional Photo)
hope someone can chime in on this
Click to expand...
Click to collapse
have you tried sleepwake detector from google play

jaythenut said:
have you tried sleepwake detector from google play
Click to expand...
Click to collapse
i installed both Wakelock Detector and BBS but both don't help in this regard

anyone?
wonder if it's due to MJ7

downloaded Catlog...
but lol it doesn't make sense to me at all

May sound silly, but have you tried a factory reset and wiped cache ? - Nine out of ten times it generally fixes most things on the Note. I know it's a pain but give it a shot and see.
Or just wipe the cache, and remove your google account and readd see if it makes any difference.
We are learning more and more each day that it is always something so trivial with this damn phone :|

radicalisto said:
May sound silly, but have you tried a factory reset and wiped cache ? - Nine out of ten times it generally fixes most things on the Note. I know it's a pain but give it a shot and see.
Or just wipe the cache, and remove your google account and readd see if it makes any difference.
We are learning more and more each day that it is always something so trivial with this damn phone :|
Click to expand...
Click to collapse
was really hoping to avoid the factory reset and cache wipe route... but guess I have to do it after my exams :/

catlog seems to point to a number of errors..
google made no sense of them
wonder if I should set the Security from Enforcing to Permissive

Note 4 Power Saving automatically turns off

Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath

corpuscallosum said:
Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath
Click to expand...
Click to collapse
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.

Tavok said:
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.
Click to expand...
Click to collapse
Thanks. Yeah I am trying to avoid factory reset because can't go thorugh the process of installing apps, setting up all the various accounts etc especially since there is no built in fully restorable backup feature. Family man with kids and have enough IT stuff to do at work.
I'm on stock/non-rooted device also. And this will be my last Samung device, if not the last Android!

I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)

Tavok said:
I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)
Click to expand...
Click to collapse
Thanks Tavok. I did download Helium and wanted to test it out, however my phone is now staying in Power Saving mode since a few days! I have done nothing new, didn't uninstall any app or change any settings as such for it to work. This is bugging me because I want to know what fixed it so that I can re-apply the fix again if need be.
I've also read that some people are complaining about Note 4 getting stuck in Power Saving mode and I hope this is not the case with mine, now that it seems to work as expected.
I will update this thread once I check it out further.

I found out how this power saving mode gets turned off. It is the Location settings. If location is off, the power saving mode stays on (this is what it was set to hence I didn't see the issue happening). But when I changed it back to High accuracy, I started to notice the power saving getting turned off from time to time when using certain applications that require Location accuracy.
This is a bug since the MM update!!
Any ideas how to use Location accuracy and still retain Power saving mode?

I did a factory reset and the issue persisted! I tried various location settings(of the 3 choices) asks none of them helped. When set to any one of them power saving automatically turns off after a while I.e. when location needs to be detected. The only workaround us to turnoff location altogether but that messes with the auto sync of accounts! Grrrrrrrr

I verified with Samsung Tech Support that Location and Power Saving are incompatible on the Galaxy Note 4, even with the latest Android version available for the device (6.0.1) . In other words, Turning on Location while Power Saving is active will disable Power Saving after a short period. Fortunately, the problem is fixed on later devices.

Navigation bar buttons as text

So this is what happened yesterday.
The battery was almost empty. I could get the message that the phone will shut down automatically. That empty. Then I wanted charge the phone, but when i putted the usb into the phone ,the phone shut down immediately.
After charging it up for a while I started the phone up again and since then the navigation bar buttons are showing as text in stead of circle and square. See the enclosed picture. I have no idea how to get it back. See the enclosed picture for the screenshot. It seems like the pictures are removed or something.
My phone is not rooted. Any ideas how to check what happened and get it back to circle and square without root?

M.Ozturk said:
After charging it up for a while I started the phone up again and since then the navigation bar buttons are showing as text in stead of circle and square....
...Any ideas how to check what happened and get it back to circle and square without root?
Click to expand...
Click to collapse
That is very strange indeed.
Have you tried changing / experimenting with the settings for this feature?
Try it in Settings > Smart assistance > Navigation bar
Also, completely shutdown & reboot the phone a few times (not restarts).
If nothing helps, you may need to try a hard reset - but only do as a last resort & after a thorough backup.

GaT7 said:
That is very strange indeed.
Have you tried changing / experimenting with the settings for this feature?
Try it in Settings > Smart assistance > Navigation bar
Also, completely shutdown & reboot the phone a few times (not restarts).
If nothing helps, you may need to try a hard reset - but only do as a last resort & after a thorough backup.
Click to expand...
Click to collapse
Solved!
Changing the buttons in smart assistance > navitation bar didn't help. The buttons change from position but the text stays.
Reboot or shutdown and reboot didnt help either, BUT doing this after cleaning the cached data solved the problem.
Thanks! Now I don't have to hard reset.

hi..try to change the teme....you have installed a complete theme..and this cud changed the nav bar

8.1 screen unlock delay

Hi there, so I updated my ph-1 to the latest Oreo 8.1 earlier this morning and have been experiencing significant delays when unlocking my screen. Sometimes the phone did not respond at all and the screen just stayed black. I had to restart the phone in such cases. Help! I seem to be the only essential phone user in entire Sydney

If you're using immersive mode, that might be the issue. Try disabling that, and see if the issue persists.

I'm experiencing the same. Setting immersive mode to None does help a bit, but it's still not as snappy as before.
And after all the same settings worked perfectly on the 8.1 beta.
Tried to go back, but on official 8.1 the recovery mode only says "no command"....

I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.

And specialty if you use immersive mode with sytem UI make it very long delay

winstonxyz said:
I am experiencing the same issue too. It doesn't have the delay problem right after reboot, it seems like it delays the unlocking when the phone has been in idle for a while.
Click to expand...
Click to collapse
Same issue here. Sometimes takes so long to unlock that I am unable to answer a phone call that comes in before it goes to Voicemail. Usually happens when the phone has been idle for a while.
Update:
Did the dreaded FDR (factory data reset). Installed the "Tiles" app from plasystore and ran the noted adb command to allow immersive mode, tile display, and enable write secure settings permissions. I chose the action to hide the navigation bar within the Tiles app. I ignored the setting to stop on sleep so the app keeps running when the phone screen goes off. In testing it for about an hour the phone seems to unlock without any issue for now and without any delay. I also made phone calls while the phone screen was off and I was able to answer the call easily. So far so good using the Tiles app!

sounds like the expanded desktop Oreo issue. There's a Xposed module DeepScreen Oreo for it.

Notifications not being pushed since update to Android Pie

Is anyone else having this problem? A few apps – Gmail and WhatsApp that I've noticed so far – will occasionally *fetch* notifications, but otherwise I don't receive notifications until I open the relevant application. I've tried going into settings --> developer options --> standby apps, but plenty of apps are set to 'active' and it doesn't make any difference. I don't particularly want to do a factory reset, so does anyone have any alternative suggestions?

Adaptive battery - off.
Battery optimization - off on every affected apps.
Maybe look at data saving mode or something.
Check notification importance on those apps.
Clear cache (or even data if it's not causing too much trouble) from affected apps.
If those 5 options do not help, factory reset is probably the way. Or maybe I missed something.

Benderisas said:
Adaptive battery - off.
Battery optimization - off on every affected apps.
Maybe look at data saving mode or something.
Check notification importance on those apps.
Clear cache (or even data if it's not causing too much trouble) from affected apps.
If those 5 options do not help, factory reset is probably the way. Or maybe I missed something.
Click to expand...
Click to collapse
Yeah, I'm pretty sure I've tried all those things Adaptive battery keeps switching itself back on, but even so, I think I managed to keep it deactivated for long enough to establish it wasn't making any difference. Very irritating. Thanks for the reply though!