calls issueshttps://source.puri.sm/Librem5/calls/-/issues2021-03-05T02:24:51Zhttps://source.puri.sm/Librem5/calls/-/issues/10accept incoming call when hardware kill switch is turned from off to on2021-03-05T02:24:51ZGuido Guntheraccept incoming call when hardware kill switch is turned from off to onWhen mic is turned off via the hw kill switch and a call comes in, calls should accept the call when the hw kill switch is turned to on.
See https://source.puri.sm/Librem5/Apps_Issues/issues/55When mic is turned off via the hw kill switch and a call comes in, calls should accept the call when the hw kill switch is turned to on.
See https://source.puri.sm/Librem5/Apps_Issues/issues/55Evangelos Ribeiro TzarasEvangelos Ribeiro Tzarashttps://source.puri.sm/Librem5/calls/-/issues/81Calls won't play the ringtone after changing the output audio device2020-06-20T22:04:33ZFrancois TecheneCalls won't play the ringtone after changing the output audio device# What problem did you encounter
Calls won't play the ringtone after changing the output audio device. This doesn't affect the call, it only affects the ringtone.
## What is the actual behaviour?
Calls plays the ringtone when getting a ...# What problem did you encounter
Calls won't play the ringtone after changing the output audio device. This doesn't affect the call, it only affects the ringtone.
## What is the actual behaviour?
Calls plays the ringtone when getting a call. Changing the audio output to the headphone makes Calls not play the ringtone anymore. Even after restoring the audio output device to the default built in audio output doesn't make Calls play the ringtone again, until the device is restarted.
## What is the expected behaviour?
Calls should keep playing the ringtone on the different audio output devices.
## How to reproduce
- Boot the device (in my case, the devkit)
- Unlock the sim card
- Get a call
- => Calls plays the ringtone loud and clear in the device speakers
- Plug in headsets to the device (and change the output device in the system settings)
- Get a call
- => Calls doesn't play the ringtone anymore in the headsets
- Unplug the headsets (and restore the output device to the default one in the system settings)
- Get a call
- => Calls doesn't play the ringtone anymore in the device speakers
# Which version of Calls did you encounter the bug in?
- [ ] I compiled it myself. If you compiled Calls from source please provide the
git revision via e.g. by running ``git log -1 --pretty=oneline`` and pasting
the output below.
- [x] I used the precompiled Debian package (e.g. by running a prebuilt
image). Please paste the output of ``dpkg -s calls`` below.
```
Package: calls
Status: install ok installed
Priority: optional
Section: comm
Installed-Size: 415
Maintainer: Bob Ham <rah@settrans.net>
Architecture: arm64
Version: 0.0.1~205.gbp974650
Depends: libc6 (>= 2.17), libebook-contacts-1.2-2 (>= 3.16.2), libglib2.0-0 (>= 2.57.2), libgom-1.0-0 (>= 0.3.2), libgsound0 (>= 1.0.1), libgtk-3-0 (>= 3.17.9), libhandy-0.0-0 (>= 0.0.10), libmm-glib0 (>= 1.5.993), libpango-1.0-0 (>= 1.14.0), libpeas-1.0-0 (>= 1.0.0), libwayland-client0 (>= 1.9.91), modemmanager
Conffiles:
/etc/xdg/autostart/sm.puri.Calls.desktop 656e549c2c3e7b931a8f37ac739cbc3c
Description: Make and receive PSTN phone calls
A GTK+ user interface for PSTN phone calls using oFono.
```
# What hardware are you running Calls on?
- [ ] amd64 qemu image
- [x] Librem5 devkit
- [ ] other (please elaborate)
# What modem are you using?
# Releveant logfiles
```
Sep 09 11:32:28 pureos pulseaudio[572]: W: [alsa-sink-308b0000.sai-sgtl5000 sgtl5000-0] alsa-sink.c: Resume failed, couldn't restore original sample settings.
Sep 09 11:32:28 pureos pulseaudio[572]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
Sep 09 11:32:28 pureos calls[792]: Attempt to load unknown IM context type 'simple'
Sep 09 11:32:28 pureos calls[792]: Error playing ringtone: Invalid state
```https://source.puri.sm/Librem5/calls/-/issues/162wys calls error reporting2021-04-26T08:10:19ZGuido Guntherwys calls error reportingcalls needs to talk to wys so we get an error if it can't set up audio routing. There should be a clear indication that something is wrong instead of just no audio in/out.calls needs to talk to wys so we get an error if it can't set up audio routing. There should be a clear indication that something is wrong instead of just no audio in/out.https://source.puri.sm/Librem5/calls/-/issues/178should abort when hitting timeout2021-12-15T10:51:33ZGuido Gunthershould abort when hitting timeoutwhen the phone has bad reception placing calls fails like
```
Okt 01 18:21:32 pureos calls[851]: Error starting outgoing call ModemManager call to `+49xxxxxxxxx': Zeitüberschreitung wurde erreicht
Okt 01 18:21:49 pureos ModemManager[510...when the phone has bad reception placing calls fails like
```
Okt 01 18:21:32 pureos calls[851]: Error starting outgoing call ModemManager call to `+49xxxxxxxxx': Zeitüberschreitung wurde erreicht
Okt 01 18:21:49 pureos ModemManager[510]: <info> [modem1/call0] user request to hangup call
Okt 01 18:21:51 pureos ModemManager[510]: <info> [modem1/call0] user request to hangup call
Okt 01 18:22:14 pureos calls[851]: Error hanging up ModemManager call to `+49xxxxxxxx': Zeitüberschreitung wurde erreicht
Okt 01 18:22:16 pureos calls[851]: Error hanging up ModemManager call to `+49xxxxxxxx': Zeitüberschreitung wurde erreicht
Okt 01 18:22:37 pureos ModemManager[510]: <warn> [modem1/call0] couldn't start call: Serial command timed out
Okt 01 18:22:37 pureos ModemManager[510]: <info> [modem1/call0] call state changed: dialing -> terminated (unknown)
Okt 01 18:22:37 pureos ModemManager[510]: <warn> [modem1] port ttyUSB1 timed out 2 consecutive times
Okt 01 18:22:42 pureos ModemManager[510]: <warn> [modem1] couldn't load call list: Serial command timed out
Okt 01 18:22:42 pureos ModemManager[510]: <warn> [modem1] port ttyUSB1 timed out 3 consecutive times
Okt 01 18:22:44 pureos ModemManager[510]: <warn> [modem1] port ttyUSB1 timed out 4 consecutive times
Okt 01 18:22:46 pureos ModemManager[510]: <warn> [modem1] port ttyUSB1 timed out 5 consecutive times
```
(Zeitüberschreitung wurde erreicht = `ETIMEDOUT`)
There's no 'beep' sound, the speaker stays perfectly silent. Hitting the red button does nothing until much later. It would likely be better to cancel the call right away when hitting the first timeout so the user gets feedback about the problem (that's what my other phone does under these circumstances).https://source.puri.sm/Librem5/calls/-/issues/186Crash when unplugging external display2021-03-25T16:10:35ZGuido GuntherCrash when unplugging external display```
Okt 29 11:51:14 pureos systemd-coredump[1728]: Process 1683 (calls) of user 1000 dumped core.
Stack trace of thread 1683:
...```
Okt 29 11:51:14 pureos systemd-coredump[1728]: Process 1683 (calls) of user 1000 dumped core.
Stack trace of thread 1683:
#0 0x0000ffffa82b0714 __GI_raise (libc.so.6)
#1 0x0000ffffa829e8e8 __GI_abort (libc.so.6)
#2 0x0000ffffa84290ac n/a (libwayland-client.so.0)
#3 0x0000ffffa842808c n/a (libwayland-client.so.0)
#4 0x0000ffffa8424a44 n/a (libwayland-client.so.0)
#5 0x0000ffffa8425e08 wl_display_dispatch_queue_pending (libwayland-client.so.0)
#6 0x0000ffffa8adf67c n/a (libgdk-3.so.0)
#7 0x0000ffffa8a7baa0 gdk_display_get_event (libgdk-3.so.0)
#8 0x0000ffffa8adf35c n/a (libgdk-3.so.0)
#9 0x0000ffffa9381674 g_main_context_dispatch (libglib-2.0.so.0)
#10 0x0000ffffa93818e8 n/a (libglib-2.0.so.0)
#11 0x0000ffffa9381984 g_main_context_iteration (libglib-2.0.so.0)
#12 0x0000ffffa8792c7c g_application_run (libgio-2.0.so.0)
#13 0x0000aaaab39c01b0 main (calls)
#14 0x0000ffffa829ed24 __libc_start_main (libc.so.6)
#15 0x0000aaaab39c0204 _start (calls)
#16 0x0000aaaab39c0204 _start (calls)
```
it's pretty reproducible and wouldn't end good for ongoing calls.