README: Update

Update link from i9100/P thread to main development thread on XDA.
use different USB PIDs for adb and adb+ums modes

Commit ad054c684524962eae3269c1d807dc60e8bca1ec made it so that
the same VID/PID pair was used for both adb and composite adb+ums
modes, which prevents the installation of drivers in Windows so that
either mode can be supported.

This uses the original VID/PID pair (18d1/d001) for adb+ums and
uses 18d1/d002 for adb.

Change-Id: I190c821995b7fe9e8177354aec70bd02c114d122
RECOVERY_VERSION: bring inline with CyanogenMod's string

Fixes makerecoveries.sh printing an empty variable:
https://github.com/CyanogenMod/android_build/blob/cm-11.0/tools/device/makerecoveries.sh
fix compiling of Advanced Edition
libtouch_gui 1.09 (cosmetics)
fb2png 2.0.0 by @McKael and @PhilZ-cwm6
enable screen capture by default
Update 6.22.5
fix permissions
Merge pull request #13 from andi34/pull

README: Update
Merge pull request #14 from PonsAsinorem/cm-11.0

Fixes makerecoveries.sh
- merge: "recovery: Compatibility with upstream minui change"
- merge: "use correct USB PID for adb and new PID for adb+ums"
- one base version is enough
- merge: "nandroid: Convert selinux_android_restorecon calls to new API" from @kumajaya
fix fb2png flag to be enabled by default
cherry-pick: "Revert "Add a copy of the updater binary to the recovery resources""
No longer necessary when a legacy property environment is available.
from @mdmower
cherry-pick: "Make legacy prop environment available to recovery"
Google changed the in-memory format for storing properties in 4.4.
Zips containing an older update-binary expect the old format, otherwise
assertions on properties in the update script fail.
This is just enough of the old property service to copy the properties
to the legacy format before running the updater.
Note: this commit is amended by @mdmower from the original version by
_that to only provide the prop system. Edits to install.c are done in a
separate commit from scratch to maintain apache2 licensing in this repo.
cherry-pick: "Use legacy property environment if old update-binary"
Instead of falling back to a provided binary when an installation
package contains an incompatible update-binary, set a legacy property
environment. This should increase compatibility with older update
packages while still using the new property system for supported
installation packages.
Method of setting prop environment based on cyanogen's commit:
"Set ANDROID_PROPERTY_WORKSPACE in exec." Tip to rename
/dev/__properties__ so that the legacy property workspace is actually
used comes from conversation with _that.

patch by @mdmower
6.23.2

thanks @mdmower we spared 160 kb on final packed recovery.img
- still hammer lazy developers to update their outdated updater binary