Related
Since a little while I have an issue where if I leave my phone locked for a while (idle), and I try to unlock it, the screen doesn't show anything.
The device does still unlock but no image is displayed, the only way to fix it temporarily is to hold the power button and reboot the device.
I'm running Rooted Marshmallow atm, but the issue occurs with any ROM I have tried so far.
Does anyone know how to fix this, because it is really annoying.
Greetings
Does anyone have an idea??
I get this actually. The 'fix' is to swipe down from the top when the phone is unlocked but the screen is black.
jonnythan said:
I get this actually. The 'fix' is to swipe down from the top when the phone is unlocked but the screen is black.
Click to expand...
Click to collapse
Thanks for your response, do you have any idea of what the cause is of this annoyance?
Sent from my XT1092 using Tapatalk
Xtremelyevil said:
Thanks for your response, do you have any idea of what the cause is of this annoyance?
Sent from my XT1092 using Tapatalk
Click to expand...
Click to collapse
Not a clue. Bug in the display driver or something. Who knows.
jonnythan said:
Not a clue. Bug in the display driver or something. Who knows.
Click to expand...
Click to collapse
I just encountered the issue again, but swiping down doesn't seem to resolve the problem.
jonnythan said:
Not a clue. Bug in the display driver or something. Who knows.
Click to expand...
Click to collapse
Could it be due to Doze?
Everything ok with my device, never had this problem. I'm running official stock 6.0 non-rooted. Try to deactivate Moto Display and see if the problem continues to happen.
theoblackhawk said:
Everything ok with my device, never had this problem. I'm running official stock 6.0 non-rooted. Try to deactivate Moto Display and see if the problem continues to happen.
Click to expand...
Click to collapse
I've "disabled" Doze for 2 days now, and the issue hasn't been back since then.
So might be a doze related bug.
Still not certain
Xtremelyevil said:
I've "disabled" Doze for 2 days now, and the issue hasn't been back since then.
So might be a doze related bug.
Still not certain
Click to expand...
Click to collapse
this also happens on my XT1093 5.1 stock...I can twist the camera on hit the home circle and that brings back the display....
Ever since the last July security update, when I try to use any number of apps from capital one too smart select with my s pen, I get it asking permissionas then coming up saying I need to turn screen overlay off. This is an os permission that many programs use. Unless I turn it off on every app, I cannot give the current apps permissions. However summarily turning them off screws up those apps.
Is Is anyone else having this problem?
udrunner said:
Ever since the last July security update, when I try to use any number of apps from capital one too smart select with my s pen, I get it asking permissionas then coming up saying I need to turn screen overlay off. This is an os permission that many programs use. Unless I turn it off on every app, I cannot give the current apps permissions. However summarily turning them off screws up those apps.
Is Is anyone else having this problem?
Click to expand...
Click to collapse
I'm glad to hear that I'm not alone. I've been really struggling lately. Seems like quite a few of the new apps trigger that "Overlay" problem. I'm not sure how/what to do. Please help
I've been having the same exact issues. It's been driving me nuts. The only thing I can think of is it must have something to do with the latest security patch we got.
Hopefully they fix it, soon!! How do we let them know?
From my non-rooted AT&T Galaxy Note 5 (N920A)
udrunner said:
Ever since the last July security update, when I try to use any number of apps from capital one too smart select with my s pen, I get it asking permissionas then coming up saying I need to turn screen overlay off. This is an os permission that many programs use. Unless I turn it off on every app, I cannot give the current apps permissions. However summarily turning them off screws up those apps.
Is Is anyone else having this problem?
Click to expand...
Click to collapse
I just turned off all the apps which using screen overlay. After I installed the new app successfully, I turned them all back on. That's annoying, but working.
twemco said:
I just turned off all the apps which using screen overlay. After I installed the new app successfully, I turned them all back on. That's annoying, but working.
Click to expand...
Click to collapse
From my experience, that only works until you open/download another app... Then you start all over
I am also having this problem, I am glad I wasn't alone, I was beginning to think it was just me!
I've found that restarting the device will resolve this issue MOST of the time. It worked for me twice yesterday...
But it's such a tedious workaround!
From my non-rooted AT&T Galaxy Note 5 (N920A)
Go in Dr. Ketan rom & check in few days back post. Someone has posted a zip file. Just flash it & its perfect. Plz take a backup before flashing the zip.
SM-N920I powered by M12 PRO.
maheshhtc said:
Go in Dr. Ketan rom & check in few days back post. Someone has posted a zip file. Just flash it & its perfect. Plz take a backup before flashing the zip.
SM-N920I powered by M12 PRO.
Click to expand...
Click to collapse
I wish that it was going to be that easy for me... I'm using a non-rooted (un-rootable) AT&T Galaxy Note 5 SM-NM920A.
Hi,
My Note 9 screen has recently started randomly coming on. Its not being touched or being moved just on my desk, im not receiving any notifications it just comes on and a few second slater goes back off.
has anyone else be getting this? im unsure what could be causing it.
Thanks
My Note 8 used to do that. I think it's the Aod That's doing it.
Sent from my SM-N960U using Tapatalk
Jammol said:
My Note 8 used to do that. I think it's the Aod That's doing it.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
i thought that so i turned AOD off but it was still doing it randomly
factory reset and try again. dont install anything.
bober10113 said:
factory reset and try again. dont install anything.
Click to expand...
Click to collapse
What about booting to safe mode 1st?
KOLIOSIS said:
What about booting to safe mode 1st?
Click to expand...
Click to collapse
well if it fixes it in safe mode, what will it accomplish? cant stay in safe mode all your life. if factory reset dosent fix it then he should put it back in the box and return it.
bober10113 said:
well if it fixes it in safe mode, what will it accomplish? cant stay in safe mode all your life. if factory reset dosent fix it then put it back in the box and return it.
Click to expand...
Click to collapse
I'm saying boot into safe mode,then,keep track of which apps you enable,perhaps one of the user apps is causing it.
Naturally,if you're in safe mode & it persists w/o re-enabling any user installed apps,then you have a defective phone.
KOLIOSIS said:
I'm saying boot into safe mode,then,keep track of which apps you enable,perhaps one of the user apps is causing it.
Naturally,if you're in safe mode & it persists w/o re-enabling any user installed apps,then you have a defective phone.
Click to expand...
Click to collapse
not aware that safe mode allowed you to cherry pick which apps you wanted to be enabled or not. from my experiance, all user apps were disabled and that was it. What is doable in regular mode is disable all your apps and do the same thing enable or disable. but to me it would be much more conveniant to wipe everything. then if the issue is gone, reinstall app by app till you hit the culprit. but anyways to each his own.
bober10113 said:
not aware that safe mode allowed you to cherry pick which apps you wanted to be enabled or not. from my experiance, all user apps were disabled and that was it. What is doable in regular mode is disable all your apps and do the same thing enable or disable. but to me it would be much more conveniant to wipe everything. then if the issue is gone, reinstall app by app till you hit the culprit. but anyways to each his own.
Click to expand...
Click to collapse
Exactly,to each their own,but,factory reset seems like the last resort/nuclear option... why go that route 1st?
KOLIOSIS said:
Exactly,to each their own,but,factory reset seems like the last resort/nuclear option... why go that route 1st?
Click to expand...
Click to collapse
because the feature he has issues with is a system level feature and i would doubt an app could affect it. and if a system setting was changed then wiping is a sure way to get that reverted.
just my 2 cents
bober10113 said:
because the feature he has issues with is a system level feature and i would doubt an app could affect it. and if a system setting was changed then wiping is a sure way to get that reverted.
just my 2 cents
Click to expand...
Click to collapse
Package Disabler Pro is a user installed app & it has profound effects on system apps functions (depending on what the user disables) ,so,that's where I'm coming from.
Using safe mode is a natural step in troubleshooting before resorting to a factory reset,regardless of what is assumed to be the obvious next step.
KOLIOSIS said:
Package Disabler Pro is a user installed app & it has profound effects on system apps functions (depending on what the user disables) ,so,that's where I'm coming from.
Using safe mode is a natural step in troubleshooting before resorting to a factory reset,regardless of what is assumed to be the obvious next step.
Click to expand...
Click to collapse
point taken.
but it would also be obvious to the said user that if he or she would have disabled stuff in the manner you explained, they would not post here for help as it would have been obviously caused by his or hers own doing.
anyways, we're not getting anywhere here.
have a good day.
bober10113 said:
point taken.
but it would also be obvious to the said user that if he or she would have disabled stuff in the manner you explained, they would not post here for help as it would have been obviously caused by his or hers own doing.
anyways, we're not getting anywhere here.
have a good day.
Click to expand...
Click to collapse
I hear ya,it's all good,the OP has input from several users/options on how to troubleshoot,that's what's ultimately important.
You have a good day as well,see ya 'round the forum. :good:
Thanks for all the info i'll have a play around with whats been said see how it goes
thanks.
I am having the exact same issue this morning with my Note 9. I restored from my Note 8 backup, so I do have a lot of programs that have migrated over. I'll have to sort through them and see what I come up with. Hopefully, the OP figures it out and let's us know what they did.
xdarktekx said:
I am having the exact same issue this morning with my Note 9. I restored from my Note 8 backup, so I do have a lot of programs that have migrated over. I'll have to sort through them and see what I come up with. Hopefully, the OP figures it out and let's us know what they did.
Click to expand...
Click to collapse
This happens to me when I restore something and it's trying to connect to an old bluetooth device like my car. The car sees the phone as the same but the phone doesn't see the car as a paired devices so the screen comes on everytime it tries to pair
---------- Post added at 04:56 PM ---------- Previous post was at 04:55 PM ----------
billbob87 said:
Hi,
My Note 9 screen has recently started randomly coming on. Its not being touched or being moved just on my desk, im not receiving any notifications it just comes on and a few second slater goes back off.
has anyone else be getting this? im unsure what could be causing it.
Thanks
Click to expand...
Click to collapse
If you restored from a backup make sure you dont have any old bluetooth devices trying to connect to your phone
Hello,
So since I installed the November patch few days ago, the AOD stopped working properly. It doesn't recognize any touch and lost the double-tap functionality, except when using the S Pen, then it works like a charm. I have no idea why this is happening but it's frustrating. Anyone else experiencing such issue?
Vortelf said:
Hello,
So since I installed the November patch few days ago, the AOD stopped working properly. It doesn't recognize any touch and lost the double-tap functionality, except when using the S Pen, then it works like a charm. I have no idea why this is happening but it's frustrating. Anyone else experiencing such issue?
Click to expand...
Click to collapse
What's your region? Notification popped up today (am in the UK) to update November security patch (see image) but I haven't. Just wondering whether I should cos this seems to be an issue.. especially when software updates start to crash your device ?...or make it "malfunction"
william-johnson said:
What's your region? Notification popped up today (am in the UK) to update November security patch (see image) but I haven't. Just wondering whether I should cos this seems to be an issue.. especially when software updates start to crash your device ?...or make it "malfunction"
Click to expand...
Click to collapse
Eastern Europe. And cannot tell you to either do or do not update. The only thing I got form Samsung Support was to do a factory reset which was a ridiculous proposal.
Vortelf said:
Eastern Europe. And cannot tell you to either do or do not update. The only thing I got form Samsung Support was to do a factory reset which was a ridiculous proposal.
Click to expand...
Click to collapse
I took the risk, updated today and it's been fine. Really crazy that Samsung suggests a hard reset. Hope u manage to sort it out.
Vortelf said:
Hello,
So since I installed the November patch few days ago, the AOD stopped working properly. It doesn't recognize any touch and lost the double-tap functionality, except when using the S Pen, then it works like a charm. I have no idea why this is happening but it's frustrating. Anyone else experiencing such issue?
Click to expand...
Click to collapse
On November security patch(build ARK3) as well on the Exynos, with no such issues.
Erase cache in recovery and re-check, well and good it it fixes, if not do a "reset settings", if still fails, do a "factory data reset" as you have no other option.
Hi guys,
Strange one this is, most of my recent apps (except the odd 4 or 5) started auto closing themselves *overnight* after the Pie update, everything is fine during day time.
This is still true after disabling Auto Optimization and Auto Restart, and locking all recent apps.
Needless to say, never had a problem in Android 8.0.
Cheers.
Same with me also
I can only imagine this would be the same for everybody -- or am I missing a magic switch somewhere??
this is normal. you have to turn off sleeping apps, or remove from that list as well as adaptive batery which is new to pie.
The more I read about this pie, the less I want it.
Fixed mine.
Setting->Device Care->Battery-> 3dot menu settings
Turn off Put unused apps to sleep.
Thanks. Will try myself.
Sadly still the same for me...
Opened apps auto closed overnight, note just overnight, day time all is fine.
Sadly still the same for me...
Apps auto closed overnight, daytime is fine.
It's the device optimisation set to run automatically every night? It is on mine
Sent from my SM-T820 using Tapatalk
pizza_pablo said:
The more I read about this pie, the less I want it.
Click to expand...
Click to collapse
Ha trust me it's so childish, and so dull.. Everything is like iphoney kind of feel! Big childish icons! They have simplified it too much! it don’t feel good, it feels way to simplified plus they have removed so much it really sucks!
When you do get the update, let us know if you’re going to stick to it or not! As i went back to Oreo day 2 man Oreo is awesome!
device optimisation is off, so is auto restart.
is this normal behaviour for adaptive battery? in which case, it would be rather stupid design -- I want my apps (especially those locked) to stay on ready to be used anytime!
yzs1002 said:
Sadly still the same for me...
Opened apps auto closed overnight, note just overnight, day time all is fine.
Click to expand...
Click to collapse
See screenshots below,
Mine is set to default 0300, to close/optimize. I set it to off.
willcor said:
See screenshots below,
Mine is set to default 0300, to close/optimize. I set it to off.
Click to expand...
Click to collapse
thanks -- mine had always been off.
N1NJATH3ORY said:
When you do get the update, let us know if you’re going to stick to it or not! As i went back to Oreo day 2 man Oreo is awesome!
Click to expand...
Click to collapse
I don't even want to take the update.
What county and provider are you and how did you downgrade to Oreo?
pizza_pablo said:
I don't even want to take the update.
What county and provider are you and how did you downgrade to Oreo?
Click to expand...
Click to collapse
UK Purchased Note 9 direct from Samsung UK.. i used SAMFIRM.EXE and Odin3_v3.13.1_3B_PatcheD to downgrade to Oreo 8.1.l it's so easy to downgrade walk in the park easy
N1NJATH3ORY said:
UK Purchased Note 9 direct from Samsung UK.. i used SAMFIRM.EXE and Odin3_v3.13.1_3B_PatcheD to downgrade to Oreo 8.1.l it's so easy to downgrade walk in the park easy
Click to expand...
Click to collapse
Hopefully, I'm able to pull that off with this locked down Verizon Note 9, if the need arises.
How do you keep it from wanting to update to Pie?
pizza_pablo said:
Hopefully, I'm able to pull that off with this locked down Verizon Note 9, if the need arises.
How do you keep it from wanting to update to Pie?
Click to expand...
Click to collapse
Just disable auto updates from software updates menu! Also don't check for updates, as you will not be able to get rid of that annoying update notification, unless you factory reset it! It’s that simple!
pizza_pablo said:
Hopefully, I'm able to pull that off with this locked down Verizon Note 9, if the need arises.
How do you keep it from wanting to update to Pie?
Click to expand...
Click to collapse
Disable both Software Update .apks via ADB/AdHell3/Package Disabler app of your choice.
KOLIOSIS said:
Disable both Software Update .apks via ADB/AdHell3/Package Disabler app of your choice.
Click to expand...
Click to collapse
I've read a lot about those, in the other threads, but none seemed reliable any more.
Maybe I'll see if I can hold off the update with AUTO UPDATES turned off in DEFROST OPTIONS and if that doesn't work, downgrade back to Oreo and then adb/Package disable.