[Bug 264563] devel/android-tools-adb causes USB issues with "sideload"

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 09 Jun 2022 21:06:21 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264563

Neel Chauhan <nc@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Closed
         Resolution|---                         |Overcome By Events

--- Comment #2 from Neel Chauhan <nc@FreeBSD.org> ---
Good news, I got this working.

Well, the non-asynchronous ADB implementation, while required on FreeBSD for
compilation was buggy (hence why it was removed). It did not work well with
FreeBSD, or at least modern versions of it.

Commit:
https://github.com/neelchauhan/freebsd-android-tools/commit/00ffd10c14d87093b12a84519942890f3b0fd2b1

I defaulted to the "modern" async one, and I could flash LineageOS to a Google
Pixel 3 this way.

In the past, I just recalled adb worked because sideloading a Custom ROM could
use the "TWRP" recovery which allowed "adb push", but LineageOS has phased that
out in favor of their homegrown recovery which only allows "adb sideload".

Closing as I found a resolution. After my last commit (to the repo), this is
more reliable than even adb on FreeBSD in the past (assuming I use a good USB-C
cable)!

It's a lot like how I maintain GNOME: I actually use adb like I use GNOME so I
have an incentive to maintain it well.

-- 
You are receiving this mail because:
You are the assignee for the bug.