This is a cache of https://discuss.96boards.org/t/adb-daemon-on-410c-linux/191. It is a snapshot of the page at 2024-11-01T04:43:17.519+0000.
Adb daemon on 410c Linux - DragonBoard410c - 96Boards Forum

Adb daemon on 410c Linux

Hi,
Has anyone tried to get adb daemon running on 410c Linux/ubuntu? i.e When I plug a 410c running ubuntu to my HOST PC, I want it to show up as an adb device.

Thanks

Hi Ashwin
I have not tried this on DB410c. But this was possible on the Ifc6410.
Steps are documented here:
https://wiki.linaro.org/Boards/IFC6410/Linaroubuntu#How_to_install_setup_and_use_Android_ADB

Once it works, we should preload the android-tools-adbd and a preconfigured : android-tools-adbd.conf as part of the ALIP or the Developer image .

I will try it later today or tomorrow and update this thread.

-Sujai.

Hi Sujai, Did you have any luck with this?

Thanks
Ashwin

Hi Ashwin
I couldnt get the arm64 version of android-tools-adbd (although android-tools-adb) is available and I could install it.
I couldnt get to cross compile android-tools-adbd for arm64 yet. If anyone can share me the procedure to setup a cross compile environment for AARCH64 it would be good.

-Sujai.

we are currently looking into that… hopefully we should get it soon…

Hi,

I tried putting ADB from following link to yocto build. It got built and adbd starts running after boot. But I cannot see it when I run “adb devices” from the host machine.
I got adb from the following link:
https://github.com/shr-distribution/meta-smartphone/blob/danny/meta-android/recipes-android/adb/adb_git.bb

unfortunately, this is still work in progress… we have this bug to track:

https://bugs.linaro.org/show_bug.cgi?id=2179

you are pointing to a very old branch (danny).

there is also working going on in this area upstream:

https://patchwork.openembedded.org/patch/125961/

if you could have a look at this and help, that would be appreciated.

Thanks for the update. I will try to build with this patch and see what happens.

I Was able to get adb shell up on yocto. I followed the instructions from this blog:
https://plus.google.com/111524780435806926688/posts/AaEccFjKNHE

hi, thanks for reporting it! can you share a bit more info about how you got it to work? for example, which version/branch of the manifest you are using, which tools did you add to the image, …

thanks!

I am using jethro branch. I downloaded and added “android-tools” recipe from the following link:
https://github.com/shr-distribution/meta-smartphone/tree/master/meta-android/recipes-android/android-tools/

I added this in the path: layers/openembedded-core/meta/recipes-connectivity and built it.
Along with this I “Function Filesystem” in kernel.

I got it working under Debian.
adbd - compiled from openembedded/jethro brach. The libcrypto dependency was conflicting with ssh on Debian, so created standalone adbd executable.
kernel - functionFS enabled