We have tracked the problem over the past weeks and come to a clearer picture:
- Each session, some 4 or 5 handsets lose their connection to our router. When you use the drop-down to see which router they are attached to, they typically say "WiFi", and all attempts to reconnect to our router fail. At this point, we switch off the offending handset, and put it on charge in a pile with the other failures, so that its serial number can be noted after the session.
- It tends to be, by and large, much the same handsets that disconnect each session.
- This did not happen this time last year, when the handsets had been in use for a couple of months.
- The disconnects tend to happen from the middle of the evening onwards.
My conclusion, to put it in the simplest terms that I can understand, is that some of the handsets get tired.
We are getting round this problem by investing in more handsets. So during the session, we have one of our six-way chargers in the background, with up to six handsets waiting to be used where needed. They are kept switched on and with the app activated.
Our offending handsets are all Acer Iconia 7-inchers. We are now buying Lenovo 7-inchers when they are £50 or less, and we will probably buy some more Amazon Fires when they come down to £30-35. The only disadvantages of the Lenovos is that they reflect the fluorescent lighting from the ceiling and the charging light doesn't change colour when full. The disadvantage of the Amazon Fires is that I haven't yet worked out how to hide all the other apps on the device; they are a bit heavier, but they feel more rugged.
I should add that we have found it to be good to activate the app on every handset before the wireless connection within the BridgeScore session is itself started. This means that when we do get the session going, we know each table already has a working BridgePal app, so we never have to replace a faulty handset right at the start of the session.