You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
AirPods Pro 3 stay silent after walking out of range and back (link stays, pause and play brings the sound back) #132
When I walk away from the player and come back, the sound stops and does not come back. The link stays connected: play, pause and skip work and the time runs on, but the AirPods are silent. The only recovery is pause, wait a few seconds, play.
Steps:
Play music to AirPods Pro 3.
Walk out of range until the sound drops, then come back.
The sound never comes back. Pause for about 3 s, then play: the sound comes back.
Not the cause: Wi-Fi is off on the player during normal use, ear detection is off, the iPhone's Bluetooth is off, and the AirPods connect to the iPhone only "When Last Connected to This iPhone".
File type
FLAC, MP3
How often?
Every time
Since when?
For two days I have owned the player and played around with it.
Error report
Install ID 0E2C6817, sent at 20:54 CET (19:54 UTC) on 2026-11-13, while the AirPods were silent and before any pause.
Anything else
This looks like F43/F69 (#99), but caused by a radio stall instead of a pause or a skip. Walking away stalls the link without a disconnect, so the stream stays started, and the AirPods get a gap longer than their buffer. After that they stay silent, even when packets come again. Pause, wait, play brings the sound back because it suspends the stream and starts a new one.
A possible fix: after a long stall, restart the stream the same way a pause does. I have not tested this.
Thanks for the very clear report and the analysis, which matches what I see.
Your report shows the player side was clean while the AirPods were silent: no errors and no gaps, and the link was still up. When you walk out of range, the radio stops sending for a few seconds without disconnecting. When it can send again, the stream carries on but the AirPods stay silent, and only a new stream start (pause, then play) wakes them.
Your fix idea (start the stream again after a long stall, as a pause does) is the right one. It needs the Bluetooth service to tell the player that a long stall happened, which it can't do yet. That touches the Bluetooth path for every pair of headphones, so I want to do it carefully and test it with AirPods out of range before it goes out. It's planned, and I'll post here when there's a build to try.
Thanks again for the precise report and the offer to test. I looked into the stream restart we talked about. During such a stall Reborn's writes keep flowing (your report shows no underrun and no blocked write), so the player can't notice the stall from the music side. Doing it inside the Bluetooth service would change the stream for every pair of headphones, and I can't test it reliably, so I'm not going to risk breaking Bluetooth for everyone. Pause, wait a moment, play stays the way to wake them up. (Small note: your report shows Wi-Fi was on at the time, at -70 dBm.)
Where we are: Y2Linux already does what a phone does: it lowers the data rate when the link struggles, keeps Bluetooth off the Wi-Fi channel, lets Wi-Fi rest while music streams, limits the catch-up after a dropout and fills gaps with silence. I've worked through every Bluetooth report again, and the player's side is clean in all of them. What's left is the hardware: the Y2 has one small radio that shares its antenna with Wi-Fi, and it just can't hold a link the way a phone can. We've reached the ceiling of what software can do here.
Honestly, if you want music without dropouts on the Y2, I'd recommend wired headphones.
Beta 9.3.34 adds one last thing: each stall of the Bluetooth link is now written down, so if something new ever shows up, a report will say when and how long. More in the 9.3.34 report. I'm closing this; thanks a lot for the reports and the patience.
Activity
SchulzCode commentedon Nov 17, 2026
Thanks for the very clear report and the analysis, which matches what I see.
Your report shows the player side was clean while the AirPods were silent: no errors and no gaps, and the link was still up. When you walk out of range, the radio stops sending for a few seconds without disconnecting. When it can send again, the stream carries on but the AirPods stay silent, and only a new stream start (pause, then play) wakes them.
Your fix idea (start the stream again after a long stall, as a pause does) is the right one. It needs the Bluetooth service to tell the player that a long stall happened, which it can't do yet. That touches the Bluetooth path for every pair of headphones, so I want to do it carefully and test it with AirPods out of range before it goes out. It's planned, and I'll post here when there's a build to try.
atmamont commentedon Nov 17, 2026
Great, I'll be waiting. Let me know if you need my help testing your builds before officially releasing them.
SchulzCode commentedon Nov 19, 2026
Thanks again for the precise report and the offer to test. I looked into the stream restart we talked about. During such a stall Reborn's writes keep flowing (your report shows no underrun and no blocked write), so the player can't notice the stall from the music side. Doing it inside the Bluetooth service would change the stream for every pair of headphones, and I can't test it reliably, so I'm not going to risk breaking Bluetooth for everyone. Pause, wait a moment, play stays the way to wake them up. (Small note: your report shows Wi-Fi was on at the time, at -70 dBm.)
Where we are: Y2Linux already does what a phone does: it lowers the data rate when the link struggles, keeps Bluetooth off the Wi-Fi channel, lets Wi-Fi rest while music streams, limits the catch-up after a dropout and fills gaps with silence. I've worked through every Bluetooth report again, and the player's side is clean in all of them. What's left is the hardware: the Y2 has one small radio that shares its antenna with Wi-Fi, and it just can't hold a link the way a phone can. We've reached the ceiling of what software can do here.
Honestly, if you want music without dropouts on the Y2, I'd recommend wired headphones.
Beta 9.3.34 adds one last thing: each stall of the Bluetooth link is now written down, so if something new ever shows up, a report will say when and how long. More in the 9.3.34 report. I'm closing this; thanks a lot for the reports and the patience.
atmamont commentedon Nov 20, 2026
Gotcha! Sad but true, I completely understand the reasoning. Thanks for getting back with an explanation.