Open cgarwood opened 7 years ago
Can this be consistently re-created, outside of the Kiosk Browser?
I haven't done much with it lately. We set up Fully to refresh the page when it detects motion and wakes up, which seems to have alleviated the issue. However, if that can be avoided it would be even better. I need to update the tablet at church and install the newest version of Fully and see if the problem still persists.
With FullyKioskBrowser/Kindle Fire Tablet:
If the wifi flakes out the app gets stuck in it's current state (either lock screen or controls screen), but no longer communicates with the node server. If it's on the controls screen, no button presses work.
This should kick back to the "Connection Lost" screen, as the websocket is disconnected, but for some reason it isn't.
Even tried killing the node server and restarting and the app didn't respond until the page was refreshed.
Need to do some further troubleshooting. Could be related to Fully Kiosk Browser, which has some Javascript helper functions that can be called to refresh things if the wifi disconnects or reconnects.