• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

OTG DAC support needed

Scheduled Pinned Locked Moved Google Nexus 5
16 Posts 7 Posters 1.1k Views 3 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I Offline
      ierihon
      last edited by ierihon 3 Nov 2021, 07:27 11 Mar 2021, 07:26

      Re: USB C Dac support

      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?

      C 1 Reply Last reply 11 Mar 2021, 11:47 Reply Quote 0
      • C Offline
        CiberSheep @ierihon
        last edited by 11 Mar 2021, 11:47

        @ierihon Hello. I have moved your post under Nexus 5 category πŸ˜‰

        Another planet, another time, another universe!

        I K 2 Replies Last reply 11 Mar 2021, 14:29 Reply Quote 0
        • I Offline
          ierihon @CiberSheep
          last edited by 11 Mar 2021, 14:29

          @cibersheep OK. Thanks. πŸ˜‰

          1 Reply Last reply Reply Quote 0
          • K Offline
            Keneda @CiberSheep
            last edited by 11 Mar 2021, 14:47

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

            2015-2023 : Meizu MX4 ☠️⚰️✝️
            2023-2024 : Nexus 5 ☠️⚰️✝️
            2024-***** : FPOS Fairphone 5 waiting UT for freedom πŸ˜‰
            πŸ‡²πŸ‡«πŸ‡¬πŸ‡§

            P 1 Reply Last reply 11 Mar 2021, 18:07 Reply Quote 0
            • P Offline
              PhoenixLandPirat @Keneda
              last edited by 11 Mar 2021, 18:07

              @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.

              1 Reply Last reply Reply Quote 0
              • L Offline
                Luksus
                last edited by 12 Mar 2021, 09:50

                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.

                I C F 3 Replies Last reply 13 Mar 2021, 12:19 Reply Quote 0
                • I Offline
                  ierihon @Luksus
                  last edited by 13 Mar 2021, 12:19

                  @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.

                  L 1 Reply Last reply 15 Mar 2021, 10:49 Reply Quote 0
                  • L Offline
                    Luksus @ierihon
                    last edited by Luksus 15 Mar 2021, 10:49

                    @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"
                    
                    I 2 Replies Last reply 15 Mar 2021, 13:38 Reply Quote 0
                    • I Offline
                      ierihon @Luksus
                      last edited by 15 Mar 2021, 13:38

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

                      1 Reply Last reply Reply Quote 0
                      • I Offline
                        ierihon @Luksus
                        last edited by 15 Mar 2021, 14:03

                        @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.

                        L C 2 Replies Last reply 19 Mar 2021, 05:57 Reply Quote 0
                        • L Offline
                          Luksus @ierihon
                          last edited by Luksus 19 Mar 2021, 05:57

                          @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...

                          1 Reply Last reply Reply Quote 0
                          • C Offline
                            cavedweller @Luksus
                            last edited by 26 Mar 2021, 11:55

                            @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.

                            1 Reply Last reply Reply Quote 0
                            • C Offline
                              cavedweller @ierihon
                              last edited by 26 Mar 2021, 11:57

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

                              1 Reply Last reply Reply Quote 0
                              • F Offline
                                flohack @Luksus
                                last edited by 27 Mar 2021, 16:28

                                @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.

                                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                L 1 Reply Last reply 28 Mar 2021, 08:42 Reply Quote 0
                                • L Offline
                                  Luksus
                                  last edited by 27 Mar 2021, 23:44

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • L Offline
                                    Luksus @flohack
                                    last edited by Luksus 28 Mar 2021, 08:42

                                    @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.

                                    1 Reply Last reply Reply Quote 0
                                    • First post
                                      Last post