[Android Software/Hacking General [Developers Only]] mateorod:
I just grabbed your ROM and as I added it to my repo of ROMs I use for checking I realized I already had it. Your ROM is made by Quarx, and as such his stuff differs quite a bit from Official Cm10 releases.

I do not know why, I do know he ports to devices that otherwise wouldn't have CM support, so maybe there are hardware limitations. But, the point is, that Quarx roms are probably the one consistent blind spot in the Auto-Patcher. Other problems do occur, but his stuff is probably the only consistent issue.

There are a bunch of scripts in our source repo (look at the diff_tools) that are expressly meant for people to create and add their own patches. We actually have a pretty kick-butt suite of tools there that pastime1971 added ages ago. I have someone who is going to maintain at least AOKP for pdroid extension, and he is getting into using those scripts.

So yeah, there are a bunch of ways to add outside mods, diffs, or programs. Those tools don't come distributed with ApG, to the best of my knowledge, or if they do, they are at minimum still command-line tools. But the whole idea of the auto-patcher is that hopefully some day people will embrace it as the all-around porting tool that it is, instead of simply a PDroid delivery service. Which is okay too, Pdroid is what keeps the interest level up for people to try the other things.

However, your suspicions about the other patches you downloaded are correct. The difference between the auto-patcher and the patches that are normally distributed through developer channels is that ALL of those diffs are source code patches, which actually differ significantly from the built code. So you couldn't apply those patches to an already built rom no matter what you do.

Also, those patches are actually syvat's original Pdroid 1.3.2 patches, so they only work on Gingerbread source. Pastime1971 updated them to ICS and then we both got together and worked out porting them further to Jellybean.

To use PDroid on Jellybean or ICS, the Auto-Patcher is your only option, unless you are willing to build from source. At which point any help you need should be broached at the patch/port thread.

See? I am usually quite helpful, but it gets my goat when people ask for help or support and then don't listen to what I have taken the time to say.

This is for sure on my wish list. As I said earlier, by hopefully the next update, the process should be much easier, with no more messing with patch dates, and the only command line arguments being the actual names of the mods you want and one of three romtypes, AOSP, AOKP or CM. No more -jb or -mod stuff.

The maintenance cost in man hours of the patches themselves has been pretty enormous lately. I am struggling to get through that. PDroid is such a massive framework change, it really deserves to be in a class by itself. But some help has surfaced lately, and I think we are getting pretty close to just expanding the team officially. I have to speak with these guys a little more, but i have some solid leads on maintainers for some of these roms for PDroid/Extension. And that will free me to start pounding out some GUI's.

My goal is a GUI for all supported platforms (maybe not OSX, but for sure Linux and Android) in the next six months. I hope to have it out well before even that, but that is my self-imposed deadline for Google Play support, at least.

But I am glad to hear that the command-line didn't prove to be too hard- we do try and keep it manageable. It will be easier when our next big update goes out, either next update or the one after that.