Anyone have working fix for Oreo roms? My fingerprint is like "dont turning on", i mean i can't fell little vibration, sensor don't recognize my finger, cannot save any pattern
Related
anyone experiencing this issue where during a call the camera randomly launches. Your face could be touching the screen and the phone will vibrate and launch the camera. Happens on almost every call. I have tried flashing bliss and then clean flashing to cyanpop but the issue still exists. Wondering if anyone has a fix or knows how to at least mitigate the camera from launching.
I have also found that this happens during whatsapp/wechat voice call but instead of the camera opening it would enable speaker phone during the call versus the camera.
Some lovely gents over at oneplus forums identifiissueslissue. Apparently it has to do with search and garak builds. Someone had posted the solution inside the straps thread.
This has to do with the double tap to wake gesture and once you disable double tap to wake and enable prevent accidental wakeup the bug goes away. Hope this helps others with the same bug.
Yeah Install Garaks or Seraph08s CM13 builds & Enable Prevent Accidental Wakeup
These ROM s are Stable than the Other CM Builds
As in the title proximity sensor stopped working during call, but only when taking from the ear. It don't wake up screen anymore. Anybody facing same problem? Is there a solution?
me too, all other sensor works except proximity that works one tiem then nothing
Waiting for asus fix the proximity sensor can be disabled from dialer settings to avoid the black call screen.
For me too!! It's very annoying . i have used xposed "sensor Disabler" module as a work around to completely disable proximity sensor!
I had the same on Android 5. Double tap the power button wakes it up.
I am having this slight delay in the fingerprint unlock when the device is off. There is a momentarily black screen. It is fine when I use the fingerprint to unlock the device when it is on. Please gimme some solution to this problem.
It makes sense to have a moment delay. I'd your phone is asleep, the device needs to recognize the touch, wake up the sensor, then wake up some of the CPU to compare the read vs. stored fingerprint, as well as get the stored from memory. There will be a short delay in there.
Hello, I'm very disappointed with the fingerprint sensor and the face unlock:
when I try to unlock my device after some time, the fingerprint is very slow, also the camera is revealing after 1 or 2 secs after the swipe. But if I unlock - lock - unlock again both methods are fast like they should be.
I think there is something putting them in stand-by to prevend battery drain, but is very very very very annoying and frustrating.
Is there any way to fix this?
Thanks!
Solution in post #4.
I have a H872. I had been running Havoc OS v3.1 10/01/2020 without any issues. This past weekend I decided to update to Havoc OS v3.4 21/04/2020 (clean flash) and everything was great until I realized that the proximity sensor wasn’t working. When I received a call the screen stayed black. Swiping down from the notification bar let me answer the call but the proximity sensor didn't work - screen stayed black. I couldn't even hang up - had to wait for the other caller to hang up. Same issue when I initiated the call.
I then tried Havoc OS v3.4 18/04/2020 (clean flash again) and the same calling/proximity sensor issue remained PLUS I could not send/receive MMS even though APN was set up exactly the same as my original configuration (I had taken screenshots of my original setup). I attempted Havoc OS v3.4 21/04/2020 once again and MMS stopped working too! As well as the proximity sensor issue.
I then restored my original nandroid of Havoc OS v3.1 10/01/2020. While it restored successfully in TWRP, it never booted into the system. It just hung on the last frame of the boot animation. I am at a complete loss as to how to fix this phone now. I have just installed MSM Xtended and the proximity sensor is still non-functioning. I have since switched my sim to my Xiaomi backup but really want to get back to my G6.
It worked perfectly…I attempted a simple upgrade and all hell has broken loose! Any tips? Please.
Update:
I completely restored the phone to stock with H872 20g kdz/LGUP and was able to send MMS but the proximity sensor was still not functioning. Can the sensor just suddenly go bad like that? It was working perfectly until I updated Havoc.
Anyway, I have re-rooted and reinstalled the latest havoc. I am hopeful that I will get MMS to work, however, am not sure the proximity sensor will. I have found here that Android 10 allows for all sensors to be disabled with a Quick Settings Tile. This would work for when I initiate a call (can use the power button to turn the screen off/on). But would not be able to activate it once a call comes in. Is there a way to automate the sensor to turn on/off automatically when a call comes in? Or better yet, just disable the proximity sensor, and only the proximity sensor, completely? Been Googling all morning but haven't found much aside from this toggle, and an Xposed mod that may not even work with Riru Xposed...not to mention I want to avoid Xposed if I can.
Still looking for advice if you have any.
Thanks!
Update 2:
I am now running the latest Havoc with working MMS but still the proximity sensor issue persists. I am getting around it by using the Quick Settings Tile/toggle that is activated in Developer Options. This turns off the proximity sensor, as well as compass, accelerometer, & gyroscope. So I have to remember to disable it after a call.
I have searched to no end for a way to disable the proximity sensor permanently but there is very little on the subject. I've tried some apps that claim to turn it off, but they have not worked for me. It seems to me it should be an easy thing to do...but no!
My request:
Someone that can explain how to disable the proximity sensor on Havoc, or someone that could maybe recompile the dialer.apk to not utilize the proximity sensor.
Thanks again!
Final update: Solved!
I decided to install EdXposed and Sensor Disabler. After a lot of experimenting I found settings that work. In Sensor Disabler I selected:
LGE Virtual Proximity Sensor & selected "Remove Sensor" and Saved
Proximity (There are 2 listed - I set both the same) & selected Mock Sensor Values & set them to the highest setting possible and Saved.
Now I can make & receive calls and have access to the Accept/Reject/Message functions, as well as the keypad to input if needed and can end calls. The power button is easily accessible on the back and turns the screen off & on during a call, so I can keep it off the whole time I'm talking.
Not the most ideal situation but works for me considering the proximity sensor is completely useless now. Hope this helps anyone else in the same predicament.
EDIT - Sensor Disabler doesn't appear to be the most reliable. After a reboot it's hit or miss if it will work. It seems that after rebooting it takes a couple minutes for the app to "kick" in and function...but then it only seems to work more for incoming calls. Ultimately I am still using the Quick Settings tile to turn off all sensors during calls.