[Quickcall] quickcall on unbuntu 20.04

Wed Jan 13 12:11:03 AEDT 2021

On Tue, Jan 12, 2021 at 11:00:59AM -0600, MIchael L. Stokes wrote:
> David,
> 
> Sorry.  I did not read your last message before I responded.  I did a make
> install and that worked fine.  I recommend you put some instructions on how
> to build and install the software in your README.

Patches welcome.  Remember this is a project I did a good long while
ago in my free time, which I now have rather less of, for a device
that I no longer use personally.

> I see the device in the audio menus, but it does not work when selected.  I
> looked in the syslog and it says

I'm not really sure which menus you mean.

> Jan 12 10:48:29 cue /usr/lib/gdm3/gdm-x-session[12138]: (II) XINPUT: Adding
> extended input device "Logitech Logitech USB Headset" (type: KEYBOARD, id
> 11)

"Logitech Logitech USB Headset"... that doesn't look like a name
associated with the Quickcall Speakerphone.  Are you sure this is
referring to the speakerphone, not another device?

> It later says "Logitech USB Headset is tagged by udev as: Key board"

That's not necessarily wrong (although incomplete) - the Speakerphone
does present as a USB HID device - basically the same as a keyboard -
in order to represent its buttons (it also appears as a USB audio
device).

> ... /usr/lib/gdm3/gdm-x-session[12138]: (II) event20 - Logitech Logitech USB
> Headset: device is a keyboard
> Jan 12 10:48:29 cue mtp-probe: checking bus 1, device 19:
> "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2"
> Jan 12 10:48:29 cue mtp-probe: bus: 1, device: 19 was not an MTP device

That also doesn't look wrong - the speakerphone is not an MTP device.

> Any ideas David?
> 
> -Mike
> 
> On 1/12/21 10:34 AM, MIchael L. Stokes wrote:
> > Well David if the device was successfully running it would appear as a
> > sound device under the UBUNTU settings menus? Right?
> > 
> > But the question that has not been answered is how does the program that
> > starts the daemon know where the daemon executable is found? The RUN+
> > option in the rule uses the syntax @QUICKCALLD@, but I have no idea how
> > that is translated into a PATH  for the executable.  Do you know?
> > 
> > The executable is still sitting in the source path directory where I
> > built it.
> > 
> > On 1/11/21 3:32 PM, MIchael L. Stokes wrote:
> > > The rules look like the following
> > > 
> > > SUBSYSTEM=="usb", ACTION=="add", ATTR{idVendor}=="046d",
> > > ATTR{idProduct}=="08d5", RUN+="@QUICKCALLD@ -u -v %S%p"
> > > 
> > > How does the system know where to find quickcalld? Does it need to
> > > go in some system bin directory? --Mike
> > > 
> > > 
> > > On 1/11/21 3:54 AM, David Gibson wrote:
> > > > On Thu, Jan 07, 2021 at 11:13:49PM -0600, MIchael L. Stokes wrote:
> > > > > It have the udev rules setup (I think), and the daemon
> > > > > compiles and runs as
> > > > > 
> > > > > sudo ./quickcalld -u -l /tmp/log.txt &
> > > > Hrm.  If the udev rules were working, you shouldn't need to manually
> > > > run the daemon - it should be automatically started when the device is
> > > > plugged in.
> > > > 
> > > > > It also show up as a usb device
> > > > > 
> > > > > $ lsusb
> > > > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > > > > Bus 001 Device 008: ID 0bda:0129 Realtek Semiconductor Corp.
> > > > > RTS5129 Card
> > > > > Reader Controller
> > > > > Bus 001 Device 007: ID 04e6:5116 SCM Microsystems, Inc.
> > > > > SCR331-LC1 / SCR3310
> > > > > SmartCard Reader
> > > > > Bus 001 Device 006: ID 2687:fb01 Fitbit Inc. Fitbit Base Station
> > > > > Bus 001 Device 005: ID 12c9:102a Newmen Tech.,LTD 2.4G Wireless Mouse
> > > > > Bus 001 Device 004: ID 03f0:164a HP, Inc HP SC Keyboard -
> > > > > Apollo (Liteon)
> > > > > Bus 001 Device 009: ID 0cf3:e005 Qualcomm Atheros Communications
> > > > > Bus 001 Device 010: ID 046d:08d5 Logitech, Inc. Speakerphone(Disabled)
> > > > > Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270
> > > > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > > > > (base) stokes at cue:~/Desktop$
> > > > Ok, that would show up whether or not quickcalld was working correctly.
> > > > 
> > > > > But it doesn't appear as a device in the setup menues. I
> > > > > also need some help
> > > > > in how to automate the quickcalld during startup.
> > > > I'm not quite sure what menu you expect the device to appear in.
> > > > 
> > > _______________________________________________
> > > Quickcall mailing list
> > > Quickcall at lists.ozlabs.org
> > > https://lists.ozlabs.org/listinfo/quickcall
> > _______________________________________________
> > Quickcall mailing list
> > Quickcall at lists.ozlabs.org
> > https://lists.ozlabs.org/listinfo/quickcall
> _______________________________________________
> Quickcall mailing list
> Quickcall at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/quickcall

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/quickcall/attachments/20210113/9618ff76/attachment.sig>