Summary:
A method of executing the device lock/unlock features of Windows Mobile by using the gestures available in FTouchFlo v1.4.1.
Here's a sample video of it in action courtesy of kidnamedAlbert: http://www.youtube.com/watch?v=wjPxHroy9VU
Current Status:
I've got the basics working on my device right now, and it works quite well. Beta version is now available, where I offer a choice of install methods. Since many users already have FTouchFlo and some version of the "true" HTC Cube application with my TFloCubeCtrl, then all that is needed for this is an update to version 1.2.0 of TFloControl, and an adjustment to the FTouchFlo config file. I also have a stand-alone cab installer for just FTouchFlo and the "slide 2 lock/unlock" capability. Note: there's no cube involved in this one!
Where is it?!
*NEW* CAB installer for TFloControl + FTouchFlo + config for "Slide to Lock/Unlock" with a left-right gesture now available here: http://rapidshare.com/files/128559842/TFloControl_v1.2.0___FTouchFlo_v1.4.1.cab
Be sure to check the install/usage notes in Post #4
If you've already got FTouchFlo v1.4.1 installed, and an HTC Cube using TFloCubeCtrl, then you can just download the new TFloControl.exe and FTouchFlo.config files from the attachments, and follow the directions in Post #4
What's Next?
Currently, configuration of TFloCubeCtrl is through command-line params fed by FTouchFlo. I think this could be made better, and possibly there should be a configuration app ... since all of my FTouchFlo gestures just map to calling TFloCubeCtrl anymore, which nowadays does so much more than just control the HTC Cube!
I'm currently talking with efrost about the possibility of turning TFloCubeCtrl and it's functionality into a plug-in for the newer FTouchSL application.
I wonder what other sorts of features I could build into it as additional parameters. So far I have:
Lock
{no params} - execute the device lock
home - return to the Today screen and then lock
suspend - lock, and then suspend the device
Unlock
{no params} - unlock the device
<milliseconds> - amount of delay between the simulating the left softkey, and clicking the unlock button. I added this in case different devices needed different amounts of lag time based on processor speed. 50ms seems to work quite well on my Kaiser.
Donations:
If you like what I've done, then please ... feel free to donate to me. It definitely helps in keeping me motivated to add new features and answer questions. However, if you find this function useful, you should also consider a donation to efrost ... because without FTouchFlo v1.4.1, this little project would not exist.
Props:
efrost - for making FTouchFlo!
Matt Armstrong - creator of DeviceLock, where I first saw that the unlock process could be automated
wacky.banana - for pointing out the "bug" that clued me in that unlock was possible via FTouchFlo
kidnamedAlbert - for making a video of it in action
Background
While working on a project to bring full HTC Cube finger control to non-Touch devices, I developed an application to work hand-in-hand with efrost's FTouchFlo application. In addition to being able to control the HTC Cube, I also added a few system control functions that you could map to FTouchFlo gestures. One such system control function was the ability to engage the standard device lock, with additional options for returning the display to the home screen, and also for suspending the device. I soon realized that this was a slick was to lock your device, by just sliding your finger across the screen left-to-right. However, this then still left me with the rather lame way of unlocking the device, pressing the left softkey, and then clicking on a button on the screen. I became further annoyed when attempting to unlock the screen in bright sunlight, where it's next to impossible to find the button on the screen (at least for me!).
Where is this going?
One day, I had a small revelation. Someone had previously reported a "bug" with TFloCubeCtrl, whereby you could open up the cube, even when the device was locked. I subsequently added some code to ensure that all functions were disabled if it detected that the device was locked. But while it was reported as a bug ... the indication here was that TFloCubeCtrl would receive calls from FTouchFlo even when the device was locked. I suddenly realized that this meant that I could also add functionality to TFloCubeCtrl to unlock the device, by automating the unlock procedure.
So, does it work?
In fact ... it works just the way I had hoped. Now, with the device on, but locked with the standard WinMo device lock functionality, I can swipe my finger left-to-right, and the device becomes unlocked. You don't even see the unlock screen (on my Kaiser anyway), as it's dismissed so quickly due to the automated unlock.
And why should I care?
Well, I like it because it works well for me, and solves some of the annoyances I've had in the past. Specifically, I like the HTC Home screen ... as I'm used to it's layout, and it has everything there I need. So I like to be able to lock the device with a quick action, and have it revert to the home screen upon locking. And thanks to FTouchFlo, a left-right swipe anywhere on the screen will work (no trying to hit a specific icon). Then, to unlock, just the same swipe again is all it takes. It's a simple action, and can be done anywhere on the screen as long as it's a complete swipe across the screen ... so you don't even need to look at the screen to unlock the device. And best of all, it all works *with* the standard device lock functionality ... so even if you lock with a different method (device lock on today screen), you can still "slide to unlock". Incoming calls work the same as before ... and PIN code input should also still function normally (initial tests have shown this to be true!)
Here are some thoughts I've come up with on possible features:
Specify an X,Y to simulate a mouse click after the Today screen is shown. (In order to ensure a particular tab is also displayed)
Specify a particular application to be displayed before locking, instead of the Today screen
Vibrate when the device is unlocked (DeviceLock offered this when "easy unlock" was enabled)
Specify a particular application to be displayed after unlocking
Installation / Usage Notes
General Usage Warnings -
This app requires FTouchFlo. As such, installing this will subject your device to known FTouchFlo "issues"
Once FTouchFlo is running, it cannot be stopped without a soft reset
While FTouchFlo is running, the Transcriber SIP and Screen Alignment utility cannot be used
Some programs that are "finger friendly" themselves do not work well with FTouchFlo, and should be added to the Exclusions list in FTouchFlo.config. Some common known apps are already in the list.
After a soft reset, you must manually start FTouchFlo before you can "Slide to Lock/Unlock". Alternatively, you can create a shortcut to FTouchFlo in your StartUp folder.
CAB Install Method -
Install the CAB file on your Windows Mobile device
Be sure to install to the Device (not a storage card)
Run FTouchFlo, found under Start->Programs
Perform a left-right slide gesture to lock the device
Perform the same left-right slide gesture again to unlock the device
Enjoy
File Install Method (Advanced Users Only) -
Use this method if you already have FTouchFlo installed, and/or if you have an HTC Cube install already on your device using TFloCubeCtrl
Copy TFloControl.exe into a \Program Files\TFloControl folder
Update your FTouchFlo.config file to reflect something similar to my sample
TFloControl is the new name for the app, replacing the old TFloCubeCtrl (it does more than control the cube!)
Morning Kona. I see you have decided to go public on this, which is great!
A couple of points from me:
One of the things you are going to have to watch out for , as you develop this tool, is getting the tool to work in a consistent and predictable manner with the inbuilt WM6 pin lock facility.
Because I am security conscious, I have pin lock initialise itself half an hour after locking the device either with device lock or Slide-To-Unlock (S2U2). When using S2U2 I have found that if a call comes in after pin lock is engaged, trying to answer the call can cause unpredictable results ranging from the call being successfully answered, to S2U2 to being presented with the pin lock keyboard to unlock the device before the call can be taken, to the call being dropped altogether.
This behaviour became such a pain that I dropped S2U2 altogether in order to get a consistent method of answering calls when the device is locked in this way, ie with device lock and pin lock in operation. I note this is an area you have not tested yet, hence me advising caution here.
Another point from me: I am assuming that your lock will not work unless a version of Ftouchflo is installed? If yes does that mean that people like me who have given up on Ftouchflo and the Cube will not be able to use your tool?
Final point; early days yet but have you thought of integrating your tool with the organic lock invented by someone on here?
Hope you find these points helpful. More than happy to undertake some testing for you if you let me know what is required, etc.
Cheers
WB
will this be a lot like the unlocking mechanism from wm 7 in which you have to slide a certain way so the device unlocks. A bit confused as far as function though. I am glad you are starting a new project...
I can not say how much i'm interested in such software, even though i dont pin lock my device, but i really like to lock it cause it many times make a call or opens and drains the battery without any need..
any way .. i'm waiting .. and i believe it's gonna be great
cheers
WB,
Thanks for the input. So far ... here's what I can tell you:
wacky.banana said:
One of the things you are going to have to watch out for , as you develop this tool, is getting the tool to work in a consistent and predictable manner with the inbuilt WM6 pin lock facility.
Because I am security conscious, I have pin lock initialise itself half an hour after locking the device either with device lock or Slide-To-Unlock (S2U2). When using S2U2 I have found that if a call comes in after pin lock is engaged, trying to answer the call can cause unpredictable results ranging from the call being successfully answered, to S2U2 to being presented with the pin lock keyboard to unlock the device before the call can be taken, to the call being dropped altogether.
This behavior became such a pain that I dropped S2U2 altogether in order to get a consistent method of answering calls when the device is locked in this way, ie with device lock and pin lock in operation. I note this is an area you have not tested yet, hence me advising caution here.
Click to expand...
Click to collapse
Since what I've done here is devise a way to use gestures as a way to interact with the standard built-in Windows Mobile locking mechanism, we should be OK here. My initial tests are indicating that everything functions predictably when PIN locking is enabled. My unlock gesture works when the PIN is not yet enabled. And once the PIN screen appears, the unlock gesture basically doesn't do much ... and you have to enter the PIN to access the phone. Incoming calls are unaffected, as the standard WinMo "Incoming Call" screen appears, and a SoftKey press will still answer without requiring an unlock. This is where people's desire for functionality is probably going to differ.
wacky.banana said:
Another point from me: I am assuming that your lock will not work unless a version of Ftouchflo is installed? If yes does that mean that people like me who have given up on Ftouchflo and the Cube will not be able to use your tool?
Click to expand...
Click to collapse
Yes ... and no. FTouchFlo is currently required, as this project is intentionally a solution to work with FTouchFlo. However, the cube is not a requirement ... it doesn't even have to be installed.
wacky.banana said:
Final point; early days yet but have you thought of integrating your tool with the organic lock invented by someone on here?
Click to expand...
Click to collapse
I have downloaded Organic Lock, and will test it out. My initial thoughts ... are that it should integrate quite well with what I've done here, since it's designed to work with the built-in WinMo device locking. I'll post my results when I get to test it out.
domineus said:
will this be a lot like the unlocking mechanism from wm 7 in which you have to slide a certain way so the device unlocks. A bit confused as far as function though. I am glad you are starting a new project...
Click to expand...
Click to collapse
Perhaps ... I honestly haven't seen what WM7 is offering. In a nutshell, what I've done here will allow you to use any of FTouchFlo's gestures to lock/unlock your device using the built-in WM6 device lock. Current FTouchFlo gestures are up-down, down-up, left-right, and right-left. You basically sweep your finger across the entire length of the screen in one continuous motion. It takes a bit of getting used to, but I get it to recognize my gestures about 95% of the time these days.
solomhamada said:
I can not say how much i'm interested in such software, even though i dont pin lock my device, but i really like to lock it cause it many times make a call or opens and drains the battery without any need..
any way .. i'm waiting .. and i believe it's gonna be great
cheers
Click to expand...
Click to collapse
I currently don't really use the PIN lock feature myself ... but your scenario of the phone accidentally waking up and doing things unintentionally is a big reason I started using the device lock to lock my phone. But when I got annoyed with the unlock procedure, I wrote the "slide to unlock" part, which is really useful (to me). This is really more of a convenience feature that a real security measure. But it makes the device lock/unlock very easy to use. I just put it on my wife's phone, because her phone kept calling people while it was in her purse!
Slide to Answer
I just had a thought ... and tested it out. You can actually "Slide to Answer" as well, when a phone call comes in.
As is true with unlock, the softkey method still works ... however, if the device is currently locked, and a phone call comes in ... if you perform the unlock gesture, TFloCubeCtrl will try to initiate the unlock by pressing the left softkey, which in turn answers the call! It's really a side-effect in this case ... but it works! Interesting ... but it would probably be more useful if I could disable the on-screen buttons, and require either a hardware keypress, or the slide gesture.
Kona_Mtbkr said:
..... It takes a bit of getting used to, but I get it to recognize my gestures about 95% of the time these days.
Click to expand...
Click to collapse
Hey Kona,
Thanks for the comprehensive response to my points. The tool looks more promising every time I hear from you.
To the point about 95% accuracy this isn't too bad and, from my experience, probably on a par with S2U2. When I was playing with TouchFlo in the early days I found you could increase the consistency of the gestures by changing the sensitivity response or whatever it was called.
When are you expecting to have a beta version of the tool out for testing then?
Cheers
WB
wacky.banana said:
Hey Kona,
Thanks for the comprehensive response to my points. The tool looks more promising every time I hear from you.
To the point about 95% accuracy this isn't too bad and, from my experience, probably on a par with S2U2. When I was playing with TouchFlo in the early days I found you could increase the consistency of the gestures by changing the sensitivity response or whatever it was called.
When are you expecting to have a beta version of the tool out for testing then?
Cheers
WB
Click to expand...
Click to collapse
Yes ... changing the sensitivity settings was key for really making FTouchFlo useful. It's a balancing act between the pressure sensitivity, and the gesture delay ... which controls how long FTouchFlo waits before deciding that you're not actually doing a gesture, so it forwards the input on to the OS. It makes it a bit trickier to try to use scrollbars or to do other dragging operations (like selecting multiple items) when FTouchFlo is in use. Not sure if FTouchSL has improved on any of these items.
As for release ... we'll see how the weekend goes. It'll be easier for me to post the new app, and a sample config for those who already have FTouchFlo and an HTC Cube install with TFloCubeCtrl. But I know that isn't going to cut it ... so I'll put a "fresh install" cab together as well.
Kona,
Good idea putting an all-in-1 cab together for an easy install otherwise all you will get is a thousand questions on how to install the app and what other linked apps are required. Probably a major distraction if what you really want to know is how the user experience is progresing.
Re the sensitivity compromise, have you had a chat with Efrost as to where his latest version of Ftouchflo is now at, from a technical perspective?
This thread is now on my auto notify list, ready for your next move.
All the best.
WB
im completely interested but does this have a transparent background on the home screen like the original windows unlock screen?
if so, this if EXACTLY what im looking for.
a lock on wakeup feature would be great too.
thanks,
wacky.banana said:
Kona,
Re the sensitivity compromise, have you had a chat with Efrost as to where his latest version of Ftouchflo is now at, from a technical perspective?
Click to expand...
Click to collapse
Well, I have contacted him through PM here ... and asked about the plugin architecture for FTouchSL, to see if he'd let me rebuild my TFloCtrl app as a plugin. He seemed to be receptive to the idea ... but I haven't heard much from him since. I'm pretty sure the free version of FTouchFlo isn't going to progress past v1.4.1 ... as all efforts are now on FTouchSL. It's only like $15, so I'll probably buy a copy at some point. efrost deserves our support! Of course, I was hoping he'd give me a license for developing my plugins against, and then I could buy a copy for my wife!
I need to get a bit more insight into his plugin architecture too, however. I'm not completely sure that everything that I've done so far with TFloCtrl will work in his plugin architecture. We'll have to see.
sounds lije it will be awesome...when developed of course. i am really into being able to lock my device easily and be something i can unlock without much thought or having to look at the keyboard whilst i enter an alpha-numeric code. kinda biometrics like without the fingerprint scanner. thanks for the info and i am waiting for more news.
kidnamedAlbert said:
im completely interested but does this have a transparent background on the home screen like the original windows unlock screen?
Click to expand...
Click to collapse
Yes, in fact, TFloCtrl has no background ... or window at all. It's more of a windowless process, that sets the display to the Today screen, locks the device, and exits. You're left at the Today screen with a locked device. Hmm, that gives me an idea for a feature, bridging between another app I'm working on. An option to also simulate a click on the Today screen, to ensure a particular tab is selected upon locking.
kidnamedAlbert said:
if so, this if EXACTLY what im looking for.
a lock on wakeup feature would be great too.
thanks,
Click to expand...
Click to collapse
Well, to put in a lock on wakeup feature would require a whole separate application. At that point, I'd almost be rebuilding armstrong's DeviceLock. You should take a look at this, as I was running it for a while for just that feature. It should work just fine with my app, because he is also using the normal built-in lock functionality. He also had an "easy unlock" feature that only required the softkey press ... but it was too "easy" for me. The swipe gesture is much less likely to occur accidentally, but still can be completed without even looking at the screen! That's the biggest benefit in my mind.
Daremo_23 said:
sounds lije it will be awesome...when developed of course. i am really into being able to lock my device easily and be something i can unlock without much thought or having to look at the keyboard whilst i enter an alpha-numeric code. kinda biometrics like without the fingerprint scanner. thanks for the info and i am waiting for more news.
Click to expand...
Click to collapse
"biometrics without the scanning" ... that's a pretty good way to describe it
I think it nice, because it offers the protection from accidental button/screen presses of the device lock, but with easier unlocking ... as you said, not having to look at the screen. But in addition, I'm also hoping it'll pair well with Organic Lock, to offer the additional security that people like WB are looking for.
And as far as "developed" goes ... it's already working on my device! I'm just thinking about what features to include for a Beta 1 release ... and also I need to invest the time to put together the installation ... or else the thread will fill with "how to install?" postings. I learned my lesson last time with the TFloCubeCtrl thread.
Just an idea, stolen from the Android platform.
You could make the unlock gesture user-customizable. Maybe there could be an interface in the settings for users to "draw" their unlock gesture and practice on it. Then, if someone wants security without a password, he can use a complex gesture.
edit: That was a horrible explanation, haha, you'll get the point from this video:
http://www.youtube.com/watch?v=arXolJrLVEg
I accidentally stumbled upon this today, wasn't sure how I did it, kept tapping and swiping till it happened again. In addition to this, I've also found that swiping up from on or below the nav bar hides QS and/or notifications with just one swipe. However, I can't seem to reproduce this 100% of the time.
Edit: 2 short rapid fire tap-swipes(down) on the status bar will produce the same outcome as "double-tap + swipe-down". Thanks to nednednerb
cptkian said:
I accidentally stumbled upon this today, wasn't sure how I did it, kept tapping and swiping till it happened again. In addition to this, I've also found that swiping up from on or below the nav bar hides QS and/or notifications with just one swipe. However, I can't seem to reproduce this 100% of the time.
Click to expand...
Click to collapse
The double tap isn't actually doing anything. The first tap opens the 6 toggles, the second tap and swipe opens QS as they normally would. You can just swipe down with 2 fingers to open the QS directly.
airmaxx23 said:
The double tap isn't actually doing anything. The first tap opens the 6 toggles, the second tap and swipe opens QS as they normally would. You can just swipe down with 2 fingers to open the QS directly.
Click to expand...
Click to collapse
Not on my phone. a single tap drops the toggles and they instantly fold right back up (they wont stay down). but a double tap drops the toggles and they stay down, then with an additional swipe down QS expands further. and finally with the double-tap+swipe down (or single tap+single tap&swipe down i get the QS right off the bat. i've tried several different ways to make this work and this has always been the final outcome...for me at least.
fyi im running stock rom (x-ota)
franco
root
twrp
and substratum (not sure this would have any affect or not)
cptkian said:
Not on my phone. a single tap drops the toggles and they instantly fold right back up (they wont stay down). but a double tap drops the toggles and they stay down, then with an additional swipe down QS expands further. and finally with the double-tap+swipe down (or single tap+single tap&swipe down i get the QS right off the bat. i've tried several different ways to make this work and this has always been the final outcome...for me at least.
fyi im running stock rom (x-ota)
franco
root
twrp
and substratum (not sure this would have any affect or not)
Click to expand...
Click to collapse
The first tap slightly open the QS (it's registering as a partial swipe) and the second tap grabs them, then you're pulling them down.
airmaxx23 said:
The first tap slightly open the QS (it's registering as a partial swipe) and the second tap grabs them, then you're pulling them down.
Click to expand...
Click to collapse
I feel we are starting to split hairs here, and maybe we are because perhaps it acts differently with different folks. But with my phone (pixel quite black 128 w/ all the goods mentioned above (forgot to mention viper 2.5.0.5 which i cant imagine would have any affect, but who knows, it is a mod afterall)).
So for me it goes as follows -
one-tap = toggles peek
double-tap = toggles stay down and notifications roll down with it
and then if i do an additional swipe down i get QS, obviously
but as mentioned in OP
one-tap, instantly followed by swipe-down (or double-tap+swipe down) i get QS instantly that way.
I would like to add that i say double-tap+swipe-down because i've seen it worded that way over the years i.e. Nova, Root Essentials, etc.
I would ALSO like to add that the entire reason for this post was because over the past 2-3 years (around the end of KitKat, maybe) I've seen the question asked a handful of times how can QS be accessed with one swipe and one finger (or thumb) while being on a stock rom. and yesterday when i did it by accident, it was like discovering a really tiny piece of gold that you weren't even looking for. I smirked when it happened, smirked again when i reproduced it, then came here and shared the wealth.
Seems like allot of extra steps
Smallsmx3 said:
Seems like allot of extra steps
Click to expand...
Click to collapse
That's just language tricking the thinker.
The doer.... Flicks the QS open so fast you need a red pill or slow motion camera to catch it.
Steps? I'm there.
Sent from my sailfish using XDA Labs
Two down swipes is how you're supposed to open QS, you can do it fast or slow. I'm sorry but this is not a hidden feature. The tap is irrelevant since you have to touch the screen to do the swipe.
airmaxx23 said:
Two down swipes is how you're supposed to open QS, you can do it fast or slow. I'm sorry but this is not a hidden feature. The tap is irrelevant since you have to touch the screen to do the swipe.
Click to expand...
Click to collapse
You should see how my 54 year old friend uses his brand new cell phone, which is also his first computer. His first email addy... I don't think he even aware of notifications as a concept though he is stumbling haphazardly. Wow! Every tap is like a huge sliding long press.
The OP did in first line state "stumbled upon".
LOTS of people value from times and brief reports like this because they learn about device. Cos no one told them "this is how you're supposed go do it, and also this is how many ways you can do it!"
I found this useful. How people understand with language is never irrelevant.
Sent from my sailfish using XDA Labs
airmaxx23 said:
Two down swipes is how you're supposed to open QS, you can do it fast or slow. I'm sorry but this is not a hidden feature. The tap is irrelevant since you have to touch the screen to do the swipe.
Click to expand...
Click to collapse
nednednerb said:
You should see how my 54 year old friend uses his brand new cell phone, which is also his first computer. His first email addy... I don't think he even aware of notifications as a concept though he is stumbling haphazardly. Wow! Every tap is like a huge sliding long press.
The OP did in first line state "stumbled upon".
LOTS of people value from times and brief reports like this because they learn about device. Cos no one told them "this is how you're supposed go do it, and also this is how many ways you can do it!"
I found this useful. How people understand with language is never irrelevant.
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
--Typed most of this up yesterday and got sidetracked, glad i waited. nednednerb is right, no point in getting butthurt over something as trivial as this. however the more i think about it, the more i'm starting to think i've been had--
What was supposed to be yesterday's reply:
You seem pretty determined to let us all know how wrong this is, and that's ok with me really, I could care less. But what you need to remember is that there are a lot of inexperienced folks here who are new to Android and/or modding, etc. And if they're here, there's a solid 50/50 chance they're learning or discovering something new for the first time That said, you should really try to focus your energy on encouraging and helping others. You never know man, that one guy/gal may have the answer you've been searching for, but they may decide not to share because their last post embarrassed them. However, if they're completely wrong and they're nearly ready to blow up their device, then by all means step in and stop them.
Also -
"Two down swipes is how you're supposed to open QS" cool new hidden feature is quicker, easier, and there's less hand movement.
"you can do it fast or slow. " hidden feature doesn't do slow, will update as soon as we gather more data
"I'm sorry but this is not a hidden feature." never claimed it was a hidden feature, but if it is, I win
"The tap is irrelevant since you have to touch the screen to do the swipe." double-tap + swipe-down has been around for some time which makes what you said kind of irrelevant
Guide for calibration FingerPrint for Red Magic 5G
After unlock bootloader .. some people may loss data calibration and some people could get it back simply just by locking the bootloader,
but if you want to get ur finger print back to work for both bootloader unlock and bootloader locked after loosing data calibration
You have to do same like instruction below:
- Dial *#9959# (dont allow data memory and clear data in system app In-Display FingerPrint)
- uncheck performance checkbox , check only calibration checkbox
- 4 step for calibration
All steps shall be in dark place
1. Press START and dont press anything it will pass
2.Press NEXT and by lattice glove press on circle it should pass
3.Press NEXT and put some anything black non reflectuvec( the display became black for calibration of the black) and it should pass
The fourth step the hardest u may fail so many times
4.Press NEXT and by thumb finger almost in vertical position press on circle(keep the thumb well pressed the initial part of the finger and slightly raised on the knuckle must be vertical in the straight direction not horizontally or slightly)
Note fourth step u may fail and repeat from begining u may reach 20 trials or more dont get bored u will success
If you are lucky see success alert in green color
In system app in setting In-Display-Fingerprint allow access data memory and reboot device .
Enjoy again your Finger Print!
P.S. = doing this procedure in a place in total darkness, there must be only the light of the display
In 4 step the finger must cover the darker part of the circle (for this I say to raise it slightly) and it must be well pressed but not too strong.
For test I used before unbricktool NO EU after I did ota update to 3.13 ,note in "in display finger print" system app you must have 3.91MB without cache and user data only for app this is very important also delete cache and data.
This procedure isn't professional but effective!
Realy appreciate the way you explained the process thanks bro it worked for me for bootloader unlocked ??
Step 4 is making me want to throw my phone at the wall lok
I notice you have actual values for each of your tests.... Mine always come back 0s
i'm having the exact same issue on the oneplus 7tpro 5g mclaren. same deal, calibration data gets shot when you unlock bootloader. ive been working on LOS bringup and have everything working but fod. I tried the calibration tests but it fails at black_rubber_sleve test. our app looks different then yours. How did you figure out the procedure? could we maybe get together and you could help me?
viper98 said:
I notice you have actual values for each of your tests.... Mine always come back 0s
Click to expand...
Click to collapse
This error may depend on the brightness of the place where you are doing the calibration and above all on the position of your thumb and the pressure you apply on the rim.
albinoman887 said:
i'm having the exact same issue on the oneplus 7tpro 5g mclaren. same deal, calibration data gets shot when you unlock bootloader. ive been working on LOS bringup and have everything working but fod. I tried the calibration tests but it fails at black_rubber_sleve test. our app looks different then yours. How did you figure out the procedure? could we maybe get together and you could help me?
Click to expand...
Click to collapse
This procedure is for Nubia Red Magic 5g ,dont know that for your device because dont should test it.
Can you show us the right way and make a video
Anaswish said:
Can you show us the right way and make a video
Click to expand...
Click to collapse
no but i already calibrated my finger print if you follow well all step and notes you will recovery FP. Many people restored with success.
Does anyone have any better tips on how to do step 4?
I've tried north of 50 times and can't proceed
A video... Dont Work for me. Error zoom ratio or get scal ratio. Ty
@s4lv0.88 Can you do me a favour?
Can you check your Drawable setting's Smallest Width for me, and also check the fingerprint scanner placement?
Smallest Width: In Developer options, scroll down to the Drawing category, and you'll find Smallest Width
For Fingerprint scanner position, if you run "adb shell am start -n com.goodix.fingerprint.setting/com.goodix.fingerprint.setting.MainActivity", you can go into "Locate Sensor"
This will really help! Thank you!
EDIT: I've just reached out to the CEO of Goodix, the sensor manufacturer to see if it's possible to get access to at least the specs of the actual calibration weights, or possibly the option to purchase them directly.
gamebenchjake said:
@s4lv0.88 Can you do me a favour?
Can you check your Drawable setting's Smallest Width for me, and also check the fingerprint scanner placement?
Smallest Width: In Developer options, scroll down to the Drawing category, and you'll find Smallest Width
For Fingerprint scanner position, if you run "adb shell am start -n com.goodix.fingerprint.setting/com.goodix.fingerprint.setting.MainActivity", you can go into "Locate Sensor"
This will really help! Thank you!
EDIT: I've just reached out to the CEO of Goodix, the sensor manufacturer to see if it's possible to get access to at least the specs of the actual calibration weights, or possibly the option to purchase them directly.
Click to expand...
Click to collapse
This is:
s4lv0.88 said:
This is:
Click to expand...
Click to collapse
Thank you so much - do you know what your DPI setting is at? The combination of the two allows for everyone to make sure that the fingerprint reader (software) is in the same position as the physical one
gamebenchjake said:
Thank you so much - do you know what your DPI setting is at? The combination of the two allows for everyone to make sure that the fingerprint reader (software) is in the same position as the physical one
Click to expand...
Click to collapse
360 dp
Tried too many times with no luck, step 4 always fails.
If anyone succeeds with this, tips will be appreciated.
I am having the same problem. I went all the way to deleting the Efs file of the phone. I could not find a solution in neither Chinese rum nor global rum. I wrote to Supporta. I saw that they didn't know anything. The thing I'm most sure about this phone is the worst phone in the world when it comes to software. I will never use zte or nubia again and would not recommend anyone to buy it.
Someone who has success in calibration, please send me the in-Display Fingerprint.apk app. I'll just try.
Successfully ! I did it !!! I passed more than 2000 attempts, but without success. I asked my wife to do it, and she did it on the second try ? I knew something was wrong with my finger
3Danger said:
Successfully ! I did it !!! I passed more than 2000 attempts, but without success. I asked my wife to do it, and she did it on the second try ? I knew something was wrong with my finger
Click to expand...
Click to collapse
Bro can u explain what happened exactly! Like is there's any trick ?