No audio output device found – Kindle PW6 (Gen 12)

[Samplik]

Trying to play text to audio via Piper TTS and error appears: "No audio output device found" regardless of whether my Air Pods are connected via bluetooth to Kindle.

ls -l /dev/snd
seq
timer

Device: Amazon Kindle PW6 (Gen 12)
OS version: 5.17.1.0.4
KOreader version: 2026.03
Audiobook Read-Along version: 0.1.6.5

audiobook-benchmark-20260515-131035.txt

playermgr_2291_007-juno_17010004_sangria_bellatrix4-435197_crash_May_15_13.13.29_2026.txt

[stradichenko]

Hi, Thank you for sharing the information, expect a follow up and probably a first patch the following week.

cheers :D

[Samplik]

Thank you, I'm looking forward to it. If you need any additional information or tests, please let me know. I can give you my direct contact.

[stradichenko]

Thank you; there has been some fixes to the report generator but probably will have to wait a couple of days more since I'm working on many new features, and will postpone any new release until they are finished.

Cheers :D

[stradichenko]

Hi @Samplik, please try again on the v0.1.9; hopefully this time you will be able to create a report.

Cheers.

[Samplik]

playermgr_2181_007-juno_17010004_sangria_bellatrix4-435197_crash_May_23_17.09.02_2026.txt
Indexer_Dump_1779545343136.txt
audiobook-benchmark-20260523-141102.txt

[Samplik]

The same error on v0.1.9.7. If you need any test (terminal for example), let me know.

[Samplik]

Your plugin is compiled for a newer Linux userspace. But Kindle PW Gen 12 has the old glibc 2.18. It is libonnxruntime.so that is incompatible and this is the reason. It is necessary to rebuild ONNX Runtime for glibc 2.17/2.18 to make it work. Audio stack Kindle working. Thanks to Chat GPT for this investigation.
It might make sense to create a short manual for the Kindle, attaching this file to replace it in the plugin, when you compile it.

[stradichenko]

Hi @Samplik v.0.1.13.0 has had an update on this issue for devices with an older gllibc version. Try it on v01.13.0, and if the issue persists at least you should be able to generate a report. Is debugging week so I hope we can solve it within the following days!

Cheers.