[Android Software/Hacking General [Developers Only]] mateorod:
I looked at their code at the time they hadn't pulled in anything new. I guess they did. I think I can fix it relatively quickly, look for next release.

As Juggles said, yep. Only AOSP 4.1.2 patches are different and that is because we have to patch the bootclasspath in the boot.img. But it is still compatible with most kernel installers (using koush's AnyKernel...i actually think franco just distributes images, though. If you are using 4.1.2 aosp, it depends.otherwise, yes.)

I have a small list of little things I want to add...one thing I have had trouble with for themes is a way to query screen resolutions, I don't know if it can be done. Also, to make such things really wide, the themers would need to create images that fix at least the major resolutions, HDPI, XHDPI and so on. Looking into that is on the list, I want to add some theme related stuff. But it is a long list at this point, be aware. I am pretty far behind right now.

I know it is not widely known, but Nexus stock roms are actually not AOSP. They are really close, but not quite. Those files are not distibuted with AOSP. We had problems with those exact files in early CM mako roms as well. But adding stock support is possible, just not done. I had some help and ideas given to me by a user (a7657626 (somestringofdigits)).

If you guys want to know what is really at the top of my list, this is it. I know we can do it, I just need to find the time. Karamelos, Juggies, I willl be in touch with something very soon.

Okay, one thing you can do is try and use an earlier rom, maybe from before 0201. And could you get me a logcat please? A bunch of stuff could be happening. What happened here is that there were a bunch of upstream changes on the 0209 or so. But every rom made with the new patches reported massive FCs. I have fixed this problem with the 4.2X roms by using the telephony-common patches from before the upstream changes. But I cannot do that with you, because for 4.1.2, the framework and telephony patches are merged.

Okay, this is what i need, if you are willing to try and debug with me:

logcat

autopatcher log of this rom patched with earlier patches (something like ./auto_patcher ROM.zip openpdroid cm 20130201)

This is needed to test your RIL's behavior as well as hopefully find out what is happening in a larger sense, and also perhaps inform a quick fix I can maybe send you. Thanks.

You can just flash the new nightly, and for a while, the same update.zip made by the autopatcher will work. But eventually it will result in a boot loop (maybe after a week or two.) You do not have to wipe, ever. Just reflash the entire rom, or take that as your sign that it is time to run your currently looping rom through the Autopatcher, boot into recovery and flash the new update.zip.

Never wipe anything due to an autopatcher problem, ok guys?

4.2.2 has been out for two days. doing what we can around here.

Have you tried editing those lines as before? I haven't heard any other complaints...just change that 2 into a zero in three places. I have attempted a couple of automations, but as i told Aussie, properly having this fix aply only when needed has proven to be a bit of a challenge, at least to do so without completely changing how we do things. Pa needs to just merge from upstream already.

Seem pretty explanatory. It has been two days and it took me all Saturday just to get 4.2.2 for OPD. I am going to test all of these mods hopefully tomorrow and then the next release will have them ready. If you are a tinkering sort, you can just change the CEILING variable for whatever mod you want to 4.2.2. You might need to bump the VERSION variable to the same, I cannot remember.

I have pretty much coded most functions of a package manager into this thing by now...I actually have a couple of pretty crazy features lurking in the branches...one of them will query your rom and return all the available mods for your Android version, and ROMTYPE (cm, pa ,etc.).

I have also been working on an 'exhaustive' feature, which would perhaps help some of the more...off-brand roms. This just methodically tries patching each jar with every patch we have for that Android version until it finds a fit or runs out of patches. Not the most efficient thing. Anyway, I don't know why I am talking about that here. Anyone think those sound neat?

This is unlikely to happen. As I said earlier, the current plan is to merge the two framework patches, pd2.0 and OpenPdroid into one. I will NOT be leaving pd2.0 people in the cold. CollegeDev and I are working on how to best make this happen as we speak. The latest Pdroid2.0 changes will be available in the next update to the OpenPdroid patches.

Wait, you are saying that because of this copied over file, you cannot send Mms? can i get a logcat of this please? I have not heard this before, and we have copied this file over to hundreds if not thousands of roms. doesn't mean it isn't possible, but I need to know more.

Try the edits, and send us a logcat if trouble, I guess

Try the 0215 version, I just checked it and it works

Like I said, I need a logcat to debug this...there is some phone related issues in the upstream code, but I thought I had managed all of that for now. So I need more to work on this.

Those are smali files, but as I have talked about some other places, the Nexus stock builds are not the same as AOSP. I know we discussed it some, and I know it sounds like nit-picking, because the differences are so slight. But they result in problems like this and can be crazy frustrating.

These two users both deodexed stock builds and then attempted to run them through our AOSP patches. Which is a fine idea, and I wish it would work. But it just doesn't, not yet. I have the road map to support stock roms. I need to sit down and get to work on it. As things settle down (I feel like a parrot squawking that every week to no purpose...but fingers crossed) I have the stock-roms and on-board stuff burning a hole in my frontal lobe. I want it as bad or worse than you guys do.

Edit: Oh and thanks BIG time to those fo you that have pm'ed me about possibly joining the team and helping create patches. I am putting together a small package for you guys and it will go out tomorrow. The process is not hard, if you have built a rom you are qualified. So thanks! That is what will free me up some and allow for this project to grow instead of merely be maintained.