Context: Calling for Rokid system-level permission opening
Hi clawsses community ๐ โ first, huge thanks to @dweddepohl and contributors for keeping the upstream alive. I've been running clawsses (forked) on Rokid Glasses (Android 12, device 1901092534012176) for 2 months building a personal AI assistant project that goes beyond the Lingzhu+SSE path. After hitting hard system-permission walls, I'm filing this issue to gather community voice โ not as a bug report against this repo, but to coordinate developers who hit the same blockers.
Cross-posted to Rokid official forum (link will be added once published): forum.rokid.com
Why this is bigger than clawsses alone
clawsses (and OpenClaw) does the right thing within the Lingzhu sandbox โ eyes/ears/mouth via official protocol, brain swappable. But the next tier of wearable AI needs:
- Custom TTS voice / emotion (not the default Lingzhu voice)
- Raw environment audio access (cricket sounds, laugh detection, emotion-from-tone)
- Custom HUD rendering (black background + AR overlays โ Lingzhu APP UI is white-bg, unreadable on transparent display)
- AI-initiated push (proactive notification when something matters)
- Continuous ambient listening (meeting auto-summary, passive memory)
- Gesture recognition via camera frames (hands-busy paging)
- Custom wake-word engine (Picovoice / sherpa for higher accuracy)
- Word-trigger ASR flush (e.g. "over"/"ๅฎๆฏ" to send immediately)
None of these are achievable through Lingzhu protocol โ they all need system-level APP installation.
The blockers (verified by 3 rounds of probe APKs)
| Blocker |
Evidence |
| WiFi auto-start at boot |
Cold reboot + 4.5min: WifiState=0, wlan0 no IP. Rokid's own launcher doesn't auto-enable either |
| User can't manually enable WiFi via touchpad |
Rokid launcher hides Settings โ WiFi entry, touchpad cannot navigate there |
WifiManager.setWifiEnabled permanently false on Android 10+ |
Non-system-signed APK |
Settings.Global.WIFI_ON deprecated since API 31 |
Writes succeed but no system effect |
Runtime.exec("svc wifi enable") from APK |
Subprocess inherits APK uid, blocked by IPC |
| AccessibilityService path |
rootInActiveWindow=null + getWindows()=[] (Rokid blocks AS window enumeration). dispatchGesture works but glasses have no touchscreen โ Settings UI uses D-pad model only |
INJECT_EVENTS for keyboard injection |
Requires system app permission |
| Bootloader nominal-unlocked but inert |
verifiedbootstate=orange + vbmeta=unlocked + flash.locked=0, but adb reboot bootloader silently restarts back to Android โ fastboot/recovery entries shut by Rokid in init |
Asks to Rokid (any one would unblock the community)
- A: Platform key signing for verified developer APKs (post-review)
- B: Bootloader unlock tool / unlock token (Xiaomi-style, developer assumes risk)
- C: Specific API exposure:
setWifiEnabled for cert'd APKs + an official "auto-enable WiFi at boot" system toggle + documenting the AIDL of SpriteWifiService (it's exported=true with no permission, hint of intended 3rd-party use)
- D: Explicit "we will not open this" โ so we can decide product strategy (stay on Lingzhu vs switch hardware platform)
Why post here
developer@rokid.com (footer of Rokid forum) bounces โ internal mailing list. Rokid's GitHub orgs (rokid/*) have been dormant since 2019, all issues unresolved. Active venues:
- https://forum.rokid.com (their own forum) โ main post linked above
- dcg-bd@rokid.com (BD email, found via dcg.rokid.com)
- This community (clawsses + OpenClaw) โ to coordinate same-blocked developers
If you've hit the same walls, please ๐ / comment with your scenario. The more developers visibly affected, the higher the chance Rokid will respond.
Context: Calling for Rokid system-level permission opening
Hi clawsses community ๐ โ first, huge thanks to @dweddepohl and contributors for keeping the upstream alive. I've been running clawsses (forked) on Rokid Glasses (Android 12, device 1901092534012176) for 2 months building a personal AI assistant project that goes beyond the Lingzhu+SSE path. After hitting hard system-permission walls, I'm filing this issue to gather community voice โ not as a bug report against this repo, but to coordinate developers who hit the same blockers.
Cross-posted to Rokid official forum (link will be added once published): forum.rokid.com
Why this is bigger than clawsses alone
clawsses (and OpenClaw) does the right thing within the Lingzhu sandbox โ eyes/ears/mouth via official protocol, brain swappable. But the next tier of wearable AI needs:
None of these are achievable through Lingzhu protocol โ they all need system-level APP installation.
The blockers (verified by 3 rounds of probe APKs)
WifiManager.setWifiEnabledpermanently false on Android 10+Settings.Global.WIFI_ONdeprecated since API 31Runtime.exec("svc wifi enable")from APKrootInActiveWindow=null+getWindows()=[](Rokid blocks AS window enumeration).dispatchGestureworks but glasses have no touchscreen โ Settings UI uses D-pad model onlyINJECT_EVENTSfor keyboard injectionverifiedbootstate=orange+vbmeta=unlocked+flash.locked=0, butadb reboot bootloadersilently restarts back to Android โ fastboot/recovery entries shut by Rokid in initAsks to Rokid (any one would unblock the community)
setWifiEnabledfor cert'd APKs + an official "auto-enable WiFi at boot" system toggle + documenting the AIDL ofSpriteWifiService(it'sexported=truewith no permission, hint of intended 3rd-party use)Why post here
developer@rokid.com(footer of Rokid forum) bounces โ internal mailing list. Rokid's GitHub orgs (rokid/*) have been dormant since 2019, all issues unresolved. Active venues:If you've hit the same walls, please ๐ / comment with your scenario. The more developers visibly affected, the higher the chance Rokid will respond.