Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show the changes to the UI after user chooses mode/purpose on list screen #307

Open
wants to merge 6 commits into
base: cci-berkeley
Choose a base branch
from

Conversation

sunil07t
Copy link
Contributor

Before the user could choose the mode/purpose but it did not show up on the screen. This change will show the selected mode/purpose on the UI. Following are the screenshots of the UI
screen shot 2017-12-27 at 11 07 20 pm
screen shot 2017-12-27 at 11 07 34 pm

@AmplabJenkins
Copy link

Can one of the admins verify this patch?

@atton16
Copy link
Contributor

atton16 commented Dec 16, 2018

When user answer to the prompt, will the answer get synced after the next trip has ended?

@shankari
Copy link
Contributor

shankari commented Dec 17, 2018

When user answer to the prompt, will the answer get synced after the next trip has ended?

In general, yes. It depends on when the user provides the answer. The trip end is typically detected ~ 5-10 mins after the user actually stops moving; we need that time to ensure that stops are not treated as trip ends.

So if the user responds before the trip end is detected, it will be pushed at this trip end, otherwise, at the next trip end. Note that the prompt happens when the trip end is detected.

The answers to the responses are stored in the local database, just like all other data collected on the phone. The goal is to make the data collection robust to connection failures - we should be able to collect data even when the user is underground, has no connectivity...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants