[Atrix 4G General] Mgamerz:
Lock Screen

But to get the Atrix Lockscreen (I dont know if moto or authentec made that - it could just be under authentecs package) you'd also need to implement however the lockscreen works.

On the app I am developing I am going to try and add a vibration on sucessful swipes, as I can't figure out how to do it on invalid ones (I beleive the swipe is a separate thread that overlays the current activity - the lock screen doesn't use the swipe to continue at all I think (even if hidden by the lockscreen itself).

I know that there are effectively two lock screens as when you kill the swipe it kicks to the pin.

08-08 13:17:59.743: INFO/FingerprintLockScreen(1549): LAP Verify END
08-08 13:17:59.743: INFO/FingerprintLockScreen(1549): Releasing semaphore
08-08 13:23:11.336: INFO/FingerprintLockScreen(1549): Trying to acquire semaphore
[COLOR="Red"]08-08 13:23:11.336: INFO/FingerprintLockScreen(1549): LAP Verify BEGIN[/COLOR]
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: command = screen
[B]08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: args = unlock-device[/B]
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: command = settext
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: args = appname Unlock
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: command = show
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: args = D4
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: command = show
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: args = D7
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: command = show
08-08 13:23:11.846: WARN/FingerprintLockScreen(1549): receiveCommand: args = please_swipe
08-08 13:24:11.307: WARN/FingerprintLockScreen(1549): onPause: Issuing thread interrupt
08-08 13:24:11.466: INFO/FingerprintLockScreen(1549): LAP Verify END
08-08 13:24:11.466: INFO/FingerprintLockScreen(1549): Releasing semaphore

I believe the lock screen is built by whatever is writing to FingerprintLockScreen Log Tag.

The bold line I beleive is the command that you use to specifiy what type of verification is requested (get-app-secret, lap-verify) as its the only command in the list (and the SDK) that uses the - marks. Going to test to see if anything shows up (I doubt it as I can't pass additional commands in the SDK they give - but if I can just get a blank slate that'd be pretty cool!)

Edit: the red line though shows lap-verify command... will try to see what happens though

Update: It... works... I mean, I don't know the commands to send to the builder (if thats what it uses) to configure the lock screen, but I think that's how the atrix lockscreen works, it builds it with a bunch of commands. "unlock-device" Update: it is binded to the lockscreen only is a valid command as it doesn't automatically hang.

The result however, is that the lock screen does initialize the sensor, and on any swipe it kicks to the pin code... different than when it just hanged (instead it wouldn't do anything)... im' guessing moto had a hand in the lock screen as it uses thier fugly swipe bars to pin and sound.

After passing the command "unlock-device" to it this is what comes under FingerPrintLockScreen:

08-08 13:47:29.696: INFO/FingerprintLockScreen(1549): Trying to acquire semaphore
08-08 13:47:29.716: INFO/FingerprintLockScreen(1549): LAP Verify BEGIN
08-08 13:47:31.763: INFO/FingerprintLockScreen(1549): LAP Verify END
08-08 13:47:31.763: INFO/FingerprintLockScreen(1549): Releasing semaphore

There is also "confirm-user" by it is binded to com.authentec.FingerprintSettings