yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] dirtyreturn:
In the pdroid2.0 thread - it replaces the original pdroid app correct? Patching either of those separately were both successful. From now on IT IS one or the other, right? A thousand thanks, mateorod, for the consistency of your help in getting some peace of mind with this stuff.
[Android Software/Hacking General [Developers Only]] mateorod:
Yep.

People need to patch for pdroid and use the original apk or patch for pd2.0 and use the PDroid 2.0 app.

Any mixing and matching will cause massive issues.

Before switching pdroid versions (either way), you should go to data/system and delete everything that has the word privacy in it. Do that before flashing the newly patched rom or else you risk FCs.
[Android Software/Hacking General [Developers Only]] poncik:
pdroid2 patching failed for evervolv nightly (http://dl.evervolv.com/n/2012.10.25/Evervolv-turba-3.1.0-bravo-nightly-20121025.zip)

http://codepad.org/bnsgvr2K
[Android Software/Hacking General [Developers Only]] mateorod:
Ok, so thanks for this info. It took awhile, but I found the problem, which was a BIG problem for anyone patching for ICS. So I am thankful to you for bringing it to my attention.

You also gave me some ideas for future error checks, so thanks for that.

As for your actual rom, the bad news is that it is as expected and is unpatchable using our tool at the moment. Not that it is impossible, just that we don't have anyone building those stock roms and therefore have no patches,

Is this a custom rom? Whoever made it is not exactly conforming to best practices, if I may be so bold. Has a build date of July, yet a release date in late September. My concern that the build query was malfunctioning is what prompted me to investigate further.

Maybe there is no source for this, though and the dev has to winzip. I guess he has his reasons...

Okay, I pushed a fix to github for this, it has been hard on people. The auto-patcher will now output an error if a non-valid ROMTYPE is selected.

You used 'jellybean' as a ROMTYPE. The only valid romtypes are {cm, pa, aokp, and aosp}. Everything else is taken care of by the patcher.

As for Evervolv, well we were able to support it all the way until 4.1.2. I don't know what they did differently, but we no longer have patches to support it for pdroid or pd2.0. Sorry. I just ran your rom through all of our latest patches and no dice.

Until an Evervolv user who builds from source and is willing to give an hour a month or so comes along, we will not be able to help you guys here. Now if someone is willing to produce patched builds (just once an update, I will give them a script they can patch/unpatch in 5 mins) I will add support.

But right now I am building pdroid patches for pa, cm, aokp and aosp as well as pd2.0 patches for cm and pa. When they break (and they all break at once) that is 12 different builds I have to pump out and debug. Not to mention maintaining the support thread and the other patches while looking for new mods for you guys. That is already way more time than I have,

Post in your forums, maybe someone there would like to join the project...
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
So mate, I was able to 100% supercharge my One X rom (the one I posted a log of earlier) using zeps new script (11/8), any idea what that script does differently than the last one in order for it to work? Can we implement this into auto-patcher(cygwin FTW) so I can give my phone's rom all of your little tweaks that make my nook amazing?
[Android Software/Hacking General [Developers Only]] karamelos:
one more pdroidv2
[Android Software/Hacking General [Developers Only]] MENNENN:
[ROM]

Paranoid Android v2.51 [4.1.2] [jellybean]

[pd2.0 Log]

http://codepad.org/vHSwcIUr

[ROM]

Ice Cream Saga FINAL [4.0.4] [Sense 3.6]

[pdroid Log]

http://codepad.org/TeNrRgwn
[Android Software/Hacking General [Developers Only]] kobik77:
I still can't get why rom devs aren't willing to incorporate pdroid patches in their roms.

It would be so easy for them and by far more convenient for us users.

Have you tried being in touch with cm or aokp teams, or maybe individual rom devs?

Edit: When pd2 support for older android os' will be available are you going to drop pdroid support?

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] mateorod:
I am not sure what you are trying to tell me. The first log looks succesful to me, although there is some weird appendage that complains about compiling, which isnt what we are doing, obviously. As for the second patch for the older rom, we don't have anyone building patches for Sense. So it is unsupported.

I for sure dont have any plans to drop original PDroid support. That program has had years of vetting and trust behind it. If I see that people stop using it, then I guess I might consider it.

I dont think that they should include it by default, personally. I maintain PA for Nook Color, and I have never even brought PDroid up. These are pretty aggressive framework changes. Seems like something best decided by the individual. If there was an easy way to switch it on and off, as in restore the frameworks completely, then maybe.

I mean, this is nothing I would ever submit to cyanogen. They would be shocked.

@Greyfox- our v6 patches work for the vast, vast majority of Roms. It would likely take me an hour or two at most to expand that to most of the rest. But zep just seems vaguely displeased to be included in auto-patcher. For awhile there, he was lurking here and directing people back to one of his users software, for people that could use our patches no problem. The whole autopatcher idea came from the fact I had modified pastime's and my Pdroid Patcher to work on V6 to make supporting Botbrew packages easier.

I actually offered the V6 autopatcher to zep, just on GP, to have for his users, but he didnt see the point. So we put it out ourselves and it grew, which turned out to be for the best. But I want the autopatcher to be a tool for developers, like with trevd (3gdongle) and even pd2.0, a tool the devs use to get their work out there, something that makes life easier for them and their users. CollegeDev created pd2.0 with the auto-patcher in mind, relying on us to port his software. A pretty cool moment, something I bet we see more of.

I still offer the v6 because some people still use the patches. But I don't put any energy into keeping up with the ins and outs of the thread, nor worry too much about expanding the program. Especially since he has worked really hard at developing competing options. If he'd like to try and keep it in-house, I am not going to fight it.

I am glad that his scripts worked for you!
[Android Software/Hacking General [Developers Only]] alharaka:
Who easy would it be? How would I go about convincing devs of my ROM? The ROM I use happens to be built from source, and I would not mind learning how to build PA nightlies from my source by forking Github and experimenting with patching (although I doubt fully possible since the cool stuff is not in repo, namely the Paranoid stuff that makes the ROM worthwhile AFAIK). Or is it possible to create a "patched" ROM by merging the update.zip ahead of time if the dev does not see an interest, making a special branch.

Sorry to even seem such a noob, but your sentiment touched what I have been thinking the last several days as I finally have the ability to patch my ROM easily, and I love love love your guys work. I see this as simply the coolest project for Android, one of the strong reasons I can show someone an Android device and say "screw your shiny stuff, my shiny stuff gives me a lot of power and discretion."
[Android Software/Hacking General [Developers Only]] mateorod:
The answer here is VERY easy. Pastime1971 created build patches that ported Pdroid to ICS. I got involved to make a smali patcher for those that don't build, and then together we managed to make patches for Jellybean and the Auto-Patcher when we realized our method could work for anything imaginable.

Those build patches are easy to apply (shoot. I have to post the 4.1.2 patches. I will post them to pastime1971's port thread today.) Go to the second post of this thread, press thank you for pastime1971, and then follow the link in his sig to the port thread.

If you have the source, it is very very easy to build, no harder than building a rom regularly.

Each ROM-type we offer here just needs ONE builder to maintain the patches for an entire romtype. So someone building for PA, using our patches, could also join the team as our patch maintainer. The people who would like to see Evervolv get support back need to find someone willing to commit to that. It is probably an hour of active time a month, not counting waiting for builds to finish.

As for building PA, everything but ParanoidPreferences is now open-source. I maintain it for the Nook Color, and was beginning to despair that they would ever actually open it up. But they were true to their word, and the entire ROM is open source. I have sent a few patches upstream to them since.

The ParanoidPreferences is now available as a binary, so there is no porting when building that rom, it is a straight build. Depending on how you set up the source, it can be extremely easy to build. This is someone building my Nook source for the first time has to enter (TOTAL):

repo init -u http://www.github.com/Mateor/android -b jellybean
repo sync
lunch
make bacon

I just say all this to inspire people to give it a try, and to see it can be quite straight forward. And if you build and want to add pdroid patches, then you should consider joining the Auto-Patcher team!

We are ALWAYS looking for workers, lol.

If you want to give it a try and have issues or questions, post them in pastime's port thread, and we can help you there.
[Android Software/Hacking General [Developers Only]] poncik:
i prepared build environment and syncing with evervolv repo now. what should i do next for patching before build process?

i'm totally new to build from source thing, sorry if i ask dumb questions =)
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, awesome! I just posted to the port thread. That's where pastime1971 and I did our work for a real long time and is a better place for build discussions. Anyone else who is even considering trying to add support to an unsupported rom someday should join us.

It is challenging in the way that you learn new things, but easy in the respect that I will be there to help solve problems, so if it is doable, we will get it done.

I just posted new working patches for 4.1.2 at the end of the thread, plus some instruction. If you have any questions, go ahead and post in that thread.
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcherv2.3.0

Auto-Patcherv2.3.0 is pushed to the master branch on github. That means that anyone who can clone or pull through Git and all ApG users can get it now.

I want to thank everyone here who tested and posted logs this last week. This was a big update, with major changes everywhere we looked, from Android 4.1.2 to Pdroid2.0 to the framework of the Auto-Patcher itself.

The idea with this release (2.3.0) is for it to be something of a LTS version. Unless upstream breaks our patches (which they will, they always do) I am going to not update for awhile. I know it has been a lot of work keeping track of the changes, with a lot of updating, so we appreciate your patience. With all that turbulence, every single report was encouraging and patient. That meant a lot, so thanks.

The newest version contains all the changes in the incremental updates the ApG users have seen. You will see it on the download page sometime in the next 12 hours. I want the people with access to the source to give it one more run.

The highlights include:

Automatic Build query- automatically finds the best patch date for your build

Simplified ROMTYPES - only four now {cm, aokp, aosp and pa}

Added external_internal mod- swaps internal and external storage- use your device without an sdcard

Added pd2.0 mod - Pdroid 2.0 by CollegeDev [Thanks to FFU5y for AOKP and wbedard for AOSP patches!]

Removed addon mod- CollegeDev moved on to PDroid2.0 and it never really worked for anyone.

Improved error messages, help menu, and error checking

Added aapt permission management- an end to apktool issues, presumably...

Confirmed working with all platforms (Linux, OSX and Windows)

...and more!

A special shout-out and hat-tip to KickNGuitar, who has signed up as our official OSX tester. Without his and TheMatrix2000's time, we wouldn't have OSX working as well as we do.

I would appreciate any of the testers with ApG to please give it a run-through and see if you find any problems. If the reports go well, I will upload the official update to our download page tonight/tomorrow morning.

As always, if you use ApG, go find a post by Kobik77 and press the thank you button. Here at auto-patcher central we don't accept donations but Kobik77 does. It takes a REAL special contribution to make me comfortable pitching a donation and ApG has turned that corner. The automatic update feature was literally vital to these improvements, I don't know if we would have them without it.

Thanks to our constant testers, karamelos, harlequin, greyfox, KickNGuitar, Kobik77, jelle and many others. Your time is very appreciated.

I want to thank the Academy...and my momma...hairdresser Steve...and my cats! Always the cats...

Let me know if you encounter anything weird and try our new '-h' menu. Thanks

Did you know: The Auto-Patcher contains over 2.5 million lines of code? Use that one at yr next sexy party.
[Android Software/Hacking General [Developers Only]] asicman:
I'm trying to add pd2.0 to paranoid android 2.51 (JB 4.1.2) using ApG. It errors out when targeting both pdroid and pdroid 2.0. Doesn't seem like much info though.

ROOT= /cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/ap/
TOOL= /cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/ap//patch_tools.tgz
ROM= /cygdrive/c/Users/shiv/Desktop/gingerbread/JB/pa_maguro-2.51-24OCT2012-161109.zip
ROMX= C:\Users\shiv\Desktop\GINGER~1\JB\PA_MAG~1.ZIP

### verify tools ###
/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/cygwin/bin/patch
/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/cygwin/bin/tar
/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/Java/bin/jar
/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/Java/bin/java
/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/cygwin/bin/cpio

### verify ROM ###
### running ./auto_patcher /cygdrive/c/Users/shiv/Desktop/gingerbread/JB/pa_maguro-2.51-24OCT2012-161109.zip pd2.0 jellybean
PATH= /cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/ap/tmp20121027000442:/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/Java/bin:/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/cygwin/bin:/cygdrive/c/Users/shiv/Desktop/gingerbread/JB/ApGPackages/cygwin/usr/sbin

### unzip patch tools ###

### unzip patch patches ###

### probe rom type ###
[Android Software/Hacking General [Developers Only]] mateorod:
Does ApG display error messages? You should be seeing this if you don't follow the new directions:

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: jellybean is not a valid ROMTYPE!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!There are only four supported ROMTYPES:
1) cm 2) aokp 3) aosp 4) pa

Find out which of the above ROMTYPES your rom is based on and try again!

That is what happened when I ran it just now. ICS and jellybean are Android flavors, not rom types. The four ROMTYPES, as said in the error message as well as the post before yours are: {cm, pa, aosp, and aokp}.

Try:

./auto_patcher pa_maguro-2.51-24OCT2012-161109.zip pd2.0 pa

even though I think the rom query works for PA reliably enough that you could probably leave off the ROMTYPE altogether.

In whatever manner ApG allows you to do that. If ApG is offering you a 'jellybean' option, then you need to update, follow the link attached to Kobik77's name in my last post.
[Android Software/Hacking General [Developers Only]] mateorod:
Hmmm. Now we have seen this once before, but when he ran the patcher again it went through.

What is happening here is that the auto-patcher's operations are going through successfully, and yet on the rebuild the smali binaries are crapping out on you. They are still somewhat temperamental, being involved in some of apktool's notorious touchyness.

The last time I saw this, I went and grabbed the rom and tested it, and it patched no problem. Give me a few minutes and I will do the same for yours. You are using the patcher correctly, and everything we do has been completed without error. One of those mysterious recompile errors.

I will edit this post with my findings sometime in the next 20 mins...

edit Well, what kind of file hosting is this? Rodfile? Coming down at 5.6 kb/s. So my estimate is going to be off. You can go ahead and try running it through a couple more times while we wait, if you're game.
[Android Software/Hacking General [Developers Only]] asicman:
Mateorod, running auto patcher for the second time worked. I was able to get pdroid 2.0 running.
[Android Software/Hacking General [Developers Only]] TheRecRuiT89:
During patching Paranoid v2.52 (GNote) for pdroid-v2, i also had an error. But similar to @asicman it was succesfull with my 2nd try. So people whose patch fails for pdroid-v2, try it just one more time :)
[Android Software/Hacking General [Developers Only]] thibz:
Autopatcher 2.3.0

./auto_patcher cm-10-20121027-NIGHTLY-i9100.zip pd2.0

... apply framework.patch ...
1 out of 5 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/gsm/GsmServiceStateTracker.smali.rej

!!! PATCHING FAILED FOR com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!
!!! patch error for com/android/internal/telephony/gsm/GsmServiceStateTracker.smali !!!
askconsent final = yes: for com/android/internal/telephony/gsm/GsmServiceStateTracker.smali

but seems to be working on phone

Same results with autopatcher 2.2.1 and ./auto_patcher cm-10-20121026-NIGHTLY-i9100.zip pd2.0

thanks for all
[Android Software/Hacking General [Developers Only]] jelle2503:
what is this rumor i heard about AP going to be native app for android?
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
not a rumor, the team is working on it being a botbrew app/script
[Android Software/Hacking General [Developers Only]] alen1901:
Will there be auto-patcher mods like evilisto mods(sense4 recent apps, windows phone 7 recent apps, lockscreen mods etc)?

Sent from SpeedMachine i9023
[Android Software/Hacking General [Developers Only]] TheDrake:
I'm testing it now and it's working only with the app. No need to patch rom.

Thanks.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
unsure, as I am not on the team though I might be an alpha tester, however I can guess that they will be focusing on getting auto_patcher as it is now ported to botbrew before looking at adding anything else.
[Android Software/Hacking General [Developers Only]] mateorod:
Thanks guys. This is a smali binary problem, and one I haven't looked into. JesusFreke (the designer) still puts out updates to these, so hopefully it will go away.

I will add it to the upcoming (mythical?) FAQ. someday.

Actually, this is not exactly an error. For some of the more complicated patches, we have what we call 'provisional' files, which are prepatched files that we can copy into your framework should the patch fail. Not every file can be used this way, but some can and we use it to bridge trouble spots.

The GSMServiceStateTracker is one of those. If you ran the script in a terminal, it would explain this, and ask your consent before continuing. You can see the log line from when that happens in the bolded section above.

The confusion is coming from the fact that kobik77 has configured ApG to answer 'yes' to that question automatically, because he trusts our judgement and it makes running the program as easy as possible. And I can understand that decision, I have considered doing the same and just relaying the information instead of asking consent myself.

Point is, that pd2.0 patching was completely successful, so try the program if you want. See the top of the OP before switching PDroids though, there are some incompatible dbs you must delete. I may add to the pd2.0 updater-script, i haven't decided.

Just so you know, with our new build query, you should be able to patch literally any Jellybean rom and have our patcher determine the correct patches to use automatically.

I don't know anything about those particular mods, but the auto-patcher was written to be as flexible as possible. I think we can pretty much add anything we want at this point. Pick your favorite and provide a link. I will look into it, as long as it fits our criteria [not available in another universal format (i.e. some format that works on every rom/device), not comprised of a developers proprietary work]

Now that the 2.3.0 stable is out, I am going to slowly start work on migrating our code to a point where we can go native. We are some months away, though. But that is the goal...
[Android Software/Hacking General [Developers Only]] TheRecRuiT89:
I really would like to see that pdroid would support TW based roms, too. Especially after the leaked JB stock rom, I have really started to think that TW roms will be far far better then CM based roms. so it would be nice to see pdroid with TW-JB based roms. But in the near future it seems not possible i guess :(
[Android Software/Hacking General [Developers Only]] TheMatrix2000:
Works

Just an Info.

Autopatcher 2.3.0 works on OS X with the latest ParanoidAndroid 2.5.2 for my SGSII. Awesome. Big big thanks. :good::good:
[Android Software/Hacking General [Developers Only]] alen1901:
There are .diff patches which needs to be applied with sources. But applying can be done manualy too, decompile change, compile. So i think its possible to implement. Here are some mods so you can se which ones could be included in program, if any.

http://xdaforums.com/showthread.php?t=1920612

http://xdaforums.com/showthread.php?t=1597928

http://xdaforums.com/showthread.php?t=1589963

http://xdaforums.com/showthread.php?t=1539335

http://xdaforums.com/showthread.php?t=1552323

Sent from SpeedMachine i9023
[Android Software/Hacking General [Developers Only]] alharaka:
Anything you guys tell me to, I will seriously consider, because what you give to me and others I need to try and match somehow, yeah? :)

Jokes aside, I have some so-so Linux/sysadmin experience, so I have glanced over build tutorials for Android. I am taking some courses on EdX now, but I will try and make time to learn how to build PA from source, which now sounds very possible according to the 411 from you re the ParaPrefs. :) Woot!

So, I guess it will be time to meet you all in that porting thread and set up a lxc on my Linux server and come learn. :)

And by the way, imilkia had asked for feature requests in PA and I actually suggest integrating this in a PM, just never got a response. I guess it is "pick myself up by the bootstraps" time.
[Android Software/Hacking General [Developers Only]] Landvogt:
Hello!

Thanks for the work you all have done so far!

I've tried to patch pd2.0 support for CM10 Android 4.1.1 for the Defy but failed. The logfile is here.

I am using a Motorola Defy MB525 with green lens (SoC camera) with the CM10-20120924-NIGHTLY-mb525.zip provided by Quarx.

If i got the error message right then the CM10 file that i am using is different from the "standard" CM10 and the patches can not be applied to this. Is this correct? What can i do to get pd2.0 running?

Many thanks in advance!
[Android Software/Hacking General [Developers Only]] mixtapes08:
+1 to this evilisto's mods are so awesome...
[Android Software/Hacking General [Developers Only]] Articudos:
+1, but that layout values are optimized for GNex(dunno about other Xhdpi devices)

Sent from my Marmite flavoured rasbean crespo