Hello!
I wonder if anyone had this issue. Yesterday suddenly the backlight of my XT894 started to act weirdly. When i pressed the unlock button, the screen would go very bright and then shut off after 2-3 seconds, but I still could swype the unlock screen and hear the unlock click, even with the dark screen. With a little bit of external light I could see the image was there, but the backlight of the screen was not on. I went on to the power shortcuts and disabled the Automatic brightness control, and as soon as I did that the display turned on, very dimly but it turned on. When I set the brightness control to maximum, it still is very low. If i set the brightness to minimum, its almost impossible to see anything. In display settings, the automatic brightness is unchecked and the brightness fader is set to maximum.
I started suspecting the light sensor, so I went ahead and downlaoded a sensor tester app, and the light sensor appeared to be reporting the light levels correctly - low readings in the dark, and much higher readings in direct light.
Is my phone backlight dying? Any idea if this might be due to defective mainboard, or the display itself?
I already did some repairing on the phone myself, so I am comfortable dissassembling it and changing parts. Few months ago I changed the main board because my old one had a broken usb connector, and it worked fine until now.
Any advice would be greatly appreciated!
Thank you in advance!
Best regards,
Konstantin
If I remember right, by default, the maximum auto-brightness is still lower than actual maximum, so if the screen can barely be seen at manual max, it makes sense that the screen is pretty much unviewable with auto on.
Idea:
If you have it installed, boot into Safestrap and see if your brightness is normal.
If not, pull up the diagnostic menu (hold Vol - while powering on iirc, might be Vol - and +).
If your brightness is normal in those, it's probably something gone wonky in Android. If not, your screen backlight might be going and needs replaced. I don't think there's anything on the mainboard that would cause it, aside from the circuitry actually supplying power to the backlight...
Screen replacement actually isn't terrible for the D4, if it comes to that, since it's not fused to the glass (like certain single-piece phones for example...*sideways glance at the S3*).
Hello!
Thank you for your reply!
Effectively something is very wrong with the device. Today I woke up to find it completely unresponsive, had to turn it off by holding the power button for a while. When it turned on again, the whole screen was white with glitchy color lines since the very reboot, and nothing else happens, couldnt even turn it off without unscrewing the battery.
I will put the old main board to see if the other one died.
Thank you again!
Best regards,
Konstantin
Related
I am having a funny issue when the standby screen is on. Example: The device is off and I turn the device on via the power button. I have the device set-up to display my 'Owner Information'. When the 'Owner Information' is displayed the right side 1/4 of the screen is much darker than the left - still viewable. When the unit comes out of standby mode and the unit is up and running everything is fine. Screen is very bright and viewable. I tried to do a soft reset to see if this solved the problem but no such luck. I even went as far as to do a hard reset and still the same result. Is anyone else having this same issue? It is possible this is the correct function of the standby screen but I don't recall the standby screen being this dark in the past.
Thoughts???
My only thought is that it may be the LED backlites, one or more may have a different (lower) light output at the lower settings. I've seen this with LEDs where a string of them will look uniform and fine at full but quite different at lower levels.
Just a thought.
I have been noticing that my auto brightness doesn't work like it did when I first got my phone a few months ago.
Back then it seemed like it changed brightness after a few seconds when it should.
Nowadays it doesn't seem to do that anymore.
Now if I hold my phone close to a bright light, hit the power button and unlock the phone, the screen is very bright, as it should. When I hold my phone in a dark place, it doesn't adjust the brightness. It keeps being very bright.
BUT, if I hold my phone in a dark place and hit the power button and unlock the phone, it's dark, but when I move my phone to a brighter location it does make the screen brighter.
I first thought this had to do with CM, but now on stock froyo it does the same thing.
Is this normal, and am I just mistaken? And should the phone adjust the brightness when I hold my thumb on the sensor thats just right under the power button on the front of the phone (I expect the screen to be less bright)? Because it doesn't do that.
Thanks in advance.
No it's not normal, mine reacts to changes in ambient light in a second or 2 (FRF50), just like yours used to.
When I cover the light sensor with my thumb, the screen dims right down.
Thanks for your reply.
Is there anything I can do to check why this doesn't happen on my phone?
Can I perform a check on the status of my sensor, on it's behavior?
And are there any known reasons why this could happen?
Thanks in advance.
This exact issue is happening with me ever since I updated to 2.2. It worked perfectly before but now I notice that once the screen adjusts to maximum brightness in a well lit area, it never dims....don't know what the problem is. But I hope there is a solution.
Good to hear I'm not the only one with problem, that gives me hope this might be a software issue rather than a non-working sensor.
Rusty! said:
No it's not normal, mine reacts to changes in ambient light in a second or 2 (FRF50), just like yours used to.
When I cover the light sensor with my thumb, the screen dims right down.
Click to expand...
Click to collapse
Actually I may have to take this back, in retrospect, the dimming actually could have been the screen timing out.
When covering the sensor with my thumb and not having the screen set to 15secs, it doesn't dim until I lock/unlock the screen.
Reading on another forum this is by design rather than a flaw, as people complained the screen would fade in and out in certain light conditions... now it can't.
Ah, okay. Good to hear.
Thanks again, Rusty.
froyo seems to fix the autobrightness for me, at least now i can see the screen brightness is changing according to lighting condition, previously i don't notice it (using cyan ROM prior to froyo).
Hiya folks. Running CM10.1 stable on my targa (aka Droid Bionic). It was beautiful except for lack of nav dock support, a problematic Google Now (different problem, with workaround), and this particular problem, which I hope someone know what I am talking about...
When a call comes in and I answer by the slider, the screen goes black, whether or not I held the phone up to my head.
I cannot turn the screen back on. None of the buttons seem to do anything, though backlight for the 4 hard buttons does turn on indicating that some command was received by the touchscreen. Not even the power button will bring the screen back during the call.
If the other party hangs up, the phone goes back to normal.
With screen off, I can't hang up.
I can hang up if my Bluetooth headset was connected and I hang up with that.
I've searched all over and this issue seem to be a pretty popular issue last December across all CM 10 builds. However, I don't know if this was ever resolved for this build.
I can't find an option in the ROM to just flat "turn off face proximity detection" either. Or in any way to "tweak" it.
CPU-Z says my proximity sensor is working, so I guess it's just not calibrated properly for the dialer?
Can we get a "special hidden tweaker" much like the light sensor tweak for the auto-brightness levels?
Figured it out. It wasn't CM. It was Screebl and the stupid orientation sensor, and how the Launcher is fixed to portrait mode.
I think I had my phone laid down and it's at a diagonal so it's in landscape mode, and the phone's fine with that when it's just showing contacts. Screebl kicks in and determines that landscape, phone orientation says stay on, so screen stayed on. It was set to turn off the screen IMMEDIATELY when the orientation goes out of "viewing range". (Saving batteries, ya know).
When the call was answered, Screebl should have turned itself off (i.e. ignore input while call is in progress). But it didn't. The "answer the phone" screen flipped the display back to portrait mode. The phone, still laid flat, in "landscape", is now "out of viewing range", and Screebl turned off the screen.
Strange interaction among the various apps, yes.
I'm still trying to figure out how to make my Bionic, with extended battery last the whole day. Juicedefender Ultimate somehow just keeps turning the screen back on every X seconds (taking root control for SOMETHING) and Wakelock detector says the phone is not going into enough deep sleep (kinda like me, hahaha)
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
I don't have the flickering when not on auto and lowest setting.
However some apps can dimm the screen while loading.
On the TF700 the stock browser did that when loading a page but on the TF701 the brightness doesn't do that.
You have an ambient light sensor built into the device. It adjusts the brightness based on the lighting in your environment. It can't be turned off either.
Sent from my Transformer Infinity TF701T using Tapatalk HD
xRevilatioNx said:
You have an ambient light sensor built into the device. It adjusts the brightness based on the lighting in your environment. It can't be turned off either.
Click to expand...
Click to collapse
It can't be turned off? So when you turn on automatic brightness it just changes the brightness more drastically? This doesn't sound right.
Based on the other poster's response, I think I need to return this unit. The screen dimming/brightening happens to often and randomly to be part of my apps and I even noticed, in some apps, that just touching the screen causes a brightness change.
Even if this is by design, it is far too distracting.
dbozam said:
It can't be turned off? So when you turn on automatic brightness it just changes the brightness more drastically? This doesn't sound right.
Based on the other poster's response, I think I need to return this unit. The screen dimming/brightening happens to often and randomly to be part of my apps and I even noticed, in some apps, that just touching the screen causes a brightness change.
Even if this is by design, it is far too distracting.
Click to expand...
Click to collapse
Read it and weep my friend. Proof is in the pudding..
Sent from my Transformer Infinity TF701T using Tapatalk HD
dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
My 701 is doing this as well. Turned off auto brightness, turned off power saver, rebooted. When it comes back up the device acts like auto brightness is on, with screen brightness fluctuaating randomly. Turning power saver on and off again seems to solve it, but that behavior is very annoying - it's why I turn auto brightness off in the first place.
US SKU running 4.3 installed via ota, no root or unlock or anything - straight stock. Its also my second device, my original had a bad cable and wouldn't charge. Serial number ends in 072259.
Sent from my K00C using Tapatalk 4
Aaroneious said:
My 701 is doing this as well. Turned off auto brightness, turned off power saver, rebooted. When it comes back up the device acts like auto brightness is on, with screen brightness fluctuaating randomly. Turning power saver on and off again seems to solve it, but that behavior is very annoying - it's why I turn auto brightness off in the first place.
US SKU running 4.3 installed via ota, no root or unlock or anything - straight stock. Its also my second device, my original had a bad cable and wouldn't charge. Serial number ends in 072259.
Sent from my K00C using Tapatalk 4
Click to expand...
Click to collapse
I also tried turning power saver mode on and off and for me it seemed to improve the situation but not eliminate it. I am going to return the tablet and wait for the nexus 10.
Ugh, mine has been doing this, too. Can't believe there isn't a setting somewhere...
Mine is doing the same thing... glad that it's not just me, but this flickering is very annoying
Driving me nuts
I'm having the same problem and it's driving me nuts!
I'm quite convinced it's a software "feature" but currently there seems to be no way to turn it off?
It's one of those "Adjust brightness of the screen based on content" or "Changing LCD refresh rate and colors for power saving" but sadly it does it the wrong way around (This has been going on for a while now, manufacturers don't really get it). When there is a lot of bright content the brightness will rise and when there is mostly a dark screen it will fall.
Of course, this should happen exactly the other way around. When there is a lot of bright/white on my screen it should lower and when there is mostly black it should become brighter thus giving you more contrast but keeping the overall lux that comes off your screen the same...... My Intel graphics notebook does this too and it's very irritating. There they do it by manipulating the LCD screen and lowering the refresh rate and other tricks to save battery. First thing I turned off.
However way it goes though, you should be able to turn it off!
Quindor said:
I'm having the same problem and it's driving me nuts!
I'm quite convinced it's a software "feature" but currently there seems to be no way to turn it off?
It's one of those "Adjust brightness of the screen based on content" or "Changing LCD refresh rate and colors for power saving" but sadly it does it the wrong way around (This has been going on for a while now, manufacturers don't really get it). When there is a lot of bright content the brightness will rise and when there is mostly a dark screen it will fall.
Of course, this should happen exactly the other way around. When there is a lot of bright/white on my screen it should lower and when there is mostly black it should become brighter thus giving you more contrast but keeping the overall lux that comes off your screen the same...... My Intel graphics notebook does this too and it's very irritating. There they do it by manipulating the LCD screen and lowering the refresh rate and other tricks to save battery. First thing I turned off.
However way it goes though, you should be able to turn it off!
Click to expand...
Click to collapse
I'm having the same issue. I think it's the smart dimmer option Asus have used before but they forgot to include it in the Asus customised options. I'll have a dig through the ROM to see where it is stored.
I'm having this problem as well.
I have my brightness set to about 80%, Auto-Brightness Off, Power Save Off.
It is very annoying when reading magazines that have a lot of white background. My screen will be stable for minutes then, often on a touch, will change the screen brightness, seemingly by 5-20%.
I was just getting ready to return it, and thought I would check here to see of anyone else has this problem. Has any actually called Asus with this complaint? I would be interested to know if they see this as a hardware defect, software bug, or working as designed.
PS - I just placed a technical support request about this on the Asus Website. Here is my problem description:
Even with automatic brightness & power saving turned off, the brightness of the screen will change over time, often seemingly in response to a touch. (Reading Mode is Off as well.)
The period between changes can vary from several minutes to 30 seconds. It happens both while docked and undocked. It happens with apps and just at the launcher.
The amount of brightness change is 5-20% and it will often seem to step through some values before it stops at a particular one.
Given how fantastic looking the screen is, this unwanted fluctuation is particularly annoying.
I also own a TF201 and have not experienced this problem on that product.
Click to expand...
Click to collapse
sschlosnagle said:
I'm having this problem as well.
I have my brightness set to about 80%, Auto-Brightness Off, Power Save Off.
It is very annoying when reading magazines that have a lot of white background. My screen will be stable for minutes then, often on a touch, will change the screen brightness, seemingly by 5-20%.
I was just getting ready to return it, and thought I would check here to see of anyone else has this problem. Has any actually called Asus with this complaint? I would be interested to know if they see this as a hardware defect, software bug, or working as designed.
PS - I just placed a technical support request about this on the Asus Website. Here is my problem description:
Click to expand...
Click to collapse
I have this issue too but not a real biggie as the connection problems between dock and tablet.
Same problem!
dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
Thank you very much for creating this topic, because I was worried for my tablet too!
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
Snah001 said:
I have this issue too but not a real biggie as the connection problems between dock and tablet.
Click to expand...
Click to collapse
I heared a lot of people say I about this, but happily I seem to don't have it or I don't detect it. What is this dock problem about?
I suspect this is the same "smart dimming" feature that the 700 had.
improvius said:
I suspect this is the same "smart dimming" feature that the 700 had.
Click to expand...
Click to collapse
Yep me too and as soon as I root I'm going to see if the same fix will turn it off
There seems to be no way to disable this. Some believe it's the light sensor, but I've taped over mine with black electrical tape and tested and I don't see any difference in the behavior. Check our my Youtube video if you are a user who doesn't see the issue (look for threads in this same XDA forum).
I've finally been able to get someone at Asus to look into this and it's been sent to TW for review. I haven't heard anything back yet. I strongly recommend that other people who are annoyed by this (I find it tremendously distracting) to search on "asus escalation" which will bring up a special mailbox. Here is the link (although I do not know if the link will work for you). This should get looked at by someone with at least some ability beyond reading a script. If enough people do this, I think that they will fix it. Since you can temporarily override it by toggling smart saver on/off, it has to be fixable by software.
http://www.service.asus.com/#!escalation-mailbox/c1scx
derekk1 said:
There seems to be no way to disable this. Some believe it's the light sensor, but I've taped over mine with black electrical tape and tested and I don't see any difference in the behavior. Check our my Youtube video if you are a user who doesn't see the issue (look for threads in this same XDA forum).
I've finally been able to get someone at Asus to look into this and it's been sent to TW for review. I haven't heard anything back yet. I strongly recommend that other people who are annoyed by this (I find it tremendously distracting) to search on "asus escalation" which will bring up a special mailbox. Here is the link (although I do not know if the link will work for you). This should get looked at by someone with at least some ability beyond reading a script. If enough people do this, I think that they will fix it. Since you can temporarily override it by toggling smart saver on/off, it has to be fixable by software.
http://www.service.asus.com/#!escalation-mailbox/c1scx
Click to expand...
Click to collapse
I returned my tf701, waited for cyber Monday, and bought the Samsung note 2014 since the nexus 10 2 is so elusive. I put in an escalation request anyway and included a link to this thread in my complaint.
improvius said:
I suspect this is the same "smart dimming" feature that the 700 had.
Click to expand...
Click to collapse
I also saw this issue on my TF701. This seems a "feature" of Tegra SoC
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.