** Description changed:

  Snappy heavily rely on systemd system session and xenial has systemd by
  [steps to construct systemd-based avila]
  1. flash images built from xenial branch [1]. This should gives a
  working xenial+upstart avila. Following steps are based on rootfs rev
- 51.
+ 56.
+ 1.1. If your system is a user build, e.g. flashed from u-d-f, you need to 
create an additional symbolic link to automatically enable adb access. You can 
do this under recovery mode:
+ 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
  2. Reboot into recovery mode and manually change upstart-local-bridge service 
type to simple. (bug 1632260)
  host$ adb shell
  device# mkdir ubuntu
  device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu
  device# exit
  host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service .
  (edit the file as mp[2] does ...)
  host$ adb push upstart-local-bridge.service \
  host$ adb shell
  device# sync; sync; sync
  device# umount /ubuntu
  device# exit
  host$ adb reboot
  3. Go to Settings::About page to enable developer mode.
  [All Pending MPs]
  1. lxc-android-config:
  [Prebuilt rootfs tarball]
  md5sum: 4fc880e60fcf66857fbbeff6ce58e025
  build_number: 56
  version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  switch to systemd on ubuntu phone xenial

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to