Hey guys/gals!
I have been rooted since the second week and just started noticing this.
I have removed voodoo and still notice the same problem.
This is what happens.
The screen will go blank and I can still touch the soft keys and they illuminate but don't actually get pressed (as in I don't get the feedback). I wait 30 seconds and try to turn the screen on, and it will act like I just returned back from the Airplane mode.
This started happening ever since I used the clockr widget, oneSeven widget, and desktop visualizer to do the wp7 style icons. I am not sure if any of this caused the problem but I started having this problem since I started using these items.
Thanks for all the help.
The phone has been working very well, no problems of any kind. It is rooted and I'm using Go Launcher along with Widget Locker for the lock screen.
I just updated the Widget launcher application and everything was working just fine.
However, the last time I woke the phone, the display was bonkers. The lower 1/3 of the screen was grey, over writing the icons for the functions located there on the home screen. When I scroll through the home screens, the lower 1/3 continues to be greyed out. However on close inspection, the underlying icons can bee seen and are activated with a touch as normal.
The overwriting seems to be somewhat of a repeat of the top 1/3 of the screen. With the moto lock screen there is a digital clock displayed in the upper part of the screen and that is showing up in the lower third also.
This greying out is more like a Ghosting effect. The screen also has a general background flicker in the upper section that is not greyed out or ghosted over. I did nothing like dropping the phone or dunking it. This does have what I would somewhat characterize as connection issue. BWDIK.
Does anyone have any idea as to what could have caused this to pop up as a problem? The new version of Widget Locker seemed to be doing just fine and I had configured it to take more icons in the ICS default theme. Everything was going great until it suddenly was not.
Suggestions or accounts of similar problems would be appreciated. I sure hope there is a cure. The phone has been great and darned capable. I'd hate to have to change it out.
Reboot your phone.
If that doesnt work, make a backup in Clockwork and wipe data.
If that doesn't work, it's hardware related.
Sent from my DROIDX using Tapatalk 2
Thanks for the help.
Could you be a little more specific as to how to make the backup and then restore?
I've restarted the phone several times. That won't clear it up.
Download droid2bootsrtap>install>flash recovery>reboot recovery
Scroll to backup/restore (use vol keys select w/ camera key)
Select backup, let it do it's thing
Select wipe data
Reboot
Thanks for the additional help.
That did not seem to get the job done for me. I still have the problem with the top third of the screen being displayed again as an overwrite of the bottom third.
One odd thing did occur while I was working on this. I had the phone connected to the charger. It was in "sleep" mode with a dark screen. I picked up the phone, pushed the wake up button top. and at the same time I disconnected from the charger. When the screen first displayed it was displaying correctly and clearly with no overwrite. I don't believe I have a failed display in the sense of dead sections or pixels. It seems that there is some cross connection in how it is being addressed so that the upper one third is being written twice, one of those being an overwrite of the lower one third. The icons that should be showing in the lower third dispaly are visible through the "fog" created by the overwrite.
I have contacted the local smartphone Mr. Fixit and ordered the new screen. The problem may be deeper than that though. Any other suggestions would be appreciated. I like the way the phone operates and am getting to understand it after about a year of working with it. It is rooted with the handy WiFi tether operating, along with a few simple customizations. It would be great to get it sorted out as I don't want to go the upgrade route at this time.
Have you tried reSBFing? I had a similar problem, except the lower 3/4 of screen went black. Got an insurance replacement, but when i was wiping my old phone, i SBFd, and the screen worked again. Granted, i still had to send the phone in, so no idea how long it would've lasted.
Sent from my DROIDX using xda premium
Nothing to do with SBF'ing. The phone is rooted, and it worked the first time, several months prior to the problem.
I finally got the screen replaced and that part is working well. Nice and bright with no ghosting of another section. However, I now have developed a problem with the dialer turning off the screen when the call starts dialing. No capability of using number pad or even hitting the End Call button. Returns to the default lockscreen when call ends from a disconnect on the other end. still a great mystery.
Question: how's your camera working?
Sent from my DROIDX using Tapatalk 2
Hi,
The navigation and status bars, and notification shade (presumably because they are controlled by the same system process) are freezing very often on my Nexus 4. It seems to happen after unlocking the phone when it's been on standby - either the little dotted circle persists for 2-3 seconds or the navigation buttons begin the 'fade in' animation, and freeze during it for a 2-3 seconds. The status bar is also affected, the time disappears from the top-right corner and the notification shade is unresponsive while frozen, then moving rapidly as it catches up with my finger movements that occurred during the freeze.
The most confusing part of the issue is that it has persisted across a full system wipe. It originally began on PA 3.99, and so I decided to do a factory wipe and go back to stock, blaming the ROM. I made sure to wipe all storage and settings, caches and restore the stock recovery. This worked for a short while but the issue has returned as bad as ever. It seems to go away temporarily when I reboot, but returns fairly soon. The only link between the installations is whatever settings are restored from Google's servers when setting up the phone. Could they be at fault? Has anyone else had the issue, or does anyone know of a fix?
Thanks.
Problem: My vs980's touchscreen is at times erratic and sometimes will not register touches in the statusbar area therefore rendering the phone mostly unusable. This first occurred about 2 days ago but wasn't bad. It went away and i didn't think anything of it but today it's back and much worse. Note that i didn't flash any new rom or make any real changes to my phone in the period that this happened.
------------------------------------------------------
Info:
Phone: vs980 ROM: Xdabbeb's VS980 1.1.0
------------------------------------------------------
Symptoms:
-The screen usually won't register taps/downward swipes in the statusbar area.
-Pinching the phone tightly together doesn't help any(it had been reported that doing that fixed some issues that some people had)
-Phantom taps in the statusbar area (which cause the screen to turn off. this happens as frequently as 10-ish second intervals)
-The phantom taps/Unresponsiveness seem completely isolated to the statusbar area (i mean, to the best of my ability to detect, exactly the pixel space the statusbar takes up, i tried this at 480 and 400dpi)
-Knock Code will not usually work with the screen off. Sometimes it's iffy with the screen on.
-The screen seems to be able to detect swipes in a direction parallel to the statusbar (ex: i can move a launcher screen left/right from the statusbar area, but it won't register a tap a downward motion in the statusbar area)
-I booted into recovery and weird things seemed to happen. There seemed to be a few phantom taps(which is dangerous) I reflashed my rom and that didn't help.
-I left the phone alone plugged up in a window for 30 minutes or so. The problem went away for 10 or so minutes and came back. Not sure if that matters..
-When scrolling or anything involving movement, the phantom taps basically make it hell to do anything
-----------------------------------------------------
Things I've tried:
-Updating touch fw in hiddenmenu. It appeared to fix it for all of 30 seconds. Knock Code worked with the screen off. But then it just came back.
-Reflashing my rom
-Rebooting
-Wiping cache/Dalvic
-Cleaning the screen/Hands
----------------------------------------------------
What i haven't tried:
-Complete TOT back to stock- I really don't want to do this
-Any more ideas?
----------------------------------------------------
Help is very much appreciated
Just got a Moto X Pure (Style XT15752) (Dual SIM India variant) a few weeks ago to replace a OnePlus that refused to charge.
Running on TruePureX MM ROM at the moment with Frankenclark kernel.
Had a few issues with ghost touches on the navigation bar early on but I always assumed it was due to moisture on the screen or something because it would always disappear in a few seconds (and in the meantime I'd give the screen a wipe with a cloth or such)
But now the nav bar completely refuses to accept touch input. When I enable show touches (in developer options), touches on the navigation bar area are not registered whatsoever.
Saw a couple threads with similar if not exactly the same issue but no solution as such.
The weird thing is that this part of the screen works perfectly in TWRP suggesting a software issue.
Tried wiping system and reflashing the ROM already with no success.
Any suggestions guys? Trying to fix this without going to service as that will take a while and I don't have a spare phone to use in the meantime. (My work seems to revolve around being connected 24/7)
P.S. Also using Button Savior to use the phone at the moment. Only the Home button works, not back and multitasking.
VikramK123 said:
Just got a Moto X Pure (Style XT15752) (Dual SIM India variant) a few weeks ago to replace a OnePlus that refused to charge.
Running on TruePureX MM ROM at the moment with Frankenclark kernel.
Had a few issues with ghost touches on the navigation bar early on but I always assumed it was due to moisture on the screen or something because it would always disappear in a few seconds (and in the meantime I'd give the screen a wipe with a cloth or such)
But now the nav bar completely refuses to accept touch input. When I enable show touches (in developer options), touches on the navigation bar area are not registered whatsoever.
Saw a couple threads with similar if not exactly the same issue but no solution as such.
The weird thing is that this part of the screen works perfectly in TWRP suggesting a software issue.
Tried wiping system and reflashing the ROM already with no success.
Any suggestions guys? Trying to fix this without going to service as that will take a while and I don't have a spare phone to use in the meantime. (My work seems to revolve around being connected 24/7)
P.S. Also using Button Savior to use the phone at the moment. Only the Home button works, not back and multitasking.
Click to expand...
Click to collapse
Go here: http://forum.xda-developers.com/moto-x-style/help/navigation-buttons-issue-t3497985