yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcherv2.3.5 has been uploaded to the download page.

If the Auto-Patcher is already doing everything you want it to, then there is no reason to rush for the update. But there are some of you that will benefit.

Improvements include:

Evervolv (aosp) support for ALL mods- Thanks to new Evervolv maintainer poncik

Fix for method cap issue with new AOKP for pdroid and pd2.0

Improved build.prop probing for romtypes

I want to say that poncik just decided that he wanted to see Evervolv supported and went out and made it happen. We welcome ALL community involvement, and it is not as hard as you may think it is. Thanks to poncik for taking the initiative and providing these patches for Evervolv users. In my limited testing of the patches, I had to copy over ContentResolver, which I expect will happen with all Evervolv roms. So let us know how the programs run, okay?

As you can see above, Evervolv is not it's own romtype, you can just enter aosp and it should be able to determine if you need the Evervolv patches from there. If you think that your rom-probe is inaccurate and you want to select the Evervolv patches manually, you can do so by using the aosp-ever romtype, but that is not an official romtype, as we are trying to keep this as uncluttered as possible.

The build.prop probing should be a little more accurate in general. There should be a great deal more accuracy determining between CM and PA. The AOSP vetting now includes the Evervolv support written about above.

I am very happy with the build date probing, so now I am going to turn my attention onto whatever I have to do to finish simplfying the romtype stuff. We are almost there, and thanks for all your testing.
[Android Software/Hacking General [Developers Only]] karamelos:
Hi pd2.0 & auto_patcher work fine on

Edit

& on the last cm10 20121103
[Android Software/Hacking General [Developers Only]] karamelos:
add cm after your command

example:

./auto_patcher your_rom.zip pd2.0 cm

or for info

./auto_patcher your_rom.zip -h
[Android Software/Hacking General [Developers Only]] Teemoo:
I did add cm, even tried with aosp :) , no luck.

edit: the log is from my second try w/o cm command, but it recognized as cm anyway.
[Android Software/Hacking General [Developers Only]] mateorod:
Actually karamelos, the patcher saw that it was a cm rom, so that isn't the issue.

I would say the best thing to do is to supply a logcat, and post it in the Pdroid2.0 thread.

There have been reports of phone malfunctioning with pd2.0, and CollegeDev has seen that it is related to a bug in his build patches. I think he has just released new ones, although we haven't upgraded our patches here at the Auto-Patcher yet.

But as far as we can tell, copying the GSMServiceStateTracker has not caused any issues. But the best way to be sure is to submit a logcat in the PDroid2.0 thread where both CollegeDev and I can look at it.

If you are unfamiliar with how to get a logcat, there are plenty of free apps in Google Play.
[Android Software/Hacking General [Developers Only]] karamelos:
delete
[Android Software/Hacking General [Developers Only]] scutworker:
First a big thanks to poncik for sorting out the Evervolv roms. I've been waiting for this a long time. Thanks to mateorod too for all his work on this.

I've using this ROM:

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

It's an Evervolv based Jellybean rom for the HTC Desire.

The patch compiles just fine and I am able to open the Pdroid2.0 app, but that's as far as I can go.

The apps all shows OK, but when I change any of the permissions they are not saved. On the main screen the profile changes from 'real' to 'custom' but the individual settings are not preserved in the actual permissions list for that app. And the app still has access to the permission even though I have blocked it.

The logcat is attached. In this I open up pdroid 2.0 app and try to save the permissions for Google maps as blocked. I then open the Google maps app.

I hope it helps and thanks again for your work.

Cheers.
[Android Software/Hacking General [Developers Only]] CollegeDev:
I can't understand why people do not read FAQ or the first page of this thread. Here is the solution:

In the next patch I will fix it that there will be no more problems to switching to pd2.0
[Android Software/Hacking General [Developers Only]] poncik:
you have to delete pdroid data files before start using pd2, go to /data/system/ and delete this folder and files

privacy folder

privacy.db

privacy.db-journal
[Android Software/Hacking General [Developers Only]] Teemoo:
thanks,

deleted those, scream of logcat stopped but still no signal, now I see this at logcat while changing airplane mode.

11-04 00:10:14.647: E/PrivacySettingsManager(261): getSettings - PrivacySettingsManagerService is null

edit: but pdroid 2 works fine :) ,tested with network info II

edit2: as you can see at screenshot :)
[Android Software/Hacking General [Developers Only]] scutworker:
Yep, that did the trick. Sorry for not realising it but it was so long ago that I tried pdroid (which didn't work) I forgot those files were there.
[Android Software/Hacking General [Developers Only]] echoedge:
It seems to be working with the new 2.3.5 update! :laugh:

Thanks materod :cowboy:
[Android Software/Hacking General [Developers Only]] Arthur_Dent0815:
Start on boot

Hello,

I patched pdroid2.0 patch on Utackas PA-Rom for galaxy note.

I've got an app called system monitor installed. Without the patch it starts at boot time for monitoring system activity.

With the patch applied it doesn't start at boot. According to catlog it seems that the activity manager doesn't start the process at boot time.

In the pdroid2.0 app I granted the rights for system monitor to start at boot.

Any ideas?

Thx
[Android Software/Hacking General [Developers Only]] curl66:
thanks for this great project

OK. i am stupid...didnt find anything with the search.

Is there a plan to integration Pdorid into CM direktly?

i mean..this is should be a core feature of the OS...

and will be easier to maintain instead of patching all roms..

or can the autopatcher skript run on android itself so it can patch a downloaded CM with the OTA feature of CM?

May be the guys of CM can include this as an option into the downloader. that will be a great feature to add Pdroid before flashing. i see that you need the Java JDK for this. so this would not be working on the phone...

thanks!
[Android Software/Hacking General [Developers Only]] mateorod:
You're going to have to take this to Pdroid2.0 thread, I don't have anything to do with how that program operates. Still bugs being worked out, as it is still a pretty new program.

CM will NEVER integrate this into their framework. That much I promise you.

As far as making getting the framework somewhat easier, I hope to have the process 'on-device' sometime into the new year. But we have always to go between then and now. As of right now, this is the only way. It really isn't that hard, I don't think.

Pdroid 2.0

CollegeDev updated his build patches. I found out they were released when you guys did. The process of updating the patches takes a coordinated effort of several people making multiple builds. That process has not finished yet, and likely won't be for several days.

I am letting those patches get some user testing before rallying my maintainers, I see CollegeDev is considering/perhaps has integrated a change already.

We will roll out an Auto-Patcher update to the new build patches in some manner that makes sense and will let you guys know.
[Android Software/Hacking General [Developers Only]] WJThomas:
I'm having some difficulty with the external_internal option. I have tried patching the encore CM10 alpha, both betas, my own build of CM10 and PA2.52. In all cases when I apply the patch I am getting a boot loop. it also appears that the restore.zip does not contain the files to undo the changes made by update.zip.

In looking at the files installed by update.zip, system/build.prop is identical to the one in the original ROM; and I do not understand what the system/etc/vold.fstab is attempting.

Previously I had implemented a change to vold.fstab (discovered through trial and error) that appears to work, but now I am curious as to what the change really should be.

I have seen and experienced your kindness and compassion in explaining things to people. Could you please explain what the external_internal is trying to do, and how it differs from what I have done? To assist you, I have attached the auto-patcher log, the update.zip, the restore.zip, and my version of vold.fstab.

Thanks in advance.
[Android Software/Hacking General [Developers Only]] scutworker:
One thing I did want to ask is about updating.

When a new patch comes out and I use the autopatcher to create a new update.zip file, can I just flash this over my existing Pdroid 2.0 installation, or do I need to reinstall the rom again into the system partition then flash the update.zip?

Cheers.
[Android Software/Hacking General [Developers Only]] mateorod:
Jeez, I missed this somehow.

I gotta be honest, I didn't write this one. Pastime put it in, but when pastime says something works, it works.

As to why it isn't working specifically for you...I will look into that. I will say that the Nook (don't think I don't recognize THAT rom) has a decidedly different rom set-up then has become standard.

But you're gonna have to give me a minute to look into that some more for you.

Are asking about when we release new patches based on CollegeDev's recent release? That will come out in the next couple days, since the maintainers came together and have started to make that happen.

But you can flash an update.zip right over that same rom, yeah, no problem.

Edit: Wbedard puts it beautifully next post.

Also: I have submitted a patch upstream to aokp that gives us some needed space in the method cap. This exact commit was merged by CM a couple of weeks ago.

If anyone reviews for AOKP, give it a look.
[Android Software/Hacking General [Developers Only]] wbedard:
As long as your update.zip was created from your current ROM (same release/version), you can just flash the update.zip.

You only need to re-flash your ROM if you're switching ROMs or upgrading to a new version/release of your current ROM. In the later case, if they offer a smaller "delta update", then you may be able to "dirty flash" the ROM update followed by the autopatcher update and be up and running after a reboot. You should really take the time to understand what you're doing if you try shortcuts like I describe, though. If you're not sure, be safe and just factory reset, flash your new ROM, flash the autopatcher update, wipe cache and reboot.
[Android Software/Hacking General [Developers Only]] m0d:
[Fixed ] ApG does not work under Desktop folder(s)

ApG sync to Github will not work if the file is saved in Desktop or a folder in desktop

Moved it to c:\ApG

And, all is working as expected
[Android Software/Hacking General [Developers Only]] mateorod:
I don't know what is going on with ApG for you. I am not privy to its operation. But I am pretty sure someone would have told me if you had to jump through all those hoops.

But if it isn't working for you, why not just use the script? You have all the dependencies installed.

My guess is that you haven't synced with github and therefore haven't downloaded the program yet, only installed the dependencies. But if anyone uses ApG and can help this person out...
[Android Software/Hacking General [Developers Only]] m0d:
You were right after all, it was not syncing to github,

ApG sync to Github will not work if the file is saved in Desktop or a folder in desktop

Moved it to c:\ApG

And, all is working as expected
[Android Software/Hacking General [Developers Only]] karamelos:
@mOd

Give a link (direct) I trying later
[Android Software/Hacking General [Developers Only]] m0d:
ApG sync to Github will not work if the file is saved in Desktop or a folder in desktop

Moved it to c:\ApG

And, all is working as expected
[Android Software/Hacking General [Developers Only]] htrakr:
Just checked. ApG works fine.

Do you have like firewall or anti virus blocking ApG
[Android Software/Hacking General [Developers Only]] coolnameless:
help

i have an ly-f1 (turbotab c8), running cm9. have attempted every way I've seen to get this patched (even tried variations of said methods), would be cool to patch my current rom. have also tried every other(supported) rom available for this tab. don't know much about debugging but most of the errors point to preexisting patching or other smalis(wifi,config,etc). any help would be greatly appreciated
[Android Software/Hacking General [Developers Only]] winnici:
m0d I have the same thing happening on multiple comps - pmed apg dev who is working on fix
[Android Software/Hacking General [Developers Only]] mateorod:
Post the log file generated by running your rom through the autopatcher. Directions on OP.

Hmm. Well, I haven't personally heard anything about a bug in ApG, but it is always possible. The GUI negotiates the download through github itself, so there are other factors than just our script at play here.

Sounds like kobik is aware of the problem, I guess.

Having said that...you don't HAVE to use ApG. ApG is great, it has brought a bunch of people the confidence to try the program. But the program works all by itself.

If you have already run ApG, then the dependencies we need should be there. But you can rerun the cygwin.exe, and install Java, cpio, and patch. There is a search bar, just enter those programs in.

Download the Auto-Patcher and place your rom in the unzipped download.

Open up cygwin and navigate to the proper directory. If you just put the unzipped Auto-Patcher folder directly in your cygwin home folder, it is easy.

cd auto-patcherv2.3.5
./auto_patcher YOURROMSNAME.zip pdroid

That's it.

There is conceivably some fine tuning, but probably not. If you want to give it the best chance, add your romtype {cm, or aokp or aosp or pa} to the end of the auto_patcher command.

If you have any trouble, attach the log file generated by running the program. It is in the same folder as the rest of the program stuff.

Try it. The program isn't broken, only possibly a GUI. Anything we can do with the auto-patcher is just as possible for you as it is for anyone else.
[Android Software/Hacking General [Developers Only]] winnici:
I've also run autopatcher on osx and Linux which of course works except pdroid2 fails for my toroplus pa rom. Well not exactly fails but encounters problem patching gsm telephony file as others have reported. I allow substitution with generic and then flash resultant update.zip but get the phone process constantly crashing behavior others describe. Didn't report bc college said to be working on updated patch so just patiently waiting.
[Android Software/Hacking General [Developers Only]] winnici:
dude, chill and reread exactly what I wrote / you just quoted - I DID read the messages and that's why I DID NOT call them errors - everything I wrote 100% accurately describes what I did and what happened with the latest version of auto-patcher - thanks for your work and this project - if I have time tomorrow, I'll try to grab the updated patches and see if they fix the NOT ERROR issue
[Android Software/Hacking General [Developers Only]] m0d:
No firewall blocking, no antivirus blocking

ApG sync to Github will not work if the file is saved in Desktop or a folder in desktop

Moved it to c:\ApG

And, all is working as expected

Also,

If ApG.ini file gets corrupted or deleted, it redownloads Java and Cygwin

It should check for the files themselves, and not depend only on .INI file to check if they are there.
[Android Software/Hacking General [Developers Only]] coolnameless:
torbotab c8(ly-f1)
[Android Software/Hacking General [Developers Only]] htrakr:
Yes just ran ApG. Maybe you had a error in download. Try downloading again maybe.

But some of the mods that were there before are missing. I only see 3gdongle, insecure and pd2.0 now. (Maybe something is off but I only use pd2.0 so can't comment on the other mods. Just to clarify they are still there but just don't show on ApG.)
[Android Software/Hacking General [Developers Only]] mateorod:
From your original post:

My point remains. It does not fail. There is

no

problem patching. That problem is a bug in pd2.0, that has happened for the few. Fixes are in route, but I believe it remains my right to stand up and say my personal work is performing as expected. The auto-patcher team has undertaken to port this software and have been successful.

Perhaps you did understand those messages but some how many others have not. Later in my post I bold a portion where I stress that your post was merely an opportunity to express where we were.

Moving forward...

Okay, we this is an opportunity for the Auto-Patcher to flex some muscles it doesn't have to use very often. It may not work, but it is worth a shot.

Obviously, this is an amazingly old rom. Do you see the excerpt of the log I bolded above? This is a portion that people always leave out when they simply quote the logfile, but is packed with info.

The BDID is the actual build date of your rom. The BID is the patch set the Auto-Patcher determined was the best match for your rom, the closest before your build date. Yes, it was hard to make the auto-patcher do all this, thanks for wondering, lol.

That patch set failed for you, but you can manually try and set a different patch date. Your rom was made during the VERY early days of the patcher and we weren't as organized as we have become. Like I say, this may not work, but it is worth trying since you have already loaded the rom and ran the program.

Simply append a date on the end of the same command you ran. Some available dates to try might be 20120615 or 20120506. You can use the ./auto_patcher ROM.zip -h to see what patches are available.

Generally speaking, people that come to us with OLD old roms like yours, there is a reason that there isn't later software being used, and that means hardware distinctions or limitations. So who knows what kind of non-standard stuff is happening in that rom. But it is worth a try.

I don't have any idea what that means. What is a compatibility zip? Do you have any specific reason that you think that would break the autopatcher, have you tried it yet?

Well, I think we can see that there is some sort of problem here. I don't have the equipment to check it myself. It sounds like the problem is with the sync to github. I know the original reporter tried to physically place the files inside the proper directories, but probably ApG failed when it tried to compress our already distributed tarballs.

The ApG users may have to use the script itself until Kobik77 gets some time. We can help you get through it if you have questions.
[Android Software/Hacking General [Developers Only]] winnici:
jesus, do you want me to underline from the same exact thing you quoted that it does not actually fail or challenge you to explain from what possible tortured logic follows the idea that a core process on patched phone constantly fcing is not a problem? It's OK to admit you were wrong for jumping all over someone for something they didn't say, no one will laugh at you, just like no one was insulting your precious code or even insinuating it - and not a particular 3rd party patch - was responsible. Thank you for continuing to develop this wonderful program we all love and do our best to support by providing feedback from testing - now please grow up
[Android Software/Hacking General [Developers Only]] mateorod:
Laugh at me?

I suspect they might. I have, after all, spent 20+ hours out of the last 48 working on an update. And yet you think that my work entitles you to speak to me any way you please.

You can take that kind of "support" elsewhere, my friend.

If you wonder why I think that someone citing that specific issue with the words fail and 'problems patching', may not understand then read this. or this. or this. or this. or this. or this. or this. or this. or this. or this. or this. or this. or this.

If you understood everything, then substance of your post is to stress that you are 'patiently' waiting for an update to fix problems I don't have any control over.

You are error reporting in the wrong place, take it to CollegeDev.

I made the effort to stress that my post was aimed at no one, that I wanted to take the opportunity to repeat the information.

Stop trolling me and this thread. Stop it.

You do not know me and your personal assumptions are unwanted.

Any one is more than welcome to come to this thread and get any help they need. But do it with, if not gratitude, then courtesy.

This is the last word on this subject. Further OT bs of this nature is going straight to the moderators/dev/null.
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
But trolling is the best :D

jk dude just messin' with you, on an android related note, the CM10 Beta 3 was just dropped for the nook color. So Eyeballer and Krylon strike again.
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcherv2.4.0 is out.

If ApG is working, you can sync it right now. It has also been uploaded to our download page, although it may not be available for 15 mins or so.

Features include

Updated pd2.0 patches to 1.5.1 for pa, cm, aokp and aosp. Evervolv is not updated yet, sorry.

The PDroid2.0 update has

Fixed FC of phone.apk for LTE-CDMA phones

Fixed intent boot complete setting (e.g. sometimes apps doesn't start on boot)

Minor bugfixes

Fix potential leak by preloading classes

Return to Chainfire's (f)aapt

Improved rom probing (especially for cm and pa...we are working towards making RomTypes a thing of the past...let us know)

Gsm files now copied in background- our data shows that this is not a problem

Get it while it is hot, I have the sinking feeling I am going to have to do this all over again in the next week or so when 4.2 comes out.

Thanks to our maintainers, wbedard, poncik, and FFU5y.

Any comments on how PDroid2.0 works for you is most useful in CollegeDev's PDroid 2.0 thread. Any problems making a patch is best handled here. It can be confusing and for the most part he and I both see what happens in either thread, but better to be safe than sorry.

ApG Users

If ApG isn't working for some reason after you install it, you can go ahead and use the script in the cygwin terminal. You can download the Auto-Patcher from our download page or you can download a signed zip here.

If you download the tagged release, you need to prep the program first:

./batch.sh
./auto_patcher ROMNAME.zip MOD

That's it. You can append a ROMTYPE {cm, pa, aokp or aosp} to the end of the auto_patcher command if you see it using incorrect patches, but the romprobing has gotten pretty solid.

Pdroid 2.0

There is one other thing to be aware of as we all begin to test CollegeDev's/Auto-Patcher's new patches for the first time. Because this was an update from upstream (i.e. a bugfix from CollegeDev) and not because the patches broke, people using an older rom CAN use the new patches. So I have made it that all 4.1.2 builds

except for those for 2012/10/16

will automatically use the new 1.5.1 Pdroid2.0 patches.

If you find these patches don't work for you, and you want to use the older patches until a fix is put together, then you will need to explicitly tell the auto-patcher that you want the patches from 10/16.

./auto_patcher ROMNAME.zip pd2.0 ROMTYPE 20121016

Hopefully the new patches work like a charm and no one ever has to worry about this. But now you know...

* If, by some quirk of fate, your rom hasn't been updated since 10/16 exactly, you can get the newest patches with the same command, but changing the 6 into a 7. Done.
[Android Software/Hacking General [Developers Only]] htrakr:
ApG is working. Just patched latest CM nightly with 2.4.0.

:thumbup:
[Android Software/Hacking General [Developers Only]] Gargantuantua:
Just tried with APG but it still says the installed patch is 1.4.8. Thought apg was updated to 1.5.1 patch but I guess I read wrong?