-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mirror reconnection issues when network drops intermittently. #84
Comments
After upgrading to version 6.0.4 still has issues reconnecting, until I "sync" mirror on the phone. Then next reading sent will reactivate the connection and mirror reconnects again. |
this is happening to me quite frequently during the day, 6 to 8 times a day. If I do not catch it, the mirror will not reconnect until I do a "sync" on the phone session mirror of Juggluco, then it comes up within the next minute or so. Could you look into this issue to see if my suggestion my be an option to resolve this soon? |
I am seeing that when this mirror gets disconnected, that the mirror on the PHONE still shows a CURRENT date and time of activity, But I still need to do a "Sync" on the mirror (on the phone Only) to get it to reconnect. |
I am running Juggluco version 5.1.14 on a galaxy watch 4 running a mirror to send sensor readings to my phone juggluco (running the same version). readings every minute.
I am experiencing a wierd condition where my network goes down for approx 10-15 secs intermittently then comes back up. However the mirror on the phone seems to stop and will not reconnect for up to 45 mins or so, if at all. I was able to determine that IF I do a "sync" on the mirror from the phone, it syncs when the next reading from the watch mirror comes thru, a very high percentage of the occurances.
I am wondering if it would possible for Juggluco to perform the "sync" function automatically when it detects the network signal has gone down. this way although the network signal drops for 15 seconds, the juggluco phone mirror will not miss ANY readings and should continue as normal.
The text was updated successfully, but these errors were encountered: