ubuntu-phonedations-bugs team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

lxc-android-config (0.156) trusty; urgency=low

  [ Oliver Grawert ]
  * Multiple bootspeed enhancements:
   - disable all default ureadahead jobs and replace them with a touch specific
     one. The mounting that happens in the initrd goes unnoticed and does not
     generate events, this job compensates it by looping over existing .pack
     files.
   - move ssh key generation to its own job that starts on starting ssh, so we
     do not generate keys on every OTA upgrade and on first boot but on first
     use of ssh.
   - make the lxc-android-config job properly fail if the container can not
     start so we can check for the exit condition if this job for starting an
     emergency adbd shell
   - ship an adbd-emergency-shell upstart job, that fires up adbd if the
     android container could not start.
   - switch plymouth-upstart-bridge to manual, it slows down the boot if there
     is no plymouthd running
  * switch lxc-android-config upstart job to start on started cgmanager,
    update the package dependencies accordingly.
  [ Sergio Schvezov ]
  * Provide environment vars for media-hub in a session override.


** Changed in: android-tools (Ubuntu)
       Status: New => Invalid

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

** Changed in: lxc-android-config (Ubuntu)
       Status: New => Fix Released

** Changed in: lxc-android-config (Ubuntu)
     Assignee: (unassigned) => Oliver Grawert (ogra)

** Changed in: lxc-android-config (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1301876

Title:
  start adbd if lxc fails

Status in “android-tools” package in Ubuntu:
  Invalid
Status in “lxc-android-config” package in Ubuntu:
  Fix Released

Bug description:
  In case there's a problem with lxc - not at all uncommon when doing device bringup and it happened for two devices in our team so far - we get no adb shell.
  Please let adbs start also if the container initialization fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1301876/+subscriptions