Sorry. It appears in r2867 (which went into Mir 0.16.0) we broke the binary input event protocol (which is separate to protobuf). It's sufficiently broken that any Mir-0.15 or earlier client will reject and ignore all input messages it gets from v0.16 or newer servers.
http://bazaar.launchpad.net/~mir-team/mir/development- branch/revision/2867#3rd_party/android- input/android/frameworks/base/include/androidfw/InputTransport.h It would be difficult and messy to repair the problem sufficiently such that the old and new binary formats could be supported simultaneously. Not impossible, but probably not something we're going to invest in right now. That plus r2893 made the problem worse by rejecting older clients outright, possibly without knowing the intricacies of the r2867 regression. Again, sorry this happened. The relevant people have been informed so hopefully it won't happen again. ** Changed in: mir Status: Triaged => Won't Fix ** Changed in: mir/0.16 Status: Triaged => Won't Fix ** Changed in: mir/0.17 Status: Triaged => Won't Fix ** Changed in: mir (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507982 Title: [regression] OTA7 broke previously working app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
