Moto E not supported?

[gciccarelli3]

Hi,

Can you provide any information as to why the Moto E android phone would be declared incompatible with Ohmage? It's android version 4.4.4. I have no data plan/ carrier associated with the phone. Is that required?

Thank You,
Greg

[stevenolen]

Hi @gr21783! I did some research and it looks like this is related to the requirement in our app for openGL es 2.0

https://github.com/ohmage/android-lib/blob/master/AndroidManifest.xml#L37-L39
(note i've linked to the android-lib project, which is for the current ohmage android version in the play store).

I'm not sure why the Moto E wouldn't support this, but it looks like unless the app has been specifically coded to fall back to an older openGL es we aren't going to be able to just set this parameter to android.required="false" in order to make it work. A stack overflow page detailing this (and suggesting that as of 2013, all android devices should support openGL es 2) can be found here

Since this is an issue with the android-lib project, I'm going to open an issue for there and reference this issue, but that project is currently without a developer, so not sure how quickly we could get a fix..new issue is here

Thanks!

[gciccarelli3]

Hi Steve,

Thanks for the information. Could you clarify some things about the state
of the ohmage project for me?

We're currently running ohmage 2.16 on an amazon EC2 system. We'd like to
upgrade to ohmage 3.0, but can't find any documents that actually confirm
3.0 is released or how to install it. What version of ohmage are you
running? Could you advise on how to go about installing it? We tried some
of the instructions on github but the /opt/ohmage directory did not appear
to be created.

Thanks,
Greg

On Thu, Nov 13, 2014 at 1:36 PM, stevenolen notifications@github.com
wrote:

Hi @gr21783 https://github.com/gr21783! I did some research and it
looks like this is related to the requirement in our app for openGL es 2.0

https://github.com/ohmage/android-lib/blob/master/AndroidManifest.xml#L37-L39
(note i've linked to the android-lib project, which is for the current
ohmage android version in the play store).

I'm not sure why the Moto E wouldn't support this, but it looks like
unless the app has been specifically coded to fall back to an older openGL
es we aren't going to be able to just set this parameter to
android.required="false" in order to make it work. A stack overflow page
detailing this (and suggesting that as of 2013, all android devices should
support openGL es 2) can be found here
http://stackoverflow.com/questions/13714484/android-maps-api-requires-opengl-es-2

Since this is an issue with the android-lib project, I'm going to open an
issue for there and reference this issue, but that project is currently
without a developer, so not sure how quickly we could get a fix..new issue
is here ohmage/android-lib#102

Thanks!

—
Reply to this email directly or view it on GitHub
#95 (comment).

[stevenolen]

Hi!

The ohmage 3.0 is in a bit of flux right now, it's not quite done -- but we don't have any developers actively focusing on it for the time being. Additionally, it was a complete re-write of the code with some core changes to how permissions and campaigns/projects work -- so once stable it will take some additional effort to migrate existing studies.

My suggestion for now would be to continue using 2.16 as the code is quite stable and being actively used in a number of large deployments. Bugfixes will continue to be pushed to the 2.16 branch!

Thanks!

[gciccarelli3]

Hi Steve,

We're building a mobile app interface to the ohmage server for signup, and
we're wondering if there is a way to avoid needing a capctcha if signup is
done from a mobile phone. In other words, could we just have a token built
into the app that lets signup bypass captcha authentication. We could
patch the 2.16 server, but if there was an easier way, we'd like to hear it.

Also, we may be having difficulty with autoenrolling of subjects. They
enroll, but the public class doesn't seem to automatically attached to the
campaign.

Thanks,
Greg

On Sun, Nov 30, 2014 at 4:51 PM, stevenolen notifications@github.com
wrote:

Hi!

The ohmage 3.0 is in a bit of flux right now, it's not quite done -- but
we don't have any developers actively focusing on it for the time being.
Additionally, it was a complete re-write of the code with some core changes
to how permissions and campaigns/projects work -- so once stable it will
take some additional effort to migrate existing studies.

My suggestion for now would be to continue using 2.16 as the code is quite
stable and being actively used in a number of large deployments. Bugfixes
will continue to be pushed to the 2.16 branch!

Thanks!

—
Reply to this email directly or view it on GitHub
#95 (comment).

[stevenolen]

Hi Greg!

As far as I know, no, there is no simpler way than patching the server to remove the captcha requirement. You may want to investigate rate-limiting that API or providing some other method by which to prevent account creation spam if you do!

We haven't seen a problem like the autoenrolling issue you're having. The standard procedure for the public class is to attach a campaign to it, and then on user/create the user is added to the public campaign (and they can refresh their campaign list on their app to view the campaign). If you're following that process (which you surely are) could you send along a server debug log of what the user/create process and I can take a look?

Finally! If you'd like to batch account create, you may want to take a look at the ohmage-2.16_user_setup_password branch on github. We appended an extra process/api to the server to help teachers in one of our deployments create accounts for the students in their classes. The mobilizingcs/teacher project accepts csv files as upload from teachers and batch creates accounts using the user/setup api. You may be able to customize it to your needs if you'd like to auto-generate/enroll accounts for participants.

good luck and happy holidays!

[gciccarelli3]

Hi Steve,

Happy New Year! We've solved our enrollment issue but have hit another
stumbling block. We tried to relocate the mysql database to a mounted
volume on the amazon ec2 instance. Everything seemed to go fine until I
had to restart the mysql server. I'm not sure if this error is independent
of the ohmage installation or not. Also, is there any way to install the
ohmage mysql database directory directly on the external drive rather than
trying to move it?

I followed this procedure here, until the end where I tried all
permutations that I could think of for restarting the server and editing
files based on the comments.
http://stackoverflow.com/questions/1795176/how-to-change-mysql-data-directory

I was able to relocate the audio and video directories, but I need to move
all the table information to the encrypted drive, hence this more involved
process.

Thanks,
Greg

On Fri, Dec 19, 2014 at 7:24 PM, stevenolen notifications@github.com
wrote:

Hi Greg!

As far as I know, no, there is no simpler way than patching the server to
remove the captcha requirement. You may want to investigate rate-limiting
that API or providing some other method by which to prevent account
creation spam if you do!

We haven't seen a problem like the autoenrolling issue you're having. The
standard procedure for the public class is to attach a campaign to it, and
then on user/create the user is added to the public campaign (and they can
refresh their campaign list on their app to view the campaign). If you're
following that process (which you surely are) could you send along a server
debug log of what the user/create process and I can take a look?

Finally! If you'd like to batch account create, you may want to take a
look at the ohmage-2.16_user_setup_password branch on github. We appended
an extra process/api to the server to help teachers in one of our
deployments create accounts for the students in their classes. The
mobilizingcs/teacher https://github.com/mobilizingcs/teacher project
accepts csv files as upload from teachers and batch creates accounts using
the user/setup api. You may be able to customize it to your needs if you'd
like to auto-generate/enroll accounts for participants.

good luck and happy holidays!

—
Reply to this email directly or view it on GitHub
#95 (comment).

[gciccarelli3]

$ service mysql restart
stop: Unknown instance:
start: Rejected send message, 1 matched rules; type="method_call",
sender=":1.26" (uid=1000 pid=29233 comm="start mysql ")
interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)"
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1
comm="/sbin/init")

On Fri, Feb 6, 2015 at 9:42 AM, Gregory Ciccarelli gciccarelli@mit.edu
wrote:

Hi Steve,

Happy New Year! We've solved our enrollment issue but have hit another
stumbling block. We tried to relocate the mysql database to a mounted
volume on the amazon ec2 instance. Everything seemed to go fine until I
had to restart the mysql server. I'm not sure if this error is independent
of the ohmage installation or not. Also, is there any way to install the
ohmage mysql database directory directly on the external drive rather than
trying to move it?

I followed this procedure here, until the end where I tried all
permutations that I could think of for restarting the server and editing
files based on the comments.

http://stackoverflow.com/questions/1795176/how-to-change-mysql-data-directory

I was able to relocate the audio and video directories, but I need to move
all the table information to the encrypted drive, hence this more involved
process.

Thanks,
Greg

On Fri, Dec 19, 2014 at 7:24 PM, stevenolen notifications@github.com
wrote:

Hi Greg!

As far as I know, no, there is no simpler way than patching the server to
remove the captcha requirement. You may want to investigate rate-limiting
that API or providing some other method by which to prevent account
creation spam if you do!

We haven't seen a problem like the autoenrolling issue you're having. The
standard procedure for the public class is to attach a campaign to it, and
then on user/create the user is added to the public campaign (and they can
refresh their campaign list on their app to view the campaign). If you're
following that process (which you surely are) could you send along a server
debug log of what the user/create process and I can take a look?

Finally! If you'd like to batch account create, you may want to take a
look at the ohmage-2.16_user_setup_password branch on github. We appended
an extra process/api to the server to help teachers in one of our
deployments create accounts for the students in their classes. The
mobilizingcs/teacher https://github.com/mobilizingcs/teacher project
accepts csv files as upload from teachers and batch creates accounts using
the user/setup api. You may be able to customize it to your needs if you'd
like to auto-generate/enroll accounts for participants.

good luck and happy holidays!

—
Reply to this email directly or view it on GitHub
#95 (comment).

[gciccarelli3]

Never mind- I think I got it- or at least that error. Knock on wood.

On Fri, Feb 6, 2015 at 9:43 AM, Gregory Ciccarelli gciccarelli@mit.edu
wrote:

$ service mysql restart
stop: Unknown instance:
start: Rejected send message, 1 matched rules; type="method_call",
sender=":1.26" (uid=1000 pid=29233 comm="start mysql ")
interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)"
requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1
comm="/sbin/init")

On Fri, Feb 6, 2015 at 9:42 AM, Gregory Ciccarelli gciccarelli@mit.edu
wrote:

Hi Steve,

Happy New Year! We've solved our enrollment issue but have hit another
stumbling block. We tried to relocate the mysql database to a mounted
volume on the amazon ec2 instance. Everything seemed to go fine until I
had to restart the mysql server. I'm not sure if this error is independent
of the ohmage installation or not. Also, is there any way to install the
ohmage mysql database directory directly on the external drive rather than
trying to move it?

I followed this procedure here, until the end where I tried all
permutations that I could think of for restarting the server and editing
files based on the comments.

http://stackoverflow.com/questions/1795176/how-to-change-mysql-data-directory

I was able to relocate the audio and video directories, but I need to
move all the table information to the encrypted drive, hence this more
involved process.

Thanks,
Greg

On Fri, Dec 19, 2014 at 7:24 PM, stevenolen notifications@github.com
wrote:

Hi Greg!

As far as I know, no, there is no simpler way than patching the server
to remove the captcha requirement. You may want to investigate
rate-limiting that API or providing some other method by which to prevent
account creation spam if you do!

We haven't seen a problem like the autoenrolling issue you're having.
The standard procedure for the public class is to attach a campaign to it,
and then on user/create the user is added to the public campaign (and they
can refresh their campaign list on their app to view the campaign). If
you're following that process (which you surely are) could you send along a
server debug log of what the user/create process and I can take a look?

Finally! If you'd like to batch account create, you may want to take a
look at the ohmage-2.16_user_setup_password branch on github. We appended
an extra process/api to the server to help teachers in one of our
deployments create accounts for the students in their classes. The
mobilizingcs/teacher https://github.com/mobilizingcs/teacher project
accepts csv files as upload from teachers and batch creates accounts using
the user/setup api. You may be able to customize it to your needs if you'd
like to auto-generate/enroll accounts for participants.

good luck and happy holidays!

—
Reply to this email directly or view it on GitHub
#95 (comment).

[stevenolen]

Hi Greg!

Glad to see you're making progress! The movement of mysql is really more of a system-level issue, but I'm happy to give you a bit more insight into ohmage's use of the db (and a typical way to migrate the ohmage data to another system.

Firstly, ohmage connects to the database only through the connection specified in /etc/ohmage.conf (or the default property set which is located here. you can modify the port/address to point the container to another mysql instance. Once you have a connection to the new database, you can either dump and restore the ohmage data (via mysql -uohmage -p ohmage > /old/system/ohmage_db_dump.sql and then mysql -uohmage -p ohmage < /new/system/ohmage_db_dump.sql) or if you don't have any data that needs to be restored, you can just prep the database as new. Prepping the database as new can be done by executing a number of these sql scripts from this directory: https://github.com/ohmage/server/tree/master/db/sql

You'll need:

• base/ohmage-ddl.sql
• preferences/default-preferences.sql
• all files from settings

If you do the prep method, you'll probably need to set a few parameters in the preferences table (such as where your static content directories are located etc.). When you start ohmage, check out /var/log/ohmage/ohmage.log (or wherever you've specified your log directory to be), it'll let you know if you've missed something!

Good luck!

[stevenolen]

one more thing to note here, I see you mention an encrypted disk for the db data. Since you're using ec2, you may want to look in to using amazon rds (http://aws.amazon.com/rds/) for your db connection to ohmage, since it provides data-at-rest encryption and removes your need to manage an encrypted disk.