Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions ROADMAP.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,11 @@ keyboard sends it over MIDI, the way a hardware tone module does.
- A tuner, and several effect slots with saved presets, so Stompbox is more
than one airwindows effect at a time.

## Bluetooth Receiver

- Calls' audio through the speaker and microphones on ESP32-S31 boards, once
that chip's Bluetooth controller carries a call's audio link reliably.

## Clock

- More faces on the clock, and a way to pick a face that's saved.
Expand Down
57 changes: 50 additions & 7 deletions apps/btreceiver/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,9 @@ speaker. Pair a phone or a computer with it and play anything. The screen
shows the cover large, and beside it everything the sender says: title,
artist, album, track number and count, genre, where the track is up to, and
the codec and rate of the stream. A line the sender leaves empty isn't shown.
With **Phone calls and battery** turned on, the board is also the phone's
hands-free unit: its battery and signal show at the top, and its calls show
on the screen.

## On a board

Expand All @@ -21,11 +24,11 @@ needs audiodsp's `audiometer`; without it the app plays with no spectrum.
Made for an 800 x 480 screen. The cover and its buffers take about 350 KB,
so it wants a board with PSRAM.

![Bluetooth Receiver on an ESP32-S31 board with a 4.3-inch screen: the track beside its cover (blurred here), the phone's battery at the top right, and shuffle and repeat both lit](docs/images/board.png)
![Bluetooth Receiver on an ESP32-S31 board with a 4.3-inch screen: the track beside its cover, the Phone calls and battery switch on at the top right, and the phone's signal bars and battery above the title](docs/images/board.png)

Here it runs on an ESP32-S31 board with a 4.3-inch screen. Shuffle and
repeat were turned on from the phone, and the buttons on the board follow
them.
Here it runs on an ESP32-S31 board with a 4.3-inch screen, with Phone calls
and battery turned on. The phone had no mobile service when this was
taken, so the status reads No service.

## Use it

Expand All @@ -42,8 +45,21 @@ track, marked with a small 1. Each lights in the screen's colour while it's
on, and follows the phone when you change it there. A phone that doesn't
report them shows neither.

The phone's battery shows at the top right whenever the phone reports it,
amber when it runs low, and a weak signal is shown beside it.
The phone's battery shows at the top right whenever its player reports it,
amber when it runs low, and a weak Bluetooth link is noted beside it.

## Phone calls and battery

The switch at the top right, **Phone calls and battery**, is off until you
turn it on, on every board, and the board remembers it the next time the app
opens. Off, the board is a speaker and nothing more.

On, the board also connects as the phone's hands-free unit, the way a car
kit does. The phone's battery and its signal show at the top right while it's
connected, the battery amber when it runs low, and its calls show on the
screen ([Calls](#calls) below). The phone gives these over its hands-free
link, so allow Calls for the board in the phone's Bluetooth settings. A
computer has no hands-free side, and shows neither.

Closing the app lets the phone go.

Expand Down Expand Up @@ -71,6 +87,33 @@ volume sits beside the play button.

![A long title on two lines, with the battery icon in amber at the top right and no shuffle or repeat](docs/images/long.png)

## Calls

Calls come to the board with Phone calls and battery turned on.

![An incoming call: a card over the player with a thin handset in rings, the caller's number large, and red decline and green answer rings](docs/images/incoming.png)

A call shows a card over the player with the caller's number, and the phone
pauses its music. Answer it on the card and the call plays through the
board's speaker while the board's microphones go to the phone; decline it
and the card goes.

![An answered call: the number, the call's time, and thin mute, use phone and red hang up rings](docs/images/call.png)

While you talk, the card counts the call's time. Mute turns the board's
microphones off, Use phone takes the call back to the phone (and Use speaker
brings it back), and Hang up ends it. When the call ends the music plays
again where it was. The call's audio needs a board whose `pcm_in` records
while `audio_out` plays; on one that can't, you hear the caller but they
can't hear you, and the card says so.

On an ESP32-S31 board the call's audio stays on the phone for now, because
that chip's Bluetooth can't yet carry it reliably. The card still shows the
caller, and answers, declines and hangs up; you talk on the phone, and the
card says so. The same goes for any board whose `HandsFree.call_audio` is
False, such as the Pico W. On an ESP32-S31 board with the setting on, a
call made through an internet calling app on the phone can reset the board.

## On a computer

On a computer, with no `btclassic`, the app plays a demo: a pretend phone
Expand All @@ -82,7 +125,7 @@ PYTHONPATH=lib python -c "import appkit; appkit.run('btreceiver')"
```

`BTRECEIVER_DEMO` holds the demo in one state (`pairing`, `idle`,
`playing`, `paused`, `nocover` or `long`), and
`playing`, `paused`, `nocover`, `long`, `incoming` or `call`), and
[`tools/shots.py`](tools/shots.py) saves a picture of each in
[`docs/images`](docs/images), where this page's pictures live:

Expand Down
Loading