InfiniTimeOrg / InfiniTimeOrg/InfiniTime
BLE connection request notifications
Open
Nobody has claimed this yet.
feature request
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Verification
- I searched for similar feature request and found none was relevant.
Pitch us your idea!
In case we keep support for unpaired/unverified devices, we could show a notification like the one for incoming calls with the name of the other device for an incoming BLE connection request. Thus, every connection would be at least known and wanted.
Contributor guide
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 existing incoming-call notification and the BLE connection-request handling in the firmware. Compare how the other device is identified, then define the notification behavior for unpaired or unverified devices. Done means an incoming BLE request produces a notification naming the other device without accepting unwanted connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100