I have a slight issue with Fully Kiosk Browser. If I have it set to screen off (so it has a fully blacked-out screen), when triggered by motion, I have to refresh the screen or navigate out and back again for the screen to update. When using it in screensaver mode, everything’s fine.
Has anyone come across this, or any advice to resolve it?
Can you clarify what you mean by “navigate out and back again”?
I’m trying to understand if you mean you are killing the Fully Kiosk app completely… or perhaps just navigating from one dashboard to another… or something else altogether?
I suspect that if the screen goes completely off, the browser part of the Fully Kiosk App likely goes into a deeper sleep at some point… that would likely stop receiving event updates and refreshing your auth token if it’s in a deep enough sleep as the browser can effectively pause the ‘webapp’ completely. In theory, once the app wakes back up and the browser part wakes back up, the event updates and token refreshes would start again… though I suspect it may take a few seconds for it all to happen.
As such, I’m curious if after waking from a deep sleep if you wait 15-30 seconds, does it eventually reconnect and update the data on its own? I’m also curious if the Socket Disconnected message shows up at the bottom of the screen at any point during that?
So I have a tasker tile which destroys any open apps, Forcing Fully Kiosk Browser to start up again
Yes
If retriggered a short while later, it will take 5 or 6 seconds to update, animated icons also freeze during this period.
I’ve noticed it once or twice but not regularly
What do you mean if ‘retriggered a short while later’?
Am I understanding correctly that the issue resolves itself after a 5-6 seconds or at least after 15-30 seconds with no intervention on your part? Just that you can also force it to be resolved immediately by refreshing the page or killing and re-opening Tasker so you don’t have to wait?
I’ve managed to resolve my updating issue, thanks
Hello Paul_Paul,
I’m facing the same issue. After sleep with screen off, when turnng on again I have a delay (in response from fully) until it reloads/updates the page.
How did you solve it?
bias
My statement that I’ve sorted it may have been slightly overestimated, as this is still a work in progress.
I’m definitely not a fan of this new socket. I’m not sure any of this will help.
Using the Fully Kiosk API, I switched from screensaver mode during daylight hours; then at sunset, it switches to screen off. This kind of works in summer, as during bedtime hours the dashboards are only used for security.
However, moving into winter, when darker days come, I want the screens to be totally blacked out (turned off). So I’ve been test-driving some app-based dashboards that come for free, along with a couple of subscriptions I have, again using the Fully Kiosk API to switch between day and night. Additionally, for each change, I have Tasker reboot them as well.
I kind of miss having the screen-off mode working all the time, as I had rules based on this.
I also have other issues, which I somewhat blame on the socket, but it could just be that my Fire tablets don’t like it.
Thanks a lot for answering. I enjoyed fully browser solution (for end solution specific reasons + the fact that the screen saver can have a youtube playlist, accoustic motion detection and mqtt) compared to the official apk solution. But because of that and until i have a solution, for better stability, I reverted to the plain apk instead of the browser version.
Over the few weeks I have had an issue with acoustic motion detection. I use alerts to exit the screensaver. I’ve detected 2 issues on my device.
The Microphone keeps getting disabled on my Fire HD 10 under Kiosk App Permissions.
App Permissions > Fully Kiosk > Microphone (is Disabled)
I also have to change the Fully Kiosk Acoustic sensitivity setting to another number and save. For example if set to 60, I’ll change to 50.
After going through these steps it works perfectly for a day or so.
Known issue under Kiosk FAQ. > Can I use Fully Kiosk with an Amazon Fire device?
**There is a bug in the newer Fire OS 7.3.1.5+ that the granted microphone access permission gets lost sometimes.