** Description changed:

  Snappy heavily rely on systemd system session and xenial has systemd by
  default.
  
  [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
- 56.
+ 59.
  
- 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 (bug 
1632602). 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. Go to Settings::About page to enable developer mode.
  
- 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 \
-   /ubuntu/lib/systemd/system/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.
- 
- [1]: 
https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial
- [2]: 
https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097
- 
- [All Pending MPs]
- 
- 1. lxc-android-config:
- * 
https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097
+ [1]: https://code.launchpad.net/~avila-private-team/avila-
+ private/+git/platform_manifest/+ref/xenial
  
  [Prebuilt rootfs tarball]
  
  
https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2
  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
Phonedations bugs, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1625023

Title:
  switch to systemd on ubuntu phone xenial

Status in Canonical System Image:
  In Progress
Status in android-tools package in Ubuntu:
  Fix Released
Status in lxc-android-config package in Ubuntu:
  Fix Released
Status in ubuntu-touch-meta package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  New

Bug description:
  Snappy heavily rely on systemd system session and xenial has systemd
  by default.

  [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
  59.

  2. Go to Settings::About page to enable developer mode.

  [1]: https://code.launchpad.net/~avila-private-team/avila-
  private/+git/platform_manifest/+ref/xenial

  [Prebuilt rootfs tarball]

  
https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2
  md5sum: 4fc880e60fcf66857fbbeff6ce58e025
  build_number: 56
  version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56

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

-- 
Mailing list: https://launchpad.net/~ubuntu-phonedations-bugs
Post to     : ubuntu-phonedations-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phonedations-bugs
More help   : https://help.launchpad.net/ListHelp

Reply via email to