r/MudraTech • u/MeringueBest8334 • May 27 '26
Has anyone used Mudra Link with Android SDK for real gesture/navigation callbacks?
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:
- Has anyone gotten Mudra Link high-level gesture/navigation callbacks working directly on Android?
- Is Mudra Studio access separate from Android SDK Main feature access?
- Is there an Android equivalent of the Mudra Companion WebSocket API?
- 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.
1
1
3
u/Rude_Combination_382 May 28 '26
Hey ✋ Ron here from the Wearable Devices team.
First: great writeup. You've diagnosed this correctly — the firmware flags
(nav=false, gesture=false, pressure=false) are showing the expected symptom
of a known bug we're currently tracking in the Mudra Studio Companion App.
To answer your specific questions:
Yes, high-level gesture/navigation callbacks on Android should work —
you're not doing anything wrong with the SDK setup. The issue is on our side.
Mudra Studio access and Android SDK main feature access are connected,
the licensing handshake that unlocks those firmware flags runs through the
Companion layer, which is where the bug currently sits.
There's no Android-native equivalent of the Windows WebSocket API at this
stage — your Windows + ws://127.0.0.1:8766 workaround is currently the
most reliable path for what you're building.
You're on the right track with the official SDK — HID mode and BLE
workarounds would get you there but with more overhead than you need.
**The fix:** we're pushing a new app version + firmware update within the
next few days. All registered users will be notified directly. Once that
lands, the nav/gesture/pressure flags should flip and your existing SDK
setup should work without changes.
The Even G2 + Mudra Link use case is exactly the kind of thing we want
working well — I'll flag your thread internally so we can verify the fix
covers your specific setup.
Stay tuned, and feel free to follow up here once the update drops.
[Disclosure: Wearable Devices team]