Repository navigation
Bluetooth Receiver: shuffle and repeat buttons that follow the phone's player - #197
Merged
Merged
Conversation
bdbarnett
force-pushed
the
btreceiver-repeat-shuffle
branch
from
November 20, 2026 19:59
9a7dfcf to
9145ae5
Compare
…s player The phone's shuffle and repeat show above the volume, lit in the screen's colour while on, and a tap changes them on the phone. Repeat steps from off to all tracks to one track, marked with a small 1. A phone, or a firmware, that doesn't report them shows neither, and the volume stays beside the play button. Checked with tests/btreceiver_contract.py on CPython and unix MicroPython: the buttons' colours, the taps' effect on the demo phone, a change made on the phone, and both hidden with a phone that doesn't report them.
Taken from the board's framebuffer while it played from a phone with shuffle and repeat on; the album cover is blurred.
…l readout The signal and its No service note come from the hands-free link, which this app doesn't read yet; the AVRCP battery stays.
bdbarnett
force-pushed
the
btreceiver-repeat-shuffle
branch
from
November 20, 2026 22:50
021ecd6 to
7c1160a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bluetooth Receiver gets shuffle and repeat buttons above the volume slider. They show the phone's player modes and change them: tap shuffle to turn it on or off, and repeat to go from off to all tracks to one track, marked with a small 1. A button lights in the screen's accent colour while its mode is on, and follows the phone when you change it there. A phone that doesn't report its modes shows neither button, and the slider keeps its place.
The icons are iconkit's outline repeat and shuffle, tinted rather than filled.
This needs
AudioSink.repeat,AudioSink.shuffleand theSETTINGSchange bit from PyDevices/omnipython-builds#600. On firmware without them the app reads None and shows no buttons. The demo phone reports modes in its playing and paused states and none for the long title, and the contract test covers each case, taps included.Tested on an ESP32-S31 4.3-inch board running main with #600, playing Spotify from a Samsung Galaxy S21. Taps on the board took repeat from off to all to one track and back to off, and turned shuffle on and off. Spotify's controls followed each tap. Changes made in Spotify reached the board within a few seconds, including shuffle from Spotify's Shuffle / Smart Shuffle sheet. The README now has a screenshot taken from that board's framebuffer, with the album cover blurred.
The board screenshot was taken with the hands-free work of #196 also running, so the phone's signal readout it showed is painted out here; this PR doesn't add it. The demo screenshots were made again from this branch. The contract test passes on CPython.