My current Dell Streak 5 dropped and the screen was cracked. I bought a new LCD screen from China. and replaced it today. But when I turn on the device, the screen backlight turns on, But the whole screen is Black...
I tried 3-4 times to re-plug the sockets and connectors. I believe I did all necessary things to solve this Black Screen problem out, but couldnt achieve.
Can anyone suggest me what to do? As I said,
when I turn the device on,
- button leds are lighted,
- backlight is lighted,
- but the LCD screen is black (no visualization)
Waiting for your suggestions...
Peace,
zedonetx said:
My current Dell Streak 5 dropped and the screen was cracked. I bought a new LCD screen from China. and replaced it today. But when I turn on the device, the screen backlight turns on, But the whole screen is Black...
I tried 3-4 times to re-plug the sockets and connectors. I believe I did all necessary things to solve this Black Screen problem out, but couldnt achieve.
Can anyone suggest me what to do? As I said,
when I turn the device on,
- button leds are lighted,
- backlight is lighted,
- but the LCD screen is black (no visualization)
Waiting for your suggestions...
Peace,
Click to expand...
Click to collapse
Sometimes the pins in the LCD socket can lead to this behaviour, are all pins in place?? If so, I would advice you to contact the seller to send a replacement.
I tried another screen from a friend of mine. It didn't work either. So obviously, the problem is on the phone board (black screen when power on the phone.)
Is it possible to change the board? Do you think it works?
sent from my LG-P895.
Changing the board will work, so long as the board hasn't been bricked or otherwise rendered non-functional.
After changing the board, imei number will change too. If so, is it possible to transfer the imei number too?
sent from my LG-P895.
In the US at least, changing the IMEI is illegal. I'm pretty sure other countries frown on the idea, since the IMEI is essentially the device's fingerprint. The Dell service code can't be changed either, but that's only because of a hardware limitation rather than legality.
Hey guys,
I am not sure if this is the right forum to ask, I am desperate and I need your help.
My navigation buttons started to push itself, so I disassembled my phone (gently of course)
I found out that the digitizer flat cable is torn like.. 3/4 of its width so that was probably the problem.
I ordered a new digitizer and it arrived yesterday, so I put everything together, started the phone and the LCD doesn't work.
When I start the phone it vibrates as usually, then the LCD screen turns on for couple of milliseconds so I can just barely see the HTC logo and then it turns black, the navigation buttons are lit and I've heard notifications after I let it run for 30 seconds.
What could be the problem? I checked multiple times if all the flat cables are plugged in correctly. It's weird that the LCD runs for couple of ms and then it turns black.
Thanks a lot for your answer,
Adam K.
How bright does the LCD get? It is possible the lighting element went bad.
It gets bright as usually, but just for half a second, then there's just black screen.
So some of you with white Z5 compact phones might have had this touch sceen bug with repetitive key presses and unstable touch screen behaviour bug which was previously "fixed" by a software upgrade:
http://www.xperiablog.net/2015/10/21/white-xperia-z5-compact-touch-screen-fix-arriving-next-week/
Lo and behold. This bug is back in MM, and there is another guy in the thread which I can see also have the bug come back
It is not always there, but sometimes its just there. I dont know what triggers it. A restart seems to help until it comes back again.
For those of you not familiar with this bug, it usually shows by repetitive touches, and highly unstable touch screen.
For example when i press the key "s", it usually put in "sssssss" like i have pushed that key 5-6 times.
Also the bugs shows, when for example you are scrolling in facebook/internet, it will not let you scroll. Whenever you touch the screen, it will enter, whereever you lay your finger on screen.
Lastly it also shows by the screen becoming completely unresponsive when you press anywhere.
I have clean installed MM and restored my apps via Sony Backup/restore app.
I am so pissed how a phone color (white) can somehow decide the behavior of the phone touch screen, and I believe sony is hiding something.
In the beginning I was thinking that maybe they made different builds for the different Z5 colors, so they might not have included the "newest" touch screen drivers for at launch time for the white version.
But the same bug appearing AGAIN in MM i have a very hard time understanding that should be the case that it was a software bug. I believe there are some hardware bug, they have somehow omitted by a software circumvention, and they forgot to add it to the white version for the MM launch.
Personally I have always had a problem with the "return" key when the phone is placed. Patch or not, this button works once out of 10.
For information, I just bought this phone. I also think there is a hardware problem. This is average for a manufacturer like Sony. I thought for a moment it back in service but when I see the number of dissatisfied with the service Sony in France, I preferred to keep my phone in the hope that a solution comes a day. We have the right to expect in my opinion ...
I did clean install via flastool also and i have/had this problem. Yesterday i did software repair via pc companion and restores apps after that and so far problem has not occured.
I also made a repair with PC Companion but nothing changed.
So there are other people here with this annoying problem.
You all have a white xperia yes?
This bug is so annoying I feel sometimes like tossing the phone into a wall.
If there was an alternative to this phone in this form factor and specs, I would have bought it yesterday.
But unfortunately there isn't
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
hipsterfont said:
It's a poor ground connection from the digitizer most likely. You can replicate this "bug" on any device with a bad USB charger. I had a charger that would cause my Nexus 7 to detect random touches.
The software fix was likely adjusting the voltage threshold for touch events to be considered actual presses. It was likely forgotten about when they updated and just needs to get readjusted again. Too bad we don't have the ability to adjust the threshold ourselves in developer options
That being said I have a white z5c and I've only had this "bug" happen once and I just chalked it up to me being plugged into the wall and didn't think much of it. I use my phone constantly too.
Click to expand...
Click to collapse
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
I also have Sony Z5 compact white version which had the touch problem from start. Now after the Marshmallow update its back. As said above, it could happen while browsing (or on home screen) e.g. Entering links instead of scolling i.e. It triggers multi click. In these situations all menu keys will also be none responsive. Its starts acting normal again after a quick push of the power button, i.e. puttning the screen to sleep.
As a former developer for mobile software, both for apps and the android platform, i thinking i would agree with the above conclusion that the problem is hardware based, and not due to a difference in the delivery software version, as i was hopping. So the question is; will this always be a problem for these versions of Z5c white, i.e. they are forgotten in new builds?
Unfortunately I'm having the same problem with my white z5 compact...
mcmanuf said:
Interesting theory. Do you think it is likely that this issue only occurs for one phone color (WHITE), and then only for some whites.
The assembly line for the phones should more or less be the same, no mater the color.
Click to expand...
Click to collapse
it happens that for different colors are used different materials.. probably white ones have different properties..
i can confirm that using bad cable/chargers this kind of bug happens with every device, with random touches and impossible scrolling.. if you have a well-known bad adapter and you note no differences with your white z5c, that's definitively the answer..
i think sony should recall all white z5cs and replace them with newer or different release
What revision of compact Z5 are you? Personally I have a revision 3 (that is written on the box).
I also had a touch of problem before moving to the latest version of Android (6).
My girlfriend also bought white Z5 Compact and funny thing... I put the Panzer Glass on the screen and guess what? Sometimes she can't turn off the alarm clock in the morning and sometimes navigation buttons are not responding. I tried then without the screen and it works without a problem. I am not sure if this is a problem with Panzer glass or sony's bug.
I have Z5 and have no problems, but mine is black edition
Mine is z5c white version as well. The bug started again on MM
And the bug quite annoying.
I bought it on updated lollipop.
And never had this problem before.
This plus Bluetooth is really making me hold off on not moving up from .200 lol
Argh - just saw the visual representation of this bug:
http://www.xperiablog.net/2015/10/06/xperia-z5-compact-owners-reporting-touch-screen-problems/
and it sounds A LOT like the one from the OnePlus One (driver & firmware issue)
easy blame: Synaptics - fix your ****
Anyway:
try enabling the double-tap-to-wake if it's not already enabled, lock the screen - give it some time to settle (~ 30 seconds),
wake it up (double-tap) - do some stuff - disable the double-tap-to-wake and lock the screen again.
Unlock it via power button and see if that improved the "situation".
Sony recommended a few times to boot into Safe Mode,
does this Mode exist on Android Marshmallow ?
Does it make any change ?
Had this in Nougat is there a fix?
It feels like a software problem! You can try to reinstall the system!
First consider whether it is a system problem. You can refresh the system to see if it is back to normal. If it still does not, then you may need to update a new LCD screen. You can go online to find the repaired video as a reference. The witrigs repair video is doing great, you can check it out!
Has anyone else faced with the issue of display not working properly in K20 Pro?
I started facing few problems from day 1, though the problems were minor like
.
[Problem 1] When using the phone with dark mode on or with absolute black background with 0-25% brightness the screen didnt respond well to on screen movements. Like when scrolling, the items on the screen produced a blue shadow on black backgrounds.
I thought this was due to Xiaomi's usage of cheap & low quality Super Amoled displays. Im not sure if it is as i thought it is or due to some other reasons.
[Problem 2] after 25-27 days of usage the ambient disolay started to switch of automatically after a few seconds of locking the screen. And when i tries to unlock the screen by fingerprint, te scanner didnt work. I had to push the lock button and then the screen switched on after 4-5 seconds of pressing the button(i was pressing the button only once and not holding it).
I still dont know why did this happen (I'll update soon)
[Problem 3] after 2-3 days of the problem 2 one fine morning my screen went dark.... Like completely blank, although i tried switching on and off multiple times but the screen didnt show a single hope to turn on.
So i took iit to the service centre and found out that there were many people with the same problem. Most of them being the first launch sale buyers(including me).
SERVICE CRNTRE told me that there was instructions from the comoany(Xiaomi) to collect all the Faulty screen K20 Pro's and provide a new sealed box within 1 week. Providing that there are no signs of external damage to the handset. Peoole will have to suubmit the box and its contents with the phone.
So Yaaay! For that but Naaay! For xiaomi for producing soo many faulty handsets out of the factory.
I'm writing this post as there are no posts regarding this issue on the internet and i was shocked when my phone went dark.
i’m facing problem 1 too
but no touch issue or burning for me
mine is China 6/128gb variant
1st batch
Hello XDA.
The screen on my LG G3 Verizon (vs985) has been acting weird and I really would like a second opinion about if I have a screen issue on my hands or if it is a motherboard problem. I included pictures below.
Screen responds to double-tap-to-wake, and buttons still work. I'm able to turn phone off by pressing power button (as long as it normally takes to display Power Menu), then tapping on where the Switch Off button ought to have been displayed. Apparently, motherboard sends stuff to screen, but screen unable to visibly display it.
I've been using motherboard since it was bought new 6 months ago so I really doubt it's the motherboard, but I could be wrong. Screen is over 4 years old. The best way would have been to try another trusted motherboard (if screen is still not normal, then it's DEFINITELY screen's fault). So in the absence of such a conclusive test, I would appreciate opinions.
Thanks.
Pictures (L-R): When booting (picture taken with flash), when booting (picture taken without flash), after booting into Android, phone charging with screen switched off.
SOLUTION: It turned out to be a screen problem (screen was replaced and voila!).