Bugfix - FlyingF3: PWM6 and PWM7 used wrong AF

They bothed used AF2 which is unused for these pins
instead of AF1 so the PWM functionality wasn't
working.

Fixes #449
Android: start implementing navigation bar
Android: navigation bar now appears

It only appears for the abstract base class right now
because all of the child classes load their own layout
which does not provide the needed elements.
Android: add nav bar to home page
Android: add nav bar to controller activity
Android: add nav bar to logger activity
Android: add nav bar to PFD activity

This one is done slightly differently since it was already
using a fragment manager. It just adds the fragment to the
main drawer layout.
Android: add nav bar to object browser
Android: add nav bar to tuning activity
Android: add nav bar to map

This also had to be done differently. Initializing the
map fragment was failing when done statically in the xml
file so not it is done dynamically.
Android: add nav bar to alarms page

This was done like the PFD and just uses the fragment
only.
Android: use nicer Navigation Drawer interface

This is based on the code found here
http://www.michenux.net/android-navigation-drawer-748.html
Android: nav bar launcher working
Android: add nav bar to attitude adjustment
Android: remove outdated home page
Android: init activities via nav bar

The nav bar is configured with the layout information
so the base class can expand the activity and have
access to the navigation slider.
Android: move ObjectEditView to view package
Android: add nav bar to tablet page
Android: save map zoom depth

Now when restoring the map it will keep the same zoom. However,
the onDestroy is only called when using the back button and not
when opening a new activity so going to the map multiple times
doesn't change things.
Android: always use map fragment

There was a lot of duplicate code in the activity which
did not need to be used anymore.