A solution to the problem seems to stop all background processes before starting Reactable mobile on S3 Android. We still have to figure out which service exactly causes the problem.
It seems that you are not the only one with this problem. For what we know so far it occurs on Samsung S3, but on the Samsung S3 which we have for testing the problem does not happen. So maybe there are some devices out there with a slightly different hardware or software version. Or maybe the problem is triggered by a specific setting or by some software running in the background.
In any case, we are working on it, but it is not easy for us to fix as we can not yet reproduce the problem.