A2. Choose CXR-M or CXR-L, and pay that path's cost
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 66
Description
CXR-L requires the Hi Rokid app installed on the phone (package check → AuthorizationActivity → bindService). CXR-M requires a Rokid developer clientSecret/accessKey plus an AES serial-number handshake. Decide which dependency the product accepts, and register for developer credentials if CXR-M.
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 with ISSUES.md and inspect the CXR-L path through the package check, AuthorizationActivity, and bindService; for CXR-M, review the clientSecret/accessKey and AES serial-number handshake requirements. Done means selecting one dependency path and completing its stated app, hardware, or credential prerequisite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- embedded-iot, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100