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.
Ok, So I've had my Acer A500 for quite some time now. Couple years in fact. Anyway a few months after getting it I noticed that I couldn't change the display brightness whatsoever. Also the autobrightness did nothing even tho I had tested the sensor and it came out fine. Now I don't know if this problem existed before I rooted and installed a custom rom, however no matter the rom the brightness still will not adjust. I have even taken the tablet apart and made sure the cable to the screen was seated well. I'm wondering if anyone might know if this is a hardware issue what may be causing it? or if it may be a driver/software problem.
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
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
I dont have this problem
vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.
sa3d12 said:
Technically speaking black color on AMOLED displays just turns off the pixels of the phone, it won't light up like what I saw from your picture.
If you are using a screen filter app such as twilight or night owl disable it and check, if not maybe try to reset your phone and I hope that is software related nothing more.
Click to expand...
Click to collapse
Not using those apps. I did a phone reset, but the problem persists.
Did You purchase Your phone from an official Samsung seller? Only phones with non AMOLED panel would light up the whole screen.
Edit: just checked my AOD, Your AOD looks slightly different than mine. On my AOD I can see a date and two small icons.
Can you post similar pictures with the default AOD clock widget?
I'm also experiencing the same issue with my S7 Edge. Problem started out of the blue two days ago; there might have been Play Store updates but I dont reckon any system updates that day. I've been using the night clock for weeks and it was working fine before now.
The problem seems to affect only AOD and night clock, since the edge feed (rubbing the side) works completely fine - only lights the used pixels. AOD and night clock light up the whole screen (not much, but clearly visible in a dark room, grayish background)
Tried resetting and flashing older firmwares via Odin but nothing changed. Hope we find an answer to this, it's shame I cant use the night clock nor the AOD since its killing battery now. :/
I remember S6 edge having the same issue with night clock?
vrblr2405 said:
I've noticed that the Always On Display now lights up the entire screen, not just the pixels for the clock and date. As you can see in the pics, even the areas that are supposed to be black (i.e. unlit) are lit up in a dark black-ish kind of glow. This seems to be appearing after the most recent update. Is anyone else seeing this issue on their phones? Is this a software issue or a display problem? Would appreciate some insights on this. Thanks.
Click to expand...
Click to collapse
Mine is working fine. You must have received an update to something in the last few days if it worked before. Either that or it's a hardware issue.
This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?
OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?
amritpal2489 said:
This seems like a LCD and not AMOLED.. Did you get your display changed due to any reason?
Click to expand...
Click to collapse
No. This is not an LCD, it's an AMOLED. This is an S7 Edge that I bought two weeks ago. Haven't changed the display or anything like that.
McKis said:
OP stated that the problem occured after an update, so I think it was working fine before that? So I wouldnt say he has S7 edge with LCD display (for whatever reason that's even possible). I can say this for sure about my situation anyway. No display changes or any other repairs, it just started malfunction for no apparent reason.
I tried a third party app for AOD and it worked flawlessy... so the built-in AOD (& night clock) lights the whole screen, while edge feed and 3rd party AOD don't. Confusing.
@vrblr2405 : did you try night clock or 3rd part aod? Is the problem still there?
Click to expand...
Click to collapse
This is the native AOD that comes preinstalled. Version 1.4.02. I've noticed that the edge clock also lights up the whole screen. Could you tell me which third party AOD app to use ? That way I can check and identify if it is a display problem or a software issue.
Try a fresh ODIN install of latest stock firmware
vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.
Don't even think about re-partitioning in ODIN.. Its not required.
Moreover if you have already flashed stock firmware using ODIN then it is surely a hardware fault buddy. Get it checked at authorised service centre even if it is out of warranty. They will let you know the exact issue. Getting it repaired through them is your choice finally.
Yeah I guess that's what I need to do. Luckily there is a Samsung Service Center nearby.
I just can't understand why would the exactly same function work on a different app if it's hardware related. That's the reason I'm baffled with things to try to get it working.
@vrblr2405, let me know how it works out and share your thoughts, thanks!
McKis said:
vrblr2405: I used (well, tried) Always on Screen by FayaX. Just make sure you disable the built-in AOD first and give the app the permissions it's asking for. Could you also check if the edge feed is working properly and doesn't lit up the screen? You know, the rubbin' thingy If those two work properly, I'm certain we are facing the same issue
@amritpal2489 : flashing stock didn't help on my situation, but of course it's always good to try.. I've been going through different (stock)firmwares now, just to see if something would change. No luck so far, downloading third one now.
Is there more to reset than the 4 files (AP, BL, CP, CSC)? How's the re-partition in Odin?
I'm unrooted, so I'll stick with stock fw's, but I'm wondering if there is something that's not "resetting" or if I can do something more to get to start every bit and piece from scratch.
Click to expand...
Click to collapse
So I downloaded the app you said. The AOD works fine with that app. I tried a couple of other third party AOD apps. The AOD works fine - only the pixels for the clock light up. So it seems to be a software issue with the Samsung AOD.
I tried the edge feeds and it works fine. No lighting up the entire screen. The entire screen being lit up happens only with the preinstalled aod apparently.
I don't intend to root my phone at least till the warranty is valid, so sticking with the original Samsung software. Will go to a service center get this checked.
usmanyasin.bk201 said:
Can you post similar pictures with the default AOD clock widget?
Click to expand...
Click to collapse
Which is the default AOD clock?
Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.
usmanyasin.bk201 said:
Just a dumb thought. Wondering if the clock type might make difference. The default one is just a simple white one. Image attached.
Click to expand...
Click to collapse
I thought so too initially. Tried with all the different clock faces. Entire screen still lights up.
Weird. Have you ever rooted the device or is rooted right now?
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