jrodal98 / connected-crossroad Goto Github PK

Each device starts advertising as device name 0 when the app starts, as seen in the startAdvertising method in AODVNetwork.java. There is a setAddress method in the same file that will change the device name. However, I don't think it will change the name that the device is currently advertising as, since I assume the nearby connection advertising method creates a copy of the address variable. I'm guessing that we either shouldn't start advertising until a device name has been set or we should restart advertising after a device name has been set. (We could also generate a really big random number and set that as the device name and pray that the laws of probability protect us from duplicate naming, but that would probably be a huge pain to type in the "send to address" section. This is what I originally did to distinguish devices in the pre-addressing scheme days).

• Movement states need to include at least walking, running, and standing still (which the api below does)
• I think this can be used to designate certain functions to run whenever a state is entered or exited: https://developers.google.com/android/reference/com/google/android/gms/location/ActivityRecognitionClient
• I think this predicts the state immediately when called: https://developers.google.com/android/reference/com/google/android/gms/location/DetectedActivity