verify the following build have adb after turned on in system-settings.
current build number: 68
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2016-10-26 00:51:22
version version: 68
version ubuntu: 20161025
version device: 20161014.0
version custom: 20161025
**
All necessary changes merged.
--
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
Temp work-arounds have been proposed. Please keep this bug open even if
they're merged later.
** Changed in: android-tools (Ubuntu)
Status: New => In Progress
** Changed in: android-tools (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you
After some discussion, we can also enable "ro.debuggable=1" in user
builds temporarily and revert it when all is ready.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
--
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
** Changed in: canonical-devices-system-image
Milestone: None => x1
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
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
7 matches
Mail list logo
