I'm running latest Resurrection remix on Redmi Note 4X. After I wiped Dalvik and cache today I noticed I had only one fingerprint memorized (right index finger), although I had 2.
Even worse is the fact that when I use that fingerprint to unlock I get the double vibration feedback and then the fingerprint scanner stops responding and I have to unlock with power button and swipe. If I use the other fingerprint it usually unlocks fine until I try the faulty one again and then I get no response from the scanner.
I tried:
- deleting fingerprints and adding new ones
- wiping cache and dalvik after removing all fingerprints.
- reflashing the rom
nothing worked, the right hand fingerprint still causes the scanner to, i guess, crash. Here's some logcat data:
When using right index finger:
Code:
D/FingerGoodix( 1530): fpcode, fingerprint_cancel()
D/FingerGoodix( 1530): fingerprint_cancel
D/FingerGoodix( 1530): fpcode, fp cancel!
D/FingerGoodix( 1530): finger print client call cancelRecognize!
D/FingerGoodix( 1530): client,cancel recognize
I/fingerprintd( 1530): type=1400 audit(0.0:650): avc: denied { call } for scontext=u:r:fingerprintd:s0 tcontext=u:r:init:s0 tclass=binder permissive=1
D/FingerGoodix( 1018): server,cancel recognize
D/FingerGoodix( 1018): Client::cancelRecognize 1
D/FingerGoodix( 1018): Already canceled!
D/FingerGoodix( 1530): fpcode, setListenerState(0x7f7744c000, 3)
W/FingerprintService( 1965): client com.android.systemui is no longer authenticating
When using a working fingerprint:
Code:
D/FingerGoodix( 1018): Received message: 0. gIRQFlag:1
D/FingerGoodix( 1018): gf_netlink_event, event:0
D/FingerGoodix( 1018): g_mode = 1
D/FingerGoodix( 1018): gf_ready_spiclk. g_spi_clk = 1
D/FingerGoodix( 1018): fnCa_GetStatus()
D/FingerGoodix( 1018): fnCa_GetStatus(), in
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 18
D/FingerGoodix( 1018): fnCa_GetStatus(), out
D/FingerGoodix( 1018): gf_netlink_event 448 status 0x2 g_mode 1 g_state 1
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 19
D/FingerGoodix( 1018): KEY:key down touch_status = 0x2, g_state = 1
D/FingerGoodix( 1018): wby master donot send key down 1!
D/FingerGoodix( 1018): notifyClient,type:2002,msg:0,ext:0,clientID:0
D/FingerGoodix( 1018): getChipMode = 1
D/FingerGoodix( 1018): it is in MODE_KEY,don't report event to Application
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 60
D/FingerGoodix( 1018): init and start timer
D/FingerGoodix( 1018): init and start timer success
D/FingerGoodix( 1018): Received message: 0. gIRQFlag:1
D/FingerGoodix( 1018): gf_netlink_event, event:0
D/FingerGoodix( 1018): g_mode = 1
D/FingerGoodix( 1018): gf_ready_spiclk. g_spi_clk = 1
D/FingerGoodix( 1018): fnCa_GetStatus()
D/FingerGoodix( 1018): fnCa_GetStatus(), in
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 18
D/FingerGoodix( 1018): fnCa_GetStatus(), out
D/FingerGoodix( 1018): gf_netlink_event 448 status 0x0 g_mode 1 g_state 3
D/FingerGoodix( 1018): #### Invalid int. g_mode = 1
D/FingerGoodix( 1018): Received message: 0. gIRQFlag:1
D/FingerGoodix( 1018): gf_netlink_event, event:0
D/FingerGoodix( 1018): g_mode = 1
D/FingerGoodix( 1018): gf_ready_spiclk. g_spi_clk = 1
D/FingerGoodix( 1018): fnCa_GetStatus()
D/FingerGoodix( 1018): fnCa_GetStatus(), in
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 18
D/FingerGoodix( 1018): fnCa_GetStatus(), out
D/FingerGoodix( 1018): gf_netlink_event 448 status 0x2 g_mode 1 g_state 3
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 19
D/FingerGoodix( 1018): KEY:key up touch_status = 0x2, g_state = 3
D/FingerGoodix( 1018): wby master donot send key up 0!
D/FingerGoodix( 1018): notifyClient,type:2001,msg:0,ext:0,clientID:0
D/FingerGoodix( 1018): getChipMode = 1
D/FingerGoodix( 1018): it is in MODE_KEY,don't report event to Application
D/FingerGoodix( 1018): delete timer
D/FingerGoodix( 1018): delete timer success
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 63
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 60
D/FingerGoodix( 1018): Received message: 0. gIRQFlag:1
D/FingerGoodix( 1018): gf_netlink_event, event:0
D/FingerGoodix( 1018): g_mode = 1
D/FingerGoodix( 1018): gf_ready_spiclk. g_spi_clk = 1
D/FingerGoodix( 1018): fnCa_GetStatus()
D/FingerGoodix( 1018): fnCa_GetStatus(), in
D/FingerGoodix( 1018): gx_ta_send_command, cmd = 18
D/FingerGoodix( 1018): fnCa_GetStatus(), out
D/FingerGoodix( 1018): gf_netlink_event 448 status 0x0 g_mode 1 g_state 1
D/FingerGoodix( 1018): #### Invalid int. g_mode = 1
I/PowerManagerService( 1965): Waking up from dozing (uid 1000)...
Update:
The problem remains when using MIUI Global stable and developer. Relocking the bootloader doesn't help either!
The right index fingerprint is read correctly on a Redmi 3 Pro.
arguson said:
Update:
The problem remains when using MIUI Global stable and developer. Relocking the bootloader doesn't help either!
The right index fingerprint is read correctly on a Redmi 3 Pro.
Click to expand...
Click to collapse
Did you use the Mi Flash tool to go to Global stable? Or did you use TWRP? If you used the latter, I think you should try a "Clean All and Lock" using Mi Flash tool.
I did a fastboot flash with clean and then with clean and lock option just to be sure
One guy I know had this issue.
He flashed back to MIUI, created second space, registered Fingerprint and then deleted Second Space. Now it's working for him.
Sent from my Redmi Note 4 using XDA Labs
ForgottenDude said:
One guy I know had this issue.
He flashed back to MIUI, created second space, registered Fingerprint and then deleted Second Space. Now it's working for him.
Sent from my Redmi Note 4 using XDA Labs
Click to expand...
Click to collapse
I have the same issue and i tried it, doesn't seem to work :/
arguson said:
I did a fastboot flash with clean and then with clean and lock option just to be sure
Click to expand...
Click to collapse
:/
Tried creating Second Space and it gives me an error when i try to enter a new fingerprint. The fingerprint service vibrates once and then stops receiving inputs altogether
Did you ever solve this? I just got this issue after wiping dalvik and cache.
Does anyone have a solution? I also have the same problem in my Mi Note 3.
Related
Hello fellow Androiders.
I have an HTC Desire for about a year and a half, and over the weekend, during snowboarding it got wet in my pocket (found a snowball in there, next to it!). I checked it, it was switched off. After returning home, i dried it and switched it back on, but it wouldn't boot the system, so i reflashed it (with sandvold.as' ICS). Seemed to work fine after formatting all mounts, except for one thing: the screen wouldn't switch off:
When i pressed the power button, the screen would switch off for much less than a second and instantly pop back with the lock screen, as if i hit the power button again. If i disable the lockscreen, it jumps back to the previous activity and instantly acts as if the volume down button was pressed.
So i started looking for what the problem could be, found a tip to play around with /system/usr/keylayout/bravo-keypad.kl
It seemed to help after i removed the WAKE from next to the volume keys, but instead of switching back on straight away, it reboots after one second (i can see the charging LED stops shining after 1 sec).
Despite of installing new ROM, this behavior stayed. I am now running the latest Oxygen.
I did an "adb logcat" (through adbWireless) and here's the output, with comments:
Code:
D/jdwp ( 273): adbd disconnected
D/jdwp ( 638): adbd disconnected
D/su ( 716): 10045 siir.es.adbWireless executing 0 /system/bin/sh using shell /system/bin/sh :
sh
D/jdwp ( 321): adbd disconnected
D/jdwp ( 220): adbd disconnected
D/jdwp ( 610): adbd disconnected
W/InputManagerService( 140): Window already focused, ignoring focus gain of: com.android.internal.v
[email protected]
D/dalvikvm( 623): GC_EXPLICIT freed 338K, 50% free 2855K/5639K, external 1690K/2137K, paused 47ms
I/power ( 140): *** set_screen_state 0
I/power ( 140): *** set_screen_state 1
D/dalvikvm( 140): GC_EXTERNAL_ALLOC freed 1021K, 42% free 5357K/9223K, external 5185K/5259K, paused
62ms
D/SurfaceFlinger( 140): About to give-up screen, flinger = 0x8ec90
D/SurfaceFlinger( 140): Screen about to return, flinger = 0x8ec90
D/AK8973 ( 120): Compass CLOSE [COLOR="Red"]// At this point somewhere the screen turned off, and instantly comes back on. I find the compass CLOSE/Start statechange a little weird. This causing the problem would make sense, since it could have been physically damaged[/COLOR]
D/AK8973 ( 120): Compass Start
W/InputManagerService( 140): Starting input on non-focused client android.view.inputmethod.InputMet
[email protected] (uid=1000 pid=140)
I/power ( 140): *** set_screen_state 0
D/SurfaceFlinger( 140): About to give-up screen, flinger = 0x8ec90
D/AK8973 ( 120): Compass CLOSE [COLOR="red"]// Here i hit the power button again. This time the screen stays black and doesn't come back on. Pressing the power button again (in hope of bringing the screen back), restarts the device after one second. This is the end of output[/COLOR]
Does anyone have any idea what to do next? Easiest would be to move on, get a new device, but there's something I love about bringing back a device from the dead. I appreciate any ideas.
Thanks,
Z.
PS: does anyone know if i could disable the compass on low-level? I suppose that would require a new kernel (?)
really, noone has any idea?
i can provide more data if needed but i dont know where to look
Hi folks.
My phone is a routed Samsung S4 i9505.
I'm impressionated with what tasker can do for us. It's fantastic.
A small annoying issue I have is a message which appears always after a profile get running that says "facebook session expired , initiate session again".
I created a profile configured to trigger when phone status is orientation face down ( It works so greate !!! ).
--> When above profile condition is true, I call a task:
- Turn OFF : Wifi, Mobile Data, Bluetooth, Auto-Sync, Auto brightness, Keyguard;
- Enable : Power save mode , Blocking mode ,
- Display brightness to 0, Display timeout 7,0,0 ( seven seconds).
--> EXIT task (When my phone is not face down position):
- Turn ON : Wifi, Mobile Data, Bluetooth, Auto-Sync,
- Keyguard (continues OFF); Auto brightness (continues OFF).
- Disable : Power save mode , Blocking mode , Display brightness to 255, Display timeout 0,5,0 ( Five minutes ).
When Exit task runs, I get that message saying : "facebook session expired , initiate session again".
How to solve this ?
Glauco
I'm working on an app to turn on the screen when my tablet is rotated from horizontal to vertical. It works as
desired when it runs at the same time as the Shake app.
When the Shake app is not running, it can take 10 to 20 seconds to much longer to never for the screen to come on after I've rotated the tablet.
What does Shake do that lets my app work as desired? What can I change in my app so the screen comes on very soon after the tablet is rotated.
The code that turns on the screen:
Code:
// Turn on the screen
PowerManager pm = (PowerManager)getSystemService(Context.POWER_SERVICE);
PowerManager.WakeLock wl = pm.newWakeLock(PowerManager.SCREEN_BRIGHT_WAKE_LOCK
| PowerManager.ACQUIRE_CAUSES_WAKEUP, "tag");
wl.acquire();
System.out.println("ScrnOnOffSrvc Turned on screen at "+ sdfTime.format(new java.util.Date()));
try{Thread.sleep(100);}catch(Exception x){} // wait some ???
wl.release(); // get rid of it and hope screen stays on a while???
My screen timeout keeps setting itself to 10 minutes even though I set it at 15 seconds repeatedly .
Set it at 15 and reboot immediately. Not sure it will work but try it.
Hey everyone, when I am in a call and I take my phone away from my face, it takes a good 5 seconds for the screen to come on. I downloaded an app to read the sensors, and when I uncover the sensor, it stays at 0.00 cm. I've already tried getting the Verizon Hidden Menu back to see if I can calibrate it, but I always get the following error when running the `am` command:
Code:
Starting: Intent { act=android.intent.action.MAIN cmp=com.lg.hiddenmenu/.HiddenMenu }
Error type 3
Error: Activity class {com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu} does not exist.
Are there any other ways of calibrating it?