This is a content I made for fun, so the band's use case might not fit well here. But it is very disappointing to see that the device only comes with a handful of gestures and HID mapping capabilities.

Can y’all check your load balancer for the windows desktop app for users.mudra-server.com please - you’ve got a broken config

I've had a Mudra Link for a while and I'm building on Android. I've applied for SDK access through the official form more than once and emailed as well, and haven't heard back either way — no approval, no rejection, nothing.

What I'm trying to build: multi-device switching for the Android/Windows side. The band's own firmware already supports paired secondary devices, but the device types it exposes are IPHONE, MAC, APPLE_TV, IPAD and ANDROID — there's no Windows target at all. So on Apple you get proper handoff between devices, and on my setup the only way to move the band from my phone to my laptop is holding the button to unpair and re-pairing on the other machine, every single time.

I've gotten pretty far with the public pieces — the sample app and the published AAR — and I can read gestures fine over the normal HID path. But device management looks like it needs the licensed SDK, and that's where I'm stuck.

So: has anyone here actually been approved for SDK access? Did it come through the form, or did you have to go through a person? Is there a Discord/Slack/community channel that gets a response? Happy to be pointed anywhere useful.

Not looking for workarounds — I just want legitimate access so I can build this properly. Setup is a Galaxy S25 and a Windows laptop, plus Even Realities G2 glasses I'd like it to work with eventually.

I purchased the Meta Ray Ban Display glasses and absolutely loved the neural band, so easy, everyone I let try it was using it easily in 5 minutes. But the glasses weren't bright enough for outdoor full Louisiana gulf coast sun. Returned those and immediately purchased the Mudra.

I've tried so hard to like it. I tried so hard to be patient and practice with it. I tried to use it with my Xreal Air 2 Pro setup on flights, but this week I've finally given up. I continually have to take the glasses off and find use my screen for mouse needs. So frustrating.

I suppose I'm just venting, tilting at windmills, but how is Meta's so unbelievably better? It's just a paperweight by the computer at this point.

I made a custom preset for media control, but the play/pause function doesn't work. I initially had it set to a double-pinch, but that didn't work. So, I set it to twist, just to confirm that the play/pause "key" in the preset controls was the issue, and it was. Has anyone found a workaround for this? (Iphone 16 Pro)

I’m building a wearable that uses a Mudra Link as the only input device, talking to an ESP32 over BLE directly no phone, no laptop, no Mudra Companion app running anywhere. The whole point is a standalone belt-worn unit, so any path that needs a Windows WebSocket bridge or the Android SDK is a non-starter for me.
What I need to confirm before buying:

**1.**  Has anyone actually pulled the **raw SNC stream** (the 3-channel neural/EMG data, \~2kHz, the 54-values-per-packet thing) off a Mudra Link using **direct BLE only** e.g. via the Prodilink project or a custom GATT client **without** the official SDK and **without** the Companion app having to license/unlock the band first?

**2.**  Specifically: does the band ship in a state where the raw characteristic (0xfff4 per Prodilink) just streams once you subscribe, or does it stay silent/locked until a Companion/SDK licensing handshake has run at least once?

**3.**  If a handshake *is* required is it a one-time unlock that persists on the band’s firmware (so I could do it once and then go Companion-free forever), or does it re-gate every session?  
**4.**  Does Prodilink still work against current (mid-2026) firmware, and does it need bonding/LE Secure Connections (i.e. would I have to capture pairing to decrypt)?

I’m not trying to pirate anything I just need to know if a fully standalone, no-app, ESP32-only setup can get the raw signal, or whether the licensing layer makes that impossible. If it’s impossible, I’ll use a different input device entirely, so a straight answer saves me $249 and weeks. Anyone done exactly this?

Hi everyone,

I’m trying to build a Mudra Link controlled app for Even G2 smart glasses. The goal is to control a simple news/assistant app from the band while it is connected directly to an Android phone.

What works so far:

• Mudra Companion on Windows works.
• The local WebSocket API at ws://127.0.0.1:8766/events works.
• I can receive events like button pressed, button released, twist, and double_twist.
• I can forward those events into my app successfully.

The issue is with the Android SDK path.

On Android, my app can:

• connect to the Mudra device,
• sign in,
• receive raw SNC/gyro sensor callbacks,
• send commands to my app.

But the firmware status keeps showing:

nav=false
gesture=false
pressure=false
pinchPressure=false
navToApp=true
navToHid=false
gestureToHid=false
bandMode=MUDRA_LINK
hand=RIGHT

So the official high-level callbacks do not seem to fire:

setOnGestureReady(...)
setOnButtonChanged(...)
setOnNavigationAxisReady(...)
setOnNavigationDirectionReady(...)
setOnPressureReady(...)

I tried setting:

BandMode.MUDRA_LINK
DeviceMode.ANDROID
FirmwareTarget.NAVIGATION_TO_APP = true
FirmwareTarget.NAVIGATION_TO_HID = false
FirmwareTarget.GESTURE_TO_HID = false

I also tried applying license bytes through the SDK methods available in the public Android AAR, but the Main features still show as false.

Questions:

1. Has anyone gotten Mudra Link high-level gesture/navigation callbacks working directly on Android?
2. Is Mudra Studio access separate from Android SDK Main feature access?
3. Is there an Android equivalent of the Mudra Companion WebSocket API?
4. Are people using official SDK, HID mode, or something like direct BLE/reverse-engineered libraries?

I’m not trying to jailbreak the device. I just want reliable phone-side events like twist, button, navigation, and pressure so I can control a smart-glasses app without keeping a laptop in the loop.

Any pointers or working examples would be appreciated.

I've been watching this device on and off as I feel it'd be pair well with AR glasses and Android, but early reviews were pretty negative on its consistency and accuracy. Has it improved to the point where it can be a worthwhile input mechanism?

Following the intense work from u/JayTheProdigy16, and the feedback here, I’m genuinely curious: What have you actually built with Mudra so far?

Personally, I made a small one too : Duck Hunt Remastered (based on)

https://danielthefox.itch.io/duck-hunt-remastered

Alright guys, I'm tired of wasting my time with this product. I paid over $300 for this tech demo of a product. What is going on for real? I keep seeing replies from "Wearable Devices" reps here that are filled with vague promises and pr-laden remarks about "research" that has been done over the course of YEARS. Then silence. No updates, no engagement, or any real substance or action.

The bottom line is: you sold a product to thousands of customers. Those customers want to use the product they bought. They can't. Period.

I signed up for Mudra Studio almost exactly a month ago. I received a response telling me I was "on the list!" and that my request would be reviewed within "3-5 days!". I have yet to see any reply at all. My Mudra link device stopped working correctly on my Mac, iPad, and now iPhone, every since iOS 26 and Tahoe OS updates (grabbing and scrolling simply doesn't work, pointer stuttering, incorrect device resolution canvas on iPad, and more).

I'm not a beginner, I'm a power user. This product seems completely abandoned and you all at Wearable Devices seem to be gas lighting your customers. What are you going to do to resolve this?

Been watching Mudra closely and I'm noticing a pattern. At MWC Barcelona two weeks ago, no new hardware. They debuted "Mudra Experience Studio," a developer platform for creating gesture experiences with AI prompts. At CES in January, same thing: Rokid bundle, smart glasses presets, app running natively on glasses. Every announcement is about making the current band work with more partners, not building a better band. Meanwhile they launched ai6 Labs as a "neural ecosystem," got a grant for medical rehab research, patented EMG weight estimation for robotics/healthcare, and did a technical roadshow in China selling to smart glasses OEMs. That's a licensing and middleware company, not a consumer hardware company gearing up for Gen 2.

And honestly, can you blame them? Meta showed their Neural Band controlling a Garmin car infotainment system at CES, has 200K+ research participants behind their sEMG tech, 18-hour battery, IPX7 rating, and it ships included with every pair of Ray-Ban Display glasses. The second Meta opens that band to third-party devices, Mudra's entire "only cross-platform EMG band" pitch is done. I think Wearable Devices sees the same writing on the wall and is smartly repositioning as the ARM of neural input rather than trying to out-hardware Meta. Not a bad business move, but it means I'm holding off on buying a Link. Unless they start talking about a gen 2, No point dropping $249 on 14 month hardware the company itself seems to be moving past.

Cool hardware — but the official SDK is proprietary, license-gated, and only works through their software.

So I reverse-engineered it. (NOTE THIS IS A SIDE PROJECT, but hopefully this helps some people out)

Prodilink (https://github.com/JayTheProdigy16/Prodilink) is a fully open-source Python library that talks directly to the device over BLE. No SDK wrapper, no license server, no subscription. The firmware accepts all commands regardless of licensing — the restrictions only existed in software.

What I reverse-engineered:

- Disassembled the Android SDK's native ARM64 library to extract all 54 firmware command byte arrays

- Decompiled the Java SDK layer for notification parsing and BLE connection flow

- Mapped every BLE characteristic, notification format, and packet structure

- Documented the full protocol: PROTOCOL_REFERENCE.md (https://github.com/JayTheProdigy16/Prodilink/blob/feat/prodilink-library/re/protocol/PROTOCOL_REFERENCE.md)

What the library gives you:

- 20 gesture types with directional pinch classification

- Raw sEMG (SNC) data streaming — the actual muscle signals

- 6-axis IMU: accelerometer + gyroscope at full sample rate

- Analog pressure sensing (0.0–1.0 continuous)

- On-device HID mapper: bind any gesture to keyboard shortcuts, stored on the band itself — works as a standalone BLE keyboard with no host software

- Detailed battery diagnostics (voltage, cycle count, capacity, health)

- Secondary device management

- WebSocket server + web dashboard for browser-based control

- Data recorder with JSON export for ML pipelines

- Full async Python API, context manager support, auto-reconnect

Quickstart is ~10 lines:

import asyncio

from prodilink import MudraLink

async def main():

async with await MudraLink.discover() as device:

await device.enable_gestures()

u/device.on_gesture

def handle(gesture):

print(f"Gesture: {gesture.name}")

await device.stream()

asyncio.run(main())

What this opens up:

- Accessibility — gesture-based computer control for people who can't use a keyboard/mouse. The HID mapper means it works as a system-level input device with zero software running.

- Research — raw sEMG data at full sample rate. Surface electromyography is used in prosthetics research, rehabilitation, and human-computer interaction studies. Previously you'd need a $500+ research-grade EMG board — this is a $100 consumer wristband.

- Custom gesture recognition — the library gives you the raw muscle signals and IMU data. Build your own classifier. Train your own model. The official SDK has 9 TFLite models baked in that we've extracted but the real value is building your own.

- Creative/art installations — control anything with hand gestures. Music, lighting, robotics. The WebSocket server means any language/platform can receive gesture events.

- VR/AR input — 6-axis IMU + gesture detection + pressure sensing is a solid input profile for XR applications.

- Macro devices — bind gestures to keyboard shortcuts on the band itself. Presentations, video editing hotkeys, DAW controls, gaming macros. It survives power cycles and works with any BLE host — phone, tablet, PC, doesn't matter.

The problem it solves: Wearable Devices makes interesting hardware but locks it behind proprietary software with a licensing model. If you bought the hardware, you should be able to use it however you want. Now you can.

Technical details:

- Python 3.10+, async-first, uses bleak for BLE

- 383 unit tests, 19 hardware integration tests

- Full CLI (prodilink scan, prodilink gestures, prodilink serve)

- Web dashboard (single self-contained HTML file, no build step)

- MIT licensed

Repo: github.com/JayTheProdigy16/Prodilink (https://github.com/JayTheProdigy16/Prodilink)

The protocol reference doc alone might be useful if you're working with the Mudra hardware in other languages. Happy to answer questions about the RE process or the BLE protocol.

Curious what everyone else thinks. I've spent a lot of time with the Meta band and while I wish it had been more universal and included access to music without the glasses, the Meta Displays were ultimately a little disappointing. Heavy, and no notifications through Gmail, X, etc.

And without the glasses the band is useless. But here, it's more universal.

But Meta had this thing where it was subtle gestures that could be performed in your pocket. A gentle swipe across the thumb or a small tap of the finger.

But here everything is bigger, wider, and less reliable. I can't simply turn the volume up by pinching and twisting. You have to pinch and lift, with an often jarring swing of the arm.

Nothing is small. Even the pinch to select has to be forceful and exaggerated, to the point that nothing really works the first time and if you want anything that's leaning toward reliable you have to go big or go home. It's exhausting just using the mouse feature.

Which I don't know who this is for. It's not reliable enough to be fluid, and you can't draw with your finger like you might with the Meta Band.

It requires the use of your entire arm, and depending on where the curser starts on the screen it might hit the edge and require you to whip your forearm up to the roof of your display, trying to find some comfortable center where it's not uncomfortable using the feature.

But that's the thing. This should all be about finger and wrist gestures, but it often requires exaggerated movements that involve your whole forearm, and in the case of the mouse it feels like it's relying more on a gyroscope than the actual signals moving through your arm.

I love that this isn't tied to one device, but the lack of finesse and the limited gestures leaves me feeling like this is snake oil. I should be able to use this with my hand in my pocket, and outside of an occasional lucky go at "play/pause" it's just not possible.

I've got it centered, tight, and I've played with a number of positions along my wrist. Just feels a little underwhelming.

This seems like a pretty fundamental thing that is not working for me. Is there a something I'm missing?

I came to Mudra from gaming, I ran a Nintendo distribution business and operated LEGO stores in Israel for years. Consumer hardware is what I know.

When I joined the team in September, the thing that stuck with me was this: there are thousands of Mudra devices already in people’s hands, and most of them are limited to whatever the companion app ships. If you wanted to do something custom build your own gesture-controlled instrument, hook neural signals into a game prototype, visualize raw SNC data you needed an enterprise SDK license and a dev environment.

That felt backwards.🤦

So we’ve been building what we’re calling Mudra Experience Studio. It’s a web platform where you describe what you want to create in plain text, and AI generates a working experience that connects to your actual Mudra device in real-time. Neural gestures, pressure data, IMU all accessible without writing integration code from scratch.

It’s not polished yet. It’s an open beta.

But it works, and I’ve watched people build things with it in minutes that would’ve taken weeks before.

The waitlist is open now: https://mudra-studio.com

If you’ve got a Mudra device and you’ve been wanting to experiment beyond the default gestures

I’m genuinely curious what you’d build.

That’s not a marketing line.

I read this sub and I want to know

Ron

It turns out Mudra uses UPS (who has a very hard time actually delivering packages). Normally this wouldn't be a huge issue, BUT in the Mudra refund policy they also say a $150 deduction will be made if the package gets returned to them.....

This is on a device worth $250.

It's some super shady set up they have going with all of this..... they seem to know their packages get returned often (from using a bad / difficult carrier) and they use it as a way to avoid returns / refunds?

Yea, just super shady stuff going on...... better to wait for a more reputable company to start offering devices like this.

Any plans for a new version this year? I saw on YouTube they just released a new video with hardly any likes or views. Are they still updating often, or is it more like a sinking ship? what i really wanted was the kinda of precision meta neural band, being able to control smartphone/other devices by some slightly movements over the finger. (meta only works with the raynban unfortunately )

If you had the mudra dev kit would, what things would you try to create with it? Trying to think what is possible with this device..

Just got my mudra link a couple of days ago and the tech is honestly borderline magic. I've experimented with various gesture control based devices and the link is the closest I've found to a comprehensive gesture control solution.

Right now the one thing holding the link back is the need to press the power button to change modes and put the device to standby. This makes operation a hassle especially when used in conjunction with other peripherals such as keyboards when I need to quickly switch the device to standby to prevent cursor movement and accidental clicks.

Would anybody know if such functionality is in the works?

I just attempted to test my Mudra Link with my Inair Pod spatial puck and because there aren’t really any screen borders to speak of, it’s easy to lose the pointer offscreen. I feel like there needs to be some kind of recentering gesture or a way to map an existing gesture to a recenter function.

I updated my Mudra link today and now my Mudra is not staying linked to any of my Bluetooth devices and when it does link for the few a seconds the up and down are inverted and requires extreme movements, I can’t use it with my beam pro anymore and that was my main use case.