If I was to aquire an E4 for parts that had a working fingerprint scanner, is there a possibility of me getting it to work on my metro variant with no scanner? I'm fairly knowledgeable when it comes to replacing phone parts with other phone parts but I'm curious if this would be possible.
It might be possible as long as the board on your device has the connections for the sensor or a place to add the connections. You'd need the firmware with the finger print scanner files for it to actually work though I would imagine.
Hmm time to start searching for parts
amarc78 said:
It might be possible as long as the board on your device has the connections for the sensor or a place to add the connections. You'd need the firmware with the finger print scanner files for it to actually work though I would imagine.
Click to expand...
Click to collapse
Any idea what the finger print scanner apps are? I'd like to remove the vibrate permission from it, but I can't guess what it is!
docwebhead said:
Any idea what the finger print scanner apps are? I'd like to remove the vibrate permission from it, but I can't guess what it is!
Click to expand...
Click to collapse
There are no apps specifically for the finger print scanner. It's all built into the whole system. What you want to do is probably not possible unless maybe if you decompile, modify, and recompile the framework and whatever system apps have something to do with it.
Sent from my Moto E (4) using XDA Labs
amarc78 said:
There are no apps specifically for the finger print scanner. It's all built into the whole system. What you want to do is probably not possible unless maybe if you decompile, modify, and recompile the framework and whatever system apps have something to do with it.
Click to expand...
Click to collapse
Blocking the vibration permission from the Android system with adb in cmd wouldn't work?
andMego said:
Blocking the vibration permission from the Android system with adb in cmd wouldn't work?
Click to expand...
Click to collapse
Maybe. That might block all vibrations for everything else though, unless you can block it for the fp scanner. don't have a fp scanner to try it or I would.
Related
The Fingerprint Scanner SDK (originally posted at http://forum.xda-developers.com/showthread.php?t=1202577) for Android has been released by Authentec. Currently there is only one device(Motorola Atrix) with a fingerprint scanner, but if you release your application with support for the fingerprint scanner (once you get the hang of it it is really not hard to use at all) then users of phones with fingerprint scanners will most likely be happier with your application.
Google has stated that Google Wallet will use fingerprints to unlock the payment system, so clearly more capable devices are on the way (source: http://www.qrcodepress.com/google-unveils-safety-measure-for-their-upcoming-mobile-wallet/853399/). Including fingerprint scanner capability in your application will also future-proof it as AuthenTec will have the same framework in place in other phones that will use their fingerprint scanner (Authentec is a leader in biometric security systems for lots of devices).
MotoDEV Article Guide:
http://developer.motorola.com/docstools/library/writing-fingerprint-enabled-apps
Read and Download the (simple) SDK at their site:
http://developers.authentec.com/
Example of SDK Usage (pulled from the SDK)At the time of this writing, it is my understanding that before you release the application you need to have them review it to meet their security specifications... They don't want you using this fingerprint scanner library and making their work look bad. It's a fair deal to me. I'm not sure if this is how they want it though - maybe that is just for Advanced SDK or maybe I'm just wrong (taken from their site) It appears right now that there is a mismatch between the developers and the makers of the authentec site... apparently there is no requirement for using the fingerprint scanner, so develop away!
I have an Atrix and the fingerprint scanner is amazing, once you use it you will never go back to patterns or pins. As such this guide was written by a user of the Atrix - future devices might not use the exact methodology but it should be nearly identical.
I have the Advanced SDK but I have not used any of the advanced functions yet. After using the code (And getting it to finally work) I have found some things that are not documented or are documented incorrectly in the SDK docs and I have come here to post items that will save you great time. If you find others I hope to hear about them so I can add it to the list - I'll even credit you (maybe with a post number so you can score some thanks points!)
The swipe fingerprint screen won't show up - but I'm getting a result (mine was always 14)
AM2 (Authentec fingerprint framework - there are a lot of unsubscribed terms in the documentation so just go with me here) requires Internet Permission (perhaps to verify the key for the advanced SDK, it might not be done locally - without a key advanced SDK functions will not load). If you don't, all uses of the tsm.jar will not work. Not listed at all in documentation
AM2ClientLibraryLoaded() doesn't work with the code they provide!?
You must Instantiate Authentec.AM2ClientLibraryLoaded() - SDK Docs shows as static but it is not used in the example program they give.
It goes into verification but does not show anything and locks up the fingerprint sensor.
Do not change the 'screen' in the examples of sScreen... I thought that was the title of the window that would appear, but apparently those strings are built into it... it would work better as static fields passed as integers. For values look at the next answer.
What can I use for sScreen (viaGfxScreen(string))?
The documentation says nothing of this but these are different types of verification screens. There is fingerprint scanning only and then there is the unlock style one where you also get the PIN. I'm guessing a modifed version of this is how the lock screen works.
"lap-verify" is fingerprint and PIN
"get-app-secret" is fingerprint only - hit and miss right now... will update when I get it perfected
Why does it lock up?
Only 1 app at a time can access the fingerprint scanner. Motoblur seems to access it occasionally and I think that's why it died on the Atrix's Froyo 1.8.3. It seems mostly fixed but as you develop you will most likely lock it up as you debug. Having a wrong sScreen variable will kill your FP scanner. If it locks in your app you will lose the ability to unlock the device with the FP scanner.
Use DDMS to kill com.authentec.TrueSuiteMobile and the lock will work again. This might work on 1.8.3 but I'm not sure it works that way. If the application exits with the home button, it seems to also lock it up. I'm looking into a way to avoid this..
I can't register my application, it's failing with code 6 - (System Error)
I encountered this one myself when using my Api key for com.mgamerzproductions.gibbertalk - I changed it to com.mgamerzproductions.gibbertalk.testing and it no longer worked. They did tell me this in the email that it is only for one package - so make sure you choose wisely, or bribe the people giving out the API keys to give you another one. I wish it was more specific (API_KEY_NOT_AUTHENTIC or something)
I'm still having problems. What can I do?
You can use these tags for debugging in logcat:
AMJNI (AuthenTec Mobile - permissions - server)
TrueMobileSuite (some gfx log info - swipe fingerprint screen)
AndroidRuntime (will tell you crash related things, as debugging for errors will produce too much to read at once)
Any other things would be greatly appreciated for all of use Developers so speak up if you have something I don't have listed and I'll add it.
If you want to use the encrypted storage provided by the framework you'll need to apply for the Advanced SDK. You have to give them a description of your app, and it has to be security related (obviously that's the whole point of the fingerprint scanner and they don't want you to abuse it).
If you like the guide, and you are on MotoDev, I wouldn't mind a kudos in the contest http://community.developer.motorola...print-Enabled-Apps-quot-article-in/td-p/17206
RESERVED
Reserved for OP at a later date
Pictures of my use right now (more later)
Spoke to OP, moved to main Android development, as this would be of more interest to the development community in general, as I'm sure other phones will be using fingerprint scanning (and this sdk) in the near future.
Originally posted in the source thread:
heilpern said:
I tried to post in the linked thread, but as I'm a new XDA poster the system wouldn't allow me to.
The INTERNET permission is required, however there aren't any connections made off of the device. The system uses sockets internally and INET sockets are used rather than UNIX sockets.
> Why does it lock up?
> Only 1 app at a time can access the fingerprint scanner.
This should not cause the system to lock up; it should cause your app to delay briefly and either continue with your request or return to you with an error. If you can duplicate some other result reliably, please share details.
> If someone also can upload and create an eclipse project it would be must easier to import and view their source code they post. I tried but eventually gave up cause of so many problems.
The eclipse projects for these examples are very simple -- with the exception of the .project you have everything you need in the example directories. Worst case is you can create a new Android project and replace its manifest, sources and resources with those provided by the examples. Then point the build path at your tsm.jar and you'll be ready to go.
Click to expand...
Click to collapse
What I meant was that if an app is asking for the fingerprint reader (not the app entirely, but actively asking for the FP reader scan), and motorola does something in the background with the FP scanner (on atrix), it can lock it up. This was heavily apparent on Atrix 1.8.3 but in the new update it seems to have been mostly fixed.
Errors: If you bring up the window with anything but lap-verify or get-app-secret, the window will lock up (and i think fingerprint reader will lock up as well - if you return to the lockscreen you'll see it never finishes initializing it) I can attempt to reproduce this error but I want to finish some development I am doing now.
heilpern said:
com.authentec.TrueSuiteMobile drives the UI, directly or indirectly depending on exactly what's going on (indirectly in the case of the lock screen, for example). If this package is killed it will restart with the next fingerprint operation however it will disrupt any currently active verification attempt (causing the requesting app to receive an error -- probably the USER_CANCELED error).
Click to expand...
Click to collapse
I never really kill it except if it locks up. Haven't tested what it returns (perhaps null)
heilpern said:
Here's something you can do to experiment if you're using StoreCredential -- swipe one of your existing fingers (the index fingers) and you'll store data to that particular finger. Swipe a different finger (multiple times as prompted) and eventually (after three swipes if all goes well) you'll be asked which finger you just enrolled (and your credential will be stored to that finger). This new finger can be used for subsequent Store Credential requests (without the automatic training session) and to release data stored with Get Secret... but only the index fingers can be used to unlock the Atrix.
Click to expand...
Click to collapse
Yeah, in the original thread I had that image posted... It's in the framework but it never was used... I'm not sure if it was there for this purpose or was just cancelled at the end because it was incredibly confusing... I don't get why you would need all those credentials. It's not like your phone will get passed around that much. You swipe new fingers just like you would if you were registering a finger, then you choose the finger... but the accuracy of the 'pick a finger' one is pretty bad.
Would love to see a test apk where we can try this out...
Nothing available right now?
My application works with the FP scanner... its not done yet though.
These are the included APK's that are the code samples they use:
Download tsm-apk-pack.zip from Host-A
Will it support HTC Desire HD? It won't right?
The fingerprint scanner is a hardware device, just like a laptop fingerprint reader. Its not touchscreen, unfortunately.
Trolling from my ATRIX 4G on probably the crappiest main US carrier
Mgamerz said:
I can't register my application, it's failing with code 6 - (System Error)
I encountered this one myself when using my Api key for com.mgamerzproductions.gibbertalk - I changed it to com.mgamerzproductions.gibbertalk.testing and it no longer worked. They did tell me this in the email that it is only for one package - so make sure you choose wisely, or bribe the people giving out the API keys to give you another one. I wish it was more specific (API_KEY_NOT_AUTHENTIC or something)
Click to expand...
Click to collapse
I agree that a more telling error code would be a better option. Error 6 is eAM_STATUS_ACCESS_ERROR but that value can be returned for other problems as well.
Note that if a generic API key is needed, TSM-0E08085A-1210171A-001A7465-632E7473 can be used if you name your package com.authentec.tsmgetsecret. You cannot post that package to the Market however if you want a means of creating a test APK with a neutral package name that package/key combination will work.
Has AuthenTec claimed that package name on the market...?
they probably should or someone might take that package...
Mgamerz said:
Has AuthenTec claimed that package name on the market...?
they probably should or someone might take that package...
Click to expand...
Click to collapse
Yes, it's already claimed in an unpublished but uploaded entry.
Hi . question: is it possible to use fingerprint senzor as wake up function? My button is very very hard to push, this function would be great....
All of the ANT+ apps - do I need them for anything other than the Samsung health apps, which are bloatware to start with.
I disabled all mine...no issues
Gotit. TNX!
ANT+ is for connecting sport related stuff like hart-rate monitors
That's what I found on-line. I want to double-check that before I freeze it with Titanium.
Finger scan needs ant .. I may be wrong. .
Sent from my SM-G900T using XDA Free mobile app
I gave up on finger scanners for any device a while back. It's just more aggro than it's worth to me.
It doesn't take up much space anyway. I just left it.
Funny how there are so many Playstore reviews with 1 star saying "OMG BLOATWARE I DUN WANT" when it is necessary for operating all features that come with the device. Added onto the fact it really takes up very little space.
Well OMG! It must be bloatware. I read it on the Internet, so it must be true. [/ROFL]
It's the same as the system services for any other technology. You need the ANT services if you are using ANT (eg. ANT+ health and fitness sensors), just like you only need the WiFi services in the system if you are using WiFi or the Phone services if you are connecting to the cellular network.
beachbum40 said:
Finger scan needs ant .. I may be wrong. .
Click to expand...
Click to collapse
Or is it that the finger scanner needs the compass so it can know which side of your finger is being scanned? So wrong.
Gotit about the services analogy.
About giving the compass the finger? [/ROFL]
Is there any way we can use finger print scanner for opening apps?
No not yet
Yea cant wait to have apps that use the android M api for authentication. It would be cool.
Does anyone know if there is a way to pass specific fingerprint events into a tasker profile? For example a variable that can be read as representing finger 1 or 2?
Any interaction between Tasker and fingerprint recognision would be more than welcome
^ I too would love to know this!
I only had a quick look at the API, but IIRC, you can't register for a specific fingerprint, only success or failure.
yes i am using this app this is perfect for me i am using on android-O .
We all know this can be fooled with a picture... From the corporate side, I'm looking for a way to disable face recognition through a script we can push out from our mobile device management infrastructure.
I don't have an S8 or S8+ to dig into. I'd like to know if someone can do a little digging on their device and let me know if this is something that's possible and what I need to do to disable the facial recognition feature.
Thanks!
jeredh said:
We all know this can be fooled with a picture... From the corporate side, I'm looking for a way to disable face recognition through a script we can push out from our mobile device management infrastructure.
I don't have an S8 or S8+ to dig into. I'd like to know if someone can do a little digging on their device and let me know if this is something that's possible and what I need to do to disable the facial recognition feature.
Thanks!
Click to expand...
Click to collapse
You could simply not use it, by going to settings under the security tab you can choose not to use Face recognition. If in doubt you can simply use the Iris Scanner, which i can guarantee that no one is going to fool that. Also the new update we've got, using a picture to unlock the phone is not as easy but then again, you could simply choose not to use it or you can choose to use Iris Scanner or disable all of them together and use your fingerprint. Face Recognition is not mandatory and is disabled by default unless you choose to enable it.
eniorodriig said:
You could simply not use it, by going to settings under the security tab you can choose not to use Face recognition. If in doubt you can simply use the Iris Scanner, which i can guarantee that no one is going to fool that. Also the new update we've got, using a picture to unlock the phone is not as easy but then again, you could simply choose not to use it or you can choose to use Iris Scanner or disable all of them together and use your fingerprint. Face Recognition is not mandatory and is disabled by default unless you choose to enable it.
Click to expand...
Click to collapse
You completely missed the point. I never said anything about me using the feature. I want to block it company wide so people who are are ignorant of the issues with face recognition cannot use it and pose a security risk.
bump
Hi @jeredh,
Your thread in "Themes, Apps, and Mods" quoted below, is not in the correct section. So, you can continue the discussion in the current thread (Q&A).
jeredh said:
I started a thread in Q&A several days ago, but I think it was in the wrong forum and should be here instead.
I'm trying to come up with a script that I can use to push out to all S8/S8+ devices in our corporate environment via MDM that will disable only the facial recognition part of smartlock. Unfortunately I do not have access to a S8/S8+ to dig into. Would anyone be willing to lend a hand on this?
Thanks in advance.
Click to expand...
Click to collapse
I had to remove the newer thread from the "Themes, Apps, and Mods" section.
Thanks for your understanding.
Regards,
Wood Man
Forum Moderator
jeredh said:
We all know this can be fooled with a picture... From the corporate side, I'm looking for a way to disable face recognition through a script we can push out from our mobile device management infrastructure.
I don't have an S8 or S8+ to dig into. I'd like to know if someone can do a little digging on their device and let me know if this is something that's possible and what I need to do to disable the facial recognition feature.
Thanks!
Click to expand...
Click to collapse
MAybe try calling Samsung and see?
http://www.samsung.com/us/business/discover/galaxy-s8-for-enterprise/
SALES & SERVICE & SUPPORT
1.866.977.9261