Talk:Display Locker - Revision history

Airon90: /* Installing on SHR */ new section

2010-01-17T21:08:07Z

‎Installing on SHR: new section

Krid: comment on false positives

2008-04-29T04:15:47Z

comment on false positives

Haakeyar at 21:08, 13 December 2007

2007-12-13T21:08:37Z

Haakeyar at 21:07, 13 December 2007

2007-12-13T21:07:55Z

Borg at 00:50, 28 November 2007

2007-11-28T00:50:06Z

Quicksand at 20:32, 27 November 2007

2007-11-27T20:32:55Z

Quicksand at 19:17, 27 November 2007

2007-11-27T19:17:04Z

Quicksand at 19:16, 27 November 2007

2007-11-27T19:16:41Z

New page

Well borg, you beat me to something that actually works!

If you haven't seen it yet, check out my python prototype of a screen lock program:

http://wiki.openmoko.org/wiki/User:Quicksand#zedlock

I put this up a few weeks ago. It's intended to be less visual, more kinetic (i.e., easy to use without looking). I want the locked screen to have information on it eventually, but I haven't gotten around to recoding it in C (with dbus, etc.) in part because neod seemed like kind of a dead-end.

Perhaps some collaboration is in order? I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both kinetic and attractive.

← Older revision		Revision as of 21:08, 17 January 2010
Line 27:		Line 27:
	Thinking about this, it occurs to me that a straight bottom-to-top motion will result in a false positive when you drag the phone out of your pocket if it's in there upside down. The iPhone's side-to-side version is much harder to accidentally trigger.		Thinking about this, it occurs to me that a straight bottom-to-top motion will result in a false positive when you drag the phone out of your pocket if it's in there upside down. The iPhone's side-to-side version is much harder to accidentally trigger.
	--Dirk		--Dirk
		+
		+	== Installing on SHR ==
		+
		+	Hi, is it possible to install this display locker elsewhere, like on SHR? --<small style="background:#f00">'''[[User:Airon90\|<span style="color:#000">→ A</span>]][[Special:Contributions/Airon90\|<span style="color:#f00;background:#000">ir</span>]][[User talk:Airon90\|<span style="color:#000">on</span>]]'''</small> 21:08, 17 January 2010 (UTC)

← Older revision		Revision as of 04:15, 29 April 2008
Line 23:		Line 23:

	I'm sorry if this is a silly idea, or maybe it is already the way it is done. I don't have a Neo to test it on, and I don't have fast enough hardware to run OM in Qemu with an acceptable speed. Anyway, you are talking about using dbus to display missed calls, SMSes etc. I was just wondering, wouldn't it be possible to have the locker transparent most of the time? When the screen is tapped, aux button is pressed etc, it will display the unlocker for a configureable amount of time (half a second? a second?), and then go back into transparent mode. So if I wanted to check the time, SMSes, etc, I'd just tap the screen or press the aux button to make the screen light up, wait a second and then I can look right at the home screen. I think most phones do something similar, at least the ones I've had. [[User:Haakeyar\|Haakeyar]] 22:07, 13 December 2007 (CET)		I'm sorry if this is a silly idea, or maybe it is already the way it is done. I don't have a Neo to test it on, and I don't have fast enough hardware to run OM in Qemu with an acceptable speed. Anyway, you are talking about using dbus to display missed calls, SMSes etc. I was just wondering, wouldn't it be possible to have the locker transparent most of the time? When the screen is tapped, aux button is pressed etc, it will display the unlocker for a configureable amount of time (half a second? a second?), and then go back into transparent mode. So if I wanted to check the time, SMSes, etc, I'd just tap the screen or press the aux button to make the screen light up, wait a second and then I can look right at the home screen. I think most phones do something similar, at least the ones I've had. [[User:Haakeyar\|Haakeyar]] 22:07, 13 December 2007 (CET)
		+
		+
		+	Thinking about this, it occurs to me that a straight bottom-to-top motion will result in a false positive when you drag the phone out of your pocket if it's in there upside down. The iPhone's side-to-side version is much harder to accidentally trigger.
		+	--Dirk

@@ Line 22: / Line 22: @@
 Hi,
-I'm sorry if this is a silly idea, or maybe it is already the way it is done. I don't have a Neo to test it on, and I don't have fast enough hardware to run OM in Qemu with an acceptable speed. Anyway, you are talking about using dbus to display missed calls, SMSes etc. I was just wondering, wouldn't it be possible to have the locker transparent most of the time? When the screen is tapped, aux button is pressed etc, it will display the unlocker for a configureable amount of time (half a second? a second?), and then go back into transparent mode. So if I wanted to check the time, SMSes, etc, I'd just tap the screen or press the aux button to make the screen light up, wait a second and then I can look right at the home screen. I think most phones do something similar, at least the ones I've had.
+I'm sorry if this is a silly idea, or maybe it is already the way it is done. I don't have a Neo to test it on, and I don't have fast enough hardware to run OM in Qemu with an acceptable speed. Anyway, you are talking about using dbus to display missed calls, SMSes etc. I was just wondering, wouldn't it be possible to have the locker transparent most of the time? When the screen is tapped, aux button is pressed etc, it will display the unlocker for a configureable amount of time (half a second? a second?), and then go back into transparent mode. So if I wanted to check the time, SMSes, etc, I'd just tap the screen or press the aux button to make the screen light up, wait a second and then I can look right at the home screen. I think most phones do something similar, at least the ones I've had. [[User:Haakeyar|Haakeyar]] 22:07, 13 December 2007 (CET)
-−
--[[User:Haakeyar|Haakeyar]] 22:07, 13 December 2007 (CET)

← Older revision		Revision as of 21:07, 13 December 2007
Line 19:		Line 19:
	cheers,		cheers,
	Olaf		Olaf
		+
		+	Hi,
		+
		+	I'm sorry if this is a silly idea, or maybe it is already the way it is done. I don't have a Neo to test it on, and I don't have fast enough hardware to run OM in Qemu with an acceptable speed. Anyway, you are talking about using dbus to display missed calls, SMSes etc. I was just wondering, wouldn't it be possible to have the locker transparent most of the time? When the screen is tapped, aux button is pressed etc, it will display the unlocker for a configureable amount of time (half a second? a second?), and then go back into transparent mode. So if I wanted to check the time, SMSes, etc, I'd just tap the screen or press the aux button to make the screen light up, wait a second and then I can look right at the home screen. I think most phones do something similar, at least the ones I've had.
		+
		+	-[[User:Haakeyar\|Haakeyar]] 22:07, 13 December 2007 (CET)

← Older revision		Revision as of 00:50, 28 November 2007
Line 10:		Line 10:

	--Quicksand		--Quicksand
		+
		+	Hi Quicksand :)
		+
		+	I actually had'nt seen your approach before i started my project, but someone in irc pointed to it some days ago. From a functional point of view, more then a simple slide from the bottom to the top isn't needed. I tested my program in my pocket and it seems to lock the phone pretty well. To the graphics: If you grab your phone and you want to simply fast unlock it, it is already unlocked before the graphics even pop up. I personally do not see an advantage in doing some sort of more complicated motion to unlock the screen. Perhaps it could be user defined and used as a password, that would be nice, i guess. However, i just wanted to have a way to lock my phone without going in suspend, so i made this as a fast hack. As you said, neod is a dead thing. I wanted to make a replacement for it [[Phoned]], but Mickeyl pointed out that they allready startet a similar project, so i will join them. However, there will soon be a deamon which will provide a dbus interface for screensavers. I think you should work in this direction, then it will be easy to make some sort of screensaver choose tool for the user and lots of coexisting screensavers.
		+
		+	I think, if you make your program sufficient configureable it can actually be exactly used as mine, so my display locker would not be needed than and we could throw it away. If this isn't possible i will maintain it as a simple and fast unlock program. I will definitly work on more low level programs in the future, so i cant help you with your tool. Of course you can use my code or the images (they are not from me anyway) or ask me things or whatever. ;-)
		+
		+	cheers,
		+	Olaf

@@ Line 5: / Line 5: @@
 http://wiki.openmoko.org/wiki/User:Quicksand#zedlock
-I put this up a few weeks ago.  It's intended to be less visual, more kinetic (i.e., easy to use without looking).  I want the locked screen to have information on it eventually, but I haven't gotten around to recoding it in C (with dbus, etc.) in part because neod seemed like kind of a dead-end.
+I put this up a few weeks ago.  It's intended to be less visual, more tactile/kinetic (i.e., easy to use without looking).  I want the locked screen to have information on it eventually, but I haven't gotten around to recoding it in C (with dbus, etc.) in part because neod seemed like kind of a dead-end.
-Perhaps some collaboration is in order?  I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both kinetic and attractive.
+Perhaps some collaboration is in order?  I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both tactile/kinetic and attractive.
 --Quicksand

← Older revision		Revision as of 19:17, 27 November 2007
Line 8:		Line 8:

	Perhaps some collaboration is in order? I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both kinetic and attractive.		Perhaps some collaboration is in order? I'd LOVE to see a combination graphical unlocker with dbus interfaces to useful info (voicemails, SMSes, GPRS state, etc.) that is both kinetic and attractive.
		+
		+	--Quicksand