[Android Software/Hacking General [Developers Only]] mateorod:
It is possible. I am looking at some evilisto stuff already. But that post is a PERFECT example of what the Auto-Patcher can do. What a conscientious developer/themer that guy is.

You have to love someone who makes something people like, and then provides the means to distribute it. But of course, this thread wouldn't exist if I didn't think we had discovered a better way.

As you can see evilisto has attached patches to the end of that post. Those are build patches, which are applied to the actual source code before building. Which is awesome, but only useful (mostly) to rom developers, as they are the ones who design the roms and decide which extra to include.

The Auto-Patcher distributes and applies smali patches. Smali binaries get a bad rap, but we have stumbled upon a method that puts them to use for the Good. What we need for every mod we offer is a built rom and then another build with the build patches attached. Then we have scripts that take it from there.

Those smali patches are what allows you (the users) to pick and choose your own elements, without having to build OR edit code.

One of my MAIN goals as this project progresses is to revamp and attack the documentation that goes with our patch-making scripts. But they are already written and can be found with our auto-patcher source code. Look at them here.

I have been working pretty hard attempting to streamline our code, as well as add comments and clear up some ambiguous variable names. That initiative is obviously ongoing. I would like the auto-patcher to be seen for what it is- a program that can legitimately port just about any mod/theme/framework to any rom/device. At the moment, it is mostly known for pdroid distribution. Which is great. But we can add anything. The only question is how much TLC it will require.

But if we can port PDroid and PDroid2.0 (Those are MASSIVE framework changes. I don't know if people realize how insane this project can be) we can do anything.

Here is a little overkill people may not want, but look here:

for FILE in ${TXTS[@]}; do
TXT=${FILE##*/}
if [[ -f $PARB/${TXT}.patch ]]; then
printtask "... apply $TXT.patch ..."
patch -Nls -p2 -d system/ < $PARB/${TXT}.patch 2>&1 > ${TXT}.log
#cat ${TXT}.log | tee -a "$LOG"
[[ `grep FAILED ${TXT}.log` != "" ]] && printerror "failed $TXT.patch"
fi
if [[ -f $PAR/${TXT}.awk ]]; then
printtask "... apply $TXT.awk ..."
awk -f $PAR/${TXT}.awk $FILE > text || printerror "failed $TXT.awk"
mv text $FILE
fi
if [[ -f $PAR/${TXT}.sed ]]; then
printtask "... apply $TXT.sed ..."
sed -f $PAR/${TXT}.sed $FILE > text || printerror "failed $TXT.sed"
mv text $FILE
fi
if [[ -f $PAR/${TXT}.sh ]]; then
printtask "... apply $TXT.sh ..."
. $PAR/${TXT}.sh 2>&1 >> ${TXT}.log || printerror "failed $TXT.sh"
fi
garbage system/
done
done

That is from the Auto-Patcher main script. That is the functionality to add any text-editing features we want. That means any script can be resolved. All those little tweaks and terminal actions (creating swap files, creating mount points etc) can be incorporated.

I have the great fortune of having some great people sign up to help me maintain the most volatile patches (Pdroid related, all). Along with Kobik77's ApG, wbedard. poncik, FFU5y...those people taking over some of the day-to-day building activities have freed me up to begin improving and solidifying the program. And that means looking for new additions.

What, that wasn't what you were asking about?:silly: I can get carried away.

I will work on adding evilisto mods over the next several days. I would like to have some new additions for 2.5, which I plan to release when we get our patches done for the Android 4.2 code update. Those will be easy to make, from the looks of it.

Thanks a bunch for the suggestions, and for indulging me in my TMI.

Edit: Let me say this, though. For themes, they will likely only work with the same resolution (i.e. hdpi, or xhdpi, mdpi...etc) unless I get a themer on board to resize images and the like. But they will port for the proper resolutions I am fairly certain.