DeviceManager sometimes not able to receive new connection

[sboettcher]

We are getting a lot of reports from participants, and have seen in our tests, that the app will sometimes not allow a new device connection (E4), even if the app is in the foreground and the device row indicates that connection should be possible. We have not been able to robustly reproduce this or pinpoint the cause, but have confirmed it can happen after some unspecified amount of time that the app is running. To solve, the app needs to be force stopped and restarted. Sometimes it also helps to press the red X button in the device row multiple (5+) times.

This might be loosely related to #269 ?

[afolarin]

Do you have any idea of the frequency of these events? For example, I know when we ran internal testing the duration was 5 days or so, so perhaps we never experienced this effect. I wonder if this is something we can replicate?

But alternatively, perhaps @blootsvoets has some ideas as to where the potential sources of this behaviour might lie (E4, Android OS or pRMT app)?

[sboettcher]

I think in our tests we also saw this before 5 days, but when I mentioned it previously I always saw it as lower priority, since it is fairly easy to reset the app. But it seems now that our participants are having a bit more trouble with than I anticipated.

I'll try to reproduce it again on my phone and also get some logs...