I had flashed LOS 16 and hade been using it for over a year with the same broken display.
Sometime back the phone would just restart by itself and sometimes wouldn't even boot so i had opened the device and found my power button to be jammed. Which i fixed when i turned the device back on started showing this flickering.
Is this a hardware issue where one of the connectors might be causing it or is It the LCD itself?? Can someone explain.
Your browser is not able to display this video.
P.S. I also wonder if its LOS itself cause every time after switching on the device the satus bars and all content on the screen would jump up and down but will revert back to normal after locking and unlocking the device
Update
just keeping the screen onwfor few minutes fas eliminated the weird glitches but there still is a slight flicker to the bottom half with lime in the middle
Your browser is not able to display this video.
Related
Hello, My G1 has just suffered a problem, i was scrolling down a web page and the screen faded out like it had lost power but the backlight was still on, the keys lit up and it still could make the trackball clicking noise when you moved it. I took out the battery and left it for 5 minutes and rebooted my phone and the screen turned on for about 3 seconds and faded out like before but it did boot into android as I heard the notification/startup sound. I think that the screen has burnt out but im not shore so has anybody had this problem before and/or might know how to fix it
Just some more infomation, If the screen dies and I leave it for a few minutes, when I unlock it or slide the screen up, the screen works for a few seconds but then fades. Also the fading looks like the screen lost power or like its losing pixels
From my experience with phone hardware this doesnt look like screen problem, but rather the lamp driver in the motherboard. the only way to narrow down is test the motherboard /screen with another phone.
If this is the case, it might require servicing the backlight driving circuit, which by far requries soldering/desoldering some components in motherboard.
wilkinlp01 said:
Hello, My G1 has just suffered a problem, i was scrolling down a web page and the screen faded out like it had lost power but the backlight was still on, the keys lit up and it still could make the trackball clicking noise when you moved it. I took out the battery and left it for 5 minutes and rebooted my phone and the screen turned on for about 3 seconds and faded out like before but it did boot into android as I heard the notification/startup sound. I think that the screen has burnt out but im not shore so has anybody had this problem before and/or might know how to fix it
Click to expand...
Click to collapse
had the same problem its a hardware issue. tmobile sent me a new phone no questions asked
Thanks for the replies, it seems that it has fixed its self as I've been using it for about 5 hours and no problems so far, I'm using it right now to type this, if the problem persists I will try and fix it or just buy a new one
I have read several threads, both here and on other support website on the Transformer's display randomly having a tendency to fail (in some cases anyway).
Often this is through no fault of the user with lots of users being affected who's Transformers aren't rooted and have suffered no damage.
I found all these forums because one day my Transformer did this. I used it that morning and then locked it for the day with wifi on walking around my college, meaning it was likely to be on wifi all day but I wasn't using it.
When I got home I pressed the lock button and the backlight came on but nothing else? This confused me so I pressed lock again, backlight switched off, press lock again, backlight came back on but still nothing actually on the display, just a black lit up display. Hmm this is definitely weird. Held down lock button until the screen had gone blank. Pressed lock and it made that mechanical click like usual and the speakers flickered like usual. The backlight had came on but no display still.
It seems that the power to display is still connected but a ribbon cable that provides the input comes loose somewhere. After rebooting several times with no luck I got bored and started shaking it around a bit. Not violently or hitting it, more waving it around like a crazy person.
Suddenly it made a clicking noise and I saw it had restarted. Now there were loads of blue lines across my screen. The blue lines remained until what seemed like the duration of the time it took to boot. Then it went blank again. I shook it around some more and when I was ready to give up I pressed the lock button and it lit up, my background and all. Touch input is working and everything appears to be working.
I thought I would just write this in case someone is experiencing this issue and rather than sending it back (or if you have rooted so have no warranty) you might with any luck be able to fix it just by having a little dance with it!
Good Luck.
After hanging up from a phone call the top left corner of my screen was really bright. There were two vertical lines down the screen and the screen was transparent and flickering. I could still see my home screen and the screen was functional. I restarted the phone and it was still acting up. Only after turning the phone off for a few mins did it stop. Has anyone else experienced this or have any ideas on what would cause it? I haven't had any issues with the phone, no drops or anything. Currently running aokp with matrix kernel.
theville502 said:
After hanging up from a phone call the top left corner of my screen was really bright. There were two vertical lines down the screen and the screen was transparent and flickering. I could still see my home screen and the screen was functional. I restarted the phone and it was still acting up. Only after turning the phone off for a few mins did it stop. Has anyone else experienced this or have any ideas on what would cause it? I haven't had any issues with the phone, no drops or anything. Currently running aokp with matrix kernel.
Click to expand...
Click to collapse
I had this issue too. My phone just arrived today. In my case the problem occurred after power cycling the phone (trying to get the WiFi to connect.. grrrr) The boot process was fine but once I got to the launcher my screen was flickering like a strobe light. I tried to power off and back on and it still happened. I didn't give it several minutes like you did so I'm not sure if it would have gone away. Since I hadn't really configured the phone yet I simply did a factory reset and it was fine. Seems to be a software issue. I hope it doesn't happen again but if it does I'll see if just leaving it off for a while helps. I hope so because I don't want to have to factory reset all the time!
-Matt
I have a Moto G4 that has had the touch screen become very erratic lately. This issue appeared shortly after a factory reset. The phone is stock, recently OTA updated to NPJ25.93-14.7. It frequently freezes and won't respond to touches of apps or the home/back/recent buttons, and won't side scroll to the next screens properly. Sometimes random apps launch on their own without any touch, and if you try to quit them with the back button they keep relaunching. The problem is intermittent.
I activated "Show Taps" in Developer Options and when the problem is happening there is a tap dot near the lower right side of the screen. It bounces up and down a little bit and vibrates sometimes. When this dot is visible tapping on anything else like app icons or buttons usually has no effect, however the taps are shown on the screen. If I hit the power button to make the screen go black it will sometimes recover when I reopen the display, other times it takes a reboot.
Wondering if it's a hardware issue, a guy at a Verizon store who seemed to know more than most said it was a faulty digitzer--it's seeing touches where there are none. I've replaced displays successfully before, would just like to have a confidence level that the digitzer is really bad before doing that, as opposed to a software or other hardware issue. Any ideas about problems that might cause this problem, like other hardware or a corrupted OTA? Seems very hardware-ish to me, but I'm no expert.
I have Drive links to a couple of short videos on the symptoms, can send links. Much appreciate any insights.
Mine has that issue as well. It will spam the 9 key on the unlock screen or anything in that spot if an app is open or what is on that spot at the home screen. I have to double unlock the phone to fix it. I guess turning the screen on and back off resets it for that session. But it's mostly every time the screen goes dark and comes back up I have to turn the screen off and back on to use the phone.
I had a similar problem and was able to send it in under warranty and get a replacement phone
G4 Digitizer or ghost touch
Apparently this is called Ghost Touch issue, and affects many phones. One solution tried is to disable Battery Optimization for System UI and Google Now Launcher in Settings>Battery>Battery Optimization. That seemed to cure it for a week or so, but the problem returned today. I can sometimes recover form it by hitting the power button to blank the screen and then reopen. Other times it requires a reboot. I see all kinds of alleged solutions out there from dimming the brightness to removing tempered glass protector to using a slow charger, but those don't seem like real fixes but workarounds (if they even work at all). Any other ideas?
I have a weird bug the last 2 days, after unlocking the screen randomly the navigation bar controls are unresponsive for 2-3 seconds, I thought it was a bug of ASE6 but I updated to ASE7 yesterday night and it's still occuring.
Am I the only one?
Yeah I have that issue time to time too. I first thought it was because of the screen protector that I didn't peel off the first week I got my device, but apparently that's not the case, especially the bottom right corner of the screen where the default back button is feels unresponsive at times. Switching on and off the screen helps. I don't know if it is a general problem or some sort of a hardware problem.
Btw does ticking the option to increase touch input responsiveness increase battery usage, and should we try that on?