New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 867664 link

Starred by 6 users
Status: Fixed
Owner:
vapier@chromium.org
Closed: Aug 2
Cc:
█ puneetster@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature



Sign in to add a comment

Uprev adb and fastboot containers

Project Member Reported by adlr@chromium.org, Jul 25 
We should uprev the adb container. ARC++ folks have confirmed there are no issues, and actually they would prefer to have it updated.

Vapier, if this will be a lot of work, can you describe it?

Comment 1 by puneetster@chromium.org, Jul 25

Cc: puneetster@chromium.org

Comment 2 by ijpedowitz@google.com, Jul 26 

Can the fastboot container also be uprevved as part of this, please?

Comment 3 by adlr@chromium.org, Jul 26

Summary: Uprev adb and fastboot containers (was: Uprev adb container)
Agree it should be both. Updated summary.

Comment 4 by vapier@chromium.org, Aug 2

Status: Fixed (was: Assigned)
if you mean updating adb inside the sdk, last time i tried that, all the ARC++ hwtests pooped themselves.  i don't have the cycles to investigate that.
  https://chromium-review.googlesource.com/810017

i just changed the source of adb/fastboot from CrOS to pulling the official Android prebuilts.  28.0.0.5 in the store seems to work for me ... my pixelbook can detect my pixel 2 phone.
►

Sign in to add a comment