Skip to content

Running the app

Jump to bottom
Justin Chan edited this page May 14, 2020 · 16 revisions

Here is a video demo of how to run our app.

Notes

  • Make sure that PUBLIC_DEMO in Constants.java is false. You have to set this to false on your own in order to run any kind of end-to-end demo. This is deliberately set to true for the .apk that is hosted for download on our website as it disables all interactions with our server backend. In other words you cannot submit reports of a positive diagnosis to our backend. And you cannot poll for potential exposures or narrowcast messages from our backend either.
  • The above video demo is done in DEBUG mode. Make sure that in Constants.java DEBUG is true. With DEBUG mode, the minimum time for exposure is 30 seconds instead of 10 minutes (which are the CDC guidelines)
  • In DEBUG mode the Bluetooth IDs change about once every 10 seconds.
  • Make sure BASE_URL in NetworkConstant.java points to the correct endpoint

The following sequence of steps can be executed to produce an end-to-end demo of the functionality of the app:

Instructions

  1. Install the app on two phones.
  2. Turn on location and Bluetooth. Leave them within Bluetooth range for about 30 seconds.
  3. On phone A, submit a infection report. On phone B, pull down to refresh. You should now observe an exposure notification.
  4. On phone A, pull down to refresh, observe that there are no notifications.
  5. On phone B, submit an infection report.
  6. On phone A, pull down to refresh, and observe that there is now an exposure notification.

A few key parameters

  • CDCExposureTimeInMinutesDebug indicates 30 seconds is the threshold for exposure
  • UUIDGenerationIntervalInSecondsDebug indicates how frequently Bluetooth IDs are generated
  • BluetoothScanIntervalInSecondsDebug indicates how frequently the device scans for Bluetooth IDs (should be the same as UUIDGenerationIntervalInSecondsDebug)
  • NetworkConstant.java contains the base URL for the backend endpoint you would want to change this.
  • Constants.java encodes
  • DEBUG can be set to true or false. The DEBUG mode uses the aforementioned parameters, and can be used for showing a demo. When DEBUG mode is false, the above parameters are altered. For example exposure time is defined as 10 minutes and IDs are generated every 15 minutes.

Our tool sends out Bluetooth IDs that are randomized every 15 minutes like in this video (0:33)

This video (0:56) demonstrates an initial prototype logging GPS and Bluetooth and sending data to a local server

Clone this wiki locally