– Stores and holds all information (device address, RSSI, etc.) for a given BLE device.

– Background service that handles communication between the sensor device and the phone. It sends updates the DeviceActivity when some kind of communication occurs between the device and phone. These updates consist of:

• Connection changes (disconnect or connection)
• Reads (if the gatt server on the device writes to the phone)
• Writes (If the phone wants to right to the device. This can be to change the transmission data rate or other key features on the device)
• Notifications (the device sends a notification to tell the phone that it has sensor data available. The phone can use this notification to extract the data and manipulate it)

– Handles the UUID information for the Gatt server hosted on the device. The UUID is a string that identifies the device by its address, name and description. It also contains information on the sensors on the board and how to change them.

– Handles the ‘about’ option accessible from the main activity. Doesn’t do much other than bring up a dialog box displaying information.

– The activity that handles the communication between the device and phone. This activity gets updates from the BluetoothLeSevice regarding device communication. Using these updates the DeviceActivity can receive sensor data. Using this data, the DeviceActivity plots the data and writes it to the web server. If there is no network connection, the activity saves the data to internal phone memory. When network connection is restored, it flushes all saved data to the database. The DeviceActivity also has options to change what accelerometer axes are being plotted and can call the HistoryPlot activity.

– An activity that allows the user to enter starting and ending dates and times and retrieve data from the database corresponding to that time interval. It then creates a static plot of that time period. This activity is only partially complete, and does not function currently.

– A class that is used to convert a saved file into a pure byte array. It is used by the DeviceActivity to retrieve saved acceleration data when the application is flushing old data to the database.

– The main activity of the application. It handles device discovery and initial connection, as well as setting up the display framework for the application. It initiates the BluetoothLeService. This is based heavily on TI code and will not need to be changed.

– Handles the display and logging for the device scanning process. It is implemented in the main activity. It is based heavily on TI code and should not be changed.

– Enum that contains data regarding each different sensor on the TI device. It includes different UUID information for each sensor. It is based heavily on TI code and should not be changed.

– Contains a list of all the UUIDs for each sensor and sensor attribute. This class does not need to be changed, as the UUIDs are set for the TI device.

– Enum that defines the states of the two buttons for the TI device. It is not useful for our application, as we do not use the buttons on the device. It is TI code, and is not removed to avoid throwing errors in the other activities.

– TI code that adjusts the display properties for some of the activities. Does not need to be changed.

– Contains utility functions for data conversion, etc.

– Timer that determines how quickly device discovery times out.

– Abstract class that has functions which are called on timeout and on tick. It is used by the CustomTimer class.

– A modified toast class. It has slightly different properties than a default toast call.

– Contains three variables that each correspond to a different axis. Used for storing acceleration axes data.