[Android Apps and Games] FFU5y:
I'm going to assume you've either already tried auto_patcher, or building it is the important thing for you, so jumping straight to that:

The best place to start is the Google information about setting up a build environment

Also The CyanogenMod build guide is good. (I arbitrarily selected the Maguro one, but it jumps to the part of most relevance to you).

The build environment needs to be 64-bit Linux. I use Ubuntu 12.04. You can run that in a virtual machine, but it will be faster if you can run it bare-metal.

Keep in mind:

Building takes a lot of drive space. Expect transient space usage of ~50GB.

Building takes processing time. My builds (from scratch) take up to 8 hours (core 2 duo laptop with USB drive and 4GB of RAM, to be fair)

Downloading the source consumes a not of traffic. Expect to download ~12GB. To save on transfers if you are doing new repo checkouts in future, consider mirrors and/or get to know the '--reference <previous_sync>' and 'git repack -a' commands.

Once you have a build environment set up, it is a matter of choosing the relevant patches to apply. There are patches available for both OpenPDroid and PDroid 2.0. If you want to go with PDroid 2.0, use the CM10 patches and then manually merge the rejects. If you are going with OpenPDroid, there are patches for AOKP, CM and soon PA - you can try each of these (separately - don't apply more than one at a time), see which apply best, and then manually merge the rejects.

To patch, go to the root of your android checkout and do the following for each patch:

patch -p1 < <patch_filename>

If you want to capture the output of the patch, you can do

patch -p1 < <patch_filename> &> output.txt

Once that's done, you can build!

I'm not familiar with JellyBam, but if it is a reasonably commonly used ROM and you are going to be building reasonably regular updates you may want to consider becoming a maintainer for OpenPDroid or PDroid 2.0 (whichever you go with).

You need the sources: remember, ~12GB of sources. Make sure you're ready for it :P

By the way, regarding '--reference':

If you already have an android checkout, you can reduce the download doing a new one by using the command

repo init -u <location of manifest, e.g. CyanogenMod's android git project> -b <branch_name> --reference=<location of another checkout>

For example:

repo init -u https://github.com/CyanogenMod/android.git -b cm-10.1 --reference=/mnt/android/cm10/

Then when you sync, it will look for the content in the 'referenced' project first, before using the net connection.

Once you've done the sync, make sure you repack your new checkout using the following command:

git repack -a

If you don't do this, the new checkout remains linked to the 'referenced' one, and deleting the referenced one destroys the new checkout. This is bad! Make sure you repack.

---------- Post added at 10:43 AM ---------- Previous post was at 10:30 AM ----------

The first thing I would try is deleting the intermediate files for the framework building process.

i.e.

rm -r out/target/common/obj/JAVA_LIBRARIES/framework_intermediates

I have found that tends to resolve quite a few build problems with symbol errors of that sort. Hopefully it will solve it for you too.

The other thing is that at a glance, some of those errors look a lot like what I saw when I was working on the Android 4.2.1 port. That doesn't necessarily mean anything - just an observation.