On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Yes, this is me too exactly. Same thing with the dev option too. Not sure if I should wait for 8.1 or if it's hardware and RMA it. Frustrating because I like this phone.
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
I have definitely noticed this as well, happy to know it wasn't just me
cb474 said:
I noticed this on my phone, clicking around in the settings and on the back and home buttons. I then did a factory reset (because of a separate issue where the location icon was always displaying in the notification area, even when not in use). After that the issue seems to have gone away. So it would seem to be software issue. I suggest trying a factory reset (though beware that this wipes everything on your device).
P.S. nonexistent, I'm impressed that you joined the XDA forums in Dec 2010 and never posted a comment until now. Of course, you might need to change your screen name to "existent," now that you're out in the open.
Click to expand...
Click to collapse
I tried a reset but the issue still showed up. In fact it happened twice on the first time setup stuff afterwards. I called Google and we went through the motions and reset it from recovery mode but it was still there when I was testing it the next couple hours. Anyway, we're doing the RMA thing. I'll let you guys know how it works out when I get my new phone.
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
I find that it occurs when I'm in a small room with the heat turned up. The sensitivity of the touch screen seems to depend a lot on moisture. If I keep my fingers moist (or wear a touch sensitive glove) it works a heck of a lot better.
ritzack said:
Got my replacement and the problem still exists. It even happens just a couple screens into the initial setup after a factory reset from recovery mode.
Click to expand...
Click to collapse
That's good and bad news I guess, hopefully just needs a software update. I have a replacement coming Monday, but I kind of expect no improvement and that this is just a common thing that a lot of people aren't noticing
I noticed that for a while in Google Play Books, in which I tap the screen frequently to turn pages. I tried a factory reset, which didn't help. I tried running in safe mode and testing on Maps and still had a problem, although less frequently (a higher percentage of taps worked). Then it started to work better. We'll see if that lasts.
I tried flicking as opposed to tapping and flicking always works.
I'd suggest posting on the Pixel product forum or calling support, so that Google becomes more aware of the issue. There are some threads on the subject on reddit and the product forum.
Out of interest are you noticing it any particular parts of the screen?
I've noticed it a few times but it's been on areas of the screen near the edges.
I assumed it was some sort of palm rejection thing going on it the background with it thinking I'm accidently mashing the display.
With me it was the right edge toward the middle, as that's where you tap to turn the page in Play Books.
I get it on the back button frequently, but it happened just now in the middle of the screen when I typed the text input box to start writing this
I think this is the whole OS hanging/freezing briefly actually, not a touchscreen input issue
- Pressing the hardware unlock button can get ignored (both locking/unlocking)
- Scrolling from a quick flick + release can suddenly stop (no additional inputs)
So most likely this is a software issue, hopefully fixed in an upcoming update? It's kinda annoying
Did you change the DPI or font size? I go back to default and it seems that everything is good now.
---
update: no it happens again…
nonexistent said:
On my pixel 2 tap inputs occasionally don't register, I've had it happen in the android system menu, the android back/home buttons, chrome, etc. Is anyone else experiencing this?
My phone's basically on stock default settings, nothing unusual running. Not sure if it's only tap inputs getting dropped or the whole system locking up temporarily. Turning on "Show taps" in Developer options I can see there's no visual effect when a missed tap occurs.
Click to expand...
Click to collapse
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Haven't changed the DPI or font size
LimitsX said:
can you be more specific? I just got Pixel 2 - black, 128GB (Canadian). I can touch and the UI responds well. But i want to test it out thoroughly..
Click to expand...
Click to collapse
I can trigger the system hang/"missed input" most reliably by visiting any m.reddit thread in chrome and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
nonexistent said:
Haven't changed the DPI or font size
I can trigger the system hang/"missed input" most reliably by visiting m.reddit in chrome (any thread w/ comments) and spamming tap on the [-] next to the username of any comment to collapse/expand the section. Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
So, I replicated what you told me, 3x. I didn't miss any taps, and no system hang/missed input..
hmm
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
nonexistent said:
Turning on Show Taps from Developer Tools in the system menu I can see taps being ignored sometimes
Click to expand...
Click to collapse
Yeah, sometimes I see a tap register visually on the screen, but the intended action doesn't happen.
redandblack1287 said:
Got my replacement and it has been much better so far. Still a few dropped inputs but I think those may be false positives because I am hyperfocused on it. Pretty sure I have always had to double click occasionally on all phones at various times.
Click to expand...
Click to collapse
It's funny. I had the issue. Did a factory reset. Felt like it was better. But now that I'm thinking about it more I notice it a lot. So I can't tell if it's really different. Before I figured I'd made a mistake. Now I think it's the phone. Damn you phone!
Anyway, I notice that the issue tends to happen more or less randomly, at any position on the screen. Also, sometimes the same tap fails to register twice in a row, but once it's starts working all subsequent taps that come in a row work (say I'm clicking through a lot of menu items in some settings). So maybe that lends some credence to the idea that there is a system for registering the taps that is not waking up and once it does it works fine.
Perhaps related, I have my ambient display set to wake on double tap. Before the Nov update it hardly worked. Now it seems to be working reliably.
Related
Hello everyone,
It has been a while since I ventured through this forum, but it seems that y'all may be my only hope.
I've been suffering through this glitch/stutter that, when scrolling, the phone registers my finger as taps everywhere my finger slides. All I simply need to do it remove my finger from the phone and I can continue scrolling like normal. It is super annoying and I cannot find out what causes it, it just seems random. It never happened on any of my Nexus phones in the past.
Now, here's a list of things I've tried in order to fix it:
- Safe mode
- Factory Reset (Restore from Google account)
- Factory Reset (New Device option)
- RMA'd through Google support and received a new pixel and the problem persists (even after going through the steps above on the new device)
Here is a short video of the glitch while it is happening.
https://goo.gl/photos/GysQXd82MexVkk836
(Hopefully that link works)
Note: the glitch will not stop until I take my finger off the phone, you can tell when it is happening when I scroll over the share button and it registers as a tap.
If you guys have any suggestions, I'm ready to try anything at this point. I don't want to go through Google support because I know they'll send me yet another Pixel (I've already talked to them again and that was their solution, I told them I'll try a few more things) and I feel like that is a waste. I'm almost 100% positive that this is a software glitch, not hardware.
Thanks!
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Jaxidian said:
Was that the Reddit app or a browser window? I'll try to reproduce if you can tell me exactly what you were running. I do not have that behavior in the XDA app as I try it right now.
Click to expand...
Click to collapse
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Skillfulshoe said:
Hey thanks for the response. I've gotten the glitch to happen all over. The Reddit app as you saw in the video, the chrome app, even scrolling through the list of apps in the stock pixel launcher. So I'm really not sure how to have you replicate the problem.
I'm thinking it is because certain settings in the settings app since Safe Mode disabled all third party apps when I tried that. I have night light enabled to turn on at dusk, I have ambient display off, auto brightness off, etc. Nothing too out of the ordinary.
I thought it may have been because I have location settings on high accuracy and when the phone pings for location maybe it bogs down the rest of my phone at that certain time but there's no way I can try and replicate that. It's a long shot anyway.
Click to expand...
Click to collapse
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Jaxidian said:
I just tried reproducing this by going to the app drawer and scrolling up and down while being sure my finger passed over both the home and app switcher buttons a good 50 or so times. The ONLY time the nav bar buttons were triggered were if my finger completely left the screen and went into the bezel - clearly that's not your problem. So I don't think I can reproduce the glitch.
If you think this is caused by your specific set of settings configured, you can always rule that out quickly with a factory reset. Just do a factory reset, set things up quickly, go ahead and login with your Gmail account so you can download some apps but do NOT change any non-basic settings. For example, go ahead and setup WiFi but do NOT change any display, input, or accessibility settings (especially the last thing there - the accessibility settings are often glitchy themselves). One setup, install a bunch more Google apps then try to reproduce the behavior again in the app drawer. If the behavior continues, then you may have a bad touchscreen sensor!
One last thing: Any chance you have really dry fingertips? Dry skin could always be your problem here!
Click to expand...
Click to collapse
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
I'm not sure if this is caused by a bad touchscreen sensor because I've had the problem on two separate Pixel phones so far. Or maybe I just got super unlucky with two faulty phones.
I don't think my fingers are too dry. If all else fails, I'll try moisturizing them I guess. I've never had this problem on all my other phones though, but I guess you never know.
Thanks for the help.
Skillfulshoe said:
I guess I'll try a factory reset and not mess with the settings although that kind of defeats the purpose of using this phone the way I want lol.
Click to expand...
Click to collapse
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Jaxidian said:
I recently had a similar situation (different bad behavior) when helping my mother-in-law with a vision disability. Atrociously unacceptable performance, multiple phones. Turned out the triple-tap-to-zoom feature in the accessibility options was the culprit and disabling that one checkbox made all the difference.
I'm not necessarily suggesting you must use defaults forever, but if this is a setting of yours, let's first prove that it's a setting before going through the long process of finding out WHICH setting it is. Does that make sense? If we reset settings to defaults and it continues, no need to spend all that time - you've got a broker phone. If that does fix it, no need to return the phone, it's a buggy setting - let's find it to see if you can live without it one way or another. It may be a major deal breaker out it may be something you really don't care much about.
Click to expand...
Click to collapse
Yeah I totally understand what you're saying. I just have gotten frustrated with this. I know it isn't a big deal honestly.
gadgetgaz said:
I think I get that issue now and again, usually whilst scrolling in chrome. I decided it was due to holding a finger on the screen just long enough (before starting to scroll) to register the press as a "select text" event.
Click to expand...
Click to collapse
Yeah that could be what causes it. Maybe it is just the way we are scrolling and how Google has calibrated the screen touch sensors.
Possible Fix
So I went into accessibility settings and changed the duration you need to hold your finger down to do a long press to medium (from the default as short). It seems that may have fixed it. I haven't experienced the glitch since I've done that change.
Here's to hoping that did indeed fix the issue.
Thanks everyone.
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
computerslayer said:
About three months ago my Pixel 2 (purchased new from Google) began having an issue where it becomes unresponsive or extraordinarily delayed on responding. It almost always happens when I'm waking the phone up from being locked. When it happens, the phone will eventually unlock but everything reacts several seconds after contact (power button, taps, swipes). A reboot or power down fixes the problem, but is always necessary.
I switched to Project Fi around that time and thought it had something to do with the switching between CDMA and GSM (Sprint/US Cellular vs T-Moble) towers, but I've switched to T-Mobile (a solely GSM provider) since and the problem persists.
I am running Android Pie (stock). My bootloader is unlocked and I do have Magisk installed. No TWRP. I don't have any obvious troublemakers installed (like Xposed, for example) and only a few apps that even use root (Cerberus, Adaway, and Nova Launcher).
I have heard about the Pixel 2 XL having a hardware issue that results in unresponsiveness and that ultimately requires sending in the device for a replacement. Is this the same thing?
Any advice would be much appreciated. If it would be helpful, I can produce logs, but I'll have to wait until it happens again to offer logs that might contain clear indications of what might be happening.
- Computerslayer
Click to expand...
Click to collapse
Do you have the navbar hidden by any chance
crixley said:
Do you have the navbar hidden by any chance
Click to expand...
Click to collapse
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
computerslayer said:
Well, I have Nova set up to hide the dock unless I swipe up (or down) on it. I can't seem to find a setting about hiding the navbar. Where should I be looking to check?
Click to expand...
Click to collapse
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
crixley said:
Did you install any apps to hide your navigation bar? Is it always visible? Immersive mode apps for example
Click to expand...
Click to collapse
We're talking about the back button and the new pill gesture button, right? If so, then no I haven't installed anything to hide those: they are always visible.
Well, after 24 hours, I had the issue resurface. Unfortunately, the logging app I was using (matlog) froze up with the phone and produced a blank text file. While rebooting restored normal function of the phone, I can't produce a log as a result.
It occurs to me that while I am not disabling the navbar, I do use a function of the Cerberus anti-theft app to disable the notification bar while locked. Could this be the source of my issue? If so, is there any way to confirm this?
In the meantime, I've disabled that function and will see if the lock-up occurs again.
I'm curious where you were going with the question about the navbar. Could you tell me more about what you were thinking it might have been?
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
computerslayer said:
I went ahead and disabled the 'block status bar' function of the Cerberus app and the problem has not resurfaced in over two days (it was occurring several times daily). Although I can't definitively prove it, I think the culprit was the app.
Thanks for the time and assistance!
Click to expand...
Click to collapse
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
crixley said:
Sorry I didn't get back to you I read this a while back and totally thought I responded. Yeah anything that hides the status bar or navbar from the system UI at all times is known to cause wake issues. On my essential phone it would require me to restart it to actually get the screen to come back on. It's called the deep sleep of death or something haha
Click to expand...
Click to collapse
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
computerslayer said:
Hello Crixley,
No worries at all - I'm always grateful when anyone responds around here because I know that we're all balancing regular life and our hobby time!
I'm relieved to hear that it is a known issue, though I'm going to miss the functionality! I wish Google would build some kind of equivalent security measure so that the network state can't be changed while the phone is locked. I'm guessing that this issue is exactly why they haven't gotten to it (yet?).
Thanks for your time & support, both here with my issue and across the forums.
Peace,
Computerslayer
Click to expand...
Click to collapse
I'm glad to hear it's fixed for you!
I try to help as much possible, I remember how good it was to have people help me when I needed it and sometimes I need a hand as well.
Sorry for the weird title, I didn't really know how to concisely describe this issue. I still don't fully understand what triggers it but basically I've noticed that if I lock my phone while on a text chat (in either Textra or Facebook Messenger but probably includes all text chats), then unlock it to reply, I can't click on the text input box or hit the navbar back button for 3-5 seconds. This can also happen while my phone is unlocked when I'm switching through apps so I wouldn't directly blame the action of being locked. I know the phone isn't frozen because I can still hit the back button at the top left corner of the screen fine.
It almost looks as if though it's navbar-related because the pill is white when I unlock the phone, then after a few seconds when it's responsive again the pill is grey. My previous phone was a Oneplus 3 and it never had any issues like this (although it had physical buttons for navigation, not a navbar) so I'm wondering if this is an issue or if this is by design for some reason. I've tested each of the navbar options (traditional navbar, pill, and gesture) and none of them resolve the issue so maybe it really isn't.
One other detail I noticed is that the cursor also doesn't blink for those 3-5 seconds, and then when it starts blinking again I can start typing so it could be something else.
I just find it annoying to have to wait a few seconds whenever I want to unlock my phone and reply to a text and this doesn't seem like regular behaviour, has anyone else heard of or experienced this and know of a fix?
Videos of the issue:
In Textra:
https://imgur.com/X0lw47J
In Facebook Messenger:
https://imgur.com/1IrRfPY
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
ducted said:
It could be part of the same ghost touch bug. Did you tried to disable NFC and see if those input lags reduce?
Click to expand...
Click to collapse
I've had NFC disabled since I got the phone so that isn't it.
I don't think it's ghost touch-related since it doesn't happen sporadically, it just seems to be when I open a text chat app or something too quick which doesn't make sense. Perhaps I can record the issue and upload a video to more clearly show what happens.
I just added videos of the issue to the OP.
That looks weird, did you tried to use the gesture navbar only or the one with all the buttons? I would try also another keyboard just to discard any GBoard related issue.
I've tried every other navbar type (including the one with just gestures and no bar) and the results are the same. I have also tried a different keyboard (Fleksy) and again, same issue. I had essentially the exact same setup as far as apps go on my Oneplus 3 and its fine, so I'm thinking it has to do with either a new version of android or the new OxygenOS but I have no idea.
Maybe it's a common issue but I haven't found any info when searching about it.
I have a P11 Pro, and since I got it, I have always been having the same issue with the tablet waking up on its own quite often, randomly, or even sometime refusing to go back to sleep.
I disabled any setting that might waking it up (tap to wake, move to wake...), and disabled several apps, but it changes nothing.
It's especially annoying since when I don't use a screen lock, with the 5 minutes stay on time I set, it keeps waking and empty the battery quite fast.
Using a screen lock reduce the issue as the tablet goes back to sleep quickly, but still doesn't solve the problem. And I don't want to use screen lock when I use the tablet at home.
Does any you know that issue, or how to fix it?
Thanks in advance!
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Stremon said:
Nothing connected.
Yeah the lid has a sensor, but it does it even when I remove the cover completely or when I leave it closed and not moving.
Yes I did several factory reset, update of the firmware, and yes I'm on the latest one.
As far I can understand, a process on the tab itself is waking up the tab randomly, I just can't put my finger on which app/function does it.
Click to expand...
Click to collapse
Look for battery usage details it should tell, after having show system services ensbled
hashtowent said:
Look for battery usage details it should tell, after having show system services ensbled
Click to expand...
Click to collapse
Nothing visible there either, the app that keeps waking up the tab isn't necessarily taking any battery.
I didn't mention as it is very visible from my profile, but I'm not a beginner with android, very far from it, if I'm asking here it's because I already tried all the obvious things
I am asking if anybody has the same issue and/or was able to fix it. If not, I guess it's just my unit.
You might try this
The command like this:
adb shell dumpsys batterystats --checkin
provides a statistic for wakeups, including the reasons.
Mine wakes up. Can't figure out why either but then I'm not by any means an Android ace. I turn the screen off then after some period of time it'll turn back on. Nothing in the notifications bar the screen just turns back on for no apparent reason. So yes, it is happening to someone else but no answer as to why.
hashtowent said:
Do you have a keyboard attached or some Bluetooth devices like mice?
Does it have a built in sensor for lid close and open when used with the original keyboardcover? That might be causing the issue then.
Did you try a factory reset?
Is the latest system update installed?
Click to expand...
Click to collapse
I'm sad to say that you were right, the magnetic cover was at least partially to blame for the wake events. That's a huge bummer, since I guess there is no way to fix the issue
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
LeNouveau said:
I had this issue.
I said that notifications must not wake up the tablet and it did not appear anymore.
I know there was no notification, but it worked for me.
(in fact, sometimes, I had the impression that a notification appeared for a very short time)
Click to expand...
Click to collapse
Interesting, I'll try that too, thanks
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
hungmung said:
I have the plus not the pro but check if near to wake up is on under the AI Experience Center in settings.
Click to expand...
Click to collapse
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Stremon said:
Everything is disabled there.
But I am quite convinced it comes from the smartcover, as since I enterily removed it, I don't have the issues anymore and the battery lasts weeks (with light usage) instead of 2 days like before.
Issue is that there is no way to disable the smart cover magnet...
Click to expand...
Click to collapse
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
hungmung said:
That is probably it. I just thought I'd offer I had similar happen and had accidentally turned that on so it was turning on every time anything moved near it.
Click to expand...
Click to collapse
Thanks, that indeed makes sense.
And I really wish it was just that.
I'll try again with the smart cover to see if I can do anything about it.
It's the official magnetic cover so it's a huge bummer that it causes issues...
Stremon said:
Interesting, I'll try that too, thanks
Click to expand...
Click to collapse
Hi, I was looking for a solution to the waking up of the screen. In the ¨AI Experience Center¨ there is an option called ¨automatically screen light-up¨. I turned this off, because it said that if sensor detects a face, the screen lights up, and also "other" objects can trigger this screen light up. I suppose the cover is detected while closed. Other object in the range of 0.5m can also trigger this light up. Also deactivated the notifications icons in the status bar, if not doing this, it continues to light up the screen in my P11.
Mine does the same thing...just sitting there and all of a sudden the screen lights up.
Solution:
Settings -> Display -> Lock Screen -> When to show
Turn "new notification" off
I have noticed, especially in Chrome, that my phone often confuses a split second touch of the screen, like when I'm trying to scroll, as a long press. On my previous devices, I can put my finger on the screen and slide a little and hold for a fraction of a second before sliding again, never taking my finger off the display, making it easy to skim without bouncing the screen all over the place, but this same action seems to make the phone think I'm long pressing and sometimes it does it when I'm just trying to flick scroll normally too. It has been driving me nuts and I thought it may just be me since I hadn't seen others complain about it but then today I saw two others say they have the same issue so now I'm curious how prevalent it is.
For the record, I'm running the QPR1 beta 3 but it was doing it on stock .031 too.
@EtherealRemnant
Go to Settings then Accessibility. Scroll down to Timing Controls and change Touch and hold delay to medium.
I can reproduce this issue when I use the full flesh of my thumb to scroll.
In normal use I've had it happen twice or so.
bjevers said:
@EtherealRemnant
Go to Settings then Accessibility. Scroll down to Timing Controls and change Touch and hold delay to medium.
Click to expand...
Click to collapse
This is why I stick around XDA, people with knowledge about the devices we use.
This cleared up --so far-- all of the quirky errant touches and context menus I've been getting the past week
Thank you!
I've seen it happen a few times while in Chrome from scrolling, but I experienced the same behavior on my Pixel 4 XL.
I'll be scrolling past stuf in Chrome, and sometimes it'll read it as " Oh, you clicked this! " then proceed to load that page up.
bjevers said:
@EtherealRemnant
Go to Settings then Accessibility. Scroll down to Timing Controls and change Touch and hold delay to medium.
Click to expand...
Click to collapse
I will try this and report back. Thanks. I didn't even think it could be an accessibility setting.
EDIT: Instantly better, thanks!
Unlike the scrolling issue, I've never had this so perhaps it's something only some devices have.
Nice find! I think the short setting is a little too short while the medium setting is a little too long. I wish they could be adjusted manually like you can with the setting on the Google keyboard.
jaseman said:
Nice find! I think the short setting is a little too short while the medium setting is a little too long. I wish they could be adjusted manually like you can with the setting on the Google keyboard.
Click to expand...
Click to collapse
I'm hoping there will be a patch soon that refines the sensitivity. I agree that medium touch-time is a bit too long when you are intentionally trying to access the context menus, but it's much less aggressively annoying than what I was experiencing with the OS
I no longer own my Pixel but when I did it had the problem. Can't remember where I found this solution but it works.......
Using ADB, I've changed the delay timeout to a non-standard value and it seems to have fixed the problem for me i.e. long click delay is consistent every time:
adb shell settings put secure long_press_timeout 401
p.s. For reference standard values are:
Short - 400
Medium - 1000
Long - 1500
appro77 said:
I no longer own my Pixel but when I did it had the problem. Can't remember where I found this solution but it works.......
Using ADB, I've changed the delay timeout to a non-standard value and it seems to have fixed the problem for me i.e. long click delay is consistent every time:
adb shell settings put secure long_press_timeout 401
p.s. For reference standard values are:
Short - 400
Medium - 1000
Long - 1500
Click to expand...
Click to collapse
I'm not familiar with shell, what would the exact command be, I did try adb shell but entering the above it says secure inaccessible or not found. I would like to try medium setting on 700.
Edit: Nvm I tried again & it worked. I set it to 600 which is better now