I have an ASUS Nexus 7 2012 Wifi (grouper). I have installed a custom rom and recovery on this device. (This didn't cause the issue)
It was on its original firmware and I was playing a lite game on it. (King of Maths) I was playing and scrolling through game menus hen suddenly the device shut down without warning the screen just turned off. Then I rebooted it (turned on with power button) and immediately started glitzing with artefacts on the screen, and touch didn't work in some places. A few years later I tried to revive it with lineage os 14.1. It had worked and was running the software, but the glitch was still there. and when I pull down notification shade, (only on home screen) and tried to just brightness with slider. The touch stopped.
Anyway I can fix this?
Thanks, Yeebee
Yeebee said:
I have an ASUS Nexus 7 2012 Wifi (grouper). I have installed a custom rom and recovery on this device. (This didn't cause the issue)
It was on its original firmware and I was playing a lite game on it. (King of Maths) I was playing and scrolling through game menus hen suddenly the device shut down without warning the screen just turned off. Then I rebooted it (turned on with power button) and immediately started glitzing with artefacts on the screen, and touch didn't work in some places. A few years later I tried to revive it with lineage os 14.1. It had worked and was running the software, but the glitch was still there. and when I pull down notification shade, (only on home screen) and tried to just brightness with slider. The touch stopped.
Anyway I can fix this?
Thanks, Yeebee
Click to expand...
Click to collapse
Just so that I understand, are you saying that upon adjusting the brightness, the touchscreen failed to respond? It seems odd that it would do that. Does the touchscreen work at all anymore? If you could enable developer options and usb debugging then it would be very useful to post the 'adb logcat' output.
Related
I've been getting very strange/unwanted touchscreen issues for a while now. It seems to happen randomly and for hours at a time. When I press the power button to wake the phone and turn the screen on, I can't even drag the unlock slider to unlock the phone. It takes numerous wake/sleep power button presses until I can get the screen to respond to my finger. Sometimes I'll be typing and it will go crazy and highlight buttons back and forth quickly, usually two or three letters almost always off to the left side of the screen. When this happens I am unable to get it to stop or register any other screen presses. I have to press the power button and then press it again to wake it and I'm stuck at the unlockable lock screen. Only after repeated attempts does it finally get through and the problem will go away for a while, only to come back later.
I have used the program 'Dotty' to track the touch points and I noticed that it will sometimes show a multicolored touch point off to the left of the screen and it will jump around, and it won't detect any other new touch points.
Soooo I think my screen touch sensor is messed up somehow. Does anyone else have this happen? Seems to have started when I flashed the kernel to get rid of the 30 fps cap. I have recently flashed Fresh 3.1.0.1 and still have this problem, different kernel with that rom correct? I'll try to get a video up sometime to show this in action...
Yes, I've been having the exact same issue. I even did a hard reset, with the assumption that it was an app. My plan was to add them back slowly until I got the issue, the problem was it happened as soon as the phone rebooted on the reflash. I have no idea what the issue is, but its very frustrating.
I'm running 2.2 stock...
Some people have reported touch screen problems with netarchy's kernel. There is usually a revision to correct this problem for people who are experiencing it. I suggest you carefully read over the OP in that thread and determine what kernel is right for you. There is usually a version specifically for Fresh users also.
MIGHT i ask what widgets are you running??
i talked about it before when running the pre-official ota rom.
it was my htc music widget (half sized one) i had running on the home screen.. caused lag like a mofo, couldnt swipe most of the time, capacitive buttons wouldnt react, pressing the app drawer button wouldnt respond till 5 seconds later...
AS A MATTER OF FACT.
im running fresh 3.1.0.1 + latest kernel + music widget on home screen.. LAAAGGG like before. removing it makes things snappier again.
YEP. Its happening again.
when i ran the STOCK Official rooted rom, with music widget on home screen didnt produce this lag and poor touch input, even with kernel it didnt produce this problem.
Mine is fine, no screen problems!!! stock rooted rom!!
MyTouch 4G keep turning off the display seemingly at random intervals and it stays off many times for long periods before it starts to behave normal. All other functions such as phone, alerts, receiving mail etc work normal while it is still in that state. In addition to the above, I also see quite a bit of curcial_oj_early_late_resume errors and a few others using OS Monitor to view the message log.
Here is what i have found out from 2 months of trying to fix it:
1. All buttons are always lit while this happens as if the screen was actually on (being used) - it even turns off the screen in the middle of using an application.
2. It receives calls, mails and messages as usual but the screen stays black. If I play with it, swiping to answer call, sometimes I am able to answer the call and talk normal.
3. At it worst times I stays blank/black even before the splash-screen and even if I try booting into recovery mode.
4. However, most of the time the blank screen appears just right after the splash-screen and the phone continue to boot normal.
5. Right after periods that it stays up long enough for me to see and flash a new ROM, it will behave for a while ... even hours normal ... then it starts acting up.
6. I tested it once while it was in boot mode and the screen stayed on for a very very long time without any problems (guess ruling out heat related?)
7. Even with different ROM versions it still occurs.
8. When it first happened was due to a battery drain (battery was changed to rule that out).
9. It behaves like a radical energy manager turning off the screen (why?) until a condition is meet. (recently used SetCPU to lower processor speed to minimum just in case of heat related ... did not work)
10. Power button has no effect on halting the problem once it is acting up
11. Problem seem to occur quicker after a ROM install as time progresses.
What has been done : (what OS routine or setting could survive this? ...)
1. Many complete wipes and re-installs (10+) via clockworkmod manually or ROM manager. (Many different Cyanogenmod ROM versions tried)
2. Changed battery.
3. SD card Format and tried different SD card. Also tried without SD card or SIM.
4. Tried different versions of busybox.
5. Lowered CPU speed to a constant 245Mhz
6. check if it is triggered by pressure, movement, or light ... (proximity sensor appears to work perfectly ok when I do take a call)
7. Sometimes the only way i can get the screen back on is to keep calling the phone and playing around with using the proximity sensor to trigger the wake. Takes hours of trying before that works though.
8. Tried "stay awake while plugged in" setting ... did not work
9. Tried running without adding any apps except those that came with ROM ... didn't work
10. Increased the screen time-out interval ... (even from ROM install it seem to ignore this time-out) ... if the screen stays inactive for 3 sec it shuts off the screen ... keep doing so until the interval get longer and longer
11. Used and Android antivirus to scan ... no problems found
12. Recently changed to Virtuous Unity which helped be bring it back from display off state with a press of the power button (pressing once to stop it -all button lights go out, and once more to bring the display up) ... but still turns off display frequently.
... few other things tried, but you get the idea.
Oh yea, I perm rooted from a while back and it worked perfectly for months before this started happening ... it started before I even considered to flash my first ROM.
I've got a few problems lately and I have no clue how to go about fixing them.
I'm not sure when it caused the problems, but I'd like to keep settings and apps that I've gotten now. I see constant factory resetting as a workaround rather than a fix. The last thing I did before I got these issues was plugging the phone with an USB cable to a Windows XP computer without installed drivers for the phone. There was a movie running in the background in MX Player and I noticed that I'm unable to unlock the phone.
First off, the lockscreen is bugged. When I try to unlock the phone the screen stays blank, but the button LEDs are glowing and vibration works if I hold the power button, suggesting that the system is still working. I tried turning the CRT animations on/off to no avail. An interesting detail is that the lockscreen that appears just after booting up the phone shows up and works fine.
The second problem I have is some of the GUI being glitched. It occurs to for example the startup lockscreen and power menu, as in the attached picture.
To make sure this wasn't a hardware fault I did a complete reflash of the phone using KDZ updaters and there were no glitches in stock ROMs. After installing back the recovery (Clockwork 6) and restoring the backup of this SDSL4 the issues are still present.
This just started occuring this afternoon before and after I installed the latest ZVA firmware:
1. The "Home" soft button responds to my touch - as in I get the visual and haptic feedback as if I've touched the soft button but it refuses to actually DO anything. I can hit the Home button on any screen and any app and it takes me nowhere.
2. The Lock screen is no longer activating - as in I let the screen hit the timeout and let it set for a few minutes. If I try to "knock" on or use the power button, it opens right back up where I left it with no Lock screen.
I hope this makes sense. I'm really stumped here. Like I said, it just started happening this afternoon and I figured that it was some weirdness to due w/ the pending OTA update. After installing the OTA update, the problems persist.
I'd rather not do a factory reset, but I will if I must
kitkat disaster
metar0n said:
This just started occuring this afternoon before and after I installed the latest ZVA firmware:
1. The "Home" soft button responds to my touch - as in I get the visual and haptic feedback as if I've touched the soft button but it refuses to actually DO anything. I can hit the Home button on any screen and any app and it takes me nowhere.
2. The Lock screen is no longer activating - as in I let the screen hit the timeout and let it set for a few minutes. If I try to "knock" on or use the power button, it opens right back up where I left it with no Lock screen.
I hope this makes sense. I'm really stumped here. Like I said, it just started happening this afternoon and I figured that it was some weirdness to due w/ the pending OTA update. After installing the OTA update, the problems persist.
I'd rather not do a factory reset, but I will if I must
Click to expand...
Click to collapse
same here, my tmobile d801 updated to stock kitkat via OTA, i was able to keep root but I was encountering "BLUETOOTH" battery drain even when bluetooth was not enabled so i did a factory reset and got a black screen with white error message
"boot certificate error"
after that the phone reboots but i have the same problems
1. Home button does not do anything but does respond to touch.
2. Notifications are not working anymore.
3. Lockscreen is not working even when enabled in settings
4. I cannot factory wipe, from settings or using volume down + power button.
5. Settings are in a list view instead of tabbed.
:crying:
kombochekenyere said:
same here, my tmobile d801 updated to stock kitkat via OTA, i was able to keep root but I was encountering "BLUETOOTH" battery drain even when bluetooth was not enabled so i did a factory reset and got a black screen with white error message
"boot certificate error"
after that the phone reboots but i have the same problems
1. Home button does not do anything but does respond to touch.
2. Notifications are not working anymore.
3. Lockscreen is not working even when enabled in settings
4. I cannot factory wipe, from settings or using volume down + power button.
5. Settings are in a list view instead of tabbed.
:crying:
Click to expand...
Click to collapse
Bringing this old post up as I just now encountered this on my AT&T LG G2. It occurred when I was using Google Maps which then crashed and caused everything to freeze. Upon reboot, I get the exact same issues as stated above. What was the outcome for you guys? Did you end up doing a hard reset?
Everything appears to be functioning with the exception of above. I'm suspecting a software issue with the home launcher as the soft keys are responsive but the Home one. The Notification Bar lags when trying to drag it down, but none of the notifications are functioning. I also noticed a significant amount of lag. Prior to the "crash" my phone was flawless with no lag for the past 10 months. I absolutely have no clue what just happened...
Was taking a pic with my 6P, and it sort of locked up on the camera screen(status bar pull down working but wouldn't respond to any touches like back, home or just going into settings from the status bar). So I just held the power button down to reboot, and now my display doesn't even turn on. The phone is running, was playing Pandora automatically when I went to my car, and can feel it unlock with the fingerprint.
Phone had been having issues with touch for about a week prior, as in it would stop responding to touches for 1-5 seconds or so constantly. Did a factory reset and wiped everything, but issue persisted.
Anything I can try here or is the display done? Guess I can't get into ADB mode because the phone is set to 'charge only' when connected to PC and I can't change it? Phone is rooted running Pure Nexus rom.
Don't think I'd bother with replacing the display if that's the fix, was ready to upgrade.