Related
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.
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?
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.
so i recently replace my mtxp screen and everything was working perfectly until one day i was watching a youtube video and tried using my navbar buttons and they were unresponsive..did everything from rebooted..clear cache..reinstall rom...same problem..its like the bottom of the screen is unresponsive and only works when screen is locked...
anyone else with the same problem/solution?
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
vodanium said:
Hi, I have the same situation: the screen was replaced some 9 months ago and worked fine until a few days ago, when the navigation bar stopped responding. I think it happened during watching a video (on facebook or YouTube) as in your case. I've also tried everything you did, but for no avail. The interesting thing is that the screen itself is reaponsive in that area e. g. during the Setup wizard or on the lock screen (e.g. the button to switch on the camera is working fine). I think I had some similar issue with another android device (LG 4X) when I was using a non-stock ROM (CM) and there was some issue with the installation of Google Apps. As I'm using the stock ROM for my Moto X Style, my best guess is that it might be a potential Google Play Services update that is causing this issue.
Maybe this theory could be checked by installing a third party ROM without Google Apps (I'm not sure if that is possible) to see whether the navbar works that way or not.
Click to expand...
Click to collapse
Hopefully I will figure it out.. It's definitely a software problem triggered by a update or system app.. My work around for now is using a nav bar app from the playstore
Hi, I have switched on the "Show touches" feature in the Developer options to see whether the screen is detecting touches in the bottom area of the screen: it actually doesn't. It is not an issue on the lock screen though but it is for the navigation bar. So, it seems it is the hardware that is acting up, after all...
I have found a thread about this issue with a workaround to increase the height of the navigation bar by xposed: https://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985
I'll try either that or by installing a custom ROM that has that option built in - e.g. AICP 12.1 (Android 7.1) seems to have such setting.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049
Same problem here - at least in my case also a hardware issue after replacing a broken screen. Thought (as many did) it was software because TWRP, lockscreen etc works, but if you actually try touching only the downmost parts of the TWRP or lockscreen buttons, it won't react. "Show touches" from developer tools also shows touches being registered only just above the normal navigation buttons.
So I had a perfectly fine Motorola MOTO X Style and all of a sudden, without notice, the navigation bar at the bottom stopped responding. I could figure out it wasn't a hardware issue because that part of the screen would still be responsive when the black navigation bar was there.
So i decided to root and unlock my phone and I've been trying to put several roms, i tried with crDroid and with pureXMM from this very same forum , and sometimes it would work and others it just wouldnt. Now i'm up to a point where I installed a new rom and it still doesnt work. i don't get why, it now doesn't work even in the TRWP recovery app. and my latest rom is pure slim (also from this very same forum) and now the whole bottom area won't respond to anything (not even the keyboard space, because I disable the navigation bar and keyboard is pushed down because of the empty space and it just wont work. I have no idea of what could be causing this problem. but it feels as if there is an invisible spacer on top of that bar that impedes the whole bar from working.
i'm so confused, any ideas?
I had a similar issue just recently. Using the developer options I was able to see that the presses under a certain line are not registered anymore. Strangely enough, after charging the phone over night, the issue is gone. I am now dreading its return and start to search for a new phone as it seems from your comments that this is a hardware defect and not a software issue...
troin said:
So I had a perfectly fine Motorola MOTO X Style and all of a sudden, without notice, the navigation bar at the bottom stopped responding. I could figure out it wasn't a hardware issue because that part of the screen would still be responsive when the black navigation bar was there.
So i decided to root and unlock my phone and I've been trying to put several roms, i tried with crDroid and with pureXMM from this very same forum , and sometimes it would work and others it just wouldnt. Now i'm up to a point where I installed a new rom and it still doesnt work. i don't get why, it now doesn't work even in the TRWP recovery app. and my latest rom is pure slim (also from this very same forum) and now the whole bottom area won't respond to anything (not even the keyboard space, because I disable the navigation bar and keyboard is pushed down because of the empty space and it just wont work. I have no idea of what could be causing this problem. but it feels as if there is an invisible spacer on top of that bar that impedes the whole bar from working.
i'm so confused, any ideas?
Click to expand...
Click to collapse
Sounds like it's hardware, try changing size of navbar in custom room to 125% to temporarily solve
Spencervb256 said:
Sounds like it's hardware, try changing size of navbar in custom room to 125% to temporarily solve
Click to expand...
Click to collapse
that's pretty muth the only thing left I can do.
The bottom part of the screen no longer works for me.it was weird because it worked for a starter but then it just stopped working. the first half inch more or less of my screen is senseless
so im having the same problem on my xt1572. Im running Aicp 7.1.2 Navbar suddenkly stopped working. so i went to dev options and enabled show touch on screen and sure enough it didnt recognise touches below the navbar start line. so i did what was suggestedand clean flashed, same problem, and then i increased navbar height, now the navbar is working but the strange thing is the show touches settings is still turned on and however much i increase the navbar height the touch is never recognized beyond the strat of the navbar so im thinking its still a software issue.
viggyv said:
so im having the same problem on my xt1572. Im running Aicp 7.1.2 Navbar suddenkly stopped working. so i went to dev options and enabled show touch on screen and sure enough it didnt recognise touches below the navbar start line. so i did what was suggestedand clean flashed, same problem, and then i increased navbar height, now the navbar is working but the strange thing is the show touches settings is still turned on and however much i increase the navbar height the touch is never recognized beyond the strat of the navbar so im thinking its still a software issue.
Click to expand...
Click to collapse
Beyond the strat? If it's still not showing touches I'd be inclined to say hardware. I don't know what it is, but these screens don't seem to hold up very well..
Spencervb256 said:
Beyond the strat? If it's still not showing touches I'd be inclined to say hardware. I don't know what it is, but these screens don't seem to hold up very well..
Click to expand...
Click to collapse
I am also suffering from this nav bar issue. Tried factory reset, 1st time it solved the problem, but it started again. I reset again, but it didn’t fix.
It seems like the culprit is nav bar. Then is the problem in hardware? Did anyone try replacing the phone screen?
My thought is,
1. Since the nav bar area seems to be causing the problem, it maybe a bug, so software issue.
2. The battery heats up alotttt, which may also cause some issue. And battery is just beneath the screen.
Please if anyone has a solution, please inform. TIA
IftekharAziz said:
I am also suffering from this nav bar issue. Tried factory reset, 1st time it solved the problem, but it started again. I reset again, but it didn’t fix.
It seems like the culprit is nav bar. Then is the problem in hardware? Did anyone try replacing the phone screen?
My thought is,
1. Since the nav bar area seems to be causing the problem, it maybe a bug, so software issue.
2. The battery heats up alotttt, which may also cause some issue. And battery is just beneath the screen.
Please if anyone has a solution, please inform. TIA
Click to expand...
Click to collapse
Some of my friends had this problem too. They had to replace a new battery and some even a new lcd. Battery caused this problem.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049