WearOS 5 compatability discussion (Galaxy Watch 7 & Pixel Watch 3) #3581
Replies: 19 comments 35 replies
-
|
For now I plan to return the watch for a refund in week or two. I don't have much hope of getting a graph watchface working. |
Beta Was this translation helpful? Give feedback.
-
|
This change in new Wear OS really sucks for us. But there is some hope. I got my very heavily modified graph working by modifying the source code and saving the graph into Bitmap format when it updates. Then I updated the Customcomplicationproviderservice to provide this image. Next, I made a watchface that uses SMALL_IMAGE complication using the WatchFaceStudio. Maybe some developer might get ideas from how I approached it, or comes up with even a better, more efficient way if possible. I don't feel comfortable sharing my changes as they have not been tested thoroughly and heavily modify the xDrip source code. People's lives might depend on it. |
Beta Was this translation helpful? Give feedback.
-
|
That is good to hear. At least it isn't impossible then. I don't have the skills to modify xDrip, but perhaps I will tinker with Watch Face Studio a bit, before refunding this watch. It looks like I should be able to display mg/dL, delta, and trend arrow at the least. Perhaps I can make this work for myself. I suppose the graph isn't vital for me.
|
Beta Was this translation helpful? Give feedback.
-
|
I can't figure out how to increase the font size of the complication. It's always a microscopically tiny font, no matter how big I make the font of everything in Watchface Studio. It's like xdrip has the font size hard coded, or Watchface Studio has a bug 
It seems their customer support is swamped after launching this watch - hopefully I get my refund… 
|
Beta Was this translation helpful? Give feedback.
-
|
I just got my galaxy watch 7 yesterday and have hit the same issue. Managed to get xdrip installed using wear installer but no watch faces and can't even get the complication working. I also haven't been able to get the complication working on my existing watch 4 for at least 6 months or so but that's fine as I use the xdrip watch face but that's no longer possible. I'd say having the BG graph on my watch is probably the main reason for wearing a smartwatch in the first place. I use the sleep tracking etc as well but none of that is important as being able to see what my BG is doing on a graph simply by looking at my wrist. I did a trade in with my watch 4 so only have a few days before I need to send my old watch back but thinking I might have to cancel and return the new watch if I can't even get my BG displaying on the new watch let alone the graph. My workaround for my watch 4 if I want to use a different watch face is to use a complication from NightWear which pulls the data from nightscout but this is less than ideal as it can be slow and is dependent on having internet access and my nightscout server being accessible. It also seems unnecessarily hacky when the device uploading the data to nightscout is connected directly to the watch in the first place. So I could probably do this on the new watch too but it feels like a huge downgrade in experience which kind of defeats the point in upgrading the watch. If anyone is able to help me get at least the complication working on the new watch I'd greatly appreciate it, otherwise I think I'll have to return the new watch. |
Beta Was this translation helpful? Give feedback.
-
|
I want to mention, developers don't need a WearOS 5 watch in order to fix this. WearOS 4 will work. Download Watch Face Studio, click add complication, and load it onto your WearOS 4 watch. From there, try to get the xDrip graph loaded into the complication. That's all we need, essentially. |
Beta Was this translation helpful? Give feedback.
-
|
I struggled with this yesterday after getting a new watch and found a fix by adding GlucoDataHandler to the mix. It pulls from x-drip and provides complications for watch faces. It's on the play store and open source. Seems to work pretty well, just had to enable 'broadcast locally' and 'broadcast service api' from the inter-app settings in x-drip. This got it working and prevented me from returning the galaxy watch 7. |
Beta Was this translation helpful? Give feedback.
-
|
I used GlucoDataHandler to show readings on Galaxy Watch 7 - works fine for me, but I have problem with Android Wear Integration on this smartwatch. Does anyone was able to get reading from Wear Collector Service running on Samsung Watch7 and Dexcom G7? If yes could you please share your preferences used for it? |
Beta Was this translation helpful? Give feedback.
-
|
I might have a way to enable the xDrip+ watchfaces on a Galaxy Watch 7, even though they are no longer officially supported on those devices. No guarantees though as I don't have a GW7 myself, nor do I use xDrip+. See here: https://youtu.be/EvTGEnPA9PY |
Beta Was this translation helpful? Give feedback.
-
|
It turns out that Google have removed the watchface runtime package completely from the Pixel Watch 3. So the method shown in my video won't work on that device :-( |
Beta Was this translation helpful? Give feedback.
-
Oh no! Excuse my ignorance, is there a possibility these packages may be removed from the GW7 in future Wear OS versions as the watch is updated? Or is there a method to check packages prior to updating? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible to add this "watchface runtime package" back in? I see someone on XDA forums exported all of the Galaxy Watch 7 .apks and one is named runtime https://xdaforums.com/t/watch-7-ultra-pulled-apps-one-ui.4682929/ |
Beta Was this translation helpful? Give feedback.
-
I've disabled updates but I see Samsung has an update available. I'm curious to hear if any brave soul running this workaround has updated. I'm also curious if there is a downgrade method to reflash a watch to original wearos version (I'm guessing no…) |
Beta Was this translation helpful? Give feedback.
-
Declarative Watch Face Runtime (also referenced as "Watch Face Format Runtime") is used to render Watch Face Format |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys..
I am Graham a 60yo insulin dependent user of xDrip. Its great on the
phones and tablet but i dont even install it on my watch anymore.
The app to interface is GlucoDataHandler (Michael has done a great job of
providing an overwhelming amount of complications for the wearer.
I have also published a number of faces on the Google Play store. I am in
the process of updating them to meet the new policies, disclosures and APK
level 33min
Anyway. That might be a better route. For get developing the Faces and
Just Pass good complications.
Graham
***@***.***
…On Thu, Jul 25, 2024 at 9:15 AM Jack Knott ***@***.***> wrote:
I just got my galaxy watch 7 yesterday and have hit the same issue.
Managed to get xdrip installed using wear installer but no watch faces and
can't even get the complication working. I also haven't been able to get
the complication working on my existing watch 4 for at least 6 months or so
but that's fine as I use the xdrip watch face but that's no longer
possible. I'd say having the BG graph on my watch is probably the main
reason for wearing a smartwatch in the first place. I use the sleep
tracking etc as well but none of that is important as being able to see
what my BG is doing on a graph simply by looking at my wrist.
I did a trade in with my watch 4 so only have a few days before I need to
send my old watch back but thinking I might have to cancel and return the
new watch if I can't even get my BG displaying on the new watch let alone
the graph.
My workaround for my watch 4 if I want to use a different watch face is to
use a complication from NightWear which pulls the data from nightscout but
this is less than ideal as it can be slow and is dependent on having
internet access and my nightscout server being accessible. It also seems
unnecessarily hacky when the device uploading the data to nightscout is
connected directly to the watch in the first place. So I could probably do
this on the new watch too but it feels like a huge downgrade in experience
which kind of defeats the point in upgrading the watch.
If anyone is able to help me get at least the complication working on the
new watch I'd greatly appreciate it, otherwise I think I'll have to return
the new watch.
—
Reply to this email directly, view it on GitHub
<#3581 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A63YKNVIPH63NGMVKPQJBPTZOECBXAVCNFSM6AAAAABLJPBJZOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJUHE3TCMQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: <NightscoutFoundation/xDrip/repo-discussions/3581/comments/10149712@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I have the new Galaxy watch ultra. GlucoDataHandler is my go-to for
complications. Use it on a s22 t send to watch 5 pro, and as follows to
send to watch Ulta from a Flip 6
…On Fri, Sep 20, 2024, 3:20 AM malbry ***@***.***> wrote:
Other users have confirmed that the method shown in this video does work
on the Galaxy Watch 7 (although not on the Pixel Watch 3):
https://youtu.be/EvTGEnPA9PY
—
Reply to this email directly, view it on GitHub
<#3581 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A63YKNREZTSCUVG6DW6OZ5TZXPLD5AVCNFSM6AAAAABLJPBJZOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZQGIYDOOI>
.
You are receiving this because you commented.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
DMM Diabetic Watch FacesSeeing the need for Diabetic Watch Faces with Wear OS 5. I've now completed my project of making Diabetic Watch Faces, that are oversized for the Visually impaired, I also have a Few Diabetic Watch Faces with Graphs. Sideloading Watch Face Apks or Personalizing .WFS files (Watch Face Studio) Go Here:https://github.com/sderaps/DMM Google Play Store Front for DMM Diabetic Watch Faces Here:https://play.google.com/store/apps/dev?id=6551812103351455972&hl=en_US |
Beta Was this translation helpful? Give feedback.
-
|
WearOS 5 auf der google Smartwatch 2 |
Beta Was this translation helpful? Give feedback.
-
|
What is the status on this issue these days? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
I don't know of any xDrip developer who is working on Wear OS. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Status is still the same as the update on the very first line, and not
expected to change. It works great on the Galaxy watch 7 but not the pixel
watch 3.
…On Tue, Mar 4, 2025, 5:14 AM Navid ***@***.***> wrote:
I don't know of any xDrip developer who is working on Wear OS.
—
Reply to this email directly, view it on GitHub
<#3581 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACOAHFNKF66ITVNOPSN7ULL2SWRMZAVCNFSM6AAAAABLJPBJZOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZYHA2DEMA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
@malbry - do you know any more details regarding "Update January 2025: this method no longer works on watches that have WearOS 5. This includes the Pixel Watch 3 and the Galaxy Watch 7 and Ultra :-(" ? Was it a particular update? xDrip is still working great on my GW7. |
Beta Was this translation helpful? Give feedback.
-
|
@tofof @gth001 @malbry I can confirm it is still working with Galaxy Watch 7, I just took a leap of faith, bought one and tried it and it works. Also, there are comments on the video after January which report success. |
Beta Was this translation helpful? Give feedback.
-
I also have it running on my GW7 per the original video, having said that I am running a very old OS release (refer to details below) and have only updated the watch once since purchase. I would be interested if others have kept the GW7 up to date with patching? @gth001 ? I am holding off with any further updates as I have some concerns it will break xDrip+ and reverting to a previous OS release is a major pita. One Ul version Software version Wear OS version 5.0 Wear core services 1.11.29.603629754 Android security |
Beta Was this translation helpful? Give feedback.
-
|
I'm on even older firmware than you. I turned off Auto Update and I'm not willing to risk trying it, not unless I'm forced to. |
Beta Was this translation helpful? Give feedback.
-
|
@imshane85 @gth001 I'm running L310XXU1AXL1 which is the latest update if I'm not mistaken, and that's what came on the watch as I have not performed any update and turned off automatic updates too. |
Beta Was this translation helpful? Give feedback.
-
|
I received a report that the method in my video wasn't working on the
latest firmware update for the Galaxy 7 series. But then someone else said
it did work. The problem is that I don't have the Galaxy 7 myself, so I
can't check directly.
…On Sat, 15 Mar 2025 at 23:54, Tom Alon ***@***.***> wrote:
@imshane85 <https://github.com/imshane85> I'm running L310XXU1AXL1 which
is the latest update if I'm not mistaken
—
Reply to this email directly, view it on GitHub
<#3581 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXXBKWP7SESSLJCO3QE5O3D2US4UFAVCNFSM6AAAAABLJPBJZOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJRGI4DGMI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Brand new Oneplus watch 3 on wearOs 5 here and unfortunately Wear Installer 2 failed to install the faces ... |
Beta Was this translation helpful? Give feedback.
-
|
If anyone can open a PR and show test results that show improvement, I believe they will be considered. |
Beta Was this translation helpful? Give feedback.
-
The problem is that Google has completely dropped the old-style watchface runtime in the recent WearOS builds. That affects new Pixel and OnePlus watches, so that watchfaces such as the xDrip+ ones can't be used. There's no way to add the watchface runtime back on those devices. For some reason Samsung has kept the watchface runtime in the latest Series 7 range, albeit not generally accessible except by using Wear Installer 2. But it's likely that even Samsung will follow Google's lead and remove the old watchface runtime at some point in the future. Sorry not to have better news. |
Beta Was this translation helpful? Give feedback.
-
|
So, I guess we've reached the end of the road for Android watches. I'll keep buying used ones that still work. After that, we can always return to Pebble now that they're going back into production :P https://store.repebble.com/ |
Beta Was this translation helpful? Give feedback.
-
|
A warning to all: I just let my Galaxy Watch 7 update today and xDrip disappeared :( "Set Watchface" in Wear Installer 2 doesn't do anything any more :( |
Beta Was this translation helpful? Give feedback.
-
|
Anyone know if samsung lets you flash the factory image to get rid of all the updates? I know Pixel Watch 3 lets you via https://developers.google.com/android/images-watch |
Beta Was this translation helpful? Give feedback.
-
|
I guess I am OK - I figured out how to use glucodatahandler complications in #3581 (comment) |
Beta Was this translation helpful? Give feedback.
-
I inadvertently followed the same fait - I pressed 'update' on the persistent notification when I was half asleep and couldn't stop it. I knew this day would come but I was not prepared! The xdrip+ watch face was (is!) way ahead of it's time in my view, especially with the zoomable and fully configurable graphs. I was so heavily reliant on it to manage my bsl. I hope some devs pick it up. For now I've also got one of the DMM watch faces running with the Bloze (LibreLinkUp) graphs, and whilst it serves a purpose in the interim, its just not the same, and requiring a data connection is a massive pita. I'm still grateful to the devs for building this, but really hanging out for glucodatahandler 2.0 and what it can offer in terms of graphs. Technology regression sucks. |
Beta Was this translation helpful? Give feedback.
-
|
I only renewed my old Samsung watch to the Ultra 16 days ago. They will not refund me as they have a 14 day return policy. I wrote them a really terrible review and they bounced straight back at me this morning with the standard 'we sympathise with your issues' and asking me to contact technical support. The problem is the way that their Website is set up you are actively discouraged from pursuing this course of action. I emailed Michael at Glucodatahandler earlier on and explained situations. He said that he also is starting to encounter restrictions which may complicate the application and running of his app. His best suggestion at least for now was to do not install any future watch updates which of course makes every logical sense. Samsung it seems do not want me to be able to use their devices to better manage my own condition but they are very happy to provide me watch faces with cats on or Bitmoji images. FFS why would anyone over the age of 7 want a watch face with cats on it? This of course excludes my ex wife who was obsessed with cats. Suggestions elsewhere on the internet are that Samsung paid Google to force us all into using their really crappy and really buggy watch face generator and watch face store. I GIVE IN I really do. At least for now I have something to be able to refer to which gives me blood glucose data on the hoof. How long this will be good for is up to Mr Samsung and those little darlings at Google. |
Beta Was this translation helpful? Give feedback.
-
|
I did a Samsung update yesterday on m y Galaxy Watch Ultra. Despite suggesting there would be no major changes, boy oh boy have they changed things. The runtime element that I am told Xdrip+ needs to run on a watch face has gone. Samsung have offered a consolation prize. You can get a watch face with a picture of 2 cats or wait for it..... Bitmoji images WOOOHOOO. Why don't they leave us all the hell alone? In any case I also found Glucodatahandler and managed to install it on phone and watch. Downloaded a couple of watch faces from Diabetic Masked Man in the US and have a couple of watch faces up and running. While these are not representative of the Xdrp+ display which I have come to know and love they do provide all relevant data and I am incredibly grateful to Michael - Glucodatahandler and the American chap Diabetic Masked Man. Here is a sneaky peak:
|
Beta Was this translation helpful? Give feedback.
-
|
Hello, I bought a watch 7 but the "Sectograph" application that made me buy the watch no longer works in it. I installed it with Wear installer 2 but the watch face did not come. I could only add it as a tab. So what should I do? Can you help me? How can I downgrade? It does not work in Wear OS 5. |
Beta Was this translation helpful? Give feedback.
-
FAQI accepted the latest Galaxy Watch 7 update. How do I use Wear Installer 2? How do I use xDrip+ watchface? How do I use non-WFF watchfaces?You cannot. Samsung has removed the capability. How do I revert the update?You cannot. The firmware image isn't anywhere online currently, XDA forums or otherwise. What do I do then?Options
I miss xDrip+ watchfaceGlucoDataHandler isn't that bad. In some ways it's better. Just try it out. I'm here because I googled "wear installer 2" or "watchface runtime" and also have Galaxy Watch 7 issuesSorry, this page is exclusively about the app xDrip+ so we cannot help with other apps - please ask in your apps github discussions instead TY Oh my god why so many emailsI'll close this thread. Samsung did what it did. I don't expect things to change at this point. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Update: #3581 (comment)
OLD THREAD BELOW:
——
I bought a Samsung Watch 7 (only $59 on Prime day!), but sadly the xDrip watchface gives a "made for an older OS" error. The xDrip prefs, snooze, etc all work on the watch, just no watchfaces. It appears Google announced a year ago that all older watchfaces not following the new "Watch Face Format (WFF)" cannot be used on any watch that ships with Wear OS 5.
Are there any short term plans to add compatibility? Or am I better off not holding my breath, and just return this watch to go back to my old one?
Either way, thanks for all the hard work everyone does!
Beta Was this translation helpful? Give feedback.
All reactions