When I lift to wake, there is a flash of distortion in the top third of the screen which disappears almost instantly. This only happens with lift to wake and does not happen with double tap or button wake.
Anyone else experience this?
Magic-design— said:
When I lift to wake, there is a flash of distortion in the top third of the screen which disappears almost instantly. This only happens with lift to wake and does not happen with double tap or button wake.
Anyone else experience this?
Click to expand...
Click to collapse
Got the same problems.
Just after the Android 10 update. It feels like it's getting worse.
I've turned off my favourite feature to see my notifications, glance view. Now it's gone but have to double tap and see if there are new notifications.
The Android 10 update from Nokia is a really bad thing.
If someone could clarify the system app that controls glance, clearing of the cache and storage might fix.
Has this been fixed with the December or jan patches?
Related
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it
WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
FWIW, Exodus and I'm sure some other ROMs, have a setting to prevent pocket wake ups by using the proximity sensor.
WyldOne91 said:
I've tried a couple of ROMs with double tap to wake. I honestly love the feature, but I've had too many issues with wake locks in my pocket, so I've decided it's not worth it and I'll turn it off. The problem is, it doesn't actually turn off. I'll hit that off switch, tap my screen a few times, and it's awake again. This is frustrating because then it wakes up in my pocket still. Is there any way to permanently remove it from the ROM? Maybe something I can flash or something I can change to completely disable this feature?
Click to expand...
Click to collapse
Are you sure it's not ambient display waking your phone?
Eh... "ambient display" doesn't wake your phone. Ambient display just shows WHEN your phone is awoken by... tap to wake, shake to wake, incoming notification.
OP: Some people confuse tap to wake and shake to wake. Nexus 6 implements shake to wake by default. Problem is that tapping on the screen can.... shake the phone.
This generally should NOT be going off in your pocket. Either, that is. Reason is that it is *supposed* to use the state of the proximity sensor as a CONDITION on whether or not it should start up ambient display. The proximity sensor will read as "near" when the phone is in your pocket, thus prevent tap or shake to wake from triggering ambient display.
So sounds like you probably tried a couple of different sysimages that both contain a bug that stops it from taking the proximity sensor into account. My guess would be something that is based on cyanogenmod (aka "the buggiest android ever conceived"). Try stock and see if the problem goes away.
Personally, I prefer to use a custom ROM with native LED control and disable ambient display.
danarama said:
Grab /system/lib/hw/power.shamu.so from a pre-rooted (untouched) stock rom or a rom that hasn't enabled it
Click to expand...
Click to collapse
what do you even mean?
slamsal said:
what do you even mean?
Click to expand...
Click to collapse
What part don't you understand?
If you haven't got a modified Nexus 6 with this problem, then this isn't relevant to you.
Hello, really new to this thread. My Mi 8 is about 2 weeks old. So recently I noticed that the home button gesture doesn't work sometimes. I have to repeatedly swipe up from the bottom of the screen for it to work...also when pressing something close to the status bar seems to trigger the status bar opening animation. This happens only every now and then then. I'm on stock global rom everything locked nothing tinkered with at all. Anyone experiencing the same thing?
Mike20017 said:
Hello, really new to this thread. My Mi 8 is about 2 weeks old. So recently I noticed that the home button gesture doesn't work sometimes. I have to repeatedly swipe up from the bottom of the screen for it to work...also when pressing something close to the status bar seems to trigger the status bar opening animation. This happens only every now and then then. I'm on stock global rom everything locked nothing tinkered with at all. Anyone experiencing the same thing?
Click to expand...
Click to collapse
what mi8have Home button？
PUBGKING12 said:
what mi8have Home button？
Click to expand...
Click to collapse
I'm talking about the home screen gesture.
Try to test if your screen has some issues, I don't experience any problem
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
You mean using the gesture settings, when you swipe from the bottom it will not go home (takes multiple tries)? If so, do you have a case or screen protector installed? The way you're supposed to swipe is pretty much from outside of the actual display, upwards, so if there is something interfering with this, or you're swiping from in the display, it may not work.
If not, then try using a touch screen test app such as Touch Screen Test from Google Play (developed by Siriuth). Touch the bottom area multiple times (swipe down, left, right, but not up as this may send you to the home screen of course). Swipe slowly to see the path properly. Does it skip at any section? If it does, touch in that area may be damaged. If this phone was purchased used or from a 3rd party seller, this may be why it is damaged.
Crossvxm said:
You mean using the gesture settings, when you swipe from the bottom it will not go home (takes multiple tries)? If so, do you have a case or screen protector installed? The way you're supposed to swipe is pretty much from outside of the actual display, upwards, so if there is something interfering with this, or you're swiping from in the display, it may not work.
If not, then try using a touch screen test app such as Touch Screen Test from Google Play (developed by Siriuth). Touch the bottom area multiple times (swipe down, left, right, but not up as this may send you to the home screen of course). Swipe slowly to see the path properly. Does it skip at any section? If it does, touch in that area may be damaged. If this phone was purchased used or from a 3rd party seller, this may be why it is damaged.
Click to expand...
Click to collapse
Just tried it... Everything seems fine. But still sometimes it tends to require several tries for the gesture to actually register. I'm on global 10.2.3.0, could be a miui bug since this version is not the best. Also has battery drain problems. Could be fixed in the next update.
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
Mike20017 said:
Just tried it... Everything seems fine. But still sometimes it tends to require several tries for the gesture to actually register. I'm on global 10.2.3.0, could be a miui bug since this version is not the best. Also has battery drain problems. Could be fixed in the next update.
Click to expand...
Click to collapse
That's very odd. Does the oleophobic coating in that area feel worn or anything? Does the friction feel high? Mine never fails, not even to open the multitasker. Do you have "Double Check for Gestures" enabled? Try turning this off perhaps? The battery drain I definitely agree. I went from 7 hrs of SOT to less than 5.
Mike20017 said:
I'm talking about the home screen gesture.
Click to expand...
Click to collapse
ok
I use a widget called screen tap to lock or something or another for the double tap to sleep on any launcher. Have been using it for a while across a few phones. However when I got the S10 I just started using face unlock due to this slow and clunky FP sensor.....but I've discovered this issue where double tap to sleep with face unlock on makes the phone immediately wake back up to the lock screen for a second unlike pressing the power button which acts correctly. I tested it out on nova's built in settings without the widget (which I was using on one UI launcher) and it does the same thing so obviously it's some sort of conflict with face unlock and double tap to sleep. Anyone know why?
carnivalrejectq said:
I just started using face unlock due to this slow and clunky FP sensor.....
Click to expand...
Click to collapse
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Ripthulhu said:
Wait, slow and clunky? Maybe off topic but mine is extremely consistent after they fixed it like 4 months ago. Maybe relearn prints and make sure you get the whole thumb scanned.
Also I have double tap to sleep setup on Nova using accessibility as screen lock method and tried your scenario with face unlock enabled, but did not encounter your issue on Android 10
Click to expand...
Click to collapse
Oh, I'm on cricket in the US , so still stuck on 9 (with no hope in sight for 10 lol). I've deleted them and reset them a few times now and idk it's just not as fast as I'm used to with capacitive ones, there's an extra second, even compared to the one in the OnePlus 7t I was using for a few days , it cannot compete. It works a lot better if you press hard and firm I guess, but again I'm not used to that. But yeah idk why it's doing that, did it to me on Nova too if I use double tap to sleep at all it immediately opens back up to the lock screen. I don't think it's looking for my face in that scenario either because it doesn't face unlock when it does it, but it definitely IS happening because of the face unlock because it doesn't happen if I turn it off altogether and use the double tap to sleep......if I press the power button to turn the screen off this does not happen.
Hi there,
Tap to wake is a neat feature but I find myself waking up my phone too often by mistake, so I tried to figure out a way to get the old double tap to wake back, but couldn't find out how.
I guess it must be implemented into custom kernel ?
Any advice would be appreciated !
Same, I had to turn this off b/c my phone kept waking in my pocket and changing songs.
I noticed too sometimes my phone wakes up in y pocket, coming from OnePlus it surprised me cause I'm used to have pocket mode. Hope there will be a workaround later.
I replaced the Pixel Launcher with Nova Launcher. Light years better. While there is no double tap to wake, you can double tap to lock the screen then just use the fingerprint reader to unlock the screen. Since owning the OG Droid long ago it seems, I have yet to find a home launcher better than Nova. Worth every penny.
Double Tap - Apps on Google Play
Easy to turn on/off screen without power. Not affected to unlock by fingerprint
play.google.com
Works perfectly on Pie.
As for Q...? Give Google time and they will screw up anything and everything.
I use NovaLauncher too and all my devices for years now. I love it.
But that's not what me and OP are complaining about. We want to double-tap the screen while the phone is laying a table and have it wake up to lock screen. Picking it up and using the fingerprint sensor on back doesn't help.
Lift to Wake works, but you have too, duh, lift it to wake it. We want the double tap for our fingers, but not erroneous dbl tap detections when phone is moving around in pocket or in my hand.
I can't tell you how many times music player skipped forward or back b/c or incorrect dbl taps, waking, and then more taps from my pocket contents or whatever.
I'm using OnePlus launcher port as I'm used to it (and I love the gesture to access hidden apps from app drawer, asking for fingerprint).
And I'm happy with it, I use Gravity box so I can turn the screen with double tap on status bar.
For now I disabled tap to wake, and I use tasker to turn on always on when there's an incoming notification, so that I don't have to wake my screen just to check if there's something new.
I'm confident someone will give us a custom kernel allowing double tap to wake someday !
Seems like there's something wrong with proximity sensor, I noticed that after trying to play with proximity sensor in tasker, it always return 5cm.
Updating to February build did not solve the issue, that could be the reason why there's no pocket mode.
Anybody else with this problem ? (There are several apps that can read sensors and check for proximity one.)
Did anyone ever figure this out. I really like the double tap to wake so I just tap my phone while it sits on table to wake. I never had an issues w/tapping to wake before (LG v35, etc) and I now realize why it is a huge problem for myt 4A 5G -- stupid Google make it tap to wake, not double tap. For me, this cause constant waking and then irritating unwanted activity (music changing, podcasts stopping) while my phone is still in my pocket. Arrrrg.
StephenMSmith said:
Did anyone ever figure this out. I really like the double tap to wake so I just tap my phone while it sits on table to wake. I never had an issues w/tapping to wake before (LG v35, etc) and I now realize why it is a huge problem for myt 4A 5G -- stupid Google make it tap to wake, not double tap. For me, this cause constant waking and then irritating unwanted activity (music changing, podcasts stopping) while my phone is still in my pocket. Arrrrg.
Click to expand...
Click to collapse
If your phone wakes up in your pocket, you must have a problem with proximity sensor, i had to remove my screen protector because of that, and now, no more accidental wake up while in the pocket (but i still miss the double tap to wake).
Hi guys!
A few months ago I tried Pixel 6 as a replacement for my ageing OnePlus 5 and in the end had to return it because it was sometimes missing screen taps. Now I have Pixel 7 and guess what? The same thing. It is the most prominent when I want to wake the phone up with a tap (Google changed from double-tap, gods know why) and it often fails. I've tried double-tap, tripple-tap, turning off/on various settings, restarting, updating... The same stuff. There seems to be a lot of talk about it on reddit. The same works flawlessly on my Pixel 5 (and also many other things which are failing on Pixel 7).
Going through discussions it seems this plagues Pixel phones for some time and it seems to be some hardware issue.
Have you encountered the same issue?
Biges said:
Hi guys!
A few months ago I tried Pixel 6 as a replacement for my ageing OnePlus 5 and in the end had to return it because it was sometimes missing screen taps. Now I have Pixel 7 and guess what? The same thing. It is the most prominent when I want to wake the phone up with a tap (Google changed from double-tap, gods know why) and it often fails. I've tried double-tap, tripple-tap, turning off/on various settings, restarting, updating... The same stuff. There seems to be a lot of talk about it on reddit. The same works flawlessly on my Pixel 5 (and also many other things which are failing on Pixel 7).
Going through discussions it seems this plagues Pixel phones for some time and it seems to be some hardware issue.
Have you encountered the same issue?
Click to expand...
Click to collapse
My works flawlessly single tap, double tap, doesn't matter but I use nova launcher and Iam rooted
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
hammered58 said:
My works flawlessly single tap, double tap, doesn't matter but I use nova launcher and Iam rooted
Click to expand...
Click to collapse
Nova Launcher, my favourite app!
Seems like some shortcomings of Pixel 7 can be solved using the root access, however it seems crazy I need to root the phone to get the same functions as on a Samsung or a OnePlus phone :-/
bobbyphoenix said:
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
Click to expand...
Click to collapse
Yes, it is as you describe. But don't hope too much, this behavior about missing already animated taps had been reported for Pixel 6 by many people, but Google seems to ignore it or what, they just don't give a care?
I encountered this issue in the beginning. Try the following and see if it solves your phone being unresponsive to tapping to unlock the device. Go to: Settings>Display>Lock screen and turn off Lift to check phone, turn on Tap to check phone.
bobbyphoenix said:
I noticed something similar because my 3 XL worked with the slightest tap. My 7 misses taps if I'm not directly tapping with a full press of my finger. If it's just a brief tip tap it sometimes doesn't work. The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap, so I have to tap again harder, and then it works. Seeing a setting to increase sensitivity makes me thing Google has the default too low, and hopefully can "fix" it in an update.
Click to expand...
Click to collapse
Hey, same here sometimes. I got a pretty good but cheap tempered glass screen protector with which FP works 8/10 plus using face unlock. Better touch input option with protector is enabled in settings.
The strange thing is if I'm tapping something on the screen it shows the touch animation, but it doesn't register the tap ...
Click to expand...
Click to collapse
Exactly this happens more often and I had that on my Pixel 6 too which I replaced with a Realme GT2 Pro (no problems with the Realme) but on Pixel 7 now again. Still using three buttons navigation bar, and often the taps don't work there too.
LOL f* Google, can't they get their stuff fixed? I mean the company which codes the OS sucks regarding their flagships more than other OEMs which only adapt the OS. Jesus f* christ.