vendor: update apns-conf.xml

Referenced SlimROMs and CM for ordering

Change-Id: I611f4c7dc4275dcca5a3329dc6e1bceffb042f49
Signed-off-by: Jake Whatley <jacob.whatley91@gmail.com>
[7/7] omni: exFAT Support

FUSE based exFAT Implementation

android: https://gerrit.omnirom.org/#/c/4448/
e2fsprogs: https://gerrit.omnirom.org/#/c/3191/
fuse: https://gerrit.omnirom.org/#/c/4443/
sepolicy: https://gerrit.omnirom.org/#/c/4444/
vold: https://gerrit.omnirom.org/#/c/4441/
vold: https://gerrit.omnirom.org/#/c/4442/

Change-Id: I45e6a30a5594b3cecba6424e4a932905972f9223
Utils: Add GitHub forking tool

Change-Id: Ida89d9e331ccdcbf627195f33c17129d383c87e2
utils: Update AOSP forking script

Change-Id: Ifbb68a5940c079b8b0898e6a7d66df92d9077c28
Merge "Utils: Add GitHub forking tool" into android-4.4
Merge "utils: Update AOSP forking script" into android-4.4
Mackay ROM

Change-Id: Ie881215e05451ef85cd72411b6f57c0b13faf0bd
Changed package selection

Change-Id: I22e41eff8928cce4d75095370b10fcbbb46b6ce8
init [1/4]: set permissions on governors sysfs nodes

1. interactive
2. ondemand
3. assume smp uses shared cpufreq policy for all CPUs

also, set permission for boostpulse
it will fix some permission issues like:

E/S5PC110 PowerHAL(  482): Error writing to boostpulse: No such device
E/S5PC110 PowerHAL(  482): Error opening interactive boostpulse interface: Permission denied
E/S5PC110 PowerHAL(  495): Error opening /sys/devices/system/cpu/cpufreq/interactive/timer_rate: Permission denied

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: I581aaa1daf2ba5911e89398a4f8a1567fd6569c9
init [2/4]: set permissions on schedulers sysfs nodes

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: Ib7653a008bbeb978ea1bca77cb76ab4e609d48b6
init [3/4]: allow system to modify ksm control files

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: Id4e70992f34c8039c06ab1131b9cc2195f6e3b63
init [4/4]: set permissions on notify_on_migrate node

 * Used by PowerHAL

Signed-off-by: Humberto Borba <humberos@gmail.com>
Change-Id: Ifbf58c145522d82d220fbae39a6b7319971ecbb5
sepolicy[1/2]: Start OmniROM Common sepolicy

Rather than having to maintain out of tree changes, it is often
easier to maintain a hiearchy of changes, starting with the vendors
common config file. From there, inheriting products can pick up a base
and start to add or remove certain bits from it, making use of the
BOARD_SEPOLICY_* functions documented in external/sepolicy/README.

appended line as example below:
line 1 "vendor/omni/sepolicy/file_contexts"

It requires: https://gerrit.omnirom.org/#/c/4795/

Signed-off-by: Humberto Borba <humberos@gmail.com>
Signed-off-by: William Roberts<wroberts@tresys.com>
Change-Id: I13244e5c6fc64ef5c3f94ff2bc03fcbc96619490