libcall-ui issueshttps://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues2024-02-28T13:25:09Zhttps://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/29Update for GTK 4.12 / adwaita 1.4 deprecations2024-02-28T13:25:09ZGuido GüntherUpdate for GTK 4.12 / adwaita 1.4 deprecationsThe example app needs a bit of care in that regard.
/cc @gautham_x do you want to have a look?The example app needs a bit of care in that regard.
/cc @gautham_x do you want to have a look?https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/27Install libcall-ui as a stand-alone library2023-11-11T17:11:23ZVivien Install libcall-ui as a stand-alone libraryHello,
In order to package GNOME Calls for GNU Guix, we would prefer if libcall-ui were a stand-alone library. This simplistic patch makes sure to install all headers, a library composed of all the sources, and the pkg-config definition...Hello,
In order to package GNOME Calls for GNU Guix, we would prefer if libcall-ui were a stand-alone library. This simplistic patch makes sure to install all headers, a library composed of all the sources, and the pkg-config definition. I unfortunately am not allowed to fork and make a merge request.
[0001-Install-libcall-ui.patch](/uploads/223773cbee616d75a9a104963674fc56/0001-Install-libcall-ui.patch)
Best regards,
Vivienhttps://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/26Fix focus order2023-09-01T05:47:04ZGuido GüntherFix focus orderThe switch to GTK4 reopened what was fixed in https://gitlab.gnome.org/World/Phosh/libcall-ui/-/merge_requests/65 : tab moves to the 'control box' rather than the keypad when hitting tab.The switch to GTK4 reopened what was fixed in https://gitlab.gnome.org/World/Phosh/libcall-ui/-/merge_requests/65 : tab moves to the 'control box' rather than the keypad when hitting tab.https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/25Can't swipe down from keypad2023-05-24T09:47:15ZGuido GüntherCan't swipe down from keypadIf I open the keypad in an ongoing call to it has a small down arrow. Other parts of the mobile environment (e.g. in phosh) use that as an indicator that a swipe gesture can be used however that doesn't work here:
![image](/uploads/a577...If I open the keypad in an ongoing call to it has a small down arrow. Other parts of the mobile environment (e.g. in phosh) use that as an indicator that a swipe gesture can be used however that doesn't work here:
![image](/uploads/a577032f369bcfefbffc3440ce410984/image.png)https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/23Hitting enter doesn't dial in "Dial Pad" after entering number2023-05-03T11:11:54Zchri2Hitting enter doesn't dial in "Dial Pad" after entering numberVersion: gnome-calls 44~alpha.1-1pureos2
Hitting `Enter` after entering a number in the "Dial Pad" view of the app doesn't start dialing.
Dialing starts when
* clicking or tapping on the `dial` button
* using (`shift`-) `tab` multiple ...Version: gnome-calls 44~alpha.1-1pureos2
Hitting `Enter` after entering a number in the "Dial Pad" view of the app doesn't start dialing.
Dialing starts when
* clicking or tapping on the `dial` button
* using (`shift`-) `tab` multiple times until the dial button is marked and then hitting `enter` or `space`
Expected behaviour would be that after entering a number using the keyboard calls would start dialing after hitting enter on the keyboard.https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/20Add video to the CallUiDisplay2022-09-02T16:39:35ZGuido GüntherAdd video to the CallUiDisplaySince we're on a redesign of the call-ui-display: there will be video support at some point: @snwh are there already thoughts or mockups how that will look like?
(nothing too urgent, more about the general direction of things).Since we're on a redesign of the call-ui-display: there will be video support at some point: @snwh are there already thoughts or mockups how that will look like?
(nothing too urgent, more about the general direction of things).https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/18Bluetooth HFP, headset, etc. audio outputs2022-09-06T08:51:34ZDylan Van AsscheBluetooth HFP, headset, etc. audio outputs# Current situation
Currently, the user can switch between the earpiece and the external speaker using the speaker button.
However, we also have a headset available (jack or USB-C audio) and Bluetooth HFP which cannot be chosen at all.
...# Current situation
Currently, the user can switch between the earpiece and the external speaker using the speaker button.
However, we also have a headset available (jack or USB-C audio) and Bluetooth HFP which cannot be chosen at all.
# Proposal
Allow selecting other audio outputs as well during a call so we can route audio to Bluetooth HFP headsets/cars or to a headset connect to a jack or USB Audio. Microphones should be handled as well since both can route audio in also. I think we shouldn't offer a way to select the microphone, it should switch together with the output device, for example:
- Internal speaker selected? internal phone microphone
- Earpiece selected? internal phone microphone
- External headset connected over USB audio or jack selected? headset microphone
- External headphones connected over USB audio or jack selected? internal phone microphone
- Bluetooth HFP selected? Bluetooth HFP microphone.
While the internal speaker and earpiece are (almost) always available, the headset and Bluetooth HFP options are not.
Headsets are only available if the jack is plugged in or the USB audio cable is plugged in.
Jack detection is handled by ALSA UCM just fine, the headset only shows up when plugged in if configured correctly.
USB Audio based headsets only show up when the USB audio card is plugged in, ALSA UCM support is unknown (which is necessary for modem audio routing in a lot of devices)
Bluetooth HFP devices are a bit of a myth yet, not much work was put into it yet as it requires kernel drivers, ALSA UCM configurations which are not used elsewhere yet, etc. However, there's some work for it on the PinePhone: https://gitlab.com/mobian1/issues/-/issues/345 and https://gitlab.com/mobian1/issues/-/issues/160
Branched of #17https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/16Provide d/copyright and/or some debian packaging2022-08-11T23:47:33ZEvangelos Ribeiro TzarasProvide d/copyright and/or some debian packagingSee https://salsa.debian.org/DebianOnMobile-team/phosh/-/merge_requests/41#note_328435See https://salsa.debian.org/DebianOnMobile-team/phosh/-/merge_requests/41#note_328435https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/15Non boolean encryption indicator/detailed (voip) encryption indicator2022-07-04T20:42:14ZEvangelos Ribeiro TzarasNon boolean encryption indicator/detailed (voip) encryption indicatorSee the popover here:
https://gitlab.gnome.org/GNOME/calls/-/issues/446#note_1463379See the popover here:
https://gitlab.gnome.org/GNOME/calls/-/issues/446#note_1463379https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/14demo: Allow manipulating call2022-07-04T20:42:21ZEvangelos Ribeiro Tzarasdemo: Allow manipulating callIt would be useful if call properties could easily be changed from the UI without resorting to gtk inspector.
I propose either a completely separate page or putting the display and preferences page into a `HdyCarousel`
(I mainly care a...It would be useful if call properties could easily be changed from the UI without resorting to gtk inspector.
I propose either a completely separate page or putting the display and preferences page into a `HdyCarousel`
(I mainly care about being able to twiddle with some knobs at all and not too much about the UX of it all -
as I suspect the demo is primarily interesting for developers).https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/12How to indicate emergency call2022-11-19T10:36:14ZEvangelos Ribeiro TzarasHow to indicate emergency callCame up in https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/904#note_1442350
> ... and have `libcall-ui` display some information like "Emergency Call" or use some specific theming.
/cc @bertob @snwhCame up in https://gitlab.gnome.org/World/Phosh/phosh/-/merge_requests/904#note_1442350
> ... and have `libcall-ui` display some information like "Emergency Call" or use some specific theming.
/cc @bertob @snwhhttps://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/10Show a reason why a call ended (if not user initiated)2022-05-23T09:16:01ZEvangelos Ribeiro TzarasShow a reason why a call ended (if not user initiated)F.e. "Remote party hung up", "Line busy", "Signal lost", "User not found" (<- SIP INVITE answered with 404)
Filing this here because of https://gitlab.gnome.org/GNOME/calls/-/issues/420F.e. "Remote party hung up", "Line busy", "Signal lost", "User not found" (<- SIP INVITE answered with 404)
Filing this here because of https://gitlab.gnome.org/GNOME/calls/-/issues/420https://gitlab.gnome.org/World/Phosh/libcall-ui/-/issues/7Keypad cleanups/rework2022-01-20T17:03:38ZEvangelos Ribeiro TzarasKeypad cleanups/reworkAddressing the discussion from https://gitlab.gnome.org/World/Phosh/libcall-ui/-/merge_requests/24#note_1335889
There is two things here:
- Being able to type numbers on the keyboard even if the entry isn't focused
- Conform to the desi...Addressing the discussion from https://gitlab.gnome.org/World/Phosh/libcall-ui/-/merge_requests/24#note_1335889
There is two things here:
- Being able to type numbers on the keyboard even if the entry isn't focused
- Conform to the design by having the blue border around the entry (like when it's focused)