WearOS 5 compatability discussion (Galaxy Watch 7 & Pixel Watch 3) #3581
Replies: 10 comments 17 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.
-
|
I couldn't get it to work on the Pixel Watch 3 either :( It fails at the step where (after you install the apk to the watch) in Wear Installer 2, you go to Third Party Apps > Xdrip+ > Install watch faces |
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.
-
|
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:/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:/notifications/unsubscribe-auth/A63YKNREZTSCUVG6DW6OZ5TZXPLD5AVCNFSM6AAAAABLJPBJZOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANZQGIYDOOI>
.
You are receiving this because you commented.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
I've been working on and completed 4 watch faces, that are oversized for visually impaired, but you need glucodatahandler.. Check it out here https:/sderaps/DMM |
Beta Was this translation helpful? Give feedback.
-
Update: xDrip works great on Galaxy Watch 7 (for now) using the method here #3581 (comment)
unfortunately Pixel Watch 3 users are out of luck.
——
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