Hello, would there be a "Mod" for the "Live Display" (found on Lineage Bone) on the Rom Stock, because my phone is equipped with the screen Tianama who suffers from the Ghost Screen because it can usually solve the problem.
Thank you for all help
Konoka2510
Nobody has an option or a trick to overcome this or Ghost Screen ?
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.
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.
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.
Hi,
I've a moto g5 plus which is not accepting any touch to the navbar area. Even when I enable the one nav button feature, the navbar keys hide but I cannot touch or register response to that. I don't think it's a hardware issue but if it is, how should I check it?! I'm currently using fluid navbar guesture app to navigate.?
The problem appeared suddenly when I was on Android 7.0, I thought ota will fix this problem. So I updated device to 8.1. But problem did not solved. So I tried hard reset, but no luck. If somebody know what exactly the problem is, I'd be glad. The device is not rooted nor the bootloader is unlocked.
How do I install stock oreo rom? I think this should fix it but I'm not sure.
Please help.
If you have your warranty you should get the device checked, that sounds hardware unless you rooted (you didn't) and touched something
What was the last thing you remember doing before this trouble started?
Does the screen touch works at the bottom? Does the navbar register the touch but it doesn't do anything? Can you see your lockscreen?
M1810 said:
If you have your warranty you should get the device checked, that sounds hardware unless you rooted (you didn't) and touched something
What was the last thing you remember doing before this trouble started?
Does the screen touch works at the bottom? Does the navbar register the touch but it doesn't do anything? Can you see your lockscreen?
Click to expand...
Click to collapse
Hi M1810, thanks for replying.
I've been told it's hardware issue by service centre but they not even touched my phone, that's another story perhaps. I don't think it's a hardware issue as I'm doubtful about how only the navbar portion of my screen became unresponsive only and not other part of screen?!!!
Last thing I remember doing is switching between one nav guesture feature toggling on and back. But it was working fine then for some time. It just suddenly stopped working. (This is the reason I think this is a software issue. With the moto nav bar feature.)
I've enabled the show touches from developer option. The taps not even getting registered on the bottom portion. Other than that, there is no problem. I can see lock screen but cannot touch the bottom three icons, the camera and google mic thing.
uXDay said:
Hi M1810, thanks for replying.
I've been told it's hardware issue by service centre but they not even touched my phone, that's another story perhaps. I don't think it's a hardware issue as I'm doubtful about how only the navbar portion of my screen became unresponsive only and not other part of screen?!!!
Last thing I remember doing is switching between one nav guesture feature toggling on and back. But it was working fine then for some time. It just suddenly stopped working. (This is the reason I think this is a software issue. With the moto nav bar feature.)
I've enabled the show touches from developer option. The taps not even getting registered on the bottom portion. Other than that, there is no problem. I can see lock screen but cannot touch the bottom three icons, the camera and google mic thing.
Click to expand...
Click to collapse
If not even the lockscreen lower part reponds then it's hardware.. if updating/reseting did not solve it
M1810 said:
If not even the lockscreen lower part reponds then it's hardware.. if updating/reseting did not solve it
Click to expand...
Click to collapse
Last question.... Can I install stock 7.0 rom by using this guide (https://forum.xda-developers.com/g5...e-npn25-137-67-5-fastboot-t3694738/amp/) )?! I'm currently on updated oreo 8.1. or should I flash the oreo based pixel experience rom?!
uXDay said:
Last question.... Can I install stock 7.0 rom by using this guide (https://forum.xda-developers.com/g5...e-npn25-137-67-5-fastboot-t3694738/amp/) )?! I'm currently on updated oreo 8.1. or should I flash the oreo based pixel experience rom?!
Click to expand...
Click to collapse
I don't know for sure, i recommend you to ask in that thread, ehat i know is that it is not recommended to install custom ROM's if you're currently on 8.1 stock
I recently changed the screen and now, flashing a custom ROM , the screen sometimes don't respond (in milliseconds), for example, when I type, sometimes it don't recognize the touch.
Someone have the same issue? Maybe it's driver related thing?
Running right now Pixel Experience Plus.