yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mateorod:
I am downloading it to have a look. I will say that 4.1.x, for whatever reason, was really stable. The patches worked for bunches of roms and never broke. That was not our experience with ICS, where we never got SlimRom sorted. I have gotten a lot better at this, though so let's see what I can do.

Well, it looks more like what is happening is that is is not able to create some sort of temporary directory where it makes backups for some intermediate step. I scan the actual patching log for any failures, that is coming up clean. And obviously people are able to run Pdroid Manager so the patching process is working. We actually never reinsert those files into a device. We either recompile them or in case of failure, discard them. So it doesn't appear to be a fatal error at this point. I will redirect standard error to the log for awhile, and add the verbose flag. We stopped taking the error messages from the patch utility because we track down its errors in a non-reported log and adding patch's output swells the log by several hundred lines. But we can do that while we track down what's going on.

As far as your edit is concerned...if what I think is happening is correct, we aren't ordering this file creation it is happening with the utility. I will just have to see more, but as far as what I explicitly order? Just to patch in place, nothing more.

I think I answered this above. We already log actual errors applying the patch, this error is some ancillary process of the patch utility. But I can order a verbose run and log stderr.

Fair enough. I can use the reports from the other folk. For those of you reading, if you are having an issue where PDroid Manager isn't working, even though you applied the update.zip, please let us know.

Provisional Evervolv support was added last night. Those of you who are using ApG can get it already. I have the patches as an adjunct to aosp.
[Android Software/Hacking General [Developers Only]] vitocor:
Didgesteve wrote:

I have had excellent results with autopatcher in the past, but my latest 4.2 build is refusing to play.

I have been a big fan of Pdroid since it came out, but understand that it needs modifying to be kept up to date.

I would like to try Opendroid, it looks great, but I'm failing to build a patch.

Tried patching with all the different rom types, but get the same error.

I am using Slim 4.2 available here

grayfoxmg1 mentioned having trouble with Slim builds in the past, but have successfully built patches for versions 2.9, 3 & 3.1, it's just this one that is giving problems.

Attached is the error, the same for whichever rom type I choose.

What can I do to fix it?

Mateorod wrote:

I am downloading it to have a look. I will say that 4.1.x, for whatever reason, was really stable. The patches worked for bunches of roms and never broke. That was not our experience with ICS, where we never got SlimRom sorted. I have gotten a lot better at this, though so let's see what I can do.

Me Write:

I am in the same situation like Didgesteve for my N7000.

Can`t create a Patch for Slim Rom 4.2.1 Beta 2 Link: (no link...not yet... don`t have 10 posts :(

It would be awesome to bring this to work...:fingers-crossed:

Vito
[Android Software/Hacking General [Developers Only]] scutworker:
And it works! I just tried it and it all seems to be working OK. Thanks very much for the update. I'll report back here if any thing causes problems.
[Android Software/Hacking General [Developers Only]] mateorod:
Scutworker or anyone who has patched either a PA or Evervolv rom...do you still have the Mms.apk functional and available?
[Android Software/Hacking General [Developers Only]] scutworker:
The apk is still there, but it doesn't seem to send a picture message. It just sits there with the messaging "sending". I never send mms messages, so didn't even think of testing it.

Here's two logcats; the first openmms.txt is when I open the messaging app, the second sendingmms.txt is when I press send.

Good luck with them.
[Android Software/Hacking General [Developers Only]] mateorod:
Ok, thanks. I am going to have to dig into the Mms patch. I have pushed a hotfix (temporarily going back to how we did it for 4.1.2). Anyone using ApG can go ahead and sync the fix now. To keep track of the bug and fix, I have updated the version to 2.5.1.

Includes: Evervolv and PA support for all 4.2.1 mods (everything but tabletUI and pd2.0)

A hotifx for Mms.apk issues

Anyone with ApG who tries 2.5.1, please report if this fixes (as it should) the issues with Mms. If so, I will wrap it up and post a new download for OSX/Linux users.
[Android Software/Hacking General [Developers Only]] 4ndr0x:
Error when ApG tries to update itself
[Android Software/Hacking General [Developers Only]] grayfoxmg1:
See if any of my tips HERE can help.
[Android Software/Hacking General [Developers Only]] kobik77:
Sorry for this, but another ApG version is up with quite few more fixes for bugs I've found.

Mostly its regarding package updating which I don't know how the hell it worked (Now it should also update the GUI properly about its progress)

Some code clean up and some debug messages I forgot to remove.

There is also a cygwin update with a new version and some missing utilities I've added.

I've done this with a pretty bad eye infection so new bugs might have snicked on me :D

mateorod, there is also a pull request I've sent you regarding all the temporary dir issue.
[Android Software/Hacking General [Developers Only]] mateorod:
I am out in the world, but I ssh'd in and ran it a couple times and everything looks good from here. I just merged it, you have always sent it great stuff.

Thanks for the updates, I know the ApG people appreciate it as well.
[Android Software/Hacking General [Developers Only]] :
Works great! The old version didn't download any packages! Good job my friend :good:

Edit:

Any idea why this happens:

ApG work directory is: C:\AP\ApG.exe
[Android Software/Hacking General [Developers Only]] pro.aggro:
When i try to install the new version (2.5.5.0) it fails after downloading cywin.
[Android Software/Hacking General [Developers Only]] :
Exactly the same thing happens to me! :eek:

Edit:

Found a workaround to fix the issue from above!

Follow this steps:

Instead of downloading the latest cygwin from:

http://d-h.st/users/kobik/?fld_id=5247#files

DON'T download the one with the date

:

2013-01-15 17:57:15 <- this is the one that ApG.2.5.5.0.exe downloads AND IT GIVES THE ABOVE ERROR!

download the one on the bottom of the above link:

2012-09-16 20:56:09 <- http://d-h.st/TB1

go to ApGPackages and delete the cygwin.exe from there and it's folder and paste the new one! Extract the new one and run ApG.2.5.5.0.exe

And the error is fixed! :D

Have fun!
[Android Software/Hacking General [Developers Only]] azrash:
Hi guys I am getting this error while patching codefirex AOSP ROM with openpdroid

i used AOSP-mod option since it is not fully AOSP

ROM link here [ROM][AOSP-4.2.1][LINARO][4.7.3-Toolchain] [SR3]

!!! PATCHING FAILED FOR android/hardware/Camera$EventHandler.smali' android/hardware/Camera.smali android/os/SystemProperties.smali !!!
!!! patch error for android/hardware/Camera$EventHandler.smali' !!!

full log available here http://codepad.org/LHLGMQJi

would appreciate any help or pointers. thanks!

edit tested again with version 2.5.2 and the same problem persist.

full log here http://codepad.org/ssthDOCB
[Android Software/Hacking General [Developers Only]] mateorod:
We're having problems with the Galaxy Nexus. I do not know why, it was no problem with 4.1.2. But for some reason, most of the device-specific errors are coming from that device.

I just pushed a fix that works for your rom. It is included in the below release and already available for ApG. That is a lot of files to replace, so report back with how that works for you. It should work, let us know.

Auto-Patcher 2.5.2

(available through ApG and download at techerrata)

Improvements include:

Support for ParanoidAndroid and Evervolv for all 4.2.1-capable mods (openpdroid included)

Fixes related to cygwin and ApG users (Thank kobik77 here.)

Hotfix for Mms.apk problems, should now be available

Available mods now show all the available mods and proper romtypes.

bugfixes.

It is recommended you update.

Also, since this was the first wide release of the OpenPDroid fork, I want to say we appreciate all the feedback that has come to the OpenPdroid thread. Thanks to your feedback, there are some improvements and bugfixes being worked on. Please keep the feedback and the logs coming, it makes the program better!

Just saw this and checked it out. Looking at their source, this is a hodge-podge of cherry-picks from all over. I gave it some runs, but it looks like it is unsupported, sorry. I know we support several roms for mako like CM10 and PA and others, though.
[Android Software/Hacking General [Developers Only]] wkwkwk:
Thanks, it sort of worked:

### jar patch openpdroid/4.2/aosp/20130109 ###
... apply framework.patch ...
... apply preloaded.patch ...
... apply core.patch ...
... apply services.patch ...
... apply telephony-common.patch ...
17 out of 78 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali.rej
2 out of 13 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/cdma/RuimSmsInterfaceManager.smali.rej
1 out of 4 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/gsm/GsmServiceStateTracker.smali.rej
2 out of 13 hunks FAILED -- saving rejects to file smali/com/android/internal/telephony/gsm/SimSmsInterfaceManager.smali.rej
!!! PATCHING FAILED FOR com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali com/android/internal/telephony/cdma/RuimSmsInterfaceManager.smali com/android/internal/telephony/gsm/GsmServiceStateTracker.smali com/android/internal/telephony/gsm/SimSmsInterfaceManager.smali !!!

File for which patching failed:
---------------------------------------------

CdmaServiceStateTracker.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

But IT MAY NOT WORK!!!

Do you want to proceed ? (YES/no)
... replace com/android/internal/telephony/cdma/CdmaServiceStateTracker.smali ...

File for which patching failed:
---------------------------------------------

RuimSmsInterfaceManager.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

But IT MAY NOT WORK!!!

Do you want to proceed ? (YES/no)
... replace com/android/internal/telephony/cdma/RuimSmsInterfaceManager.smali ...

File for which patching failed:
---------------------------------------------

GsmServiceStateTracker.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

But IT MAY NOT WORK!!!

Do you want to proceed ? (YES/no)
... replace com/android/internal/telephony/gsm/GsmServiceStateTracker.smali ...

File for which patching failed:
---------------------------------------------

SimSmsInterfaceManager.smali

---------------------------------------------

We can try to add a premade copy of those files.
This sometimes works.

But IT MAY NOT WORK!!!

Do you want to proceed ? (YES/no)
... replace com/android/internal/telephony/gsm/SimSmsInterfaceManager.smali ...
### rebuild jar ###
... rebuild framework.jar ...
... rebuild core.jar ...
... rebuild services.jar ...
... rebuild telephony-common.jar ...
### create update-aosp-maguro-20121120-openpdroid.zip ###
### finished ###
flash update-aosp-maguro-20121120-openpdroid.zip to install the patched files
flash restore-aosp-maguro-20121120.zip to restore the original system

I'll flash it tomorrow and report back. Thank you.
[Android Software/Hacking General [Developers Only]] zwolf4444:
Unfortunately, your trick doesn't seem to work for me. Every time I replace cygwin, ApG just downloads it again and replace it with the other one.

EDIT: I figured it out. Just changed the URL it tries to update from, redirected it to nowhere. The only problem now is that TabletUI mode apparently doesnt work yet with 4.2?
[Android Software/Hacking General [Developers Only]] kobik77:
As I am currently not 100% well, let us say that the following couple of versions would likely have some more bugs to iron, so please inform any problem you would find and add ApG.log to that.

Thanks
[Android Software/Hacking General [Developers Only]] Didgesteve:
Rest up, and if you have an eye infection, stop looking at the screen.

Hope you feel better soon.
[Android Software/Hacking General [Developers Only]] Febby:
Woot.. Finally got the new APG set up. Trying out Toroplus galaxy nexus stock 4.2.1 ROM but gave me this error under the opendroid - AOSP selections. Not complaining but hopefully logs can eventually help fix this since you guys are aware of the Gnex issues. :)

openPdroid - AOSP log = http://codepad.org/ZabTqpBu

openPdroid - AOSP JB = http://codepad.org/zI0LXl97
[Android Software/Hacking General [Developers Only]] nsmart:
I tried to patch newest cm9-nightly-galaxys2 build from 20120708 with auto_patcher version 2012.07.06. (v0.7.1).

I get the following error:

### apply services.patch ###

114 out of 115 hunks FAILED -- saving rejects to file smali/com/android/server/ServerThread.smali.rej

As I can successfully patch the cm9-20120704-nightly build, it seems that I have to wait for a newer version of auto_patcher, which includes more recent cm9-patches. Or is there an 'easy' way to fix this myself ?
[Android Software/Hacking General [Developers Only]] pastime1971:
damn...

i confirm the above, even with today's updated patch, i still get the same error for galaxys2.

edit: i spoke too soon. i'm getting a bunch of new commits upon "repo sync". maybe it needs just another nightly of our patches.
[Android Software/Hacking General [Developers Only]] mateorod:
Well, give it a day or two before we draw too many conclusions from it. I had a patch break for encore do to an overlay error a month or two ago. It failed for two nightlies and then broke.

I'll start a 7/08 build and see about the patch as well.

Edit: Did you see the defy is having a problem with the same hunks? I'll run out a manual and check those two devices with it.
[Android Software/Hacking General [Developers Only]] mateorod:
pastime1971 made some new patches that should resolve any problems patching roms from last night (0708).

pastime tested it on the galaxy successfully, and I would be suprised if the issues with defy weren't addressed as well.

The newest version (20120708v072) is attached to the OP.
[Android Software/Hacking General [Developers Only]] galom:
I tried the latest autopatcher (0708) with latest nightly for desire (0708) I still get errors. Is the issued reported last week still a problem. I noticed there were full ROMs posted last week.

Thank you.
[Android Software/Hacking General [Developers Only]] nsmart:
I still get an error with version 20120708v072: "failed compiling framework.jar".

The rom I tried to patch is: cm-9-20120708-NIGHTLY-galaxys2.zip.

With auto_patcher version (20120706v071) I was able to patch an older build "cm-9-20120704-NIGHTLY-galaxys2.zip". The newest version (20120708v072) also fails to patch this older cm9-build.

Attached are two log files with auto_patcher version (20120708v072). One log file when trying to patch cm9-build 20120704, the other log file when trying to patch cm9-build 20120708.
[Android Software/Hacking General [Developers Only]] mateorod:
pastime1971 just repo synced and built the rom to make the 0708 patches. So it is concievable that his patches included commits that aren't in your nightlies from last night. When a ROM is in a high state of flux like CM9 appears to be, this is sometimes an issue; when you run the repo sync can matter very much when the patches are going out of date every other day.

But you should be able to find a rom that is patchable from the last week or so without too much trouble.

I would recommend trying the 0707 maybe, using the 20120706 patch set. The problem you are having with the 0704 rom is that you are using the latest patches. try using a patch date. For the 0704 rom, the command would look something like this...

./auto_patcher <ROM.zip> pdroid cm9 20120626

you can try

./auto_patcher <ROM.zip> -h

to see the patch sets

@galom I don't know whaqt problem from last week you are asking about. The only real problem left unsolved is the CM7.2 Final iteration. We can patch CM7 nightlies, just not the Final snapshot.

Every so often, there will be some nightlies we can't patch just due to the timing of individual builds repo sync. But that isn't too often, just when (as is happening in CM9 right now) the repo is changing over a bunch.
[Android Software/Hacking General [Developers Only]] pastime1971:
that is weird.

your log file shows it failed

...
### rebuild framework.jar ###
tmp\system\framework\framework.jar.out\smali\android\net\DhcpInfoInternal.smali[0,0] null^M

although it looks like the log file was terminated.

i just downloaded auto patcher 20120708 v072, and ran it for cm-9-20120708-NIGHTLY-galaxys2.zip, http://get.cm/get/31v and it creates patched.zip

### rebuild framework.jar ###
adding: classes.dex(in = 8313476) (out= 3419210)(deflated 58%)
adding: preloaded-classes(in = 84498) (out= 14529)(deflated 82%)

### rebuild core.jar ###
adding: classes.dex(in = 2481136) (out= 1043358)(deflated 57%)

### rebuild services.jar ###
adding: classes.dex(in = 1622720) (out= 736644)(deflated 54%)

### create updater.zip ###
added manifest
adding: system/framework/framework.jar(in = 3434324) (out= 3410290)(deflated 0%)
adding: system/framework/core.jar(in = 1047596) (out= 1041833)(deflated 0%)
adding: system/framework/services.jar(in = 737103) (out= 736098)(deflated 0%)
ignoring entry META-INF/
adding: META-INF/com/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/(in = 0) (out= 0)(stored 0%)
adding: META-INF/com/google/android/update-binary(in = 245040) (out= 153879)(deflated 37%)
adding: META-INF/com/google/android/updater-script(in = 120) (out= 85)(deflated 29%)

could you download rom and patcher and try again ?

---------- Post added at 04:54 PM ---------- Previous post was at 04:44 PM ----------

could you post a link to your rom ?
[Android Software/Hacking General [Developers Only]] galom:
http://get.cm/get/30X

Thanks
[Android Software/Hacking General [Developers Only]] pastime1971:
didn't realize it is cm7 bravo.

anyhow, patching seems to ignore only EriManager.smali, but i guess rom bootloops again, right ?

i will upload the pdroid-compiled-kang(nightly).

edit: uploaded at http://www.mediafire.com/?wuhyok3ohl3535r
[Android Software/Hacking General [Developers Only]] galom:
Yes, boot loops. Thanks for the full rom.
[Android Software/Hacking General [Developers Only]] anomalya:
So the chef finally replied and agreed to add support in his next release (ETA indefinite - thanks to JB). When that occurs, I will post it here for greater visibility/support.

Side note: If it's any relevant, the ROM in question comes from an official ICS release from Rogers phone carrier but heavily modified. I would assume since that is the case - the framework/build based on stock (this is where my limited understanding of such things comes to a halt) - it shouldn't be that far out of reach of being patched. It's only too bad, I wasn't able to patch it myself using Cygwin.
[Android Software/Hacking General [Developers Only]] nsmart:
I just tried to redo the patch this morning *WITHOUT* downloading new version of auto_patcher or cm9-build, and now it patched without errors. I am using the cygwin-method. I did not restart my PC. Don't know what went wrong here, but I used exactly the same files as yesterday, I did not even rename a file or a path !?
[Android Software/Hacking General [Developers Only]] pastime1971:
that's good that at least it works now.
[Android Software/Hacking General [Developers Only]] mateorod:
The newest version of the Auto-patcher is up on the OP.

CM9 has been undergoing a bunch of upheaval. The patches we have work, but when the patches are for such a specific amount of time (they seem to change about every other day) it can sometimes be difficult to match with your rom. My guess is that they are working hard at getting it to stable before they move on to Cyanogen 10.

It sounds like they are going to throw their long-term support behind Jelly Bean, leaving ICS as a series of RCs and Stables starting not to soon after the source is released. That will leave CM with long-term support for Gingerbread and Jelly Bean.

Which seems prudent. But may be a bit of a bumpy ride for us here while they get everything tidied up.

If you fail while patching a CM or CM derivative, don't get discouraged. We can and do support all CM roms, it is just a matter of having the patch be made at the same time as major commits. Simply try the patch dates around your build date, up or down one. If that fails, go to a nightly from within a day of the original ROM and try the same patch dates you tried before. I would be very suprised if you can't find a matching patch set somewhere in there.

@pastime- For CM7 bravo ErieManager is a very small file, it is related to the erie.xml you'll find in the app resources. There should be no problem with skipping that patch, so the issue is probably elsewhere
[Android Software/Hacking General [Developers Only]] anomalya:
SKY-ICS ROM for Samsung Galaxy S II (Skyrocket)

I guess I got what I wished for (much) sooner than I expected! The chef has, indeed, released an update that includes a patch for PDroid among other things, though the app itself is unresolved?

And I'm quoting from his changelog:

-added three qualcomm specific tweaks
to allow better caching and status bar handling
hopefully for a smoother overall experience
pre patched services .jar to jave oom groupings on by default
(basically what supercharger does)
and patched it for pdroid(no working with the app but its damn patched
ill post a screeny to prove it if you want to see it)
abd si much more

The link to his update post includes his ROM base files (straight build) and the updates which include the PDroid patches.

Forgive me for being presumptuous, but perhaps it might be worth a second look from you guys. :good:
[Android Software/Hacking General [Developers Only]] mastalee:
i think readlink is very basic on the mac it only supports the -n option

mac:~$ readlink -h
readlink: illegal option -- h
usage: readlink [-n] [file ...]
[Android Software/Hacking General [Developers Only]] kaizokan:
just a small thing, the PDroid link on the first post does not lik to the PDroid page but instead to the main Android Development and Hacking section ;)
[Android Software/Hacking General [Developers Only]] pastime1971:
i see.

would you be willing to test some mac-compatible script later ?

i will try to get auto patcher to probe OS and select functions accordingly.

this will have to support linux, cygwin, macosx.
[Android Software/Hacking General [Developers Only]] beginnerteur:
I'm getting exactly the same error like pro.aggro and the workaroud from zylor doesn't help...:confused:
[Android Software/Hacking General [Developers Only]] HekllSpawn666:
4.2.1 --> TabletUI

Hello, is there a possibility to update the TabletUI patch for the 4.2 branch ?

Thanks in advance
[Android Software/Hacking General [Developers Only]] lolmachine4:
Same error here. Tried both fixed, none worked.
[Android Software/Hacking General [Developers Only]] :
Actually the workaround is mine... Learn to read :)
[Android Software/Hacking General [Developers Only]] beginnerteur:
Ouh....****....sorry!!! I don't know why, I think I posted his name, because I read his post quoting you. Sorry, I editet it ;)
[Android Software/Hacking General [Developers Only]] kobik77:
New ApG version with a new Cygwin package which was the major cause for all this mess.

Hopefully, things would settle down now.

Edit: Hold it.

Now it won't download Java...

Update coming soon.

Edit2: Re-uploaded version 2.5.6.0.

Share your experience.