Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
all good on ArrowOS, DT2W and sleep working great... i know it's possibly not what ur looking for... but it's a seriously good rom.
ApexPrime said:
Dt2w works fine for the first few minutes after locking phone but after that, it requires 7-8 taps to wake up. Anyone else experiencing this? Im using xiaomi.eu 12.5 stable.
Click to expand...
Click to collapse
Yes, this happens also for me
I'd assume this would also be an issue on the Global rom?
If so, we can bring it to Poco's attention via Poco community forum.
Otherwise, we'd have to bring it to Xiaomi's attention on the Mi community forum.
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
this any good? or there's others if you search playstore....
this one maybe
(as a possible temporary solution, i mean)
EDIT: sorry, i read ur post as a touch sensitivity issue. have re-read, don't think those apps are of much use
Interestingly, don't have problems with double tap to wake, it works always, only with tapping for always on display to quick check time or notifications. Works 1 in 10 times. It's funny, tap, nothing, double tap ok.
Morak75 said:
I'm on the weekly and I also have this issue. Not 7-8, but I have to tap twice. Like 2 taps then 2 taps again. Happens sometimes.
Click to expand...
Click to collapse
same issue
Same issue, probably the biggest annoyance for me since I'm almost unable to use 10 second AOD tapping to conserve standby power.
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
blackhawk said:
Any power management active?... destroyer of worlds.
Try clearing system cache, and a hard reboot.
Try altering AOD settings or clearing apk data.
Maybe a firmware glitch... they happen.
Click to expand...
Click to collapse
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Nemix77 said:
Already done this to fix my drain problem one day one of receiving the device.
I know Android is just like any other OS installed on a computer sometimes needs clearing of cache, a shutdown of the OS or a manual reboot.
In fact I've done it many times just to make sure MIUI is not glitching on me.
Click to expand...
Click to collapse
You be amazed how many have no clue or just don't think using of it.
It may be a settings glitch or again some sort of power management running amuck in the background. Play with it...
I posted the issue on Mi Community and Poco Community forum.
Not many people seem to use the double tab to wake feature with AOD set to 10 seconds.
I tried searching on Xiaomi and Poco both forums with keyword double tap and not a single thread for the Poco F3/Redmi K40.
festor said:
I noticed this too but for me it’s the very slight movement between taps where it presumes a gesture is upcoming. It also seems a little worse with a slippery tempered glass protector.
If I make a conscious effort not to move position between taps it works for me every time. Maybe they can adjust swipe detection sensitivity?
Click to expand...
Click to collapse
I think youre right bro. If i time my taps perfectly and dont move position between taps, it works most of the time. Same goes for the AOD. Single tap works but it takes almost 2 seconds for the AOD to pop up which is pretty slow imo.
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Nemix77 said:
I think figured it out, 3 fast taps without moving my finger always works with AOD now.
Whatever, I'll just leave the posts on the Mi and Poco forum...hopefully they can replicate the issue and improve single/double/triple tap detection with future updates.
Click to expand...
Click to collapse
Bro did you try single tapping and waiting for ~2 seconds?
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Nemix77 said:
Everything magically works now, after I let the battery deplete to 0% (MIUI auto shutdown) for a second time and then charge to 100% (for initial battery calibration).
Of course I won't be letting the battery deplete past 20% anymore after this, and I'll only be charging up to 90% when I have the phone rooted.
I'm pretty sure there some other minor issues with MIUI I haven't encountered yet, but for now it's pretty enjoyable to use.
Click to expand...
Click to collapse
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
colosocool said:
One question, double tap to wake drains battery on Amoled screens? read somewhere that it was a function for LCD displays
Click to expand...
Click to collapse
Might depend on the device. Doesn't use much at all on my Samsung Note 10+.
With AOD touch to view active and phone/text running I use less than .5% @HR.
Never tried deactivating Double Tap on though... it's too useful.
More than likely it's not the culprit. Cloud apps and trashware like WhatsApp, FB, Google system apks are prime suspects.
Easy enough to test...
Related
I'm just trying to narrow down why randomly the fingerprint scanner does not wake the phone. It might happen once a day or not for a couple of days, but it seems to always come back. Not a huge deal since the power button will always work, but it is disconcerting when it happens. I'm not using any power widget or lock program although I do use Nova Launcher Pro. Does this happen to anyone else and if so have you narrowed it down?
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
jbdan said:
Mine always wakes my phone, although every now and then it doesn't recognize my print. However, I believe it's because of how my finger lays on the sensor so I think it's user error in my case.
I've registered 4 prints, 2 from each index finger and all in different positions on the sensor to get the least reading errors.
Are you saying that you get no vibration as in it doesn't even register at times therefore you HAVE to use the power button to wake it?
I use nova pro too.
Click to expand...
Click to collapse
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
bobby janow said:
Yes exactly, no vibration. I've had it where it vibrates and doesn't unlock because my fingers are slightly wet or something. This is like it doesn't even know my finger is on the sensor. Power button unlocks and then it works again. Last time I said ok I'm not unlocking with the power button I'm gonna get this to work. Nope, had to power button it on after a minute or so of trying. As I said, it's not that big a deal and only happens once in a while. Glad it's not Nova though. Kernel dev said it's not the kernel , I'm using Elemental X. I might try going back to the stock kernel just to test it out. Problem is that I can't reproduce it.
Click to expand...
Click to collapse
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
SlimSnoopOS said:
I get this occasionally when charging but that occurred on stock everything, can't say I've noticed it in any other capacity. Are you using smart lock or an app to lock your screen?
Edit: I should read your post before replying, disregard my app question. Still asking about smart lock though.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Smart lock, yes. Well smart unlock isn't it? I have a couple of BT unlock devices, Mi Band and car BT radio but that's it.
jbdan said:
And I meant to include the "big" question in my original reply. Big being "what mods are you using"
Best way to trial and error issues as you well know? I'd test it on all stock (for a day or 2) and see what that gets you then you can narrow down to if it's the kernel or not. I'm not a kernel dev, but an educated guess would point to that imo
Click to expand...
Click to collapse
No mods.. well let me rephrase that. I have a bunch of programs running naturally, but the only "mod" I have is Cataclysm and systemless root along with Elemental X kernel. Cataclysm is considered a mod these days as it's just an overlay on stock 6.01. I know I'd have to go full stock to test for a few days but I'm so so trying to avoid that as I'm sure you know. Thanks for all the input guys, I know this can't just be me right? Hey wait a sec.. I do have a BT smart band unlock running. I'm going to take that off and see if that makes a difference. Maybe that is interfering with the fingerprint requirement.
Edit..nope not it. Gonna run stock kernel next.
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
tofuwrice said:
The exact same thing is happening to me. Same symptoms but I am on fully stock. I'm also using nova pro. Been searching around for an answer but haven't found anything.
Click to expand...
Click to collapse
Too many people on Nova Pro for it to be an undocumented issue. I know it's been said that it is not the kernel, however, yesterday morning I flashed this one http://forum.xda-developers.com/nexus-5x/orig-development/jolla-kernelbullhead-t3271530 and I've not had the issue since. I usually have it at least once / day and none so far. That doesn't mean it's not going to happen in 5 minutes though. I went with stock kernel values if you're rooted and feel like giving it a try.
I was having this issue randomly when running custom hotplugging. Currently no issues with default cpu hotplug settings and ElementalX.
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
jgummeson said:
For me I have a case on my 5x. There are two cutouts - one for fingerprint sensor and one for camera. They're both about the same size. Every once in awhile I find myself reaching for the camera instead of the fingerprint sensor. When I first got the phone I thought my fingerprint wasn't working at times. Turns out I was just putting my finger on the camera instead of the fingerprint sensor. Any chance this is what's going on?
Click to expand...
Click to collapse
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
bobby janow said:
Don't make me question my own sanity! hehe. I did the same thing at the outset but quickly realized my error. This is not what happens here, however. I even put it back in my pocket once to make sure it wasn't some aberration. It just wouldn't recognize there was even a finger there. Almost thought the phone had shut down but power button got it working again. Haven't had the issue in well over a day now with this kernel but I'm not sure that's what it is.
Click to expand...
Click to collapse
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
morenoa48 said:
This has happened to me twice. Both times while charging. Has not happened any other time. (stock everything/not rooted)
Click to expand...
Click to collapse
Happened to me not charging, rooted with custom kernel. So it's across the board hit or miss. I have a feeling it will be fixed in an update or OTA. Not a deal breaker just odd is all. Oh well, if we didn't have a power button it would be major.
After 3 years of usage my Nexus 5X fingerprint scanner stopped working at all and i can't do anything about it apparently. The issues started when i sent the phone to LG to fix the bootloop
Out of random, usually when I take it out of my pocket, my OnePlus 3 (Soft Gold) doesn't register that my finger is touching the fingerprint scanner. It doesn't vibrate or anything. It's quite random and dont know why it's doing it. When it doesn't do it, it works perfectly fine. Fast as ever! Has anyone else experienced this issue with their OP3?
connorhiller said:
Out of random, usually when I take it out of my pocket, my OnePlus 3 (Soft Gold) doesn't register that my finger is touching the fingerprint scanner. It doesn't vibrate or anything. It's quite random and dont know why it's doing it. When it doesn't do it, it works perfectly fine. Fast as ever! Has anyone else experienced this issue with their OP3?
Click to expand...
Click to collapse
And I would say it does it only 5% of the time.
When the proximity sensor is triggered, opt goes into pocket mode which disables the fps. Check if you are covering the proximity sensor
Sent from my OnePlus 3 using XDA Labs
connorhiller said:
And I would say it does it only 5% of the time.
Click to expand...
Click to collapse
Hi Connor,
i'm experiencing the same issue but it seems to be more like 20 percent of the time, depending on how long I keep it pressed there. Did you figure out what was wrong?
-Bob
The same exact things also happen with my OP3 A3000 Soft Gold, sometimes when I put it in the pocket for a long time (probably around 20-45 minutes), it doesn't instantly recognize my fingerprint anymore.
But it only happened on random occasions and not so often, so I don't' really mind it. My workaround for this is just pressing the power button to light up the screen and put my finger on the fingerprint scanner and it will be unlocked as usual.
BTW, I'm on OOS 4.0.2 and Franco R10 kernel.
Happens to me too, but rarely. When the phone is left untouched for a long time. I have the graphite one.
geekmax said:
Happens to me too, but rarely. When the phone is left untouched for a long time. I have the graphite one.
Click to expand...
Click to collapse
This can be due to the doze which deactivate the sensor and hence makes it slow or unresponsive
Sent from my OnePlus3 using XDA Labs
Prattham said:
This can be due to the doze which deactivate the sensor and hence makes it slow or unresponsive
Click to expand...
Click to collapse
Doze is supposed to leave the sensors alone , right ?
geekmax said:
Doze is supposed to leave the sensors alone , right ?
Click to expand...
Click to collapse
Well there are two doze
Normal and advanced
You will be familiar if you have used apps like naptime force doze etc
Sent from my OnePlus3 using XDA Labs
I too have the same model but it hasn't happened with me ever.
I would suggest you to record several fingerprints of the same finger...
But if the problem persists try factory reset:good:
Actually, I have the same issue. I guess I swipe my finger too quickly sometimes
Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
luckyvictor said:
Hi all
I have been using this phone for a month, and I have experienced a lot of different small issues, I hope someone may have solution to them.
Phone:
Mi A2 Lite, rooted (Magisk) Android one pie, January update. Has a screen protector.
Apps:
Here are some apps that I think may cause the issue that I mention below, these apps are Nova and datally. Really can't think of a third one, I don't use any cleaning app or battery performance app.
Issue:
1. Typing experience is horrible. Using stock google input, the keyboard is not very sensitive and accurate. The letter just can't be recognized even though I am sure I have pressed the key and pressed the right key. So my typing is really slow, the key doesn't display immediately (it does seem to have a delay), and for some reason I always type wrong and missing some letters, so gotta use backspace a lot.
2. It always wakes up randomly in my pocket, so I may take the phone out with torch on and airplane mode on without my awareness.
3. When I am on a call, I can accidentally press some random on screen keys.
4. The background apps AWALYS get killed, even though I have turned the battery optimization off globally, and the individual apps that I never want to be killed.
5. Messaging service apps have huge delay when delivering the notification. It may only show when I open the app. Used PNF app but couldn't fix the problem.
Does anyone have the same issue and know the fix?
I hope it is only the software problem (Pie system) and maybe I can fix it by flashing a better rom, but I don't seem to find a stable official custom ROM for Mi A2 Lite (even lineage OS is unofficial)
Many thanks
Click to expand...
Click to collapse
Try to update I never had any of those issues
I have also these problems. I have February update.
madmanwild said:
I have also these problems. I have February update.
Click to expand...
Click to collapse
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
rob420p said:
Try to update I never had any of those issues
Click to expand...
Click to collapse
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
luckyvictor said:
Do you have all these problems? or just one or two? After seeing my configuration/apps that I installed, do you think is it app related or system related?
Click to expand...
Click to collapse
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
madmanwild said:
all these problems without wakes up in pocket. killing the background application is the biggest problem for me (I use a lot of smart home app- eWelink,Room Heat,Magic Home) and it's horrible. ewelink starts 5sec after kill, Room Heat - frequent crash like a white screen...
the next problem is huge delay when delivering the notification....
I am on Stock Android One-February update,I'm allowed only cam2api...
Click to expand...
Click to collapse
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
luckyvictor said:
not even one of these? Your background app never get killed?
Are you using Stock Android One? did you root your phone?
Click to expand...
Click to collapse
I am on stock but I do have root.havent done much modification yet waiting for twrp
rob420p said:
I am on stock but I do have root.havent done much modification yet waiting for twrp
Click to expand...
Click to collapse
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
luckyvictor said:
Don't understand why there is such different, did you have battery optimisation off and all time since the first day you use the device?
Click to expand...
Click to collapse
Honestly I don't think so I really haven't messed with the battery besides putting a %
luckyvictor said:
You have battery optimization off? any battery improvement app? I think all these is because the 'intelligence' in Android is playing up, it doesn't understand exactly how we use the app. However, even have it turned off, the problem exists....
Click to expand...
Click to collapse
Yes, all off - battery adaptation and manually set no optimization on my app...
Hello guys!
I have bought a brand new Mate 20 X just 3 days ago!
I noticed that some times I click something and it wont do anything or do it with delay and sometimes I click on something and it vibrates like it did it but nothing happened (like home button for example).
Does anyone else face this issue? do you know how to fix it?
Have a great day!
Nothing here, I also use the gestures so never use the home button. Is it specific apps that cause issues or just in general?
yetiweston said:
Nothing here, I also use the gestures so never use the home button. Is it specific apps that cause issues or just in general?
Click to expand...
Click to collapse
everywhere all apps all places
omer919 said:
Hello guys!
I have bought a brand new Mate 20 X just 3 days ago!
I noticed that some times I click something and it wont do anything or do it with delay and sometimes I click on something and it vibrates like it did it but nothing happened (like home button for example).
Does anyone else face this issue? do you know how to fix it?
Have a great day!
Click to expand...
Click to collapse
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
ajsmsg78 said:
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
Click to expand...
Click to collapse
All stock, latest update no unlocked bootloader (EVR-L29)
I disabled all gestures, I dont have a nano memory card, its not app related, it even happens on the notifications tray when I try to reply to someone but the button doesnt work. even when I type there is a delay that make me miss some clicks I have done
omer919 said:
everywhere all apps all places
Click to expand...
Click to collapse
Have you tried a hard reset to see if that fixes it?
yetiweston said:
Have you tried a hard reset to see if that fixes it?
Click to expand...
Click to collapse
yes, from recovery. didnt help
also scrolling is very slow compared to other phones even when scrolling the fastest I can its very slow.
ajsmsg78 said:
Yep, it happens to me quite frequently. I don't think it has anything to do with the screen though. Do you have a nano memory card? Are you stock? What apps have you installed? What browser do you use? Mine started doing it after the 192 update (I think) and has been doing it ever since whether I'm on stock or on a custom rom. You'll tap a program and see that it selected but sometimes it takes like five to ten seconds to open.
Click to expand...
Click to collapse
Exactly the same a few times a day on stock or openkirin rr
Sent from my Kirin Treble using Tapatalk
sometimes when I touch with 2 fingers to zoom (for example on a document) it just stays on zoom mode even when I touch with 1 finger (so when I try to move around it will change the size like a 2 fingers gesture).
scrolling is way slower than any other phone I tested, has anyone else noticed that?
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
stestesteste said:
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
Click to expand...
Click to collapse
It's not a screen issue, it's a software issue.
stestesteste said:
Take screen protector off and clean it might be smudged . Maybe you could try glove mode it's more sensitive in settings
Click to expand...
Click to collapse
tried both, didnt help.
I thought I was the only one with this issue.
After flashing the Resurrection Remix rom I have never encountered this problem.
I'll be going back to stock soon so I'll see if the problem still exists.
Mine works perfectly. Even with the protective film scratched. Worked perfectly with my previous screen protector, a tempered glass type. I have the chinese EVR-TL00 midnight blue model. Everything stock, no root.
I also have this problem
You're not alone, this is happening to me as well on the EVR-L29. In my experience it is most noticeable when tap typing and a letter I tapped on does not register. Also, once in a while when I tap on an app to open it nothing happens and I'll have to tap it again for it to open. It's a mild annoyance for me, but not to the point of ruining the experience. I'm hoping a future software update addresses this, unless it's hardware related. I love the phone, but this is probably my biggest gripe outside of the possibility of no future upgrades in Huawei's spat with the US.
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
cjvphd said:
I understand that this was an issue on the 7, but this morning I woke up and my 7T wouldn't (when I tapped it). Anybody else having this issue, or have any suggestions on how to fix it?
Click to expand...
Click to collapse
I am also having this issue after the screen has been off for a while. Anyone have a solution?
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
italia0101 said:
I also have this issue, noticed it seems to be something to do with the ambient light sensor? If I cover it up double tap or tap to wake won't work ( like it's in pocket mode).
Pocket mode is no longer an option so it's like it's built in now?
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
This has been my experience today.
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Do You have Greenify installed?
Globus.gd said:
Do You have Greenify installed?
Click to expand...
Click to collapse
No.
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Globus.gd said:
I found a problem with no proper configuration of greenify. After some changes, tap to wake is working with no problems.
Click to expand...
Click to collapse
What is greenify? And should I have it?
http://greenify.wikidot.com/
italia0101 said:
I also have this issue, [...]
But yea for me it seems like it works fine in the day, but soon as night comes along and I'm in dimmer environments it becomes flakey
Click to expand...
Click to collapse
cjvphd said:
This has been my experience today.
Click to expand...
Click to collapse
Hey guys,
same for me since today. Until some hours ago all was working fine.
But why you think it's related to dimmer/light. Because for me there is no difference when I turn on the light in room or change the timezone in settings. For now it's just not working (like broken)
I rebooted (also turned off and on) several times, turned off and on the inactivity display settings and some other tests, but nothing helped.
CHEERS
bjs339 said:
There's a thread on this in the 7 Pro forum with a possible solution. Looks like it's worth a shot:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-fix-double-tap-to-wake-t3933504
Click to expand...
Click to collapse
Like for some others in the thread the factorymode won't be opened via *#808#
But I see the process installed and running when searching for it in settings. Maybe there is something crashed in bg?!
CHEERS
---------- Post added at 12:40 AM ---------- Previous post was at 12:05 AM ----------
UPDATE
Suddenly it began working again...
No changes in location, lighting or whatever (except 39 minutes).
But not I can confirm this laggy working of this function. No idea why...
Last days it worked like 10/10 but now maybe 4/10.
CHEERS
Launching the camera in landscape mode seems to trigger it for me occasionally.
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
A through clean up resolves the problem for my phone
i am facing the same issue with my phone. sadly i have noticed it is a reoccurring problem and it has something to do with the sensors. i tried all the fixes like toggling tap to wake, toggling face unlock assists light, clearing the cache and app data but nothing helped my case. factory reset is of no help either so i'd say don't even bother with that.
what really helped me fix this issue multiple times was something rather unexpected. what you should do is take off your phone's cover, get a wet towel, and thoroughly clean the phone all around, being especially thorough around the front facing camera and the top two edges. I give it extra attention around the front side being careful of the top speaker and after a couple of cleans and wipes both tap to wake and lift to wake starts working perfectly fine. then i put on the cover and voila it all good. Give it a try and let me know if it helped resolve this issue for you.
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Flamehell said:
What s the difference between dt2w and "tap the screen to show" in ambient display? Are them the same thing or are doing same stuff? Tnx
Click to expand...
Click to collapse
Hey!
The (single) tap to wake funktion will show up the ambient display, so that u can see clock, messages and use the fingerprintsensor if u want to enter.
It's a quick awake of screen to see Infos with minimal usage of display resources.
DT2W (double tab to wake) is the same as pressing the power button. So this will fully turn on screen into the lockscreen and also activate the face recognition. (for sure fingerprintsensor can be used, too)
BUT you can only activate one of those things and it will automatically turn off for example tab to wake if you activate DT2W.
Personally I like to use the single tab awake for ambient display, as I always can full activate by power button, which would be a dublicate function then.
CHEERS
---------- Post added at 02:08 AM ---------- Previous post was at 02:06 AM ----------
Hannibal226 said:
Today the rollout for version 10.0.5 was announced and should fix this DT2W bug.
Let's see if it's true.
Official post from OnePlus:
LINK
CHEERS
Click to expand...
Click to collapse
First ppl with new update (only some hours, max a day of usage) reported in OP Forum that they didn't have any problem for now.
So seems to fix this screen awake problem.
CHEERS