On 19.05.20 18:16, Stefan Sauer wrote:
was there anything helpful in the -v output. Any idea what to try next?
Enable some debug output?
Stefan
> On 19.05.20 08:16, Clemens Ladisch via Alsa-user wrote:
>> Stefan Sauer wrote:
>>> idProduct=5209 is the Pixel C as a midi device, 520a is when it con
On 19.05.20 08:16, Clemens Ladisch via Alsa-user wrote:
> Stefan Sauer wrote:
>> idProduct=5209 is the Pixel C as a midi device, 520a is when it connects
>> as MTP.
> Your lsusb output showed 520a. Was it supposed to be in MIDI mode at
> that time?
>
> Please show the output of "lsusb -d 18d1:5209
Stefan Sauer wrote:
> idProduct=5209 is the Pixel C as a midi device, 520a is when it connects
> as MTP.
Your lsusb output showed 520a. Was it supposed to be in MIDI mode at
that time?
Please show the output of "lsusb -d 18d1:5209 -v".
Regards,
Clemens
On 18.05.20 17:25, Clemens Ladisch via Alsa-user wrote:
> Stefan Sauer wrote:
>> If I use my pixel c tablet, the alsa device is recognized (it shows
>> up in /proc/asound/ and also creates a midi0 entry)
> Does it show up in the output of "amidi -l"?
>
> Is the ID 5209 or 520a? Your logs show both
Stefan Sauer wrote:
> If I use my pixel c tablet, the alsa device is recognized (it shows
> up in /proc/asound/ and also creates a midi0 entry)
Does it show up in the output of "amidi -l"?
Is the ID 5209 or 520a? Your logs show both.
Regards,
Clemens
_
hi,
most recent andoid phone let you connect it to a computer via USB and
select the USB mode. The modes also contain midi. This e.g. allows to
run a midi controller on the phone/table as a control surface for music
software.
If it do this with a pixel 3 phone it all works, but since it is a
phon
