Ask / Submit
44

[Idea] Lockscreen Code Input Method

asked 2014-10-18 12:58:28 +0300

r0kk3rz gravatar image

updated 2014-10-20 12:50:50 +0300

rainisto gravatar image

I've been thinking of a new way to input the lock screen code on the Jolla. Android has had pattern unlock for a long time and it has been pretty popular so I was thinking something along those lines. The idea I have was inspired by the circle based input for the alarm clock menu.

image description

The code is input via 4 circles, each of the circles starts at the top (12 O Clock) and can be swiped left or right to create the desired shape.

Input would be to start at the inner layer, and draw the innermost circle which then locks into place once you lift your finger, and you then proceed to the next layer until the pattern is complete.

If each circle has 7 possible positions left or right, that gives 14 possible positions for each circle for around 40,000 possible combinations. This method of code input isn't as secure as a 5-6 digit numerical code, but I thought I would share it anyway as someone else might be able to improve it from a security/complexity perspective.

EDIT: changed the input description, will come up with some more pictures to describe it better

edit retag flag offensive close delete

Comments

1

I think this system would be quite unintuitive because of the need of lifting your finger between the circles, accompanied with the required precision to hit the right position in the circle. I mean, my experiences from the clock application is that it can be quite difficult to hit the right digit if I'm trying to be fast, and if there'd be four of those circles, the inner circles would have to be really small, so using them would be even more difficult. And though you have to lift your finger with the numerical code too, it doesn't involve as much need of accuracy as the buttons are much bigger. I think your idea would be visually great, but I feel it just isn't fast and intuitive enough.

Grunt ( 2014-10-18 15:07:36 +0300 )edit

@Grunt that was one of the reason why I suggested 7 possible positions rather than 12 like the clock (or 60 for the minutes), so it would be easier/quicker to get right, in practice that number might have to be tweaked to hit the right speed vs complexity.

One possible implementation I thought of was that you draw the first shape (inner most) then it 'locks' into place, then you draw the second shape. This does mean you have to get them all perfect in order, which could slow things down from retries, but solves the "innermost being small" problem

Also, bare in mind that this is a lock, unintuitive can actually be a feature in this case, if you dont know how to input the code (because its not your phone) how can you unlock it?

r0kk3rz ( 2014-10-18 15:31:50 +0300 )edit

I think this is quite an interesting idea! Would like to see it in use :)

Mariusmssj ( 2014-10-18 22:55:53 +0300 )edit

@r0kk3rz - The Android lock goes from one distinct point to another. The sailfish lock could be started anywhere. Buttons vs gestures.

vattuvarg ( 2014-10-18 23:04:07 +0300 )edit

Interesting idea! Plus it would be like solving a Myst puzzle, how cool would THAT be? ;)

thisisme ( 2014-10-26 17:16:04 +0300 )edit

7 Answers

Sort by » oldest newest most voted
9

answered 2014-10-18 20:26:47 +0300

virgi26 gravatar image

just another way to look at your method (sorry if idea is not new): what if it would be only one line, but to unlock you will need to move it several times (like you do it with safes). For example, move it to 5 oclock, then backwards to 11 oclock, then 6, then 9. The problem with andoide method is that, propbably, you can guess the code by finger prints, that you left while unlocking, And with this method you can not.

edit flag offensive delete publish link more

Comments

in practice its hard to unlock the phone via screen smears alone, unless the person keeps a very clean phone screen.

Your method would help shoulder surfing the code though, as its less visually obvious

r0kk3rz ( 2014-10-18 21:26:20 +0300 )edit

so it would basically be a radius+angle based unlock shape?

Yaniel ( 2015-09-10 13:24:50 +0300 )edit
4

answered 2014-10-18 22:16:34 +0300

vattuvarg gravatar image

updated 2014-10-19 19:55:12 +0300

This was a comment but I was requested to change it to an answer.

Gestures on the lock screen can move in eight directions. Would it be possible to put a finger on the screen, drag it a number of times in different directions and then release the finger to feed the code? A gesture-based OS needs a lock based on gestures too. To remember the code, think of directions to numbers in the corners.

edit flag offensive delete publish link more
2

answered 2014-10-19 03:26:39 +0300

TK gravatar image

updated 2014-10-19 03:40:24 +0300

Just another idea inspired by Sailfish OS. We have pulley menus with vibration feedback. So we could unlock the phone without watching the screen.

My idea: Have a horizontal bar, a pulley up and a pulley down menu with numbers. The order we will do the actions will be a part of the code.

eg code1: set bar to nr2 , pulley up to nr4, pulley down to nr 1, bar to nr8 confirm with swipe.

The combination could be either smaller or larger and may not use the three input methods (eg could be affected only from pulley menus)

And an option to have only vibration feedback without showing the numbers in pulley menus of course :).

What do you think?

edit flag offensive delete publish link more
1

answered 2015-09-10 17:42:12 +0300

r0kk3rz gravatar image

New Idea, a mixture of common Android-Pattern-Lock and @vattuvarg's suggestion but with a little more rigor put around it for easier implementation and repetition.

This article discusses some of the limitations and behavioral flaws of the grid type pattern lock and I hope to improve on some of those here.


The process to unlock is to define a connect-the-dots pattern on a circular arrangement of 10 dots, any dot can be connected to any other dot which can give a reasonable amount of complexity fairly quickly.

Blank dialog looks like this.

image description

Example lock pattern. This one is using 8 of the available nodes, and so is reasonably complex without being impossible to remember or visually being a complete mess.

image description

edit flag offensive delete publish link more
1

answered 2015-09-10 20:00:33 +0300

MoritzJT gravatar image

Generally I think pattern based unlock codes to be the least safe ones. You can much easier remember those, than you can remember numbers while looking at someone doing it. I really suggest to take a look at the blackberry scrambled numbers lock page, where you have to enter your lock code by hitting the right numbers but the screen is full of them to pick from and randomized each time. Someone trying to catch that will have a much harder time than seeing the pattern you draw to unlock your device. I can even know some of the patterns just by observing part of the wrist movement of some of my friends and I don't even want to crack their security.

edit flag offensive delete publish link more
0

answered 2014-10-19 15:51:15 +0300

dridk gravatar image

i love this idea ! its confused, but that's the goal of a lock!! ringlock!!

edit flag offensive delete publish link more
0

answered 2014-11-02 12:30:44 +0300

Andy gravatar image

Good ideas, all of them could be implemented and made choosable form the system settings. Furthermore each of the method used could be tracked to see which is used the most and which is used the least.

In the meantime it would be nice to get the screen unlocked without tapping the "unlock" button - that is, unlock the screen as soon as the correct code has been entered without the "unlock" button which is an additional tap. Also do not limit the number of digits to say minimum 5 or and/maximum 6. Make minimum 1. Oh..and do not give the visual feedback of the code entered - just like the ssh login. :)

edit flag offensive delete publish link more
Login/Signup to Answer

Question tools

Follow
4 followers

Stats

Asked: 2014-10-18 12:58:28 +0300

Seen: 1,092 times

Last updated: Sep 10 '15