Hello,
We've been running into some issues while trying to use the ODK
Collect android application. The application was downloaded via the
Android Marketplace - it is the current version posted there.
In particular, the error we're seeing is: "Sorry, unable to load
remote form list!" when trying to manage the remote forms/files list.
This is over a wifi connection on a T-Mobile G1 (android 1.6, fully
updated). It isn't working "out of the box" for the default 'http://
open-data-kit.appspot.com' url, nor for a custom url [on our local
network] - although the HTTP request/response itself is definitely
being made in the case of the latter.
We're able to browse the web via wifi on the phone and there isn't any
form of redirection/proxying taking place on the wireless network.
Interestingly enough, when we enter the /formList url manually into
the phone's browser it appears to initially try to render the content
(text inside the xml tags - i.e. the form names) and then appears to
crash (the phone falls back to the home screen). (Charset encoding
issue of some sort ???)
It's also worth mentioning that we do have the ODK Collect app running
fine in an android emulator (tested on both 2.2 and 1.6) on a local
machine from the same network.
Is it possible this issue is caused by the fact that we're using wifi
on a phone with no sim card installed? From a technical perspective I
can't imagine this being problematic - HTTP is HTTP whether its via 3g
or 802.11.. But I have very little experience with these phones and
don't know if there are any issues/differences between the way the
phone handles HTTP transport for each.
At any rate, we were wondering if anyone in the community has ever
experienced/witnessed any similar issues and could potentially shed
some light on the situation.
Thanks!
-Adam
hey adam,
sorry collect isn't working for you. sounds like you've done a fair
bit of troubleshooting already, but have you checked the sd card?
to download forms, the phone needs to write to that card and if it is
bad or the odk folder is corrupted, it will fail. make sure your sd
card is working and you can delete odk folder and see if that helps.
if that doesn't work, then plug in the phone, get a stack trace of the
error, post it to dpaste.com and send out a link. i tend to hang out
in the odk chatroom (http://is.gd/3eBfu) so if you need more help,
find me there...
yaw
ยทยทยท
On Thu, Jul 22, 2010 at 10:01, Adam Hammouda wrote:
> Hello,
>
> We've been running into some issues while trying to use the ODK
> Collect android application. The application was downloaded via the
> Android Marketplace - it is the current version posted there.
>
> In particular, the error we're seeing is: "Sorry, unable to load
> remote form list!" when trying to manage the remote forms/files list.
> This is over a wifi connection on a T-Mobile G1 (android 1.6, fully
> updated). It isn't working "out of the box" for the default 'http://
> open-data-kit.appspot.com' url, nor for a custom url [on our local
> network] - although the HTTP request/response itself is definitely
> being made in the case of the latter.
>
> We're able to browse the web via wifi on the phone and there isn't any
> form of redirection/proxying taking place on the wireless network.
>
> Interestingly enough, when we enter the /formList url manually into
> the phone's browser it appears to initially try to render the content
> (text inside the xml tags - i.e. the form names) and then appears to
> crash (the phone falls back to the home screen). (Charset encoding
> issue of some sort ???)
>
> It's also worth mentioning that we do have the ODK Collect app running
> fine in an android emulator (tested on both 2.2 and 1.6) on a local
> machine from the same network.
>
> Is it possible this issue is caused by the fact that we're using wifi
> on a phone with no sim card installed? From a technical perspective I
> can't imagine this being problematic - HTTP is HTTP whether its via 3g
> or 802.11.. But I have very little experience with these phones and
> don't know if there are any issues/differences between the way the
> phone handles HTTP transport for each.
>
> At any rate, we were wondering if anyone in the community has ever
> experienced/witnessed any similar issues and could potentially shed
> some light on the situation.
>
> Thanks!
>
> -Adam