A4. Evaluate `onAiKeyDown` as push-to-talk
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 66
Description
It is the only input event CXR-M delivers to the phone. Measure press-to-capture latency, repeat behaviour, and whether the built-in assistant intercepts the key first.
Blocks: #spec-voice-no-text-entry (push-to-talk requires an explicit wearer action).
Section A — Hardware verification (needs a Rokid device). Registered from ISSUES.md.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the TypeScript entry point for onAiKeyDown and read ISSUES.md, then test the event on a registered Rokid device. Measure press-to-capture latency, repeat behaviour, and whether the built-in assistant intercepts the key first. Done means recording those results and determining whether the event supports the explicit wearer action required by #spec-voice-no-text-entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100