ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    ADB not working. No devices detected

    Ask your questions right here!
    4
    18
    690
    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.
    • Kiazoa JoaoK
      Kiazoa Joao @tom
      last edited by

      @tom yes I do see the LEDs, and I tried using another cable.

      1 Reply Last reply Reply Quote 0
      • VinnyV
        Vinny ModalAI Team @Kiazoa Joao
        last edited by

        Hi @Kiazoa-Joao
        Ahhh, yes WSL has issues and cannot fully replicate the environment needed for these platforms.
        I am a windows user (hardware team) and the best I can get with WSL is ADB and a few basic shell commands.
        The trick with WSL is to use a normal command prompt and try to get ADB over that, then WSL usually can see it... but for some reason, one blocks the other until they both work.
        I've found I need to kill and restart the ADB server on both WSL and Command prompt, sometimes a few times, to get WSL to see the ADB device(s).
        Longer term, you will need a Linux machine.
        We are exploring the option of dual boot PCs in our Hardware lab, so that may be something worth exploring, but WSL will not work long-term and will not work for loading the SDKs.

        Kiazoa JoaoK 1 Reply Last reply Reply Quote 0
        • Kiazoa JoaoK
          Kiazoa Joao @Vinny
          last edited by

          @Vinny I see. thank you for explaining that. can you please help me get this trick to work? every time I try the ADB devices command on the normal command prompt, it either says "ADB" not found or "'adb' is not recognized as an internal or external command,
          operable program or batch file."

          VinnyV 1 Reply Last reply Reply Quote 0
          • VinnyV
            Vinny ModalAI Team @Kiazoa Joao
            last edited by

            HI @Kiazoa-Joao
            Try installing ADB in your windows environment. Then try to repeat with once you get ADB devices listing in Command prompt, it should appear in WSL. That is what usually works for me.
            But I repeat, you will likely not be able to install SDK's... I tried and it instantly fails in WSL.

            Kiazoa JoaoK J 2 Replies Last reply Reply Quote 0
            • Kiazoa JoaoK
              Kiazoa Joao @Vinny
              last edited by

              @Vinny Thank you so much.

              1 Reply Last reply Reply Quote 0
              • J
                jonathanrblazer @Vinny
                last edited by

                @Vinny Hi, has there been any update on this front?
                I am also using WSL on a Windows laptop, trying to get a Starling 2 up and running but 'adb devices' does not list anything
                (if I run 'Get-WmiObject Win32_USBHub' on PowerShell it does list the Qualcomm Android device')

                Any good news? I would like to get this baby flying but am reticent to get a dedicated Linux machine; MAYBE I could consider a dual boot solution...

                Thanks for reading!

                VinnyV Kiazoa JoaoK 2 Replies Last reply Reply Quote 0
                • VinnyV
                  Vinny ModalAI Team @jonathanrblazer
                  last edited by

                  Hi @jonathanrblazer
                  Yes, do a dual boot. It's what we do in our HW lab and we have no issues.
                  WSL just does not work the way it needs for our Ubuntu flavors.
                  Hope that helps!

                  1 Reply Last reply Reply Quote 1
                  • Kiazoa JoaoK
                    Kiazoa Joao @jonathanrblazer
                    last edited by

                    @jonathanrblazer Hi! WSL did not work for me. I've been using a VirtualBox called Oracle. You can download it for free. I hope this helps.

                    J 1 Reply Last reply Reply Quote 1
                    • J
                      jonathanrblazer @Kiazoa Joao
                      last edited by

                      @Kiazoa-Joao Hey! I’ve been using Oracle VirtualBox and it’s going well. I’m at the end of the bootcamp at the part on voxl-cross, have you been running Docker INSIDE the VirtualBox? If so, any important considerations? If not, what are you doing instead?

                      Kiazoa JoaoK 1 Reply Last reply Reply Quote 0
                      • Kiazoa JoaoK
                        Kiazoa Joao @jonathanrblazer
                        last edited by

                        @jonathanrblazer I am glad it worked out for you. yes, I've been running the docker inside the VirtualBox, but you can also run it outside the VM, just use your wifi and "ssh root@ip". Always "commit" any changes you make inside the docker; otherwise, you'll have to re-download your packages over and over again. I also had a lot of issues with communication. The docker container wouldn't communicate with the drone. If you're trying to run MAVROS, follow these steps here https://docs.modalai.com/mavros-0_9/

                        1 Reply Last reply Reply Quote 1
                        • First post
                          Last post
                        Powered by NodeBB | Contributors