Public Alpha Test: Audio Without Compromise - Volumio on Bookworm Begins

Volumio Development Volumio Beta Testing
, , , ,
485

@Rui_C Good news, again thanks. You helped locating a typo in the existing code, which caused the ALC897 spdif unmute to fail
It would not have worked for other codecs either, but probably these codecs did not come with spdif being muted to begin with (not all codecs have an ‘IEC958,16’ mixer, most only have ‘IEC958’).
This has been fixed, it should make the next version, if not, it will be in the one after that.

1 Like
486

Hey @SimonE,

Thanks for the detailed follow-up. Noted:

  • OTA update to 0.069 on Pi 4 with 7" screen v1.1 and Topping D10s completed fine.
  • GUI worked immediately, but screen and NAS needed power cycles to recover.
  • After full power restarts, everything tested OK: Spotify, NAS, Bandcamp, Soundcloud, Web Radio, YouTube Music, Touch Display, Now Playing, Bluetooth, Play Here, Multiroom.

Also glad to hear the download issue is resolved. We’ll treat the screen behavior as hardware-related for now.

Kind Regards,

487

Hey @Robert.Hecht,

Thanks again for confirming the successful OTA to 0.069 and your thorough testing - this is invaluable.

Regarding the Tidal Connect playback issue:

Analysis

Your log clearly shows consistent buffer underruns during Tidal Connect playback:

[audio_output_buffer.cpp:25] Tried to write 9216 samples, but wrote 8820

This type of message indicates truncated buffer writes - effectively a streaming underrun - which matches the distorted, reverberating sound you’re hearing. Additionally, we see:

[PlaybackControllerImpl.cpp] Illegal state:1
Ignore play request because playback state is not STARTED

This reflects a misalignment between the internal state machine and the actual playback state — potentially a race condition or state desync in VTCS.

Status as of 0.069

This aligns with the current Known Issues for v0.069:

TIDAL Connect – under developer review

So you’re not alone in seeing this - it’s already acknowledged by the dev team and actively under investigation.

Next Steps

Your log and audio description have been forwarded to the developers. Depending on how the investigation progresses, we may follow up with specific test cases or a patch build for validation. I’ll keep you posted.

Thanks again for your detailed report and support.

Kind Regards,

488

Hey @njaustin123,

Thanks a lot for your encouraging feedback and for testing both Pi 4B and Pi 3B+ setups. Glad to hear YT Music and YouTube Cast are working well on Bookworm - we know how frustrating that YT Music gap has been.

Regarding the Waveshare 7" DSI Touchscreen Rotation

To help us properly investigate and support rotation issues on your Waveshare 7-inch DSI screen, we need a bit more detail to avoid guesswork. Waveshare offers several 7" DSI-compatible models, and each behaves slightly differently depending on firmware overlays and kernel DRM behavior.

Could you please provide the following:

  1. Exact model number of the screen (printed on PCB or sticker), or link to:

    • Waveshare Wiki for that screen
    • Purchase page or datasheet if available

  2. System information:

    • Full log link from Volumio after reproducing the issue:
      Please go to http://volumio.local/dev, click “Send Log or Bug Report”, and paste the URL here.

  3. Output of these shell commands (via SSH):

    cat /proc/cmdline
cat /boot/config.txt
cat /boot/userconfig.txt

We’ll use this to confirm whether display_lcd_rotate=2 or KMS overrides are the cause, and suggest the right fix. We’re actively validating DSI touchscreens as part of the Bookworm BETA process and your data will directly help improve support.

Kind Regards,

489

Hey @jocoman,

Thanks for the detailed info and screenshots - they’re extremely helpful.

We’ve reviewed everything and can confirm that your current working setup (Volumio 3.799) is using kernel 6.6.62-v8+, where your TP-Link Archer T3U Plus (2357:0138) is correctly handled by the rtl8822bu driver.

For Volumio .069, just to clarify - it uses the Raspberry Pi official kernel 6.12.27-v8+, and this kernel does include the rtw88_8822bu module by default. So this is not a missing driver issue.

Instead, the problem may be:

  • The module not being loaded automatically at runtime,
  • USB port-related initialization issues (especially on USB 3.0),
  • Or a problem in how the USB device is being recognized or bound.

To investigate properly, we’d like you to run a controlled test:

Test Procedure (Two USB Ports)

  1. Power up the Pi without the dongle connected.

  2. Plug the Archer T3U Plus into one of the USB 2.0 ports (black port on the Pi 4).

  3. Wait about 5 - 10 seconds after insertion.

  4. Visit http://<your-volumio-ip>/dev and click Send Log or Bug Report.

    • Copy and save the debug log URL.

  5. Reboot the Pi again with the dongle unplugged.

  6. This time, plug the dongle into a USB 3.0 port (blue port on the Pi 4).

  7. Wait another 5 - 10 seconds.

  8. Again, go to http://<your-volumio-ip>/dev and submit a second log.

    • Copy and save this second debug log URL.

These logs will allow us to:

  • Verify if the correct kernel modules are being triggered,
  • Identify differences in USB behavior between ports,
  • Catch any errors during device initialization or binding.

Once we have both URLs, we’ll review and get back to you with next steps.

Kind Regards,

490

Mate, i’m very glad that i could help…
If you’re happy with my help, i’m very happy for help you.

You can ask me for other issues, just tell me, 'i’ll try my best.

Offtopic: Is it save to replace 3.807 for 0.069 version? I know it’s in alpha stage, but seems very solid…

491

I sent you 2 url’s of logs . thanks

492

Hey @jocoman,

Thanks for the update! We haven’t seen the two debug log URLs posted yet - could you please share them here so we can analyze what’s happening when your TP-Link Archer T3U Plus dongle is connected to USB 2.0 vs USB 3.0?

If you’re not sure how to generate or retrieve those logs, here’s the official Volumio instruction page for reference:
https://help.volumio.com/help/how-to-send-a-log-link-for-a-bug-report

To recap the steps:

  1. Boot your Pi without the WiFi dongle plugged in.

  2. Insert the dongle into a USB 2.0 port (black port on the Pi 4), wait 5 - 10 seconds.

  3. Open a browser and go to:
    http://<your-volumio-ip>/dev
    Click “Send Log or Bug Report”, then copy and share the log URL here.

  4. Reboot again, this time plug the dongle into a USB 3.0 port (blue port), wait again.

  5. Visit the same http://<your-volumio-ip>/dev page, submit the second log, and share that URL here too.

Once we have both logs, we’ll be able to confirm whether the driver is loading correctly, how the device is handled across ports, and identify any firmware or binding issues. This also helps align your case with other community members testing similar Realtek-based WiFi dongles in this thread - particularly where USB port behavior has played a role.

Looking forward to reviewing those logs.

Kind Regards,

493

http://logs.volumio.org/volumio/J7MehtY.html

http://logs.volumio.org/volumio/7bjN5M9.html

494

going to install and test Volumio-0.069-2025-05-23-pi today we will see what will happen :slight_smile:

  • install finish
  • youtube working nice
  • touchdisplay working for 50% i can not get the keyboard to work because chromium is not letting me use it ? any idee how to get it working ?

thx all

20250524_090813
20250524_0908131884×4080 400 KB

495

Hey @jocoman,

Thanks for sharing both logs:

We’ve reviewed them carefully.

In both cases, the system references wlan0, but there’s no evidence that your TP-Link Archer T3U Plus is ever bound to that interface. There are kernel messages indicating rtw88_8822bu loaded, and signs that the interface was created (e.g., wlan0: renamed from ...), which we would expect from a USB WiFi dongle attaching correctly.

Since Volumio always uses wlan0, it’s highly likely that the onboard WiFi interface is grabbing it first, leaving no available slot for the USB dongle. This may be blocking the Realtek device from being initialized or usable.

Suggested Next Step

Disable the onboard WiFi to let the USB dongle claim wlan0. You can do this by adding the following line to:

/boot/userconfig.txt

Add:

dtoverlay=disable-wifi

Then reboot.

This will prevent the internal WiFi from starting and should free up wlan0 for the USB adapter — assuming the module binds correctly. Once that’s done, re-run the same USB 2.0 and USB 3.0 tests and resubmit the debug logs for review.

This approach has helped other users in this thread who were testing different Realtek-based USB WiFi adapters and seeing similar symptoms.

Kind Regards,

496

Hey @DoNaLdDuck,

Status: On-screen Keyboard on Volumio-Bookworm (Chromium Kiosk)

  • The Touch Display plugin on Bookworm uses modern Chromium (v118+).
  • Chromium dropped support for Manifest V2 extensions.
  • The on-screen keyboard plugin previously used was built with Manifest V2 and is therefore non-functional.
  • The original plugin developer has not updated it to Manifest V3.
  • No functional Chromium extension exists for on-screen keyboard under the current Chromium based Volumio environment.

Conclusion

There is currently no working on-screen keyboard solution integrated or compatible with Chromium under the Touch Display plugin in Volumio Bookworm builds. This will remain the case until someone ports the keyboard plugin to Manifest V3 or implements an alternative that is not workaround-based.

Kind Regards,

1 Like
497

Hi, I install v0.068 on rasbery pi 5. Everything works for me (youtube cast receiver plugin, youtube music plugin). Can I update to version 0.069 without rewrite new image? In update settings get a message you`re already on the last version. Test mode on in dev settings.

498

Fresh install v0.069 on a 2nd Volumio system
Logs

Pi4B booting to SSD
Output device HDMI
Wired connection

Tested, all OK:

  • Touch Display
  • Now Playing
  • Music sources: Spotify, Web Radio, Bandcamp, local music files
  • Time/date ok
  • Access GUI via wired and wifi connections
  • Working as a NAS to another Volumio system
  • Play Here & multiroom
  • Bluetooth pairing

All good!

499

Thank you for the reply.

This is the display

Command outputs below:

cat /proc/cmdline
coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=2C:CF:67:05:40:92 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 quiet console=ttyS0,115200 console=tty1 imgpart=UUID=68b923ad-5431-41eb-9208-ae82d0557a20 imgfile=/volumio_current.sqsh bootpart=UUID=99C0-8768 datapart=UUID=539217d3-3606-4533-bd39-fadf6d2c5c91 uuidconfig=cmdline.txt pcie_aspm=off pci=pcie_bus_safe rootwait bootdelay=7 logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa= snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 loglevel=0 nodebug use_kmsg=no

cat /boot/config.txt
### DO NOT EDIT THIS FILE ###
### APPLY CUSTOM PARAMETERS TO userconfig.txt ###
initramfs volumio.initrd
gpu_mem=128
gpu_mem_256=32
gpu_mem_512=32
gpu_mem_1024=128
max_usb_current=1
[pi5]
usb_max_current_enable=1
[all]
include volumioconfig.txt
include userconfig.txt

cat /boot/userconfig.txt
# Add your custom config.txt options to this file, which will be preserved during updates

#### Touch Display rotation setting below: do not alter ####
lcd_rotate=2
display_hdmi_rotate=2

Link to the Log (Touch display Issue)

500

Dear @nerd , team,

today my volumio proposed next update (didn‘t see an announcement here but may missed it)

Update (OTA) to 0.069 has again worked without any problem - reboot still worked directly.

(HW) Config:
Pi5,
Raspi 2 Display (DSI),
BT remote &
Two rotary encoders on several GPIOs

Testing:

  • Spotify plugin, works (my only use case).
  • Touch display (and corresponding plugin) works
  • Rotary encoders are working
  • BT remote is working
  • WiFi is working (can access from laptop / phone).
  • “Now Playing” plugin works

Great work, again!

Regards,
Ralf

501

Hey @njaustin123,

Thanks again for the detailed report. Based on your setup using a Raspberry Pi 4B with the Waveshare 7-inch DSI touchscreen, here’s the proper fix to resolve the display rotation issue under Bookworm:

Issue

  • Touch input rotates correctly - this is handled by legacy input rotation (lcd_rotate=2).
  • Display output does not rotate - because Bookworm now uses KMS (Kernel Mode Setting), which ignores lcd_rotate for DSI displays.

Fix for Display Rotation (KMS-Based)

1. Edit /boot/userconfig.txt and add:

dtoverlay=vc4-kms-v3d
dtoverlay=vc4-kms-dsi-7inch

These overlays enable KMS graphics and initialize the DSI1 display used by your Pi 4B.

2. Edit /boot/cmdline.txt

At the very beginning of the single-line file, prepend:

video=DSI-1:800x480M@60,rotate=180

Ensure the rest of the line stays intact - all parameters must remain space-separated on a single line.

3. Reboot the device

About Touch Input

You can keep:

lcd_rotate=2

in userconfig.txt for now to preserve touch input orientation. While this no longer affects the display output under KMS, it may still influence touch calibration under Xorg, which is often used by the Touch Display plugin.

If you notice touch input becomes misaligned after fixing display rotation, we can assist with setting a transformation matrix using xinput or libinput.

Let us know how it goes - this will help improve default support for DSI displays in the Bookworm builds.

Kind Regards,

502

@Rui_C With an alpha version, nothing is safe, with beta you would get an already fairly well tested version, with a RC you’re more or less safe. But that is my opinion.
Surely it depends on how much time you would have to invest to re-install 3.8xx.
If the alpha version has what you need, and you are happy with re-installing 3.8xx in case the alpha goes south, nobody will stop you.
In the end it is something you need to decide for yourself.

503

Hey @gariklihodey,

You’re absolutely right to ask before proceeding - here’s the accurate breakdown based on how ALPHA channel updates are handled.

You’re running version v0.068 of Volumio on a Raspberry Pi 5, which is part of the ALPHA testing channel. This version includes a predefined sentinel file that locks your system to the ALPHA OTA update path.

When you enabled Test Mode under Developer Settings, your system switched to the BETA OTA channel instead. Since no BETA build corresponds to this alpha series, the system reports:

“You’re already on the last version.”

This is expected behavior due to the mismatch between your installed build’s OTA channel and the channel now being checked.

To receive the v0.069 update via OTA:

  • Disable Test Mode in Developer Settings
  • Reboot your system
  • Check for updates again

If your build is unmodified and correctly set to the ALPHA channel, and the 0.069 OTA has been published, it will appear and install normally. Manual re-flashing is not required.

Kind Regards,

504

Hey @rkorell,

Thanks once again for your excellent and detailed feedback!

We can confirm that v0.069 (May 23, 2025) is the current Alpha version, fully documented in the changelog post. This update is eligible for OTA rollout from v0.067 onwards, and your successful transition confirms that the process is working as intended.

Appreciate you verifying stability across your setup:

  • Pi5 + Raspi 2 DSI Touch
  • Dual GPIO rotary encoders
  • Bluetooth remote
  • Spotify and “Now Playing” plugins
  • Full Wi-Fi access

We’re currently finalizing the next testing milestones, and your feedback remains a critical reference point. Keep it coming.

Kind Regards,

1 Like