Script for theft alarm using HDAPS - Revision history

Jdthood at 16:20, 5 August 2011

2011-08-05T16:20:00Z

T33nkp4d: /* Activation */

2010-11-20T13:05:14Z

‎Activation

Matt: /* LCARS edition */ memory-alpha

2010-11-13T21:33:03Z

‎LCARS edition: memory-alpha

Matt: +LCARS edition

2010-11-13T21:30:57Z

+LCARS edition

Kiraven: /* Prerequisites */

2010-02-11T18:36:32Z

‎Prerequisites

Kiraven at 10:54, 6 August 2009

2009-08-06T10:54:40Z

Trbs at 11:11, 2 May 2009

2009-05-02T11:11:59Z

Thinker: /* A comprehensive script */ prose

2007-02-22T22:04:44Z

‎A comprehensive script: prose

Thinker: /* Activation */ BlueTooth done

2007-02-22T22:00:00Z

‎Activation: BlueTooth done

Thinker: /* A comprehensive script */ BlueTooth support

2007-02-22T21:59:30Z

‎A comprehensive script: BlueTooth support

@@ Line 17: / Line 17: @@
 The volume and alarm sound can be adjusted at the top of the script. On a ThinkPad {{T43}}, the synthetic siren at <tt>$alarm_volume=100</tt> (up from the default 70) is quite ear-splitting, and combined with <tt>$acpi_volume=15</tt> it is dangerously loud.
-The script is designed to run continuously in the background, so by default the alarm will be activated only when the KDE screen saver is locked. If you you open the laptop lid (or press the lid button) shortly before or after the beginning of movement, the alarm will be suspended (except for a brief warning) and you will get a few seconds of grace to unlock the screen saver (preferably, [[How to enable the fingerprint reader|using the integrated fingerprint reader]]!). You can disable this functionality by passing the <tt>--arm</tt> parameter, by setting <tt>$use_kde=0</tt> and <tt>$use_lid=0</tt>, or by using the simpler script below.
+The script is designed to run continuously in the background, so by default the alarm will be activated only when the KDE screen saver is locked. If you you open the laptop lid (or press the lid button) shortly before or after the beginning of movement, the alarm will be suspended (except for a brief warning) and you will get a few seconds of grace to unlock the screen saver (preferably, [[How to enable the integrated fingerprint reader|using the integrated fingerprint reader]]!). You can disable this functionality by passing the <tt>--arm</tt> parameter, by setting <tt>$use_kde=0</tt> and <tt>$use_lid=0</tt>, or by using the simpler script below.
 There is also an option to track a BlueTooth device (e.g., a mobile phone). In this case, the alarm is activated (and optionally, the KDE desktop is locked) whenever the device is turned off or too distant for a given period, and deactivated when the BlueTooth device is nearby. You need to provide the device's BD address. If both KDE screen saver and BlueTooth checking are enabled, then the alarm will be activated when *either* the screensaver is enabled or the BlueTooth device is amiss.

@@ Line 68: / Line 68: @@
 * Gnome and xscreensaver support (similarly to [http://fdd.com/software/radeon/lightwatch.pl lightwatch.pl]?)
 * Monitor X server presence  and make noise on sudden X server shutdown (i.e. catch {{key|ctrl}}{{key|alt}}{{key|backspace}} events).
-* Monitor AC power and take it into account for alarm activation -- thieves seldom carry a UPS.
+Already done !* Monitor AC power and take it into account for alarm activation -- thieves seldom carry a UPS.
 * Don't arm the alarm if movement of similar magnitude was happening also before the screensaver was auto-locked (the owner might be in a moving vehicle, etc.).
 * Disarm the alarm (or hold it off for a few seconds, as already implemented for lid open) based on voice/sound recognition using the built-in microphone.

@@ Line 50: / Line 50: @@
 == LCARS edition ==
-The simple script modified to show a LCARS red alert flash animation from Star Trek Voyager instead of a beep.
+The simple script modified to show a [http://memory-alpha.org/wiki/LCARS LCARS] red alert flash animation from Star Trek Voyager instead of a beep.
 ===Prerequisites===

← Older revision		Revision as of 21:30, 13 November 2010
Line 48:		Line 48:

	{{CodeRef\|tp-theft-basic}}		{{CodeRef\|tp-theft-basic}}
		+
		+	== LCARS edition ==
		+	The simple script modified to show a LCARS red alert flash animation from Star Trek Voyager instead of a beep.
		+
		+	===Prerequisites===
		+	* ThinkPad with [[Active Protection System]]
		+	* [[HDAPS\|hdaps]] kernel module loaded (included in kernel 2.6.14 and later)
		+	* <tt>gtk-gnash</tt> [http://www.gnashdev.org/ Gnash] a GNU SWF movie player
		+	* internet connection to get the swf from http://lcars.org.uk (you may download the file and adjust the path)
		+
		+	===The script===
		+
		+	{{CodeRef\|tp-theft-lcars}}

	==Ideas for improvement==		==Ideas for improvement==

@@ Line 42: / Line 42: @@
 * [[HDAPS|hdaps]] kernel module loaded (included in kernel 2.6.14 and later)
 * <tt>aumix</tt> mixer control utility (included in all modern Linux distributions)
-* <tt>sox</tt> (SOund eXchange) sound utility (included in all modern Linux distributions)
+* <tt>sox</tt> (SOund eXchange) sound utility (included in all modern Linux distributions, e.g. packages "sox" and "libsox-fmt-oss" in Ubuntu)
 * in newer Versions of sox (e.g. shipped with current Ubuntu), the used parameters are no longer supported. You have to replace "-t nul /dev/null" with "-n" in line 19.

@@ Line 101: / Line 101: @@
 http://r3blog.nl/index.php/thinkpad-theft
 It has almost the same features as the comprehensive script above, with a few improvements. It uses dbus to query the screensaver status and gconf for storing configuration value. To improve the delay before the alarm sounds, it has a built-in wav player, and it opens the file-descriptor of the wav at startup time (thereby removing the need to spawn an application to play the alarm; imagine someone stealing your laptop while you're doing heavy disk io). Furthermore, it has a trayicon allowing you to manipulate most settings stored in gconf aswell as showing you the current status of the alarm. The 0.2 release features activation on missing presence of a bluetooth or usb device.
 ==Conceptional thoughts==

← Older revision		Revision as of 21:59, 22 February 2007
Line 18:		Line 18:

	The script is designed to run continuously in the background, so by default the alarm will be activated only when the KDE screen saver is locked. If you you open the laptop lid (or press the lid button) shortly before or after the beginning of movement, the alarm will be suspended (except for a brief warning) and you will get a few seconds of grace to unlock the screen saver (preferably, [[How to enable the fingerprint reader\|using the integrated fingerprint reader]]!). You can disable this functionality by passing the <tt>--arm</tt> parameter, by setting <tt>$use_kde=0</tt> and <tt>$use_lid=0</tt>, or by using the simpler script below.		The script is designed to run continuously in the background, so by default the alarm will be activated only when the KDE screen saver is locked. If you you open the laptop lid (or press the lid button) shortly before or after the beginning of movement, the alarm will be suspended (except for a brief warning) and you will get a few seconds of grace to unlock the screen saver (preferably, [[How to enable the fingerprint reader\|using the integrated fingerprint reader]]!). You can disable this functionality by passing the <tt>--arm</tt> parameter, by setting <tt>$use_kde=0</tt> and <tt>$use_lid=0</tt>, or by using the simpler script below.
		+
		+	There is also an option to track a BlueTooth device (e.g., a mobile phone). In this case, the alarm is activated (and optionally, the KDE desktop is locked) whenever the device is turned off or too distant for a given time, and deactivated when the BlueTooth is nearby. You need to provide the device's BD address. If both KDE screen saver and BlueTooth checking are enabled, then the alarm will be activated when either the screensaver is enabled or the BlueTooth device is amiss.

	===Prerequisites===		===Prerequisites===