[Q] Screen flicker problem. Please help - Nexus 7 Q&A, Help & Troubleshooting

I am experiencing a screen flicker on my Nexus 7.
It happens once every 5-10 minutes always in the same spot, across the bottom third of the screen.
I am running Paranoid Android 2.1.6 rom on it.
It is still within the two week exchange policy of the best buy where i purchased it. Yet, if i can diagnose the problem and fix it, i would prefer not to exchanging the unit.
Is it a rom problem or a hardware issue?
Can someone please help?
Much appreciated.

Define flicker.
If people here talk about screen flicker they refer to an issue where the brightness of the entire screen changes. It happens on low brightness and seems to be related to wifi.
What you're describing leans more to another known issue, namely the vertical stripe. It happens periodically and manifests as a single vertical line (in landscape) across the screen for a few frames duration. This seems to be a software problem and is reportedly fixed by flashing motley's kernel.
If your problem is really 1/3 of your screen flickering then to me that's an unknown issue and I would rma if I were you. Unless it's to do with your rom, for rom related issues you should check the thread. Can't hurt to try another rom before swapping device ofc.

Logic_ said:
Define flicker.
If people here talk about screen flicker they refer to an issue where the brightness of the entire screen changes. It happens on low brightness and seems to be related to wifi.
What you're describing leans more to another known issue, namely the vertical stripe. It happens periodically and manifests as a single vertical line (in landscape) across the screen for a few frames duration. This seems to be a software problem and is reportedly fixed by flashing motley's kernel.
If your problem is really 1/3 of your screen flickering then to me that's an unknown issue and I would rma if I were you. Unless it's to do with your rom, for rom related issues you should check the thread. Can't hurt to try another rom before swapping device ofc.
Click to expand...
Click to collapse
Thanks so much for your reply.
The verical stripe is exactly the issue I am having.
Can I flush the motley's kernel right on top of paranoid android?
The vertical line is thin, it doesn't take up tbe third of the screen.

Related

[Q] Nexus 4 Ghost touches

So I bought a used N4 sold as is because the seller said he had some issues with the ROM and the touch sensitivity and all it needed was a stock ROM flash. I took up the challenge and flashed stock 4.4.4.
While I'm at the home screen everything's fine, as soon as opened the app drawer there were random touches all over the bottom half of the screen. Some were shown in the center and many at the bottom left corner but most were just random. I mean like 7-8 touches per second. The same happened whenever I went into play store, Opera or Chrome. Didn't test it further since I decided to try another rom.
Flashed Purity ROM and at first glance it worked flawlessly. Not random touches in home screen, app drawer or settings. Then I flash Gapps and the same thing happens with Play and Opera.
The funny thing is that the problem persists but at different circumstances. Can't pinpoint the exact cause. Should I get a new screen and try? Or maybe something else is at fault there?
I've been having the exact same problem as you. It started after I replaced the screen and the usb flex.
Ghost touches 1-2 each second only on some apps (none on homescreen or settings). I noticed that it happen in 4.4.4 app drawer but not in the 4.2.2 app drawer. I got almost no ghost touches on 4.2.2 messaging app also. It happens in almost any app, like play store, dropbox,chrome....
I thought it was the battery so I replaced it, but it did not fix it.
I have been trying to troubleshoot the problem but I ran out of theories. I wish the best luck to find the solution, as I almost gave up on it. If you happen to solve it tell me.
I think i found out what's causing this issue.
My theory was that apps with a lot of white would trigger the ghost touches. So I tested with flashlight screen apps that only show white on the screen. As expected the ghost touches only started to appear when i turned the flashlight on.
Therefore my theory was correct.
In my case I will contact the seller that sold me the screen to see if I can get a replacement.
I've had the intermittent touch screen issue, just above the capacitive buttons and also the ghost touches.
Started about 2+ weeks ago.
I reverted back to the stock "HOME" launcher instead of the Google Now launcher and that seemed to have fixed the issue.
I will have to keep an eye out to see if it lasts.
Nexus4 Ghost touch navbar fixed (for rooted only)
Nubrig said:
So I bought a used N4 sold as is because the seller said he had some issues with the ROM and the touch sensitivity and all it needed was a stock ROM flash. I took up the challenge and flashed stock 4.4.4.
While I'm at the home screen everything's fine, as soon as opened the app drawer there were random touches all over the bottom half of the screen. Some were shown in the center and many at the bottom left corner but most were just random. I mean like 7-8 touches per second. The same happened whenever I went into play store, Opera or Chrome. Didn't test it further since I decided to try another rom.
Flashed Purity ROM and at first glance it worked flawlessly. Not random touches in home screen, app drawer or settings. Then I flash Gapps and the same thing happens with Play and Opera.
The funny thing is that the problem persists but at different circumstances. Can't pinpoint the exact cause. Should I get a new screen and try? Or maybe something else is at fault there?
Click to expand...
Click to collapse
Hi everyone. this is my first post. i may make some grammar mistakes, because english is not my native language.
I found a solution for the ghost touch issue on my nexus 4, so maybe it can help who is having the same problem.
1- Download and instal the NOMone Resolution Changer on Play store
(this is my first post here, so i cant paste de link here, but you will not have trouble to find it)
2- when asked, Allow superuser
3- open the app and change the height resolution to 1250. (it worked for me, but make some tests to see if you need to disable a bigger part of the screen to avoid de problem)
This is not the best way to keep using your phone, because you may lost a part of the usable screen, but worked for me.
Thanks!
I workaround this issue avoid using undervoling in the kernel, and avoid lower temperatures in phone, yes as you read ... this issue give my crazy when my phone was to hot and I tried to cold my phone using one ice cube in screen and back, the temperature of the phone down but ghost touches appears again, so played some videos to warm the phone again and dissapear again.
Don't ask me about how it works, or relation with screen, digitizer or battery, I don't understand but help me to workaround the issue.

[SM-G730A] ATT Galaxy SIII Mini (KitKat/Touchscreen Issue)

I am not sure how many owners of the SM-G730A are mobile gamers at all, but maybe some of you have noticed this...
Since the update to Android KitKat 4.4.2 the touchscreen behaves erratically in certain games, primarily FPS shooters. I know it is not an issue with my particular device, goto Google Play and look up Dead Trigger 2. View the reviews for this device model only, you will see numerous complaints beginning after the date the OTA was released (8/27/14) complaining about the touchscreen controls.
I have downloaded the kernel source code from Samsung for both 4.2.2 and 4.4.2. Upon examining the kernel source, the Atmel touchscreen driver has been updated in 4.4.2. I believe this to be what is causing the problem. I am not sure if it is configured incorrectly or if it is just a poor driver. The Jelly Bean driver gave NO issues what so ever. I would revert back to 4.2.2 Jelly Bean if I could. I also compiled a kernel for KitKat which includes the Jelly Bean Atmel driver, however due to the locked bootloader, it does me no good.
What happens is this, you will have two fingers on the screen. Suddenly it is as though you lifted one, even if you are still touching the screen. Touches are erratic for a few seconds after this happens, then touch returns to normal temporarily until it happens again (usually only a few seconds later). This makes using the device for gaming extremely annoying, and difficult. This issue does not occur in normal use, only gaming, where there is rapidly changing multitouch inputs.
If any of you have noticed this, maybe you can contact Samsung/ATT complaining of the issue, if we're lucky maybe a patch will be released. Or it will be fixed in a future firmware update. I already wrote to both, ATT says they will forward the complaint to their management, Samsung has yet to reply.
http://www.samsung.com/us/support/contact / [email protected]
Also, this is a video I created demonstrating the problem. The video includes annotations describing the issue that can only be viewed from PC YouTube.
https://www.youtube.com/watch?v=3FMEPB51Y-4
Thanks for reading.
Has anybody with this device tried a multi-touch test? I'm starting to wonder if it's related to my screen protector. The issue only started after the KitKat update though, immediately after. I do a good amount of mobile gaming or I'd never have noticed it still to this day. Never presents itself outside of fps games.
Best way to check (within multi-touch test app):
Touch screen with two fingers.
Keep one stationary and rapidly slide the other around for a few seconds then stop and lift that finger only.
The stationary touch will act as though you lifted even though you didn't.
Sometimes touches will be erratic for a while if the test is repeated several times.
If anyone tries this please let me know if you have a screen protector or not and how it behaved. Thanks.
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
quakeaz said:
Nobody with this device on KitKat is willing to do a multitouch test for me?
All you have to do is turn the phone sideways so the app is in landscape mode, touch with two fingers, one on each side of the screen.
Keep one still, move the other rapidly for a little while then stop, but keep touching the screen.
Does the app show that you lifted the other finger even though you didn't?
I'd appreciate it, trying to narrow it down to a kernel driver issue, or screen protector issue.
https://play.google.com/store/apps/details?id=com.rn.yamtt
Click to expand...
Click to collapse
Its the phone mine does these same. Might just be a cheap screen make
Deonta23 said:
Its the phone mine does these same. Might just be a cheap screen make
Click to expand...
Click to collapse
Thanks for verifying. It's not the screen itself from what I can tell. I tried this on Jelly Bean with no issues. I did go through the kernel source for KitKat and believe it is the KitKat kernel touch driver. I am hoping for ATT/Samsung to release a kernel patch. The multitouch was perfect in JB.

Tab 4 10.1 SM-T530NU Brightness Not Changing

I've just noticed that the brightness slider moves from end to end with no change in screen brightness.
Anyone got a fix?
Android 5.0.2
Yes, I have the same problem. Mine is weird though. Mine will sometimes get bright and match the setting, but a majority of the time it goes to the most dim level on the screen regardless of where the brightness level is set. I'm hoping that it is something that I can fix, but I don't know if people will say that it's a hardware issue. My Tab is rooted again after I reinstalled the stock firmware again to try and fix the problem. Hopefully someone can offer an insight to this problem. I'm wondering if taking it apart and heating up the processor with a heat gun would cause it to work. That worked as a temporary fix on an Apple computer.
I have the same problem after I rooted the tablet. The only solution I found is install the app Screen Filter.
Are you on a custom ROM?
Can you reproduce the issue with a stock ROM?
If not,its probably the custom ROM have bugs.
Or maybe sth else

Left Third of Screen Flickers On Gray Image

Hey all.
So I got my MXP about a month ago, as my faithful Nexus 6 has long been deteriorating (#RIPshamu), and I wanted to try something a little different. I love the device and have almost gotten it tweaked and set up just the way I like it. However, I'm currently facing an issue that I can't seem to fix.
When I have a dark gray image on screen, such as the dimming when you pull down the notification bar over a white screen, the left side of my screen flickers rapidly from dark to normal, as if changing brightness. It is most noticeable on higher brightness settings, but plenty present enough on lower ones anyhow. I have made sure that no odd display tweaks in GravityBox are interfering with system presets, and I can't figure out what might be causing this.
I'm hoping it is software-related; I bought the device off-contract and without warranty, as I do with all my handsets, but if the problem is with hardware I should be able to fix it on my own so long as I know what part is causing the issue.
I'm running TruPureXMM with FrankenClark kernel. (systemless SU, magisk/systemless-xposed if any of that matters to you). Can provide logs upon request, but things seem normal to me at first glance.
Anyone else experienced this or have a fix?
I too am running TruPure and Frankenclark. I've been having a similar issue with the display, except it's the bottom half of the screen that is dimmed. I've also noticed that the 'dimming' takes on vertical lines of color depending on what the screen is displaying. The 'dimming' has consistently been transparent for me.
I originally thought that it may have started because I changed some settings using kernel adiutor, however changing those settings back did not fix the issue. I've yet to try returning to stock. I've also noticed the same display issue on boot up and in TWRP, which suggests a hardware problem, not a software one.
Some research online suggests that there is a known display bug with the Moto pure, and that the temporary fix is to reboot, but that doesn't solve the problem for me.
I think I'll try reverting to stock first, and if that is unsuccessful, then I'll try to reseat the display connector.

Brightness dependent yellow tint and black lines on the screen

Hello,
I've been having this issue for the past few weeks, where my screen will turn yellow and display lines across the screen at medium brightness. At max and min brightness it works normally, but at intermediate brightness it displays varying degrees of this issue.
Have anyone encountered this issue before? What can be done about it?
The issue just suddenly showed up. I went to bed and it worked fine, I woke up and it was like this.
I do not have any warranty, so any repair would be done myself. Issue occurs in TWRP as well, independent of the OS.
Video of the issue: https://streamable.com/zrvqh
The issue has been resolved by switching kernel. I was previously on the S8 NX kernel, and now tried switching to Velocity kernel and the issue is gone.
Should be pointed out the new kernel is "flicker-free", while the other is not. Not sure if that matters, but it's a screen related change in the kernel at least.
In case anyone else comes here looking for a solution, try a kernel swap.
Edit: Nope, for some reason this works as a temporary fix but doesn't last. Issue comes back.
Make.Sense said:
The issue has been resolved by switching kernel. I was previously on the S8 NX kernel, and now tried switching to Velocity kernel and the issue is gone.
Should be pointed out the new kernel is "flicker-free", while the other is not. Not sure if that matters, but it's a screen related change in the kernel at least.
In case anyone else comes here looking for a solution, try a kernel swap.
Edit: Nope, for some reason this works as a temporary fix but doesn't last. Issue comes back.
Click to expand...
Click to collapse
any luck with this issue ? happened to me now

Categories

Resources