OTG DAC support needed

ierihon

I have Nexus 5 with UT. And i buy OTG DAC with interface chip CM108. On Windows, Ubuntu Desktop and Android Phone they work well. But on UT won't.

Can you help me?

CiberSheep

@ierihon Hello. I have moved your post under Nexus 5 category

ierihon

@cibersheep OK. Thanks.

Keneda

@cibersheep Not sure this lack of support for his DAC is only on N5.

PhoenixLandPirat

@keneda all my devices support my usb-c earphoes on android but none on Ubuntu Touch, so it isnt just a nexus issue, howeber, I dothink its specifically a porting issue, and since only a minority of people have or use usb-c dacs, its either over looked, or difficult to debug.

Luksus

I assume it is a kernel issue.
The kernel used by the ubuntu touch port is just too old (3.16 -> Android 5.1) to contain the needed kernel modules, while the nexus 5 already recieved Android 11, which means a much more current kernel.

ierihon

@luksus For info: my DAC work well on Android 6.0.1. I not tested in on older Android Phones.

The CM108 interface chip (C-Media CM108) is used for maximum compatibility.

Luksus

@ierihon
Mh. I think even if it is recognized, it will not be used automatically.

You could check if pulseaudio is seeing your device:

pacmd list-sinks | grep -e 'name:' -e 'index:'

And if it gets listed, try to set it as default using the name (i.e.: <my_ext_device>):

pacmd "set-default-sink my_ext_device"

ierihon

@luksus Thanks a lot! I will try it later.

ierihon

@luksus there is result:

Filed to create secure directory (/root/.config/pulse): No such file or directory
There is no PulseAudio daemon running, or it is not running as a session daemon.

All settings is default.

Luksus

@ierihon did you execute it with sudo? That should not be necessary.
Do you have a pulse-directory in your /home/phablet/.config/ ?

It is also possible, that your phone with an older halium-port is just not using pulse for audio.
I believe there should already be a halium7.1 port for the nexus5. Perhaps it is worth a try...

cavedweller

@luksus I think it's a rule/routing issue, I'm on the Vollaphone and I'm facing the same problem, I'm actually dual booting because of it, I use them daily con android.

cavedweller

@ierihon Thanks, I'll also test it, because it is properly recognized by pulse and by alsa-utils using aplay -L

flohack

@luksus sorry to say but you are wrong, in general vendors do not upgrade the underlying kernel with a newer Android version, they try to stay as much as possible on the one they made already. Thats also the reason why on LineageOS trees you can live comfortably across 5 or 6 Android versions with the same kernel repo

No security updates or bugfixes
No support for newer hardware

Thats what you get with Android. You are suppsed to throw away your device every other year.

Luksus

This post is deleted!

Luksus

@flohack Yes, I forgot that the rootfs is the same across different halium versions.
But I wonder if it still isn't possible, that some components like pulse are used differently.
For example, why does it claim, that no pulseaudio deamon is running for ierihon, while it lists sinks for me on bq 4.5 and FP3?

And isn't it also about kernel modules for a common audiochip, which could be supported by a newer kernel?

Edit:
Ah, you said that they do not upgrade the kernel,
I thought you was talking about vendor blobs.