I've had this problem with 2 different roms now (PureNexus, Chroma) on a few kernels (stock, ElementalX) so I'm not sure whats causing it but I need a fix. In a call, many times the screen just stops responding. Sometimes I can turn the screen on/off using power button and its fixed. Other times nothing works and I have to do a hard reboot by holding down power key since nothing else works on screen.
This is on latest version of the rom/kernels. Any ideas?
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Only when in contact with ears?
akholicc said:
When you say its stops responding, do you mean it goes dark and nothing displays on screen? Or that its on with everything displaying but tapping it does nothing?
Click to expand...
Click to collapse
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
ECrispy said:
Its on, touch doesn't do anything. The phone is working since volume keys bring up the UI but you can't do anything. Also proximity sensor works, it turns on/off as I bring near ear. I don't have a screen protector.
Click to expand...
Click to collapse
I'm having a similar issue from the last month.. I'm on DP5
when i get a call most times the screen is off.
To answer the call i've to put on the screen, unlock the phone and then go to the heads up notification and choose answer there..
waiting for nougat final hoping it'll fix this.
Tried fiddling around with notifications importance setting.. it helped a little but then there was the annoying heads up showing along with the regular incoming call screen.
Sometimes (very rarely, has happened twice) the screen just remains black and will only work normally after a reboot.
Anybody have any suggestions?
I was having similar issues, also on the Developer Preview and I ended up noticing that the phone app was blocked from showing any notifications despite the fact that I never set it that way. I would hear the call ringing but would never see the screen to answer. Just changed that setting and everything was back to normal. Perhaps something is causing the phone app to fail to show notifications for you as well.
Related
I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks
Legaleye3000 said:
I thought the screen shuts off when you're in the middle of a call (proximity sensor?). On the iPhone, when you're in the middle of the call, it shuts the screen off when its by your face just so you don't hit anything like mute, etc...
Any way to get around this? Thanks
Click to expand...
Click to collapse
Mine shuts off the screen when your face is close to it.
Settings -> Call Settings, do you have Keep screen awake checked?
I don't see that option. Settings, then call settings... I see voicemail, call forwarding... That's pretty much it. Running Stock 2.1
Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.
bluehaze said:
Mine has done this a couple times now,i'll be talking to someone and all of a sudden start hearing beeps as if hitting the numbers on the keypad. First time it happened I thought it was the person on the other end but it happened again last night and I looked at the phone after I got off the call and it had #2* or something like that in the dialer so something is definitely weird here.
Click to expand...
Click to collapse
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.
Maybe you have a really skinny head that's not passing the sensor?
nmesisca said:
are you using a screen protector/skin/case ... anything?
mine has never given a problem.
so far.
Click to expand...
Click to collapse
Nope, I imagine this will happen to everyone at some point though. It doesn't happen very often, it just out of the blue will happen one day. I guess the more you talk on the phone the more likely you will be to eventually experience it Maybe it has something to do with enabling the keypad? As that is what I did last night to punch in an extension.
This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.
bofslime said:
This problem happened with my gf, when she had a droid. For some reason while she was talking on the phone the screen wouldn't always stay off and she would bump the on screen buttons with her cheek and end up usually trying to add a new caller to the call, thus muting whom she was talking to. She also had a lot of problems with the Capacitive touch screens, it wouldn't register half the time where she touched.
I've never had this happen to me, I doubt it actually will. It must be something related to how we hold our phones, and where it lines up to peoples differently shaped heads.
Click to expand...
Click to collapse
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.
I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.
Legaleye3000 said:
I'm not using a case or anything. It NEVER happened to me with the iPhone, but it happens quite often with the Nexus One. VERY annoying... It should be like the iPhone, where when its by your face, it shuts off the screen AND disable the touch buttons below the screen.
I think its the touch buttons causing the problem... Because my screen does turn off when its by my face.
Click to expand...
Click to collapse
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.
krohnjw said:
This is the behavior I experience with my nexus one (stock and custom roms). As soon as I place it near my face the proximity sensor turns off the screen.
The capacitive buttons below the screen are disabled when the screen turns off for me as well. I just called in to voice mail and hit every one while the screen was off due to the proximity sensor, not a single response from any button or the screen and no change in call status when I moved the phone away and the screen came back on.
Click to expand...
Click to collapse
Yea it's some kind of fluke, It happens so randomly I am thinking it might be something to do with the internet connection like checking mail or maybe the GPS doing something that wakes up the buttons while the proximity sensor keeps the screen off because everything will be fine then all of a sudden it happens while the screen is still blacked out.
Sounds like a factory reset might fix this issue... definitely not normal behavior.
I think this is happening to a bunch of people. I don't think a factory reset would help. I think its a bug...
uansari1 said:
Sounds like a factory reset might fix this issue... definitely not normal behavior.
Click to expand...
Click to collapse
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.
bluehaze said:
Never happened to me in 2-3 years with the Iphone. To act like it is happening because we are holding the phone wrong is a bit absurd, I mean it's not exactly a complicated process I will try and figure out what's happening, haven't paid much attention to it yet because I figured it was a fluke but it happened twice now and is happening to other people.
One thing I noticed last night was the phone screen was still blacked out while the beeps happened so it's not a sensor thing the screen is actually blacking out it's just being activated again by something that happens after it's off I assume.
Click to expand...
Click to collapse
Are you accidentally hitting the volume buttons on the side of the phone? It sounds like you might be turning the in call volume down, thus leading to it being muted.
^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.
Legaleye3000 said:
^^ No... My face actually hits the mute button. I then have to click the mute button with my finger once i realize the person can't hear me and then they start hearing me again after I click it.
It happens with other buttons on the screen too.
Click to expand...
Click to collapse
Figured I would ask... I sell cell phones, and I get about 1 person a day in that has muted their in call volum by accidently hitting the volume toggle button without knowing it... all different phones (BB's are the worst!).
Anyways, my proxy sensor works perfect! I even just tested it a bit, and it senses a single finger tip starting about 1" away from the screen anywhere along the top of the screen... worked on both the left and right side and everywhere in between just fine.
I use my phone a lot at work in call (calling in to CS, calling the manager, etc) and have not had a single proxy sensor issue in the week I have had my phone.
bluehaze said:
No it's not a normal behaviour you are correct however it's not anything a factory reset is going to fix either. It's some kind of software bug that once enough people experience it will get sorted, just a matter of time before enough people start complaining to bring it to attention of Google or HTC.
Click to expand...
Click to collapse
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.
bofslime said:
May not be normal, but its not a bug that seems to be effecting all phones. Same thing that not everyone is experiencing random touch events, 2g/3g toggling, or dust/dogfooding. To say every phone has this problem because you do is simply short sighted.
Click to expand...
Click to collapse
LOL shortsighted eh? It's a bug it will happen to more and more people eventually and you will see, i'm sure it will happen to you eventually as well. Only thing shortsighted is your reply.
Good day to you sir.
Hi, I have a huge problem. Every time I make a call, preferably my voicemail, it asks me to press a number in the keypad.
Okay, that's fine. But the only problem is the screen blacks out immediately when the call is made and I cannot choose any of the options. I'm still in the call, although it will repeat the options for about a minute and just end the call.
I can't end the call manually or use the keypad. Tried pressing the lock button, the search, the menu, and Back button. Nothing seems to work.
Is there anything I can do about this? Because this is really becoming a hinderance.
Hi the proximity sensor should brighten the display up the moment you take it away from your ear, if it dosent prpbably there is a problem with it and you need to check it out with either the provider or HTC if you can.
normally to end call you click on the notification on top of the phone.
It is kinda annoying there is no physical button to end calls but i guess thats touchscreens for you
Probabily you use one case
that cover the proximty sensor
I don't use any case or screen protiction... maybe I should to replace it...Thanks..
dr.alkaiser said:
I don't use any case or screen protiction... maybe I should to replace it...Thanks..
Click to expand...
Click to collapse
if so, you should replace it ... sorry mate
dr.alkaiser said:
Hi, I have a huge problem. Every time I make a call, preferably my voicemail, it asks me to press a number in the keypad.
Okay, that's fine. But the only problem is the screen blacks out immediately when the call is made and I cannot choose any of the options. I'm still in the call, although it will repeat the options for about a minute and just end the call.
I can't end the call manually or use the keypad. Tried pressing the lock button, the search, the menu, and Back button. Nothing seems to work.
Is there anything I can do about this? Because this is really becoming a hinderance.
Click to expand...
Click to collapse
I had the same problem. Hard reset solved it. Also solved a problem I had connecting with intermittent connections to Wifi. I think a bum app may have caused the problems.
Starting to happen again, not like last time though. Now it's intermitent and seem to recover when the other end hangs up. May try to get a replacement phone this time.
From what I've seen around the internet this is an OS issue... And it happens to me intermittently as well, though my lock button brightens the display... It seems to have something to do with the screen timeout and the lock screen enabling itself...
Mine had the same issue.
I would pull it away from my face, nothing.
Laid it down flat, nothing
Occasionally it would flash.
I had to return it, no problems since.
The sensor must have been loose and slid behind the open area of the glass.
If you can still, get a replacement
My replacement is in the mail. I have found that if I shake or tap the phone it will flicker and come back during a call. I think the sensor is faulty.
There seem to be several proximity sensor threads but I've done a search and have not found anyone that is having this same problem.
When I make a phone call, my screen turns off right away. I can only get it to come on by pressing the power button or tilting the phone so that a bright light or glare is on the proximity sensor or light sensor. This is a pain. I use my power button to end calls but I have to disable that option. Otherwise, any time I need to use touch tones for an in-call menu, I hang up or spend a minute tilting my phone or holding it up to a light bulb. I know there are workarounds that I could be using but I am wondering if my proximity sensor or light sensor is malfunctioning or if it is a software issue.
Also, when using the visual voice mail app, my screen goes black but not off. I can still see the status bar. It happens as soon as I tap the play button and works just fine after my voice mail stops. This is likely unrelated but I can't be sure.
Thanks in advance to anyone that helps!
Running stock and unrooted with no physical damage or obstruction of sensors. I have tried a factory reset... twice.
I'm having a weird issue with mine as well. Mine is a little different though. If I need to make a call that requires to enter # prompts and as soon as I move the phone away from my face the keypad will start beeping on the other end so the prompts will always get invalid responses. While on the phone and I move the phone away from my face for any reason, the person on the other end will hear the beeping.
mokash34 said:
There seem to be several proximity sensor threads but I've done a search and have not found anyone that is having this same problem.
When I make a phone call, my screen turns off right away. I can only get it to come on by pressing the power button or tilting the phone so that a bright light or glare is on the proximity sensor or light sensor. This is a pain. I use my power button to end calls but I have to disable that option. Otherwise, any time I need to use touch tones for an in-call menu, I hang up or spend a minute tilting my phone or holding it up to a light bulb. I know there are workarounds that I could be using but I am wondering if my proximity sensor or light sensor is malfunctioning or if it is a software issue.
Also, when using the visual voice mail app, my screen goes black but not off. I can still see the status bar. It happens as soon as I tap the play button and works just fine after my voice mail stops. This is likely unrelated but I can't be sure.
Thanks in advance to anyone that helps!
Running stock and unrooted with no physical damage or obstruction of sensors. I have tried a factory reset... twice.
Click to expand...
Click to collapse
It sounds like your issue is hardware related. Take it to a sprint repair store and have it exchanged.
mrwicked said:
I'm having a weird issue with mine as well. Mine is a little different though. If I need to make a call that requires to enter # prompts and as soon as I move the phone away from my face the keypad will start beeping on the other end so the prompts will always get invalid responses. While on the phone and I move the phone away from my face for any reason, the person on the other end will hear the beeping.
Click to expand...
Click to collapse
You issue also sounds hardware related. The touchscreen sounds like it is going out. It might be the dialer app but I doubt it. Speaking from experience of course.
I went to Sprint store yesterday and they gave me a replacement for mine.
insuusvenerati said:
It sounds like your issue is hardware related. Take it to a sprint repair store and have it exchanged.
You issue also sounds hardware related. The touchscreen sounds like it is going out. It might be the dialer app but I doubt it. Speaking from experience of course.
Click to expand...
Click to collapse
Thanks I will head to a store and follow up here for anyone else. Thanks again.
I would check the sensor settings and play around before trying the store. But if that doesnt work it prob is hardware issues
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
JimSmith94 said:
Since updating to marshmallow, my longer notification sounds, especially Calendar Snooze, are cut off.
I read somewhere about an app setting to allow it to turn the screen on as a fix. I did that but now I can't remember what app I made the change in or where I read that suggestion. I thought it might have been Light Flow, but I can't find it in there.
Now my power button fails to wake up the screen the majority of the time. Sometimes the lock screen will flash for a fraction of a second and go black again. Usually it takes 6-10 tries before the screen finally stays on so I can use my phone.
Since the wake up problem started when I tried to fix the notification sound, I'm pretty sure they're related. Any ideas?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
if youre using lightflow id suggest wiping the data in it and resetting your notification settings. it does tend to override the system so i can see that screwing with the duration of the notification, and starting fresh usually solves most problems
i have mine set to wake the screen for SMS but not MMS. it creates similar problems with the screen
Thanks for the info. I tried just toggling the screen on settings on and back off for all of the Light Flow apps, and it seems to have fixed my screen turn on problem, at least for now.
Sent from my Nexus 6 using Tapatalk
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
A.Ahmed79 said:
I'm having the same notification sound cut short problem, I have a nexus 7 wifi 2013 model running Mohamed rom v2.1
Whenever anyone calls me on google hangouts, the ring only lasts for a second before its cut off, this doesn't happen if the front cover is open, it happens only when its closed.
I didn't have this problem on kitkat, but on MM this problem started from day 1.
I don't see any light flow option anywhere.
Any suggestions to fix this will be very appreciated.
Thanks.
Click to expand...
Click to collapse
LightFlow fixed my screen problems, but it was just a coincidence that I installed Marshmallow and my sounds got cut off around the same time. I'm still looking for a solution to that issue. Similar to you, if my screen is on, the notification sounds work correctly. If the screen is off, they get cut off.
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
I would say it's a warranty job, just tried turning my brightness to zero and you can still see the screen.
I did have a similar problem on an old note that had root and custom rom though but I had somehow set the volume rocker to control brightness and it had lowered itself to minimum in my pocket
KEVIN88GT said:
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
Click to expand...
Click to collapse
Try pressing and holding Volume down and power button for 5 to 7 seconds to force power off, then try to boot to download mode Volume Down + Bixby + Power button and see if the download mode screen shows......if not then probably a bad screen.
Sent from my God Mode 8
Tried it......nothing.....warranty job it is.... Bummed to have some refurnished phone in exchange for a Brand new 900 dollar phone just a few months back?
KEVIN88GT said:
Tried it......nothing.....warranty job it is.... Bummed to have some refurnished phone in exchange for a Brand new 900 dollar phone just a few months back?
Click to expand...
Click to collapse
Yeah that sucks, i can imagine..... i too hate the idea of refurbished units being swapped for warranty....bs, should be brand new unit!
Sent from my God Mode 8
so I had it replaced under warranty through T mobile. Refurb phone will come in today. One quesion. Should I let the Tmobile techs do the data/settings transfer from old phone to new one or just do everything myself from scratch (which will obviously take longer).
This happened to my phone twice for the past month or so. (both in Nougat and Oreo - Non rooted) Black screen but phone seems to be responding -- I can receive calls and notifications etc -- And force reboot doesn't fix it. I've also tried drainging the phone when it first happened to me but doesn't work. HOWEVER, it gets okay so randomly. Like I just left it for couple of hours and it just worked when I hit the power button.
I did tried bringing the device to Samsung but what they did is to just manually upgrade/reset the software in their end which I could have done in my part but I just let them do it. They told me to come back if it happens again which is kinda BS.
I can conveniently say this is a Hardware issue. I will wait for it to happen again on my phone and request for a replacement. Phone is 4 months old when it first happened.
I have the same issue with blank screen but phone is working.
It started couple of weeks after i dropped my phone on the ground. There is black dot on my screen and broken glass but phone was working ok and was still pretty usable. But then it started:
Display works fine but when i switch display of, lock the phone or display switched because of its timer it didn come switch on... But phone works, i can use it with blank (black) screen.
I had to do force restart so the display will turn on with samsung logo and booting screen, and keep on till another switch of.
I was trying every setting (but no hard reset) and then i found a little hack:
When you turn on the "Always On Display" (AOD) function you can let the screen switch off or do it manually, wait for 1-2 sec and always on display will come up to the screen. Then when you press home button or lock button screen will swtich on normally. YOu can type pin and use phone witch screen working. But when you try to unlock from "AOD" with your finger or your eyes it unlock but with screen black.
So i was using it like this. everytime you need to wait second untill AOD comes up, but it was working fine.
Problem nu 2 is that now it stop working, AOD is working but when i want to switch screen on from AOD it shows black screen and phone is working on blind.
So everytime after my screen goes black or to AOD i have to unlock the phone blindly and "Force restart" it and have to keep waiting until boot, and then have to never let phone to screen of.
Its not usuable.
¨
Now what do you think? Is it hardware problem or software problem? Because screen is working but randomly. The black dot of dead pixels on the screen is getting slightly bigger in time (about 1 year) but its like 1.5cm round. Maybe this cause the problem? And why hack with AOD was working for half a year and then stoped working? There wasnt any updates right before, but i tried to install some apps (non display related) so ill try to uninstall them.
Hawe you got any idea if i can repair it on my own even if i loose the waterproofability?
Or can it be replaced for free if i have a warranty? (I dont have insurance)
Thanks for your tips guys.
Reprocrastinator said:
I have the same issue with blank screen but phone is working.
It started couple of weeks after i dropped my phone on the ground. There is black dot on my screen and broken glass but phone was working ok and was still pretty usable. But then it started:
Display works fine but when i switch display of, lock the phone or display switched because of its timer it didn come switch on... But phone works, i can use it with blank (black) screen.
I had to do force restart so the display will turn on with samsung logo and booting screen, and keep on till another switch of.
I was trying every setting (but no hard reset) and then i found a little hack:
When you turn on the "Always On Display" (AOD) function you can let the screen switch off or do it manually, wait for 1-2 sec and always on display will come up to the screen. Then when you press home button or lock button screen will swtich on normally. YOu can type pin and use phone witch screen working. But when you try to unlock from "AOD" with your finger or your eyes it unlock but with screen black.
So i was using it like this. everytime you need to wait second untill AOD comes up, but it was working fine.
Problem nu 2 is that now it stop working, AOD is working but when i want to switch screen on from AOD it shows black screen and phone is working on blind.
So everytime after my screen goes black or to AOD i have to unlock the phone blindly and "Force restart" it and have to keep waiting until boot, and then have to never let phone to screen of.
Its not usuable.
¨
Now what do you think? Is it hardware problem or software problem? Because screen is working but randomly. The black dot of dead pixels on the screen is getting slightly bigger in time (about 1 year) but its like 1.5cm round. Maybe this cause the problem? And why hack with AOD was working for half a year and then stoped working? There wasnt any updates right before, but i tried to install some apps (non display related) so ill try to uninstall them.
Hawe you got any idea if i can repair it on my own even if i loose the waterproofability?
Or can it be replaced for free if i have a warranty? (I dont have insurance)
Thanks for your tips guys.
Click to expand...
Click to collapse
If you're under warranty it will likely be a free repair, unless they find other damage. Like moisture damage.
As far as fixing it yourself, it's just about as cheap to have Samsung do it than it is to buy the parts yourself. It's $229 for Samsung to do it, and you'll maintain the water resistance rating.
same has happened to me
KEVIN88GT said:
Non rooted, T mobile branded 3 month old note 8. No water damange, no drops etc.
Using chrome one miniute, set the phone down to watch a movie on my tablet, picked up the phone to check messages and boom. Screen is off. The phone works, I can even answer calls because I know where the answer button is on the screen, haptic feedback works, all indicator lights work. The phone screen remains off.
Tried a soft reset (tried hard reset too the best I could being I cant see the screen) and the phone seems to reset based on the vibration and indicator light patters but the screen remains off. It's as if a physical connection between the screen and the brains of the phone has been severed. Literaraly the weirdest thing that has happened to me in a decade of Android phone ownership.
Googled all the black screen issues with these phones and most of them are resolved with just a soft reset... some said that the phone is in it's lowest dimmed state and go to a dark room and i'll see it faintly and then can increase brightness... no luck...
Has anyone experienced this?
Click to expand...
Click to collapse
This has just happened to my note 8 too. I was about to update it and had started it. set my phone down and picked it up and phone screen is black but can hear the haptic feedback.
I can only see the lock screen and the notifications. Everytime I try to unlock my phone I only get to see a glimpse of the notescreen and then the screen turns black. Even when I try to go to camera through the lock screen the screen goes black too. When I charge my phone it heats up so I haven't really charged it as well. Has this also happened to anyone? It seems as if the phone's sensitivity still works in all places but when I unlock it the screen just goes black.
I also have problem of freezings and always rebooting. Tried soft and hard resets/factory reset. Still same problem. This phone has hardware issue. Do not buy.
I realize this thread is quite old but I have this exact same issue now. I have managed to discover some other information by playing around with various settings which are noted below. To begin with, I was able to used the AOD hack posted above for a while but it no longer works. The only way I can get my screen to come back is with a soft reset - but as soon as the screen times out or i turn it off, it goes black, with or without AOD enable. All the on screen buttons still work as well as the haptic feedback - I just can't see anything.
Now on to what I have found:
One thing I have found is if I turn off adaptive screen brightness and crank the brightness slider to the right, when it goes black I can faintly see some of the buttons - enough that I can turn the phone off or restart it from the power menu (If I switch the default setting to night that also helps to see the buttons a bit better). Also, if I enable night mode I can also see the brightness slider faintly but when I slide it left, it just makes the screen completely black and when I slide it right, it only returns it to the very faint brightness level.
So at this point I am stuck. To summarize the issue:
1. When the screen either times out or turns off, it is still "alive" but goes black. It will not return to normal brightness.
2. Turning off adaptive brightness and cranking brightness slider to right allows you to see faint buttons after screen times out but won't return to normal brightness.
3. Enabling night mode helps to see the faint buttons, in particular the brightness slider a bit better. However the screen still cannot return to normal brightness.
4. The only way to get the screen back to full brightness (albeit temporarily until the next timeout) is to turn off the phone or reset from the power menu; or soft reset holding volume down + power simultaneously.
Hopefully someone else has figured out a way to recover this. I am on Android 9 with Samsung UI 1.0
Phone is completely stock, never rooted and completely out of warranty.