Move SDK specific methods into Compat.

On certain devices (e.g., Donut), the application crashes if a class is
using a method that does not exist with a VerifyError even before any
methods on the class can be invoked.

To avoid this, we introduced a Compat interface, which hides all the
platform specific method calls. However, the disableWriteAheadLogging()
method was being called on SQLiteDatabase without following this
pattern, leading to a crash on start-up.

This commit moves those calls behind the interface.
Merge pull request #134 from flerda/v2.0.2-donut

Move SDK specific methods into Compat.
Remove unnecessary try/catch.

Since we now use the Compat class, there is no need for the try/catch
block.
Merge pull request #135 from flerda/v2.0.2-try

Remove unnecessary try/catch.
Add disableWriterAheadLogging() on Nook HD Plus.

The Nook HD Plus seems to have trouble without calling this hidden API.
This should fix users of this device. Further testing is required to
know if the same fix is required on other versions of Nook as well.
Merge pull request #136 from flerda/v2.0.2-nook

Add disableWriterAheadLogging() on Nook HD Plus.
Fix query to find siblings in order to bury them.
Merge pull request #137 from hssm/v2.0.2-sibling-bury-fix

Fix query to find siblings in order to bury them.
Bumped version to 2.0.2beta8
Merge pull request #138 from flerda/v2.0.2-beta8

Bumped version to 2.0.2beta8
Kanji Info for Ankidroid! Second version.
Improve Aedict integration

When Adding card via Aedict intent, automatically add meaning
information when avaliable. Before it was only adding the
reading(hiragana) and the word in kanji. With this new functionality, if
the user model has at least 3 fields, extra information will be added
(meaning/reading/kanji).
Nullcheck in StudyOptionsActivity.onMenuOpened
Extract custom fonts into an extension.

Currently, a lot of our classes have a very large amount of code,
implementing many different features, all mixed together. This is quite
hard to manage and makes the code overly complex.

What I am aiming to do is separate out some of the code that does
related things, offering a better paradigm for implementing new features
that does not clutter the existing code.

As a proof of concept, I am aiming to extract the Custom Fonts support
(which I wrote and therefore know reasonably well) into a set of classes
that separate classes that define anything relating to that particular
feature, so that the rest of the code does not need to know about it.

This is a work in progress: it will take a bit of time to get to the
perfect solution; but it is a step forward in that direction. Probably
things will change as I go along, so nothing is really final yet.