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

Surveys including the camera-los control are not rendered properly #164

Open
rgamez opened this issue Jul 24, 2015 · 1 comment
Open

Surveys including the camera-los control are not rendered properly #164

rgamez opened this issue Jul 24, 2015 · 1 comment

Comments

@rgamez
Copy link

rgamez commented Jul 24, 2015

Cardigan Bay are having a couple of issues with their Tablet devices since the latest update. One of the more serious issues is that the camera capture functionality seems to have been lost. Instead of giving access to camera they can only choose existing image files (see attached image). The device on the left is after the update and the device on the right has yet to be updated.

170246057

@rgamez rgamez changed the title Surveys including the camera-va control are not rendered properly Surveys including the camera-los control are not rendered properly Jul 24, 2015
rgamez added a commit to edina/fieldtrip-camera-va that referenced this issue Jul 24, 2015
Function signature changed in the core

Issue cobweb-eu/cobweb#164
rgamez added a commit to edina/fieldtrip-cobweb-project that referenced this issue Jul 24, 2015
Update:
[email protected]
decision [email protected]

Revert plugins (removing the bluetooth one) to the ones used for the 0.1.0
release

Issue cobweb-eu/cobweb#164
rgamez added a commit to edina/fieldtrip-cobweb-project that referenced this issue Jul 24, 2015
Update:
[email protected]
decision [email protected]

Revert plugins (removing the bluetooth one) to the ones used for the
0.1.0 release

Issue cobweb-eu/cobweb#164
@MHiggins-EnvSys
Copy link

Ruben, I took a look at this on a virtual tablet and compared APK v.0.1.0 against APK v.0.1.1. The older APK presented the issue above. There were no display issues in the more recent app - everything looked normal, so it looks to be fixed. Unfortunately we do not have access to a physical tablet at the moment so take from this what you will.

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

No branches or pull requests

2 participants