Same issue here…
Only restart is working…
Same issue here -for over a year!- with my XA2 single sim, KPN.
Already since Sailfish OS Seitseminen 3.1.0.11 when i wasn’t really aware so reboots might have solved it at that time.
Since than i went through every available update, right now i’m still @ 3.3.0.16 awaiting the fixed 3.4.0.22 but the “no audio in either direction issue” is always there !
Rebooting -even several times- doesn’t make any difference …
The only inconvenient way to make a phonecall is by use of the build in handsfree loudspeaker so everybody in my vicinity could join my conversation …
Pretty useless for a phone right ?!
Will this EVER get fixed ?!?
@Franksz:
Please, try the following if you are confident in using the command line and a simple text editor. If you have never used the developer mode before then do not try.
Find a short how-to in https://jolla.zendesk.com/hc/en-us/articles/202011863 and in https://jolla.zendesk.com/hc/en-us/articles/360010391013
devel-su
cp /usr/lib/systemd/system/pulseaudio.service /usr/lib/systemd/system/pulseaudio.service.original ## save the original - just in case
cat /usr/lib/systemd/system/pulseaudio.service ## glance thru the file if you want
vi /usr/lib/systemd/system/pulseaudio.service ## edit the file
Look for the following 3 lines in the editor (they should be from line #18 onwards):
Restart=always
RestartSec=1
Type=notify
Add the following command immediately after those three:
TimeoutStartSec=120
Save the change and exit the editor. Check the file content to be sure the editing session worked:
cat /usr/lib/systemd/system/pulseaudio.service
Restart the phone.
Should there be a need to return to the original you should give the following commands:
devel-su
cp /usr/lib/systemd/system/pulseaudio.service.original /usr/lib/systemd/system/pulseaudio.service ## get the original back (let it overwrite)
reboot
9 Likes
@jovirkku :
Thanks for yor detailed reply i sadly haven’t used developer mode before.
I know where to enable it , i’m not a digital moron but for now this might be a step too far.
I might need a little how to for this or will this become clear once i’ve enabled Developer mode ?
[root@XperiaXA2 nemo]# cat /usr/lib/systemd/pulseaudio.service
cat: can't open '/usr/lib/systemd/pulseaudio.service': No such file or directory
This is on a freshly flashed XA2 running 3.4.
These are the installed pulseaudio services, which one should I edit as per your suggestion?
[root@XperiaXA2 nemo]# find /usr/lib/systemd/ | grep pulseaudio
/usr/lib/systemd/user/pulseaudio.service
/usr/lib/systemd/user/pulseaudio.socket
/usr/lib/systemd/user/user-session.target.wants/pulseaudio.service
/usr/lib/systemd/system/pulseaudio.service
/usr/lib/systemd/system/emergency-call.target.wants/pulseaudio.service
Edit: looks like your intent is the systemd/system service (just missed it in your first step). I have tried this edit and will report back. It will also be good to know what the systemd/user service gets used for, if anything.
1 Like
Yes, indeed. Thanks for pointing it out. How embarrassing to have a clear mistake in one’s instructions… Arghh.
I have fixed the 1st command of my post now.
3 Likes
Yeah, it seems to be common enough. I have this issue I’d say on about 25% of my calls. I don’t make or receive that many calls so it’s difficult to say, but it has caused me significant issues by missing important calls that have taken some time to arrange, and that can’t simply be remade after rebooting.
It’s been happening for me on my XA2 for at least the past two major updates. When it happens, the problem is consistent, seems isolated to just calls (WhatsApp, media etc. still work fine), and doesn’t go away until I reboot the phone. I’m still on 3.3, and was hoping that this would be fixed in 3.4 but that doesn’t seem to be the case. I know voice calls aren’t what they used to be, but it’s still a pretty fundamental bug, that a phone can’t be relied upon for, you know, phone calls.
2 Likes
Thank you for your reply. So it seems quite common if it is happening with device. I hoped it could be something which I can work around with Audio Output Chooser like head phone problem earlier, but it seems not.
I’m wondereing if it could be depending on operator.
With my J1 I’m experiencing mobile data problems after changing operator. Even when mobile data is connected nothing gets transfered. After swithing mobile data off and on I get “Limited connection” status. After this I have to turn it off, enable and disable flight mode and then enable mobile data again.
This seems to happen in morning and possibly because Situations turns mobile data off and network mode to 2G over night. This is of course just a thought.
When I reach the required forum trust level (3 days now…) I am going to add a poll to the initial post here to see if we can see what % of XA2 users and what variants are affected by this issue. It was a great idea to start looking in to that. Figuring out operators will probably be a bit much to poll via the forum but we can start talking about that as this thread gets more traction 
1 Like
Thank you for that. I really apreciate it. My original idea was to make poll as my reply and I was making sure it’s ok to you since this is your topic, but adding it to topic is much better. 
Taking closer look of polls, I’m not sure how they should be build. Looks like they need to be separate polls. So I’m made proof-of-concept polls below to see how it works. I made them with Show who voted option. Hopefully that way it’s possible to keep answers together.
Edit: I closed polls as it looks like they work as intended.
Sailfish version
- 3.0.3
- 3.1
- 3.2
- 3.3
- 3.4
0 voters
XA2 variant
- Normal
- Plus
- Ultra
0 voters
Having call audio issue?
- Yes
- No
0 voters
Hi @jovirkku,
I am also having the “no sound” issue on X10 dual sim 3.3.0.16 (Rokua).
I just added the lines to the pulseaudio - but a “no sound” situation just occurred again, I did not even try to make a call.
When i press start in csd-tool loudspeaker test: i get the following in journalclt -af
Oct 11 18:18:38 Xperia10-DualSIM kernel: glink_tx_common: 110 callbacks suppressed
Oct 11 18:18:38 Xperia10-DualSIM kernel: apr_audio_svc_lpass_smem: glink_tx_common: R[0]:68 Intent not present
Oct 11 18:18:38 Xperia10-DualSIM kernel: __apr_tal_write: glink_tx failed, rc[-11]
Oct 11 18:18:38 Xperia10-DualSIM kernel: apr_audio_svc_lpass_smem: glink_tx_common: R[0]:68 Intent not present
Oct 11 18:18:38 Xperia10-DualSIM kernel: __apr_tal_write: glink_tx failed, rc[-11]
Oct 11 18:18:38 Xperia10-DualSIM kernel: apr_audio_svc_lpass_smem: glink_tx_common: R[0]:68 Intent not present
Oct 11 18:18:38 Xperia10-DualSIM kernel: __apr_tal_write: glink_tx failed, rc[-11]
Oct 11 18:18:38 Xperia10-DualSIM kernel: apr_tal_write: Unable to send the packet, rc:-11
Oct 11 18:18:38 Xperia10-DualSIM kernel: apr_send_pkt: Write APR pkt failed with error -11
Oct 11 18:18:38 Xperia10-DualSIM kernel: afe_set_lpass_clk_cfg: AFE clk cfg failed with ret -11
Oct 11 18:18:38 Xperia10-DualSIM kernel: afe_set_lpass_clock_v2: afe_set_lpass_clk_cfg_v2 failed -22
Oct 11 18:18:38 Xperia10-DualSIM kernel: msm_sdw_codec 152c1000.msm-sdw-codec: __msm_sdw_reg_read:failed to enable the INT_MCLK1
Oct 11 18:18:38 Xperia10-DualSIM kernel: __msm_sdw_reg_read: 10 callbacks suppressed
I additionally recognized that the proximity sensor and the light sensor in CSD -Tool did not give any readings!
May this be connected to https://together.jolla.com/question/193485/any-workaround-for-malfunctioning-proximity-sensor-xa2/ or https://together.jolla.com/question/225772/xperia-10-plus-no-audiosound-with-new-log/ ?
What logs / outputs can I give you the next time the error occurs to give more usefull information?
Thank you a lot,
this solve my problem of muted encryption: https://together.jolla.com/question/226333/missing-sounds-in-xperia-x-rokua-330-encrypted/
Hi all,
Before i jump into the developer mode part (@jovirkku ) i will wait for next update.
Reading about the CSD-tool above i tried some testing as well and i figured out that
the Receiver playback test failed !
I’m wondering right now if that’s a hardware failure ?
Microphone up and down (for what it means ?) worked fine after a reboot.
Anyone familiar with this failure ?
Edit… that part seems to be solved now by inserting and extracting headphones as read in a german post
I’m also experiencing no sound during phonecalls (other sounds seem allright).
3.4.0.24 on XA2
EDIT: now after 5 restarts of the phone I have sound in phonecalls again.
I tried the systemd unit-file manipulation above but it doesn’t seem to help.
systemctl status pulseaudio reports it as inactive (dead). Not sure if that in itself is abnormal as I’ve not had a reason to check it on this phone before…
Please, let’s try to keep this discussion here on voice problems during phone calls (not being able to hear what the people involved in a phone call say). Missing sounds (beeps, ringing tones, etc.) is a different thing and should be handled in a dedicated bug.
1 Like
If the receiver playback test (in CSD) fails then the so-called receiver or earpiece (the sound-producing component at the top part of the phone, that is supposed to be next to one’s ear during a call) might be defective. In particular, if you can never hear what the remote party says during a phone call (but you can hear that via the HF loudspeaker at the lower part of the phone).
Sorry, that is just bad language. It means the microphones at the top and bottom parts of the phone.
Well, that is from year 2016. Sailfish has changed a lot since then, and there are new devices in use. But if there is an audio routing error somewhere, connecting/disconencting a headset might help to correct the routing.
In normal use this is totally normal. System Pulseaudio is only used for emergency calls in the black unlocking UI that opens home encryption. You are probably more interested in user session Pulseaudio which you can query with systemctl-user status pulseaudio.
2 Likes
OTA update today to Pallas tunturi 3.4.0 => totally muted and not able answer (open) call. Similar phenomena as privious update with added encryption. This is not any missing beeb or alarm sound at the moment. Have to probably fix with tihis pulseaudio…
Same here only reboot helps. no ring no voice no speakers , have to reboot then all fine