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
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
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Well me getting same problem.. still not figured out issue.
Sent from my ONEPLUS A3003 using Tapatalk
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Hastaloego said:
dont use it as your pocket vibrator then...
have you checked the smart lock? it can keep your phone unlocked while you carry it.
Click to expand...
Click to collapse
Hahaa ;p
well, smart lock is not active in my phone...
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
binners said:
Does it only happen when the screen / fingerprint scanner are against your body? Maybe they are detecting skin through your clothes and constantly trying to do something?
Click to expand...
Click to collapse
thebcooper said:
This. I think this is causing the issue. If you are slightly warm/damp/moist (someone reading hates that word ), it will try and scan your leg. My guess is perhaps it's not checking the ambient/proximity sensor to see if it's in the pocket or not.
I had this issue on the OnePlus 2 as well, although not as bad.
Click to expand...
Click to collapse
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
MagDag said:
Thanks guys!
I'll try to wear the phone outward inside my pocket to see whether the problem still occurs.
Btw, i did some tests via "GSam Battery Monitor" and figured out the main-process which is producing the problem:
It's the "kernel". Does the kernel controls one of the mentioned sensors (ambient/proximity sensor) ?
Click to expand...
Click to collapse
Just be more wary of the screen being knocked/bumped!
Yeah that handles hardware as far as I know (might also be under other processes if they use it too though)
Alright, thanks for your quick feedback.
I guess i will reset my phone now...
I'm pretty sure it's the fingerprint sensor. Really sad to see that OP3 has this issue too, this started happening to me on OP2 too after the marshmallow update. They made the fingerprint scanner much more sensitive, greatly improving it's speed but this started happening. The workaround is to keep the phone in your pocket screen facing outwards...
I have the same problem. It should be fixable via system update to not activate the fingerprint sensor while the proximity sensor detects something.
Or am i missing something here?
Same issue here
Same issue. It's kind sad that OP can't handle this to prevent waking up using proximity sensor like it happens with duoble tap. I hope that they will release an update soon.
Is there anything in settings called "pocket mode"?? a friend has a THL phone that has pocket mode which stops the phone from doing anything when it detects its in a pocket
Nope, I've searched whole settings and there no option like 'pocket mode'.
same issue and the screen is showing the message "too many attempts. try again later" i can't use my smartwatch because the phone make a call or sent a message it self in my pocket.
I've created an e-mail to support with issue describe. Will update thread while getting reply.
Yes this is a bad bug which OP need to fix asap.
So what's the solution to the problem, finally?
MagDag said:
Hey people,
my OnePlus 3 loses much energy (up to 3 percent in 5 Minutes) if it’s inside my pocket (!) - especially then if I move at the same time.
I have already disabled the gesture functions - however, the problem remains.
Actually the problem can only be reproduced in my pockets
- latest Stock-ROM
- no root or other deep system changes
Any ideas how to narrow down this issue?
Best Regards,
Chris
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
ArjunRanaOO7 said:
We simply keep the phone face up in our pockets? That seems like a quick fix we shouldn't have to live with...
Click to expand...
Click to collapse
You would think that priority would be given to the proximity sensor. If triggered it would disable the finger print input.
Today I kept my OP3 (Stock Rom Rooted) for 10/15 minutes the phone in my pocket and it become extremely warm (seems to be nabk with my OP2) !!
I made the following thoughts:
- the ambient display wakes up the phone and make it warm
- the FPS feels "something" and it wakes up the phone
- the proximity sensor doesn't work properly
Does some of you ahve the same issue ? Any feedback is welcome !
Now I disabled the ambient display, and let's see what happens.
I am facing same Heat issue when in pocket and riding the vehicle. Have disabled Gesture control in phone setting, Let us see the result.
yes..me too facing the same heat issue
Same here
raghumantap said:
I am facing same Heat issue when in pocket and riding the vehicle. Have disabled Gesture control in phone setting, Let us see the result.
Click to expand...
Click to collapse
I don't use the gestures, except the double tap to wake which honestly is use less with fps...
Sent from my OnePlus3 using XDA Labs
same here, i already started another thread for this issue:
http://forum.xda-developers.com/showthread.php?t=3403583
MagDag said:
same here, i already started another thread for this issue:
http://forum.xda-developers.com/showthread.php?t=3403583
Click to expand...
Click to collapse
I didn't used your thread just because you talk about energy and not heat (even if usually mr Joule said these are linked)... BTW I read it's because of fps: could be... I want to try the setup without gestures and ambient and than I will confirm it!
Sent from my OnePlus3 using XDA Labs
Hey!
it also generate heat here...
It's definitely the fingerprint sensor. Face the screen outwards inside your pocket and the problem doesn't occur anymore (thanks @Rauttis)
This happens to me also but I have no gestures enabled on the lock screen so it can't be that. Thus as MagDag says, it is probably the fingerprint scanner. I'll try to face it outwards to prove it.
MagDag said:
Hey!
it also generate heat here...
It's definitely the fingerprint sensor. Face the screen outwards inside your pocket and the problem doesn't occur anymore (thanks @Rauttis)
Click to expand...
Click to collapse
I will try this out and report back.
Sent from my OnePlus3 using XDA Labs
I have no problems so far. Using it for a week now.
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Due to Gestures Fingerprint sensor, confirmed for me (haven't tried with Gestures ON and fingerprint sensor OFF) . Ambient display is on.
Sent from my OnePlus3 using XDA Labs
I used the following setup: no gestures, Yes ambient, fps on the outside side of the pocket... Seems extremely better (with 38 degrees here during the day)
Sent from my OnePlus3 using XDA Labs
Same problem for me too..
same issue and the screen is showing the message "too many attempts. try again later" i can't use my smartwatch because the phone make a call or sent a message it self in my pocket.
Soumitra.5693 said:
Due to Gestures, confirmed for me. Ambient display is on.
Click to expand...
Click to collapse
It's not due to gestures. As I said above, I have gestures turned off (and ambient display off too) but this problem still occurs for me, frequently.
bulletmark said:
It's not due to gestures. As I said above, I have gestures turned off (and ambient display off too) but this problem still occurs for me, frequently.
Click to expand...
Click to collapse
Hi, yes, I think it is due to the fingerprint sensor. I must have placed the phone facing away from my skin after disabling gestures (which was pretty stupid).
Sent from my OnePlus3 using XDA Labs
I have the same problem especially when at work although my pants are slim so the phone is against my body but going to try turning gestures off and seeing if the issue remains
I also have the same problem, thinking of returning the phone(ask for a replacement)
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
same problem here... if I turn off fingerprint then it will be fine. the sensor is too sensitive
So I have a very weird issue and I'll try to explain the best I can;
For some reason, ever since the S10+ I've had issues with Samsung phones, I think its something to do with the proximity sensor that's now under the glass, I'll explain as I'm getting similar and more issues on my S20 Ultra.
So last year when I had an S10+ and when I was on a call, which I mainly use my left ear (I think my right ear is a few db less so I use my left) I would quite frequently seem to activate the menu (top right) and therefore end up pressing things with my ear, unbeknown to me, sometimes I'd add a 2nd person to the call or simply put the other person on hold! This happened a lot and I was close to sending it off for repair even though I used apps to test to ensure the proximity sensor was working correctly but in the end, I sold it and got an OnePlus 7 Pro, which I didn't have an issue with. During my time with the S10+ I noticed that even though I held the earpiece to my ear I could see the screen light up and that's where I think I'd end up pressing the screen accidentally as I've just explained.
Roll on to now where I'm facing similar issues but also I'm finding if I need both of my hands and therefore use my left shoulder to keep my phone against my ear the call disconnects as if I'm hanging up. Now it seems a straightforward resolution which is not to do that but I've never had this issue before and I've tested it out quite a bit when I do this the screen isn't on and my face is nowhere near the end button!! It's really driving me crazy at the moment and annoying my other half who's normally on the phone to me when this happens!!
Anyone got any suggestions or thoughts, does it happen to anyone else or am I just being stupid??
I haven't gone down the route of resetting the phone yet but I'm going to consider it.
T.I.A
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Xode said:
Hi..don't have such an issue, but when i talk with someone longer, i turn off the screen with the Power button and so it stays the whole time black during call....
S20U-Exynos
Click to expand...
Click to collapse
I did that the other day, however, when I moved the screen away I saw it light back up....
maverick1103 said:
I did that the other day, however, when I moved the screen away I saw it light back up....
Click to expand...
Click to collapse
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
View attachment 5012913
S20U-Exynos
Xode said:
Yeah,weird a bit, try to go into the secure lock screen settings and do as i did...maybe it helps ..... like i wrote before, my screen stays black whatever i do while i talk...
S20U-Exynos
Click to expand...
Click to collapse
Thanks, I've already got that enabled, will just have a play around.
maverick1103 said:
Thanks, I've already got that enabled, will just have a play around.
Click to expand...
Click to collapse
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
vrgolin said:
Hi , do you make it work? I have the same problem with my Samsung A71, I have been using all kinds of apps a no one make it work.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Not yet, still having issues.
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...