/usr/share/doc/blueproximity/manual.html is in blueproximity 1.2.5-6.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
<TITLE></TITLE>
<meta name="generator" content="Bluefish 1.0.7">
<meta name="author" content="Lars Friedrichs">
<META NAME="CREATED" CONTENT="20070811;21544300">
<META NAME="CHANGEDBY" CONTENT="Lars Friedrichs">
<META NAME="CHANGED" CONTENT="20070911;23213900">
<STYLE TYPE="text/css">
<!--
@page { size: 21cm 29.7cm; margin: 2cm }
P { margin-bottom: 0.21cm }
H1 { margin-bottom: 0.21cm }
H1.western { font-family: "Helvetica"; font-size: 16pt }
H1.cjk { font-family: "DejaVu Sans"; font-size: 16pt }
H1.ctl { font-family: "DejaVu Sans"; font-size: 16pt }
H2 { margin-bottom: 0.21cm }
H2.western { font-family: "Helvetica"; font-size: 14pt; font-style: italic }
H2.cjk { font-size: 14pt; font-style: italic }
H2.ctl { font-size: 14pt; font-style: italic }
H3 { margin-bottom: 0.21cm }
H3.western { font-family: "Helvetica" }
-->
</STYLE>
</HEAD>
<BODY LANG="de-DE" DIR="LTR">
<H1 CLASS="western">BlueProximity manual</H1>
<H2 CLASS="western">Introduction</H2>
<P>This manual tries to give you the most pleasurable experience with
your BlueProximity environment. You should read it carefully to get
the idea behind and fully understand its possibilities and limits.</P>
<P>Basically BlueProximity is a tool to detect your presence near
your computer. It can automatically lock your computer once you leave
it and unlock it when you are back. Technically it does it the
following way. It connects to your mobile phone via bluetooth and
uses the rssi value – something like the automatically set
transmission power – to get a distance approximation. It gives more
a quality information than a quantity one. Bigger numbers are most
likely bigger distances but the rssi value changes slowly and is a
little inaccurate since you could also cover your phone with your
hands – that will increase the rssi value without any distance
change...</P>
<P>You see, we cannot measure exact distances but in stable
environments you will most likely get reproduceable results.</P>
<H2 CLASS="western">Installation</H2>
<P>There are two ways of installing BlueProximity. One and by far the
easiest is by installing the Ubuntu (Feisty) package that can be
downloaded via sourceforge. If you are unsure if that will do or you
have a different distribution you can also select a normal tarball
installation explained below. If the Ubuntu package is installed you
find the start icon in your Applications menu in the utilities
subfolder. To start BlueProximity from the console just type
<KBD>blueproximity</KBD>. You can add this one to your session
manager's startup profile for automatic start with system boot.
Please start it now and move on to the next chapter <EM>Configuration</EM>
in this document.</P>
<P>Using the tarball the prerequisites include a unix system with an
installed python interpreter. You need the <KBD>hcitool</KBD> tool
installed. On my Ubuntu system they are included in the <EM>bluez-utils</EM>
package. You also need the <STRONG>PyGTK</STRONG> (<EM>python-gtk2,
python-glade2</EM>), <EM> </EM><STRONG>ConfigObj</STRONG>
(<EM>python-configobj</EM>) and <STRONG>Bluetooth</STRONG><EM>
(python-bluez) </EM>extensions for python.</P>
<P>You should download the newest version of BlueProximity from its
sourceforge site at <A HREF="http://blueproximity.sourceforge.net/"></A><A HREF="http://blueproximity.sourceforge.net/"></A><A HREF="http://blueproximity.sourceforge.net/">http://blueproximity.sourceforge.net</A><A HREF="http://blueproximity.sourceforge.net/"></A><A HREF="http://blueproximity.sourceforge.net/"></A>
and unpack it via <KBD>tar xvzf blueproximity-versionnumber.tar.gz</KBD></P>
<P>Start BlueProximity by typing <KBD>start_proximity.sh</KBD> which
can also be put in your gnome menu and into the session manager for
automatic start with system boot.
</P>
<H2 CLASS="western">Configuration</H2>
<H3 CLASS="western">Setting up the phone</H3>
<P>First you should pair your computer and your mobile phone. Please
refer to the FAQ part at the end of this manual how to do that. Once
being paired your mobile won't ask for a password when a connection
from the computer to the phone is made. There is still the
possibility that your mobile phone will ask you to accept the
connection which is an additional layer of security appart from the
pairing mechanism. Your phone should have an option to disable this
question for all or even one special paired device. Disable that
question as not disabling it renders BlueProximity quite unusable
since you must always do something to your phone when you come back
to your computer.</P>
<H3 CLASS="western">Connecting the phone</H3>
<P>After setting up the phone computer pair you can now move on and
configure BlueProximity. After the first start you should see the
settings window. If you closed that by accident or it did not show up
(because you had installed BlueProximity earlier), you see the
BlueProximity icon in the notification area as shown here.</P>
<P><IMG SRC="manual_html_34e1dc3d.png" NAME="Grafik1" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>A
single left click on the icon to make the settings screen appear.</P>
<P><IMG SRC="manual_html_m1df5b94c.png" NAME="Grafik2" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>You
will see three tabs regarding different types of settings. On the
first tab you may configure the basic connection between computer and
phone, the second tab will show settings to adapt the distance
detection to your hardware, the third tab defines the actions and
commands that should be engaged when locking or unlocking happens.</P>
<P>The first setting you should adjust is the MAC address of your
mobile phone. If you know it you can skip the next step.</P>
<P>To find out that address you should configure your phone to
bluetooth visible mode. It may be the standard setting but you never
know... Now click on the <KBD>Scan for devices</KBD> button. A scan
takes about 10 seconds. You should find your device in the list now,
maybe among other bluetooth devices around your place.</P>
<P><IMG SRC="manual_html_m4f150133.png" NAME="Grafik3" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>Just
click on your device and on the <KBD>Use selected device</KBD>
button. Your device's mac address should now appear in the mac
address field. If your BlueProximity was started for the first time
your changes will be activated after you close the window, otherwise
any change will be active immediately.</P>
<H3 CLASS="western">Setup distance detection</H3>
<P>Now BlueProximity should already start working but there might be
further tuning of distance parameters needed. Note: Your screen will
never be locked as long as the settings screen is shown. This way you
can change the detection parameters and test them. You will notice
how the icon changes if you play with the values. See the FAQ for a
good way to tune these settings.</P>
<P>The second tab will look like this:</P>
<P><IMG SRC="manual_html_42101a15.png" NAME="Grafik4" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>You
see three sections called Locking, Unlocking and measured atm.
</P>
<P>The Locking section sets the parameters when to lock the screen.
The distance parameter refers to the ruler in the distance section.
You should experiment by placing the phone to a place where you want
the lock to happen. Wait some seconds and you should see the value
grow. It might be easier if you click on the <KBD>Reset Min/Max</KBD>
button, move the mobile phone to the lock perimeter and wait some
seconds. Take it back to the computer and you will see the maximum
value right to the button. Set the lock distance to that value. The
duration parameter controls how many seconds the measured distance
should stay at least at or above the lock distance to lock the
screen. You should set this value to more than one second as it is
possible for the rssi value to oscillate sometimes. You will only
loose seconds of security but win usability by not unexpectedly
locking your screen.</P>
<P>Set the values for unlocking in a similar maner. It is usual to
set the distance lower than the lock distance. Please note that
BlueProximity uses the new settings immediately.</P>
<H3 CLASS="western">Setup of locking actions</H3>
<P>Switch to the third tab named locking to see the following screen:</P>
<P><IMG SRC="manual_html_m16b1226e.png" NAME="Grafik11" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>The
upper section refers to the commands that BlueProximity will execute
for the according event. The preset is the command to lock/unlock the
screen using the GNOME desktop screensaver. If you are a KDE user you
should activate the combobox and select the xscreensaver-command
entry. Please note that this will only work with the KDE integrated
version of xscreensaver. The original xscreensaver does not include
an unlock command.</P>
<P>The proximity command is a command that is executed every given
interval while the user is in reach (the screen is unlocked). That
way you can e.g. prevent your screensaver from becoming active while
you are near. Actually this is the standard setup.</P>
<P>The lower section refers to logging of state changes. The syslog
entry allows you to generate a syslog message on every state change
coming from the given logfacility and the loglevel notice. You may
also additionally or exclusively log to a certain file.</P>
<H3 CLASS="western">Testing the settings</H3>
<P>You could just press the close button and see if your desktop gets
locked or use the simulation mode which is always active if the
settings dialog is open. You can switch to the second tab to see the
actual measured values and the resulting locking state right to the
reset button. You may also have a look at the notification area icon
which even gives you a nice tooltip when hovering your mouse pointer
over it. You will see these icons and messages:</P>
<P><IMG SRC="manual_html_232399f2.png" NAME="Grafik5" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>The
green key shows that BlueProximity thinks everything is ok and you
are around within the safe distance.</P>
<P><IMG SRC="manual_html_m6fd06b47.png" NAME="Grafik6" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>The
yellow key let's you know that the detected distance is now still
below the lock distance but above the unlock distance. So if your
computer was locked by BlueProximity it would not yet be unlocked
here.</P>
<P><IMG SRC="manual_html_m4dd3226e.png" NAME="Grafik7" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>The
red key shows what you would never see while the preferences dialog
is closed – this shows the screen would be locked now.</P>
<P>You should play around with the settings for some time to find a
good setting that fits your demand and environment. See the FAQ if
you have problems to find good values.</P>
<H3 CLASS="western">The configfile</H3>
<P>Once started a config file named ~/.blueproximityrc is created and
shows all configurable settings with their default values. In this
file you may adjust all values found in the gui plus the
communication channel to the mobile phone.
</P>
<H3 CLASS="western">Pausing the software</H3>
<P>If you would like keep the software from connecting to your phone
(because you want to transfer files and it is somewhat interfering
the transmission) you can activate <EM>pause mode</EM>. Right click
on the icon to get the popup menu</P>
<P><IMG SRC="manual_html_20077f87.png" NAME="Grafik8" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>and
select <KBD>Pause</KBD> in that menu. You will see the icon changing
to pause mode too.</P>
<P><IMG SRC="manual_html_m33642ea5.png" NAME="Grafik10" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>To
deactivate pause mode do the above steps again. You will see
BlueProximity reconnecting to your phone and work again.</P>
<H3 CLASS="western">Stopping the software</H3>
<P>If you would like to stop the software (for whatever reason that
might be) you should right click on the tray icon
</P>
<P><IMG SRC="manual_html_20077f87.png" NAME="Grafik9" ALIGN=LEFT BORDER=0><BR CLEAR=LEFT>and
select <KBD>close</KBD> in that menu. It may take up to three seconds
to shutdown the software.</P>
<H3 CLASS="western">FAQ</H3>
<P><EM>Q:</EM> I can't see my mobile phone when scanning.</P>
<P><EM>A:</EM> You need to activate bluetooth and disable
invisibility in your phone's bluetooth settings.</P>
<P><BR><BR>
</P>
<P><EM>Q:</EM> My phone gets detected but the distance is always 255.</P>
<P><EM>A:</EM> Most likely your phone uses another channel for
communication than the phones we tried. You can find a usable channel
by brute force or by using the <KBD>sdptool browse</KBD> command. In
the output watch for the lines starting with <EM>RFCOMM</EM> and
<EM>Channel:</EM> where the number after channel is the needed
channel number. In the config file <CODE>~/.blueproximityrc</CODE>
change the <CODE>device_channel</CODE> setting to the new channel.
Channels address different services on the phone – you might
sometimes even appear as a headset e.g.</P>
<P><BR><BR>
</P>
<P><EM>Q:</EM> I want to connect to my phone (or to my computer) to
send files but it tells me I am already connected and this won't
work. Killing the connection via the phones menu does not work. What
can I do?</P>
<P><EM>A:</EM> You cannot kill the connection from your phone because
BlueProximity restarts the connection immediately afterwards. You can
put BlueProximity into <EM>pause mode</EM> (see previous chapter) or
quit BlueProximity for the time connecting. Pause mode should be
prefered, of course :-).</P>
<P><BR><BR>
</P>
<P><EM>Q: </EM>My Device (either computer or phone) always asks for a
password or pin. How can I change that?</P>
<P><EM>A: </EM>Most likely your devices are not paired yet. Please
install the gnome-bluetooth applet if that is not there yet. With
Ubuntu the package's name is bluez-gnome.
</P>
<P>After starting the applet (bluetooth-applet) you should configure
your
computer as laptop and visible to others. (Right click on the
new Bluetooth
icon and click on Preferences/Einstellungen)
</P>
<P>Afterwards take your phone and do something similar to these
steps: (I
have a nokia 6230)
</P>
<P>0. If BlueProximity is running, rightclick on its icon and select
"Pause"
</P>
<P>1. Take the phone and enter the BT menu
</P>
<P>2. Move to "Paired Devices" (Gekoppelte Geräte)
</P>
<P>3. Select Options->"Pair new device" (Neues Gerät
koppeln)
</P>
<P>The phone should look for unpaired bluetooth devices in reach. It
should
then show at least your notebooks name (as found in the
bluetooth applets
settings)
</P>
<P>4. Select your notebook and it should ask you for your pin. Now
enter the
pin from /etc/bluetooth/pin.
</P>
<P>5. The bluetooth applet should now state that it trusts your
mobile
(created bonding).
</P>
<P>6. You should now change the settings for the notebook on your
phone, so
select the notebook
</P>
<P>7. Select Options->connect without confirmation (Automatische
Verbindung
ohne Bestätigung) and set that to Yes.
</P>
<P>Now you are ready to use BlueProximity. Please note again that the
above
steps are only valid on a nokia 6230 - if your phone is
different, you
should adopt the above procedure to your phones menu
setup.
</P>
<P>If BlueProximity is still in Pause mode click on Pause again. It
should
now connect without any hassle.</P>
<P><BR><BR>
</P>
<P><EM>Q: </EM>The locking or unlocking doesn't feel right – it
takes too long to get it locked or locks to early or unlocks too
late.</P>
<P><EM>A: </EM>Use this algorithm to get good results:
</P>
<P>Set the lock distance up a bit and increase lock duration even
more. (I am using 7/10.) Your milage may vary since it all depends on
the hardware and the environment. The distance control is done by
measuring the rssi (signal strength indicator) which is not
deterministic. Sometimes it goes up to a certain value for no reason
and will go back normal soon, so you should set the lock distance to
that level and since it won't stay there long set the lock duration
value something to like 10.
</P>
<P>For unlocking you should select a value of about half of the lock
distance but a very small unlock duration. That makes sure you are
around and not just passing by but it should still unlock fast enough
to use it after you sat down. (4/1 is my value pair here). Note that
the distance value is calculated and never does big in-/decrements.
so if you come back and the first measured value is 8, it will
probably go down one by one per second so the 1 second unlock
duration still feels quite long. If there is too much time passing
you should increase the unlock distance by one and test it again.</P>
</BODY>
</HTML>
|