Will the "Galaxy Pocket Neo" ... S5310 ...work with CommCare?

[Eric Stephan]

Hello Everyone --

Is there a chance that anyone can tell me the likelihood that the Samsung Galaxy Pocket Neo -- Samsung S5310 ... will work OK with CommCare?

The photo of that model is attached...

I believe that it is the "super low end" samsung android, you know, those little smaller ones that cost USD $83 here in Bangkok.

For the record, about 1-2 years ago I bought what at that time was the similar "very cheap, smaller, less than $100" android" option, and it has worked well with CommCare though I haven't tried huge forms.

Any guess on the likelihood that this phone will work OK with CommCare? if yes, I will then make a small purchase and do further testing.

Eric

[Jeremy W.]

Hi, Eric,

This phone will most likely work fine with CommCare, at least for basic forms. It sounds like a good next step to purchase one for testing before buying more.

Criteria for devices that should work as well as things to test for are described here: https://confluence.dimagi.com/display/commcarepublic/Recommended+Phones+and+Choosing+a+Phone#RecommendedPhonesandChoosingaPhone-AndroidPhonesandTablets

I don't see anyone having specifically tried/listed this device, though a different Galaxy Pocket (Duos) has been tested and worked.

Jeremy

--
You received this message because you are subscribed to the Google Groups "commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to commcare-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Jeremy Wacksman

Dimagi, Inc.

[Clinton Sears]

Hi Eric, Jeremy and everyone else,

I'm wondering if anyone has tried the Samsung Galaxy S Duos (S7562)?  We have some and tried our app on them and encounter critical errors (Binary XML inflating class error) when moving from one form to another within a module.  Unfortunately the app works fine on my personal Galaxy SIII and my coworkers Android phone.

Jeremy, I just want to clarify what you said below--you have heard that the Duos was tested and worked?  If so, any ideas on what may be causing this error?

Thanks!!

Clinton

[Jeremy W.]

Hi, Clinton,

The specific phone listed on the help site as having been tested is the Galaxy Pocket Duos rather than the Galaxy S Duos - though maybe someone else on this list has had experience with the latter. However we would expect it to work on both and that is a strange error. We have seen your bug report and will follow up with you about that error.

Thanks,

Jeremy

[Derek Hans]

The "Duos" moniker, when associated with Samsung phones, simply indicates that the phone has two SIM card slots. There's not much else that connects "Duos" phones - CommCare working on one does not indicated it will work on another one.

Clinton, the error reported is surprising. It sounds like maybe it ran out of space. I would be curious to know if trying again results in the same error. Is this with the latest build of CommCare?

[Clinton Sears]

Hi Derek,

Thanks for noting that! I'll check with Cheryl in my DC office because we reviewed a list of phones Dimagi had tested and purchased based on that, however there may have been some confusion.  It's important to sort these things out so someone else doesn't have this happen.

Also, just FYI--the phones are running Android OS 4.0.4 and CommCare 2.16.1.  These are the latest versions we can upgrade to.  The phones have 1GB internal storage (of which about 750MB is free) and an empty 1GB SD card which is (should be!) more than enough for our needs.  

For those who are curious the models that don't work are GT-S7562.  We do have two GT-S7582L with us that work.

Clinton

You received this message because you are subscribed to a topic in the Google Groups "commcare-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/commcare-users/NhU_xaMu18M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to commcare-user...@googlegroups.com.

[Cheryl Tam]

Hi all,

I work with Clinton in our DC office. It's really unfortunate that we've encountered these errors, as I specifically selected the Samsung Galaxy S GT-7562 because it was listed as tested and recommended:

• Samsung Galaxy S GT-7562 (successfully supported Hindi script in India, but should still be tested locally. Also largely supports Odiya script. Joint letters in Odiya appear separate but most Odiya readers can manage to read and understand the text despite that) Note: This model is being replaced by the Samsung Galaxy S Duos 2 GT-7582 in India (the GT-7582 has not been tested but is succeeding the GT-7562, so there's a good chance that it would work)

As Derek alluded to, I believe it's more important to focus on the actual model numbers, which seem to be the unique identifiers used by Samsung, instead of the names--however, I'm not sure if there is a difference between the S GT-7562 and the GT-S7562. For this activity, we had also ordered a batch of GT-S7582 phones as well, though we have not run into any issues with CommCare on those devices. We appreciate your help in trying to identify what may have gone wrong in this case.

Thanks!

Cheryl

[Eric Stephan]

Hi all -- just wanted to throw one more piece of info into the thread -- we purchased several of that exact model and it's worked very smoothly for us, we haven't seen that error message or any others. (And it's been able to display both thai and lao script.)   

Hoping that you'll find that the odd message you're getting is a fixable but that's rooted in something other than the model of phone! --Eric

[Clinton Sears]

Hi Eric,

Thanks for that interesting piece of information.  This really is a pickle :(

We'll be taking the phones with us and will try to figure out the cause.  If we learn something useful, I'll be sure to post it here for others' benefit.

Thanks!!

Clinton

On Wed, Nov 19, 2014 at 11:14 AM, Eric Stephan <este...@fhi360.org> wrote:

Hi all -- just wanted to throw one more piece of info into the thread -- we purchased several of that exact model and it's worked very smoothly for us, we haven't seen that error message or any others. (And it's been able to display both thai and lao script.)   

Hoping that you'll find that the odd message you're getting is a fixable but that's rooted in something other than the model of phone! --Eric

--