yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] dorfd1:
I have a galaxy player 3.0 running cm10.1 nightly 7/10/2013

The DPI is set to 90

I was able to patch tablet ui in the last build from 6/22/13 which was the build previously compiled for the device.

When ever I patch tablet ui in the 7/10/2013 build, system ui crashes.

I use autopatcher GUI for windows.
[Android Software/Hacking General [Developers Only]] GnatGoSplat:
Thanks so much, lack of git was exactly it. My understanding of git is as source control, and since I don't do any development myself, I didn't realize I would need it. The link you posted installed git and the auto updating worked. I was able to patch and everything installed perfectly.
[Android Software/Hacking General [Developers Only]] mateorod:
Well, to be fair, I have not really publicized the information. I have enabled it by default but am otherwise kind of sitting back and watching.

I am thankful that you took the time to install git, now we know that updating does indeed work on OSX. That is pretty neat! I need to add git to our published dependencies soon. Git is pretty much only used for version control, but I have leveraged it to provide updates. This is pretty much the same system that kobiik used to update the script in ApG.
[Android Software/Hacking General [Developers Only]] Android-Andi:
Hello together,

i´m sorry if this question was asked before.

Is it possible to build the patch with "tabletUI cm 20130403" and "openpdroid cm 20130516" together? I tried but i didn´t got it worked.

Will i have problems if i flash both as single-zip? There are no problem to build single patch.

Im on a Galaxy Tab 2 7.0 (P3110) and CM 10.1.2 Stable release. Patch without an changed date didn´t worked.

Windows 8 Pro on my Laptop.
[Android Software/Hacking General [Developers Only]] mateorod:
Lots of people have applied both but maybe not with older patches. If you flash two separate zips you will wipe out the changes to the services.jar from the first one you flash. It has to both in one zip. That is one of the big advantages to the autopatcher (even if very few people use it this way) you can layer mods. Distributing flashable zips forces people to choose one or the other.

One long gap in functionality we have is that when needing to use older patches, you cannot specify two dates on the command line. If applying multiple mods, the date specified will apply only to the first mod. And in whatever order you put the mods, the "pdroid" mod will go first, for internal reasons.

So if you put a date, it will use that date on openpdroid, and all other mods will default to their "latest" patches. This has only been a theoretical problem until now, but with the stables and final releases, based on old code, I guess it theorectically could be an issue with just those two mods.

I would rather have a log in front of me before I say you cannot do it for certain,,,but my best advice is to just use a current nightly release. if you want the code from the stable, just use the nightly from two or three weeks ago.

I know that isn't a perfect answer...it has been on my mind that I want to fix that lack of function, but it requires some heavy intellectual lifting, and probably a complete re-write of the build query, now using multi-dimensional arrays and all the rest. If the program was written in an object-oriented language, this would be easier. Any interested parties can read my previous thoughts on this on our issues list on github, but I never fixed it as it was a mere intellectual issue until, I guess, now.
[Android Software/Hacking General [Developers Only]] Android-Andi:
Thanks for your answer.

Isn´t there any way to change the directorys of the patches to "emulate" the latest version?

Mybe delete the \ApGPackages\ap\patches\tabletUI\4.2\cm\20130627 or rename the older one?
[Android Software/Hacking General [Developers Only]] mateorod:
Oh there are options, it just depends on how willing you are to get your hands dirty. And how married you are to wanting to use the stable release. There is a vector there, it just depends where you are on it.

But I am 100% certain the actual patches are compatible. But it will not be quite as "auto"-patching as previously ;)

Easiest way to try off the top of my head (if using OSX, might differ slightly), change into the autopatcher directory.

cd patches/tabletUI/4.2/cm
rm latest
ln -s 20130403 latest
cd -
./batch.sh
./auto_patcher ROMSNAME.zip openpdroid,tabletUI cm 20130516

Like I said, possibly you will need to adjust that some, but the mechanism is just as you guessed. Repointing the "latest" symlink to your desired tabletUI match should work fine. Just deleting the any new patches along with the above might make it certain.

If you have git installed, you may want to enter "git reset --hard && ./batch.sh" afterwards to reset yoiur environment. We have an auto-updater but it only works if it can merge with local changes.

Good luck!
[Android Software/Hacking General [Developers Only]] Android-Andi:
Got the new "latest", date is in there but if i use "Manual Patching" Auto Patcher didn´t use it... it choose the old date (new date i don´t want to use :P ) like before ...

## copy patch openpdroid/4.2/cm/latest ###

... copying system/media/PDroid.jpeg ...

... overwriting system/media/PDroid.jpeg from openpdroid ...
`patches/openpdroid/4.2/cm/latest/system/media/PDroid.jpeg' -> `./system/media/PDroid.jpeg'

... overwriting ContentResolver.smali ...
### delete patch openpdroid/4.2/cm/latest ###
### jar patch openpdroid/4.2/cm/latest ###

... apply framework.patch ...
1 out of 9 hunks FAILED -- saving rejects to file 'smali/android/provider/Settings$Secure.smali.rej'

... apply preloaded.patch ...
!!! PATCHING FAILED FOR android/provider/Settings$Secure.smali' !!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

i´m sry 4 my english... and thanks for your help!

Maybe i´ll try one of the next cm nightlys ;)

Will AP work with the stable without any problems next time (after update) ?
[Android Software/Hacking General [Developers Only]] mateorod:
Got the new "latest", date is in there but if i use "Manual Patching" Auto Patcher didn´t use it... it choose the old date (new date i don´t want to use :P ) like before ...

i´m sry 4 my english... and thanks for your help!

Maybe i´ll try one of the next cm nightlys ;)

Will AP work with the stable without any problems next time (after update) ?[/QUOTE]

I would need our log to diagnose...that should work if those are indeed the correct patches for that ROM. I may take a peek out of intellectual curiosity. I will probably not refractor the build query to handle the stable builds right now. It is a problem that will go away when I go to the next model I have in mind. Hopefully soon-ish. But the Stable-releases just use old code with new build dates. It is more a reflection of how far the CM code base has come than anything else. Try a nightly, it is very rare that the one you choose has introduced any new issue over the stable, and it will have several great features I know the stables do not.

The stable/Final/RC cycle is a rare occurrence...it will not be an issue for Android 4.3, that much I can say.
[Android Software/Hacking General [Developers Only]] Android-Andi:
Should i upload my log files?
[Android Software/Hacking General [Developers Only]] Urinophoria:
I'm curious too, still learning this stuff, so I'd look at it at least if you uploaded it
[Android Software/Hacking General [Developers Only]] KingKuno:
Hi,

I use ApG. But where are updates ? My last update is "2013.05.30. (v2.9.8) Improve apk handling: fix disappearing apks. New opd: evervolv,slim".

I download the .exe new and update it but it is still the same. When I patch a Rom it fails but I know somebody where it works. So what is the/my problem ?
[Android Software/Hacking General [Developers Only]] Android-Andi:
Logs attached
[Android Software/Hacking General [Developers Only]] mateorod:
Is the Mms.apk stil disappearing for people? I have literally fixed everything I know how to fix. The ;ast thing to try will be looking into resigning the apks, which I really don't want to do.

If you have the Mms.apk disappearances using autopatcherv2.9.924 or later, please post your logs. Thanks guys.
[Android Software/Hacking General [Developers Only]] bustedwings:
Had It happen with my last build. Here is the log
[Android Software/Hacking General [Developers Only]] mateorod:
Shoot. I have been working on this behind the scenes almost constantly for the last several weeks. I have tried many of the different apktool forks floating around, changed/improved many of the ways we handle apks and their certificates. I have fixed the GSM and CDMAServiceStateTracker replacements, which certain people suggested may be the cause...I am really at a loss.

There remains the distinct possibility that resigning the apks could help...but I really have to be thoughtful about that. I don't want to introduce security concerns, the cure cannot become the poison. I may have to just start looking at ways that we can remove Mms.apk patching from the process, if that is even possible. I have also beta-tested using the baksmali binaries instead of apktool, perhaps I need to go back to finishing that.

Thanks for the log...please keep them coming folks. I need to try and find out the common denominator. If it disappears and you have to sideload, please post logs for me, ok?
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, I made the switch away from apktool to just the baksmali binaries. This is one of the more aggressive changes I have made in this battle. Anyone who has the disappearing Mms.apk please try and report.

The version with the fix is up, but make sure you are using Autopatcherv2.9.25.

This is almost guaranteed to cause some problems for some people...switching away from apk means turning off all of the hard-fought workarounds that makes apk patching work for most people. Just let us know what happens and post a log. Thanks guys.
[Android Software/Hacking General [Developers Only]] dorfd1:
The new update fixed tablet ui. Tablet ui is working fine on my galaxy player 4.0 running the 7/10 build of cm10.1
[Android Software/Hacking General [Developers Only]] bustedwings:
Will try patching same release and post log. Also try patching latest weekly and post log.

The MMS is actually under system apps after flash just can't launch. Also when try to install gives error. Almost thinking it may be the signing that's causing a problem... Just a thought.

As always keep up the good work. Its appreciated.
[Android Software/Hacking General [Developers Only]] bustedwings:
Both patches seemed to work flawlessly. MMS app is showing up.

log for Slim build 7

View attachment log20130714222500.txt

log for Slim build 7.2

View attachment log20130714224747.txt
[Android Software/Hacking General [Developers Only]] redandr:
Trying patching the new CM 10.1.1 for manta and CM 10.1.2 for mako (both stable) with opendroid.

Same error occurs:

error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied

I work under Windows with ApG.

Update: strange thing. With the latest nightly builds it works again like it should, no problems on both devices.
[Android Software/Hacking General [Developers Only]] Wartickler:
Same as above

Same here, though CM 10.1.2 spyder. Tried openpdroid + supercharger, and then just openpdroid which worked on previous CM 10.1.1

Using ApG

pastebin: http://codepad.org/O5yrd08k

EDIT: tried with nightly 20130714 and opendroid and it patched!
[Android Software/Hacking General [Developers Only]] mateorod:
My good man. thanks for the report. I have changed things drastically enough that I am going to go aheadw and mark this solved until I hear otherwise. You win the award for my favorite post....maybe ever.

If you want to know the reason, read my posts from the last couple days. otherwise update, I fixed this for you.

Autopatcherv2.9.9.265 is out, and should be immediately updated for Linux and OSX users, while ApG users can update as usual.

Improvements include

Fix "disappearing" Mms.apk

Should be no more need for sideloading or special Mms,apk handling. I have thought this before, so let me know if I am wrong.

Automatic patching for CM10.1 Final builds (10.1.1 and 10.1.2 and so forth)

Upgraded to SlimRom aphtool and aapt (except for OSX, sorry) so theming for SlimRom will remain intact

Caldair refined and fixed some SystemUi FCs in tabletUI

LOTS of behind-the-scenes bugfixes

Much of this you guys already have if you have been updating regularly. But we believe we have solved several long--term bugs so I am announcing the update. Plus, I recently got confirmation that auto-updating is working for OSX users.
[Android Software/Hacking General [Developers Only]] dirtyreturn:
Good evening @mateorod and all. With latest auto_patcher 2.9.9.266 patching CM-20130715-Nightly-maguro fails with secure settings.

Here is log: http:// http://codepad.org/l1sZIGZ6

Edit- same with 2130714 nightly.
[Android Software/Hacking General [Developers Only]] mateorod:
My bad. I fixed it. I was setting everything to Final. whoops.

Fixed in Autopatcherv2.9.9267
[Android Software/Hacking General [Developers Only]] IRKONIK:
Errr.. Is this fixed, too? :)

Edit: nope, it's not. :(

Gesendet von meinem Nexus 10 mit Tapatalk 2
[Android Software/Hacking General [Developers Only]] mateorod:
Okay...I did not realize that this was a different problem than the pther broken PA patches (which we fixed last week thanks to [MENTION=4418789]Urinophoria[/MENTION] and [MENTION=4515360]juggies[/MENTION]).

I added a workaround that allows this rom to patch...only you can tell us how that fix performs. But it patches with autopatcherv2.9.9268. Update and try again.
[Android Software/Hacking General [Developers Only]] freddysam:
Whatever version was the latest on July 14th worked perfectly on slimbean build 7.2 for openpdroid. I just used v2.9.9268 with strange results. Both the restore and openpdroid zips are missing the "app" folder (ie the mms.apk).

http://codepad.org/moIutb8V

Also, the change log hasn't updated since July 7th v2.9.92 even though the patches have been updating on ApG.
[Android Software/Hacking General [Developers Only]] mateorod:
If I updated the version number for every commit, the change log would be a thousand lines long. I update the change log for second decimal level changes, I.e. 2.9.7 to 2.9.8. If you need more fine grained change information, visit the github page which has each change line by line.

The restore zip is mostly there to keep me from getting questions about it, the best thing to do is to simply reflash the ROM. But I did just change the MMs handling so I can fix that.
[Android Software/Hacking General [Developers Only]] raziel23x:
I have not seen much updates to the binary for the windows version. Does it need updating or is it just a translator for the Linux scripts and does not need anything done other the updates from Linux scripts
[Android Software/Hacking General [Developers Only]] mateorod:
Yeah, it just resolves our dependencies and provides button clicks. The program itself is updated in the GUI straight from github so you are getting the latest changes.
[Android Software/Hacking General [Developers Only]] freddysam:
I can understand not adding entries in the change log for the nightlies. I just didn't realize that we were using the nightlies by default. I was assuming ApG wasn't updating because the change log stayed the same. What might help is using the patch version in the name of the created zips in addition or instead of the date since that is more significant. Just a suggestion.

The openpdroid zip was missing the mms.apk in latest patch too.
[Android Software/Hacking General [Developers Only]] brGabriel:
Hey guys. [MENTION=1449163]Caldair[/MENTION], Having some trouble using the tabletUI patch on a CM based ROM. I've used Auto-Patcher successfully with this ROM for several months, but this time I'm getting an error with the SystemUI.apk during the patching process. I've included my log. Thanks for great work, guys!
[Android Software/Hacking General [Developers Only]] Caldair:
That rom is in the "sweet spot" between working tabletUI patches(June20-June 27). It may not be possible to produce a mod based on that particular build at all, but you could try to run the autopatcher this way:

./auto_patcher sentinelrom_v4_80_manta.zip tabletUI cm 20130627

You might get lucky and that may work. I am doubtful though, more likely you will have to go back a build and wait for the next release, if you want tabletUI.
[Android Software/Hacking General [Developers Only]] mateorod:
Wait a minute. So something isn't working in either Cygwin or your particular environment. We need to figure out which it is. I just tested your rom and both the restore and update zip are correct and contain the Mms.apk.

I need to look at this. If anyone has cygwin and can run this for me and post a paste of the output, I would appreciate it

bash -x ./auto_patcher ROM.zip openpdroid

.

I am probably not going to change the versioning information. All info for each run is available in the logs, and the source is available for perusal. We update the changelog maybe once a week with over-arching changes. I also provide a changelog.txt for every update if you use the command-line updater, which has every commit listed, exactly as you would see from things like CMUpdater. That document is provided each time the script updates. If you want a commit-by-commit changelog, you can use the command line and the auto-updater. Or you can retain control of when it updates by turning auto-updating off.

Using ApG overrides much of this information, as it preempts my internal updater. But using the command-line, you can get all the information you need. ApG tries to take care of much of that for you, and tries to have sensible defaults. I believe that we are as transparent as we can be.

Now what is happening with your update.zips, I don't know. Have to look into it. Can anyone else using Cygwin check in and see if the Mms.apk is getting put into the update.zip?
[Android Software/Hacking General [Developers Only]] cdx47:
Patch fail Device:Mako, Rom CarbonRom AOSP Nightly 17/07

Here is the failure log while using Windows ApG to patch AOSP CarbonRom on my Mako

... apply preloaded.patch ...

!!! PATCHING FAILED FOR android/app/Fragment.smali android/content/AsyncTaskLoader.smali android/os/SystemProperties.smali android/provider/Settings$Secure.smali' !!!

!!! patch error for android/app/Fragment.smali !!!

File for which patching failed:

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

Fragment.smali

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

We are adding a pre-patched copy of those files.

Please only file a bug report if running the program gives you problems!!!

... replace android/app/Fragment.smali ...

`patches/openpdroid/4.2/.provisionals/system/framework/framework.jar.out/smali/android/app/Fragment.smali' -> `tmp/system/framework/framework.jar.out/smali/android/app/Fragment.smali'

... failed patch sucessfully resolved ...

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!! error: failed android/content/AsyncTaskLoader.smali in framework.jar cannot be remedied

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Here is the full log via Pastebin: http://codepad.org/hyAnbpNs
[Android Software/Hacking General [Developers Only]] freddysam:
Here you go:
[Android Software/Hacking General [Developers Only]] brGabriel:
Thanks for your reply, I'll give it a shot! And if not, I can wait until the next release. :fingers-crossed:
[Android Software/Hacking General [Developers Only]] mateorod:
Okay, looks like Cygwin was using a slightly different expansion than the standard bash shell. I have fixed it up, I believe.

The problem we now face is whether or not the fix for the "disappearing Mms.apk" was fool's gold. If anyone has the Mms problems using the new autopatcherv2.9.9268 or later, please report.
[Android Software/Hacking General [Developers Only]] freddysam:
Everything seems to be working now. Thanks!
[Android Software/Hacking General [Developers Only]] Android-Andi:
thanks for your hard work. will there be an updated for windows apg?
[Android Software/Hacking General [Developers Only]] Didgesteve:
New Slim 7.2 weekly works a treat. All the features working, and mms is fine.

Good work.
[Android Software/Hacking General [Developers Only]] Christoph21x:
Hi Mateorod!

Thanks a lot for this GREAT utility!

I just discovered an issue which prevents some ROM's from successful patching:

Some newer (low-budget) tablets don't have a SIM card anymore, like e.g. Samsung Galaxy Tab 2 type(s) p3110/5110.

Thus they don't have a Mms.apk - this leads to failure when auto_patcher is trying to "rebuild" this.

Maybe you can simply enter a flag - if not found in the ROM package, don't try to rebuild? ;)

Workaround for your post #1 for the time being: copy a Mms.apk from the same build date from model WITH SIM to System/apps and run auto_patcher without any problem.

Anyhow: the tablet will never call this apk. If anyone want, he/she could even erase (recompiled) Mms.apk after successful run of your auto_patcher.

Thank again for this great help -

Greetz from Switzerland, Chris.
[Android Software/Hacking General [Developers Only]] mateorod:
Whoops. Actually, I already have provisions for this, but when I changed a variable name yesterday to account for the Cygwin environment, I missed one change. That was then skipping the part that allows for no Mms.apks.

The details are at the github page, but all I had to do was change a "~" to an "@" and everything is now working. I wont forget about wifi tablets, because those are the only Android devices I own!

Thanks for the report, Didgesteve, but just in case will you repatch with 2.9.9.269? I had a bug introduced yesterday, I want to make sure you have all working and patched files. Thanks!
[Android Software/Hacking General [Developers Only]] Christoph21x:
THANK YOU! Wow - what a great and fast answer... !

Greetz - Chris
[Android Software/Hacking General [Developers Only]] Android-Andi:
Tablet UI fails on CM-10.1.2. APG set´s the date for it on 20130516 but does not exist. Must be 20130403 for Tablet UI.

Openpdroid works (20130516 is right).
[Android Software/Hacking General [Developers Only]] mateorod:
Well spotted. It took me a minute, but I was able to fix it. You should be able to run both of those together in autopatcherv2.9.927. Pointed me to a bug that has probably been lurking for quite some time, and may enable me to knock out a few lingering issues on my issues page.

Thanks.
[Android Software/Hacking General [Developers Only]] Didgesteve:
Slim 7.2 re-patched with the latest and everything working great ::thumbup
[Android Software/Hacking General [Developers Only]] Android-Andi:
Building openpdroid + tabletui together for CM 10.1.2 without any problems now :)

Thanks!
[Android Software/Hacking General [Developers Only]] meviox:
Hi mateorod,

I get the following error message when patching today's CM nightly (cm-10.1-20130719-NIGHTLY-i9100.zip) with the autopatcher v2.9.9271:

error: failed android/provider/Settings$Secure.smali' in framework.jar cannot be remedied

May have to do with the replacement of SEAndroid by SELinux (cf. the changelog)?

Attached the log file.