Symptoms of a dying screen or... ? - Moto G 2015 Q&A, Help & Troubleshooting

Phone was never dropped and the screen is in pristine condition besides these two "blobs" that appeared over time and seem to be getting more visible.
It's kinda hard to see them when capturing with another phone but to the naked eye they are noticeable especially on white background. I can't seem to come up what might cause this besides
A slowly dying screen
B expanding battery pushing from the inside ?
Stock 6.0 and Lineage Rom 7.1.2 same issue
https://imgur.com/a/1236OjD

B, may be the reason. Because when i press hard and hold the screen from outside same happen with me at the same place. Good thing is that it's gone when I left that.

I have the same issue. my battery had expanded and that caused the screen to bend and almost pop. I opened the phone and replaced the battery but I think the damage was done and its still there. not as much as before though.

Related

[Q] screen disaster - random tinting, solarization, turns upside down

sooo, yeah. my wife has the t959v. the screen cracked months ago, replaced it with one from ebay, works fine. a few weeks ago, it was involved in an accident and needed yet another screen replacement; ergo, back to ebay i go. installed the new screen yesterday, turn it on, all is well. for a bit.
now, the phone isn't currently, nor has it ever been rooted; pure stock tmo us 2.3.6. during boot, the splash screens and boot animation are gorgeous and perfect in appearance. the recovery menu is exactly as expected. android boots as you'd want it to, and then the display will do one of the following:
-work properly (rare)
-automatically turn off, capacitive buttons still lit, touchscreen unresponsive - turning it "off" darkens the cap buttons, turning it back on flashes the screen on for a half-second, then off, with cap buttons still lit (common)
-graphical corruption ("solarized" colors, completely wrong colors, pixel vomit in essence) (fairly common)
-screen tinting, blue most often, followed by pale yellow, then greenish, then red (almost constant)
-screen inversion - the display will show as rotated 180 degrees; grabbing a framecap in ddms shows it right way up. touches are also inverse; you have to touch where the onscreen element would be if it were displayed properly instead of where the element is; e.g. a button on lower-left will display in the upper right, upsidedown, but the screen registers the button when you touch the lower-left portion of the screen. (quasi common, equally infuriating and hilarious)
none of these problems will show up in a screenshot at all.
i can reliably reproduce any of the above by simply adjusting the screen brightness. this will, quite literally, cycle through every possible defective display mode randomly for a split-second before moving on to a different one as long as you move the brightness slider.
MOST of these issues are transient and are either fixed (temporarily) or replaced with a different listed issue if you lock/unlock the display. it feels like a hardware issue what with the solarizing and color horrors, but is acting like a software issue, considering that recovery and boot are perfect and have never displayed any of these issues. i tried gently flexing and stressing the case in areas that might be a weak connection point, but can't get it to bug out that way.
in no way am i suggesting that i didn't screw something royally in the reconstruction stage, but i tore down and rebuilt that phone 4 times with identical results, so i can guarantee it's not some loose ribbon connector or zif socket.
i beg of you, great minds of xda, what the balls did i muck up this time? any hope for a fix? are there different panels, drivers, something?
thanks in advance
OK, if your screenshots appear normal, then your phone appears to be working correctly!
or at least it thinks it is we can conclude that it isn't the rom, kernel, or anything that you can blame the phone for going screwy.
Try buying another screen??
The ribbon connector might be broken?
yeah, these were what i figured what my options were. it just seems odd that the boot process and recovery menus have error-free displays while only the full android os doesnt. oh well, i'll probably just have to make a stink about it on ebay or something.
thanks for reading
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
lumin30 said:
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
Click to expand...
Click to collapse
hell, warranty's void at this point anyway, right? may as well thanks much!
welp, all went well, screen was perfect through the whole heimdall/recovery process, but the problems still exist in the os c'est la vie. at least my wife's phone is finally rooted, i suppose. thanks anyway!
Have you tried opening it back up and reconnecting?
yup, 4 times, but i guess one more wont hurt
[edit]
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
zero01101 said:
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
Click to expand...
Click to collapse
That's interesting and could very well be a hardware problem with the screen. You wouldn't see that in recovery as the OS isn't loaded to mess with the brightness in that mode.
Does it do it on-demand if you mess with the brightness slider?
stephen_w said:
Does it do it on-demand if you mess with the brightness slider?
Click to expand...
Click to collapse
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
zero01101 said:
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
Click to expand...
Click to collapse
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
stephen_w said:
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
Click to expand...
Click to collapse
as fun as that sounds, unfortunately i bet i'll end up just getting my wife a used phone on ebay or somewhere similar and using this one as a development monkey. i was assuming that it wasn't something i could fix but hoping otherwise... yeah, that worked out
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
kristoper said:
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
Click to expand...
Click to collapse
nawp, nothing even close to a solution here i did end up buying my wife a whole new replacement phone and turned the broken one into my api10 development device. for what it's worth, yeah, autobrightness off does help a bit for when the phone is actively displaying content, but after you put it to sleep/screen off and try to turn it back on, it's a crapshoot. for a few horrifying hours, the screen was upsidedown even in recovery/boot animation and would NOT flip back to right-side-up until i ran the battery completely flat.
is no fun, 'tis truth. sorry for your troubles.

[Q] Screen Issue? (XT926)

I received my XT926 as a refurb and I have been experiencing a strange screen issue.
I will often have my phone on a dock, charging and sometimes I will notice the screen is black like it's off, but the touchscreen is responsive. Hitting the power button does nothing but it makes the sound as if I had locked the phone. Hitting the power button a second time will turn the screen on like normal operation.
Very rarely I have noticed the screen will turn off while I'm actually using the phone and it's a weird effect. The easiest way to describe it is that it looks like entire lines disappearing randomly over a period of 1-2 seconds, going from all visible, then to all black, kind of like slatted blinds being closed, but at random. After this, it displays the same symptoms as if I had found the screen off while in a dock/charging.
Now, I don't want to say it's related, but I first started experiencing this on the Stock KitKat update from Verizon. I am currently using Cyanogenmod 12 nightlies and I am experiencing the same issue. It seems to be happening with greater frequency.
I have also experienced the blue screen effect when certain animations/elements/apps are up on my screen, but I think they are unrelated.
Also, there is a faint discoloration bar about 2/5ths of an inch thick uniformly vertically from top to bottom of my phone on the righthand side (just under where the notification bar would be if turned horizontal).
I've tried to find more information about this but my search results have been relatively lackluster (90% of the results are trying to sell me the phone or specification pages)
So I'm breaking down and turning to here. Does anyone know what's going on here? My current theory is that my screen is going bad. I have no intention of replacing the screen on this phone (would rather just buy a new one), so any suggestions that don't involve physical hardware repairs would be appreciated.
I thought i was the only one experiencing it.
The screen turning off with a weird effect happens rarely but yeah it happens. And the blue screen effect, i noticed it only happens when im on the youtube app when the video stops working because of my connectivity issues.
Im not rooted nor is my bootloader unlocked. On the latest system version. Sounds like a software problem but hey im no expert.
kayonesoft said:
I received my XT926 as a refurb and I have been experiencing a strange screen issue.
I will often have my phone on a dock, charging and sometimes I will notice the screen is black like it's off, but the touchscreen is responsive. Hitting the power button does nothing but it makes the sound as if I had locked the phone. Hitting the power button a second time will turn the screen on like normal operation.
Very rarely I have noticed the screen will turn off while I'm actually using the phone and it's a weird effect. The easiest way to describe it is that it looks like entire lines disappearing randomly over a period of 1-2 seconds, going from all visible, then to all black, kind of like slatted blinds being closed, but at random. After this, it displays the same symptoms as if I had found the screen off while in a dock/charging.
Now, I don't want to say it's related, but I first started experiencing this on the Stock KitKat update from Verizon. I am currently using Cyanogenmod 12 nightlies and I am experiencing the same issue. It seems to be happening with greater frequency.
I have also experienced the blue screen effect when certain animations/elements/apps are up on my screen, but I think they are unrelated.
Also, there is a faint discoloration bar about 2/5ths of an inch thick uniformly vertically from top to bottom of my phone on the righthand side (just under where the notification bar would be if turned horizontal).
I've tried to find more information about this but my search results have been relatively lackluster (90% of the results are trying to sell me the phone or specification pages)
So I'm breaking down and turning to here. Does anyone know what's going on here? My current theory is that my screen is going bad. I have no intention of replacing the screen on this phone (would rather just buy a new one), so any suggestions that don't involve physical hardware repairs would be appreciated.
Click to expand...
Click to collapse
i also have this with my referb i made moto give me my money back and they let me keep the phone for me it was very rare but my new phone also had a really bad screen all yellowish and bad white balance in low light if you are unhappy with it call them and say you are unhappy with the replacement here is the white glove number 800-653-7185 they are more understanding and nice but you may lose you ability to unlock your bootloader on the new phone if it comes with the latest software just a warning
I have that screen off with lines slowly disappearing thing, too And, yeah, it's also a refurbished one, bought from one of the sellers on aliexpress... I thought Lollipop was the culprit or something like that. Oh, well... It rarely happens. And luckily I only have that, not the second issue you mentioned
I am having this exact same issue. The weird lines-to-black screen thing, and the flickering blue screen when watching video. Are you saying the solution is to call Motorola and ask for a new phone?
The blue flickering can be prevented by going into Developer Options and checking "Disable HW Overlays".
The discolored stripe on the screen sounds like burn-in; these AMOLED screens are much more susceptible to burn-in than the LCD screens used in older phones. Whomever owned the phone before it was returned to Motorola probably had something running on their screen continuously with a bright-colored bar at the top, likely in a car or desk dock. The screen is very easy to replace yourself with an eBay part, if you're inclined; it involves 2 screws and 2 connectors.
I've seen the lines-to-black thing exactly twice since I got this phone refurb two months ago. Sorry, I don't know what causes it or how to avoid it, but the workaround is quick and simple enough that I'm not worried about it, yet.

Finicky LCD? Other problems too

So i've been having a lot of issues with my N5 lately, mostly small stuff like general slowness, poor battery life, not surprising on an almost 3 year old phone. I also lose cell service way too frequently (not an issue with my carryer, all my friends are on the same network and are fine). Camera won't focus anymore (though im pretty sure this was my fault, probably broke it while taking it apart). I'm pretty sure the battery connector on my motherboard is damaged. I've had many problems with the battery reading its temperature as -30 C (battery heath "cold"), i've replaced the battery 4 times now and i still get that problem every now and then. Pushing on the connector fixes it temporarily, so im pretty sure some pin is bent slightly out of place and i don't know how to fix that. It recently started having this issue where just moving or bumping the phone the wrong way would cause the phone to shut off. Probably an issue with the battery connector again. I tried fiddling with it but it didn't do much.
The other day i turned it on and the LCD was backlit, but black except for one single vertical white line. Rebooted and it looked normal. Few hours later i got really pissed off with it for shutting off in the middle of an important text and threw it at the wall (not the best idea i know). Screen was already cracked so i didn't really care. Ever since then the LCD has been a real pain in the ass. i can turn the phone on but there's nothing on the screen. Ii get haptic feedback when the Google logo would up, and the notification LED is flashing like i have a message. The backlight is on and pushing hard on the cable connecting the motherboard to the daughter board i can see it start to turn on, (Google logo, few seconds of boot animation) but then back to black (while still backlit).
I can post photos if it would help diagnose/fix this, my phone is my main camera and i don't want to bother anyone if i don't have to.
Anyone know any tricks that might squeeze another mouth out of this dying phone? Any response is appreciated, Thanks!
The issues could have been related to the power button or physical internal damage. My suggestion: replace the screen with a cheap 3rd party screen if the internal components are still working. This will give you more time with your existing phone and allow you to have a working backup.

Broken screen working again on low battery

Hi guys,
Some while ago my oneplus 7pro felt from the stairs. The backside is complety broken, but the frontscreen was ok because of the screenprotector.
After a while i noticed 'a lot' of dead pixels on the lower left side of the screen. The phone was still usable so i didn't bother about it.
Suddenly during normal use, my screen started flickering and my screen went off. It seemed that the screen was devided in 2 where the notificationbar was on the same height of the broken screen pixels.
I could see some things, but with a green film. But not possible of unlocking the screen.
I tought that the screen was completly broken and i moved to a spare phone.
I still hoped that the screen would do some sort of a reset when I let the battery completely drain, charge a bit and try again.
I checked almost every day on what percentage. But when it was on 13% (or nearby that %) the screen was working again like nothing happened before. I tought it was working again and charged it.
Because it worked again on a low percentage, I tought it may be a lower refreshrate of some sort of stuff that is on during battery save mode.
I left it charging some small time, tried again and screen was broken again.
I tought it was a lucky shot, so i didn't bothered again about the phone.
Yesterday i checked my phone again out of curiosity, and guess what, it was working again.
So I'd like to know what might cause it to work again on low battery. I lowered the resolution and refresh rate already.
Anyone who got an idea?
Nothing short of taking the phone to a repair shop will restore your phone to normal.
It's just going to get worse, there's nothing you can do to stop the progression, short of a repair & even then, you're probably throwing good money after bad, considering the type of damage incurred.
oepsiepoepsy said:
Anyone who got an idea?
Click to expand...
Click to collapse
Can't be sure, my guess is some voltage leakage on higher voltage and short the screen somehow. If you can try de assemble and re assemble the phone. Just my guesses.
I suppose the higher the voltage the phone is able to provide the screen the worse it's going to get. Send it to OnePlus. Don't get it done independently, they cost way more

Screen won't turn on G965F

Hello! I replaced my battery with a genuine one yesterday. The phone worked fine for a few hours. Then it started showing a white frame with a green line once in a minute. After that it progressively worsened in the course of two hours. It went through green screen with numerous green horizontal lines, completely black screen and a black screen with a few green lines. Now the screen is completely black and shows the lockscreen for a few milliseconds when locking/unlocking and now this is a permanent state. It is not going better. The only way I am able to use the phone now is through Dex and scrcpy.
The screen has no cracks and the phone has never been dropped. Which is strange, because it really looks like a hardware issue. There is no water damage as well.
I would like to know what may be the cause and I will be grateful if you could suggest any temporary or permanent solutions.
Currently I have tried the safe mode, oled saver, min and max brightness in the hope of being a software issue and still no luck.
Thank you in advance!
jormil1 said:
Hello! I replaced my battery with a genuine one yesterday. The phone worked fine for a few hours. Then it started showing a white frame with a green line once in a minute. After that it progressively worsened in the course of two hours. It went through green screen with numerous green horizontal lines, completely black screen and a black screen with a few green lines. Now the screen is completely black and shows the lockscreen for a few milliseconds when locking/unlocking and now this is a permanent state. It is not going better. The only way I am able to use the phone now is through Dex and scrcpy.
The screen has no cracks and the phone has never been dropped. Which is strange, because it really looks like a hardware issue. There is no water damage as well.
I would like to know what may be the cause and I will be grateful if you could suggest any temporary or permanent solutions.
Currently I have tried the safe mode, oled saver, min and max brightness in the hope of being a software issue and still no luck.
Thank you in advance!
Click to expand...
Click to collapse
Are you certain that the replacement batter is the original OEM battery with the same specs and ratings as the stock battery or is it a higher rated aftermarket battery with "OEM design"?
If replacing your battery required opening the device and exposing the hardware to remove the battery, you may have damaged other parts of the hardware without realizing it.
From your description, your display is fried, probably due to the battery not being compatible or due to something internally making contact that shouldn't be making contact or due to the ribbon being damaged or slightly pulled loose while changing the battery and eventually completely disconnected after replacing the battery and reassembling the device.
Either way, it is definitely a hardware issue.

Categories

Resources