* Deal with missing parameters on Solo

* Fix trigger set

* travis-ci add more caching

* travis-ci move doxygen to semaphoreci

* travis-ci move linux debug to semaphoreci

* travis-ci try ccache on OSX and android

* travis-ci ccache stats

* try again

* Attempt to prepend ccache to qmake command

* Test enabling ccache for ios too

* Deploy ccache from S3 per @dagar

* Revert "Test enabling ccache for ios too"

It was a nice thought.

This reverts commit 7e7aeb367696ee9c8abc5cc8122dcd35196d96bb.

* Try to optimally set the number of make jobs

* Fix job estimation and disable ccache on android

* Android: reenable ccache and disable parallel jobs

* Check if android build passes with 4 workers

* Try to parallelize xcodebuild too

* Give mac builders an extra worker and pretty up the ios build output

* Add make output filtering with correct exit code, no sudo or ccache on ios build

* Try wrapping ccache to enable use on xcodebuild

* Make ios ccache helpers executable

* Turn back on pretty printing for IOS

* Show some ccache stats on IOS build to see if we're getting hits

* Change android build OS type to linux

* Require trusty for android build

* Require sudo for android so we get trusty

* Maybe this will function properly on edge?

* Try to use stripped binary bzips

* Screw it! Run android on precise again

* Back to the original android build configuration. I give up

Temporarily disable MAVLink version check as the QGC settings have no effect and it will mess with the upgrade from v1 to v2 and has no real value

Add voltage/current calculators

Support both THR_MID and MOT_THST_HOVER

ArduCopter 3.4: Update meta data

Rover radio cal

Throttle trim must be center throttle

Support for "Use compass" params

Plan: Mission loads from vehicle automatically

Rover fixes

Parameter loader fixes

- Cache only supported on PX4. Solo sends param updates at a high rate
to update gimbal values. This was causing the cache to update itself at
too high of a rate, killing performance, especially on iOS.
- Fixed read/write index usage to provide correct progress bar updates

They may show up after parameters ready is signaled. No way around this
since this is a protocol problem. So can’t test secondary component.