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
is there anyone who has managed to get that touch lock screen where u connect the points in a pattern of your choice on the leo (i think its from the droid but i might be wrong)? i'd like a tiny bit more security then the normal lock screen but something a little better than the normal pin entering kefuffle
You are probably referring to ThrottleLock, which fakes Android unlock sequence.
I tested it on my Leo, it was ugly with the default skin, awfully slow and the G-sensor was not recognized. In fact, it was better on my Kaiser...
I wish we had more alternatives than the iphoneish slide unlock. No offence to A_C but I'm tired of having every iphone owner say "oh they even copied the unlock screen". I'm tempted to write my own using the multi-touch capabilities (like "press A + B at the same time to unlock"), but I need to improve my C# first...
I'm using throttlelock, which has the pattern. It's working fine on my Leo and is quick. Much quicker than my Kaiser was. I don't mind the look of the classic throttlelock which is transparent. I'm more than happy with it.
cheers, i downloaded and installed throttlelock but i cant get it to lock with throttlelock when i press the lock button... any way of chaging the settings for it to use throttlelock instead of the current screen?
Edit: I changed my configurations and now ThrottleLock locks automatically on power-on. I've even changed the original skin to VGA so its much less ugly now.
Hi! Same issues with ThrottleLock in my phone:
It recognizes the GSensor, but its very slow to update the screen with the 3D effect.
It doesn't lock the screen automatically on poweroff-poweron. In fact, sometimes it locked the screen automatically, I don't know exactly under which circunstances that happened.
I don't know how to make it show notifications. But perhaps, that's because I didn't understand its configuration.
I thought about posting a message in ThrottleApps forum, but the forum looks kind of abandoned. :-(
That's a pity because, although it wouldn't win beauty contests, I really liked its password scheme.
I solved my problems with the automatically lock.
I've changed the background skin for a WVGA one and it looks better now. (But the G-Sensor is still very slow, so I'll disable the 3D animation.)
I'll try ThrottleLock for some time.
wvga skin for throttlelock
Hey just wonder where you found a wvga skin for throttlelock
searched through google, xda and throttlelock's website and all i could find were dead links.
its also a pity that throttlelock hasn't been updated in over a year as the idea is a good one.
movieman14 said:
Hey just wonder where you found a wvga skin for throttlelock
searched through google, xda and throttlelock's website and all i could find were dead links.
its also a pity that throttlelock hasn't been updated in over a year as the idea is a good one.
Click to expand...
Click to collapse
In fact, I customized the original skin to WVGA. Mostly, I changed the background picture, did some smal changes to the file skin.xml and doubled the icon's size.
I attached the skin. Put the directory Akira.WVGA under your skins directory (in my case, its \Program Files\ThrottleLock\Skins) and change the skin in ThrottleLock Settings. You can change the file back.png to one that suits your tastes.
Note: I'm on the verge of switching back to Slide2Unlock2. Sometimes ThrottleLock takes several seconds to unlock. I'll test if this problem occurs with S2U2 too.
thanks
thanks for the skin
will use soon as hd2 gets back from repair
With throttelock The screen locks during a call.
When a call is in progress and the phone is close to the ear, the screen shuts down to prevent accidental taps without locking the screen and when the phone moves from the ear, the screen wakes up and it's possible to use it forward.
But with throttelock, the the screen shuts down and locks itself and when the phone moves from the ear during a call, I must first unlock it.
How can I make the screen only to be shut down when a call is in progress and the phone is close to the ear and not to lock the screen?
Someone needs to develop a new home screen manager. One that instead of just moving left to right moves up and down as well. This way screens are always just one flick away instead of 2 or more depending on where you are at. It would be like a cube where the main homescreen is in the middle and the other 4 screens would each be in a direction (up, down, left, right). Moving from one of those screens in a direction (up, down, left, right) would result like moving from the home screen. So more than just a cube. A little more complex. I'll develop it if someone can help me along. Just an idea i had when looking at the linear movement of the ui.
Unfortunately I don't have any of the required skills or time to match even 1% of the ability of the Android development community but I'd definitely second this request. A very unique idea and I really like it.
BTW, a big thanks to the devel community. Without you guys fulfilling my gadget whore needs, I'd be buying a new device every week!
This is cool..maybe even an option in the notification bar to switch screens while in an app? Like the Linux desktop cube?
Sent from my Floyo Tazz using XDA App
Rather than write something from scratch, maybe you could try to contribute this as an option in ADW.Launcher?
This has already been done before on a certain rom. I remember it being ported to the vogue android. I cant remember the phone it was ported from though. Blur or something.
Gde home had exactly this feature
~ The Nameless Creator
Actually there were a few Windows CE based home mangers that had this feature. I also would love to have this. I asked a while back and got no response as to if there is anthing out there that did this.
wouldnt it be kinda hard to keep track of which screen is in which direction? like it seems orientation would feel very complex. but maybe not, i dunno
SLOflatlander said:
wouldnt it be kinda hard to keep track of which screen is in which direction? like it seems orientation would feel very complex. but maybe not, i dunno
Click to expand...
Click to collapse
I could see something like dots on the edge of the screen kinda like how launcher pro does it.
SLOflatlander said:
wouldnt it be kinda hard to keep track of which screen is in which direction? like it seems orientation would feel very complex. but maybe not, i dunno
Click to expand...
Click to collapse
Wait'll you see the home screen replacer I'm building based on a tesseract.
http://en.wikipedia.org/wiki/Tesseract
You just need to turn your head sideways to keep track of what face you're on.
Who doesn't want 24 home screens?
For a 4 or 5 way slide/cube desktop, look at Dx Top. It has not been updated for a while but is stable and can use themes built for many of the other desktop replacements.
I have been running it over many ROMs and it works on all so far. Was a little funny with the app drawer on SkyRaider, it kept rebuilding the icons for some reason, that might have been due to installing too many icon packs.
Thanks for the support on this guys and the answers. i'm going to do some research and see what can be done/ported or if needed then created. Just trying to do like most people and think outside the box. Its what makes android 1000x better than the iphone/ipod scene. They are so restricted. i mean come on. 1 button. But keeping on topic, i really appreciate no flaming on the topic.
Hey all,
One thing I've always wanted on android is the ability to slide-unlock, THEN to enter pattern/passcode/whatever.
Is there any way to do this? I found no way to do it in CM6. I'm now running MIUI and there's no way in this ROM either.
Is there some hack or software out there that will do this that I don't know of?
Have you tried downloading Widget locker from the market? That seems to be the most popular lockscreen replacement
No, there's no trial and I can't buy stuff off the market anyways. Does this allow for unlock->pass unlock?
From the screenshots it looks like it may.
ninjai117 said:
No, there's no trial and I can't buy stuff off the market anyways. Does this allow for unlock->pass unlock?
From the screenshots it looks like it may.
Click to expand...
Click to collapse
just curios why do you want to unlock your phone twice?? ocd?
Haha no, I just like having a password on my phone and the lock screen with pattern lock is fugly. I don't want to see big dots all over my screen. I was able to fix this with CM6 by making it all invisible.
I sort of want it how the iphone does it, or how my buddies android 1.6 phone does it.
ninjai117 said:
Haha no, I just like having a password on my phone and the lock screen with pattern lock is fugly. I don't want to see big dots all over my screen. I was able to fix this with CM6 by making it all invisible.
I sort of want it how the iphone does it, or how my buddies android 1.6 phone does it.
Click to expand...
Click to collapse
I actually really miss this function from my G1. Haha. I don't like the invisible buttons because it just makes the screen look absolutely empty. I would love a Unlock -> Password option.
Uhm, am I missing something or isn't that how it works by default? When I have a password or pin setup, and go to unlock my phone, I get the unlock screen. Once I've swiped to unlock, then I get the password/pin prompt. The only time it doesn't behave like that is when a pattern-unlock is being used.
sknoslo said:
Uhm, am I missing something or isn't that how it works by default? When I have a password or pin setup, and go to unlock my phone, I get the unlock screen. Once I've swiped to unlock, then I get the password/pin prompt. The only time it doesn't behave like that is when a pattern-unlock is being used.
Click to expand...
Click to collapse
I do believe he was talking about pattern-unlock
melder2011 said:
I actually really miss this function from my G1. Haha. I don't like the invisible buttons because it just makes the screen look absolutely empty. I would love a Unlock -> Password option.
Click to expand...
Click to collapse
I was actually looking for a way to add a picture frame or somrthing similar to fill the empty space with.
Originally Posted by sknoslo View Post
Uhm, am I missing something or isn't that how it works by default? When I have a password or pin setup, and go to unlock my phone, I get the unlock screen. Once I've swiped to unlock, then I get the password/pin prompt. The only time it doesn't behave like that is when a pattern-unlock is being used.
I do believe he was talking about pattern-unlock
Click to expand...
Click to collapse
Yep, I was. Makes no sense why you can't have this for pattern unlock as well!
I can't understand why anyone would want that!
It's one of the main reasons I don't like HTC sense roms - you can't get rid of the stupid unlock slider even when you have the pattern unlock enabled.
Why would I want to unlock it twice?!?
I want it because I frequently look at my phone for the time or for other various locked-screen uses, and it's aesthetically displeasing to look at it with the big bubbles all over the screen. Not to mention you lose the ability to slide to vibrate and that sorta stuff you get normally by default.
If you can't get WidgetLocker, try Simply Lockscreen. WidgetLocker looks way better, same with GoTo (but both are paid).