[Android Software/Hacking General [Developers Only]] mateorod:
Oh, I didn't know that about XPrivacy. I havent had as much time to look at that as I want to. I know that MB66 is a sharp guy, he contributed a fix to OpenPdroid in the early days. But I agree about needing to block system apps and system processes. I don't install user apps that I don't trust completely...system apps are the number one thing I want protection from.

XPrivacy has the very real advantage of not needing to patch updates...but I have a method for that for OpenPdroid too, Hopefully one day I can get it out there.

Thanks for showing me this...I always have to hedge my bets with ApG since I only tried it once in its very early development. Now I know where to send people.

There are "kitchens" which can deodex entire roms for you...but there may be a reason why the only custom rom for your hardware is odexed. If you are willing to build from source, you can surely apply our source patches from the OP.

Well, we mostly ship text, not binaries. The only binaries we have are apktool and sdk components. But you have every reason to be confused about the latest autopatcher.

I added an auto-update function to the autopatcher awhile back, and then stopped posting updated packages so I could see where and when that function was working, as well as for whom. You seem to be in one of the use cases where you are not getting updates.

ApG has automatic updating through the GUI so I disabled it for Cygwin. Most Linux and OSX users who get the script through a git clone either update themselves or have caught up to the update where I added the feature.

My guess is that you have downloaded the packages from our download page but that you do not have the program git in your path. Could you explain your environment for me so I can account for your situation?

Edit: i just searched and saw your earlier post where you posted a log. OSX, good. That will be helpful. Can I ask you to do one more thing and then i will provide you with a concrete solution? Would you install 'git' into your system and then run it again? Here is a link to an installer GUI that may help. That should enable auto-updating. But OSX testing is very very limited. Post your log if you can do that last thing and then hopefully all will work.

Hmmm...thanks. Those lines must not play nice in Cygwin. Cygwin only makes a limited shell available. As I have expanded and refined the autopatcher I have sometimes used commands that are uunavailable to cygwin.

I will try and send that stderr message to /dev/null. You don't need to worry about it. I finally made the step of hiding all extraneous and handled error messages to the log only, so as to cut down on bug reports I was getting on patching operations that were completely sucessful. Part of that operation included the lines you are having trouble with. But all those commands do is send some colorized text to the terminal for command-line users, congratulating them on successfully running the software and gently encouraging them to not file bug reports if they see that message.

If the autopatcher is working correctly, you don't have a problem. Thanks for the report.

I guess I should put something on the OP, although I do not know how often that gets read. The 10.1.x releases are RC or Finals or Stables and use old code. Either patch a nightly release or look back over the posts from the last day or so and get instructions on how to patch using slightly older patches.