NO Notification sounds, speakers test does not work and NO phone ring, how to check?

1 Like

Also calendar does not alert with sound either… PLEASE ALERT SOME ONE THAT CAN FIX… YOU ALL ARE WARNED DO NOT USE A FULL-UPGRADE!!!
Reverting back to Gluegle spy machine til can get help to fix this, very disappointed in this and software updates!!!
Dave

1 Like

Maybe an issue on PA Pineline output, reinstall it may fix it. Also Purism it has an Arsenal of Scriptish to test anything…(kudos for purism).

1 Like

:face_vomiting:

I suggest a reflash in that case. That would confirm that the phone can be gotten back to a working state.

Also, I suggest periodic backup (all the time) and a backup before a major upgrade. That of course applies to any computer.

Yeah, don’t do full-upgrade.

2 Likes

Testing through the terminal the phone ring tone works good volume, as well as alarm clock and timer. Still nothing on speaker tests… dead but highlights when buttons clicked.

2 Likes

Carlos, what is PA Pineline output and where can I locate download for reinstall?

1 Like

Is PA the phone app?
? Proper term used to reinstall using terminal?

1 Like

rm -rf ~/.config/pulse && sudo apt reinstall pulseaudio


2 Likes

PA == Pulseaudio

2 Likes

Thanks for info and help, solved last night reinstalled gnome-phone
Works fine but the speaker test still not working.

1 Like

For me, it worked to remove the ~/.config/pulse directory and then reboot, apparently then the files ni there are recreated with some default settings that work. After that, ringtone for incoming calls works again, as well as other audio things like alarm clock sound which was also broken before. Thanks @carlosgonz :+1:

However I still don’t know why the problem appeared and what the difference was between the working and not working settings.

I did save the old files before removing them, like this:

cp -r ~/.config/pulse saved_dot_config_pulse_files
rm -rf ~/.config/pulse

and was hoping to see something by doing a diff between new and old afterwards, but it looks like the files are in some binary format so that was not so easy to do.

There are five files in the ~/.config/pulse directory, with long names starting with something cryptic and then filename endings like this:

[...]-card-database.tdb
[...]-default-sink
[...]-default-source
[...]-device-volumes.tdb
[...]-stream-volumes.tdb

If anyone here knows how to look at the contents of those files, to get a meaningful diff between new and old versions of those five files?

2 Likes

sudo apt install tdb-tools

tdbdump xxx.tdb

tdb == trivial database. It is used by Samba (which is where I have encountered it).

Unfortunately, while that will move you forward, that won’t fully answer your actual question (because the key values are themselves somewhat opaque, at least in the one that I looked at).

3 Likes

Thanks, using that I can dump old and new files and look at differences.

Here are some things that differ in the “stream-volumes” tdb file (there are other differences also in addition to these):

old:

key(33) = "source-output-by-media-role:phone"
data(13) = "B\020m\00v\00100N0N"

key(30) = "sink-input-by-media-role:phone"
data(13) = "B\020m\00v\00100N0N"

key(30) = "sink-input-by-media-role:event"
data(93) = "B\021m\02\01\02v\02\00\00\00\00\00\00\00\00101talsa_output.platform-sound.HiFi__hw_L5__sink\001talsa_card.platform-sound\00"

new:

key(33) = "source-output-by-media-role:phone"
data(13) = "B\020m\00v\00000N0N"

key(30) = "sink-input-by-media-role:phone"
data(13) = "B\020m\00v\00000N0N"

key(30) = "sink-input-by-media-role:event"
data(13) = "B\020m\00v\00000N0N"

This got me thinking that maybe it got confused by me having connected headphones earlier, maybe the ringtone was sent to the headphone jack (even though headphones were no longer connected).

I won’t dig into it more now, but it’s good to know that it can be viewed in that way. Thanks!

2 Likes

Also my sound sometimes get messed up. I have this forum post bookmarked to fix it.

Maybe it would be useful to have somewhere in the gnome-settings a “reset audio” functionality to do this. This would be easier for non-technical users. What do you think about this suggestion? Should I create somewhere a request for this?

3 Likes

I’m not sure, on one hand it would be convenient, but on the other hand it may be better to focus efforts on fixing the bugs that cause the settings to get messed up in the first place.

4 Likes

True. Although going back to default settings is also something people might want to do after they deliberately changed sound settings.

3 Likes

Yes, do it.

Huh? full-upgrade was the recommended method… by @dos, IIRC.

1 Like

@dos has not posted in this topic.

1 Like

Well, I remember someone saying. I tried searching the forum and thought I was zooming in on @jeremiah, but I don’t think it was him. :thinking:

1 Like