You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If I dont touch my phone every 2 Minutes the screen saver causes the meeting to be interrupted
Android 11
Samsung S10
Samsung Smart Cover
Chrome Browser (latest)
Andriid Web View latest
BBB server could be supplied later if needed
To Reproduce
Steps to reproduce the behavior:
Set Screen Timeout to 5 Min on device settings
start meeting
talk for 5 min and dont use the phones touch screen or buttons
if you have smart cover, close the cover
after 5 min latest meeting gets interrupted
we would need to reconnect to the meeting from entering tbe URL again.
Expected behavior
Continue the meeting until end of meeting without breaking the connection by OS (deep) sleep
Thank you
I am happy to help testing
The text was updated successfully, but these errors were encountered:
Hi,
Thanks for reporting this! Currently all of the developers of this app are working on their respective thesis. We will definitely get back to it after those is done and rewrite the app using the newest version of flutter as well.
We will keep this issue in mind during the rewrite!
Describe the bug
If I dont touch my phone every 2 Minutes the screen saver causes the meeting to be interrupted
Android 11
Samsung S10
Samsung Smart Cover
Chrome Browser (latest)
Andriid Web View latest
BBB server could be supplied later if needed
To Reproduce
Steps to reproduce the behavior:
Set Screen Timeout to 5 Min on device settings
start meeting
talk for 5 min and dont use the phones touch screen or buttons
if you have smart cover, close the cover
after 5 min latest meeting gets interrupted
we would need to reconnect to the meeting from entering tbe URL again.
Expected behavior
Continue the meeting until end of meeting without breaking the connection by OS (deep) sleep
Thank you
I am happy to help testing
The text was updated successfully, but these errors were encountered: