my fingerprint sensor takes many times 2-3 sec delay when i wake up the phone from deep sleep
this started when i switched to pure nexus rom and elemental x kernel
i was okay on stock roms and n preview
anyone else facing this?
Yes. Think it's the March update.
Related
solved
seijidinzuala said:
Hello,
I bought a Redmi 1s online and from the very first day, the proximity sensor doesn't work well, whenever I made a call, after putting the phone near my face, the screen goes dark as normal but it sometimes just won't turn back on. I tried calibrating it through *#*#64663#*#*, I was able to calibrate fine 2 times, but after putting a screen guard on, the sensor became buggy again.
*I've tried flashing different ROM's which doesn't help
*I've removed the screen guard and still buggy
*I cannot calibrate the sensor anymore and just fails
*I've tested the sensor with a 3rd party app from play store and it seems to work fine in that app.
I'm currently out of ideas, can anyone help me?
PS: Sometimes, the screen goes off right after hitting the call button and wont turn back on until the call ends.
Click to expand...
Click to collapse
Yes problem with proximity sensor was their and because it was on base rom so it reflected in other roms too. Currently i am not experiencing it in miui 6. So either try miui v50 (Latest official stable update) or try miui 6.
Again its a software problem and will be solved.
I have updated OxygenOS to 4.0.1 and now I have problem with proximity sensor during call (on 4.0 I haven't noticed that).
Firstly, there was a problem with changing volume during call. There is also problem that screen doesn't turn off when I keep it right next to my face and I'm during call. Also there is a problem that screen turned off while in call and when I took it away from my face, it turned on after few seconds.
Anyone on 4.0.1 having the same problem? I thought OP fixed this problem on that version but I'm having it. Maybe I should do something to fix that (dirty flashed from 4.0, maybe I should clean something or try wiping system and flashing 4.0.1 on top of that?
I'm having the same problem on 3.2.8, and had it ever before. Maybe you just didn't notice it till now?
Proximity sensor is bugged on this thing from MM times. Sometimes it works and other time, it doesn't
abhibnl said:
Proximity sensor is bugged on this thing from MM times. Sometimes it works and other time, it doesn't
Click to expand...
Click to collapse
It would be more widely reported if that were true, never had an issue with proximity sensor on 3.2.8 or 4.0
Renosh said:
It would be more widely reported if that were true, never had an issue with proximity sensor on 3.2.8 or 4.0
Click to expand...
Click to collapse
I didn't have that on 3.2.8 also and on 4.0 this also didn't happen but on 4.0.1 I have that problem on every call.
trawel said:
I didn't have that on 3.2.8 also and on 4.0 this also didn't happen but on 4.0.1 I have that problem on every call.
Click to expand...
Click to collapse
I'm on 4.0.1 don't have a single issue so not sure what you want me to tell you. Best solution is backup and reset device
Renosh said:
It would be more widely reported if that were true, never had an issue with proximity sensor on 3.2.8 or 4.0
Click to expand...
Click to collapse
Like I said mate, sometimes it worked but it never bugged me to the point of frustration so ignored it.
I am facing the proximity sensor issue too. when on call the screen is switched on and many keys are pressed. sometimes by accident even the airplane mode is switched on.
this is constantly a problem with OP3 even in 4.1.3. very poor software support. I think now that are focused only on op5.
No it's not a proximity sensor problem, it's a OnePlus dialer app bug.
There are several bug reports in OnePlus forums about this issue and in one of them they say it will be patched in next version of OOS (I assume stable not tried with new open beta which installs new dialer) so if you don't want to wait, for me the solution that works it's to install Google dialer app from this post https://forum.xda-developers.com/oneplus-3/how-to/guide-how-to-install-google-dialer-phone-t3443006
I recommend to follow all steps in the first post to install it without problems and you won't have this issue anymore.
Hope it helps you.
Un saludo
Has anyone any idea when this will be fixed by oneplus? It is driving me mad, nearly every call gets interrupted by my ear pressing a button turning on the light etc.
I want to keep my phone stock so cannot use the google dialler tip posted above. Thanks
Hi people,
I have an one plus 3 that i didn't use it for about 4 months and in the past everything was good and workfine with the lineage 15.1 I try another rom "theOne3OS" and from then now somethimes the screen won't wake up.
I installed the lineage 16 and still have the same problem.
does anyone has the same problem?
any idea?
I have the same issue bro... Try flashing mcd kernel that may help you
Mohammed Raihan said:
I have the same issue bro... Try flashing mcd kernel that may help you
Click to expand...
Click to collapse
In one of the topics in here they said to put the oxygenOS rom as default and it works fine for me.
Yes oos oreo works oos pie may not work.. And if you want to use custom roms then you need to flash mcd kernel
How do you try to wake up the device? Double tap to wake? Power button? Fingerprint sensor? you can try to narrow down the issue defining a recurrent pattern....I had that issue from time to time, in my case i was unable to wakeup the device in any way...was some sort of power saving configuration that putted the phone so low in performance it was almost freezed. For example when phone was idling for few minutes and screen turned off i had no issues, in comparison with the phone idling for an hour or so, the issue randomly appeared.....you have to try to define a behaviour pattern to define the causes
Recently in the last day my phone has experienced significant lag when bringing the screen on. When I press the power button or use the fingerprint reader it takes 1-2 seconds with a black screen before anything shows up. I'm not sure what's happened but before it was almost instant. I'm running on Havoc OS 2.3
Please anyone that can help? This is driving me nuts. What can I do before a hard reset?
Anyone? I can't be the only person with this problem
Never experienced this. Kinda weird. Any updates?
Sent from my Redmi Note 5 using XDA Labs
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Restarting your device can fix some minor issues like unstable Wi-Fi, a frozen program, or a faulty fingerprint sensor. So the best solution for your fingerprint sensor might be to reset it.
jack lamters said:
Restarting your device can fix some minor issues like unstable Wi-Fi, a frozen program, or a faulty fingerprint sensor. So the best solution for your fingerprint sensor might be to reset it.
Click to expand...
Click to collapse
by resetting, you mean restarting my device? i tried... but still giving me issue,,,
godlyitem said:
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Click to expand...
Click to collapse
Since you are running a custom ROM, the best person to ask is the creator of that ROM. See if maybe other people running the ROM have the same issue. Since you are not running Stock and haven't even mentioned which ROM you use, it's hard to help you here in any way.
godlyitem said:
i recently tested custom roms... and rooted my p6p but somehow the fingerprint reader doesb't sense my finger when it's in lockscreen and only work after i wake the phone up... anyone has ideas what's causing it?
Click to expand...
Click to collapse
I am not running custom rom but that fingerprint reader problem is on mine too and its sporadic. The reader would work fine after a reset/flash, days later it would bug out. I have to tap once or lift the phone to activate the screen for the reader to work. Rebooting the phone a few times would get it to work again but its random.
I've noticed on AOD the fingerprint reader doesn't respond while in a smartlock area and i have to press power to get to lockscreen then fpr works (or it shows me unlocked by smartlock depending if it's been 4 hours) . Can others confirm/rebut that theirs only does this in smartlock zones and not in the wild (or if you bt smartlock whether or not being connected causes this)
so i rooted and went back to stock OS. It didn't work in AOD. After several reboots, it started to work again..... this is crazy
godlyitem said:
so i rooted and went back to stock OS. It didn't work in AOD. After several reboots, it started to work again..... this is crazy
Click to expand...
Click to collapse
Yeah, its a crapshoot if it will remain working the next time you restart.