no adb access under xenial+systemd user build
Bug #1632602 reported by
You-Sheng Yang
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
You-Sheng Yang | ||
android-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
adb service under user build involves several other parties and is currently not implemented.
Changed in canonical-devices-system-image: | |
milestone: | none → x1 |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
importance: | Undecided → Critical |
Changed in android-tools (Ubuntu): | |
status: | In Progress → Confirmed |
To post a comment you must log in.
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 \\x3duser. target. wants \\x3duser. target. wants system/ android- tools-adbd. service
device# mkdir <email address hidden>
device# cd <email address hidden>
device# ln -s /lib/systemd/
Here, the folder name is "android- container@ <KEY>\x3d< VALUE>. target. wants". That backslash character is required.