Skip to content

Releases: Holy-Coders/muse-launcher

Muse Launcher 0.7.1 — reply bubbles and tray mirroring

Choose a tag to compare

@AaronDovTurkel AaronDovTurkel released this 14 Oct 20:51

Muse replies now appear in swipeable chat bubbles above the avatar, with the avatar docked bottom-left looking up.

Optional Hide mirrored Android notifications retains private launcher bubbles while dismissing ordinary clearable Android tray alerts. Calls, alarms, full-screen and ongoing alerts keep their system presentation. Mirrored bubbles survive listener reconnect and can be swiped or cleared. Android may still sound/show the first source alert before the listener receives it. This setting is off by default.

Pairing documentation now distinguishes initial setup from daily use. The current Android BLE flow still requires Muse on a second phone for initial authorization. Afterward the launcher connects directly over the internet. Same-phone or desktop-assisted Android provisioning is not shipped; existing Mac pairing adapters pair Mac gadgets.

Validation: 58 core tests, 204 Python tests, debug/release builds and both lint checks pass. Five Jelly Star / Android 13 targeted tests pass, including real source-notification cancellation, persisted bubble retention, protected call/alarm categories, notification/reply layout and swipe dismissal. The firmware-bound optional physical-button gate is preserved; this does not certify locked/background activation on other devices.

Android 11+, 64-bit arm64 or x86_64. Community prerelease. Bring your own personal Muse SDK token; no credentials, personal media, custom avatar or signing key included. Source builds fetch caption models separately. Use the checksums file from the same directory as the APK and source archive.

Muse Launcher 0.7.0 — community preview

Choose a tag to compare

@AaronDovTurkel AaronDovTurkel released this 14 Oct 20:32

Muse Launcher turns a spare Android phone into a companion for your own Muse.
This is an independent, credential-free community preview by Holy Coders.

Install

Download muse-launcher-0.7.0.apk below and open it through Android's installer.
Android 11+ with a 64-bit arm64/x86_64 system is required. Pairing requires your
own personal Muse SDK token, BLE advertising support and Muse on a second phone.
No root or red button is needed. See the installation and privacy guides in the repo.

Controls

  • Tap your avatar once to record, then again to send.
  • Hold the avatar and release to send; double tap opens camera.
  • Info opens gesture instructions; Settings includes status updates and optional Developer mode.
  • Notification bubbles appear above the avatar, docked bottom-left and looking up.
  • Custom avatars get locally generated procedural animation; generic profiles use the built-in companion.
  • Photos/videos attach to the next voice request. Standalone video also sends locally extracted embedded audio; no describe-video request is added.

Verification and limits

58 core tests and 204 protocol tests pass. Six clean Android 15 emulator tests
and five Jelly Star UI tests pass, including native touch cancellation, avatar
movement during a hold, developer controls, Info, animation generation and
notification positioning. A generated video/audio test verifies that Muse follows
the spoken request inside the clip and recognizes both visual phases.

Hardware keys remain optional and must be physically calibrated on each phone.
Locked/background key activation is not universally supported or certified.
32-bit Android is unsupported; other manufacturers still need device testing.
Video is SD, capped at 8 MB; video audio is bounded to 60 seconds. Captions are
local English, and read-aloud uses Android voices. Native Muse push delivery is
not established; notifications use optional Android listener access.

The app contains no maintainer token, personal avatar, account data or signing key.
Muse service use remains subject to its personal, non-commercial token terms;
this is not an approved commercial or app-store integration. Puck-compatible
internal package/protocol identifiers are retained for update/data continuity.