Replies: 10 comments 25 replies
-
|
hi, i might give it a try. another problem i had was the lack of the libreview upload feature in the wear os version. i havent tested if the watch can start a libre 3 via nfc or if novopen 6 works on the watch to trigger insulin data upload. i hope this helps. |
Beta Was this translation helpful? Give feedback.
-
|
Do you mean with "if however is switch to direct sensor connection only every 3rd or 5th sensor data interval ends up beeing recogniced"? That you receive values every 3 or 5 minutes instead of every minute in the watch, but that there are no values missing for long periods? This is really unusual. Watch 6 is nearly identical to Watch 4, except for Bluetooth 5.3, A2DP, LE, while for Watch 4 it is, Bluetooth 5.0, A2DP, LE. Under Watch settings->Apps->Juggluco is mentioned "Battery 0% used since last fully charged". NFC can't be used any application under WearOS, it is monopolized by Google Pay. |
Beta Was this translation helpful? Give feedback.
-
yes you got this right, my thoughts are that they "enhanced" their powersaving strategy or that it might be an interference with other bluetooth devices connected to the watch (wireless earbuds) that prevent the watch from getting data every minute.
i have removed the app from the watch but i can reinstall it to test some things for you if this helps, let me know what you need.
thanks for saying this is not normal behaviour, this brings up my hope to get a working solution in the future.
thats a pitty, but something i can imagine google would do ... |
Beta Was this translation helpful? Give feedback.
-
|
one additional question, if i have direct sensor connection with the watch, does the activated libreview upload on the phone get the values from the watch and uploads them, i ask because i had no values in libreview during the timeframe i switched to the watch. might be impatience on my side though. |
Beta Was this translation helpful? Give feedback.
-
|
It doesn't make a difference from what the phone receives the glucose values, it will do the same with them. When it receives the glucose values from the watch (or a mirror connection), the phone will send them to Libreview, to Kerfstok, use them in the xDrip/Nightscout Webserver in Juggluco, the Uploader or Watchdrip if Juggluco is configured as such. |
Beta Was this translation helpful? Give feedback.
-
Because glucose values are send to the phone, it doesn't matter that you uninstalled Juggluco from the watch. Send me the file saved with left middle menu->Export->Stream and tell me when you tried out the WearOS version of Juggluco. |
Beta Was this translation helpful? Give feedback.
-
|
i have installed 5.1.8 now and test again, i will send you new values as i cant pinpoint when i used the watch the last time. |
Beta Was this translation helpful? Give feedback.
-
|
Don't needs to be that specific. If you know the day, it is good enough. |
Beta Was this translation helpful? Give feedback.
-
|
here you go, switch to watch at 11:34. SENSORID 12499 1693041849 2023-08-26-11:24:09 2 12498 108 -0.01 STABLE |
Beta Was this translation helpful? Give feedback.
-
|
You didn't have the previous data because you uninstalled Juggluco and only to test it out you installed it again? |
Beta Was this translation helpful? Give feedback.
-
exactly
it alternates between last error and last success in the connection row
i am still testing.
the phone version waits for new data, after 2 minutes it syncs with the watch and shows the current value, still only every 2nd datapoint.
yes, rechecked after reboot.
yes, it took a few minutes but without intervention or starting anything manual the data came back on watch and phone. here the stream output during app close and watch reboot: SENSORID 12499 1693041849 2023-08-26-11:24:09 2 12498 108 -0.01 STABLE |
Beta Was this translation helpful? Give feedback.
-
|
Because your are not a user of Juggluco, you used another app or device to connect with the Libre 3 sensor. Are you certain that Abbott’s Libre 3 app or reader wasn’t active in the background? |
Beta Was this translation helpful? Give feedback.
-
|
certanly, i never used the abbott reader. but i can shutdown my phone which is the only device i ever used with the sensor and observe the stream on the watch. give me ten minutes. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I also shouldn't have mentioned Abbott's Libre 3 reader, because Juggluco can't take over Libre 3 sensors from it because it's Libreview Account ID is unknown. |
Beta Was this translation helpful? Give feedback.
-
|
bad news, i haven't even started my phone yet to get the stream export, but Left Menu>Sensor still shows bi minute errors. |
Beta Was this translation helpful? Give feedback.
-
|
Can you show the content of Left menu->Sensor on the watch in a few screenshots? (press both buttons). |
Beta Was this translation helpful? Give feedback.
-
|
Now I see the SensorID, you had edited out of the exported Stream data. |
Beta Was this translation helpful? Give feedback.
-
|
yea, im not very fond to have the sensorid on the web but if its necessary. |
Beta Was this translation helpful? Give feedback.
-
|
I didn't need Turbo for Libre3, but for Libre2 had maybe made a difference. |
Beta Was this translation helpful? Give feedback.
-
|
i can enable wakelock and android 13 if you want to test that too. |
Beta Was this translation helpful? Give feedback.
-
|
with turbo still only every 2 minutes. |
Beta Was this translation helpful? Give feedback.
-
|
Wakelock and Android 13 are certainly not necessary. I think about removing these options; to many people turn them on. |
Beta Was this translation helpful? Give feedback.
-
|
i can provide you with a teamviewer session and android studio to be able to debug directly via adb if you want that? |
Beta Was this translation helpful? Give feedback.
-
|
do i have to install the logcat version on the phone also? i ask because under left menu> watch>wear os> config there is no longer my watch listed, so i can't init app and move sensor to watch. current config: phone 5.1.8 watch 5.1.3-wear |
Beta Was this translation helpful? Give feedback.
-
|
Does the Wearable app show a connection? |
Beta Was this translation helpful? Give feedback.
-
|
in the clone menu yes, in the default screen "network problem?" |
Beta Was this translation helpful? Give feedback.
-
|
What does the Android Samsung Galaxy Wearable app say? |
Beta Was this translation helpful? Give feedback.
-
|
nevermind, it took some time, i toggeled bluetooth two times now i could init the app. i moved the sensor to the watch and redisabled battery optimisation. collecting data now. |
Beta Was this translation helpful? Give feedback.
-
|
i have send the logcat dump to your gmail address. |
Beta Was this translation helpful? Give feedback.
-
|
The pattern seems to be repeatedly: getting a connection with the sensor, receiving a glucose value and immediately thereafter an onConnectionStateChange, disconnecting with status=0. Hereafter it takes some time before a connection is re-established. |
Beta Was this translation helpful? Give feedback.
-
|
hi thanks for checking, the watch is basicly stock, i added glucodatahandler and juggluco, there is a lot of samsung bloat on the watch but im not yet commiting to remove it. ive read about an android 13 issue here: https://issuetracker.google.com/issues/242755161?pli=1 which might be of interrest. i activated the android13 option an currently test reliability. |
Beta Was this translation helpful? Give feedback.
-
|
i tried android 13 as option, it behaves "differently" at first it took longer to get a value (3-5 min) toggeling bluetooth helped. i then added the juggluco watchface, next step was to turn "always on display" on. to give the app as much "priority" as possible, then i went into the clone menu and switched on wifi to test if the connection with the phone disables ble somehow. all actions had no effect. all in all i would say the android 13 option does work less reliable. |
Beta Was this translation helpful? Give feedback.
-
|
Good Day, i have removed most of the Stock apps on the watch following the link you posted. On watch 6 there where a buch more default apps some directly indicating working with bluetooth. Like galaxy buds controller. I removed them as well. Unfortunately there Was no change in the behaviour. I rebooted watch and phone after uninstallation of the bloatware. |
Beta Was this translation helpful? Give feedback.
-
|
Did you ever figure out what's causing this? We noticed the same behavior when switching my son's watch from Galaxy Watch 4 Classic to Galaxy Watch 6 Classic a few months ago; instead of getting reliable 1-minute readings, we're getting readings only once every few minutes. This hasn't been a huge issue for us (we export to xDrip and that's what we parents then follow, and that only updates every 5 minutes anyway) but sometimes when the BG is acting up I switch back to the phone as collector, just to make sure I get all the readings. Perhaps this is related to WearOS 4, as the Watch 6 came with that out of the box, whereas Watch 4 was still running 3.5 when we switched? Maybe some "optimization" is trying to save battery this way (in my experience, the battery lasts about as long on GW6 as on GW4, which is at most about a day, so whatever it tries to do doesn't work as intended). |
Beta Was this translation helpful? Give feedback.
-
From reading the discussions and issues on this juggluco page, there seems to be MANY individuals (including myself) that are VERY INTERESTED in connecting ANY smartwatch up to use AS A COLLECTOR. and send data to phone. Can a discussion be started that shares ONLY the models of smartwatches that are CONFIRMED to work as collectors with Juggluco.?
Watch Model, Sensor model, version of juggluco, and optionally, the process used to configure the smartwatch to work as a collector.
I know myself and my others would be very interested in this information......Thank You.
Beta Was this translation helpful? Give feedback.
All reactions