Fingerprint Scanner wont unlock even after data/cache wipe

[GoogleCodeExporter]

Phone (Int/AT&T/etc.):AT&T
Radio:91
CM Release (NO NIGHTLIES!):Weekly build, 2011-12-10
Hacks/Mods used:none
Kernel: inclued in cm7

What is the expected behavior?
the fingerprint scanner will unlock the phone at the lockscreen.

What is the actual behavior?
i unlock the lock screen and instead of it reading"swipe finger for unlock" it 
says "screen on:. when i try to swipe my finger it say UI timeout and goes into 
lockout mode for 30 seconds. after 30 seconds is over it says "screen on" again 
and the whole process is repeated. i tried re flashing rom, wipedata and wipe 
cache, then flash and still not results. after setting up finger print scanner 
after fresh install it works for the first unlocfk and then after it goes back 
to scrren on/ui timeout. please help me my phone is locked. thank you guys so 
much for all the work you do, it is greatly appreciated.

What steps will reproduce the problem?
1.locking the screen. 
2.trying to change the screen lock to password instead of fingerprint 
3.

Can you reproduce this problem after a complete wipe/factory reset? (do not
restore any apps or settings when testing)

yes as stated above

Possible workarounds: none that i can think of because phone is completely 
locked

Original issue reported on code.google.com by reggieme...@gmail.com on 17 Dec 2011 at 6:08

[GoogleCodeExporter]

hi!
I'm having the same problem here since weekly 23-nov. It works again rebooting 
by pulling the baterry off (once in a while don't, just repeat it until unlock 
the fps). Its not a hardware problem cause if you go back to homebase or alien, 
no such problem.
Even in the "screen on" bug, if u go to the emergency dialing screen the fps 
works perfectly as a touchpad (???). Everytime that I managed to get the fps 
"unlocked", the wallpaper is back to default (my only clue). It's intermittent 
(and annoying), so I changed the locking method to PIN, everything else is 
perfect.
Thanks.

Original comment by apedrop...@gmail.com on 17 Dec 2011 at 8:41

[GoogleCodeExporter]

I forgot to says my specs: at&t, cm7 weekly 10dec, .30P radio, clemsyn no oc 
kernel ( i tried other kernels but got the same issue).

Original comment by apedrop...@gmail.com on 17 Dec 2011 at 8:45

[GoogleCodeExporter]

I flashed a friends Atrix earlier and now she has the same issues.

steps performed
-unlock bootloader
-install CWM recovery
-install cyanogen
-install gapps
-reboot
-configure phone
-enroll fingerprint
-test unlocked the phone - worked
-rebooted the phone - could no longer unlock, 
-same behaviour as above: the phone keeps timing out

-performed cache wipe and factory reset
-rebooted
-configured the phone
-fingerprint enrollment now fails?
-resorted to a pattern on her phone for now. 

her phone is only about a month old and the FP scanner was working fine until 
flashing CM. I haven't had any issues with my Atrix

Original comment by syntheti...@gmail.com on 23 Dec 2011 at 7:07

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

i have this issue ... FingerPrint Database corrupt...
No solution... come back from nandroid to solv..

This is because i have enroll 8 fingerprints .. with 2 fingerprint no  issue

8 fingerprint enroll... wait phone discharge to 0%... reboot... and no cant 
unlock.. Wait for ask my Google account to unlock.. try to go back in 
fingerprint menu... ForceClose with "database error code #6"... when... Boot 
loop..
Wipe or flash rom again don't solv ... Only flash old nandroid solv (to go back 
to Ba2Tf) solv..

Message on log : "corrupt database : error code #6"

Original comment by renaud....@gmail.com on 24 Dec 2011 at 5:38

[GoogleCodeExporter]

Same issue. The tract feature still works but refuses to enroll fingers after 
reboot. I get an error=6 or 17

Original comment by Mark.Muf...@gmail.com on 24 Dec 2011 at 5:58

[GoogleCodeExporter]

I seemed to fixed my issue. I recently decided to reinstall the December 10th 
nightly, wiped the data and the cache and DID NOT restore any apps. I think 
this was my problem...i  haven't had any problems at all in the last week. I 
hope this helps!

Original comment by Mark.Muf...@gmail.com on 14 Jan 2012 at 3:42

[GoogleCodeExporter]

Will this issue never be fixed?? We're already on weekly #5!! This is a 
critical issue. It locks completely the cel, even after a reboot, forcing us to 
wipe data and reinstall everything. Very boring. A possible workaround is 
enable an alternate way (PIN) to unlock the phone. C'mon people. You're the 
best!!

Original comment by djmso2...@gmail.com on 26 Jan 2012 at 1:26

[GoogleCodeExporter]

@comment 8, an alternate way is already there, if you fail and get blocked 
twice/three times, you can unlock with your google account.

If there is anyone else with an issue after a reinstall and no data/apps 
restore, please say so and post a logcat after being locked out of your phone, 
otherwise I'll close this report.

Original comment by buhitoes...@gmail.com on 26 Jan 2012 at 8:07

• Changed state: WaitingForUser

[GoogleCodeExporter]

Hi everyone!

I'm finally managed to reproduce this weird bug (damn, I stopped using FP long 
time ago only because of this!!!!!).

Well, fp unlock stops working when you disable USB debbuging!!!! And that's 
it!!! If you change any other setting it doesn't happen. Since it involves USB 
debbuging I can't do a logcat (can I? Buhitoes, if there's a way to do it I 
offer myself to, because my phone has no personal data at the moment).

If you want to test, here goes the steps (remember to NAND backup because you 
will be unable to unlock even with google credentials):
1 - full wipe
2 - install cm7 normally
3 - ending first boot, register your finger print and make it you unlock pattern
4 - go to settings > applications > development > USB debugging and unmark it
4 - reboot and you're locked!!

Hope it helps! Thanks for the awesome work with cm!!

Original comment by apedrop...@gmail.com on 28 Jan 2012 at 8:21

[GoogleCodeExporter]

You can use one of the wifi adb apps on the market to get a logcat.

PS: if you get locked you can re-enable adb to gain access from recovery

adb shell

and inside

mount /data
echo -n 1 > /data/property/persist.service.adb.enable
sync
reboot

Original comment by buhitoes...@gmail.com on 29 Jan 2012 at 4:11

[GoogleCodeExporter]

What's the status of this on the latest nightly? I haven't been able to 
reproduce

http://get.cm/?device=olympus

Original comment by buhitoes...@gmail.com on 10 Mar 2012 at 7:04

[GoogleCodeExporter]

Granted not the latest nightly, but I ran into this same behavior on nightly 
12-11-2011, and re-enabling adb via recovery did allow me to finally gain 
access.  Thanks for the notes and workaround!

Original comment by aram.ebl...@gmail.com on 16 Mar 2012 at 1:33

[GoogleCodeExporter]

Original comment by buhitoes...@gmail.com on 2 Apr 2012 at 8:19

• Changed state: Stale