Is there a way to disable the touch function of the fingerprint scanner? It drives me nuts. At first i thought it would be ghosting but then i figured out that when i tab the fingerprint scanner it selects stuff on my launcher and in system settings.
Using Arrow Os 12 beta right now and before i had Ancient OS with the same "error". Before that i had Miui Oneos and it didnt have that "function". Is it just a bug of Arrow OS 12? Why did Ancient OS 5.6 which is still android 11 also have the same problem?
Any insight on this issue?
You're more likely to receive help if you post in the respective ROM forum. This is for general questions and answers.
Related
Hello all, I've been having a problem with the fingerprint sensor and have no idea where the problem comes from.
As you can see from my comment history, I had a problem with LOS15 being unable to find my fingerprint sensor. I thought it was a bug with the ROM so I just went back to OOS and thought nothing of it.
Today, I decided to do a clean install of Android 10 beta. Fingerprint isn't working again... I rolled back with latest fastboot OOS ROM, fingerprint still wasn't working.
Downloaded MSM and went back to stable 9.0.2 - fingerprint working. Updated it to 9.0.9 - still working. Updated to 10 - not working again.
Tried the same but went from 9.0.2 to Beta 25 and then flashing 10 again, fingerprint not working again.
I'm at a complete loss, dialing *#808# and doing both fingerprint tests shows the sensor is working, but nothing happens when I touch it. Now, I have to go back to 9.0.2 with MSM and then go back to beta 25. Lost the whole day thanks to this and still can't understand why it's doing this.
I am sure it is not because of the beta itself because noone else has mentioned anything in the OpenBeta thread and because it also happened when I tried LOS.
This essentially means I'm stuck at Beta 25 or stable 9.0.9 and also that I won't be able to use custom ROMs at all.
I had the same issue, it was faulty finger print sensor. Had to get it replaced
Iamshadderz said:
I had the same issue, it was faulty finger print sensor. Had to get it replaced
Click to expand...
Click to collapse
It can't be a faulty sensor, I think... If it was faulty then how does it work now when I got back on Android 9 ? It makes absolutely no sense and it's starting to make me hate this phone.
Hi!
I have installed Resurrection Remix 8.6.4 GSI on my SM-T590.
After a few hours of testing, seems like all the functions I need are working except one, the automatic brightness setting. The sensor (CM3323E) is detected in sensor testing apps, also they can read the light value. Automatic brightness icon shows up next to the brightness slider, but it doesn't do anything, no new logcat messages are produced when I tap the icon.
Also, I have issues with WiFi and Bluetooth quick setting toggles. If the status bar icon shape is set to circular, and I tap one of them, SystemUI crashes because of a Resources$NotFound exception. I think this isn't related to the brightness sensor, more like a ROM bug, but who knows.
Where should I start debugging? I'm relatively new to Android development.
UDPSendToFailed said:
Hi!
I have installed Resurrection Remix 8.6.4 GSI on my SM-T590.
After a few hours of testing, seems like all the functions I need are working except one, the automatic brightness setting. The sensor (CM3323E) is detected in sensor testing apps, also they can read the light value. Automatic brightness icon shows up next to the brightness slider, but it doesn't do anything, no new logcat messages are produced when I tap the icon.
Also, I have issues with WiFi and Bluetooth quick setting toggles. If the status bar icon shape is set to circular, and I tap one of them, SystemUI crashes because of a Resources$NotFound exception. I think this isn't related to the brightness sensor, more like a ROM bug, but who knows.
Where should I start debugging? I'm relatively new to Android development.
Click to expand...
Click to collapse
How dit u get gsi's to work on the sm-t590?
Tab a 10.5 right?
Mikxx said:
How dit u get gsi's to work on the sm-t590?
Tab a 10.5 right?
Click to expand...
Click to collapse
Yea, I have Tab A 10.5 (2018), SM-T590.
Basically I installed TWRP from here: [RECOVERY][ROM][ROOT][UNOFFICAL] TWRP 3.3.1-0 + Lineage [SM-T590/SM-T595/SM-T597] | XDA Developers Forums (xda-developers.com)
Then I just downloaded some GSIs and flashed them to see which one works, with some changes to the original post. I may create an updated guide for installing GSI ROMs using MrHomebrew's TWRP without having to mess with SD cards, etc, but you can follow the original guide to have a mostly working system.
You can download ROMs from here: Generic System Image (GSI) list · phhusson/treble_experimentations Wiki · GitHub
I'm still not sure about how that A-only / AB thing works, if you have updated to Android 10 on stock system, AB ROMs with A64 binder will run.
I flashed the Corvus OS on my Samsung Galaxy A505-F 4GB\64GB variant and when I tried to setup fingerprint I found that it could not sense my on screen fingerprint sensor and was directing me to place my finger on the back of my phone and there is no sensor there. How can I fix this ? I like the OS and would prefer not to change it. I flashed the 64 arm ab vanilla version of the OS
I've also had the same issue on my Samsung Galaxy A31 and support for my device in the modding community is still very low but I'm hoping someone can help me create a patch for the fingerprint on my device because mine shows the fingerprint where it should be (under the display) but it doesn't scan
Hlw good people. I'm facing problem in double tap to wake. For experience i flash roolback firmware oxygen os 9 android version 9 also where double tap to wake on display work perfectly but after updating to android 10 or 11 it doesn't work at all. Then i tried some custom rom like crdroid, pixel experience and kosp but my double tap to wake on display and single tap to wake doesn't work. After that again i flash oxygen os 9 and it worked again . What is the problem? Is there any solution? Please help.
Thanks.
I also have the same problem as you. When I flashed to Android 9 with 9008, double tap to wake is working, once upgraded to Android 10 or 11, double tap to wake is not working anymore.
I think it may be that we have a special batch of 7 Pro hardware in our hands, In the previous OTA updates to fix the double-tap wake issue, OnePlus seems to have forgotten us.
But don't worry bro, I'm one of the internal test group for the Chinese version of ColorOS 12 and I've given feedback on this issue to the OPPO development engineers (oneplus is not oneplus anymore, lol) and detailed feedback on social media platforms （To this end, I recorded the whole process of upgrading from Android 9 to ColorOS 12 to prove that double tap to wake is not available, and it also includes several touch log extractions.）and the engineers told me they are trying to find the reasons of the issue.If this issue is fixed, I think the same will be available in OxygenOS 12.
lllyyyz said:
I also have the same problem as you. When I flashed to Android 9 with 9008, double tap to wake is working, once upgraded to Android 10 or 11, double tap to wake is not working anymore.
I think it may be that we have a special batch of 7 Pro hardware in our hands, In the previous OTA updates to fix the double-tap wake issue, OnePlus seems to have forgotten us.
But don't worry bro, I'm one of the internal test group for the Chinese version of ColorOS 12 and I've given feedback on this issue to the OPPO development engineers (oneplus is not oneplus anymore, lol) and detailed feedback on social media platforms （To this end, I recorded the whole process of upgrading from Android 9 to ColorOS 12 to prove that double tap to wake is not available, and it also includes several touch log extractions.）and the engineers told me they are trying to find the reasons of the issue.If this issue is fixed, I think the same will be available in OxygenOS 12.
Click to expand...
Click to collapse
Thanks for your information
If you find something further please let me know.
lllyyyz said:
I also have the same problem as you. When I flashed to Android 9 with 9008, double tap to wake is working, once upgraded to Android 10 or 11, double tap to wake is not working anymore.
I think it may be that we have a special batch of 7 Pro hardware in our hands, In the previous OTA updates to fix the double-tap wake issue, OnePlus seems to have forgotten us.
But don't worry bro, I'm one of the internal test group for the Chinese version of ColorOS 12 and I've given feedback on this issue to the OPPO development engineers (oneplus is not oneplus anymore, lol) and detailed feedback on social media platforms （To this end, I recorded the whole process of upgrading from Android 9 to ColorOS 12 to prove that double tap to wake is not available, and it also includes several touch log extractions.）and the engineers told me they are trying to find the reasons of the issue.If this issue is fixed, I think the same will be available in OxygenOS 12.
Click to expand...
Click to collapse
Brother any further news ?
And is they release any close beta 2 ?
Udaydas88 said:
Brother any further news ?
And is they release any close beta 2 ?
Click to expand...
Click to collapse
Unfortunately, after I updated colorOS beta 2, this issue still hasn't been fixed. I learned from the OPPO staff who docking with me, the 7 Pro was done by a foreign OPPO development team (not Chinese OPPO team), which means that the system development was outsourced. The OPPO staff told me that the foreign developer directly shut down the issue of this problem.
This is disappointing to me, both in the way they outsourced the development of the system and in the way the developers simply closed the issue because they couldn't find the cause of the problem.
But I'm still continuing to interface with OPPO staff and hope to bring good news in beta 3.
But then again, OPPO promised that coloros 12.1 for 7 pro would be publicly tested in June, yet it is only now, a month after beta 1 was released, that beta 2 was released, even extremely perfunctory, many obvious and serious bugs were not fixed in beta 2, OPPO's attitude towards 7 pro users is worth pondering.
Bro, I can only tell you: leave, stay away from the current oneplus and don't get your hopes up for the 7Pro. I'm using Xiaomi MIX4 as my daily phone now.
I am actually on closed beta 3 Color OS.
Very, nice. Fluid and the double tap issue seems to be resolved.
1
Udaydas88 said:
Brother any further news ?
And is they release any close beta 2 ?
Click to expand...
Click to collapse
Good news! I got the solution from my friend and my double tap to wake has worked properly. The most bizarre thing is that the OnePlus aftermarket didn't know how to fix the problem, it was another friend who came up with the cause of the problem by trying to replace the phone's motherboard, and the cause of the problem was a screen driver issue. Here's how to fix it
1. Upgrade the latest ColorOS 12 / OxygenOS 12 (necessary)
2. Enter *#899# in the dialer into EngineerMode
3. Click manual test, select the second horizontal tab DEVICE DEBUGGING, then select the TouchScreen option below
4. Enter the password 6776 (I'm using ColorOS, but I'm not sure if this is the password for Oxygen OS)
5. Follow !!the red tips!! to start calibrate until the green PASS tips.
After exiting you will find that the double click wake up is working properly, then you can return to the old build to swipe in any custom ROM and enjoy
(Off topic, OnePlus after sales service is really bad, for nothing I sent so many emails with their CSSF team)
It worked. Thank you so much
Hey everyone. I've been trying different roms on my rn11pro 5g for the last week, and it seems like fingerprint scanner won't work on them.
It was working just fine on stock miui, 13.0.2.0 global, but on project elixir (both 12.1 and 13) when trying to add a fingerprint, it reaches the last position on the fingerprint add scale, and gets stuck there. Same thing happens on Evo. On Arrow Os there's simply no fingerprint option in the security settings, not sure if by design or because of my phone.
I even flashed back to miui to check if fingerprint scanner works, and it does. But no luck on custom roms.
I also found some old threads on other redmi devices forums, and it seems like some. Xiaomi models can use different fp scanner modules, namely by either goodix or fpc, and some roms won't work with goodix.
Is that also the case for this phone? So far I've found only one person reporting the same issue as me.
I'm wondering if anyone else has encountered it, or perhaps even solved it
Trying to fix it bcuz I'm facing same on Poco
the fingerprint scanner works for me on both elixir(a13) & evolutionX(a13)
redmi note 11 pro 5G (veux eea)
JustRay76 said:
Hey everyone. I've been trying different roms on my rn11pro 5g for the last week, and it seems like fingerprint scanner won't work on them.
It was working just fine on stock miui, 13.0.2.0 global, but on project elixir (both 12.1 and 13) when trying to add a fingerprint, it reaches the last position on the fingerprint add scale, and gets stuck there. Same thing happens on Evo. On Arrow Os there's simply no fingerprint option in the security settings, not sure if by design or because of my phone.
I even flashed back to miui to check if fingerprint scanner works, and it does. But no luck on custom roms.
I also found some old threads on other redmi devices forums, and it seems like some. Xiaomi models can use different fp scanner modules, namely by either goodix or fpc, and some roms won't work with goodix.
Is that also the case for this phone? So far I've found only one person reporting the same issue as me.
I'm wondering if anyone else has encountered it, or perhaps even solved it
Click to expand...
Click to collapse
I also have problems with my fingerprint, just like you! On stock 13.0.2.0, the fingerprint is normally registered and works fine, but on any custom, the fingerprint is not registered! I have already tried to put almost all customizations for Poco x4 Pro 5g, but either there is no fingerprint registration point in the settings, or registration freezes at the last step and it is not possible to finish it! I really hope that a solution will be found over time !
Same here