[Android Software/Hacking General [Developers Only]] Urinophoria:
Looks like in both cases you're using old patches:

Patches are openpdroid/4.2/cm/20130516

Can you flag "latest" and give it another rip?

At least for CM that is; the Task650 AOKP may not work. He's actually done a lot of work on that ROM that has diverged from stock AOKP. It actually stopped working on auto-patcher a while back, but it was breaking in framework back then.

That's not criticism, btw. I'm a huge fan of his breed of AOKP on the i747, but he definitely made it his own.

(another edit: It may not be divergence/fragmentation, it may just be that he's so damn much faster than Official AOKP) I'm building some patches for it right now. If it finishes in the next 20 or so, I'll post them up with some basic instructions.

If it doesn't work, let me know, I keep his repo synced on my machine and can either build you some patches or have Mateorod train me on provisionals if its still close enough.

[MENTION=4342828]mateorod[/MENTION] As of this instant, autopatcher is still patching CM10.1 just fine from the Linux command line (on my machine). I'm going to flash it and test pdroid manager functionality in about 10 minutes to see if I can duplicate/fix [MENTION=1786104]Christoph21x[/MENTION] issues.

---------- Post added at 07:58 AM ---------- Previous post was at 07:39 AM ----------

Bad news is, I can't duplicate it from here. Good news is, there are still unexplored variables (like where did you get pdroid manager?). So far everything is working brilliantly on my phone, but I normally run PAC or Task's AOKP, so it was a full-wipe install for me.

So, variables:

1) Did you full wipe?

2) I got my pdroid manager off the play store, where did you get yours? Since the problem seems to be in manager (my AP log was near identical to yours where it counted) I'm wondering if you have some bad data in the settings for PDroid Manager. Maybe clear data for it, uninstall it, reinstall it?

3) I need to fire up my VM and try it with APG, lol.

Let me know on the first two, and I'll work on the third.

Edit:

Ok, just took a run at variable #3, Everything is still working good @ my end, even with (I died a little inside) patching from windows. That leaves a question of the first two variables. If you did a full wipe, and you've cleared data for pdroid manager and reinstalled it, can you get an adb logcat of you going through each of your 4 scenarios? A little weird that it would do that to you on 3 different devices if it was a variable like that; but then I have my tf101 set up almost identically to my s3, so if your usage habits are anything like mine, it's still possible. Improbable, but possible. Considering that lately I'm syncing all my local repos a couple times a day, and CM is taking between 5-20 minutes every time I sync it; there's a chance (if you're dirty flashing) you got hit with framework changes that mess up the communication between openpdroid and manager.

At least that's my theory behind why it might break on a dirty flash. I cheat a little and dirty flash already patched builds when I update PAC, so my common use scenario is (probably) a little different from yours.