yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] mj084:
Seems that you have used the attachment from side before...

you need a full package from first site...
[Android Software/Hacking General [Developers Only]] kobik77:
Yeah, no go.

Too many errors.

You've probably missed this part in Cygwin installation
[Android Software/Hacking General [Developers Only]] raimundo amador:
ok, I just downloaded the files again, and it gives me 'error: Missing "jar (JDK)" when executing the cygwin. But I already installed the jdk files from oracle. Any idea?

any help will be very welcome.

Many thanks,

Rai
[Android Software/Hacking General [Developers Only]] l3ullseye:
When I apply this patch, I lose network connection and sometimes it says invalid SIM, I believe it has to do with the files it changes, because it cannot get patched

The log http://codepad.org/QYj8WfLj

The rom http://xdaforums.com/showthread.php?t=2115520 the 20130130 version

Thanks
[Android Software/Hacking General [Developers Only]] Tardigrada:
Milestone2 support

Hey mateorod,

first of all thanks for your hard work on this projekt!!!

Just wanted to say that i'd also love to see pdroid2 working on the milestone2, hope you can fix this issue somehow... :fingers-crossed:

Btw under tezets CM9 with syvats original pdroid patching was successfull.

kind regards,

Alex
[Android Software/Hacking General [Developers Only]] jimbo0815:
i wanted to patch pdroid to the I9300_Omega_v40_XXEMA2.zip or I9100_Omega_v18_XXLSJ.zip

both have "error: system/media/PDroid.jpeg is missing in the patch"

i already read a lot of, pdroid / the AP has a lof of problems with the samung or the s3, with omega and only working with stock roms and blablabla..

so now i wanted to ask what is true and what can i / we do.

i wanted to test pdroid. :|
[Android Software/Hacking General [Developers Only]] karamelos:
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

it's not your setting in openpdroid ? (so restricted)
[Android Software/Hacking General [Developers Only]] steamydump:
Awesome job! I used this a couple of months ago to patch cm10 with pdroid 2.0.

however, i no longer see "pd2.0" as an option in the GUI (latest version ApG v2.5.7)... worked correctly from command line though. did you deliberately remove "pd2.0" as a choice?
[Android Software/Hacking General [Developers Only]] l3ullseye:
@karamelos

I didn't even had it install yet, and also tried to install and configure without any luck

Thanks
[Android Software/Hacking General [Developers Only]] vander13:
Got it working

Now ApG is working finally, just gave up trieing on winxp and switched to a computer with win7 instead.

I tried to modify these roms. It didnt work for Slim CM 10.1 and Slim PAC JB Revision-1 for some reason.

All other roms from that thread was processed successfully, but there was some warning or failed message while it builds the patch. I patched opendroid/pdroid/supercharger, depending on whats available for each rom.

I still havent tried how they work, but I am looking forward to have soon an slim and safe phone, thx a lot for ur good work guys :)
[Android Software/Hacking General [Developers Only]] dadonking:
ParanoidAndroid for Nexus 4 is not that smooth with patch as without patch.

- Setting opens delayed

- Popup of statusbar in tabletUI doesnt run that smoothly

Is that a known problem?

My log -> http://pastebin.com/jG1Z72LW
[Android Software/Hacking General [Developers Only]] kobik77:
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

No, but I know what's the problem is.

I need to fix a regexp to not catch pd2.0.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher v2.6.0 is out.

This is a nearly, although not quite, complete release. I unfortunately have not been able to test things as much as I would like, but with the state of the upstream repos, we needed to get this out to y'all. So let me know, there are a couple of things left to do and check.

This includes the new OpenPDroid patches, v1.0.1. Fixes that are hopefully in order include:

Fix for the SMS problems (I don't have SMS, let me know)

Cache issues

Performance Issues

Much more.

The build patches have been updated in the OpenPDroid repos, for those so inclined.

Among the things we are still aware of yet have not fixed:

The Llama/Cell Tower bug

But the performance and SMS were the big issues, along with the broken AutoPatcher patches, so hopefully this is an improvement. There are patches for CM10, CM10.1, AOKP 4.1.2 and 4.2.1, AOSP 4.1.2 and 4.2.1, Evervolv and SlimRom 4.2.1.

ParanoidAndroid is not yet updated to OpenPDroid 1.0.1!!

! I am building it now, so it should be soon.

I have also rebuilt the Cyanogen10.1 TabletUI. Those of you using that, let me know how it goes. This was a virgin build that works perfectly on my grouper. If you guys are still having trouble, then I will probably just have to let it go. I just don't have the time, this was over 10 hours I didn't have to give. But if it works, then I will update the AOSP and AOKP patches.

AutoPatcher v2.6.0 is available to be synced to ApG and downloaded on Techerrata any second.

From my TODO list:

Mako Cm10.1 is patching fine.

I could not find an official Milestone build, anyone have a link?

TabletUI for Cm10.1 needs users tests.

Anything I am forgetting? It has been a long night already...

I am going to let you guys give it a spin, and then bugfix (if necessary) tomorrow. Then I will update the OP. Already added to the OP:

Karamelos and Grayfoxmg1 were added to the contributor list in recognition of their time they give to the thread. No continued effort is expected or implied by this, but it felt appropriate given the help you two have given.
[Android Software/Hacking General [Developers Only]] :
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

Awesome work mateorod!

Upcoming week: donation!

:highfive: :o
[Android Software/Hacking General [Developers Only]] kobik77:
And there is the fix ApG.2.5.7.8... :good:
[Android Software/Hacking General [Developers Only]] nsmart:
Thank you for the new update of the openpdroid patches.

With newest openpdroid patches (v1.01) on cm-10.1-20130131-NIGHTLY-mako.zip patching was fine without errors. When using GPS Status the compass is still slow and slows down the device when using it. See attached logcat. Camera and SMS seem to work fine. Cell tower location is also working (tested with google maps and osmand).
[Android Software/Hacking General [Developers Only]] scutworker:
I have been using the new patches on an Evervolv rom and sometimes GPS Status is very slow (like before), but other times it is not.

I've attached two logcats, one the full one, the other filtered for errors and warnings. I've opened GPS Status then twiddled the phone around while capturing them.

That said, my phone is a lot faster now when GPS is closed; these updates have certainly improved openpdroid. Not sure about cell towers, I thought that wasn't fixed yet?

Once again, thanks to everybody who develops on this and the Autopatcher.

Cheers.
[Android Software/Hacking General [Developers Only]] brGabriel:
Hey mateorod! Thanks for the latest updates, especially to tabletUI as I know it must be time consuming.

Just reporting that I tried patching a CM10.1 based ROM for manta with tabletUI and, unfortunately, no change in UI. I will play around with it more and test some "pure" CM10.1 ROMs. It may be similar to how tabletUI works on vanilla AOSP but not on modified ROMs. I'll keep you posted. :good:
[Android Software/Hacking General [Developers Only]] xMemphisx:
Attempted build on stock/rooted/deodexed Mako rom again, still having issues with the camera hardware. Here's the log again

./auto_patcher ../mako_4.2.1_Deodexed.zip openpdroid

The Auto-Patcher v2.6.0

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.2.1 rom= aosp ...
... Using results of ROM check ...
... openpdroid patch date has been set to: 20130109 ...
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
inflated: system/framework/telephony-common.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
inflated: system/app/Mms.apk
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
... decompile telephony-common.jar ...
### copy patch openpdroid/4.2/aosp/20130109 ###
... copying system/app/Mms.apk ...
... overwriting system/app/Mms.apk from openpdroid ...
... copying system/media/PDroid.jpeg ...
### jar patch openpdroid/4.2/aosp/20130109 ###
... apply framework.patch ...
2 out of 14 hunks FAILED -- saving rejects to file smali/android/hardware/Camera.smali.rej
1 out of 23 hunks FAILED -- saving rejects to file smali/android/media/MediaRecorder.smali.rej
... apply preloaded.patch ...
!!! PATCHING FAILED FOR android/hardware/Camera.smali android/media/MediaRecorder.smali !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed android/hardware/Camera.smali in framework.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I'm not complaining at all, you had just mentioned that there should be a fix in 2.6.x so I wanted to make sure I hadn't missed something in this process. Keep up the good work, and get some sleep!
[Android Software/Hacking General [Developers Only]] Teemoo:
any news about maguro camera issues ?
[Android Software/Hacking General [Developers Only]] mateorod:
I have put up a new issue related to these reports...thanks for the logcats, that is the way problems get fixed.

Would you link to the post you posted the jars from, the one where someone with Mako followed the edits and handmade a tabletUI? You attactched the jars at one point. What I am thinking is that you just need different hard coded values than the N7 and N4 seem to. I would like to look at that post.

I just tested rebuilt AOSP tabletUI patches, and they are working for my grouper on all tests. I also have confirmation that the patches are working for n4 users, albeit with a status bar issue of some sort. (hopefully fixed with these new patches, time will tell). Also, will you upload your log? There is always the possibility that you are using the older patches...you are flashing something that says "update-cm-20130201-tabletui.zip" or close to it, correct?

Actually, what is happening here is that you are still using the older patches, because your rom is older than the dates I set for the 1.01. patches. You will want either the 20130120 or the 20130201 patches, they are both the same. Usually I would remove the older patches, except that some changes to the upstream repos had the patches go out of date recently. The reason doesn't matter. After these new patches get some tests, I will hardcode the OpenPDroid 1.0.1 to be default for all build dates for Auto-patcher v2.6.1

For now, the way to get the new patches is to specify the date. You might have to use manual patching if you are an ApG user. The command line version would be

./auto_patcher Mako-4.2.1rom.zip openpdroid aosp 20130201

I have actually only tested the mako cyanogen roms, which patch fine. I am going to try and test a stock mako rom now, but if you have any success let me know. I will figure out a solution if stock mako roms give us trouble, though. Despite my irrititation that mako is significantly different from the N7 or N10, I do think it is important to support the device.

I am downloading a stock mako rom now, I will update this post when my test is complete.

Update: No mako stock still fails on Camera. It does patch for Cyanogen now, though. I will attempt a fix for 2.6.1, I foolishly only tested CM befor release. We'll get it.
[Android Software/Hacking General [Developers Only]] scutworker:
Hi mateorod,

Further to my logcats above, I'm now wondering if I have the right patches at all.

I'm running an Evervolv rom and when running the autopatcher in cygwin I see that the patch date is set to 20130109. Shouldn't this be 20130201?

Should I correct in manually using: ./auto_patcher rom.zip openpdroid aosp 20130201 ?

I've attached the autopatcher log when I just used it without any choices.

Ta.
[Android Software/Hacking General [Developers Only]] mateorod:
It is defaulting to the older patches because your rom is a little too old. You can do it manually "./auto_patcher ROM.zip openpdroid aosp 20130201", although I don't know the exact ApG protocol. You do need to designate a romtype (i.e. aosp) in order to specify a date. The easiest thing is to update to a rom made aftre 1/21 or so ( the date I hardcoded for 1.01. to start at).

`As for mako, stock mako is failing still. I tested a fix to the Camera and MediaRecorder but then it just fails later in services.patch. A reminder for now that even with Nexus devices, stock is not the same thing as AOSP. For now, CM10.1 patches for mako, and if anyone could try an AOSP as opposed to stock build, we will know more. I will continue to look at mako, and support for stock of all roms is my next project after OpenPdroid 4.2.1 gets stable.

I also just pushed 2.6.1 to github for ApG users, everyone else will have to wait until this afternoon. It has updated aosp tabletUI patches, which are working for my 7 inch tablets. Maybe that is all they will support in 4.2.1.

Edit Shoot! I also fixed CM9, thanks so much to the person who found that issue. I finally removed the huge backlog of old patches that just aren't need anymore, and I accidentally left a lonely symlink. You should repatch with 2.6.1 if you have ApG. If not, I will upload 2.6.1 later today.
[Android Software/Hacking General [Developers Only]] yavu:
Is C-Rom Mix V9 Android 4.2.1 based on CM10 and Helly Bean vor SGS patchable without any problems?
[Android Software/Hacking General [Developers Only]] scutworker:
Right, I did that and have just applied the latest patches and...it works! The GPS slowdown seems to be gone, so you should ignore my logcat from the previous post as that was made using the old patches I inadvertently applied.

Thanks so much for your help on all this.
[Android Software/Hacking General [Developers Only]] madyinwhich:
Hi mateorod, I patched the CM10.1 nightly for my Galaxy S2 a few hours ago and so far no problems, it is all very smooth now. Thank you very much!
[Android Software/Hacking General [Developers Only]] brGabriel:
Like you said, these issues with tabletUI may be specific to Nexus10 (manta) devices.

The jars I previously posted were pulled from a patched AOSP ROM with TabletUI found here: http://xdaforums.com/showthread.php?t=2078315

The post with the jar files themselves are here: http://xdaforums.com/showpost.php?p=37220451&postcount=1938

It's interesting with the dates of the patch vs. the actual dates of the created zip itself. On the CM10.1 ROM, I manually specified the patch date as "20130201" and the log seems to reflect that it was the patch used. However, the date on the zip shows "update-cm-manta-20130120-tabletUI". Similar occurrence when I tested an AOSP ROM. This may be purely superficial and irrelevant, but I thought I'd at least point it out.

In addition to the logs from both an AOSP and CM10.1 ROM I've attempted to patch, I've also attached the AOSP zip file in case you can use it.
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher 2.6.25 is uploading to techerrata and is already available for ApG users.

Improvements;

Rebuilt AOSP and CM TabletUI.

Confirmed working on 7 inch screens, and mostly on Nexus 4. That may be it.

Fixed a bunch of broken Symlinks that happened in 2.6.1 update.

Removed all OLD patches. If you are using a REALLY old rom, try an Autopatcher 2.5 or below. We still support CM7 to CM10.1!

All OpenPDroid patches are 1.0.1 and are available for the ENTIRE supported roms list 4.1.2 and above

Roms: CM10, CM10.1, AOSP and AOKP 4.1.2 and 4.2.1. Evervolv, PA and SlimRom 4.2.1.

Mako support for AOKP and Cm10.1,

not

stock (b/c Nexus4 is not supported by AOSP, thats the issue here)

Fix for slow GPS

Fixed SMS problems

Huge performance increase (should be no drain on performance at all)

Cache protections

Increased debugging logic

...more

Added karamelos and Grayfoxmg1 to contributor list on OP in recognition of their work here in the thread. No further responsibility is assumed or implied. Added lightspeedbriefs to contributor list for a pull request sent.

For the rom builders out there, we have pushed build patches for OpenPDroid 1.0.1 as well, so you can non-destructively add OpenPdroid to your project or home build.

I believe all of the mods are now relatively stable for 4.2.1, tabletUI investigations nonwithstanding. I have some small issues internally that I want to get to, but this catches us up to the major bug fixes from OpenPDroid. I am going to let you guys report how this is treating you and then we will try and settle on a LTS version (2.6.3 or so) and refrain from updating unless something in the upstream repos forces our hand.

Let us know how it goes, and remember to post Auto-Patcher logs for auto-patcher problems and logcats for OpenPDroid problems. It is the only way we can fix things.
[Android Software/Hacking General [Developers Only]] xbox1513:
I used this on the latest cm for nexus 7 grouper, "cm-10.1-20130131-NIGHTLY-grouper-tabletUI-20130201-update", it shows the tablet ui, but when click to expand the notification, i get a system UI error.
[Android Software/Hacking General [Developers Only]] brGabriel:
Still no UI change with version 2.6.25 on Nexus10--AOSP or CM10.1 roms :crying:
[Android Software/Hacking General [Developers Only]] Teemoo:
v 2.6.25

pa 2.99 beta 4 openpdroid - maguro , patched with error(?) RIL sender 15/15 ignore, but so far works great, camera works fine, no performance issues, no leak at network info2

thanks.
[Android Software/Hacking General [Developers Only]] nsmart:
I am not sure if there were any fixes for the slow gps/compass issues between v2.60 and 2.6.25. Just for completeness, they are still present in 2.6.25 (see logcat). After using it for some more hours I noticed that it is not always slow. It seems that it is slow after a reboot of the device. If I use another app like google maps to get a sat fix and then switch to gps-status, the compass is fine.
[Android Software/Hacking General [Developers Only]] fezzawinkle:
I get an error patching the Modaco JR4 rom for the Nexus 7 3G. Would you expect this to work? I can paste a log if that helps. But it is working fine on Temasek's CM10.1 [Unofficial] from 29 Jan.
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Hi mateorod, I ran into issues again patching PA 2.99 betaNINE for the Galaxy SII i9100 - same issue as before the RIL$RILsender.smali file patching.

Log of unsuccessful patch:

http://codepad.org/tao6cX9b

PA 2.99 betaNINE i9100:

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

Exact issue is the following part of the patch:

invoke-static {v10}, Lcom/android/internal/telephony/RIL;->access$200(Lcom/android/internal/telephony/RIL;)V

When I modify the telephony-common.patch with the code below and run ./batch.sh again it patches successfully and the update zip applies correctly without causing the phone process to continually crash:

invoke-static {v10}, Lcom/android/internal/telephony/RIL;->access$000(Lcom/android/internal/telephony/RIL;)V

Successful log:

http://codepad.org/aDbrnUGY

Looks like I may be the only person running PA 2.99 on the i9100 who is applying the OpenPdroid patch as I am the only one constantly bugging you about this! :laugh:

I am happy to modify the patch so I can successfully apply the OpenPdroid patches for this Rom but just wanted to let you know what I found. Thanks again for all your work on this I couldn't live without having the power of Pdroid!
[Android Software/Hacking General [Developers Only]] karamelos:
Thank @mateorod work well !!!

cm-10.1-20130131-NIGHTLY-n7000.zip (n7000)

cm-10.1-20130131-NIGHTLY-grouper.zip (nexus 7 wifi)

cm-7-20130201-NIGHTLY-cooper.zip (s5830)
[Android Software/Hacking General [Developers Only]] fanedhardy:
Openpdroid - AOSP-4.2.1

Hey guys,

is it possible to patch the following Rom:

[ROM] [AOSP-4.2.1] [J0P40G] [Linaro 4.7.3-toolchain] [SR8] OFFICIAL codefireX Builds

http://xdaforums.com/showthread.php?p=34386599

I only get a restore..*..zip file. Could sb help me?!

Thx

Chris
[Android Software/Hacking General [Developers Only]] liebowa:
I had this same issue last week on an earlier nightly and reported it then. I just tried again with the same nightly you tried (1/31) and can confirm that this issue still exists, unfortunately.

I'm going to try a few other Nexus 7 ROMS and see how it goes...
[Android Software/Hacking General [Developers Only]] pommegmx:
official Milestone build

Like this ? :)

http://sendbox.fr/pro/0l8whakklweh/...GBRTFR_P012_A006_HWp2a_Service1FF.sbf.gz.html

:victory:
[Android Software/Hacking General [Developers Only]] daibaron:
Hello,

i have a Samsung Galaxy S2 with ICS 4.0.4 Stock rom ... can i use the "autopatcherv2.6.25" and get my rom patched ?

Or shall i follow the entire process to generate my very own update.zip/restore.zip

regards
[Android Software/Hacking General [Developers Only]] mateorod:
I did not experience this, but maybe I missed it. This tabletUI thing, man. This is what I am going to do. I am gonna look at it some more over the next week or so, now that OpenPDroid is at a somewhat stable place and no longer the bloodbath it was there for a little bit. I am aiming to have a final solution for 2.6.7. That could be one of several things;

a) Only available for 7 inchers

b) works, but has this bug

c) removed entirely from auto-patcher

d) Completely fixed

e) something else?

Just letting you know, any of those could happen. I dropped it from 2.6 for a reason, but let myself get sucked into offering it again. I will give it a little more time, but honestly, it isn't my thing, and is proving to be a pretty big hassle.

The patches have only been changed that one time, and really all I did was remake them in case there was a breakdown in the patch generation. See above, I will let you know more when I know more.

Unless you post your log, I know less than you.

Unless you post a log, I can't help or know, sorry.

Well, thanks but not quite. I was told that the Official Release of Cyanogen Rom for Milestone was failing. I couldn't find an Official milestone release. Maybe I missed it. But if someone see that, let me know. If there isn't an official release, then I can maybe look at the unofficial build, but those builds are unofficial for the same reason that they will be hard to patch- they have hardware abnormalities that require special attention and software tweaks.

Doubtful that you can patch a stock rom right now. I will be working on bringing this to stock roms next, basically as soon as I can put the tabletUI to bed, one way or another.
[Android Software/Hacking General [Developers Only]] pommegmx:
Milestone

Ok, sorry, it was the last official rom from motorola :o

The only cm rom for milestone 2 is here :

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

There isn't an other one. :confused:
[Android Software/Hacking General [Developers Only]] fanedhardy:
Sorry for that. I started a new try (log attached - I used this command: ./auto_patcher cfx_ace-4.2.1-SR8.zip openpdroid aosp).
[Android Software/Hacking General [Developers Only]] masterex567:
Sorry for the noob question.

Can this patch diff files?
[Android Software/Hacking General [Developers Only]] 51liberty:
AOKP-MR1 for Nexus 4 (mako) is failed. (OpenPDroid)

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

!!! PATCHING FAILED FOR com/android/server/ServerThread.smali !!!