Mir

tools/install_on_android.sh kills adb, rendering the device uncontactable (since flipped images)

Bug #1206369 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Daniel van Vugt
mir (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I just upgraded the Nexus 4 for the first time in a month or two and found adb frequently goes AWOL. adb often can't find any devices till the phone is rebooted. And even then, it only works for a while before vanishing again...

$ adb devices
List of devices attached

$

Image: 20130726.1
Device: Nexus 4 mako

Related branches

affects: indicator-server → phablet-tools
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

When the Nexus goes AWOL, the PC it's connected to gets this in dmesg:
    USB disconnect, device number 24

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I have even tried reflashing everything today. Went back to Android and then phablet-flashed again. Still the problem persists.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, think I found the problem. It's Mir's android installation script. It hasn't been updated to work for flipped images and inadvertently kills adb on the device.

Changed in mir:
status: New → In Progress
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in phablet-tools:
status: New → Invalid
summary: - adb frequently goes AWOL. Can't connect to phone without rebooting it.
+ tools/install_on_android.sh kills adb, rendering the device
+ uncontactable (since flipped images)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision 894, scheduled for release in mir, milestone 0.0.9

Changed in mir:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mir - 0.0.8+13.10.20130731.2-0ubuntu1

---------------
mir (0.0.8+13.10.20130731.2-0ubuntu1) saucy; urgency=low

  [ Dmitrijs Ledkovs ]
  * Use explicit boost-dev packages.

  [ Alexandros Frantzis ]
  * gbm: Support non-cloned display configurations.

  [ Thomas Voß ]
  * Adjust documentation to account for lightdm/packaging changes.
  * Don't make Mir become a process group leader, to avoid CTRL-C
    killing the X server.

  [ Alan Griffiths ]
  * test_framework: Provide boost exception diagnostics.
  * graphics: Remove use of frontend::Surface from graphics interface &
    implementation.

  [ Daniel van Vugt ]
  * Don't run Android commands which are no longer valid in flipped
    phablet images. They will only kill your connection to the device.
    (LP: #1206369). (LP: #1206369)
  * Fix documentation to suit the new "flipped" phablet images. Also
    remove extraneous comment which could cause copy/paste mistakes.

  [ Eleni Maria Stea ]
  * mir option --nested-mode <host-socket>.
  * added a native platform interface in
    include/server/mir/graphics/native_platform.h added a new static
    library for the nested platform added some stub
    create_native_platform and create_nested_platform functions to be
    called when mir runs in nested mode.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 901
 -- Ubuntu daily release <email address hidden> Wed, 31 Jul 2013 12:55:57 +0000

Changed in mir (Ubuntu):
status: New → Fix Released
Changed in mir:
importance: Undecided → Medium
Changed in mir (Ubuntu):
importance: Undecided → Medium
no longer affects: phablet-tools
Changed in mir:
milestone: none → 0.0.9
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.