lp://staging/~kdub/mir/richer-fd-in-android-platform

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

1789. By Kevin DuBois on 2014-07-25

reenable all tests

1788. By Kevin DuBois on 2014-07-25

update for the removal of the gmock additions

1787. By Kevin DuBois on 2014-07-25

merge in copy con

1786. By Kevin DuBois on 2014-07-25

tmp

1785. By Kevin DuBois on 2014-07-22

tmp

1784. By Daniel van Vugt on 2014-07-22

Automate checking for ABI breakage.

This may well be over-sensitive to header changes that don't constitute
ABI changes, but I think that's better than being under-sensitive.

You can find out which headers are causing the failure by running:
  sha1sum -c server-ABI-sha1sums
  sha1sum -c client-ABI-sha1sums

If the offending change is a real ABI break, bump it! Then regardless of
whether it was a break, generate a new checksum for the file using "sha1sum"
and insert it into {client,server}-ABI-sha1sums.

Approved by PS Jenkins bot, Daniel van Vugt, Cemil Azizoglu, Alan Griffiths, Kevin DuBois.

1783. By Kevin DuBois on 2014-07-21

android: do not propogate errors when initially turning on the display, as some of the rc's from the driver indicate that the display is already in the state that was requested.

fixes: lp: #1345533.

Approved by PS Jenkins bot, Alberto Aguirre.

1782. By Robert Carr on 2014-07-21

Provide some symbolic names for cursors.

Approved by PS Jenkins bot, Kevin DuBois, Cemil Azizoglu, Alan Griffiths.

1781. By Alan Griffiths on 2014-07-21

config: remove support for the legacy client code.

Approved by Daniel van Vugt, Kevin DuBois, PS Jenkins bot.

1780. By Daniel van Vugt on 2014-07-21

Stop Android logging from consuming significant CPU (on every input event).
(LP: #1343074)

Two things needed fixing:
  1. Verbose logging (ALOGV) is meant to be disabled (optimized out) unless
     debugging, but it wasn't ever being removed. This means expensive calls
     to ALOGV remained, for example in EventHub.cpp on every input event.
  2. Our own Mir version of __android_log_print was extremely inefficient,
     formatting log messages unconditionally even when they did not meet the
     reporting threshold and were never used.
. Fixes: https://bugs.launchpad.net/bugs/1343074.

Approved by PS Jenkins bot, Daniel d'Andrada, Kevin DuBois, Alan Griffiths.