Sony Smartwatch Alerts

Hi I wonder if someone can help me - I’ve been using a Sony Smartwatch 3 as a standalone collector for some years now, initially with G5 and now G6, but unfortunately that watch failed.
I have since purchased a couple more second hand and although I have managed to get them working and showing XDip graphs and readings fine, I have been unable to get any alerts working on the watches. If the phone is on it alerts but the alerts never show or vibrate on the watch, have I perhaps inadvertently set something wrong in either the phone or watch menus?

If I go into XDrip Prefs. on the watch these settings are showing:
BT Collector - DexcomG5
Enable Collector - Connect to BT Collector when phone is out-of-range - Ticked
Force Collector - Force phone to use Wear Collection Service - Ticked
Under G5 settings the only ticked item is Auth G5/read
Enable Alerts - Enable BG Alerts - Ticked
High Alerts - Enable Persistent High Alerts - Ticked
Play Sound - User watch speaker if it has one to play alerts sound - Ticked
Refresh on CH.. - Refresh face on data change on data change instead of every minute - Ticked
Show Toasts - Not Ticked
Show Status - Not Ticked

I also believe I have used the same .apk file as used for the original watch, rather than using later versions, so the only difference is probably the adb file as the powershell script always seems to downloads the latest version.

I’d be very grateful for any hints or tips that anyone can give….

1 Like

I maybe one of the few that still use the Sony watch. I was very surprised when a Dexcom engineer emailed me to report the Sony watch will flawlessly work with the G7. She said they can’t acknowledge that fact since the watch is not in production. The only problem with the watch is to occasionally replace the battery.

2 Likes

On the Sony watch that failed the most common failure is the battery. I have seen many failed Sony failures all fixed with a new battery. I was probably one of the few diabetics that started using the Sony when it was new. One other bit of information, there are 2 versions of the Sony identified by the 4 character ID. If the characters are all alpha like F3B8 it is the most common. If all 4 characters are alpha or numonic it’s a version that has very special added features like a magnatron and navigation.

1 Like

I found the answer to my query above dated March 2026:

There is a setting on the Wear OS app on my Samsung S7 phone - from the top page scroll up and select ‘Notifications’ - then select ‘Change watch notifications’ - there is then a specific xDrip+ notification on/off button.

I have no idea how that changed as I have never been in that menu before, but all resolved now!!

Some other useful info. I found is the watch does not use the high and low level alert settings found on the phone xDrip+ app under ‘Level Alerts’ instead the watch uses the high and low settings under ‘Glucose Units’ on the phone, these also determine the high and low lines on both the Phone and Watch displays.

Hope someone finds this info. helpful…

Hi Dennis et al, I have one of the later Sony watches that has the magnatron, accelerometer, navigation, speech control etc. however I have two issues with it:

  1. Although my Samsung S7 thinks it’s connected to watch, the watch isn’t connected according to the watch bluetooth settings and it keeps crashing the Wear OS app on the phone.
  2. When trying to use adb on the watch with my PC it always comes up unauthorised - I have tried every remedy I can find on the web to get around the unauthorised status, however the watch never prompts to allow the connection to my PC.

I don’t suppose you or someone else can suggest any remedies to the above?

PS good to hear about the G7 as I’ll be migrating soon….

1 Like

Sounds like you need to enable developer mode.

Try the response in this link:

Yeah this smells like a notification bridge issue, not your xDrip settings. If alerts fire on the phone but the watch stays dead, 9 out of 10 it’s Android killing the Wear OS notification service or permissions being half broken. Go check app notifications for xDrip on the phone, make sure they’re allowed, then in Wear OS app enable “mirror phone notifications”. Also disable battery optimization for xDrip and Google Play Services, that one kills alerts silently. And honestly, those old Smartwatch 3 units are janky now, I had one and alerts just randomly stopped until a reboot, so don’t overtrust the hardware either.

Sorry to take so long to reply. As I may have previously responded; the Wear OS used with the watch to show the correct xDrip+ watch faces is 2.13.0.199332 for release date of 6-27-2018. With this release date the xDrip+ watch faces will are available even when a newer release date is downloaded. This version seems to work for the Dexcom G5, G6 and now G7. With the G7 version I’m not sure what version the watch had working.

I will again try to get in touch with the Dexcom engineer for any additional information. Dexcom can’t publisize the Sony watch since it is no longer available. I do have a lot of Sony parts and many spare watches. Let me know if I can be of any help. The watch has always been a surprise as to what it can do. It can also control the smartphone to enable and disable some allerts. It is sometimes annoyable since I have had sometimes disable the phone alerts with the watch.

I have always used a Samsung phone since it has a unique feature to show the xDrip+ display in the ‘sleep’ mode while it is charging. The CGM value is the best part in the sleep mode since the graph is not very usable in that mode on the display at night.

By the way to allow the watch to be the CGM data collector perform the following steps: On watch swipe the display to the left an select xDrip Prefs. Enable Collector ‘Connect to BT Collector’.

There is also a setting that allows the watch to switch between the Slave mode and Collector mode when a person misplaces the phone.

Also try not to enable too many notifications on the Wear OS for the watch. That can be very distracting and use more battery power.

Dennis

One thing I forgo to to mention, many years ago I started with the Samsung S5 then the S7, S9, S22+ and now the S25. Hard to keep track of the S numbers.

Dennis