-
Notifications
You must be signed in to change notification settings - Fork 2
Prototype Operation
This page describes the operation of TrafficSense prototypes and Pebble application.
The application will start automatically when the Android application is started, but it will start to function only after the Android application has finished loading the route.
While waiting for the vehicle or walking to the bus stop, the application will show the stop name, vehicle line number and time until the estimated arrival time of the vehicle.
On the estimated arrival time or on arrival to the second stop of the segment, the screen will automatically change to a view which shows the next 2 stops and after those, the last one. When arriving to the second last stop, it will change back to the basic screen.
On the stop list view, press the middle button on the right side of the watch to toggle viewing stop codes and stop names.
On any screen, press the button on the left side to exit the application.
- The Pebble application is dependent on the Android application.
The FirstPrototype retrieves a journey sent by HSL Reittiopas to an e-mail account and traces it by using time information.
-
Send a journey to your designated e-mail account from Reittiopas
-
Tap "automatic" button.
The prototype is then expected to follow the journey using wall clock time. When we are approaching a stop, a Toast is shown on Android device and Pebble UI is scrolled one stop down. When we are reaching the end of current segment, that is when we are about to change connection, Android device and Pebble smart watch are vibrated in addition to textual notifications.
The aforementioned notifications work also when the Android application is in background.
User may tap "stop" at any time after the prototype started to follow the journey. Practically, this means that the Toast is showing and/or the lowest text box is being updated.
The boolean value useWallClock in class org.apps8os.trafficsense.android.Constants indicates whether the time-based service use wall clock or "toy time".
Second prototype uses location information and GeoFencing to assist the user on the route. The user interface includes two alternative views: schematic view and map view.
Google Play services library that allows us to draw circles on the map. These circles around each bus stop detects approaching user (device).
-
User sends a journey from Reittiopas to his/her designated email
-
In Android application tap "START JOURNEY" button.
-
Map UI will refresh and show the route.
"SCHEMATIC JOURNEY" button enables stop list view.
"MAP JOURNEY" goes back to map view.
- Android and Pebble provide notifications along the route.
On entry to second last GeoFence (stop) of each segment a notification for approaching end/change is generated.
- Map will not work without proper APK signing.
- GeoFencing requires the device to be configured to enable Google Location Service and allow transmitting location information to Google for services.
- Current radius of GeoFences is 100 meters.
- The number of GeoFences is limited by Google to 100. This prototype is thus unable to track a journey with more than 100 waypoints/stops.
- Set
Constants.useWallClockin Library to true to enables journey-in-the-past check. #4
In the testing situation we can use mock location: lockito.
Suggested procedure:
-
Reboot the phone.
-
In Settings: disable GPS and Google Location service related options.
-
Start lockito, start an itinerary and let it lock the location of the device.
-
In Settings: enable previously disabled settings.
-
Start TrafficSense prototype.
See here