+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Arch Linux on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=159)
+---- Thread: No audio on calls after using wired headset (/showthread.php?tid=17695)
No audio on calls after using wired headset - Zebulon Walton - 12-06-2022
I noticed today that when using a wired headset, after making the first call with it all audio stops working on calls both incoming and outgoing. When this happens there are no audio devices listed in the sound section of settings, everything is just greyed out. Rebooting the phone fixes it until you use the headset again. (This is Arch+Phosh running from an SD card, updated as of yesterday.)
RE: No audio on calls after using wired headset - cone99 - 12-07-2022
(12-06-2022, 07:33 AM)Zebulon Walton Wrote: I noticed today that when using a wired headset, after making the first call with it all audio stops working on calls both incoming and outgoing. When this happens there are no audio devices listed in the sound section of settings, everything is just greyed out. Rebooting the phone fixes it until you use the headset again. (This is Arch+Phosh running from an SD card, updated as of yesterday.)
This issue is a major pain in the butt. I get it regularly after making or receiving a call.
You can issue...
Code:
pulseaudio -k && pulseaudio --startto reset it, rather than rebooting. I did try a cron job with this in but using 'pulseaudio --check' still returns '0', even when it's messed up and assigned the 'dummy' audio device.
I've never used PA in 16 years of using Linux, just ALSA, so if there's a PA user out there who could please advise on the correct method for checking when this happens, then please do! I'll try and find some time to investigate further myself.
RE: No audio on calls after using wired headset - Zebulon Walton - 12-07-2022
(12-07-2022, 08:01 AM)cone99 Wrote: You can issue...
Code:pulseaudio -k && pulseaudio --start
to reset it, rather than rebooting. I did try a cron job with this in but using 'pulseaudio --check' still returns '0', even when it's messed up and assigned the 'dummy' audio device.
Thanks, that pulseaudio reset sounds like the best approach for now. It would be easy enough to run a script from an icon on the screen to do that.