[Android Software/Hacking General [Developers Only]] mateorod:
Auto-Patcher 2.8.3 is available through ApG and our download page

Improvements include:

PACman support for all 4.2.2. mods (all mods but tabletUI, essentially)

The script should determine the correct patches automatically. If it doesn't, you can force '.aosp-pac' on the command line.

This ROM support comes courtesy of new team member, AussieLambChops, who also is responsible for the Samsung PA workaround.

Apks that fails to compile for any reason, now have the option of being copied over and resolving itself.

Thanks to AussieLambChops!

Well, I am not sure what you are asking here? Are you offering to maintain for a device?

We maybe could use that, but maybe no need. Good news for all of Android world today, with full AOSP support now for Nexus 4, 7, 10, and all GNex. This should end up straightening out all problems for those devices, although it may take a little while for that to proliferate. I am going to talk with wbedard and karamelos about updating our 4.2.2 patches early next week and see if the recent merge helps.

It is a really big day for open source, I think...Google decided to spend the money or exert the pressure but either way, those GSM stack binaries are out, and there was no hint it was coming. No wonder JBQ was being so cagey about the factory images.

#### Standard Build Query ####
# VER= v2.8.1
# OS= linux-gnu 64bit
# VID= 4.1.2
# PID= openpdroid
# MID= pa_skate-eng
# RID= pa
# ANDR= 4.1
# BDID= 20130227
# DID= skate
# BID= 20121017

I have been meaning to add this to the OP...right now anything using CM10 frameworks/base is broken in roms 0208 and later. The FM radio commit (or something else) broke our patches and we haven't fixed them yet. Try a build from before 0208 and it will patch and wait for us to update the patches. The only thing you are missing with the earlier ROM is really just FM radio...development for 4.1.2 is pretty much over.

I just tried cm-10.1-20130301-NIGHTLY-n7100.zip from the CM download site and it works now. I figured it might, since that failure looks to me like just some of the 4.2.2. code had not made it into your rom.

As for the PA rom, the same thing for you as the guy above you, you'll have to use 4.1.2 roms from before 0208 for now, until we can fix it and rebuild those patches. We will fix it...we basically have continuous coverage since Android 2.3.4, I am not letting it go now...

Sorry that didn't work. Have you tried again with a later rom? You will see time fixed a Cm10.1 build for the n7100.

This is weird! I saw that the person above provided logs, I am going to post them so the upstream OpenPdroid team can see them. I hmay request one of you test something, pm me if you are experiencing this and are willing to perhaps test a fix when I attempt one.

So you have the same thing as above when it does patch, right? A disappeating Mms app in the launcher? I will look at the logcat provided by the first user. If you have the time, another logcat always helps.

As for the problem with compiling on ubuntu, what is happening is that you already have an aapt in your path, but it is an outdated one. Update your SDK and it should probably be fixed. We package aapts and add them to your path in the script, but whichever one your shell encounters first takes precedence. With most binaries, I could simply call a specific copy or location, but it is apktool that is calling the aapt, not the script.

Maybe I will look into sending a patch to the apktool people, allowing you to point to a specific aapt. But for now, for you, update your sdk. You can try removing the MMs from the update.zip and seeing if that allows you to have functionality. It won't be as secure as with it, but some OpenPdroid is better than none.

(also, the second item on the above features of 2.8.3 release should maybe solve this problem for you already, as it should copy over an Mms.apk if it fails to compile. I say 'should' because it is a hard thing to test, you have to engineer a failure, and my testing isn't that rigourous :). But that won't help you on the disappearing Mms problem anyway, so just a feature plug for no reason, I guess)

Some of those are probably failing just because they are not supported roms, although it is suspicious that they all fail at the same file. Did you try an official CyanogenMod release?

Also, you can patch that PA build, there is very small edit you have to make to the telephony-common.patch...AussieLampChops posted the edits, it is very simple.

I have been promising to add that trick to the autopatcher, it just hasn't been as simple as I thought. I keep adding it, and it keeps tickling other failures on down the line.

Not yet...I am pretty sure I know what the exact problem is for the Nexus 7 failures, it is looking for a png in the wrong folder. But a logcat will hopefully confirm that as well as point out the exact resource and hopefully suggest a fix.

For the Nexus10 and GalaxyTab10, I have heard that tabletUI works with a DPI increase. So I am considering some ways of perhaps resolving that. TabletUI isn't a mod I designed, and it isn't exactly handled in an elegant way as is. If something looks doable, I will do it.

Okay, well that means that something is breaking for the Nook in particular. I actually expect the tabletUI patches to work for the Nook, since they reportedly work for the GalaxtTab, which has the same specs and resolution. Could you please post your autopatcher log and hopefully a logcat? I bet I can fix it with those, and your reward will be (most likely) working tabletUI for the Nook Color...

Did the SlimRom patches fail? I think he said they were still okay, unless I missed something. I think we will need to rebuild for things soon now that AOSP is updating. I hope that will inspire some changes for trouble devices like the toro and toroplus. Plus this rash of ASyncLoader failures has me curious. I would copy it over, but I haven't had time to test that yet.