FAQs

Q: What can I use AIRS for?

A: AIRS can record a plethora of information, either directly originating from your device (sensors like orientation or light as well as information such as tasks running and many more) or attached via Bluetooth (such as the AliveTech ECG monitor). The recorded data can be used for many purposes such as activity recording, lifestyle monitoring, GPS tracking (with annotation of things like phone orientation) or many more. AIRS is currently used in the UK-funded project PAL for activity monitoring related to lifestyle management. Since Version 1.8.6, there is a JAR file included in the distribution that parses the locally recorded text files of AIRS (after uploading them to your desktop) and inserts the values into a locally installed MySQL database. You could use such MySQL database for, e.g., visualising the values in a local browser (using PHP scripting or similar).


Q: Where can I get the source code from?

A: AIRS is hosted in its own Github project, where you can review the code or branch your own project. AIRS is licensed under LGPL2.0 (in order to enable your own applications on top of the general platform).


Q: Where can I get the application server from?

A: The application server is still part of the original NORS development at Sourceforge. You can download the application server as a separate package from Sourceforge.


Q: Is it possible to add a particular sensor to AIRS?

A: Generally, AIRS can be extended with any ‘sensor’ that you like, e.g., physical information (such as light) or phone information (such as RAM etc). You can either do this yourself, as explained here, or drop me an email with the idea and I’ll see what I can do.


Q: Does AIRS allow to spy on me?

A: Generally, NO! AIRS records various data. You are under full control as to what this data is as well as when to record. It is you who needs to start AIRS on the mobile and you need to install the application server, if you want to record remotely.


Q: Why can’t I share certain sensor values with a long click on a sensor in the measurement window?

A: Meaningful strings of sensor values are only supported for certain (although most) sensors.


Q: How can do anything meaningful with my local recordings?

A: You would need to parse the text file that is created during a local recording and perform actions (such as displaying values) over these recordings. Dana Pavel has kindly agreed to include a Java-based file in the current Github distribution of AIRS that does exactly that. There is a readme file included that explains how to set up the required MySQL software. What you will get with this additional step is a MySQL database that is populated with your recordings. You can then more easily implement, e.g., PHP-based web pages that visualize your recordings to your liking.


Q: How can I adjust the sound pressure levels for the AA sensor?

A: Go into the Audio Sampling settings with the Handler Settings menu. Here, you can find a setting that defines the adjustment for the sound pressure in dB. The way to use this adjustment is by measuring a constant noise level with a calibrated noise meter while running AIRS. Compare the AA reading in AIRS with the noise meter’s reading, calculate the difference between noise meter and the AA reading. Place this difference (including the possible sign when the difference is negative) into the adjustment setting.


Q: How can I quickly change settings for supporting different recording scenarios?

A: Since V2.6.6.1, AIRS supports creating launcher shortcuts that are bound to particular settings. Hence, configure AIRS according to your scenario (including the handler and general settings), select the sensors you like to record. Then create a Quick Start shortcut in the local tab of the main UI. A shortcut will appear on your launcher homescreen (in many replacement launchers, you can rename the shortcut into something more meaningful). Every time you start AIRS through this shortcut, the associated settings will be copied over the current ones (this will also remove any setting change you might have done!). If you want a different recording scenario, simply configure AIRS accordingly as before and create another shortcut through the Quick Start menu. When starting AIRS through this shortcut now, the different settings will be used instead.

Leave a Reply