ODK hangs after the file is about 2MB

Hello there,

Does anyone encounter this issue that if the file is about or more than
2MB, ODK hangs and give the message "ODK Collect is not responding. Would
you like to close it?"? I attached a file for your reference. Thanks so
much for your support.

GSF_Commune_DB.xml (2.28 MB)

Installing a log capture tool is helpful in these situations:
http://code.google.com/p/opendatakit/wiki/CollectTroubleshooting

In this case, I see an "OutOfMemory" error being reported in the log.

Your form is simply too big for ODK Collect to handle.

Your form is not particularly complicated, but you have over 5000 villages
in your list of villages. It is likely that this list is causing the
problem.

I recommend dividing your form into one for each province (I would try
creating one for the largest province first, and seeing if it can be
loaded).

Mitch

··· On Sun, Oct 21, 2012 at 8:15 PM, Chan Choth wrote:

Hello there,

Does anyone encounter this issue that if the file is about or more than
2MB, ODK hangs and give the message "ODK Collect is not responding. Would
you like to close it?"? I attached a file for your reference. Thanks so
much for your support.

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

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Dear Mitch,

I tested with one small province and it was OK. Is there any possibility
that we can link the form especially this location hierarchy? I found this
feature is available for PoiMapper. By the way, I use Samsung Galaxy S2 and
it is still hang and I am concern if the phone which has small capacity
than this might have a lot of problem. If I root the phones, all my phones
will be void from warranty. I hope with ODK version 2 this might be not a
problem, right?

Thanks for your kind assistance and I am looking forward to hearing from
you.

Best regards,
Chan Choth

··· On Monday, October 22, 2012 10:15:13 AM UTC+7, Chan Choth wrote: > > Hello there, > > Does anyone encounter this issue that if the file is about or more than > 2MB, ODK hangs and give the message "ODK Collect is not responding. Would > you like to close it?"? I attached a file for your reference. Thanks so > much for your support. >

Some of the newer phones/tablets with high-resolultion screens should have
an additional 8MB available in the Virtual Machine (24MB vs 16MB).

From this, for Android 2.1:
http://static.googleusercontent.com/external_content/untrusted_dlcp/source.android.com/pt-PT//compatibility/android-2.1-cdd.pdf

3.7. Virtual Machine Compatibility
Device implementations MUST support the full Dalvik Executable (DEX)
bytecode
specification and Dalvik Virtual Machine semantics [Resources, 10].
Device implementations MUST configure Dalvik to allocate at least 16MB of
memory
to each application on devices with screens classified as medium- or
low-density.
Device implementations MUST configure Dalvik to allocate at least 24MB of
memory
to each application on devices with screens classified as high-density.
Note that
device implementations MAY allocate more memory than these figures, but are
not
required to.

And for Android 4.1:
http://static.googleusercontent.com/external_content/untrusted_dlcp/source.android.com/pt-PT//compatibility/android-4.1-cdd.pdf

3.7. Virtual Machine Compatibility
Device implementations MUST support the full Dalvik Executable (DEX)
bytecode specification and Dalvik Virtual
Machine semantics [Resources, 17 ].
Device implementations MUST configure Dalvik to allocate memory in
accordance with the upstream Android
platform, and as specified by the following table. (See Section 7.1.1 for
screen size and screen density definitions.)
Note that memory values specified below are considered minimum values, and
device implementations MAY
allocate more memory per application.
Screen Size Screen Density Application Memory
small / normal / large ldpi / mdpi 16MB
small / normal / large tvdpi / hdpi 32MB
small / normal / large xhdpi 64MB
xlarge mdpi 32MB
xlarge tvdpi / hdpi 64MB
xlarge xhdpi 128MB

··· ------------- If you have older devices you can root, and have the technical resources, you can change these too:

Mitch

On Mon, Oct 22, 2012 at 11:04 AM, Mitch S mitchellsundt@gmail.com wrote:

Installing a log capture tool is helpful in these situations:
http://code.google.com/p/opendatakit/wiki/CollectTroubleshooting

In this case, I see an "OutOfMemory" error being reported in the log.

Your form is simply too big for ODK Collect to handle.

Your form is not particularly complicated, but you have over 5000 villages
in your list of villages. It is likely that this list is causing the
problem.

I recommend dividing your form into one for each province (I would try
creating one for the largest province first, and seeing if it can be
loaded).

Mitch

On Sun, Oct 21, 2012 at 8:15 PM, Chan Choth chanchoth@gmail.com wrote:

Hello there,

Does anyone encounter this issue that if the file is about or more than
2MB, ODK hangs and give the message "ODK Collect is not responding. Would
you like to close it?"? I attached a file for your reference. Thanks so
much for your support.

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

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

I don't have a solution in 1.x except to have separate forms for each
province. Anything else would require changing the software.

In ODK 2, the data is stored as rows in a database table, and you will be
able to issue queries on other tables to produce filtered lists of values.

Mitch

··· On Thu, Oct 25, 2012 at 7:10 PM, Chan Choth wrote:

Dear Mitch,

I tested with one small province and it was OK. Is there any possibility
that we can link the form especially this location hierarchy? I found this
feature is available for PoiMapper. By the way, I use Samsung Galaxy S2 and
it is still hang and I am concern if the phone which has small capacity
than this might have a lot of problem. If I root the phones, all my phones
will be void from warranty. I hope with ODK version 2 this might be not a
problem, right?

Thanks for your kind assistance and I am looking forward to hearing from
you.

Best regards,
Chan Choth

On Monday, October 22, 2012 10:15:13 AM UTC+7, Chan Choth wrote:

Hello there,

Does anyone encounter this issue that if the file is about or more than
2MB, ODK hangs and give the message "ODK Collect is not responding. Would
you like to close it?"? I attached a file for your reference. Thanks so
much for your support.

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

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

When is the release date of ODK2? Is it still supporting new cascading
selections?

Thanks,
Chan Choth

··· On Friday, October 26, 2012 10:14:56 AM UTC+7, Mitch wrote: > > I don't have a solution in 1.x except to have separate forms for each > province. Anything else would require changing the software. > > In ODK 2, the data is stored as rows in a database table, and you will be > able to issue queries on other tables to produce filtered lists of values. > > Mitch > > On Thu, Oct 25, 2012 at 7:10 PM, Chan Choth <chan...@gmail.com wrote: > >> Dear Mitch, >> >> I tested with one small province and it was OK. Is there any possibility >> that we can link the form especially this location hierarchy? I found this >> feature is available for PoiMapper. By the way, I use Samsung Galaxy S2 and >> it is still hang and I am concern if the phone which has small capacity >> than this might have a lot of problem. If I root the phones, all my phones >> will be void from warranty. I hope with ODK version 2 this might be not a >> problem, right? >> >> Thanks for your kind assistance and I am looking forward to hearing from >> you. >> >> Best regards, >> Chan Choth >> >> >> On Monday, October 22, 2012 10:15:13 AM UTC+7, Chan Choth wrote: >>> >>> Hello there, >>> >>> Does anyone encounter this issue that if the file is about or more than >>> 2MB, ODK hangs and give the message "ODK Collect is not responding. Would >>> you like to close it?"? I attached a file for your reference. Thanks so >>> much for your support. >>> >> -- >> Post: opend...@googlegroups.com >> Unsubscribe: opendatakit...@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com >

The technology of ODK2 is very very different (it does not use XML, XForms,
or XPath expressions).

But yes, it will have cascading selection support, as it will provide
access to underlying SQLite queries in a simplified form or as raw SQL
expressions (for doing joins across tables in that database). We won't
provide any support for queries across databases.

We are not far enough along to set a release date. The release cycle is as
follows:

(1) limited alpha available 'soon' for the evolving ODK Collect and
XLS2Form pieces -- this will be restricted to the key groups developing
OpenRosa-compatible data collection software. This serves as a concrete
talking point for discussions on where tools built upon HTML5 / JSON / REST
should evolve/change. After we get the major kinks addressed...
(2) public alpha 'before the end of the year.' There will still be many
things in flux, including the structure of the XLS2Form spreadsheet, and
you should not use this alpha in any live deployment -- it is only for
evaluation, bug reporting, and user feedback from the broader community.
Depending upon how the discussions in (1) go, there may be significant
changes to the interoperability layers of the ODK2 system (e.g., redefined
submission interfaces, etc.). This is another reason not to use the alpha
for live deployments.
(3) one or more beta releases and/or release candidates.
(4) official release

Mitch

··· On Tue, Nov 6, 2012 at 7:17 PM, Chan Choth wrote:

When is the release date of ODK2? Is it still supporting new cascading
selections?

Thanks,
Chan Choth

On Friday, October 26, 2012 10:14:56 AM UTC+7, Mitch wrote:

I don't have a solution in 1.x except to have separate forms for each
province. Anything else would require changing the software.

In ODK 2, the data is stored as rows in a database table, and you will be
able to issue queries on other tables to produce filtered lists of values.

Mitch

On Thu, Oct 25, 2012 at 7:10 PM, Chan Choth chan...@gmail.com wrote:

Dear Mitch,

I tested with one small province and it was OK. Is there any possibility
that we can link the form especially this location hierarchy? I found this
feature is available for PoiMapper. By the way, I use Samsung Galaxy S2 and
it is still hang and I am concern if the phone which has small capacity
than this might have a lot of problem. If I root the phones, all my phones
will be void from warranty. I hope with ODK version 2 this might be not a
problem, right?

Thanks for your kind assistance and I am looking forward to hearing from
you.

Best regards,
Chan Choth

On Monday, October 22, 2012 10:15:13 AM UTC+7, Chan Choth wrote:

Hello there,

Does anyone encounter this issue that if the file is about or more than
2MB, ODK hangs and give the message "ODK Collect is not responding. Would
you like to close it?"? I attached a file for your reference. Thanks so
much for your support.

--
Post: opend...@googlegroups.com
Unsubscribe: opendatakit...@**googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

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

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Hi Mitch,
The fact that it will not support XML, XForms or XPath, is this a
limited resource decision?

I'm currently slated to conform to your aggregate interface on our (Uni of
Syd) soon-to-be opensource Heurist Research Data Store for individual
researchers or research groups. This is a system which sits on top of
MySql/PHP and implements a graph DB system for for highly and freely linked
research data. The research community here in Aus is pretty well set to
Open Linked Data which is fundamentally RDF/XML driven. Since we do JSON
also, we can connect, however this restricts the open connectedness that
(mainly XML) files inherently supports. Do you intend to have a structured
format for the export of the data to a file so that other transport
mechanisms can be used in a non-connected scenario, such as a snicker-usb
net? Perhaps maybe even viewer that supports a structured view of the form
instance.

Going to a on phone/tablet db solution gives the flexibility of linked
data where one forms instance references another, do you intend to make
forms creation re-entrant?

Cheers,
Steve

··· On Thursday, November 8, 2012 5:28:53 AM UTC+11, Mitch wrote: > > The technology of ODK2 is very very different (it does not use XML, > XForms, or XPath expressions). > > But yes, it will have cascading selection support, as it will provide > access to underlying SQLite queries in a simplified form or as raw SQL > expressions (for doing joins across tables in that database). We won't > provide any support for queries across databases. > > We are not far enough along to set a release date. The release cycle is as > follows: > > (1) limited alpha available 'soon' for the evolving ODK Collect and > XLS2Form pieces -- this will be restricted to the key groups developing > OpenRosa-compatible data collection software. This serves as a concrete > talking point for discussions on where tools built upon HTML5 / JSON / REST > should evolve/change. After we get the major kinks addressed... > (2) public alpha 'before the end of the year.' There will still be many > things in flux, including the structure of the XLS2Form spreadsheet, and > you should not use this alpha in any live deployment -- it is only for > evaluation, bug reporting, and user feedback from the broader community. > Depending upon how the discussions in (1) go, there may be significant > changes to the interoperability layers of the ODK2 system (e.g., redefined > submission interfaces, etc.). This is another reason not to use the alpha > for live deployments. > (3) one or more beta releases and/or release candidates. > (4) official release > > Mitch > > On Tue, Nov 6, 2012 at 7:17 PM, Chan Choth <chan...@gmail.com wrote: > >> When is the release date of ODK2? Is it still supporting new cascading >> selections? >> >> Thanks, >> Chan Choth >> >> >> On Friday, October 26, 2012 10:14:56 AM UTC+7, Mitch wrote: >> >>> I don't have a solution in 1.x except to have separate forms for each >>> province. Anything else would require changing the software. >>> >>> In ODK 2, the data is stored as rows in a database table, and you will >>> be able to issue queries on other tables to produce filtered lists of >>> values. >>> >>> Mitch >>> >>> On Thu, Oct 25, 2012 at 7:10 PM, Chan Choth wrote: >>> >>>> Dear Mitch, >>>> >>>> I tested with one small province and it was OK. Is there any >>>> possibility that we can link the form especially this location hierarchy? I >>>> found this feature is available for PoiMapper. By the way, I use Samsung >>>> Galaxy S2 and it is still hang and I am concern if the phone which has >>>> small capacity than this might have a lot of problem. If I root the phones, >>>> all my phones will be void from warranty. I hope with ODK version 2 this >>>> might be not a problem, right? >>>> >>>> Thanks for your kind assistance and I am looking forward to hearing >>>> from you. >>>> >>>> Best regards, >>>> Chan Choth >>>> >>>> >>>> On Monday, October 22, 2012 10:15:13 AM UTC+7, Chan Choth wrote: >>>>> >>>>> Hello there, >>>>> >>>>> Does anyone encounter this issue that if the file is about or more >>>>> than 2MB, ODK hangs and give the message "ODK Collect is not responding. >>>>> Would you like to close it?"? I attached a file for your reference. Thanks >>>>> so much for your support. >>>>> >>>> -- >>>> Post: opend...@googlegroups.com >>>> Unsubscribe: opendatakit...@**googlegroups.com >>>> Options: http://groups.google.com/**group/opendatakit?hl=en >>>> >>> >>> >>> >>> -- >>> Mitch Sundt >>> Software Engineer >>> University of Washington >>> mitche...@gmail.com >>> >> -- >> Post: opend...@googlegroups.com >> Unsubscribe: opendatakit...@googlegroups.com >> Options: http://groups.google.com/group/opendatakit?hl=en >> > > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com >

We are still discussing the details of how ODK2 offers backward integration
with the ODK1 infrastructure.

The ODK2 Collect alpha will be support the download of JSON forms from ODK1
Aggregate with the submission of data into ODK1 Aggregate using XML formats.

This path will, however, never be able to have the richness and power of
the information flows available in the pure-ODK2 system.

The move away from XML toward HTML5/Javascript/JSON is motivated by the
desires to:

(1) enable submissions to be published, updated and followed-up (revised)
via dynamic data-sharing across devices -- to make information flow
bi-directional.
(2) enable the community to easily and rapidly add widgets and customize
the UI through CSS, Javascript and HTML5 editing.
(3) make the clients (tablets and phones) equal peers to the server
(Aggregate), enabling them to have data cleansing, data aggregation and
data visualization capabilities.

In ODK2, the cloud (Aggregate) becomes a mediator for sharing information
from and back out to the devices, in addition to being a
repository-of-record for the collected information.

Mitch

··· On Wed, Nov 7, 2012 at 6:58 PM, Stephen White wrote:

Hi Mitch,
The fact that it will not support XML, XForms or XPath, is this a
limited resource decision?

I'm currently slated to conform to your aggregate interface on our (Uni of
Syd) soon-to-be opensource Heurist Research Data Store for individual
researchers or research groups. This is a system which sits on top of
MySql/PHP and implements a graph DB system for for highly and freely linked
research data. The research community here in Aus is pretty well set to
Open Linked Data which is fundamentally RDF/XML driven. Since we do JSON
also, we can connect, however this restricts the open connectedness that
(mainly XML) files inherently supports. Do you intend to have a structured
format for the export of the data to a file so that other transport
mechanisms can be used in a non-connected scenario, such as a snicker-usb
net? Perhaps maybe even viewer that supports a structured view of the form
instance.

Going to a on phone/tablet db solution gives the flexibility of linked
data where one forms instance references another, do you intend to make
forms creation re-entrant?

Cheers,
Steve

On Thursday, November 8, 2012 5:28:53 AM UTC+11, Mitch wrote:

The technology of ODK2 is very very different (it does not use XML,
XForms, or XPath expressions).

But yes, it will have cascading selection support, as it will provide
access to underlying SQLite queries in a simplified form or as raw SQL
expressions (for doing joins across tables in that database). We won't
provide any support for queries across databases.

We are not far enough along to set a release date. The release cycle is
as follows:

(1) limited alpha available 'soon' for the evolving ODK Collect and
XLS2Form pieces -- this will be restricted to the key groups developing
OpenRosa-compatible data collection software. This serves as a concrete
talking point for discussions on where tools built upon HTML5 / JSON / REST
should evolve/change. After we get the major kinks addressed...
(2) public alpha 'before the end of the year.' There will still be many
things in flux, including the structure of the XLS2Form spreadsheet, and
you should not use this alpha in any live deployment -- it is only for
evaluation, bug reporting, and user feedback from the broader community.
Depending upon how the discussions in (1) go, there may be significant
changes to the interoperability layers of the ODK2 system (e.g., redefined
submission interfaces, etc.). This is another reason not to use the alpha
for live deployments.
(3) one or more beta releases and/or release candidates.
(4) official release

Mitch

On Tue, Nov 6, 2012 at 7:17 PM, Chan Choth chan...@gmail.com wrote:

When is the release date of ODK2? Is it still supporting new cascading
selections?

Thanks,
Chan Choth

On Friday, October 26, 2012 10:14:56 AM UTC+7, Mitch wrote:

I don't have a solution in 1.x except to have separate forms for each
province. Anything else would require changing the software.

In ODK 2, the data is stored as rows in a database table, and you will
be able to issue queries on other tables to produce filtered lists of
values.

Mitch

On Thu, Oct 25, 2012 at 7:10 PM, Chan Choth chan...@gmail.com wrote:

Dear Mitch,

I tested with one small province and it was OK. Is there any
possibility that we can link the form especially this location hierarchy? I
found this feature is available for PoiMapper. By the way, I use Samsung
Galaxy S2 and it is still hang and I am concern if the phone which has
small capacity than this might have a lot of problem. If I root the phones,
all my phones will be void from warranty. I hope with ODK version 2 this
might be not a problem, right?

Thanks for your kind assistance and I am looking forward to hearing
from you.

Best regards,
Chan Choth

On Monday, October 22, 2012 10:15:13 AM UTC+7, Chan Choth wrote:

Hello there,

Does anyone encounter this issue that if the file is about or more
than 2MB, ODK hangs and give the message "ODK Collect is not responding.
Would you like to close it?"? I attached a file for your reference. Thanks
so much for your support.

--
Post: opend...@googlegroups.com
Unsubscribe: opendatakit...@**googlegroups.**com
Options: http://groups.google.com/group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

--
Post: opend...@googlegroups.com
Unsubscribe: opendatakit...@**googlegroups.com
Options: http://groups.google.com/**group/opendatakit?hl=enhttp://groups.google.com/group/opendatakit?hl=en

--
Mitch Sundt
Software Engineer
University of Washington
mitche...@gmail.com

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

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com