Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

S5: Finger print lockscreen stops working #1759

Closed
DirkStorck opened this issue Jun 26, 2014 · 25 comments
Closed

S5: Finger print lockscreen stops working #1759

DirkStorck opened this issue Jun 26, 2014 · 25 comments

Comments

@DirkStorck
Copy link

Hi,

If I use fingerprint lockscreen on my S5 and I have XPrivacy activated and reboot the phone the fingerprint lockscreen stops working: I have to unlock the device with the alternative passwort.
I looks like the whole finger print sensor stops working because if I enter settings where I can register a finger print and use that option I get a message telling me that the sensor does not work I have to reboot the phone.

Thanks!

@M66B
Copy link
Owner

M66B commented Jun 26, 2014

Without a logcat there is nothing I can do.

@DirkStorck
Copy link
Author

Where can I add a logcat? Thx

@M66B
Copy link
Owner

M66B commented Jun 26, 2014

You can use gist to paste the logcat too and reference it from here.
Be sure to enable XPrivacy debug logging before capturing a log and please keep the logcat as short as possible. Finding a problem in megabytes of log lines is hard ...

@DirkStorck
Copy link
Author

Ok. Thanks. Here is the logcat

https://gist.github.com/89be1975a1f83f4aa066

@M66B
Copy link
Owner

M66B commented Jun 26, 2014

There is nothing about XPrivacy in the logcat.
Did you enable XPrivacy debugging in the XPrivacy main settings?

@DirkStorck
Copy link
Author

Yes sorry man...noticed that I forgett to activate debug in XPrivary
Here again with debug enabled

https://gist.github.com/3e68338182b36b310262

@Bleep5143
Copy link

I just wanted to point out that I too am experiencing the issue described above after the most recent update of xprivacy. I'll work on getting you a logcat as well. (Galaxy S5 T-Mobile)

@M66B
Copy link
Owner

M66B commented Jun 27, 2014

Unfortunately I cannot find anything wrong in the logcat.
No warning, no errors, no crashes, nothing unusual.
Please try again with the version I will release today, maybe some of the changes I did will fix this.

@Bleep5143
Copy link

https://gist.github.com/tracerfett/3ce9300b53d018544ca5 (Logcat from today)
https://gist.github.com/tracerfett/77fb3cba963999d7361c (one from yesterday)

Hopefully there is something useful in there... I enabled recording of logcat, went into the Fingerprint registration app, and attempted to connect to the reader multiple times (each time popping up a message about an issue with accessing the reader), then saved to the gists above.

@M66B
Copy link
Owner

M66B commented Jun 27, 2014

What exactly is the error message shown?

@M66B
Copy link
Owner

M66B commented Jun 27, 2014

It looks like the secure storage cannot be read:

06-27 06:53:01.385 E/SecureStorage(  339): [ERROR]:SPID(0x0000001C)internal error
06-27 06:53:01.385 E/SecureStorage(  339): [ERROR]:SPID(0x0000001C)internal error
06-27 06:53:01.385 I/SecureStorage(  339): [INFO]: SPID(0x0000001C)Secure Storage Daemon finished processing with result: -2
06-27 06:53:01.385 I/SecureStorage(  339): [INFO]: SPID(0x0000001C)PID: 2899, TID: 2899
06-27 06:53:01.385 E/SecureStorage(  339): [ERROR]:SPID(0x0000001D)Processing of client command finished with error
06-27 06:53:01.385 E/SecureStorage( 2899): [ERROR]:SPID(0x00000000)dynamic libraries buffer length error
06-27 06:53:01.385 E/SecureStorage( 2899): [ERROR]:SPID(0x00000000)Error processing data
06-27 06:53:01.385 E/SecureStorage( 2899): [ERROR]:SPID(0x00000000)Android: read data error: -2

This might be caused by a timing issue caused by XPrivacy.
If this is the case it can probably not be fixed.

I am assuming the secure storage is used to store the fingerprint.

@Bleep5143
Copy link

The error is:

Attention
An error has occurred with the fingerprint sensor. If this message appears repeatedly, restart your device.

Obviously I've restarted and what not... I don't understand why I didn't have any issues with previous version of XPrivacy... I'm rolling back version by version to see what the latest workable version is. I'll let you know once I find out.

@Bleep5143
Copy link

2.1.6 is the most recent working version for me

@M66B
Copy link
Owner

M66B commented Jun 27, 2014

A lot has been changed from 2.1.6...2.1.8

@M66B
Copy link
Owner

M66B commented Jun 27, 2014

Assuming you have tried version 2.1.12 already (else please do so), can you try these versions:

IPC/Reflection disabled:
https://crowd.xprivacy.eu/XPrivacy_2.1.12-2.apk

IPC/Ixxx disabled:
https://crowd.xprivacy.eu/XPrivacy_2.1.12-3.apk

@Bleep5143
Copy link

Yes I have. I'll give those two a shot and report back

On Fri, Jun 27, 2014 at 10:21 AM, Marcel Bokhorst [email protected]
wrote:

Assuming you have tried version 2.1.12 already (else please do so), can
you try these versions:

IPC/Reflection disabled:
https://crowd.xprivacy.eu/XPrivacy_2.1.12-2.apk

IPC/Ixxx disabled:
https://crowd.xprivacy.eu/XPrivacy_2.1.12-3.apk


Reply to this email directly or view it on GitHub
#1759 (comment).

@Bleep5143
Copy link

2.1.12-2 worked ok
2.1.12-3 had the same issue with the finger print reader
Updated logcat for .12-3: https://gist.github.com/tracerfett/0f974581f8d000690b8f

@M66B
Copy link
Owner

M66B commented Jun 27, 2014

I like to see a logcat for 2.1.12-2 too.

@Bleep5143
Copy link

Sure thing

On Fri, Jun 27, 2014 at 11:15 AM, Marcel Bokhorst [email protected]
wrote:

I like to see a logcat for 2.1.12-2 too.


Reply to this email directly or view it on GitHub
#1759 (comment).

@Bleep5143
Copy link

M66B added a commit that referenced this issue Jun 28, 2014
@M66B
Copy link
Owner

M66B commented Jun 28, 2014

Can you please try if this version fixes the problem:
https://crowd.xprivacy.eu/XPrivacy_2.1.12-4.apk

@DirkStorck
Copy link
Author

Hi. I can confirm that Finger Print is working fine for me with XPrivacy_2.1.12-4.apk

Thank you for you effort !

@M66B
Copy link
Owner

M66B commented Jun 28, 2014

Thanks for testing and reporting back!

@M66B M66B closed this as completed Jun 28, 2014
@tyl0re
Copy link

tyl0re commented Jun 28, 2014

Thanks Allot

@Bleep5143
Copy link

Yes, thank you!
On Jun 28, 2014 4:52 AM, "Marcel Bokhorst" [email protected] wrote:

Closed #1759 #1759.


Reply to this email directly or view it on GitHub
#1759 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants