General Goodix fingerprint and how to deal with it actually - Redmi Note 11 (spes/spesn)

So, I'm still reading that there are still issues with those phones that have the goodix fp sensor. I'm also one of those people. I have a rn11 with nfc (Spesn) and my phone also has this *****y goodix fingerprint sensor.
But I don't really see the big problem anymore since I found out how to deal with it. In my case the problem is directly pressing the fp-button leads to lockscreen instead of sending the phone to standby. So always when I listened to music eg, 'locked' my phone this way in hurry and put it in my pocket (screen still on) ui button actions began to start. Freaking annoying.
Until I found out that leaving the finger shortly on the fp before pressing it, did the job and the screen went properly to standby.
Long story short: if you have a goodix fp and your screen doesn't properly go to standby when pressed directly, just leave your finger for a short touch on the fp before pressing it (not even a second).
This should work until it's properly fixed everywhere.
I thought maybe there are still people who have their hassle with this issue and maybe find this helpful (like button is enough) if I share this experience here. Cheers
PS: additional experiences are welcome for sure

Its been bugging me out for a while now too. Here's a temporary fix I made while we wait for proper fixes. Install via Magisk.

3DMapPlayer said:
Its been bugging me out for a while now too. Here's a temporary fix I made while we wait for proper fixes. Install via Magisk.
Click to expand...
Click to collapse
Is this really a temporary fix for this problem?
I have a spes with Goodix sensor and in many custom ROMs I have that bug (except in Evolution X)
I'm going to try it with AncientOS (which I want to use as a daily driver for customization) and comment if everything works correctly.
EDIT: Works flawlessly on AncientOS. Probably with other ROMs with the same bug

3DMapPlayer said:
Its been bugging me out for a while now too. Here's a temporary fix I made while we wait for proper fixes. Install via Magisk.
Click to expand...
Click to collapse
Thank you, this fixes it fully!! Thanks a lot!
A question: Is there a way to patch this fix without Magisk? I don't need root and it creates lots of problems with banking apps...

douteiful said:
Thank you, this fixes it fully!! Thanks a lot!
A question: Is there a way to patch this fix without Magisk? I don't need root and it creates lots of problems with banking apps...
Click to expand...
Click to collapse
A magisk module needs magisk which needs root.

I hope more ROMs incorporate this fix for spes with goodix sensors because Magisk breaks banking apps for me and I don't need root... apparently PE already did

douteiful said:
I hope more ROMs incorporate this fix for spes with goodix sensors because Magisk breaks banking apps for me and I don't need root... apparently PE already did
Click to expand...
Click to collapse
They are doing it, but halfway, since they use an overlay to mitigate it, but you realize that you can not turn off the phone if you cover the entire button and leave it pressed. This module is the ultimate solution, but no ROM I know of has implemented it.

Bumping this because this issue still exists in some way or another in all the ROMs I've tried. The module in #2 fully fixes it but we should have this fix in ROM. I hope more devs see this.

Related

[Q] Issues with xposed on N915P (Sprint Galaxy Note Edge)

I just rooted and downloaded xposed. I've done this like 20 times now so I know it's not coincidence, but every time I install xposed, SMS sending (not receivingnevermind) is crippled. 99% of messages I try to send either hang forever or fail, every now and then one goes through (10 minutes later or something). Oddly MMS sending is not affected (receiving now seems to be). What the heck is going on‽‽‽‽‽‽‽‽
sum1 plz halp?
P.S. there may or may not be a problem with screen timeouts too. I'll post about that once I get more concrete data.
EDIT:
Some clarifications. No modules, nada. The ONLY variable is whether or not xposed is installed.
jooniloh said:
I just rooted and downloaded xposed. I've done this like 20 times now so I know it's not coincidence, but every time I install xposed, SMS sending (not receivingnevermind) is crippled. 99% of messages I try to send either hang forever or fail, every now and then one goes through (10 minutes later or something). Oddly MMS sending is not affected (receiving now seems to be). What the heck is going on‽‽‽‽‽‽‽‽
sum1 plz halp?
P.S. there may or may not be a problem with screen timeouts too. I'll post about that once I get more concrete data.
EDIT:
Some clarifications. No modules, nada. The ONLY variable is whether or not xposed is installed.
Click to expand...
Click to collapse
I can confirm that for the t-mobile variant n915t this is also an issue. For me causes eras with the settings on the edge menu, in addition to many laggy installations and random errors everywhere. I'm not using xposed until this gets resolved. I installed last stable but I am Not sure if the unreleased most recent one might be better compatible but I'm not interested in trying till someone confirms there is a working version because I am tired of playing with my phone like this I want to enjoy it lol
Eras=errors
zz1049 said:
I can confirm that for the t-mobile variant n915t this is also an issue. For me causes eras with the settings on the edge menu, in addition to many laggy installations and random errors everywhere. I'm not using xposed until this gets resolved. I installed last stable but I am Not sure if the unreleased most recent one might be better compatible but I'm not interested in trying till someone confirms there is a working version because I am tired of playing with my phone like this I want to enjoy it lol
Eras=errors
Click to expand...
Click to collapse
YES! YES! I never thought the laggy installs were related too! I didn't even get around to testing that because the SMS issue was frustrating me so much. The experimental version of xposed installer doesn't fix anything. I've just stuck my SIM in my note 3 for now until a fix is released.
Interesting thing. The guy on this thread has the same issue on as s5, but he says a kernel update fixed it . . .
EDIT:
The following threads all document similar, if not the same issues:
http://forum.xda-developers.com/xposed/xposed-touchwiz-stock-messaging-app-t2795905
http://forum.xda-developers.com/xposed/issues-xposed-n915p-sprint-galaxy-note-t2947850
http://forum.xda-developers.com/note-edge/help/n915p-cf-auto-root-fails-t2944539
http://forum.xda-developers.com/xposed/xposed-note-4-t2928864
Find a fix yet zz1049?
jooniloh said:
Find a fix yet zz1049?
Click to expand...
Click to collapse
Not yet until then I'm just finding replacement rooted apps to fill the gaps in till then..
http://forum.xda-developers.com/note-edge/help/q-successfully-rooted-note-edge-n915t-t2940554/page6
Member pieces of cake stated he resolved it it was simple, don't know what that really means but you could ask him. I checked there has not been any new uploaded versions of Xposed. I'm just going to wait for a patch to Xposed unless we hear of any fixes.
zz1049 said:
Not yet until then I'm just finding replacement rooted apps to fill the gaps in till then..
http://forum.xda-developers.com/note-edge/help/q-successfully-rooted-note-edge-n915t-t2940554/page6
Member pieces of cake stated he resolved it it was simple, don't know what that really means but you could ask him. I checked there has not been any new uploaded versions of Xposed. I'm just going to wait for a patch to Xposed unless we hear of any fixes.
Click to expand...
Click to collapse
ugh. well I guess whatever works. I was rather dependent on greenify's xposed features and wanam. I hope someone figures out a fix soon.
try this guys
Just disable secure storage in Wanam this fixes the lag as others mentioned
Its Wanam Xposed, under "Security" tab and checkbox "Disable Secure storage" and/ or used XSecureStorage module.
http://besttopics.net/link/189924_fix-how-to-fix-xposed-framework-lag-on-note-4

Rotation bug with EVERY available rom!

Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
dont think its a software problem, maybe you should get your phone checked out
njuz said:
Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
Click to expand...
Click to collapse
Its of course a well know bug for all mi5 roms. I read yesterday that last thursday rom update fix this:
"Fix - Accelerometer and gyroscope didn't work after and OTA update (08-12)
Fix - Accelerometer and gyroscope didn't work normally (08-12)"
The problem occured with miui as well as with unofficial CM build, what i am using now. This indicates to me that it has nothing to do with the installed rom directly.
After rebooting, everything works fine again.
I suspect apps like Pokémon go to stay in relation to the bug. Since i am not playing that game anymore it occures much rarer...
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
I was having the same problem. I dont play pokemon. Im still on vendor rom. But now the bug gone i tried to simulate the bug but it rotate normally
I have this issue. I'm on the latest CM 13 build and I get issues where the camera won't take in landscape and full screen videos won't switch to landscape when you rotate the phone. It's so nearly perfect apart from that.
shucrut said:
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
Click to expand...
Click to collapse
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
I installed a couple of Sensor Test apps and neither one can see my accelerometer sensor to even test it. So it's like the sensor isn't even there. I know it works because one of Shade.sh's beta CM 13 builds was able to detect the sensor OK! Any ideas?
Here's the sensors detected in the Check My Android app. There seems to be only two axis detectors working. How does this compare to a healthy Mi 5?
sharkyblunt said:
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
Click to expand...
Click to collapse
Yes, i actualy did. After installing developer version 6.9.18 the problem never appeared again. Now im on 6.9.22 and the rotation bug is gone
Hmm, I've just tried SlimRom and the same bug is present, presumably because it's derived from the same tree as CM 13.
I'm actually tempted to give MIUI 6.9.22 a go then if it's the only way to get this fixed.
I have just flashed the MIUI developer ROM 6.9.2.2 and my sensors are working perfectly now. So it must be something for flaky in the CM stack or Kernel version. See screenshot.

RP2-specific fixes/updates with 9.0 update?

To those who have updated to Android 9.0, have you seen any improvements/fixes specific to the RP2? I know many of us have noted issues with the speakers (notably at lower volumes) and the camera software (mostly fixed by using Gcam), although there's been other more isolated/random issues for some too (Bluetooth, cellular signal, etc).
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Hangouts doesn't give a notification sound when the app isn't open. I've made another thread about that earlier
------------------------------------------------------------------------------
Never mind. Had to go deep into Hangouts settings to fix it. Still annoying
I would willingly trade fully functional wifi for speakers that don't crackle and cut out at lower volumes, since I have unlimited data and solid LTE signal everywhere I go. Though I've had that wifi issue on rare occasion on Oreo too.
They moved the clock :'(
Anyone notice potential decrease in touch sensitivity after the upgrade? I had a screen protector on and it seemed like I need to push down a little more to get the touches to register. Took off the protector to test and it was fine with just the screen. Put another one on and occasionally touches aren't registering or registering but releasing early on swipes.
Sent from my Phone 2 using Tapatalk
CalebQ42 said:
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Click to expand...
Click to collapse
How do you unlock your bootloader, bro? How did you root your phone?
acegrace said:
How do you unlock your bootloader, bro? How did you root your phone?
Click to expand...
Click to collapse
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Gamesoul Master said:
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Click to expand...
Click to collapse
crap, i just updated last night - can i factory reset and do the same thing?
alawiggle said:
crap, i just updated last night - can i factory reset and do the same thing?
Click to expand...
Click to collapse
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Gamesoul Master said:
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Click to expand...
Click to collapse
nice, thanks!

Woke up...phone is dead

Guys,
I have Tencent version with WW fingerprint. Had it since end of September. It will not charge (no lights) and not turn on with any combination of power and volume etc. I have tried both ports in a PC and nothing.
If anyone can help, great, but I'm not optimistic. Anyone know if there was an update last night. I did have Asus Launcher 1.04 by HomerSP installed (https://forum.xda-developers.com/rog-phone-2/themes/app-asusupdater-ww-updates-tencent-t4022547) and was just wondering if somehow it did update but I suspect something went pop in the night. It was charging at the time.
I'm in the UK so I doubt Asus will honour a warranty.
Thanks guys for taking the time to read.
EDIT: Guys Phone just came on. Held down power and plugged it in to my PC. Sorry for the time you wasted reading this....
Glad u fix it, i think it's software issue, before i had a few bugs like fps drops in games, screenrotation after unlocking screen etc... For me that default rom is really crap, so looking forwrd for Android10 and custom roms. Btw i can recommend to flash kernel from here https://forum.xda-developers.com/ro...rnel-kirisakura-1-0-0-asus-rog-phone-t4028237 - since then i didn't have serious issue
Thanks for the suggestion. I do like custom ROMs but I need to retain my banking apps. Using magisk modules didn't help with my old doggee S60 phone... They still spotted the root.
If anyone can confirm it works with starling, vanquis and EE I'd give it a go
scum2000 said:
Thanks for the suggestion. I do like custom ROMs but I need to retain my banking apps. Using magisk modules didn't help with my old doggee S60 phone... They still spotted the root.
If anyone can confirm it works with starling, vanquis and EE I'd give it a go
Click to expand...
Click to collapse
Did You change magisk manager's app name? Did the trick for me (hide etc ofc enabled)
VarDes said:
Did You change magisk manager's app name? Did the trick for me (hide etc ofc enabled)
Click to expand...
Click to collapse
Yes, I tried that on S60 made no difference. It's coming to the point where I may risk it. I miss twrp and I want to have LTE and WiFi calling. I'm sick of waiting for Asus to official activate them. I'm really happy with the phone overall.

Pixel 4XL Face Unlock

I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.
@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.
@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.
sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.
@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM
this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(

Categories

Resources