yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] xpria2012:
Hi,

I'm trying to patch FreeXperia Project's CM 9.1 ROM for Xperia P with the latest version of The Auto-Patcher. However I'm getting an error, and honestly I have no idea what is wrong with it. I'm trying to patch the version FXP204. Until the version FXP202 I was able to patch the ROM successfully. I'd really appreciate it if you could look at it. Thanks a lot in advance!

$ ./auto_patcher FXP204-cm-9-20130126-UNOFFICIAL-nypon.zip pdroid,v6supercharger

The Auto-Patcher v2.5.7

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.0.4 rom= cm ...
... Using results of ROM check ...
... pdroid patch date has been set to: 20120811 ...
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
### jar patch pdroid/4.0/cm/20120811 ###
... apply framework.patch ...
The next patch would create the file 'smali/android/app/ContextImpl$36.smali',
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/android/app/ContextImpl$36.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
38 out of 38 hunks ignored -- saving rejects to file smali/android/net/wifi/WifiConfigStore.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
15 out of 15 hunks ignored -- saving rejects to file 'smali/com/android/internal/telephony/RIL$RILSender.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file 'smali/com/android/internal/telephony/sip/SipPhone$SipConnection.smali.rej'
... apply preloaded.patch ...
... apply core.patch ...
... apply services.patch ...
114 out of 117 hunks FAILED -- saving rejects to file smali/com/android/server/ServerThread.smali.rej
!!! PATCHING FAILED FOR com/android/server/ServerThread.smali !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Android Software/Hacking General [Developers Only]] liebowa:
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

A HUGE thank you for edd adding the TabletUI options back. Great work!!

I've downloaded and installed the latest nightly CM build for my Nexus 7. I then ran the autopatcher against it and installed the resulting zip file and all went well.

But, I just found that the notifications are failing with a System UI has

Stopped error.

And, as I'm typing this, I noticed that when I try to use Google

Voice Input, it is also crashing. Both of these items worked before installing the patched zip file which I created with ApG.

This is with last nights CM nightly and the latest gapps.

What can I send along to help you debug or investigate?
[Android Software/Hacking General [Developers Only]] mateorod:
I have quoted the wrong post, sorry, but I was asking for a link to the thread where that patched services and android.policy came from. But I think I am just going to rebuild aosp for this mod, something isn't acting right. Although the smali patches look exactly like I would expect and match up fine with the others.

Might just have to use an older build until we can get these updated patches out. I hope it will be soon, it just takes a bunch of time and effort, and I can't fully devote too much time until Monday night.

I don't see why that would be, with the status 7. That generally means that you are failing an assert, usually the device check. If that rom installs, then the update.zip should install, we basically just copy/paste the original updater-script right over. As for compatibility, if it isnb't expressly on the list, you can try it. Most of our mods will work for all roms. But the PDroid-type mods are very invasive, and only by trying will you know. I can't keep up with all the roms, especially ones for devices I don't own. I have never heard of Minco, so your guess is as good as mine. Good luck!

Well, even if your device is still doing all that you want it too (can you make phone calls after deleting this jar?) you are losing some PDroid functions by deleting this file. My advice would be to use a build from a week or two ago until we release new patches, sometime this week. (I promise.)

Yes, that lag is the cache. Essentially, we noticed that the original 4.1.2 patches were requesting access to the database and then leaving it open. So as a nod to better practice, we cleaned up and started closing it behind us. Unfortunately that has resulted in the database getting near constant requests to open. One thing that I believe will help is a switch to SuperSu. Delayed and repeated requests to SU usually are found with Superuser app. For instance, while I have seen this reported often, I have never experienced it myself. Maybe I am lucky, or maybe SuperSu helps.

Sorry, I don't really know what is going wrong there. Would you do me a favor, and try a recent Official Cyanogen9 release? (Doesn't matter which device, we just want to see if it patches). If it patches, then that just means your device's rom starys too far from the Official tree to be supported. If it doesn't, then that means that our CM9 patches broke and just nobody noticed. If that is the case, I will rebuild and update the CM9 patches.

Jeez. I just tested this on a Nexus 7 CM build yesterday. This is an official release? One question, are you sure that the gapps are up to date? I had the exact same problem with all voice search and Google now, and then I checked the play store and updated the Search app and it was fixed.

I had these exact same issues on the exact same device and was able to fix it in this manner. Let me know.
[Android Software/Hacking General [Developers Only]] :
I'm sorry my good friend :highfive:

See my quote from mateorod :)

Mateorod thank you my good friend for all your hard work :good::victory:
[Android Software/Hacking General [Developers Only]] liebowa:
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

You solved the voice search issue I was having by downloading the updated search app from the store. THANKS!!

Still having the issue with the notifications panel though.

Many, many thanks man!
[Android Software/Hacking General [Developers Only]] D-m-x:
Just wanted to report, that the patching for the newest AOKP unofficial for Mako is failing. Maybe something has changed.
[Android Software/Hacking General [Developers Only]] Tha Maxx:
I am also having issues patching latest xennonhd rom http://codepad.org/Rotm9boE for view
[Android Software/Hacking General [Developers Only]] l3ullseye:
Yes I have tried with a CM and successfully apply the patch, so I think maybe it's something with that rom, I'm gonna try later with a different version, thanks.
[Android Software/Hacking General [Developers Only]] madyinwhich:
Thanks mateorod, after switching to SuperSu it is much better now. The apps get the root privileges in time. But there is still an issue with the status bar especially after rotating the screen the status bar crashes sometimes and need to restart. But maybe there will be a fix for that some time in the future. :)
[Android Software/Hacking General [Developers Only]] AuSSiELaMbChOpS:
Fix for PA 2.99 - Samsung Galaxy SII i9100

Hey mateorod, I was still encountering issues with PA 2.99 betaNINE on the Galaxy SII, patches were being made successfully but the phone process was crashing continually. Deleting the telephone-common.jar stopped this from happening but as you have mentioned would result in the reduced functionality of Pdroid itself.

Finally nailed down the issue to the RIL$RILsender.smali file and some of the access$ values used, as it works for you on your grouper this must be specific to the Galaxy SII i9100 branch of PA.

I have attached the modified smali to this post if you are interested, very minor changes made if you would like to include this I could make a pull request in github to the original file or another location. Totally up to you.

I am so happy Pdroid & the OpenPdroid patch are now working without issue on my phone full of Paranoid goodness.

The modified update zip I created and flashed is linked below, I provide this with the usual disclaimer that I am not responsible for anything that may happen to your phone by flashing this package etc.

CAUTION THIS IS FOR THE i9100 PA 2.99 20130125 BUILD!!!! PLEASE DON'T TRY THIS ON OTHER PHONES/ROMS

http://d-h.st/1Hn

Enjoy!!
[Android Software/Hacking General [Developers Only]] xMemphisx:
I have a stock/rooted/deodexed ROM (plus BusyBox) for the Mako (LG Nexus 4), 4.2.1. I cannot get the auto-patcher to work for me. Looks like there may be some kind of issue with the camera. Here's my log output:

./auto_patcher mako_4.2.1_Deodexed.zip openpdroid

The Auto-Patcher v2.5.7

### 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
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

usage: ./auto_patcher <ROM> <MODS> <ROMTYPE>
example: ./auto_patcher CM10.zip openpdroid cm

Use ./auto_patcher -h for the help menu

Any ideas?
[Android Software/Hacking General [Developers Only]] Ich@:
Hi samsungmario, can you tell me, what i must do, to use pdroid on 'Omega 19.1'

THANK YOU GUYS!!!
[Android Software/Hacking General [Developers Only]] a3955269:
well, easy:

- autopatcher jb patches

- baksmali omega framework

- manually apply autopatcher patches

- smali changes back

repeat until it works:)

did it for neat already:

http://xdaforums.com/showpost.php?p=37243942&postcount=25713

use forum search to begin with..
[Android Software/Hacking General [Developers Only]] samsungmario:
Grab the three framework files from a3955269 and ADB push them to /system/framework folder. Then change permissions to rw-r-r and don't forget to push the apk file (PDROID) to /system/app folder and do the permissions as well. You are all set. a3955269 mentioned that you can do the same for Neat Rom lite as well. Cheers.

---------- Post added at 06:19 AM ---------- Previous post was at 05:22 AM ----------

manually apply autopatcher patches - this part I don't understand. is there a command line to this while in auto patcher environment? i am using linux. Cheers.
[Android Software/Hacking General [Developers Only]] mateorod:
Dangit! I replied and posted this morning,I guess it did not go through on my end. Just noticed as I was going through my todo list of fixes. Quick and dirty, so I don't waste all my development time posting here...

I know that some people have had success with build 2. but it doesn't necessarily suprise me that there may be issues. I am rebuilding patches as we speak. This problem should be resolved by the update we have sometime this week.

I don't know much about xenon, sorry. If it isn't on our supported list, then the try and see method is all I can offer you. I could be convinced to expand support if you could find a maintainer, which essentially involved building a patched rom every month or so. Try the 'cm' or 'aokp' patches, just because you never know.

Thanks to your log, and one below you I have found a problem. I updated the smali binaries (the tools that decompile/recompile the jars) for the AutoPatcher2.5 release, and apparently those updated binaries cannot recompile 4.2 framework.jars. i will add a fix for that tonight, you should be able to use the program again next update. Thanks for the report.

There are fixes for most, if not all of the performance/cache/Mms issues which are being constructed as we speak. It will take a couple days...

Okay. I tested this on grouper and encore and tilapia, without thinking that I don't have phone on any of them. My mistake. I am going to pull that RIL from the patcher. If you want the patcher to still work for you, just drop the one you found to work in

patches/openpdroid/4.2/.provisionals/system/framework/telephony-common.jar.out/smali/com/android/internal/telephony

and run ./batch.sh. Then the patcher will work for you as normal, but without inserting a bad RILSender file.

As I said above, your two reports led me to find a bug in the smali binary. I will fix it tonight.

Yeah, I know about this. Kind of a shame that Google would have their latest and best nexus device go off tree. I had hoped that the GNex would be the last time that would happen. It makes developing for all the Nexii mroe difficult than I think it should be. I guess it is a consequence of them dishing out the hardware contracts all willy-nilly.

When we release the 2.6.0 auto-patcher (with the new openpdroid patches) I will build and bundle in fixes to support mako, don't worry. I think it is important to support that device.

I can fix this. Look for the next minor update (within 24 hours or so) and try again.
[Android Software/Hacking General [Developers Only]] a3955269:
actually adb install pdroid.apk, it doesn't require root permissions.

theres also a cwm zip in sgs2 omega thread:)

---------- Post added at 06:19 AM ---------- Previous post was at 05:22 AM ----------

you need to merge the patches/changes by hand. e.g. check which file(s) a patch is for and merge by comparing/understanding the diffs.

use your favorite merge/diff/patch tools for that.
[Android Software/Hacking General [Developers Only]] HekllSpawn666:
TabletUI

Hello,

I have an Acer Iconia A700 with latest CM 10.1 nightly Rom.

I "patched" the rom with the TabletUI, but I always have 2 "bars" as before.

The patch seems to work because my keyboard (Swiftkey) is now smaller, but the only one thing that is interesting for me is to merge the button and the notification bars.

Could you please do something ? I can test what you want, just tell me.
[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher 2.5.8 is out

Limited fixes this time as we get ready for 2.6.0. But I wanted to get the fixes for ICS back out there.

Improvements

Fixed ICS PDroid patching

Removed RIL$RILSender provisional

Added Fragment.smali provisional (Beanstalk (?) rom should patch for openpdroid now)

This is what I have left TODO (as in, not included in 2.5.8) that I know of:

Autopatcher

Check out Motorola Milestone

Rebuild AOSP TabletUI (check CM)

Bundle fixes for Mako (openpdroid)

Update OpenPDroid patches

OpenPDroid (to be included, if done, in next patch set)

Mms/Sms bugs (fixed)

Performance issues (fixed)

Cache/Play Store FC (fixed)

Cell tower location always blocked (not fixed yet)

Llama problem (not fixed yet)

If you have a pet issue, post it and I will add it to the list and take a look. (For something relating to our supported roms list, please. Anything else, I can give no promises at this point. I have you in mind long term, but this list is for 2.6.0)

For the OpenPdroid bugs that are not yet fixed, we have some ideas, CollegeDev has been very active with us, and we hope that with the four to five people actively working on the code, we can squash those last bugs and get back to work increasing the security and moving to on-board.

Thanks for the patience, 2.5.8 is up for ApG and should be available for general download on Techerrata any minute. The only improvements from 2.5.7 are listed above, so if they don't apply to you, no need to update. Lates.
[Android Software/Hacking General [Developers Only]] xpria2012:
Hi, I've tried patching with v2.5.8, however the bug still seems to exist. I'd really appreciate it if you could take a look at it before the release of v2.6.0. Thanks in advance!

$ ./auto_patcher FXP204-cm-9-20130126-UNOFFICIAL-nypon.zip pdroid,v6supercharger

The Auto-Patcher v2.5.8

### verify tools ###
### verify ROM ###
### unzip patch tools ###
### unzip patch patches ###
inflated: system/build.prop
### probe rom type ###
... result of ROM check: version= 4.0.4 rom= cm ...
... Using results of ROM check ...
... pdroid patch date has been set to: 20120811 ...
### unzip rom ###
inflated: system/framework/core.jar
inflated: system/framework/framework.jar
inflated: system/framework/services.jar
### create updater script ###
inflated: META-INF/com/google/android/update-binary
inflated: META-INF/com/google/android/updater-script
... using Clockworkmod installer ...
### create restore.zip ###
### decompile system files ###
... decompile framework.jar ...
... extract preloaded-classes ...
... decompile core.jar ...
... decompile services.jar ...
### jar patch pdroid/4.0/cm/20120811 ###
... apply framework.patch ...
The next patch would create the file 'smali/android/app/ContextImpl$36.smali',
which already exists! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file 'smali/android/app/ContextImpl$36.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
38 out of 38 hunks ignored -- saving rejects to file smali/android/net/wifi/WifiConfigStore.smali.rej
Reversed (or previously applied) patch detected! Skipping patch.
15 out of 15 hunks ignored -- saving rejects to file 'smali/com/android/internal/telephony/RIL$RILSender.smali.rej'
Reversed (or previously applied) patch detected! Skipping patch.
4 out of 4 hunks ignored -- saving rejects to file 'smali/com/android/internal/telephony/sip/SipPhone$SipConnection.smali.rej'
... apply preloaded.patch ...
... apply core.patch ...
... apply services.patch ...
114 out of 117 hunks FAILED -- saving rejects to file smali/com/android/server/ServerThread.smali.rej
!!! PATCHING FAILED FOR com/android/server/ServerThread.smali !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! error: failed com/android/server/ServerThread.smali in services.jar cannot be remedied
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

usage: ./auto_patcher <ROM> <MODS> <ROMTYPE>
example: ./auto_patcher CM10.zip pdroid cm

Use ./auto_patcher -h for the help menu

PS tried specifying romtype as cm too, also didn't work
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, sorry, I know it may not look like it, but this is a different rom and problem than what you posted last time. The CM9.1 log you posted patched perfectly, but had a problem recompiling. That was a bug on our end. This log shows a failed patching, which just means that it is an unsupported rom. I would that this is based off of the stock rom with CM tree components, just by the name and I could be wrong. But either way, this rom goes significantly enough off the the standard CM release that our patches don't cover it. We do our best, and cover a vast amount of roms from Gingerbread to today, but some don't patch.

Luckily, I believe that there are roms that DO patch for basically every device. The other rom you posted earlier seems to be one of those. Good luck!
[Android Software/Hacking General [Developers Only]] pommegmx:
Milestone 2

Hi,

I am also interested in the support of milestone. :D

So if you need someone to test, to give log or anything else which could help you, I'm open(pdroid) :silly:

Thanks for your job !!
[Android Software/Hacking General [Developers Only]] Klaus N.:
AW: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

Unfortunately my i9100 stucks this time with the openpdroid patches. But I use the autopatcher patching for supercharger - works great.

But I'm looking forward - with all available patience - for the 2.60- update :D

Thank you for your awsome job to all devs!!!
[Android Software/Hacking General [Developers Only]] dangerzone:
xperia s FXP204-cm-10-20130126-UNOFFICIAL-nozomi fails

FYI to any CM10 Xperia S users:

when using autopatcher2.5.8:

patching "FXP204-cm-10-20130126-UNOFFICIAL-nozomi" with openpdroid fails (even on a retry- see attachment)

patching "FXP202-cm-10-20130110-UNOFFICIAL-nozomi" with openpdroid works

:cowboy:
[Android Software/Hacking General [Developers Only]] im-pulze:
I had heavy bugs with openpdroid installed on the newest 10.1 cm nightly on nexus s.

Constantly crashing statusbar, switching mobile network was impossible, heavy performance issues with bluetooth enabled.

without apg-patches it works flawless.

I wait for the updates and check again if something has changed

It is exactly this problem
[Android Software/Hacking General [Developers Only]] samsara00:
I am currently using CM10 by FXP for my Sony Xperia S, the patcher always worked until now for the newest release (FXP204-cm-10-20130126-UNOFFICIAL-nozomi)

It is not based on stock, so i dont know why it suddently wont work anymore.

http://codepad.org/2N81YpX3

-edit-

oh, just saw dangerzone´s post.
[Android Software/Hacking General [Developers Only]] brGabriel:
Just an update on tabletUI. I tried flashing an update patch on a cm10.1 based ROM today on Nexus10 and same issue as with AOSP. Everything completed successfully, flash went fine, but no change in UI. Just wanted to pass that along since I know you're probably working on it as we speak. Thanks!
[Android Software/Hacking General [Developers Only]] Febby:
Hey Mateorod, I just wanted to report this issue on a ATT SGH i727 (Skyrocket) on the latest slim ROM 3.1.0 when trying to patch with openPdroid for the device. Regular Pdroid patch worked though.

Here is the pastebin log. Hopefully if you get a chance you can take a look at it. :) (Psst I was the guy who has the galaxy nexus that was not so developer friendly). :p

edit: Ok it patched successfully using CM rather than AOSP, not sure if it will cause problems, lol. :)

Log link:

http://codepad.org/fJc0VzJl

ROM thread link:

http://xdaforums.com/showthread.php?t=1897264
[Android Software/Hacking General [Developers Only]] Sandpapers:
Tried patching Slim3.1.1 for LG Nitro HD P930 with v2.5.8.

Fails with openpdroid and pd2.0

Here are the logs.
[Android Software/Hacking General [Developers Only]] Febby:
Re: [Utility][2.5.7][1/25] Auto-Patcher (4.2.1)

Did you try patching it under CM or aosp? If you tried aosp try under cm. That worked for me on my device.