~phartman 1 year, 6 months ago

What device is this?

On Fri, May 19, 2023 at 04:12:19PM +0000, ~euhmeuh wrote:

Hello ! I waited quite some time before updating to 1.13 because I know for sure I get issues when updating too soon... Alas, I still got screwed up by the update T_T

sxmo is unable to switch to callaudiod, which makes calls impossible, and I can't even hang up the call because the audio crash makes the hang up script fail too.

I investigated a little and found that the call to :

dbus-send --session --print-reply --dest=org.mobian_project.CallAudio /org/mobian_project/CallAudio org.freedesktop.DBus.Properties.Get string:org.mobian_project.CallAudio string:"AudioMode"

returns correctly uint32 0 (which means Normal mode)

but calling :

dbus-send --session --print-reply --type=method_call --dest=org.mobian_project.CallAudio /org/mobian_project/CallAudio org.mobian_project.CallAudio.SelectMode uint32:1

returns org.freedesktop.Dbus.Error.Failed: Operation failed

without further explanation...

I tried starting callaudiod myself with debug enabled like so : killall callaudiod && G_MESSAGES_DEBUG=all callaudiod

but it keeps spamming the logs with callaudiod-pulse-CRITICAL: No suitable card found, retrying in 3s...

I can correctly switch profiles and play with the sound using pavucontrol though, but the whole calling logic in sxmo still fails because it expects the dbus call to succeed.

The sound cards are correctly shown by alsa. I also did the pactl unload-module module-suspend-on-idle trick.

Also, I uninstalled sxmo-common-bluetooth, sxmo-common-audio-pipewire and installed sxmo-common-audio-pulse.

I also checked that pipewire was not running.

Any ideas ? That's kinda important for me to find a solution because I can't have phone calls at all right now :/

-- View on the web: https://todo.sr.ht/~mil/sxmo-tickets/575

-- sic dicit magister P https://phartman.sites.luc.edu/ GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)

~phartman referenced this from #575 1 year, 6 months ago

~bgkillas 1 year, 6 months ago

i have this issue on the pinephone pro postmarketos edge

~euhmeuh 1 year, 6 months ago

Oopsie, forgot to mention that's the pinephone on postmarketos edge.

~phartman 1 year, 6 months ago

Just as an FYI, running pinephone on pmos edge and I do not experience this. That said, I didn't go through the normal ugrade process so maybe a package is missing. Will dig a little deeper.

On Sat, May 20, 2023 at 12:47:43PM +0000, ~euhmeuh wrote:

Oopsie, forgot to mention that's the pinephone on postmarketos edge.

-- View on the web: https://todo.sr.ht/~mil/sxmo-tickets/575#event-238924

-- sic dicit magister P https://phartman.sites.luc.edu/ GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)

~phartman referenced this from #575 1 year, 6 months ago

~bgkillas 1 year, 6 months ago

reinstalled pmos and still callaudiod loops

~aren 1 year, 6 months ago*

This might be related https://gitlab.com/postmarketOS/pmaports/-/issues/2115.

Can someone who's having trouble with callaudiod provide the output of pactl list cards? I think it's possible it's not loading the right alsa ucm file and there's no voice call profile which would cause the described output from callaudiod.

Also there's a couple secondary bugs in your report that we should probably address:

The current release is 1.14, I'm guessing you got the version from the config menu entry which is out of date.

I can correctly switch profiles and play with the sound using pavucontrol though, but the whole calling logic in sxmo still fails because it expects the dbus call to succeed.

We definitely need to cleanup the call files if this happens.

~phartman 1 year, 6 months ago

Just updated today and got the problem...

On Mon, May 22, 2023 at 04:04:33PM +0000, ~aren wrote:

This might be related https://gitlab.com/postmarketOS/pmaports/-/issues/2115.

Can someone who's having trouble with callaudiod provide the output of pactl list cards? I think it's possible it's not loading the right alsa ucm file and there's no voice call profile which would cause the described output from callaudiod.

Also there's a couple secondary bugs in your report that we should probably address:

The current release is 1.14, I'm guessing you got the version from the config menu entry which is out of date.

I can correctly switch profiles and play with the sound using pavucontrol though, but the whole calling logic in sxmo still fails because it expects the dbus call to succeed.

We definitely need to cleanup the call files if this happens.

-- View on the web: https://todo.sr.ht/~mil/sxmo-tickets/575#event-239221

-- sic dicit magister P https://phartman.sites.luc.edu/ GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)

~phartman referenced this from #575 1 year, 6 months ago

~phartman 1 year, 6 months ago

Looks like pmos edge just pushed a new callaudiod that fixes it for me.

On Mon, May 22, 2023 at 04:04:33PM +0000, ~aren wrote:

This might be related https://gitlab.com/postmarketOS/pmaports/-/issues/2115.

Can someone who's having trouble with callaudiod provide the output of pactl list cards? I think it's possible it's not loading the right alsa ucm file and there's no voice call profile which would cause the described output from callaudiod.

Also there's a couple secondary bugs in your report that we should probably address:

The current release is 1.14, I'm guessing you got the version from the config menu entry which is out of date.

I can correctly switch profiles and play with the sound using pavucontrol though, but the whole calling logic in sxmo still fails because it expects the dbus call to succeed.

We definitely need to cleanup the call files if this happens.

-- View on the web: https://todo.sr.ht/~mil/sxmo-tickets/575#event-239221

-- sic dicit magister P https://phartman.sites.luc.edu/ GPG keyID 0xE0DBD3D6 (CAE6 3A6F 755F 7BC3 36CA 330D B3E6 39C6 E0DB D3D6)

~phartman referenced this from #575 1 year, 6 months ago

~euhmeuh 1 year, 6 months ago

Oh wow yes I just updated and it works again. Seems like I updated at the worst possible time... as always... sigh Anyways I think we should have the calling and sms logic NOT fail when sound is failing, and have a tiny backup plan, cause I wasn't able to receive calls nor SMS messages because of that error. Thanks for your time investigating this!

~sleep_walker 1 year, 6 months ago

I can confirm update fixed it for me (PostmarketOS Edge @ PinePhone) as well.