on first start use last known location
Translate new string to spanish
Updated Polish translation
Added Audi in-car wifi

Source: observation and documentation [1]

[1]: http://www.audi.de/content/de/brand/de/neuwagen/layer/audi-connect-lp.html#page=/de/brand/de/neuwagen/layer/audi-connect-lp/hinweise-und-haeufige-fragen.html
Added Konstanz-Meersburg ferry-boat SSIDs

Source: observation
minor improvement regarding enabling GPS
Merge pull request #1315 from piotrdrag/dev

Updated Polish translation
Merge pull request #1318 from JensErat/blocklist-additions

Blocklist additions
Merge pull request #1314 from stripTM/patch-10

Translate new string to spanish
Added sdk-manager-plugin support so that the Android SDK installs
automatically
Updated install documentation
Merge pull request #1319 from cascheberg/fix

@cascheberg Fix MapLocationListener pausing GPS
Merge pull request #1321 from cascheberg/fix-gps

@cascheberg Minor improvement regarding enabling GPS in MapLocationListener
Comparing GPS time and system time is a bad idea, and likely source of
bugs, use one type of time only.
The delay to wait for the gps was wrong,
t < initial-gps-delay, should be
t > initial-gps-delay then isTimeWindowForMovementExceeded() return true
Merge pull request #1331 from garvankeeley/motion-detect-one-time-system

Motion detect: Comparing GPS time and system time is a bad idea, and likely source of bugs
Merge pull request #1332 from garvankeeley/motion-detect-fix-initial-delay

Motion detect: The delay to wait for the gps was wrong,
merge
Motion Detect: more logging
- log activity shows isTimeWindowForMovementExceeded logic
- removed some log spam from the tile code
Merge pull request #1333 from garvankeeley/motion-detect-logging

Motion Detect: more logging
Motion Detect: had an extra wait period for first GPS fix. This logic is
of no value.
.
Remove this extra time window, and just use the existing time window,
called mPrefMotionChangeTimeWindowMs, in this code. The code is
cleaner with one time window (as it now has) instead of 2.

The reason the old code was not good, is that the extra time window to
wait for GPS fix is not any different than the existing motion change
time window, except that it was hard coded to 5 mins.

What would happen is that when scanning was started, and there is no GPS fix,
it would wait 5 mins before the motion detection logic would kick in.
This is confusing to anyone trying to understand the workings
of this code. It should be easy to grok based on the developer setting
(the setting for wait XXX seconds before pausing).