Skip to content

fw/applib/ui/vibes: add per-segment amplitude control to public SDK#833

Open
mdrunk wants to merge 1 commit intocoredevices:mainfrom
mdrunk:feature/vibe-amplitude-control
Open

fw/applib/ui/vibes: add per-segment amplitude control to public SDK#833
mdrunk wants to merge 1 commit intocoredevices:mainfrom
mdrunk:feature/vibe-amplitude-control

Conversation

@mdrunk
Copy link

@mdrunk mdrunk commented Feb 16, 2026

Expose vibration motor intensity control to apps via a new vibes_enqueue_custom_pattern_with_amplitudes() API. The internal syscall (sys_vibe_pattern_enqueue_step_raw) and hardware drivers already support per-step strength values; this bridges the gap in the public SDK.

Also fix a pre-existing issue where active vibration patterns were not explicitly stopped on app exit by adding
sys_vibe_pattern_clear() to the app cleanup path.

Copy link
Member

@jplexer jplexer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

is there a way to re-do ci? @gmarull

@gmarull
Copy link
Member

gmarull commented Feb 17, 2026

lgtm

is there a way to re-do ci? @gmarull

rebase

@mdrunk
Copy link
Author

mdrunk commented Feb 18, 2026

lgtm
is there a way to re-do ci? @gmarull

rebase

so is this something that I need to do? I'm pretty good with code, but absolute trash with github, which is why claude is involved with this PR at all.

@gmarull
Copy link
Member

gmarull commented Feb 18, 2026

just git rebase against upstream main, then force-push

@mdrunk mdrunk force-pushed the feature/vibe-amplitude-control branch 2 times, most recently from d34f702 to 2f53622 Compare February 18, 2026 20:05
@gmarull
Copy link
Member

gmarull commented Feb 19, 2026

please adjust commit title to e..g. fw/applib/ui/vibes: ...

@mdrunk mdrunk changed the title vibes: add per-segment amplitude control to public SDK fw/applib/ui/vibes: add per-segment amplitude control to public SDK Feb 19, 2026
@mdrunk mdrunk marked this pull request as draft February 19, 2026 22:01
@mdrunk mdrunk force-pushed the feature/vibe-amplitude-control branch from 2f53622 to d5c14a7 Compare February 19, 2026 23:09
Expose vibration motor intensity control to apps via a new
vibes_enqueue_custom_pattern_with_amplitudes() API. The internal
syscall (sys_vibe_pattern_enqueue_step_raw) and hardware drivers
already support per-step strength values; this bridges the gap
in the public SDK.

Also fix a pre-existing issue where active vibration patterns
were not explicitly stopped on app exit by adding
sys_vibe_pattern_clear() to the app cleanup path.

Signed-off-by: Jeremy Lambert <jeremylambert@gmail.com>

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mdrunk mdrunk force-pushed the feature/vibe-amplitude-control branch from d5c14a7 to 7cd4f6e Compare February 19, 2026 23:11
@mdrunk mdrunk marked this pull request as ready for review February 19, 2026 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments