Processing power needed for a very long form

Hi All,

I have finished creating a form that is about 500 questions, where each
question has at least 5 logic requirements applied to it. I have the entire
form working fine on my Nexus One Android phone. However, our client is
testing the form on a Samsung Galaxy Mini and they are encountering an
error at the very end of the survey.

They say that once the entire form is filled out and they reach the last
screen (where you click the "Mark as Finished" button) and click the "Save"
button, the phone says "...saving" and then either Force Closes or just
goes back to the home menu (once here, the form can not be found on the
phone at all).

I have tried the form multiple times to see if I can recreate the error,
which I can't. Is it possible that the phone they are using doesn't have
enough processing power or memory to process such a long form? Has anyone
ever experienced a problem like this before?

Another problem we are having is that on the Galaxy Mini phone when ODK
force closes, our client says there there is no "Report" option. Is there
an option to turn this on/off somehow?

Thanks
Evelyn

··· -- Evelyn Castle Director, eHealth Nigeria www.eHealthNigeria.org 25 Race Course Road, Kano, Ng mobile: (NG) 0809-515-0585 (NG) 0813-883-2395 (US) 714-721-3157

Have you reproduced this on a second galaxy mini? It could be as simple as
a bad SD card.

Hi All,
I have finished creating a form that is about 500 questions, where each
question has at least 5 logic requirements applied to it. I have the entire
form working fine on my Nexus One Android phone. However, our client is
testing the form on a Samsung Galaxy Mini and they are encountering an
error at the very end of the survey.
They say that once the entire form is filled out and they reach the last
screen (where you click the "Mark as Finished" button) and click the "Save"
button, the phone says "...saving" and then either Force Closes or just
goes back to the home menu (once here, the form can not be found on the
phone at all).
I have tried the form multiple times to see if I can recreate the error,
which I can't. Is it possible that the phone they are using doesn't have
enough processing power or memory to process such a long form? Has anyone
ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone when ODK
force closes, our client says there there is no "Report" option. Is there
an option to turn this on/off somehow?

··· On Friday, February 10, 2012, Evelyn Castle wrote: > Thanks > Evelyn > > -- > Evelyn Castle > Director, eHealth Nigeria > www.eHealthNigeria.org > 25 Race Course Road, Kano, Ng > mobile: (NG) 0809-515-0585 > (NG) 0813-883-2395 > (US) 714-721-3157 > > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en >

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

··· On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello wrote: > Have you reproduced this on a second galaxy mini? It could be as simple as > a bad SD card. > > > > On Friday, February 10, 2012, Evelyn Castle wrote: >> Hi All, >> I have finished creating a form that is about 500 questions, where each >> question has at least 5 logic requirements applied to it. I have the entire >> form working fine on my Nexus One Android phone. However, our client is >> testing the form on a Samsung Galaxy Mini and they are encountering an error >> at the very end of the survey. >> They say that once the entire form is filled out and they reach the last >> screen (where you click the "Mark as Finished" button) and click the "Save" >> button, the phone says "...saving" and then either Force Closes or just goes >> back to the home menu (once here, the form can not be found on the phone at >> all). >> I have tried the form multiple times to see if I can recreate the error, >> which I can't. Is it possible that the phone they are using doesn't have >> enough processing power or memory to process such a long form? Has anyone >> ever experienced a problem like this before? >> Another problem we are having is that on the Galaxy Mini phone when ODK >> force closes, our client says there there is no "Report" option. Is there an >> option to turn this on/off somehow? >> Thanks >> Evelyn >> >> -- >> Evelyn Castle >> Director, eHealth Nigeria >> www.eHealthNigeria.org >> 25 Race Course Road, Kano, Ng >> mobile: (NG) 0809-515-0585 >> (NG) 0813-883-2395 >> (US) 714-721-3157 >> >> >> -- >> Post: opendatakit@googlegroups.com >> Unsubscribe: opendatakit+unsubscribe@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > -- > Post: opendatakit@googlegroups.com > Unsubscribe: opendatakit+unsubscribe@googlegroups.com > Options: http://groups.google.com/group/opendatakit?hl=en

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had the
upgraded Android version (Gingerbread). The phones that are not working are
still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot of
information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen but the
    form is not in the "send finalized forms" section or "edit saved forms"
    section
  2. The application force closes

Here is the stack trace from one of the times the application force closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue
herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

alogcat.2012-02-13-14-36-45+0100.txt (11.9 KB)

alogcat.2012-02-13-15-27-38+0100.txt (13.6 KB)

··· On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as simple
as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle evelyn@ehealthnigeria.org wrote:

Hi All,
I have finished creating a form that is about 500 questions, where each
question has at least 5 logic requirements applied to it. I have the
entire

form working fine on my Nexus One Android phone. However, our client is
testing the form on a Samsung Galaxy Mini and they are encountering an
error

at the very end of the survey.
They say that once the entire form is filled out and they reach the last
screen (where you click the "Mark as Finished" button) and click the
"Save"

button, the phone says "...saving" and then either Force Closes or just
goes

back to the home menu (once here, the form can not be found on the
phone at

all).
I have tried the form multiple times to see if I can recreate the error,
which I can't. Is it possible that the phone they are using doesn't have
enough processing power or memory to process such a long form? Has
anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone when ODK
force closes, our client says there there is no "Report" option. Is
there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria


25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number: GT-S5570.
    The problem is consistent: when a full survey is entered (meaning that no
    large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is about
    the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try to do
    that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

··· On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had the
upgraded Android version (Gingerbread). The phones that are not working are
still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot of
information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen but
    the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.com wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle evelyn@ehealthnigeria.org wrote:

Hi All,
I have finished creating a form that is about 500 questions, where each
question has at least 5 logic requirements applied to it. I have the
entire

form working fine on my Nexus One Android phone. However, our client is
testing the form on a Samsung Galaxy Mini and they are encountering an
error

at the very end of the survey.
They say that once the entire form is filled out and they reach the
last

screen (where you click the "Mark as Finished" button) and click the
"Save"

button, the phone says "...saving" and then either Force Closes or
just goes

back to the home menu (once here, the form can not be found on the
phone at

all).
I have tried the form multiple times to see if I can recreate the
error,

which I can't. Is it possible that the phone they are using doesn't
have

enough processing power or memory to process such a long form? Has
anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone when ODK
force closes, our client says there there is no "Report" option. Is
there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with the
options to "wait" and "force close"? Or does it just give you a message
that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday with
a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

··· On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is about
    the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try to do
    that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle evelyn@ehealthnigeria.orgwrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had the
upgraded Android version (Gingerbread). The phones that are not working are
still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot of
information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen but
    the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.com wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle <evelyn@ehealthnigeria.org wrote:

Hi All,
I have finished creating a form that is about 500 questions, where
each

question has at least 5 logic requirements applied to it. I have the
entire

form working fine on my Nexus One Android phone. However, our client
is

testing the form on a Samsung Galaxy Mini and they are encountering
an error

at the very end of the survey.
They say that once the entire form is filled out and they reach the
last

screen (where you click the "Mark as Finished" button) and click the
"Save"

button, the phone says "...saving" and then either Force Closes or
just goes

back to the home menu (once here, the form can not be found on the
phone at

all).
I have tried the form multiple times to see if I can recreate the
error,

which I can't. Is it possible that the phone they are using doesn't
have

enough processing power or memory to process such a long form? Has
anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone when
ODK

force closes, our client says there there is no "Report" option. Is
there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Hi Laura,

One quick point before the smart ones chime in: you can always save mid-way
by swiping backward to the last question (which, by definition, must have
been either answered or not required).

Best,

Chris

··· On Monday, February 13, 2012, Laura Costica wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is about
    the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try to do
    that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle evelyn@ehealthnigeria.orgwrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had the
upgraded Android version (Gingerbread). The phones that are not working are
still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot of
information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen but
    the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.com wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello
<

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes to
sleep. When you wake it up by pressing the centre button on the phone, you
see the ODK main menu and your form is not under "Edit saved form" or "Send
Finalized Form". There is no error whatsoever. This doesn't happen when I
keep touching the screen as it's saving to prevent it from going to sleep;
in this case it actually saves.

As for saving before the end, see my previous reply to Christopher. That
lead to a crash and I copied the stack trace for it. I've also attached the
log of the crash to this email.

Thanks for your help,
Laura

alogcat.2012-02-13-17-21-56+0100.txt (6.7 KB)

··· On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung wrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with the
options to "wait" and "force close"? Or does it just give you a message
that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday with
a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica laura.costica@gmail.comwrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try to
    do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle <evelyn@ehealthnigeria.org wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had
the upgraded Android version (Gingerbread). The phones that are not working
are still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot of
information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen but
    the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.com wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions, where
each

question has at least 5 logic requirements applied to it. I have the
entire

form working fine on my Nexus One Android phone. However, our client
is

testing the form on a Samsung Galaxy Mini and they are encountering
an error

at the very end of the survey.
They say that once the entire form is filled out and they reach the
last

screen (where you click the "Mark as Finished" button) and click the
"Save"

button, the phone says "...saving" and then either Force Closes or
just goes

back to the home menu (once here, the form can not be found on the
phone at

all).
I have tried the form multiple times to see if I can recreate the
error,

which I can't. Is it possible that the phone they are using doesn't
have

enough processing power or memory to process such a long form? Has
anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone when
ODK

force closes, our client says there there is no "Report" option. Is
there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Hi Christopher,

You're right. It wasn't possible in the older 1.1.7 RC2 version, but I
upgraded it a few days ago. I tried that and it worked up until the first
loop. After the loop (a birth table), I tried saving again and it crashed.
The Stack trace says:

java.lang.RuntimeException: An error occured while executing
doInBackground()
at android.os.AsyncTask$3.don(AsyncTask.java:200)
at
java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
at java.util.concurrent.FutureTask$Sync,innerRun(FutureTask.java:307)
at java.util.concurrent.FutureTask.run(FutureTask.java:137)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java.1068)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:561)
at java.lang.Thread.run(Thread.java:1096)
Caused by: java.lang.NullPointerException at
org.javarosa.core.model.FormDef.canCreateRepeat(FormDef.java:343)
at
org.javarosa.form.api.FormEntryModel.isIndexRelevant(FormEntryModel.java:387)
at
org.javarosa.form.api.FormEntryController.stepEvent(FormEntryController.java:198)
at
org.javarosa.form.api.FormEntryController.stepToNextEvent(FormEntryController.java:169)
at
org.odk.collect.android.logic.FormController.stepToNextEvent(FormController.java:287)
at
org.odk.collect.android.tasks.SaveToDiskTask.validateAnswers(SaveToDiskTask.java:264)
at
org.odk.collect.android.tasks.SaveToDiskTask.doInBackground(SaveToDiskTask.java:80)
at
org.odk.collect.android.tasks.SaveToDiskTask.doInBackground(SaveToDiskTask.java:1)
at android.os.AsyncTask$2(AsyncTask.java:185
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
...4more

Other info:
Exception class name: java-lang.NullPointerException
Source file: FormDef.Java
Source class: org.javarosa.core.model.FormDef
Source method: canCreateRepeat
Line number: 343

Laura

··· On Mon, Feb 13, 2012 at 4:36 PM, Christopher Robert < chris_robert@hksphd.harvard.edu> wrote:

Hi Laura,

One quick point before the smart ones chime in: you can always save
mid-way by swiping backward to the last question (which, by definition,
must have been either answered or not required).

Best,

Chris

On Monday, February 13, 2012, Laura Costica wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try to
    do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle <evelyn@ehealthnigeria.org wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had the
upgraded Android version (Gingerbread). The phones that are not working are
still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot of
information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen but
    the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.com wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello
<

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

I looked into this more and there were two separate bugs.

The first was a race condition when the screen fell asleep during a save.
This has been resolved and a new version of 1.1.7 has been pushed to
market and updated in the downloads section of our website.

The second was that the form used "jr:count=" for a repeat and referenced a
node that had no answer entered when the user tried to save. This is
actually a bug in javarosa. The workaround is to make that group relevant
only if the node referenced by jr:count is greater than 0. the relevance
check properly handles the empty answer case, jr:count does not. This bug
also causes a crash when trying to use the "jump to" feature, and the
workaround also fixes the "jump to" case.
-Carl

··· On Mon, Feb 13, 2012 at 10:02 AM, Laura Costica wrote:

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes to
sleep. When you wake it up by pressing the centre button on the phone, you
see the ODK main menu and your form is not under "Edit saved form" or "Send
Finalized Form". There is no error whatsoever. This doesn't happen when I
keep touching the screen as it's saving to prevent it from going to sleep;
in this case it actually saves.

As for saving before the end, see my previous reply to Christopher. That
lead to a crash and I copied the stack trace for it. I've also attached the
log of the crash to this email.

Thanks for your help,
Laura

On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung carlhartung@gmail.comwrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with the
options to "wait" and "force close"? Or does it just give you a message
that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday
with a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica laura.costica@gmail.comwrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try to
    do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had
the upgraded Android version (Gingerbread). The phones that are not working
are still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot of
information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen but
    the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.com wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions, where
each

question has at least 5 logic requirements applied to it. I have
the entire

form working fine on my Nexus One Android phone. However, our
client is

testing the form on a Samsung Galaxy Mini and they are encountering
an error

at the very end of the survey.
They say that once the entire form is filled out and they reach the
last

screen (where you click the "Mark as Finished" button) and click
the "Save"

button, the phone says "...saving" and then either Force Closes or
just goes

back to the home menu (once here, the form can not be found on the
phone at

all).
I have tried the form multiple times to see if I can recreate the
error,

which I can't. Is it possible that the phone they are using doesn't
have

enough processing power or memory to process such a long form? Has
anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone when
ODK

force closes, our client says there there is no "Report" option. Is
there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Hi everyone,

Thanks Carl, I downloaded the new version from
herehttp://code.google.com/p/opendatakit/downloads/detail?name=ODK%20Collect%20v1.1.7.apk&can=2&q=.
The one on the Android
markethttps://market.android.com/details?id=org.odk.collect.android&feature=search_result#?t=W251bGwsMSwxLDEsIm9yZy5vZGsuY29sbGVjdC5hbmRyb2lkIl0.is
from 8th Feb. The time out issue seems to have been resolved.

However, I am having another problem now. If I start filling out a survey
and after a few questions I go the desktop, leaving ODK open, when I go
back to it, it re-loads ODK, returning to its main menu without saving. The
enumerators do this very often, accidentally pressing the centre button on
the phone, being returned to the desktop. Normally, pressing the ODK icon
on the desktop should get them back where they were in the survey, but
that's not the case now.

I've attached a log of the this issue. Could Carl or someone else who has
time look into this?

Thanks,
Laura

alogcat.2012-02-15-13-40-57+0100.txt (36.1 KB)

··· On Wed, Feb 15, 2012 at 12:13 AM, Carl Hartung wrote:

I looked into this more and there were two separate bugs.

The first was a race condition when the screen fell asleep during a save.
This has been resolved and a new version of 1.1.7 has been pushed to
market and updated in the downloads section of our website.

The second was that the form used "jr:count=" for a repeat and referenced
a node that had no answer entered when the user tried to save. This is
actually a bug in javarosa. The workaround is to make that group relevant
only if the node referenced by jr:count is greater than 0. the relevance
check properly handles the empty answer case, jr:count does not. This bug
also causes a crash when trying to use the "jump to" feature, and the
workaround also fixes the "jump to" case.
-Carl

On Mon, Feb 13, 2012 at 10:02 AM, Laura Costica laura.costica@gmail.comwrote:

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes to
sleep. When you wake it up by pressing the centre button on the phone, you
see the ODK main menu and your form is not under "Edit saved form" or "Send
Finalized Form". There is no error whatsoever. This doesn't happen when I
keep touching the screen as it's saving to prevent it from going to sleep;
in this case it actually saves.

As for saving before the end, see my previous reply to Christopher. That
lead to a crash and I copied the stack trace for it. I've also attached the
log of the crash to this email.

Thanks for your help,
Laura

On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung carlhartung@gmail.comwrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with the
options to "wait" and "force close"? Or does it just give you a message
that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday
with a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica laura.costica@gmail.comwrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try to
    do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had
the upgraded Android version (Gingerbread). The phones that are not working
are still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot
of information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen
    but the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.
java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.com wrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace or
log after an Android "Force Close"" we have instructions on how to get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe the
version of Android on the phone, the version of collect and attach the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions, where
each

question has at least 5 logic requirements applied to it. I have
the entire

form working fine on my Nexus One Android phone. However, our
client is

testing the form on a Samsung Galaxy Mini and they are
encountering an error

at the very end of the survey.
They say that once the entire form is filled out and they reach
the last

screen (where you click the "Mark as Finished" button) and click
the "Save"

button, the phone says "...saving" and then either Force Closes or
just goes

back to the home menu (once here, the form can not be found on the
phone at

all).
I have tried the form multiple times to see if I can recreate the
error,

which I can't. Is it possible that the phone they are using
doesn't have

enough processing power or memory to process such a long form? Has
anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone
when ODK

force closes, our client says there there is no "Report" option.
Is there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Laura,

Can you verify that this happens consistently?

I've seen this happen during development where an application is launched
some way other than by clicking on it with your finger. In that case, when
you hit "home" and then try to open the application by clicking on it,
Android doesn't recognize that the app is already open and starts a new
instance (even though Collect is configured to only have one instance
running). Pressing "back" at the main menu should take you to your
partially completed form. I'd recommend at that point pressing back until
ODK completely exists and start again. I've never seen that problem happen
other than on the first load.

-Carl

··· On Wed, Feb 15, 2012 at 4:54 AM, Laura Costica wrote:

Hi everyone,

Thanks Carl, I downloaded the new version from herehttp://code.google.com/p/opendatakit/downloads/detail?name=ODK%20Collect%20v1.1.7.apk&can=2&q=.
The one on the Android markethttps://market.android.com/details?id=org.odk.collect.android&feature=search_result#?t=W251bGwsMSwxLDEsIm9yZy5vZGsuY29sbGVjdC5hbmRyb2lkIl0.is from 8th Feb. The time out issue seems to have been resolved.

However, I am having another problem now. If I start filling out a survey
and after a few questions I go the desktop, leaving ODK open, when I go
back to it, it re-loads ODK, returning to its main menu without saving. The
enumerators do this very often, accidentally pressing the centre button on
the phone, being returned to the desktop. Normally, pressing the ODK icon
on the desktop should get them back where they were in the survey, but
that's not the case now.

I've attached a log of the this issue. Could Carl or someone else who has
time look into this?

Thanks,
Laura

On Wed, Feb 15, 2012 at 12:13 AM, Carl Hartung carlhartung@gmail.comwrote:

I looked into this more and there were two separate bugs.

The first was a race condition when the screen fell asleep during a save.
This has been resolved and a new version of 1.1.7 has been pushed to
market and updated in the downloads section of our website.

The second was that the form used "jr:count=" for a repeat and referenced
a node that had no answer entered when the user tried to save. This is
actually a bug in javarosa. The workaround is to make that group relevant
only if the node referenced by jr:count is greater than 0. the relevance
check properly handles the empty answer case, jr:count does not. This bug
also causes a crash when trying to use the "jump to" feature, and the
workaround also fixes the "jump to" case.
-Carl

On Mon, Feb 13, 2012 at 10:02 AM, Laura Costica laura.costica@gmail.comwrote:

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes to
sleep. When you wake it up by pressing the centre button on the phone, you
see the ODK main menu and your form is not under "Edit saved form" or "Send
Finalized Form". There is no error whatsoever. This doesn't happen when I
keep touching the screen as it's saving to prevent it from going to sleep;
in this case it actually saves.

As for saving before the end, see my previous reply to Christopher. That
lead to a crash and I copied the stack trace for it. I've also attached the
log of the crash to this email.

Thanks for your help,
Laura

On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung carlhartung@gmail.comwrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with
the options to "wait" and "force close"? Or does it just give you a
message that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday
with a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica <laura.costica@gmail.com wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try
    to do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had
the upgraded Android version (Gingerbread). The phones that are not working
are still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot
of information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen
    but the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.
java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.comwrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the
first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace
or
log after an Android "Force Close"" we have instructions on how to
get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini
at
http://code.google.com/p/opendatakit/issues/list. Please describe
the
version of Android on the phone, the version of collect and attach
the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions,
where each

question has at least 5 logic requirements applied to it. I have
the entire

form working fine on my Nexus One Android phone. However, our
client is

testing the form on a Samsung Galaxy Mini and they are
encountering an error

at the very end of the survey.
They say that once the entire form is filled out and they reach
the last

screen (where you click the "Mark as Finished" button) and click
the "Save"

button, the phone says "...saving" and then either Force Closes
or just goes

back to the home menu (once here, the form can not be found on
the phone at

all).
I have tried the form multiple times to see if I can recreate the
error,

which I can't. Is it possible that the phone they are using
doesn't have

enough processing power or memory to process such a long form?
Has anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone
when ODK

force closes, our client says there there is no "Report" option.
Is there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Laura,
I verified that this behavior also occurs when you install a non-market
source and hit "open" at the last install screen, so I'm guessing that's
the issue. Rebooting or opening ODK and hitting "back" until you're at the
desktop will restore the normal behavior.
-Carl

··· On Wed, Feb 15, 2012 at 9:00 AM, Carl Hartung wrote:

Laura,

Can you verify that this happens consistently?

I've seen this happen during development where an application is launched
some way other than by clicking on it with your finger. In that case, when
you hit "home" and then try to open the application by clicking on it,
Android doesn't recognize that the app is already open and starts a new
instance (even though Collect is configured to only have one instance
running). Pressing "back" at the main menu should take you to your
partially completed form. I'd recommend at that point pressing back until
ODK completely exists and start again. I've never seen that problem happen
other than on the first load.

-Carl

On Wed, Feb 15, 2012 at 4:54 AM, Laura Costica laura.costica@gmail.comwrote:

Hi everyone,

Thanks Carl, I downloaded the new version from herehttp://code.google.com/p/opendatakit/downloads/detail?name=ODK%20Collect%20v1.1.7.apk&can=2&q=.
The one on the Android markethttps://market.android.com/details?id=org.odk.collect.android&feature=search_result#?t=W251bGwsMSwxLDEsIm9yZy5vZGsuY29sbGVjdC5hbmRyb2lkIl0.is from 8th Feb. The time out issue seems to have been resolved.

However, I am having another problem now. If I start filling out a survey
and after a few questions I go the desktop, leaving ODK open, when I go
back to it, it re-loads ODK, returning to its main menu without saving. The
enumerators do this very often, accidentally pressing the centre button on
the phone, being returned to the desktop. Normally, pressing the ODK icon
on the desktop should get them back where they were in the survey, but
that's not the case now.

I've attached a log of the this issue. Could Carl or someone else who has
time look into this?

Thanks,
Laura

On Wed, Feb 15, 2012 at 12:13 AM, Carl Hartung carlhartung@gmail.comwrote:

I looked into this more and there were two separate bugs.

The first was a race condition when the screen fell asleep during a
save. This has been resolved and a new version of 1.1.7 has been pushed to
market and updated in the downloads section of our website.

The second was that the form used "jr:count=" for a repeat and
referenced a node that had no answer entered when the user tried to save.
This is actually a bug in javarosa. The workaround is to make that group
relevant only if the node referenced by jr:count is greater than 0. the
relevance check properly handles the empty answer case, jr:count does not.
This bug also causes a crash when trying to use the "jump to" feature, and
the workaround also fixes the "jump to" case.
-Carl

On Mon, Feb 13, 2012 at 10:02 AM, Laura Costica <laura.costica@gmail.com wrote:

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes to
sleep. When you wake it up by pressing the centre button on the phone, you
see the ODK main menu and your form is not under "Edit saved form" or "Send
Finalized Form". There is no error whatsoever. This doesn't happen when I
keep touching the screen as it's saving to prevent it from going to sleep;
in this case it actually saves.

As for saving before the end, see my previous reply to Christopher.
That lead to a crash and I copied the stack trace for it. I've also
attached the log of the crash to this email.

Thanks for your help,
Laura

On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung carlhartung@gmail.comwrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with
the options to "wait" and "force close"? Or does it just give you a
message that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday
with a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica < laura.costica@gmail.com> wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try
    to do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on
had the upgraded Android version (Gingerbread). The phones that are not
working are still running 2.2.1. When I tried the form with the upgraded
version of Android, I was able to save the form fine and was not able to
recreate their error. However, on the Galaxy Mini, it took over a minute
for the form to load.

The error is only occurring when the survey is filled out with a lot
of information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen
    but the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.
java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.comwrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you
see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the
first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace
or
log after an Android "Force Close"" we have instructions on how to
get
a log of exactly where the phone crashed. Follow those steps and
post
the trace and a description of how it was caused on the Galaxy Mini
at
http://code.google.com/p/opendatakit/issues/list. Please describe
the
version of Android on the phone, the version of collect and attach
the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions,
where each

question has at least 5 logic requirements applied to it. I have
the entire

form working fine on my Nexus One Android phone. However, our
client is

testing the form on a Samsung Galaxy Mini and they are
encountering an error

at the very end of the survey.
They say that once the entire form is filled out and they reach
the last

screen (where you click the "Mark as Finished" button) and click
the "Save"

button, the phone says "...saving" and then either Force Closes
or just goes

back to the home menu (once here, the form can not be found on
the phone at

all).
I have tried the form multiple times to see if I can recreate
the error,

which I can't. Is it possible that the phone they are using
doesn't have

enough processing power or memory to process such a long form?
Has anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone
when ODK

force closes, our client says there there is no "Report" option.
Is there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

Hi Carl,

Rebooting solved the problem. Thanks!

Laura

··· On Wed, Feb 15, 2012 at 6:43 PM, Carl Hartung wrote:

Laura,
I verified that this behavior also occurs when you install a non-market
source and hit "open" at the last install screen, so I'm guessing that's
the issue. Rebooting or opening ODK and hitting "back" until you're at the
desktop will restore the normal behavior.
-Carl

On Wed, Feb 15, 2012 at 9:00 AM, Carl Hartung carlhartung@gmail.comwrote:

Laura,

Can you verify that this happens consistently?

I've seen this happen during development where an application is launched
some way other than by clicking on it with your finger. In that case, when
you hit "home" and then try to open the application by clicking on it,
Android doesn't recognize that the app is already open and starts a new
instance (even though Collect is configured to only have one instance
running). Pressing "back" at the main menu should take you to your
partially completed form. I'd recommend at that point pressing back until
ODK completely exists and start again. I've never seen that problem happen
other than on the first load.

-Carl

On Wed, Feb 15, 2012 at 4:54 AM, Laura Costica laura.costica@gmail.comwrote:

Hi everyone,

Thanks Carl, I downloaded the new version from herehttp://code.google.com/p/opendatakit/downloads/detail?name=ODK%20Collect%20v1.1.7.apk&can=2&q=.
The one on the Android markethttps://market.android.com/details?id=org.odk.collect.android&feature=search_result#?t=W251bGwsMSwxLDEsIm9yZy5vZGsuY29sbGVjdC5hbmRyb2lkIl0.is from 8th Feb. The time out issue seems to have been resolved.

However, I am having another problem now. If I start filling out a
survey and after a few questions I go the desktop, leaving ODK open, when I
go back to it, it re-loads ODK, returning to its main menu without saving.
The enumerators do this very often, accidentally pressing the centre button
on the phone, being returned to the desktop. Normally, pressing the ODK
icon on the desktop should get them back where they were in the survey, but
that's not the case now.

I've attached a log of the this issue. Could Carl or someone else who
has time look into this?

Thanks,
Laura

On Wed, Feb 15, 2012 at 12:13 AM, Carl Hartung carlhartung@gmail.comwrote:

I looked into this more and there were two separate bugs.

The first was a race condition when the screen fell asleep during a
save. This has been resolved and a new version of 1.1.7 has been pushed to
market and updated in the downloads section of our website.

The second was that the form used "jr:count=" for a repeat and
referenced a node that had no answer entered when the user tried to save.
This is actually a bug in javarosa. The workaround is to make that group
relevant only if the node referenced by jr:count is greater than 0. the
relevance check properly handles the empty answer case, jr:count does not.
This bug also causes a crash when trying to use the "jump to" feature, and
the workaround also fixes the "jump to" case.
-Carl

On Mon, Feb 13, 2012 at 10:02 AM, Laura Costica < laura.costica@gmail.com> wrote:

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes
to sleep. When you wake it up by pressing the centre button on the phone,
you see the ODK main menu and your form is not under "Edit saved form" or
"Send Finalized Form". There is no error whatsoever. This doesn't happen
when I keep touching the screen as it's saving to prevent it from going to
sleep; in this case it actually saves.

As for saving before the end, see my previous reply to Christopher.
That lead to a crash and I copied the stack trace for it. I've also
attached the log of the crash to this email.

Thanks for your help,
Laura

On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung carlhartung@gmail.comwrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with
the options to "wait" and "force close"? Or does it just give you a
message that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday
with a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but
there appears to be some information missing. The error in the logs seems
to indicate that your logo file is unreadable (either corrupt or not a
.png), but that shouldn't have anything to do with saving... and it
shouldn't cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica < laura.costica@gmail.com> wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving,
    not letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try
    to do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on
had the upgraded Android version (Gingerbread). The phones that are not
working are still running 2.2.1. When I tried the form with the upgraded
version of Android, I was able to save the form fine and was not able to
recreate their error. However, on the Galaxy Mini, it took over a minute
for the form to load.

The error is only occurring when the survey is filled out with a
lot of information. So if they fill out only a few questions and then save
the form, it will save and can be uploaded. However, if they fill out the
form completely (say with 10 children's information, aka. a ton of data),
then when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen
    but the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.
java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.comwrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you
see
power and memory issues when the form is loading the first time,
but
not on save.

Does the problem happen when they save using the menu on say the
first
prompt? Or the last prompt? What happens if you reboot the phone
and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack
trace or
log after an Android "Force Close"" we have instructions on how to
get
a log of exactly where the phone crashed. Follow those steps and
post
the trace and a description of how it was caused on the Galaxy
Mini at
http://code.google.com/p/opendatakit/issues/list. Please describe
the
version of Android on the phone, the version of collect and attach
the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be
as simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions,
where each

question has at least 5 logic requirements applied to it. I
have the entire

form working fine on my Nexus One Android phone. However, our
client is

testing the form on a Samsung Galaxy Mini and they are
encountering an error

at the very end of the survey.
They say that once the entire form is filled out and they reach
the last

screen (where you click the "Mark as Finished" button) and
click the "Save"

button, the phone says "...saving" and then either Force Closes
or just goes

back to the home menu (once here, the form can not be found on
the phone at

all).
I have tried the form multiple times to see if I can recreate
the error,

which I can't. Is it possible that the phone they are using
doesn't have

enough processing power or memory to process such a long form?
Has anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone
when ODK

force closes, our client says there there is no "Report"
option. Is there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

I don't know if it will act differently, but ask the enumerator, once in
the main menu to hold down for 3 seconds on the center button. This should
bring up a list of currently running applications. Then have them click on
ODK. It's worth a try.
Curtis

··· On Wed, Feb 15, 2012 at 1:54 PM, Laura Costica wrote:

Hi everyone,

Thanks Carl, I downloaded the new version from herehttp://code.google.com/p/opendatakit/downloads/detail?name=ODK%20Collect%20v1.1.7.apk&can=2&q=.
The one on the Android markethttps://market.android.com/details?id=org.odk.collect.android&feature=search_result#?t=W251bGwsMSwxLDEsIm9yZy5vZGsuY29sbGVjdC5hbmRyb2lkIl0.is from 8th Feb. The time out issue seems to have been resolved.

However, I am having another problem now. If I start filling out a survey
and after a few questions I go the desktop, leaving ODK open, when I go
back to it, it re-loads ODK, returning to its main menu without saving. The
enumerators do this very often, accidentally pressing the centre button on
the phone, being returned to the desktop. Normally, pressing the ODK icon
on the desktop should get them back where they were in the survey, but
that's not the case now.

I've attached a log of the this issue. Could Carl or someone else who has
time look into this?

Thanks,
Laura

On Wed, Feb 15, 2012 at 12:13 AM, Carl Hartung carlhartung@gmail.comwrote:

I looked into this more and there were two separate bugs.

The first was a race condition when the screen fell asleep during a save.
This has been resolved and a new version of 1.1.7 has been pushed to
market and updated in the downloads section of our website.

The second was that the form used "jr:count=" for a repeat and referenced
a node that had no answer entered when the user tried to save. This is
actually a bug in javarosa. The workaround is to make that group relevant
only if the node referenced by jr:count is greater than 0. the relevance
check properly handles the empty answer case, jr:count does not. This bug
also causes a crash when trying to use the "jump to" feature, and the
workaround also fixes the "jump to" case.
-Carl

On Mon, Feb 13, 2012 at 10:02 AM, Laura Costica laura.costica@gmail.comwrote:

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes to
sleep. When you wake it up by pressing the centre button on the phone, you
see the ODK main menu and your form is not under "Edit saved form" or "Send
Finalized Form". There is no error whatsoever. This doesn't happen when I
keep touching the screen as it's saving to prevent it from going to sleep;
in this case it actually saves.

As for saving before the end, see my previous reply to Christopher. That
lead to a crash and I copied the stack trace for it. I've also attached the
log of the crash to this email.

Thanks for your help,
Laura

On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung carlhartung@gmail.comwrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with
the options to "wait" and "force close"? Or does it just give you a
message that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday
with a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica <laura.costica@gmail.com wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try
    to do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on had
the upgraded Android version (Gingerbread). The phones that are not working
are still running 2.2.1. When I tried the form with the upgraded version of
Android, I was able to save the form fine and was not able to recreate
their error. However, on the Galaxy Mini, it took over a minute for the
form to load.

The error is only occurring when the survey is filled out with a lot
of information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen
    but the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.
java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.comwrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the
first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace
or
log after an Android "Force Close"" we have instructions on how to
get
a log of exactly where the phone crashed. Follow those steps and post
the trace and a description of how it was caused on the Galaxy Mini
at
http://code.google.com/p/opendatakit/issues/list. Please describe
the
version of Android on the phone, the version of collect and attach
the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions,
where each

question has at least 5 logic requirements applied to it. I have
the entire

form working fine on my Nexus One Android phone. However, our
client is

testing the form on a Samsung Galaxy Mini and they are
encountering an error

at the very end of the survey.
They say that once the entire form is filled out and they reach
the last

screen (where you click the "Mark as Finished" button) and click
the "Save"

button, the phone says "...saving" and then either Force Closes
or just goes

back to the home menu (once here, the form can not be found on
the phone at

all).
I have tried the form multiple times to see if I can recreate the
error,

which I can't. Is it possible that the phone they are using
doesn't have

enough processing power or memory to process such a long form?
Has anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone
when ODK

force closes, our client says there there is no "Report" option.
Is there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--

Curtis BRODERICK
Head of training and user support
Tél : + 33(0)1.53.02.40.61 06.15.33.57.37

---------------------------EpiConcept---------------------------
Systèmes d'Information en Santé
Health Information System
47, rue de Charenton - 75012 PARIS
Tel : +33 (0)1 53 02 40 60 Fax : +33 (0)1 53 02 40 62
-----------------------www.epiconcept.fr------------------------

Ce message et toutes les pièces jointes sont établis à l'intention
exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur, merci de le détruire et d'en
avertir l'expéditeur.

The information contained in the Email and any attachments is
confidential and intended solely and for the attention and use of the
named address(es). It may not be disclosed to any other person without
the express authority of EpiConcept, or the intended recipient, or
both.
If you are not the intended recipient, you must not disclose, copy,
distribute or retain this message or any part of it.

Hi Curtis,

This issue was resolved by rebooting the form. Apparently it happens when
you download applications from non-market sources.

The survey works perfectly now. I'm as pleased as punch :).

Laura

··· On Thu, Feb 16, 2012 at 9:43 AM, Curtis Broderick <c.broderick@epiconcept.fr wrote:

I don't know if it will act differently, but ask the enumerator, once in
the main menu to hold down for 3 seconds on the center button. This should
bring up a list of currently running applications. Then have them click on
ODK. It's worth a try.
Curtis

On Wed, Feb 15, 2012 at 1:54 PM, Laura Costica laura.costica@gmail.comwrote:

Hi everyone,

Thanks Carl, I downloaded the new version from herehttp://code.google.com/p/opendatakit/downloads/detail?name=ODK%20Collect%20v1.1.7.apk&can=2&q=.
The one on the Android markethttps://market.android.com/details?id=org.odk.collect.android&feature=search_result#?t=W251bGwsMSwxLDEsIm9yZy5vZGsuY29sbGVjdC5hbmRyb2lkIl0.is from 8th Feb. The time out issue seems to have been resolved.

However, I am having another problem now. If I start filling out a survey
and after a few questions I go the desktop, leaving ODK open, when I go
back to it, it re-loads ODK, returning to its main menu without saving. The
enumerators do this very often, accidentally pressing the centre button on
the phone, being returned to the desktop. Normally, pressing the ODK icon
on the desktop should get them back where they were in the survey, but
that's not the case now.

I've attached a log of the this issue. Could Carl or someone else who has
time look into this?

Thanks,
Laura

On Wed, Feb 15, 2012 at 12:13 AM, Carl Hartung carlhartung@gmail.comwrote:

I looked into this more and there were two separate bugs.

The first was a race condition when the screen fell asleep during a
save. This has been resolved and a new version of 1.1.7 has been pushed to
market and updated in the downloads section of our website.

The second was that the form used "jr:count=" for a repeat and
referenced a node that had no answer entered when the user tried to save.
This is actually a bug in javarosa. The workaround is to make that group
relevant only if the node referenced by jr:count is greater than 0. the
relevance check properly handles the empty answer case, jr:count does not.
This bug also causes a crash when trying to use the "jump to" feature, and
the workaround also fixes the "jump to" case.
-Carl

On Mon, Feb 13, 2012 at 10:02 AM, Laura Costica <laura.costica@gmail.com wrote:

Hi Carl,

By "times out" I mean it keeps wanting to save until the screen goes to
sleep. When you wake it up by pressing the centre button on the phone, you
see the ODK main menu and your form is not under "Edit saved form" or "Send
Finalized Form". There is no error whatsoever. This doesn't happen when I
keep touching the screen as it's saving to prevent it from going to sleep;
in this case it actually saves.

As for saving before the end, see my previous reply to Christopher.
That lead to a crash and I copied the stack trace for it. I've also
attached the log of the crash to this email.

Thanks for your help,
Laura

On Mon, Feb 13, 2012 at 6:43 PM, Carl Hartung carlhartung@gmail.comwrote:

Hi Laura,

For #1, when you say "times out". Does Android pop up a dialog with
the options to "wait" and "force close"? Or does it just give you a
message that the program has stopped/crashed and only the option of "ok"?

For #4, we just updated 1.1.7 on the market and website last Thursday
with a fix for the "response required" bug, so you can now save mid-way.
Android should've alerted you to the update, but if not you can install it
manually.

There's definitely something strange going on in those logs, but there
appears to be some information missing. The error in the logs seems to
indicate that your logo file is unreadable (either corrupt or not a .png),
but that shouldn't have anything to do with saving... and it shouldn't
cause a crash.

You might want to make sure this file is good, or delete it:
/mnt/sdcard/odk/forms/JPAL Basline Feb10-media/form_logo.png

On Mon, Feb 13, 2012 at 7:31 AM, Laura Costica < laura.costica@gmail.com> wrote:

Hi everyone,

I'm the one on whose phone these errors happen. A few clarifications:

  1. I've tried it on several Galaxy Minis SG-5570 3. Model Number:
    GT-S5570. The problem is consistent: when a full survey is entered
    (meaning that no large skips are made), it times out when saving.
  2. Interestingly, when I keep touching the screen as it's saving, not
    letting it go to sleep, it ends up saving.
  3. The second log attached (alogcat.2012-02-13-15-27-38+0100.txt) is
    about the same crash described in the Stack Trace info.
  4. It's not possible to save the form at any point mid-way. If I try
    to do that it says "Response required". 99% of the questions are required.

Any ideas of what could be causing this instability?

Thanks,
Laura

On Mon, Feb 13, 2012 at 3:58 PM, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi Yaw and Gaetano,

Unfortunately, the only Galaxy Mini that I was able to test it on
had the upgraded Android version (Gingerbread). The phones that are not
working are still running 2.2.1. When I tried the form with the upgraded
version of Android, I was able to save the form fine and was not able to
recreate their error. However, on the Galaxy Mini, it took over a minute
for the form to load.

The error is only occurring when the survey is filled out with a lot
of information. So if they fill out only a few questions and then save the
form, it will save and can be uploaded. However, if they fill out the form
completely (say with 10 children's information, aka. a ton of data), then
when they try to save the form, one of 2 things happen.

  1. the form says it is saving and then goes back to the home screen
    but the form is not in the "send finalized forms" section or "edit saved
    forms" section
  2. The application force closes

Here is the stack trace from one of the times the application force
closed:

java.lang.RuntimeException: Unable to pause activity
{org.odk.collect.android/org.odk.collect.android.
activities.FormEntryActicity}:
java.lang.ClassCaseException: android.view.View
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3354)
at android.app.ActivityThread.performPauseActivity(
ActivityThread.java:3311)
at android.app.ActivityThread.handlePauseActivity(
ActivityThread.java:3294)
at android.app.ActivityThread.access$2500(ActivityThread.java:126)
at android.app.ActivityThread$H.handleMessage(ActivityThread.
java:2049)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4633)
at java.lang.reflext.Method.invokeNative(Native Method)
at java.lang.reflect.Medhod.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit(MethodAndArgsCaller.run(
ZygoteInit.java:858)

Also attached to this email (also made an issue herehttp://code.google.com/p/opendatakit/issues/detail?id=515&thanks=515&ts=1329145069)
are the logs from when the survey just returned to the home screen.

Thanks,
Evelyn

On Sat, Feb 11, 2012 at 4:25 PM, Yaw Anokwa yanokwa@gmail.comwrote:

Evelyn,

Agreed with Gaetano. This could be a device issue. Generally, you
see
power and memory issues when the form is loading the first time, but
not on save.

Does the problem happen when they save using the menu on say the
first
prompt? Or the last prompt? What happens if you reboot the phone and
try the last screen. Does it crash then?

The lack of a Report button has to do with the build of Android on
that phone. Some phones have it, others don't. In
http://opendatakit.org/help/faq/ under "How do I get a stack trace
or
log after an Android "Force Close"" we have instructions on how to
get
a log of exactly where the phone crashed. Follow those steps and
post
the trace and a description of how it was caused on the Galaxy Mini
at
http://code.google.com/p/opendatakit/issues/list. Please describe
the
version of Android on the phone, the version of collect and attach
the
form there. We'll try to reproduce it on our least powerful device.

Yaw

On Fri, Feb 10, 2012 at 11:52, Gaetano Borriello gaetano@cs.washington.edu wrote:

Have you reproduced this on a second galaxy mini? It could be as
simple as
a bad SD card.

On Friday, February 10, 2012, Evelyn Castle < evelyn@ehealthnigeria.org> wrote:

Hi All,
I have finished creating a form that is about 500 questions,
where each

question has at least 5 logic requirements applied to it. I have
the entire

form working fine on my Nexus One Android phone. However, our
client is

testing the form on a Samsung Galaxy Mini and they are
encountering an error

at the very end of the survey.
They say that once the entire form is filled out and they reach
the last

screen (where you click the "Mark as Finished" button) and click
the "Save"

button, the phone says "...saving" and then either Force Closes
or just goes

back to the home menu (once here, the form can not be found on
the phone at

all).
I have tried the form multiple times to see if I can recreate
the error,

which I can't. Is it possible that the phone they are using
doesn't have

enough processing power or memory to process such a long form?
Has anyone

ever experienced a problem like this before?
Another problem we are having is that on the Galaxy Mini phone
when ODK

force closes, our client says there there is no "Report" option.
Is there an

option to turn this on/off somehow?
Thanks
Evelyn

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Evelyn Castle
Director, eHealth Nigeria
www.eHealthNigeria.org
25 Race Course Road, Kano, Ng
mobile: (NG) 0809-515-0585
(NG) 0813-883-2395
(US) 714-721-3157

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en

--

Curtis BRODERICK
Head of training and user support

Tél : + 33(0)1.53.02.40.61 06.15.33.57.37

---------------------------EpiConcept---------------------------
Systèmes d'Information en Santé

                Health Information System

           47, rue de Charenton - 75012 PARIS
     Tel : +33 (0)1 53 02 40 60  Fax : +33 (0)1 53 02 40 62

-----------------------www.epiconcept.fr------------------------

Ce message et toutes les pièces jointes sont établis à l'intention exclusive de ses destinataires et sont confidentiels.
Si vous recevez ce message par erreur, merci de le détruire et d'en avertir l'expéditeur.

The information contained in the Email and any attachments is confidential and intended solely and for the attention and use of the
named address(es). It may not be disclosed to any other person without the express authority of EpiConcept, or the intended recipient, or both.

If you are not the intended recipient, you must not disclose, copy, distribute or retain this message or any part of it.

--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en