Database Users

Screen flickering problem

Temp fix on post 7
Hey, I've owned my phone for
about 6 months. It has been fine till about a week ago when I flashed a miui rom (Mintberry). At first, it was just occasional flickering, everyday or two for a few seconds, but now it's turned into a fair bit more.
If I don't use my phone heavily for about 3 hours, and go back to the phone, the screen has turned completely grey. When this happens, no matter what state my phone is in the screen flickers. It generally begins flickering very fast then after 5 seconds the screen is completely grey (even once rebooted).
I have dropped my phone a few times like everyone does, nothing severe or even close though. I didn't drop it then have it instantly happen.
I have since tried a few things...
Changed pixel density in rom toolbox (works once rebooted, but only till I stop using)
Changed from miui to ICS (no difference, but took an hour for it to start)
Am I looking at buying a new screen?
Edit: tried another battery, no success (didn't expect much)
Sent from my GT-I9000 using xda premium

Bump.
Sent from my GT-I9000 using xda premium

I had similar issue with my phone. I do not think it has anything to do with software.. but yours is far worse thn mine.. I only had minor flickering which could only be seen sometimes and you really need to notice it with black or white background.. I tired diffrent roms it was on all of them.. I switched back to original rom.. and then got my screen replaced underwarranty... working fine since then..

OK thanks, ill give them a call today.
Sent from my GT-I9000 using xda premium

Had mine flickering in the same fashion. Out of warranty. Took it to a repair place and apparently it was just the screen connection was loose - thats what they told me anyway - $80 later everything worked again - probably ripped me off but im not a hardware tech so didnt want to screw with it myself

I'll have a look at a disassemble guide today, see if I can fix the cable. Thanks man, generally screen flickering is from a loose cable.
Sent from my GT-I9000 using xda premium

Well today I found a fix...
I accidently left my phone in the car when it was pretty hot. Seemed fine when i used it for a few minutes so i assumed it was water damage and decided to take the battery out and leave it for a while.
Came back to the phone after i had done the shopping to see if it was still working. Nope... It was noticably colder though as the car was now in the shade.
I ended up getting a heat bag and wrapping it around the phone. The screen almost immediately started working and the screen was perfect.
Sent from my GT-I9000 using xda premium

Damaged super amoled?

I had sixaxis app running and apparently when its running in the backround the screen wont turn off. I plugged my phone into the charger last night and when the phone was done charging the notification for done charging popped up and turned the screen on. because I had sixaxis open it didnt let the screen turn off and my screen was on all night. My question is have I damaged my screen by doing this? I fear of the infamous burn in now.

If you don't see an image burned in you're probably just fine
Sent from my MB860 using XDA

I have one question. Did you even bother to LOOK and see if your screen was damaged before starting a new thread?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

americasteam said:
I have one question. Did you even bother to LOOK and see if your screen was damaged before starting a new thread?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yes I did, that was the first thing i did when i woke up and found my phone with the screen on. I was only curious if i did damage that i might not see at the moment. I guess im fine then.

lolol. Were really babying these things

Pretty sure LED doesn't burn images. Just tube screens and some LCD's.
Sent from my DROIDX

Sniper_5 said:
Pretty sure LED doesn't burn images. Just tube screens and some LCD's.
Click to expand...
Click to collapse
There is quite a bit of proof out there confirming that AMOLED will suffer burn-in. The most common cause seems to be a docking station where the user displayed an alarm clock all night or played music with the screen on for an 8+ hours a day.
So screen burn-in is a problem, but one night isn't going to significantly harm the phone,and typical users won't see any issue during the lifetime of the display.

Screen responsiveness

I've noticed that the screen responsiveness varies. Sometimes it takes a few touches before it responds other times it responds as expected.
Assume it's user error so are there any tricks/hints when using the N7? Not using a screen protector

+1 on this question.
Not sure if the varying screen response it me (user error) or the N7 itself.
Is anyone else having this problem? Or, as the OP asked, do you have any tricks/hints to share?

It looks like this happens to a bunch of people. It happens to me frequently and I usually just lock the device, pick it up and then unlock it being careful I don't have any fingers on the screen before I hit the button.
I'm not sure if it's a defect or not. Some say it is. I would tend to think so too.

There's another thread on this topic, there I asked this same question.
Do you have a screen protector installed?
If not perhaps you're in a region/area with high electrostatic or humidity, moisture..
Sent from my Nexus 7 using xda app-developers app

No offense, but I doubt the electrostatic or humid environment idea since it seems to be solved instantly by turning the screen off and back on.
I have this problem with a screen protector installed. I may remove it and try without it, but I've never had issues with XO Skins before and don't really want to trash a $20 screen protector.

I have this problem without a screen protector on
Sent from my Galaxy Nexus using xda app-developers app

I've notices laggy screen response on my 1 day old N7. I'm contemplating doing a factory restore/wipe.

I don't have a screen protector but it definitely lacks touch responsiveness.
Sent from my Nexus 7 using xda app-developers app

I have had to on occasion press twice on buttons when the first press doesn't register as well. I've seen that other thread about playing games heating up the tegra chipset affecting screen responsiveness severely, but in my case this is from light usage.

Mine has been pretty responsive so far without any issue. Just got it yesterday.

I've started to notice this issue today for sure. I thought it was my imagination before as I had only gotten it in games but today I got it in tapatalk as well. Thinking about trying for a replacement. I had gotten mine at Walmart so I guess I could go through them for exchange...
Sent from my Nexus 7 using Tapatalk 2

shinji257 said:
I've started to notice this issue today for sure. I thought it was my imagination before as I had only gotten it in games but today I got it in tapatalk as well. Thinking about trying for a replacement. I had gotten mine at Walmart so I guess I could go through them for exchange...
Click to expand...
Click to collapse
I got my 1st one at Wal-Mart too, so I went back there yesterday to get a 2nd one to compare.
It seems to me that I'm not experiencing the lag as often on the 2nd one (I don't play any potentially resource-draining games, so I notice the lag more when I'm reading something and trying to scroll up or down).
I have started to wonder though if, in my case, maybe it's happening because I haven't installed a screen protector yet. I have one on my KFire and don't have the lag/sensitivity problem. So I figure I'll get one installed on my N7 soon and hopefully that'll cure this for me...

I noticed this the last 2-3 days. However, it seems to be only in Chrome browser. I never close my browser, and towards the end of the day, I'll unlock the tab, go into chrome, and I'll have to hit everything twice...keyboard included. I just completely close it out and start it back up, and it's fine again for another day. So it's not a problem for me.

Just had it again and while it was happening I went ahead and enabled the Dev option to show presses and it definitely requires a harder press to respond over time. I believe the digitizer is at fault on this.
Sent from my Nexus 7 using Tapatalk 2

Screen ripple fix?

Is there anyway to fix the screen ripple?
Sent from my iPhone using Tapatalk

In the words of the virgin Mary, come again?

Sorry. I was wondering if there was a fix for when you pressed down on the side of the screen and it started to ripple like an lcd

RMA it like I did yesterday.
Sent from my Nexus 7 using xda app-developers app

ncvikingx97 said:
Sorry. I was wondering if there was a fix for when you pressed down on the side of the screen and it started to ripple like an lcd
Click to expand...
Click to collapse
It ripples like an lcd because it is an lcd.
Sent from my LG-P999 using xda app-developers app

Yeah, I dont think an rma is going to fix this. Don't squeeze it so hard... fixed.
Mine does it as well, so not knockin ya but. It has yet to be an issue in actual real life use. Sure you can sit there and pinch the thing, but just stop, and you'll never notice it again.

I am very OCD about my devices. Honestly, as long as I know that nothing is wrong with it in that category, I will be fine

I noticed the ripple on two of the three N7's I tried. While I think it probably SHOULDN'T be happening (i.e., it represents an underlying design and/or manufacturing flaw), I don't think it will cause any issues. Like the screen lift, it's one of those things where it's technically a defect, but it's not likely to cause any performance or other issues.
If I hadn't had other problems with mine, I'd have put the best N7 in a case and forgotten all about those two issues.

What were your other problems

My first one had pretty good screen seperation all along the left side, and pretty bad lightbleed from the left side.
My new one has barely any lift (just a 1 inch section, about a third the way up on the left side), but has the lcd ripple.
The screen seperation isn't even noticeable unless you lay it flat and look across the glass and this one feels solid, the first one was spongy.
I can handle the ripple, because it only happens when im messing with it, trying to make it happen.

regalpimpin said:
Yeah, I dont think an rma is going to fix this. Don't squeeze it so hard... fixed.
Mine does it as well, so not knockin ya but. It has yet to be an issue in actual real life use. Sure you can sit there and pinch the thing, but just stop, and you'll never notice it again.
Click to expand...
Click to collapse
Tried it on mine. I am kind of shocked at how hard it had to press to get it to ripple. I am hoping get that the op has a worse case than I do because if not this is crazy. I would never pinch that hard I every day use.
Sent from my Nexus 7 using xda app-developers app

ncvikingx97 said:
What were your other problems
Click to expand...
Click to collapse
Dead pixel on one, and a putrid yellow tint on the other two.
Sent from my iPad using Tapatalk HD

Just found another stuck pixel. Prob going for a return

Moto X Screen burn-in

I bought my Moto X around the end of September and about two weeks after getting it, I had a screen burn-in from the notification bar and navigation bar. I let Motorola know and they happily replaced it. However few weeks after owning the second one I experienced the issue again and I let them know. They told me they were stunned and that I was literally the only person who had reported the issue.
What I am wondering is if anyone else has experienced this. I know it is a common problem with AMOLEDs, but I didn't expect it to happen so soon.
Sent from my XT1060 using xda app-developers app

I have never seen screen burn in on any phone. Not sure I would notice it in the notification and navigation areas since they always display the same things.
Sent from my Nexus 7 using Tapatalk

Screen burn in after 2 weeks? On 2 devices? Come on now...
Love your avatar BTW. I can quote that entire movie.

The galaxy nexus had that issue
Sent from my Nexus 7 using Tapatalk

_MetalHead_ said:
Love your avatar BTW. I can quote that entire movie.
Click to expand...
Click to collapse
Me to !! Hehe
Sa sens le Rooting icite !!

I saw burn in on a display model at Best Buy. It was the big Motorola M logo that displays at the boot animation. If you looked at a white web page or any solid, but light colored image, you could see the ghostly circle the size of a quarter complete with the swishy M in the middle of the screen. Got them to open a second demo model and boot it up so I could see a clean screen and bring it to their attention. Weird thing to have burned in, too.
Sent from my Moto X

Op did you leave both phones display on for 2weeks straight at 100% brightness? Lol
I have had mine for 2 months, do at least 4 hours sot daily, most of which is on reddit and xda, so nav and status are almost always static... I have zero sign of burn in.
I had it pretty good on my s3, but I blame ingress for that... Being outside playing so much and had it at 100% brightness because that screen was so dark... Even then it took at least 2 months before I saw any burn in and I was playing A LOT!
Can't imagine how you would get burn in on two devices, each in two weeks... Seems like that's a feat that you have to try and do, lol.
AT&T Moto X rocking rooted 4.4

_MetalHead_ said:
Screen burn in after 2 weeks? On 2 devices? Come on now...
Love your avatar BTW. I can quote that entire movie.
Click to expand...
Click to collapse
What do you thing the man is making this up? Come on Now!

flacco40 said:
What do you thing the man is making this up? Come on Now!
Click to expand...
Click to collapse
I'd be hard pressed to believe this as well... I've had numerous amoled devices and abused the crap out of them and even then, it took months to get any sort it noticeable burn in... If it were one device then I wouldn't second guess it, chalk it up to manufacture defect... But two in a row? I'm curious as to what the op uses his phones for and if he ever turns off the screens... Even store display models take a while to get burn in and they are on 3-4 times as much as a typical power user.
AT&T Moto X rocking rooted 4.4

scottjb said:
I have never seen screen burn in on any phone. Not sure I would notice it in the notification and navigation areas since they always display the same things.
Click to expand...
Click to collapse
I'll have to send you a pic of my GNex then, so you can see the perfect "ghost" of a Pandora logo in the middle of the screen from running the display full time in my car dock.
I also remember similar complaints when the GNex first came out, of people claiming they were getting burn-in on the notification bar area, and I thought they were ridiculous at the time. Now, not so much.

It happened to my gnex, so I'm not surprised that it happened on this phone too.
I'm not saying you're faking it, but 2 weeks is a little too soon for it to be happening. The gnex only had the issue after a year or so. Are you keeping the display on all the time when charging or something?

They will eventually burn in if you set the screen to never time out and leave it displaying the same thing for hours or days on end. Most store models have some level of burn it. In normal use cases it should never be an issue though.

aooga said:
It happened to my gnex, so I'm not surprised that it happened on this phone too.
I'm not saying you're faking it, but 2 weeks is a little too soon for it to be happening. The gnex only had the issue after a year or so. Are you keeping the display on all the time when charging or something?
Click to expand...
Click to collapse
It happened with my GNex too.

Main reason I can't use another amoled phone
Sent from my Nexus 10 using XDA Premium 4 mobile app

Just passing by, but 2 weeks is entirely possible.
If you keep using the phone with the notification bar displayed and then two weeks later open a full screen browser, you will most likely notice burn in if you look close enough.
It's extremely easy to do.

I bought an S3 from ebay with real bad screen burn in (that the seller didn't mention). She actually didn't believe me and accused me of scamming her until I replied back with a contact name and number that was burned into the top of the screen from the messaging app (the keyboard was also burned in, I guess she constantly texted this person).
I think burn in is more likely to happen when brightness is higher. I had a GNex and GS3 that never got any sort of burn in but I also rarely had the brightness above 50%.

you know, now that I look, I have it too. It's faint, and I thought it was from the Nova Launcher beta, but ****, this is screen burn in. Damn.
---------- Post added at 05:26 PM ---------- Previous post was at 05:13 PM ----------
I don't even use my phone that much. Generally around 1.5 or 2 hours screen time per day. Brightness is about half. Kinda crazy.

Recommend using an app such as:
https://play.google.com/store/apps/details?id=com.feetstech.screenburn&hl=en
to minimize this. Most plasma TV's have something like this built in as they are also prone to burn-in. Use it for 10 minutes every once in a while (even if you don't see burn in) and it should prevent it.

I got screen burn in on my S4 after 2 months. But I also blame ingress for that. I have a X coming and hope to minimize that by not playing ingress so much or play on another device. One thing that I do for the status bar to help out is with nova launcher I have it set to swipe the notification bar on top away. I try to leave it off the screen as much as possible. But yes amoled screens suck for burn in.

I usually turn my phone to the 270 degree position to have the navigation bars switch sides every now and then. That helps a bit.
And with AMOLEDs, it's more important to turn off the screen when not in use rather than let it time out. I have mine set to 10 minutes, but I usually manually turn off the screen because I know AMOLEDs are prone to burn-in over time.