The top of the screen where the notification bar is is unresponsive...sort of. It registers touch like normal, except it thinks I am touching the screen about half a centimeter below where I am actually touching it. This is only present in the status bar area. Also, it is probably not a software issue as I have wiped the phone and installed other roms and kernels since the problem came up. Also, what's strange is that every now and then, it will just start working like normal again, and then stop after a while.
As a work around, you can use a custom launcher (adw, go, apex) which has homescreen swipe gestures and use something like "swipe down" to access the notification bar. If you notice this issue impedes your everyday use, swipe gestures are probably your best solution.
Related
My watch was working perfectly before the 5.1.1 update, but ever since the update, it is slow to wake, unable to swipe away cards from the watch face without opening them, the touch sensitivity is TERRIBLE....have to swipe over and over to get it to register, and for notifications I am unable to select "ALL"...can only select "priority" and "none".
Is anyone else having these problems?
5.1.1 problems are being discussed here if you're not aware:
http://forum.xda-developers.com/zenwatch/general/android-5-1-1-ota-files-online-t3109484
No problem in starting a new thread, though.
nhpilot43 said:
Is anyone else having these problems?
Click to expand...
Click to collapse
I noticed that the touch screen seems derpy to me too. Something is definitely weird with the toggle shade thingy. I'm having the same problem with selecting "all". You can get it, but you have to find the exact spot below and to the left and tap frantically like a dozen times. I reccomend using the test app in developer settings and open the touch test. It will display a small grid and it will trace all your touches. Don't worry if it says fail. Just notice whether or not its tracking your finger. To get it to pass you have to turn the lines green by swiping in a certain direction. Mine tracks perfectly so, for me at least, the hardware is fine. Definitely a software issue.
-Andy
Sent from my Apple Newton.
Yesterday I installed the Android M preview on my phone, and so I had to do a reset on my watch. Now all of the touchscreen wonkiness has gone away, and it's working fine!
Before I was unable to get the app list to appear by swiping from the right, but only by tapping once. Also, I couldn't swipe in the center of the screen in the mode selector shade, but only above or below the row of icons. Now that's all working as well.
I have a Lenovo P2 for around 3 months now. It works wonder but a few days ago, I woke up and noticed that the bottom part of the phone is not responsive to anything other than the navigation bar. Anyone else have this problem? I have read several threads from March and it seems that they have the same problem.
Methods I tried to fix it :
1. Resetting the phone to factory default.
2. Removed the screen protector.
3. Install the November security update.
None of this work. Before that day, it works perfectly, now the touchscreen on the bottom part only respond to the navigation bar and not any other apps. I ran test using Lenovo Companion app and it seems that it doesn't recognise the bottom part as a touchable area either. Swiping up the navigation bar also doesn't work, when horizontal the swiping action works on the top part of the phone not the bottom. Although it's possible to swipe up from the bottom, it takes many repeated quickswipes before it show up, I don't think it's lag either since the top part works instantly.
I am considering taking this to a Lenovo phone collection shop for claiming warranty. If this is software, the same might happen again after they fix it.
Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
marshle said:
Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
Click to expand...
Click to collapse
I tried to replicate what your talking about. However, I couldn't do it. Maybe because I'm using Nova launcher, which may be a viable option for you. A factory reset might be helpful, however, we all know how much fun that ISN'T! Definitely an interesting issue your having. Then again, I think these devices have a mind of their own at times ?
Thanks for your reply. Forgot to mention, I have tried safe mode and done a factory reset and it did not remove the issue. It seems after a factory reset you are still on Oreo 8.1, so I'm not able to confirm it the issue exists in 8.0. I also have tried Nova Launcher.
Every once in awhile, my notifications pull-down won't pull down.
If I lock the phone, then unlock it, the pull-down starts working again.
It's been like this through multiple clean OS re-installs.
Am on Magisk 17.3.
I've had more software bugs on the PXL3 than any other phone before, including the PXL1.
I have the same damn problem. It just doesn't work all the time. I also had the issue of bright white screen on double tap to wake. So, I called Google Support for this, and the guy on the other said made me clear the cache of the phone app, force stop it, turn the phone off for 2 mins and then restart for both issues. I even asked him how this relates to the fingerprint sensor not detecting, he replied some stuff that, phone app controls the vibration and the display waking up.
Of course both problems does not occur for me frequently, so after that procedure I did not encounter the white screen problem, but fingerprint gestures were still kinda hit and miss. Although they work pretty good now, less miss count. For me they work when I swipe just the edge of index finger lightly, also if finger is very dry, it doesn't detect.
I tried the pulldown five times while this logcat was running.
I'm on Nova Launcher but think it happened on stock launcher too.
After installing a new display module on my OP5T, I noticed something weird. The display seems to be perfect, either original or a very good one. Bright, perfect color, no issues with it whatsoever. I've tested it in multiple apps (like Draw on screen) and it works perfectly, recognizing every input, never interrupting the line while I drag. All the buttons I press on the screen in apps work perfectly. When typing letter never gets missed.
However, it does have a SLIGHLY less sensitive touch. Like, if you very lightly tap it with a finger, it won't register, while before, it would. The difference really is miniscule. I usually wouldn't tap that lightly on it either way. However, it works up to be an annoyance, because now certain "swipe left-right" actions lack a certain "inertia" to them, which I think is because of this.
Like, before, to move around the launcher screens, I would just swipe sideways lightly and carelessly and it would switch to the next screen, now it will start moving and roll back. To make sure I switch a screen I have to apply effort with my finger. Same thing with opening notifications or app drawer.
Is this a hardware issue? Faulty touch? Or can I just increase sensitivity a bit with some software tweaking?
dude i am also in the same boat. Did u by any chance buy the replacement screen from lcdbaba?