Very important stuff.

See
https://developer.android.com/guide/topics/ui/notifiers/notifications.html#NotificationResponse

If the schema of the database is incompatible with the schema expected
by the code, the database throws a DbSchemaException. LifecycleManager
indicates the error to BriarService, which uses HomeScreenActivity to
show a notification and quit the app.

Fixes bug #7. The service is restarted after a crash even if
onStartCommand() returns START_NOT_STICKY, but after restarting the DB
key is not restored and so the app can't usefully proceed.

This allows quick access to any part of the app, including quitting (two
touches).

See issue #3612607.

CryptoExecutor and DatabaseExecutor now use bounded thread pools with
unbounded queues, since running too many tasks in parallel is likely to
harm performance; IncomingConnectionExecutor, PluginExecutor and
ReliabilityExecutor use unbounded thread pools with direct handoff,
since their tasks may run indefinitely. There are no longer any bounded
executors, and all executors discard tasks when shutting down, which
fixes issue #3612189.

Responsibility for starting and stopping services has been moved from
BriarService in briar-android to LifecycleManagerImpl in briar-core.
However, BriarService is still responsible for stopping the
Android-specific executors, which is ugly. It would be better if
executors registered themselves with LifecycleManager.

This should make it possible to develop the core in Eclipse without the ADT.