However, like what we've have for eng build, one may simply hook
android-tools-adbd service to another valid property under user build,
e.g. "ro.build.type=user".

device# cd /ubuntu/etc/systemd/system
device# mkdir android-contai...@ro.build.type\\x3duser.target.wants
device# cd android-contai...@ro.build.type\\x3duser.target.wants
device# ln -s /lib/systemd/system/android-tools-adbd.service

Here, the folder name is "android-
container@<KEY>\x3d<VALUE>.target.wants". That backslash character is
required.

** Also affects: android-tools (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1632602

Title:
  no adb access under xenial+systemd user build

Status in Canonical System Image:
  Confirmed
Status in android-tools package in Ubuntu:
  New

Bug description:
  adb service under user build involves several other parties and is
  currently not implemented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632602/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to