Skip to content

Vascular load and antioxidant index do not work. #11

Closed

Description

@shadow019

Hello! I went through the setup process on my Galaxy Watch 8, but the "vascular load" and "antioxidant index" options aren't working. Instead, a message appears stating: "This feature requires a Galaxy Watch 8, Galaxy Watch Ultra, or newer models." Is this just a typical error that can occur right after installation, or do these two features actually not work?

Image

Activity

  1. FacuM commented on Oct 18, 2026

    @FacuM
    Contributor

    Hello, that's quite an interesting issue. Let me get that checked!

  2. added
    bugSomething isn't working
    confirmedThe reported issue was confirmed
    needs responseWaiting for maintainer response
    on Oct 18, 2026
  3. FacuM commented on Oct 18, 2026

    @FacuM
    Contributor

    Hey OP @shadow019, is this on Health+ or on the official app?

  4. shadow019 commented on Oct 18, 2026

    @shadow019
    Author

    It's on the Samsung Health+ version. The Labs version of both of them came pre-activated automatically through the normal process. I've tried deactivating and reactivating them to see if it works, but neither worked.

    Image
  5. FacuM commented on Oct 18, 2026

    @FacuM
    Contributor

    6. It's on the Samsung Health+ version. The Labs version of both of them came pre-activated automatically through the normal process. I've tried deactivating and reactivating them to see if it works, but neither worked.

    Hmm, this is a limitation of the mod, unfortunately.

    Please try these mitigations:

    • Log in on both Health apps (official and the mod with your Samsung account)
    • On both apps, again, head over to Settings and scroll to the Privacy section.
    • Consent to all of the collection toggles
    • Force-close and restart both apps, or restart your phone.
    • Open the official app, check that it's synced and the vascular load data shows up. If that's good, Health+ should start working in about 7 days.

    I understand that this implementation sounds like the biggest bullshit in the world, and that's because it is. I'm working on something better but it needs a fair bit of work (even for an AI model), as it requires a lot of back-and-forth and manual testing with the hardware.

    I encourage you to refer to #9 for additional information and updates.

    I'm closing this one for now as it's not a bug but rather a criminally terrible (but known and expected) limitation on the implementation. Of course, feel free to hit me up again if you want to talk more about this or if you feel like my decision is not correct.

    Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingconfirmedThe reported issue was confirmed

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions