[Android Software/Hacking General [Developers Only]] Deviant Ollam:
ah, i had not noticed that earlier version... i did actually try the -h flag to see what it would turn up. But thank you, mateorod, for spelling it out in greater detail so that people like myself who read this thread can benefit from a detailed explanation as to what is expected

I had higher hopes, since the process didn't error out right away, but i still encountered some patching failed errors, as seen below...

!!! PATCHING FAILED FOR android/content/pm/ContainerEncryptionParams.smali !!!

File for which patching failed:
---------------------------------------------

ContainerEncryptionParams.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

But IT MAY NOT WORK!!!

Do you want to proceed ? (YES/no) y

Are you sure ? (YES/no) y
... replace android/content/pm/ContainerEncryptionParams.smali ...
... apply core.patch ...
... apply services.patch ...
1 out of 7 hunks FAILED -- saving rejects to file smali/com/android/server/am/Ac
tivityManagerService.smali.rej
136 out of 137 hunks FAILED -- saving rejects to file smali/com/android/server/S
erverThread.smali.rej
!!! PATCHING FAILED FOR com/android/server/am/ActivityManagerService.smali com/a
ndroid/server/ServerThread.smali !!!

File for which patching failed:
---------------------------------------------

ActivityManagerService.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

But IT MAY NOT WORK!!!

Do you want to proceed ? (YES/no) y

Are you sure ? (YES/no) y
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed services.patch
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

! please refer to /cygdrive/c/Users/Deviant/Desktop/pDroid stuff/ApGPackages/ap/
log20121021215951 for any debugging

! patching failed.
! it may be possible to patch /cygdrive/c/Users/Deviant/Desktop/pDroid stuff/ApG
Packages/ap/CM10-20120924-NIGHTLY-mb525.zip using other patch version

The Auto-Patcher v2.1.9
pdroid 1.32 patches 2012.09.13.
v6supercharger patches 2012.08.17.

usage: ./auto_patcher ROM.ZIP MODS [ROMTYPE] [PATCHDATE]

MODS can be pdroid,v6supercharger or pdroid or v6supercharger
optional [ROMTYPE] can be cm9, aokp, etc.
optional [PATCHDATE] can be specified to use older patch versions.
try "./auto_patcher ROM.ZIP -h" to see what is available

it would seem that the error message is attempting to suggest the use of the same pdroid code package that others had suggested (20120913)... i love what i'm hearing in the discussion of a new version of the auto-patcher. it will hopefully help out folk like me who are still scratching the surface in this field.

---------- Post added at 03:12 AM ---------- Previous post was at 03:07 AM ----------

just to follow-up, because you took the time to ask for clarification (albeit, you did so in a way that was pretty scathing, heh) when i was spoke of "internal" patches, i was referring to the code packages that are incorporated with the Auto Patcher utility itself.

i had also downloaded these new .diff files separately (in pdroid132_cm10.tgz) and was asking if there was a way for the Auto-Patcher to make use of those additional files -- files that are external to the program itself. From what you're saying, the two are not part of the same process.

So, if i'm starting to understand more about this... .diff files something to do a quick modify of source code, while the Auto-Patcher is performing patches on ROMs that have already been compiled? (and, thus, the Auto-Patcher wouldn't make use of diff files) just seeing how close to reality my perception of all this is.