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

    USB connection to my Pixel 3A not working.

    Scheduled Pinned Locked Moved Google Pixel 3a/3a XL
    13 Posts 7 Posters 1.2k 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.
      • M Offline
        marlboro50 @arubislander
        last edited by

        @arubislander thanks for your reminding me. I am on the stable channel of Xenial OTA 25. I had forgotten to mention it.

        1 Reply Last reply Reply Quote 0
        • M Offline
          marlboro50 @arubislander
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • E Offline
            Emphrath
            last edited by

            I have to say i'm on 16.04 dev branch and same here - so it's been for a while

            1 Reply Last reply Reply Quote 0
            • U Offline
              ullgren @marlboro50
              last edited by ullgren

              @marlboro50 @arubislander Same problem here.

              Laptop running Pop!_OS 22.04 LTS with latest patches.

              Pixel 3a XL running Ubuntu Touch 20.04 Development (20.04 r578).

              Neither adb nor lsusb shows the phone.

              Looking in the kernel ring buffer using dmesg show the following when connecting the device.

              [  614.866393] usb 1-2: new full-speed USB device number 7 using xhci_hcd
              [  614.994416] usb 1-2: device descriptor read/64, error -71
              [  615.438415] usb 1-2: device descriptor read/64, error -71
              [  615.674372] usb 1-2: new full-speed USB device number 8 using xhci_hcd
              [  615.806351] usb 1-2: device descriptor read/64, error -71
              [  616.042397] usb 1-2: device descriptor read/64, error -71
              [  616.150711] usb usb1-port2: attempt power cycle
              [  616.562364] usb 1-2: new full-speed USB device number 9 using xhci_hcd
              [  616.562539] usb 1-2: Device not responding to setup address.
              [  616.770503] usb 1-2: Device not responding to setup address.
              [  616.978333] usb 1-2: device not accepting address 9, error -71
              [  617.110362] usb 1-2: new full-speed USB device number 10 using xhci_hcd
              [  617.110520] usb 1-2: Device not responding to setup address.
              [  617.318765] usb 1-2: Device not responding to setup address.
              [  617.526334] usb 1-2: device not accepting address 10, error -71
              [  617.526404] usb usb1-port2: unable to enumerate USB device
              
              Mario.CHM 1 Reply Last reply Reply Quote 0
              • Mario.CHM Offline
                Mario.CH @ullgren
                last edited by

                Hi @ullgren,

                According to my research, you should try the solution described in the following link:

                https://urukrama.wordpress.com/2009/01/27/usb-drive-not-recognised-error-71/

                If you can rule out hardware issues, such as cable, power supply (if you have a USB hub in between) and or low battery (on the Phone or even Laptop).

                Good luck πŸ€

                Greetings Mario

                πŸ“± Oneplus Nord N100 UT20.40 (OTA5); then Xperia X (since 2020) at last UT 20.04(OTA5), now out of service due to defective camera
                🐎 When you realize you are riding a dead horse, get off!
                My languages skill: πŸ‡¨πŸ‡­πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ, and only orally: πŸ‡¬πŸ‡§ πŸ‡ΉπŸ‡­

                U 1 Reply Last reply Reply Quote 0
                • MrT10001M Online
                  MrT10001
                  last edited by MrT10001

                  From experience:
                  If you have replaced the cable
                  Tried another USB port
                  Tried another device with the same cable and that device connects
                  Tried another PC
                  Tried another Operating system
                  Installed Android Studio to get the most up to date ADB and fastboot drivers on the PC
                  Cleaned the devices USB port with 99% Isopropyl alcohol
                  Your device is second hand and you don't know its history (lots of eBay devices)

                  All the above fails to connect with a PC then your devices USB port is faulty and needs to be replaced which is no easy task on any of the Pixel phones.

                  I have numerous USB cables and have tried sometimes 5 different ones to get a contact.

                  Xiaomi Redmi Note 7.... And more...
                  I have too many devices...

                  U 1 Reply Last reply Reply Quote 0
                  • U Offline
                    ullgren @Mario.CH
                    last edited by

                    @Mario-CH Thanks for your tip however use_both_schemes was set to Y by default on my distro.

                    1 Reply Last reply Reply Quote 0
                    • U Offline
                      ullgren @MrT10001
                      last edited by

                      @MrT10001 Indeed cleaning the usb port on the phone seems to have solved the issue. Thanks.
                      Weird since I used the same setup (laptop, phone and cable) to just minutes before flash the PQ3B.190801.002 factory image and then install Ubuntu Touch. Do not even think I disconnected the USB cable anytime during the process.

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        marlboro50 @ullgren
                        last edited by

                        @ullgren nothing worked for me. No changes.

                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          davedanger
                          last edited by

                          I had this same problem and put my phone in Fastboot mode and my computer recognized my phone. I'm not sure what caused it, but I think it may had been something like the utadblocker app but I'm really not sure.

                          arubislanderA 1 Reply Last reply Reply Quote 0
                          • arubislanderA Offline
                            arubislander @davedanger
                            last edited by

                            @davedanger It is very unlikely an app caused issues with ADB detection.

                            πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
                            Happily running Ubuntu Touch
                            Google Pixel 3a (20.04 DEV)
                            JingPad (24.04 preview)
                            Meizu Pro 5 (16.04 DEV)

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